CVE-2026-98020

pds_core: fix cmd_regs access racing BAR unmap on reset

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.

Key facts

Published
25 Sep 2026
Last changed
19 Oct 2026
Assigned by
Linux
EPSS
0.168% likely to be exploited in the next 30 days, higher than 6.115% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • f6ec6ac9432941ec85a2221c91b1ecfc85680d89 up to but excluding 0bf9f3bae3c4b1eadb7a2bf63350333db7dac0d9 (affected)
  • e96094c1d11cce4deb5da3c0500d49041ab845b8 up to but excluding 2cc697565fd19b5ba2d100cdd4a20dd6d263abc2 (affected)
  • e96094c1d11cce4deb5da3c0500d49041ab845b8 up to but excluding fa31bd14c5042c6315bb2182c963f03ca6e79ca4 (affected)
  • e96094c1d11cce4deb5da3c0500d49041ab845b8 up to but excluding 09f831bfe39de5b8026fefb3d106b5cc93272170 (affected)
  • e96094c1d11cce4deb5da3c0500d49041ab845b8 up to but excluding 7980325b2f71e3f65c1323c39792e2455da6fab6 (affected)
  • 692488941283d72362274620b9abd28109fc459f (affected)
  • 6.6.16 up to but excluding 6.6.158 (affected)
  • 6.7.4 up to but excluding 6.8 (affected)
LinuxLinux
  • Default status: affected
  • 6.8 (affected)
  • 0 up to but excluding 6.8 (unaffected)
  • 6.6.158 up to and including 6.6.* (unaffected)
  • 6.12.111 up to and including 6.12.* (unaffected)
  • 6.18.53 up to and including 6.18.* (unaffected)
  • 7.2.7 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 25 Sep 2026 Published

References