CVE-2024-35989: dmaengine: idxd: Fix oops during rmmod on single-CPU platforms
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.21% (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 023b6390a15a98f9c3aa5e7da78d485d5384a08e, 47533176fdcef17b114a6f688bc872901c1ec6bb, 9edd3aa34d50f27b97be30b2ba4a6af0945ff56b.
Low priority for now. Upgrade to Linux Linux 023b6390a15a98f9c3aa5e7da78d485d5384a08e, 47533176fdcef17b114a6f688bc872901c1ec6bb, 9edd3aa34d50f27b97be30b2ba4a6af0945ff56b 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: dmaengine: idxd: Fix oops during rmmod on single-CPU platforms During the removal of the idxd driver, registered offline callback is invoked as part of the clean up process. However, on systems with only one CPU online, no valid target is available to migrate the perf context, resulting in a kernel oops: BUG: unable to handle page fault for address: 000000000002a2b8 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD 1470e1067 P4D 0 Oops: 0002 [#1] PREEMPT SMP NOPTI CPU: 0 PID: 20 Comm: cpuhp/0 Not tainted 6.8.0-rc6-dsa+ #57 Hardware name: Intel Corporation AvenueCity/AvenueCity, BIOS BHSDCRB1.86B.2492.D03.2307181620 07/18/2023 RIP: 0010:mutex_lock+0x2e/0x50 ... Call Trace: <TASK> __die+0x24/0x70 page_fault_oops+0x82/0x160 do_user_addr_fault+0x65/0x6b0 __pfx___rdmsr_safe_on_cpu+0x10/0x10 exc_page_fault+0x7d/0x170 asm_exc_page_fault+0x26/0x30 mutex_lock+0x2e/0x50 mutex_lock+0x1e/0x50 perf_pmu_migrate_context+0x87/0x1f0 perf_event_cpu_offline+0x76/0x90 [idxd] cpuhp_invoke_callback+0xa2/0x4f0 __pfx_perf_event_cpu_offline+0x10/0x10 [idxd] cpuhp_thread_fun+0x98/0x150 smpboot_thread_fn+0x27/0x260 smpboot_thread_fn+0x1af/0x260 __pfx_smpboot_thread_fn+0x10/0x10 kthread+0x103/0x140 __pfx_kthread+0x10/0x10 ret_from_fork+0x31/0x50 __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30 <TASK> Fix the issue by preventing the migration of the perf context to an invalid target.
- Published
- May 20, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 11th 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 kernel5.13 and later · before 5.15.158
- linux linux kernel5.16 and later · before 6.1.90
- linux linux kernel6.2 and later · before 6.6.30
- linux linux kernel6.7 and later · before 6.8.9
- linux linux kernel6.9
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
- 5.13affected
- 81dd4d4d6178306ab31db91bdc7353d485bdafce and later · before 9edd3aa34d50f27b97be30b2ba4a6af0945ff56baffected · git
- 81dd4d4d6178306ab31db91bdc7353d485bdafce and later · before 023b6390a15a98f9c3aa5e7da78d485d5384a08eaffected · git
- 81dd4d4d6178306ab31db91bdc7353d485bdafce and later · before f976eca36cdf94e32fa4f865db0e7c427c9aa33caffected · git
- 81dd4d4d6178306ab31db91bdc7353d485bdafce and later · before 47533176fdcef17b114a6f688bc872901c1ec6bbaffected · git
- 81dd4d4d6178306ab31db91bdc7353d485bdafce and later · before f221033f5c24659dc6ad7e5cf18fb1b075f4a8beaffected · git
- before 5.13not affected · semver
- 5.15.158 and later · up to and including 5.15.*not affected · semver
- 6.1.90 and later · up to and including 6.1.*not affected · semver
- 6.6.30 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | bpftool | before 7.3.0-427.40.1.el9_4 | 7.3.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-core | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-core | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-devel | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-devel-matched | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-devel | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-devel-matched | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules-core | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules-extra | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-abi-stablelists | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-core | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-cross-headers | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-debug | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-debug-core | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-debug-devel | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-debug-devel-matched | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
| AlmaLinux:9 | kernel-debug-modules | before 5.14.0-427.40.1.el9_4 | 5.14.0-427.40.1.el9_4 |
+96
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-2024-35986May 20, 2024 · phy: ti: tusb1210: Resolve charger-det crash if charger psy is unregistered28Monitor
- ← EarlierCVE-2024-35987May 20, 2024 · riscv: Fix loading 64-bit NOMMU kernels past the start of RAM22Monitor
- Later →CVE-2024-35991May 20, 2024 · dmaengine: idxd: Convert spinlock to mutex to lock evl workqueue22Monitor
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 | 023b6390a15a98f9c3aa5e7da78d485d5384a08e | Vendor (CNA) |
| Linux Linux | 47533176fdcef17b114a6f688bc872901c1ec6bb | Vendor (CNA) |
| Linux Linux | 9edd3aa34d50f27b97be30b2ba4a6af0945ff56b | Vendor (CNA) |
| Linux Linux | f221033f5c24659dc6ad7e5cf18fb1b075f4a8be | Vendor (CNA) |
| Linux Linux | f976eca36cdf94e32fa4f865db0e7c427c9aa33c | Vendor (CNA) |
| almalinux:bpftool | 7.3.0-427.40.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel | 5.14.0-427.40.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-427.40.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-427.40.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-427.40.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-427.40.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-427.40.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-427.40.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-427.40.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-427.40.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-427.40.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-427.40.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.1.90-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.3.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-427.40.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
+1
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.
No history yet (it accumulates with the daily EPSS job).
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).
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-secondary
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 (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.