[CVE-2026-72329][MODERATE 7.0] net/liquidio: drop cached VF pci_dev LUT [ Upstream

[CVE-2026-72329][MODERATE 7.0] net/liquidio: drop cached VF pci_dev LUT [ Upstream

[AL-KERNEL]

CVE: CVE-2026-72329
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: net/liquidio: drop cached VF pci_dev LUT [ Upstream
Commit: 81acef3a247fd523513a2e9f71de1c167bc0f882
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=81acef3a247fd523513a2e9f71de1c167bc0f882
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72329
Analysis date: Sat, 15 Aug 2026 19:38:26 -0400
ActionableScore: 7
ActionableScore lower bound: 4
Actionable bucket: Strong Important candidate / Actionable Moderate at minimum
Manual review required: YES

Summary:
The liquidio PF driver cached VF pci_dev pointers without owning references, allowing a VF mailbox FLR request to dereference stale PCI device state and potentially crash the host kernel, with worst case concern for UAF style integrity impact across an SR_IOV guest to host boundary.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-72329 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72329

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: MODERATE 7.0
Manual review required: YES

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-72329	MODERATE	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H';*CWE-416;*CWE-672;CWE-825;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:H';BEST CVSS score: '7.8';DESCR 'The liquidio PF driver cached VF pci_dev pointers without owning references and later used those pointers when processing an OCTEON_VF_FLR_REQUEST mailbox command. Because the pci_get_device iterator drops the previous device reference, the cached entries can become dangling pointers and a later pcie_flr call may dereference freed or stale PCI device memory. For the CVSS the PR:L is used because the attacker generally needs control of a VF context or a local process that can drive VF mailbox behavior, but full host administrator privileges are not necessarily required in virtualized SR-IOV deployments. The issue is not directly network reachable and is tied to local PCI SR-IOV device access rather than packet traffic. Impact is at least denial of service via host kernel crash and in worst case may allow confidentiality or integrity impact due to a UAF style memory safety flaw, so it should be reviewed manually.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Strong Important candidate / Actionable Moderate at minimum (with actual score 6)	YES	REMOTE INIT NETWORK HARDWARE KPANIC  KPANIC INCREASED_TO_HIGH_BASED_ON_GUESSCVSS DECREASED_TO_MODERATE7_BASED_ON_FALSEPOSCHECKOFKP	NO	NO	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=7
ActionableScoreLower=4

## 1. ActionableScore

* Conservative score: 4
* Paranoid score: 7
* Final recommended bucket: **Strong Important candidate / Actionable Moderate at minimum**::

## 2. Signal breakdown

Conservative signals:

* Local unprivileged or reduced privileged trigger: +1. A VF or VM context may be able to send the OCTEON_VF_FLR_REQUEST mailbox command without full host root privileges.
* Memory corruption, weak or indirect corruption candidate: +1. The bug is a stale pci_dev pointer dereference, but no controlled reclaim or overwrite primitive is shown.
* Real lifetime corruption: +1. The cached pci_dev entries do not own references and may outlive the referenced object.
* Reliable kernel crash / strong DoS: +1. Dereferencing a stale pci_dev in pcie_flr can plausibly crash the host kernel.
* Rare AND difficult to reach subsystem/configuration: -1. Requires LiquidIO hardware, SR-IOV enabled, and VF mailbox activity.
* Privileged kernel/device-management memory corruption path: +1. The stale pointer is used in PCI SR-IOV / FLR device-management code.

Paranoid additional signals:

* Memory corruption, strong corruption primitive: +2 instead of weak +1. The patch fixes an actual object lifetime bug involving a stale kernel object pointer.
* Confidentiality impact plausible: +1. UAF-style stale object reuse can sometimes expose kernel object state, though not demonstrated here.
* Integrity impact plausible: +1. A stale pci_dev passed to pcie_flr could theoretically act on corrupted or wrong PCI device state.
* Weak LPE concern: +1. Not proven, but the bug crosses a guest/VF-to-host driver boundary and involves stale trusted PCI object state.

## 3. Reachability analysis

The likely trigger is a VF-controlled mailbox request handled by the PF driver, especially OCTEON_VF_FLR_REQUEST. This is not network reachable in the TCP/IP sense and should not receive a remote score. The practical attacker is more likely a local user, VM, or reduced-privilege environment with access to a LiquidIO VF. Full host administrator privileges are not necessarily required in SR-IOV deployments, so PR:L is more appropriate than PR:H for paranoid triage.

The path is not broadly default-enabled. It depends on LiquidIO CN23XX-class hardware, SR-IOV configuration, and VF mailbox handling. Namespaces alone do not make it reachable, but VM assignment or delegated device access can lower the practical privilege boundary.

Call-site confidence: high. The patch includes both the stale cached table construction and the later pcie_flr call site.

## 4. Severity interpretation

This is not an ordinary low-risk cleanup. The core issue is a real lifetime/reference bug where pci_dev pointers were cached without owning references and later dereferenced in a privileged PF driver path. Realistic impact is most clearly host kernel DoS. Privilege escalation is not demonstrated, because the patch does not show attacker-controlled reclaim, arbitrary write, callback control, or type confusion. However, because this is a stale trusted kernel object used across a VF/PF boundary, it is an Actionable Moderate at minimum and a Strong Important candidate under paranoid triage.

## 5. One-sentence report phrase

The liquidio PF driver cached VF pci_dev pointers without owning references, allowing a VF mailbox FLR request to dereference stale PCI device state and potentially crash the host kernel, with worst case concern for UAF style integrity impact across an SR_IOV guest to host boundary.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

This should be manually reviewed because it is a real lifetime bug involving stale pci_dev pointers in a PCI SR-IOV device-management path, and the reachable VF-to-PF boundary makes the practical impact higher than a simple driver-local crash.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: net/liquidio: drop cached VF pci_dev LUT [ Upstream
Commit: 81acef3a247fd523513a2e9f71de1c167bc0f882
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=81acef3a247fd523513a2e9f71de1c167bc0f882

Changed files:
  drivers/net/ethernet/cavium/liquidio/lio_main.c
  drivers/net/ethernet/cavium/liquidio/octeon_device.h
  drivers/net/ethernet/cavium/liquidio/octeon_mailbox.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=81acef3a247fd523513a2e9f71de1c167bc0f882

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-72329 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72329

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:H
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
  The Best / paranoid CVSS score: 7.8

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 4
  Paranoid ActionableScore: 7

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: MODERATE
KPANIC detected for this report: YES
Published priority for this report (same as in Subject): MODERATE 7.0

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).