LiveActive security incident?Get immediate response
CVE Record

CVE-2024-58093: PCI/ASPM: Fix link state exit during switch upstream function removal

In the Linux kernel, the following vulnerability has been resolved: PCI/ASPM: Fix link state exit during switch upstream function removal Before 456d8aa37d0f ("PCI/ASPM: Disable ASPM on MFD function removal to avoid use-after-free"), we would free the ASPM link only after the last function on the bus pertaining to the given link was removed. That was too late. If function 0 is removed before sibling function, link->downstream would point to free'd memory after. After above change, we freed the ASPM parent link state upon any function removal on the bus pertaining to a given link. That is too early. If the link is to a PCIe switch with MFD on the upstream port, then removing functions other than 0 first would free a link which still remains parent_link to the remaining downstream ports. The resulting GPFs are especially frequent during hot-unplug, because pciehp removes devices on the link bus in reverse order. On that switch, function 0 is the virtual P2P bridge to the internal bus. Free exactly when function 0 is removed -- before the parent link is obsolete, but after all subordinate links are gone. [kwilczynski: commit log]

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash affected systems during certain PCIe device removal scenarios. It involves PCIe power-management state being freed at the wrong time, especially around PCIe switches and hot-unplug. The public data does not show active exploitation or remote attack evidence.

Executive priority

Treat this as a targeted stability risk for Linux infrastructure with specialized PCIe hardware. Patch through normal kernel maintenance, but prioritize environments where hot-plug, PCIe switches, or removable devices are operationally important.

Technical view

The flaw is in PCI/ASPM link-state cleanup. Freeing a parent ASPM link on the wrong upstream function removal can leave remaining downstream ports referencing freed memory. The description reports general protection faults, especially during pciehp hot-unplug. The fix frees the link when function 0 is removed.

Likely exposure

Exposure is most likely on Linux systems running affected kernels with PCIe ASPM, PCIe switches, multifunction upstream ports, and hot-plug or device-removal workflows. Generic Linux systems without that hardware pattern may have limited practical exposure. Version evidence in the bundle is incomplete and should be mapped to vendor kernels.

Exploitation context

The bundle has no KEV listing and provides no cited evidence of active exploitation. The described impact is kernel faults during device removal, suggesting operational denial-of-service risk rather than confirmed remote compromise. No exploit maturity, privilege requirement, or attack vector is established in the provided sources.

Researcher notes

Evidence supports a kernel memory-lifetime bug causing GPFs in specific PCIe ASPM teardown paths. The bundle does not provide CVSS, CWE, exploit status, or full affected-version mapping. Distro kernel backports may differ from upstream version labels.

Mitigation direction

  • Update to a vendor kernel that includes the referenced PCI/ASPM fix.
  • Check Linux distribution advisories for backported fixes matching your kernel package.
  • Prioritize systems using PCIe hot-plug, switches, or removable accelerator/storage devices.
  • Avoid unnecessary PCIe hot-unplug operations on suspected affected systems until patched.
  • Track kernel change notes for commit cbf937dcadfd or equivalent backport.

Validation and detection

  • Inventory Linux kernel versions and vendor package release notes.
  • Confirm whether PCIe ASPM and pciehp are used on relevant hardware.
  • Review kernel logs for GPFs around PCIe hot-unplug or device removal.
  • Verify the vendor kernel contains the referenced stable fix or equivalent.
  • Test hot-unplug behavior only in a lab or maintenance window.
Prepared
Confidence
medium
Sources
3

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-58093 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
0ADP providers
2Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux456d8aa37d0f56fc9e985e812496e861dcd6f2f2, 666e7f9d60cee23077ea3e6331f6f8a19f7ea03f, 7badf4d6f49a358a01ab072bbff88d3ee886c33b, 9856c0de49052174ab474113f4ba40c02aaee086, 7aecdd47910c51707696e8b0e045b9f88bd4230f, d51d2eeae4ce54d542909c4d9d07bf371a78592c, 4203722d51afe3d239e03f15cc73efdf023a7103, 5.4.251, 5.10.188, 5.15.121, 6.1.39, 6.3.13, 6.4.4unaffected
LinuxLinux6.5, 0, 6.15affected
Weakness

CWE details

No CWE listed

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