CVE-2026-98020

CVE CVE-2026-98020EUVD EUVD-2026-86673Published 2026-09-25T10:23:40.000Z

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux patch: 7.2.7; e96094c1d11cce4deb5da3c0500d49041ab845b8 <09f831bfe39de5b8026fefb3d106b5cc93272170; f6ec6ac9432941ec85a2221c91b1ecfc85680d89; 6.8; e96094c1d11cce4deb5da3c0500d49041ab845b8 <2cc697565fd19b5ba2d100cdd4a20dd6d263abc2; 6.7.4 <6.8; 6.6.16 <6.7; e96094c1d11cce4deb5da3c0500d49041ab845b8 <7980325b2f71e3f65c1323c39792e2455da6fab6; patch: 6.18.53; patch: 0; patch: 6.12.111; patch: 7.3-rc3; e96094c1d11cce4deb5da3c0500d49041ab845b8 <fa31bd14c5042c6315bb2182c963f03ca6e79ca4; 692488941283d72362274620b9abd28109fc459f

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.