In the Linux kernel, the following vulnerability has been resolved:
9p/xen: fix release of IRQ
Kernel logs indicate an IRQ was double-freed.
Pass correct device ID during IRQ release.
[Dominique: remove confusing variable reset to 0]
Security readout for executives and security teams
Plain-English summary
A Linux kernel flaw in the Xen 9p filesystem transport can release the same interrupt resource twice because the wrong device identifier is supplied during cleanup. This may destabilize an affected system and potentially compromise confidentiality, integrity, or availability. Exposure depends on using the affected kernel code and configuration.
Executive priority
Treat as a high-priority kernel maintenance issue for Xen environments using 9p. Patch exposed systems during the next expedited maintenance window, accelerating action for sensitive or multi-tenant workloads. Systems not using the affected 9p/xen path are lower priority pending configuration validation.
Technical view
CVE-2024-56704 is a CWE-415 double-free in Linux 9p/xen IRQ cleanup. The resolved implementation passes the correct device ID when releasing the IRQ. The supplied CVSS 3.1 score is 8.4 with local access, low complexity, no privileges or user interaction, unchanged scope, and high impact ratings.
Likely exposure
Likely exposure is concentrated in systems running affected Linux kernel builds where the Xen 9p transport is present and its IRQ release path can execute. The source bundle lists multiple affected kernel versions, but its duplicated commit entries and abbreviated version data do not establish precise distribution-specific boundaries.
Exploitation context
The supplied record is not in KEV, and no cited source establishes active exploitation or a public working exploit. The CVSS vector describes a local attack surface. Kernel logs showing a double-freed IRQ motivated the fix, but the bundle does not document demonstrated privilege escalation or other exploitation outcomes.
Researcher notes
The defect concerns mismatched IRQ registration and release identity, resulting in a reported double-free. Nine stable-kernel commit references are supplied, suggesting backports across maintained branches. Exact affected and fixed package versions must be determined through distribution guidance; the bundle's version list alone is insufficient for reliable fleet matching.
Mitigation direction
Install a supported vendor kernel containing the applicable upstream stable fix.
Check distribution advisories for the correct package version and backport status.
Prioritize Xen hosts or guests using the Linux 9p transport.
Follow vendor guidance if immediate kernel replacement is operationally impractical.
Validation and detection
Inventory Linux kernel versions across Xen hosts and guests.
Identify systems configured to use the Xen 9p transport.
Compare installed kernels with vendor advisories and the referenced stable commits.
Review kernel logs for IRQ double-free or related 9p/xen cleanup errors.
After updating, confirm the fixed kernel is running following reboot.
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.
cwe · low confidence lookup
CWE-415: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
2CVSS vectors
3Timeline events
2ADP providers
12Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.