NVD / CVE Program· CNA Linux

CVE-2023-53446: PCI/ASPM: Disable ASPM on MFD function removal to avoid use-after-free

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.15% (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 4203722d51afe3d239e03f15cc73efdf023a7103, 456d8aa37d0f56fc9e985e812496e861dcd6f2f2, 666e7f9d60cee23077ea3e6331f6f8a19f7ea03f.

Low priority for now. Upgrade to Linux Linux 4203722d51afe3d239e03f15cc73efdf023a7103, 456d8aa37d0f56fc9e985e812496e861dcd6f2f2, 666e7f9d60cee23077ea3e6331f6f8a19f7ea03f 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: Disable ASPM on MFD function removal to avoid use-after-free Struct pcie_link_state->downstream is a pointer to the pci_dev of function 0. Previously we retained that pointer when removing function 0, and subsequent ASPM policy changes dereferenced it, resulting in a use-after-free warning from KASAN, e.g.: # echo 1 > /sys/bus/pci/devices/0000:03:00.0/remove # echo powersave > /sys/module/pcie_aspm/parameters/policy BUG: KASAN: slab-use-after-free in pcie_config_aspm_link+0x42d/0x500 Call Trace: kasan_report+0xae/0xe0 pcie_config_aspm_link+0x42d/0x500 pcie_aspm_set_policy+0x8e/0x1a0 param_attr_store+0x162/0x2c0 module_attr_store+0x3e/0x80 PCIe spec r6.0, sec 7.5.3.7, recommends that software program the same ASPM Control value in all functions of multi-function devices. Disable ASPM and free the pcie_link_state when any child function is removed so we can discard the dangling pcie_link_state->downstream pointer and maintain the same ASPM Control configuration for all functions. [bhelgaas: commit log and comment]

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

BDU:2025-12977

Published: Sep 18, 2025
Updated: Jun 17, 2026
EPSS: 0.1% · 4th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

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

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

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.

Running WordPress? Scan your site free with WP Lens

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.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

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

linux linux kernel4.11 and later · before 5.4.251
linux linux kernel5.5 and later · before 5.10.188
linux linux kernel5.11 and later · before 5.15.121
linux linux kernel5.16 and later · before 6.1.39
linux linux kernel6.2 and later · before 6.3.13
linux linux kernel6.4 and later · before 6.4.4

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
- 4.11affected
- b5a0a9b59c8185aebcd9a717e2e6258b58c72c06 and later · before 666e7f9d60cee23077ea3e6331f6f8a19f7ea03faffected · git
- b5a0a9b59c8185aebcd9a717e2e6258b58c72c06 and later · before 7badf4d6f49a358a01ab072bbff88d3ee886c33baffected · git
- b5a0a9b59c8185aebcd9a717e2e6258b58c72c06 and later · before 9856c0de49052174ab474113f4ba40c02aaee086affected · git
- b5a0a9b59c8185aebcd9a717e2e6258b58c72c06 and later · before 7aecdd47910c51707696e8b0e045b9f88bd4230faffected · git
- b5a0a9b59c8185aebcd9a717e2e6258b58c72c06 and later · before d51d2eeae4ce54d542909c4d9d07bf371a78592caffected · git
- b5a0a9b59c8185aebcd9a717e2e6258b58c72c06 and later · before 4203722d51afe3d239e03f15cc73efdf023a7103affected · git
- b5a0a9b59c8185aebcd9a717e2e6258b58c72c06 and later · before 456d8aa37d0f56fc9e985e812496e861dcd6f2f2affected · git
- before 4.11not affected · semver
- 5.4.251 and later · up to and including 5.4.*not affected · semver

Package-level exposure

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

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.52-1	6.1.52-1
Debian:13	linux	before 6.4.4-1	6.4.4-1

Same product

linux: all records

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-2023-53444Sep 18, 2025 · drm/ttm: fix bulk_move corruption when adding a entry
22Monitor
← EarlierCVE-2023-53445Sep 18, 2025 · net: qrtr: Fix a refcount bug in qrtr_recvmsg()
22Monitor
Later →CVE-2023-53447Sep 18, 2025 · f2fs: don't reset unchangable mount option in f2fs_remount()
18Monitor

Remediation

Which version to upgrade to

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

Product / package	Fixed version	Source
Linux Linux	4203722d51afe3d239e03f15cc73efdf023a7103	Vendor (CNA)
Linux Linux	456d8aa37d0f56fc9e985e812496e861dcd6f2f2	Vendor (CNA)
Linux Linux	666e7f9d60cee23077ea3e6331f6f8a19f7ea03f	Vendor (CNA)
Linux Linux	7aecdd47910c51707696e8b0e045b9f88bd4230f	Vendor (CNA)
Linux Linux	7badf4d6f49a358a01ab072bbff88d3ee886c33b	Vendor (CNA)
Linux Linux	9856c0de49052174ab474113f4ba40c02aaee086	Vendor (CNA)
Linux Linux	d51d2eeae4ce54d542909c4d9d07bf371a78592c	Vendor (CNA)
debian:linux	6.1.52-1 · Debian:12	Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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.

Credits

All researchers

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.

The bug in code

The whole CWE-416 class

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

Vulnerable

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

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&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

Fix✗ → ✓Sep 28, 2026, 10:09 PM UTC

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

References

git.kernel.org/stable/c/4203722d51afe3d239e03f15cc73efdf023a7103

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records