CVE-2022-48849
kernel: drm/amdgpu: bypass tiling flag check in virtual display case (v2)
Overview
Description
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: bypass tiling flag check in virtual display case (v2)
vkms leverages common amdgpu framebuffer creation, and
also as it does not support FB modifier, there is no need
to check tiling flags when initing framebuffer when virtual
display is enabled.
This can fix below calltrace:
amdgpu 0000:00:08.0: GFX9+ requires FB check based on format modifier
WARNING: CPU: 0 PID: 1023 at drivers/gpu/drm/amd/amdgpu/amdgpu_display.c:1150 amdgpu_display_framebuffer_init+0x8e7/0xb40 [amdgpu]
v2: check adev->enable_virtual_display instead as vkms can be
enabled in bare metal as well.
Source: OX vulnerability database
Severity
5.5 · MEDIUM
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Affected packages · 0
No registry package. This ID affects operating system packages only.
Operating systems · 30 fixes
Red Hat 3 releases · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 7 | bpftool +25 | eol |
| 8 | bpftool +45 | wont fix |
| 9 | bpftool +106 | wont fix |
SUSE Linux Enterprise 2 releases · 7 packages
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| 15.4 | kernel-livepatch-5-14-21-150400-24-128-default | 1-150400.9.3.1 | SUSE-SU-2024:2929-1 |
| 15.4 | cluster-md-kmp-default +17 | 5.14.21-150400.24.128.1 | SUSE-SU-2024:2929-1 |
| 15.4 | kernel-default-base | 5.14.21-150400.24.128.1.150400.24.62.1 | SUSE-SU-2024:2929-1 |
| 15.5 | kernel-livepatch-5-14-21-150500-13-64-rt | 1-150500.11.3.1 | SUSE-SU-2024:2894-1 |
| 15.5 | kernel-livepatch-5-14-21-150500-55-73-default | 1-150500.11.3.1 | SUSE-SU-2024:2939-1 |
| 15.5 | kernel-azure +4 | 5.14.21-150500.33.63.1 | SUSE-SU-2024:2947-1 |
3 more rows
SUSE Linux Enterprise Micro 3 releases · 3 packages
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| 5.3 | kernel-rt +1 | 5.14.21-150400.15.88.1 | SUSE-SU-2024:2902-1 |
| 5.3 | kernel-default | 5.14.21-150400.24.128.1 | SUSE-SU-2024:2929-1 |
| 5.3 | kernel-default-base | 5.14.21-150400.24.128.1.150400.24.62.1 | SUSE-SU-2024:2929-1 |
| 5.4 | kernel-rt +1 | 5.14.21-150400.15.88.1 | SUSE-SU-2024:2902-1 |
| 5.4 | kernel-default | 5.14.21-150400.24.128.1 | SUSE-SU-2024:2929-1 |
| 5.4 | kernel-default-base | 5.14.21-150400.24.128.1.150400.24.62.1 | SUSE-SU-2024:2929-1 |
3 more rows
debian 3 releases · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 12 | linux | 5.16.18-1 |
| 13 | linux | 5.16.18-1 |
| 14 | linux | 5.16.18-1 |
echo 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| linux | 5.16.18-1 |
openSUSE Leap Micro 1 release · 3 packages
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| 5.5 | kernel-rt | 5.14.21-150500.13.64.1 | SUSE-SU-2024:2894-1 |
| 5.5 | kernel-default | 5.14.21-150500.55.73.1 | SUSE-SU-2024:2939-1 |
| 5.5 | kernel-default-base | 5.14.21-150500.55.73.1.150500.6.33.8 | SUSE-SU-2024:2939-1 |
root.io debian 2 releases · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 12 | rootio-linux | 5.16.18-1 |
| 13 | rootio-linux | 5.16.18-1 |
References
- access.redhat.com https://access.redhat.com/security/cve/CVE-2022-48849
- git.kernel.org https://git.kernel.org/stable/c/cb29021be49858059138f75d6311a7c35a9379b2
- git.kernel.org https://git.kernel.org/stable/c/e2b993302f40c4eb714ecf896dd9e1c5be7d4cd7
- git.kernel.org https://git.kernel.org/stable/c/fcd1d79aa943fff4fbaa0cce1d576995a7960699
- lore.kernel.org https://lore.kernel.org/linux-cve-announce/2024071624-CVE-2022-48849-3119@gregkh/T
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2022-48849
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2022-48849
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.