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

> A use-after-free in the Linux kernel PCI/ASPM subsystem can cause a general protection fault during device hot-unplug, leading to system crashes.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Apr 2025
- **Updated:** 16 Jul 2026
- **Also known as:** BELL-CVE-2024-58093, DEBIAN-CVE-2024-58093, GHSA-xcjf-5v2r-gvc9, ROOT-OS-DEBIAN-11-CVE-2024-58093, ROOT-OS-DEBIAN-12-CVE-2024-58093, ROOT-OS-DEBIAN-13-CVE-2024-58093, UBUNTU-CVE-2024-58093

## What is CVE-2024-58093?

CVE-2024-58093 is a high-severity use after free vulnerability in Linux kernel, published on 16 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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]

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2024-58093?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-58093?

Apply the vendor's patch.

## Is CVE-2024-58093 being exploited?

There is no known exploitation of CVE-2024-58093 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-58093 and fix it if it is affected.

What it is: CVE-2024-58093 is a high-severity use after free vulnerability in Linux kernel, published on 16 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-58093 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-58093/ (Markdown: https://insights.sbomify.com/CVE-2024-58093/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-58093
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-58093
- OSV: https://osv.dev/vulnerability/CVE-2024-58093

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-58093/
Summaries are generated and may contain mistakes; the official description above is the record.