CVE-2024-41096: PCI/MSI: Fix UAF in msi_capability_init
Noroxi assessment
Priority: Monitor (action score 31/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.24% (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 0ae40b2d0a5de6b045504098e365d4fdff5bbeba, 45fc8d20e0768ab0a0ad054081d0f68aa3c83976, 9eee5330656bf92f51cb1f09b2dc9f8cf975b3d1; azl3 kernel 6.6.35.1-5 on Azure Linux 3.0 6.6.43.1-7; azl3 kernel 6.6.43.1-7 on Azure Linux 3.0 6.6.43.1-7.
Low priority for now. Upgrade to Linux Linux 0ae40b2d0a5de6b045504098e365d4fdff5bbeba, 45fc8d20e0768ab0a0ad054081d0f68aa3c83976, 9eee5330656bf92f51cb1f09b2dc9f8cf975b3d1; azl3 kernel 6.6.35.1-5 on Azure Linux 3.0 6.6.43.1-7; azl3 kernel 6.6.43.1-7 on Azure Linux 3.0 6.6.43.1-7 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: PCI/MSI: Fix UAF in msi_capability_init KFENCE reports the following UAF: BUG: KFENCE: use-after-free read in __pci_enable_msi_range+0x2c0/0x488 Use-after-free read at 0x0000000024629571 (in kfence-#12): __pci_enable_msi_range+0x2c0/0x488 pci_alloc_irq_vectors_affinity+0xec/0x14c pci_alloc_irq_vectors+0x18/0x28 kfence-#12: 0x0000000008614900-0x00000000e06c228d, size=104, cache=kmalloc-128 allocated by task 81 on cpu 7 at 10.808142s: __kmem_cache_alloc_node+0x1f0/0x2bc kmalloc_trace+0x44/0x138 msi_alloc_desc+0x3c/0x9c msi_domain_insert_msi_desc+0x30/0x78 msi_setup_msi_desc+0x13c/0x184 __pci_enable_msi_range+0x258/0x488 pci_alloc_irq_vectors_affinity+0xec/0x14c pci_alloc_irq_vectors+0x18/0x28 freed by task 81 on cpu 7 at 10.811436s: msi_domain_free_descs+0xd4/0x10c msi_domain_free_locked.part.0+0xc0/0x1d8 msi_domain_alloc_irqs_all_locked+0xb4/0xbc pci_msi_setup_msi_irqs+0x30/0x4c __pci_enable_msi_range+0x2a8/0x488 pci_alloc_irq_vectors_affinity+0xec/0x14c pci_alloc_irq_vectors+0x18/0x28 Descriptor allocation done in: __pci_enable_msi_range msi_capability_init msi_setup_msi_desc msi_insert_msi_desc msi_domain_insert_msi_desc msi_alloc_desc ... Freed in case of failure in __msi_domain_alloc_locked() __pci_enable_msi_range msi_capability_init pci_msi_setup_msi_irqs msi_domain_alloc_irqs_all_locked msi_domain_alloc_locked __msi_domain_alloc_locked => fails msi_domain_free_locked ... That failure propagates back to pci_msi_setup_msi_irqs() in msi_capability_init() which accesses the descriptor for unmasking in the error exit path. Cure it by copying the descriptor and using the copy for the error exit path unmask operation. [ tglx: Massaged change log ]
- Published
- Jul 29, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-416
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 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.
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Is your version affected? Check itNoroxi 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 |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
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.17affected
- bf6e054e0e3fbc9614355b760e18c8a14f952a4e and later · before 0ae40b2d0a5de6b045504098e365d4fdff5bbebaaffected · git
- bf6e054e0e3fbc9614355b760e18c8a14f952a4e and later · before ff1121d2214b794dc1772081f27bdd90721a84bcaffected · git
- bf6e054e0e3fbc9614355b760e18c8a14f952a4e and later · before 45fc8d20e0768ab0a0ad054081d0f68aa3c83976affected · git
- bf6e054e0e3fbc9614355b760e18c8a14f952a4e and later · before 9eee5330656bf92f51cb1f09b2dc9f8cf975b3d1affected · git
- before 5.17not affected · semver
- 6.1.109 and later · up to and including 6.1.*not affected · semver
- 6.6.37 and later · up to and including 6.6.*not affected · semver
- 6.9.8 and later · up to and including 6.9.*not affected · semver
- 6.10 and laternot affected · original_commit_for_fix
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel5.17 and later · before 6.1.109
- linux linux kernel6.2 and later · before 6.6.37
- linux linux kernel6.7 and later · before 6.9.8
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 6.1.112-1 | 6.1.112-1 |
| Debian:13 | linux | before 6.9.8-1 | 6.9.8-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-2024-41094Jul 29, 2024 · drm/fbdev-dma: Only set smem_start is enable per module option22Monitor
- ← EarlierCVE-2024-41095Jul 29, 2024 · drm/nouveau/dispnv04: fix null pointer dereference in nv17_tv_get_ld_modes22Monitor
- Later →CVE-2024-41097Jul 29, 2024 · usb: atm: cxacru: fix endpoint checking in cxacru_bind()22Monitor
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 | 0ae40b2d0a5de6b045504098e365d4fdff5bbeba | Vendor (CNA) |
| Linux Linux | 45fc8d20e0768ab0a0ad054081d0f68aa3c83976 | Vendor (CNA) |
| Linux Linux | 9eee5330656bf92f51cb1f09b2dc9f8cf975b3d1 | Vendor (CNA) |
| Linux Linux | ff1121d2214b794dc1772081f27bdd90721a84bc | Vendor (CNA) |
| azl3 kernel 6.6.35.1-5 on Azure Linux 3.0 | 6.6.43.1-7 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.43.1-7 on Azure Linux 3.0 | 6.6.43.1-7 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.112-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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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 (1)
- 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.