CVE-2026-98020pds_core: fix cmd_regs access racing BAR unmap on reset
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: pds_core: fix cmd_regs access racing BAR unmap on reset pdsc_reset_prepare() and pdsc_reset_done()'s pdsc_map_bars() error path clear/iounmap cmd_regs without devcmd_lock, and pdsc_legacy_firmware_update()'s download loop derefs cmd_regs after dropping and retaking the lock without re-checking. An FLR concurrent with a devlink flash can unmap cmd_regs under an in-flight devcmd, causing a NULL deref or a write to unmapped MMIO. Take devcmd_lock across the BAR unmap/remap, and re-check cmd_regs in the download loop. Only the PF maps cmd_regs and runs devcmd, so skip the unmap on a VF, as pdsc_remove() and pdsc_reset_done() already do. A reset that completes entirely within the unlocked window is not a correctness problem for the image: the device clears its update session, so a resumed download is rejected, and it verifies the staged image before writing a flash slot, reporting PDS_RC_BAD_FW rather than activating it. pdsc_unmap_bars() also clears info_regs, intr_status and intr_ctrl. The interrupt and start/stop readers of those are quiesced before the unmap by pdsc_fw_down(), which frees the interrupts and tears down the queues. The debugfs readers are not, since those files outlive a reset; that is pre-existing and out of scope here.
Timeline
ID reserved
By Linux
Published
- 24 days later
· 24 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected f6ec6ac9432941ec85a2221c91b1ecfc85680d89 – < 0bf9f3bae3c4b1eadb7a2bf63350333db7dac0d9
- affected e96094c1d11cce4deb5da3c0500d49041ab845b8 – < 2cc697565fd19b5ba2d100cdd4a20dd6d263abc2
- affected e96094c1d11cce4deb5da3c0500d49041ab845b8 – < fa31bd14c5042c6315bb2182c963f03ca6e79ca4
- affected e96094c1d11cce4deb5da3c0500d49041ab845b8 – < 09f831bfe39de5b8026fefb3d106b5cc93272170
- affected e96094c1d11cce4deb5da3c0500d49041ab845b8 – < 7980325b2f71e3f65c1323c39792e2455da6fab6
- affected 692488941283d72362274620b9abd28109fc459f
- affected 6.6.16 – < 6.6.158
- affected 6.7.4 – < 6.8
- affected 6.8
- unaffected < 6.8
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.111 – ≤ 6.12.*
- unaffected 6.18.53 – ≤ 6.18.*
- unaffected 7.2.7 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References5
- https://git.kernel.org/stable/c/0bf9f3bae3c4b1eadb7a2bf63350333db7dac0d9 (opens in a new tab)
- https://git.kernel.org/stable/c/2cc697565fd19b5ba2d100cdd4a20dd6d263abc2 (opens in a new tab)
- https://git.kernel.org/stable/c/fa31bd14c5042c6315bb2182c963f03ca6e79ca4 (opens in a new tab)
- https://git.kernel.org/stable/c/09f831bfe39de5b8026fefb3d106b5cc93272170 (opens in a new tab)
- https://git.kernel.org/stable/c/7980325b2f71e3f65c1323c39792e2455da6fab6 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-86673 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98020)Record last updated .