Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 37/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
  • Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 08ff33dce6f91510bb296a753a232db0ca3fd3d8, 1cf5c6a80adc31456f3e93b2922a2446fd63e2c4, 4ec87796fadf5a631ee6513c258c0e3d9ca62f79; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.

Low priority for now. Upgrade to Linux Linux 08ff33dce6f91510bb296a753a232db0ca3fd3d8, 1cf5c6a80adc31456f3e93b2922a2446fd63e2c4, 4ec87796fadf5a631ee6513c258c0e3d9ca62f79; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

CriticalCVSS 9.3 · v3.1—No exploit Fix available
Published
Aug 15, 2026
Updated
Oct 30, 2026
EPSS
0.1% · 9th percentile
CWE
—

Report tools

JSON

Action score

37

Monitor

Low priority for now.

CVSS
37 / 40 · 9.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
9.3
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-72329

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.10affected
    • ca6139ffc67ee6ef0459f81e37894ed411083855 and later · before 4ec87796fadf5a631ee6513c258c0e3d9ca62f79affected · git
    • ca6139ffc67ee6ef0459f81e37894ed411083855 and later · before e3b20de8d7c06c8f1a0ded1e52be9d282609c3daaffected · git
    • ca6139ffc67ee6ef0459f81e37894ed411083855 and later · before 1cf5c6a80adc31456f3e93b2922a2446fd63e2c4affected · git
    • ca6139ffc67ee6ef0459f81e37894ed411083855 and later · before 08ff33dce6f91510bb296a753a232db0ca3fd3d8affected · git
    • ca6139ffc67ee6ef0459f81e37894ed411083855 and later · before 81acef3a247fd523513a2e9f71de1c167bc0f882affected · git
    • ca6139ffc67ee6ef0459f81e37894ed411083855 and later · before 5c0e3ba4f500fd4314ceb42f07f16bc445156431affected · git
    • before 4.10not affected · semver
    • 6.1.191 and later · up to and including 6.1.*not affected · semver
    • 6.6.160 and later · up to and including 6.6.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.170.1.el8_104.18.0-553.170.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.170.1.rt7.511.el8_104.18.0-553.170.1.rt7.511.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.170.1.rt7.511.el8_104.18.0-553.170.1.rt7.511.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.170.1.rt7.511.el8_104.18.0-553.170.1.rt7.511.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.170.1.rt7.511.el8_104.18.0-553.170.1.rt7.511.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.170.1.rt7.511.el8_104.18.0-553.170.1.rt7.511.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.170.1.rt7.511.el8_104.18.0-553.170.1.rt7.511.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.170.1.rt7.511.el8_104.18.0-553.170.1.rt7.511.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.170.1.rt7.511.el8_104.18.0-553.170.1.rt7.511.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.170.1.rt7.511.el8_104.18.0-553.170.1.rt7.511.el8_10

+65

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-72325Aug 15, 2026 · perf/x86/amd/core: Avoid enabling BRS from the SVM reload path
    0Monitor
  • ← EarlierCVE-2026-72326Aug 15, 2026 · net/sched: cake: reject overhead values that underflow length
    0Monitor
  • Later →CVE-2026-72330Aug 15, 2026 · net/tls: Consume empty data records in tls_sw_read_sock()
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux08ff33dce6f91510bb296a753a232db0ca3fd3d8Vendor (CNA)
Linux Linux1cf5c6a80adc31456f3e93b2922a2446fd63e2c4Vendor (CNA)
Linux Linux4ec87796fadf5a631ee6513c258c0e3d9ca62f79Vendor (CNA)
Linux Linux5c0e3ba4f500fd4314ceb42f07f16bc445156431Vendor (CNA)
Linux Linux81acef3a247fd523513a2e9f71de1c167bc0f882Vendor (CNA)
Linux Linuxe3b20de8d7c06c8f1a0ded1e52be9d282609c3daVendor (CNA)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 kernel 6.6.159.1-1 on Azure Linux 3.06.6.161.1-1 · Release NotesMicrosoft (MSRC)
almalinux:bpftool4.18.0-553.170.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.170.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt4.18.0-553.170.1.rt7.511.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-core4.18.0-553.170.1.rt7.511.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug4.18.0-553.170.1.rt7.511.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-core4.18.0-553.170.1.rt7.511.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-devel4.18.0-553.170.1.rt7.511.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules4.18.0-553.170.1.rt7.511.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules-extra4.18.0-553.170.1.rt7.511.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-devel4.18.0-553.170.1.rt7.511.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules4.18.0-553.170.1.rt7.511.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules-extra4.18.0-553.170.1.rt7.511.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.12.115-2 · Debian:13Package registry (OSV)
debian:linux7.1.5-1 · Debian:14Package registry (OSV)
red hat:kernel-rt0:4.18.0-553.170.1.rt7.511.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-core0:4.18.0-553.170.1.rt7.511.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug0:4.18.0-553.170.1.rt7.511.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-core0:4.18.0-553.170.1.rt7.511.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-debuginfo0:4.18.0-553.170.1.rt7.511.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-devel0:4.18.0-553.170.1.rt7.511.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-kvm0:4.18.0-553.170.1.rt7.511.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)

+7

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records