Skip to main content
VulnerabilityPublished Updated

CVE-2026-72329: Linux kernel · net/liquidio: drop cached VF pci_dev LUT

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 9.3 Critical · fixed in e3b20de8d7c06c8f1a0ded1e52be9d282609c3da : patch Linux kernel as a priority.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in e3b20de8d7c06c8f1a0ded1e52be9d282609c3da, 81acef3a247fd523513a2e9f71de1c167bc0f882, 08ff33dce6f91510bb296a753a232db0ca3fd3d8 +2
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ ca6139ffc67ee6ef0459f81e37894ed411083855, < e3b20de8d7c06c8f1a0ded1e52be9d282609c3da
Fixed in
  • e3b20de8d7c06c8f1a0ded1e52be9d282609c3da
LinuxLinuxAffected
  • ≥ ca6139ffc67ee6ef0459f81e37894ed411083855, < 81acef3a247fd523513a2e9f71de1c167bc0f882
Fixed in
  • 81acef3a247fd523513a2e9f71de1c167bc0f882
LinuxLinuxAffected
  • ≥ ca6139ffc67ee6ef0459f81e37894ed411083855, < 08ff33dce6f91510bb296a753a232db0ca3fd3d8
Fixed in
  • 08ff33dce6f91510bb296a753a232db0ca3fd3d8
LinuxLinuxAffected
  • ≥ ca6139ffc67ee6ef0459f81e37894ed411083855, < 5c0e3ba4f500fd4314ceb42f07f16bc445156431
Fixed in
  • 5c0e3ba4f500fd4314ceb42f07f16bc445156431
LinuxLinuxAffected
  • ≥ ca6139ffc67ee6ef0459f81e37894ed411083855, < 1cf5c6a80adc31456f3e93b2922a2446fd63e2c4
Fixed in
  • 1cf5c6a80adc31456f3e93b2922a2446fd63e2c4
LinuxLinuxAffected
  • =4.10
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: net/liquidio: drop cached VF pci_dev LUT The PF SR-IOV enable path caches VF pci_dev pointers in dpiring_to_vfpcidev_lut[] by iterating with pci_get_device(). Those entries do not own a reference, because the iterator drops the previous device reference on each step. The cached pointer is then dereferenced later when handling OCTEON_VF_FLR_REQUEST. Replace the cached VF mapping with runtime lookup on the mailbox DPI ring: derive the VF index from q_no, resolve the VF via exported PCI IOV helpers, validate it with the PF pointer and VF ID, then issue pcie_flr() and drop the reference with pci_dev_put(). Remove the unused VF lookup table initialization and cleanup.

References

Community reviews

Loading reviews…