CVE-2022-48704 json
drm/radeon: add a force flush to delay work when radeon
published 2024-05-03 2 y ago modified 2026-06-17 4 mo ago also EUVD-2022-53583
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 14%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
drm/radeon: add a force flush to delay work when radeon
Although radeon card fence and wait for gpu to finish processing current batch rings, there is still a corner case that radeon lockup work queue may not be fully flushed, and meanwhile the radeon_suspend_kms() function has called pci_set_power_state() to put device in D3hot state. Per PCI spec rev 4.0 on 5.3.1.4.1 D3hot State. > Configuration and Message requests are the only TLPs accepted by a Function in > the D3hot state. All other received Requests must be handled as Unsupported Requests, > and all received Completions may optionally be handled as Unexpected Completions. This issue will happen in following logs: Unable to handle kernel paging request at virtual address 00008800e0008010 CPU 0 kworker/0:3(131): Oops 0 pc = [<ffffffff811bea5c>] ra = [<ffffffff81240844>] ps = 0000 Tainted: G W pc is at si_gpu_check_soft_reset+0x3c/0x240 ra is at si_dma_is_lockup+0x34/0xd0 v0 = 0000000000000000 t0 = fff08800e0008010 t1 = 0000000000010000 t2 = 0000000000008010 t3 = fff00007e3c00000 t4 = fff00007e3c00258 t5 = 000000000000ffff t6 = 0000000000000001 t7 = fff00007ef078000 s0 = fff00007e3c016e8 s1 = fff00007e3c00000 s2 = fff00007e3c00018 s3 = fff00007e3c00000 s4 = fff00007fff59d80 s5 = 0000000000000000 s6 = fff00007ef07bd98 a0 = fff00007e3c00000 a1 = fff00007e3c016e8 a2 = 0000000000000008 a3 = 0000000000000001 a4 = 8f5c28f5c28f5c29 a5 = ffffffff810f4338 t8 = 0000000000000275 t9 = ffffffff809b66f8 t10 = ff6769c5d964b800 t11= 000000000000b886 pv = ffffffff811bea20 at = 0000000000000000 gp = ffffffff81d89690 sp = 00000000aa814126 Disabling lock debugging due to kernel taint Trace: [<ffffffff81240844>] si_dma_is_lockup+0x34/0xd0 [<ffffffff81119610>] radeon_fence_check_lockup+0xd0/0x290 [<ffffffff80977010>] process_one_work+0x280/0x550 [<ffffffff80977350>] worker_thread+0x70/0x7c0 [<ffffffff80977410>] worker_thread+0x130/0x7c0 [<ffffffff80982040>] kthread+0x200/0x210 [<ffffffff809772e0>] worker_thread+0x0/0x7c0 [<ffffffff80981f8c>] kthread+0x14c/0x210 [<ffffffff80911658>] ret_from_kernel_thread+0x18/0x20 [<ffffffff80981e40>] kthread+0x0/0x210 Code: ad3e0008 43f0074a ad7e0018 ad9e0020 8c3001e8 40230101 <88210000> 4821ed21 So force lockup work queue flush to fix this problem.
Patch / fix
- Linux Linux 4.9.328, 4.14.293, 4.19.258, 5.4.213, 5.10.143, 5.15.68, 5.19.9, 6.0
- linux Debian 14, Debian 13, Debian 12 5.19.11-1
debian advisories DEBIAN-CVE-2022-48704
- linux Ubuntu 18.04 LTS 4.15.0-201.212
- linux Ubuntu 20.04 LTS 5.4.0-136.153
- linux Ubuntu 22.04 LTS 5.15.0-57.63
- linux-aws Ubuntu 18.04 LTS 4.15.0-1147.159
- linux-aws Ubuntu 20.04 LTS 5.4.0-1093.101
- linux-aws Ubuntu 22.04 LTS 5.15.0-1027.31
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1097.106
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1026.33
ubuntu advisories UBUNTU-CVE-2022-48704
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-rt SLE Micro 5.2, SLE Micro 5.1 5.3.18-150300.211.1
- kernel-source-rt SLE Micro 5.2, SLE Micro 5.1 5.3.18-150300.211.1
- kernel-rt SLE Micro 5.4, SLE Micro 5.3 5.14.21-150400.15.106.1
- kernel-source-rt SLE Micro 5.4, SLE Micro 5.3 5.14.21-150400.15.106.1
- kernel-64kb SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS, SLE High Performance Computing 15 SP4-ESPOS 5.14.21-150400.24.122.2
- kernel-syms SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +3 more 5.14.21-150400.24.122.1
- kernel-source SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +3 more 5.14.21-150400.24.122.1
- kernel-default SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE Micro 5.4 +9 more 5.14.21-150400.24.122.2
suse advisories SUSE-SU-2025:01995-1SUSE-SU-2025:0231-1SUSE-SU-2024:2189-1SUSE-SU-2024:2185-1SUSE-SU-2024:2184-1SUSE-SU-2024:2011-1
- git.kernel.org/stable/c/b878da58df2c40b08914d3960e2224040fd1fbfe commit
- git.kernel.org/stable/c/4e25e8f27fdbdc6fd55cc572a9939bf24500b9e8 commit
- git.kernel.org/stable/c/c0a45f41fde4a0f2c900f719817493ee5c4a5aa3 commit
- git.kernel.org/stable/c/c72d97146fc5a4dff381b1737f6167e89860430d commit
- git.kernel.org/stable/c/826b46fd5974113515abe9e4fc8178009a8ce18c commit
- git.kernel.org/stable/c/5a7a5b2edac4b05abd744eeaebda46d9dacd952d commit
- git.kernel.org/stable/c/16cb367daa446923d82e332537f446a4cc784b40 commit
- git.kernel.org/stable/c/f461950fdc374a3ada5a63c669d997de4600dffe commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-48704 updated cvss 5.5
kernel: drm/radeon: add a force flush to delay work when radeon
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +82 moreaffected: no fix available
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/b878da58df2c40b08914d3960e2224040fd1fbfe
patch
-
git.kernel.org
/stable/c/4e25e8f27fdbdc6fd55cc572a9939bf24500b9e8
patch
-
git.kernel.org
/stable/c/c0a45f41fde4a0f2c900f719817493ee5c4a5aa3
patch
-
git.kernel.org
/stable/c/c72d97146fc5a4dff381b1737f6167e89860430d
patch
-
git.kernel.org
/stable/c/826b46fd5974113515abe9e4fc8178009a8ce18c
patch
-
git.kernel.org
/stable/c/5a7a5b2edac4b05abd744eeaebda46d9dacd952d
patch
-
git.kernel.org
/stable/c/16cb367daa446923d82e332537f446a4cc784b40
patch
-
git.kernel.org
/stable/c/f461950fdc374a3ada5a63c669d997de4600dffe
patch
Sources
- CVE List CVE-2022-48704
- NVD CVE-2022-48704
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.