Security readout for executives and security teams
Plain-English summary
This is a Linux kernel use-after-free flaw in PCI endpoint cleanup. A local low-privileged user could potentially trigger serious confidentiality, integrity, and availability impact on affected systems. The source bundle does not show active exploitation.
Executive priority
Treat as high priority for affected Linux hosts, especially shared systems, appliances, or embedded platforms with local user access. It is not currently evidenced as exploited, so prioritize patching through normal high-severity kernel update processes.
Technical view
pci_epc_destroy() released a PCI domain ID using epc->dev after device_unregister() had freed it, and also used the wrong device for the domain. The fix releases the domain before unregistering and uses epc->dev.parent.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions with PCI endpoint controller code in use or reachable. The bundle lists Linux 6.12 through 6.13 affected, with stable kernel fix references. Distribution backports may change practical exposure.
Exploitation context
The CVSS vector is local, low complexity, low privileges, and no user interaction. KEV is false in the bundle, and no provided source states active exploitation or public exploit availability.
Researcher notes
Key issue is object lifetime and incorrect parent device use in pci_epc_destroy(). Validate whether downstream kernels contain the fix, not just their version string. Evidence is limited to CVE metadata and upstream stable commits.
Mitigation direction
- Apply a vendor kernel update that includes the referenced stable fixes.
- Check Linux distribution advisories for backported fixed kernel packages.
- Prioritize systems exposing PCI endpoint functionality or untrusted local users.
- Limit local shell access on affected systems until patched.
- Track vendor guidance if no packaged fix is available.
Validation and detection
- Inventory kernel versions across Linux fleets.
- Map vendor packages to the referenced stable fix commits.
- Check whether PCI endpoint controller drivers are enabled or loaded.
- Confirm updated systems boot the fixed kernel.
- Run existing regression tests for PCI endpoint workloads where applicable.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-416: 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.
Open ATT&CK lookupCVE-2024-56561 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/c74a1df6c2a2df7dd45c3fc1a5edc29a075dcf22CVE reference, Linux
- https://git.kernel.org/stable/c/4acc902ed3743edd4ac2d3846604a99d17104359CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.