Quick answers
- Is CVE-2026-98020 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-98020 being exploited in the wild.
- How severe is CVE-2026-98020?
- Informational severity, published 25 September 2026.
- Which products and versions are affected?
- Unknown Linux kernel Affected versions prior to fix commit 7980325b2f71e3f65c1323c39792e2455da6fab6 in pds_core driver.
- Is there a fix for CVE-2026-98020?
- A patch was published on 2026-09-21. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-98020 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-98020?
- Check whether you run Unknown Linux kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A race condition exists between pdsc_reset_prepare() and pdsc_firmware_update() in the pds_core driver. The reset path unmaps BAR registers (cmd_regs) without holding the devcmd_lock, while the firmware download loop can release and re-acquire the lock without re-checking if cmd_regs remains mapped, allowing an FLR (Function Level Reset) to unmap cmd_regs during active devcmd operations. The fix adds proper locking around BAR unmap/remap operations and adds cmd_regs validity checks after lock re-acquisition in the firmware update loop.
Affected products
- <UNKNOWN> Linux kernel Affected versions prior to fix commit 7980325b2f71e3f65c1323c39792e2455da6fab6 in pds_core driver
Timeline
- 2026-09-25: disclosed
- 2026-09-21: patched