CVE-2026-80917: PCI: host-generic: Fix NULL pointer dereference on 32-bit CAM systems
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.16% (FIRST EPSS).
- Fixed version: Linux Linux 008cb88edb41f3c7c8e0ed763ff9f26719830984, 0916948026f623844acd08888f7cbedbf1c48d6b, 0c55707bd5d0d7670704cfd0dda933809b052f67; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
Low priority for now. Upgrade to Linux Linux 008cb88edb41f3c7c8e0ed763ff9f26719830984, 0916948026f623844acd08888f7cbedbf1c48d6b, 0c55707bd5d0d7670704cfd0dda933809b052f67; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.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: host-generic: Fix NULL pointer dereference on 32-bit CAM systems On 32-bit systems the config space is too large to ioremap in one go, so pci_ecam_create() maps each bus segment separately and relies on the ->add_bus callback (pci_ecam_add_bus) to populate the per-bus mapping in cfg->winp[]. pci_ecam_map_bus() then uses that mapping as the base for every config access. The generic ECAM ops (pci_generic_ecam_ops) already provide the ->add_bus and ->remove_bus callbacks, but the CAM (legacy) ops in pci-host-generic.c do not. As a result, on a 32-bit host using "pci-host-cam-generic" the per-bus mapping is never set up and the first config read dereferences a NULL base, crashing during bus enumeration: Unable to handle kernel NULL pointer dereference at virtual address 00000800 Oops [#1] CPU: 0 PID: 1 Comm: swapper Not tainted 6.9.7+ #43 Hardware name: Digilent Nexys-Video-A7 RV32 (DT) epc : pci_generic_config_read+0x40/0xb0 ra : pci_generic_config_read+0x2c/0xb0 [<c038db9c>] pci_generic_config_read+0x40/0xb0 [<c038da04>] pci_bus_read_config_dword+0x50/0xb0 [<c0391e94>] pci_bus_generic_read_dev_vendor_id+0x3c/0x1ec [<c039245c>] pci_scan_single_device+0xa4/0x11c [<c0392570>] pci_scan_slot+0x9c/0x23c [<c039388c>] pci_scan_child_bus_extend+0x58/0x2f4 [<c0393db0>] pci_scan_root_bus_bridge+0x64/0xe8 [<c0393e54>] pci_host_probe+0x20/0xc8 [<c03bc6f4>] pci_host_common_probe+0x144/0x1e4 Fix this by giving the CAM ops the same ->add_bus/->remove_bus callbacks. Since pci_ecam_add_bus() and pci_ecam_remove_bus() are static to ecam.c, move the CAM ops definition there as pci_generic_cam_ops (mirroring pci_generic_ecam_ops) and export it for pci-host-generic.c to reference. [mani: removed timestamp from log]
- Published
- Sep 9, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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
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 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
- 0b5877a1aeacdbf32b3bea91326592004ec7806f, a037ebbe72a4f98495b193112e2b2000e5e09eb5, 5.14affected
- 8fe55ef23387ce3c7488375b1fd539420d7654bb and later · before 5e52eb0290f66ba0732956dcb1e365b5ca3c5108affected · git
- 8fe55ef23387ce3c7488375b1fd539420d7654bb and later · before baf9b0383ff770fdff123d3a832f3a99641d96ddaffected · git
- 8fe55ef23387ce3c7488375b1fd539420d7654bb and later · before 8d08713ec83a18526d1ed1fd5f0d2b901d103a10affected · git
- 8fe55ef23387ce3c7488375b1fd539420d7654bb and later · before 74456843f18ba7f3045974d7e8b88ab993152b8caffected · git
- 8fe55ef23387ce3c7488375b1fd539420d7654bb and later · before 0c55707bd5d0d7670704cfd0dda933809b052f67affected · git
- 8fe55ef23387ce3c7488375b1fd539420d7654bb and later · before a199293f3038db8d31d47aa60f1e18272cd82354affected · git
- 8fe55ef23387ce3c7488375b1fd539420d7654bb and later · before 0916948026f623844acd08888f7cbedbf1c48d6baffected · git
- 8fe55ef23387ce3c7488375b1fd539420d7654bb and later · before 008cb88edb41f3c7c8e0ed763ff9f26719830984affected · git
- 5.12.19 and later · before 5.13affected · 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.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.107-1 | 6.12.107-1 |
| Debian:14 | linux | before 7.1.12-1 | 7.1.12-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-80914Sep 9, 2026 · Bluetooth: ISO: fix use-after-free of listener socket in iso_conn_ready35Monitor
- ← EarlierCVE-2026-80916Sep 9, 2026 · kcov: fix data corruption and race conditions on PREEMPT_RT0Monitor
- Later →CVE-2026-80918Sep 9, 2026 · HID: core: fix number/pointer type confusion on long items0Monitor
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 | 008cb88edb41f3c7c8e0ed763ff9f26719830984 | Vendor (CNA) |
| Linux Linux | 0916948026f623844acd08888f7cbedbf1c48d6b | Vendor (CNA) |
| Linux Linux | 0c55707bd5d0d7670704cfd0dda933809b052f67 | Vendor (CNA) |
| Linux Linux | 5.13 | Vendor (CNA) |
| Linux Linux | 5.14 | Vendor (CNA) |
| Linux Linux | 5e52eb0290f66ba0732956dcb1e365b5ca3c5108 | Vendor (CNA) |
| Linux Linux | 74456843f18ba7f3045974d7e8b88ab993152b8c | Vendor (CNA) |
| Linux Linux | 8d08713ec83a18526d1ed1fd5f0d2b901d103a10 | Vendor (CNA) |
| Linux Linux | a199293f3038db8d31d47aa60f1e18272cd82354 | Vendor (CNA) |
| Linux Linux | baf9b0383ff770fdff123d3a832f3a99641d96dd | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~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).
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 researchersFinders, 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
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/0916948026f623844acd08888f7cbedbf1c48d6b
- git.kernel.org/stable/c/0c55707bd5d0d7670704cfd0dda933809b052f67
- git.kernel.org/stable/c/5e52eb0290f66ba0732956dcb1e365b5ca3c5108
- git.kernel.org/stable/c/74456843f18ba7f3045974d7e8b88ab993152b8c
- git.kernel.org/stable/c/8d08713ec83a18526d1ed1fd5f0d2b901d103a10
- git.kernel.org/stable/c/a199293f3038db8d31d47aa60f1e18272cd82354
- git.kernel.org/stable/c/baf9b0383ff770fdff123d3a832f3a99641d96dd
Vendor advisories and official records. Exploit/PoC links are deliberately left out.