CVE-2026-90421: PCI: Fix UAF when probe runs concurrent to dyn ID removal
Noroxi assessment
Priority: Monitor (action score 0/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.20% (FIRST EPSS).
- Fixed version: Linux Linux 2cbcb0819c6367e1d5b0792a960594cc19576e23, 3ffc4c9690c33ee28cdb3d0182b12f9c623e3acc, 42a5661ff7e4c7d3c5025d0f8e5079fb5479ea49.
Low priority for now. Upgrade to Linux Linux 2cbcb0819c6367e1d5b0792a960594cc19576e23, 3ffc4c9690c33ee28cdb3d0182b12f9c623e3acc, 42a5661ff7e4c7d3c5025d0f8e5079fb5479ea49 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: Fix UAF when probe runs concurrent to dyn ID removal Dynamic IDs are only guaranteed to be valid when dynids.lock is held, as remove_id_store() can free the node. Thus, make a copy in pci_match_device(). Also, clarify that the id parameter is only valid during probe.
- Published
- Sep 17, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
—
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
- 2.6.30affected
- 0994375e9614f78657031e04e30019b9cdb62795 and later · before 74133e74619d108eeaaa787d78906314d7a7b077affected · git
- 0994375e9614f78657031e04e30019b9cdb62795 and later · before d867db0a2602919510f346bc555f7b3093f6b6ccaffected · git
- 0994375e9614f78657031e04e30019b9cdb62795 and later · before 2cbcb0819c6367e1d5b0792a960594cc19576e23affected · git
- 0994375e9614f78657031e04e30019b9cdb62795 and later · before c36816feff47f676dcc51919777d483f4146c1eeaffected · git
- 0994375e9614f78657031e04e30019b9cdb62795 and later · before 42a5661ff7e4c7d3c5025d0f8e5079fb5479ea49affected · git
- 0994375e9614f78657031e04e30019b9cdb62795 and later · before 3ffc4c9690c33ee28cdb3d0182b12f9c623e3accaffected · git
- before 2.6.30not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*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.192-1 | 6.1.192-1 |
| Debian:12 | linux-6.12 | before 6.12.115-2~deb12u1 | 6.12.115-2~deb12u1 |
| Debian:13 | linux | before 6.12.115-2 | 6.12.115-2 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-90419Sep 17, 2026 · nilfs2: prevent out-of-bounds read in super root block parsing28Monitor
- ← EarlierCVE-2026-90420Sep 17, 2026 · nilfs2: fix infinite loop in nilfs_clean_segments()0Monitor
- Later →CVE-2026-90422Sep 17, 2026 · clk: mediatek: pllfh: Fix IO remapping leak in register_pllfhs error path0Monitor
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 | 2cbcb0819c6367e1d5b0792a960594cc19576e23 | Vendor (CNA) |
| Linux Linux | 3ffc4c9690c33ee28cdb3d0182b12f9c623e3acc | Vendor (CNA) |
| Linux Linux | 42a5661ff7e4c7d3c5025d0f8e5079fb5479ea49 | Vendor (CNA) |
| Linux Linux | 74133e74619d108eeaaa787d78906314d7a7b077 | Vendor (CNA) |
| Linux Linux | c36816feff47f676dcc51919777d483f4146c1ee | Vendor (CNA) |
| Linux Linux | d867db0a2602919510f346bc555f7b3093f6b6cc | Vendor (CNA) |
| debian:linux | 6.1.192-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.6-1 · Debian:14 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.115-2~deb12u1 · 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/3ffc4c9690c33ee28cdb3d0182b12f9c623e3acc
- git.kernel.org/stable/c/42a5661ff7e4c7d3c5025d0f8e5079fb5479ea49
- git.kernel.org/stable/c/74133e74619d108eeaaa787d78906314d7a7b077
- git.kernel.org/stable/c/c36816feff47f676dcc51919777d483f4146c1ee
- git.kernel.org/stable/c/d867db0a2602919510f346bc555f7b3093f6b6cc
Vendor advisories and official records. Exploit/PoC links are deliberately left out.