NVD / CVE Program· CNA Linux

CVE-2024-42302: PCI/DPC: Fix use-after-free on concurrent DPC and hot-removal

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.22% (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 11a1f4bc47362700fcbde717292158873fb847ed, 2c111413f38ca5cf87557cab89f6d82b0e3433e7, 2cc8973bdc4d6c928ebe38b88090a2cdfe81f42f; Azure Linux 3.0 ARM 6.6.47.1-1; Azure Linux 3.0 x64 6.6.47.1-1.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 11a1f4bc47362700fcbde717292158873fb847ed, 2c111413f38ca5cf87557cab89f6d82b0e3433e7, 2cc8973bdc4d6c928ebe38b88090a2cdfe81f42f; Azure Linux 3.0 ARM 6.6.47.1-1; Azure Linux 3.0 x64 6.6.47.1-1 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/DPC: Fix use-after-free on concurrent DPC and hot-removal Keith reports a use-after-free when a DPC event occurs concurrently to hot-removal of the same portion of the hierarchy: The dpc_handler() awaits readiness of the secondary bus below the Downstream Port where the DPC event occurred. To do so, it polls the config space of the first child device on the secondary bus. If that child device is concurrently removed, accesses to its struct pci_dev cause the kernel to oops. That's because pci_bridge_wait_for_secondary_bus() neglects to hold a reference on the child device. Before v6.3, the function was only called on resume from system sleep or on runtime resume. Holding a reference wasn't necessary back then because the pciehp IRQ thread could never run concurrently. (On resume from system sleep, IRQs are not enabled until after the resume_noirq phase. And runtime resume is always awaited before a PCI device is removed.) However starting with v6.3, pci_bridge_wait_for_secondary_bus() is also called on a DPC event. Commit 53b54ad074de ("PCI/DPC: Await readiness of secondary bus after reset"), which introduced that, failed to appreciate that pci_bridge_wait_for_secondary_bus() now needs to hold a reference on the child device because dpc_handler() and pciehp may indeed run concurrently. The commit was backported to v5.10+ stable kernels, so that's the oldest one affected. Add the missing reference acquisition. Abridged stack trace: BUG: unable to handle page fault for address: 00000000091400c0 CPU: 15 PID: 2464 Comm: irq/53-pcie-dpc 6.9.0 RIP: pci_bus_read_config_dword+0x17/0x50 pci_dev_wait() pci_bridge_wait_for_secondary_bus() dpc_reset_link() pcie_do_recovery() dpc_handler()

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

BDU:2024-10086

Published: Aug 17, 2024
Updated: Oct 15, 2026
EPSS: 0.2% · 13th 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.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.

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
debian	debian linux	cpe:2.3:o:debian:debian_linux

Affected versions

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

debian debian linux11.0
linux linux kernel5.10.176 and later · before 5.10.224
linux linux kernel5.15.104 and later · before 5.15.165
linux linux kernel6.1.16 and later · before 6.1.103
linux linux kernel6.2.3 and later · before 6.6.44
linux linux kernel6.7 and later · before 6.10.3

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
- 0081032082b5b45ca902b3c3d6986cb5cca69ff2, 6.3affected
- d0292124bb5787a2f1ab1316509e801ca89c10fb and later · before c52f9e1a9eb40f13993142c331a6cfd334d4b91daffected · git
- ffe2318405e605f1b3985ce188eff69e6d1d1baa and later · before 2c111413f38ca5cf87557cab89f6d82b0e3433e7affected · git
- 189f856e76f5463f59efb5fc18dcc1692d04c41a and later · before f63df70b439bb8331358a306541893bf415bf1daaffected · git
- 53b54ad074de1896f8b021615f65b27f557ce874 and later · before 2cc8973bdc4d6c928ebe38b88090a2cdfe81f42faffected · git
- 53b54ad074de1896f8b021615f65b27f557ce874 and later · before b16f3ea1db47a6766a9f1169244cf1fc287a7c62affected · git
- 53b54ad074de1896f8b021615f65b27f557ce874 and later · before 11a1f4bc47362700fcbde717292158873fb847edaffected · git
- 5.10.176 and later · before 5.10.224affected · semver
- 5.15.104 and later · before 5.15.165affected · semver
- 6.1.16 and later · before 6.1.103affected · 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.106-1	6.1.106-1
Debian:13	linux	before 6.10.3-1	6.10.3-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-2024-42283Aug 17, 2024 · net: nexthop: Initialize all fields in dumped nexthops
22Monitor
← EarlierCVE-2024-42292Aug 17, 2024 · kobject_uevent: Fix OOB access within zap_modalias_env()
28Monitor
Later →CVE-2024-42304Aug 17, 2024 · ext4: make sure the first directory block is not a hole
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 / package	Fixed version	Source
Linux Linux	11a1f4bc47362700fcbde717292158873fb847ed	Vendor (CNA)
Linux Linux	2c111413f38ca5cf87557cab89f6d82b0e3433e7	Vendor (CNA)
Linux Linux	2cc8973bdc4d6c928ebe38b88090a2cdfe81f42f	Vendor (CNA)
Linux Linux	5.10.224	Vendor (CNA)
Linux Linux	5.15.165	Vendor (CNA)
Linux Linux	6.1.103	Vendor (CNA)
Linux Linux	6.3	Vendor (CNA)
Linux Linux	b16f3ea1db47a6766a9f1169244cf1fc287a7c62	Vendor (CNA)
Linux Linux	c52f9e1a9eb40f13993142c331a6cfd334d4b91d	Vendor (CNA)
Linux Linux	f63df70b439bb8331358a306541893bf415bf1da	Vendor (CNA)
Azure Linux 3.0 ARM	6.6.47.1-1 · kernel	Microsoft (MSRC)
Azure Linux 3.0 x64	6.6.47.1-1 · kernel	Microsoft (MSRC)
CBL Mariner 2.0 ARM	5.15.167.1-1 · kernel	Microsoft (MSRC)
CBL Mariner 2.0 x64	5.15.167.1-1 · kernel	Microsoft (MSRC)
debian:linux	6.1.106-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.

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.

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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-24-1290 · Aug 19, 2024(Linux Kernel Güvenlik Bildirimi)

All national notices →

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/11a1f4bc47362700fcbde717292158873fb847ed

Show all references (8 more)

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

All records