CVE-2022-48704: drm/radeon: add a force flush to delay work when radeon
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 16cb367daa446923d82e332537f446a4cc784b40, 4e25e8f27fdbdc6fd55cc572a9939bf24500b9e8, 5a7a5b2edac4b05abd744eeaebda46d9dacd952d.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 16cb367daa446923d82e332537f446a4cc784b40, 4e25e8f27fdbdc6fd55cc572a9939bf24500b9e8, 5a7a5b2edac4b05abd744eeaebda46d9dacd952d or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 3, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 4.9.328
- linux linux kernel4.10 and later · before 4.14.293
- linux linux kernel4.15 and later · before 4.19.258
- linux linux kernel4.20 and later · before 5.4.213
- linux linux kernel5.5 and later · before 5.10.143
- linux linux kernel5.11 and later · before 5.15.68
- linux linux kernel5.16 and later · before 5.19.9
- linux linux kernel6.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.18affected
- 0bfa4b41268ad5fd741f16f484e4fee190822ec6 and later · before b878da58df2c40b08914d3960e2224040fd1fbfeaffected · git
- 0bfa4b41268ad5fd741f16f484e4fee190822ec6 and later · before 4e25e8f27fdbdc6fd55cc572a9939bf24500b9e8affected · git
- 0bfa4b41268ad5fd741f16f484e4fee190822ec6 and later · before c0a45f41fde4a0f2c900f719817493ee5c4a5aa3affected · git
- 0bfa4b41268ad5fd741f16f484e4fee190822ec6 and later · before c72d97146fc5a4dff381b1737f6167e89860430daffected · git
- 0bfa4b41268ad5fd741f16f484e4fee190822ec6 and later · before 826b46fd5974113515abe9e4fc8178009a8ce18caffected · git
- 0bfa4b41268ad5fd741f16f484e4fee190822ec6 and later · before 5a7a5b2edac4b05abd744eeaebda46d9dacd952daffected · git
- 0bfa4b41268ad5fd741f16f484e4fee190822ec6 and later · before 16cb367daa446923d82e332537f446a4cc784b40affected · git
- 0bfa4b41268ad5fd741f16f484e4fee190822ec6 and later · before f461950fdc374a3ada5a63c669d997de4600dffeaffected · git
- before 3.18not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 5.19.11-1 | 5.19.11-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-48690May 3, 2024 · ice: Fix DMA mappings leak22Monitor
- ← EarlierCVE-2022-48695May 3, 2024 · scsi: mpt3sas: Fix use-after-free warning31Monitor
- Later →CVE-2022-48705May 3, 2024 · wifi: mt76: mt7921e: fix crash in chip reset fail22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 16cb367daa446923d82e332537f446a4cc784b40 | Vendor (CNA) |
| Linux Linux | 4e25e8f27fdbdc6fd55cc572a9939bf24500b9e8 | Vendor (CNA) |
| Linux Linux | 5a7a5b2edac4b05abd744eeaebda46d9dacd952d | Vendor (CNA) |
| Linux Linux | 826b46fd5974113515abe9e4fc8178009a8ce18c | Vendor (CNA) |
| Linux Linux | b878da58df2c40b08914d3960e2224040fd1fbfe | Vendor (CNA) |
| Linux Linux | c0a45f41fde4a0f2c900f719817493ee5c4a5aa3 | Vendor (CNA) |
| Linux Linux | c72d97146fc5a4dff381b1737f6167e89860430d | Vendor (CNA) |
| Linux Linux | f461950fdc374a3ada5a63c669d997de4600dffe | Vendor (CNA) |
| debian:linux | 5.19.11-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0494 · May 16, 2024(Linux Kernel Güncellemesi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/4e25e8f27fdbdc6fd55cc572a9939bf24500b9e8
- git.kernel.org/stable/c/5a7a5b2edac4b05abd744eeaebda46d9dacd952d
- git.kernel.org/stable/c/826b46fd5974113515abe9e4fc8178009a8ce18c
- git.kernel.org/stable/c/b878da58df2c40b08914d3960e2224040fd1fbfe
- git.kernel.org/stable/c/c0a45f41fde4a0f2c900f719817493ee5c4a5aa3
- git.kernel.org/stable/c/c72d97146fc5a4dff381b1737f6167e89860430d
- git.kernel.org/stable/c/f461950fdc374a3ada5a63c669d997de4600dffe
Vendor advisories and official records. Exploit/PoC links are deliberately left out.