Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0a0f9aecf66b98959aab7fb5764b4b3e522f4f5b, 4d96930239981f312821a4065db8cc0f8240a173, 5.10.236; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 CBL-Mariner Releases.

Low priority for now. Upgrade to Linux Linux 0a0f9aecf66b98959aab7fb5764b4b3e522f4f5b, 4d96930239981f312821a4065db8cc0f8240a173, 5.10.236; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 CBL-Mariner Releases or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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]

Published
Apr 16, 2025
Updated
Nov 5, 2026
EPSS
0.2% · 14th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-58093

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.4.251 and later · before 5.5
  • linux linux kernel5.10.188 and later · before 5.11
  • linux linux kernel5.15.121 and later · before 5.16
  • linux linux kernel6.1.39 and later · before 6.2
  • linux linux kernel6.3.13 and later · before 6.4
  • linux linux kernel6.4.4 and later · before 6.15

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • d51d2eeae4ce54d542909c4d9d07bf371a78592c, 4203722d51afe3d239e03f15cc73efdf023a7103, 6.5affected
    • 666e7f9d60cee23077ea3e6331f6f8a19f7ea03f and later · before 0a0f9aecf66b98959aab7fb5764b4b3e522f4f5baffected · git
    • 7badf4d6f49a358a01ab072bbff88d3ee886c33b and later · before 62db339ecc3d58d8fd83a9e4d80061cd943bb6e2affected · git
    • 9856c0de49052174ab474113f4ba40c02aaee086 and later · before e5cd58f61e9d8024ee11bd78c12c8916891d4077affected · git
    • 7aecdd47910c51707696e8b0e045b9f88bd4230f and later · before cd4b07507794f7ad1a74e12eca75121d98187e66affected · git
    • 456d8aa37d0f56fc9e985e812496e861dcd6f2f2 and later · before 8b930ddc2044e36866c41423e89889e0258695a3affected · git
    • 456d8aa37d0f56fc9e985e812496e861dcd6f2f2 and later · before f556b6ba0ac5f8353287ce6ed761228f0b4fafb7affected · git
    • 456d8aa37d0f56fc9e985e812496e861dcd6f2f2 and later · before ba4cdc14c0d4df00d3e99bff7fe545303db98183affected · git
    • 456d8aa37d0f56fc9e985e812496e861dcd6f2f2 and later · before 4d96930239981f312821a4065db8cc0f8240a173affected · git
    • 456d8aa37d0f56fc9e985e812496e861dcd6f2f2 and later · before cbf937dcadfd571a434f8074d057b32cd14fbea5affected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.135-16.1.135-1
Debian:13linuxbefore 6.12.25-16.12.25-1
SUSE:Linux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7-RT_Update_1before 1-150700.1.3.11-150700.1.3.1
SUSE:Linux Micro 6.0kernel-defaultbefore 6.4.0-29.16.4.0-29.1
SUSE:Linux Micro 6.0kernel-default-basebefore 6.4.0-29.1.21.76.4.0-29.1.21.7
SUSE:Linux Micro 6.0kernel-kvmsmallbefore 6.4.0-29.16.4.0-29.1
SUSE:Linux Micro 6.0kernel-livepatch-MICRO-6-0_Update_7before 1-1.21-1.2
SUSE:Linux Micro 6.0kernel-livepatch-MICRO-6-0-RT_Update_8before 1-1.21-1.2
SUSE:Linux Micro 6.0kernel-rtbefore 6.4.0-31.16.4.0-31.1
SUSE:Linux Micro 6.0kernel-sourcebefore 6.4.0-29.16.4.0-29.1
SUSE:Linux Micro 6.0kernel-source-rtbefore 6.4.0-31.16.4.0-31.1
SUSE:Real Time Module 15 SP7kernel-rtbefore 6.4.0-150700.7.3.16.4.0-150700.7.3.1
SUSE:Real Time Module 15 SP7kernel-rt_debugbefore 6.4.0-150700.7.3.16.4.0-150700.7.3.1
SUSE:Real Time Module 15 SP7kernel-source-rtbefore 6.4.0-150700.7.3.16.4.0-150700.7.3.1
SUSE:Real Time Module 15 SP7kernel-syms-rtbefore 6.4.0-150700.7.3.16.4.0-150700.7.3.1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-23130Apr 16, 2025 · f2fs: fix to avoid panic once fallocation fails for pinfile
    22Monitor
  • ← EarlierCVE-2025-23134Apr 16, 2025 · ALSA: timer: Don't take register_mutex with copy_from/to_user()
    22Monitor
  • Later →CVE-2024-58096Apr 16, 2025 · wifi: ath11k: add srng->lock for ath11k_hal_srng_* in monitor mode
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0a0f9aecf66b98959aab7fb5764b4b3e522f4f5bVendor (CNA)
Linux Linux4d96930239981f312821a4065db8cc0f8240a173Vendor (CNA)
Linux Linux5.10.236Vendor (CNA)
Linux Linux5.15.180Vendor (CNA)
Linux Linux5.4.292Vendor (CNA)
Linux Linux6.1.134Vendor (CNA)
Linux Linux6.4Vendor (CNA)
Linux Linux6.5Vendor (CNA)
Linux Linux62db339ecc3d58d8fd83a9e4d80061cd943bb6e2Vendor (CNA)
Linux Linux8b930ddc2044e36866c41423e89889e0258695a3Vendor (CNA)
Linux Linuxba4cdc14c0d4df00d3e99bff7fe545303db98183Vendor (CNA)
Linux Linuxcbf937dcadfd571a434f8074d057b32cd14fbea5Vendor (CNA)
Linux Linuxcd4b07507794f7ad1a74e12eca75121d98187e66Vendor (CNA)
Linux Linuxe5cd58f61e9d8024ee11bd78c12c8916891d4077Vendor (CNA)
Linux Linuxf556b6ba0ac5f8353287ce6ed761228f0b4fafb7Vendor (CNA)
azl3 kernel 6.6.92.2-1 on Azure Linux 3.0CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.135-1 · Debian:12Package registry (OSV)
suse:kernel-default6.4.0-29.1 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-default-base6.4.0-29.1.21.7 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-kvmsmall6.4.0-29.1 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0_Update_71-1.2 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0-RT_Update_81-1.2 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-SLE15-SP7-RT_Update_11-150700.1.3.1 · SUSE:Linux Enterprise Live Patching 15 SP7Package registry (OSV)
suse:kernel-rt6.4.0-150700.7.3.1 · SUSE:Real Time Module 15 SP7Package registry (OSV)
suse:kernel-rt_debug6.4.0-150700.7.3.1 · SUSE:Real Time Module 15 SP7Package registry (OSV)
suse:kernel-source6.4.0-29.1 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-source-rt6.4.0-150700.7.3.1 · SUSE:Real Time Module 15 SP7Package registry (OSV)
suse:kernel-syms-rt6.4.0-150700.7.3.1 · SUSE:Real Time Module 15 SP7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records