LiveActive security incident?Get immediate response
CVE Record

CVE-2024-38385: genirq/irqdesc: Prevent use-after-free in irq_find_at_or_after()

In the Linux kernel, the following vulnerability has been resolved: genirq/irqdesc: Prevent use-after-free in irq_find_at_or_after() irq_find_at_or_after() dereferences the interrupt descriptor which is returned by mt_find() while neither holding sparse_irq_lock nor RCU read lock, which means the descriptor can be freed between mt_find() and the dereference: CPU0 CPU1 desc = mt_find() delayed_free_desc(desc) irq_desc_get_irq(desc) The use-after-free is reported by KASAN: Call trace: irq_get_next_irq+0x58/0x84 show_stat+0x638/0x824 seq_read_iter+0x158/0x4ec proc_reg_read_iter+0x94/0x12c vfs_read+0x1e0/0x2c8 Freed by task 4471: slab_free_freelist_hook+0x174/0x1e0 __kmem_cache_free+0xa4/0x1dc kfree+0x64/0x128 irq_kobj_release+0x28/0x3c kobject_put+0xcc/0x1e0 delayed_free_desc+0x14/0x2c rcu_do_batch+0x214/0x720 Guard the access with a RCU read lock section.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel memory-safety bug in interrupt descriptor handling. A race can leave kernel code using a freed interrupt descriptor, which can crash or destabilize affected systems. The supplied sources do not provide CVSS, public exploit evidence, or active exploitation claims.

Executive priority

Treat this as a kernel reliability and safety update with unknown exploitability. It is not KEV-listed in the supplied data, so prioritize through normal kernel patch governance unless exposed systems show instability or vendor guidance raises urgency.

Technical view

irq_find_at_or_after() dereferenced an interrupt descriptor returned by mt_find() without sparse_irq_lock or an RCU read-side lock. Another CPU could free the descriptor before irq_desc_get_irq() uses it, producing a use-after-free. The kernel fix guards the access with RCU read locking.

Likely exposure

Exposure is limited to systems running affected Linux kernel builds. The bundle lists Linux version markers including 6.5, 6.6.34, 6.9.5, and 6.10, but exact distribution impact depends on vendor backports and packaging.

Exploitation context

The bundle shows a KASAN-detected use-after-free during kernel paths involving irq_get_next_irq() and show_stat(). It does not show a weaponized exploit, remote attack path, privilege requirement, CVSS score, or CISA KEV listing.

Researcher notes

Evidence is strongest for a concurrency use-after-free fixed by adding an RCU read-side critical section. The source bundle lacks CVSS, CWE, affected distro mapping, exploitability analysis, and proof of active exploitation, so conclusions should stay bounded to upstream kernel evidence.

Mitigation direction

  • Apply Linux stable or distribution kernel updates containing the referenced irqdesc fix.
  • Confirm vendor advisories for your distribution before assuming a kernel package is fixed.
  • Prioritize hosts on affected kernel lines, especially systems requiring high availability.
  • Plan reboot windows where kernel package updates require restart.
  • If patch timing is constrained, monitor for kernel crashes or KASAN use-after-free reports.

Validation and detection

  • Inventory running kernel versions across Linux servers, endpoints, and appliances.
  • Check whether installed kernels include the referenced upstream stable commits.
  • Review distribution security changelogs for CVE-2024-38385 or irqdesc RCU fixes.
  • Confirm patched hosts have booted into the updated kernel.
  • Search kernel logs for related KASAN, irqdesc, or use-after-free messages.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-38385 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux721255b9826bd11c7a38b585905fc2dd0fb94e52, 721255b9826bd11c7a38b585905fc2dd0fb94e52, 721255b9826bd11c7a38b585905fc2dd0fb94e52unaffected
LinuxLinux6.5, 0, 6.6.34, 6.9.5, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.