[CVE-2026-74527][MODERATE 7.0] octeontx2-af: Block VFs from clobbering special CGX PKIND state [ Upstream

[CVE-2026-74527][MODERATE 7.0] octeontx2-af: Block VFs from clobbering special CGX PKIND state [ Upstream

[AL-KERNEL]

CVE: CVE-2026-74527
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: octeontx2-af: Block VFs from clobbering special CGX PKIND state [ Upstream
Commit: d3c6b0f48f126a36955b3fb4154a59d0b3621d97
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d3c6b0f48f126a36955b3fb4154a59d0b3621d97
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74527
Analysis date: Sat, 15 Aug 2026 17:56:19 -0400
ActionableScore: 5
ActionableScore lower bound: 4
Actionable bucket: Actionable Moderate at minimum
Manual review required: YES

Summary:
A VF on octeontx2 can overwrite shared CGX LMAC PKIND and TX parse configuration owned by the PF when HiGig2 or EDSA parsing is active, causing VF/PF isolation breakage and possible traffic disruption or policy misclassification.

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

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

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-74527	MODERATE	CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:H';CWE-284;CWE-862;CWE-693;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:H';BEST CVSS score: '7';DESCR 'A VF on octeontx2 can overwrite shared CGX LMAC PKIND and TX parse configuration that should be controlled by the PF when special parsing modes such as HiGig2 or EDSA are active. This is a VF/PF isolation and authorization issue rather than memory corruption. For the CVSS the PR:L is used because a local actor with access to an assigned VF or guest side VF control can trigger the relevant mailbox and LF allocation paths, while full host administrator privileges are not necessarily required in SR-IOV deployments. The issue is not directly reachable from the external network by ordinary packet traffic. Impact is mainly denial of service or network policy disruption due to corrupted parse configuration, with a paranoid limited confidentiality and integrity impact if the parser state affects traffic separation or classification on a shared LMAC.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 5)	YES	REMOTE LOCK INIT NETWORK HARDWARE LINUS  DECREASED_TO_MODERATEREG_BASED_ON_FALSEPOSCHECKOFKP	YES	NO	checked

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

ActionableScore=5
ActionableScoreLower=4

## 1. ActionableScore

* Conservative score: **4**
* Paranoid score: **5**
* Final recommended bucket: **Actionable Moderate at minimum**::

## 2. Signal breakdown

Conservative signals:

* **Local or guest-side VF trigger: +1**. A VF with access to the relevant mailbox or LF allocation path can influence the shared CGX LMAC PKIND state.
* **Cross-boundary isolation or policy bypass: +1**. The bug lets a VF affect PF-owned shared hardware parser configuration.
* **Integrity impact plausible: +1**. Clobbering HiGig2 or EDSA parse state can alter packet classification or parsing policy.
* **Availability impact realistic: +1**. Incorrect parser state can disrupt PF or shared-LMAC traffic handling.
* **Practical exploit chain strongly implied: +1**. The commit directly describes VF NIX LF allocation resetting LMAC RX PKIND or TX parse config over PF setup.
* **Rare hardware and configuration dependency: -1**. Requires Marvell octeontx2 / CGX LMAC sharing, SR-IOV VF use, and special HiGig2 or EDSA parsing.

Paranoid additional signal:

* **Confidentiality impact plausible: +1**. If parser state affects traffic separation or classification on a shared LMAC, limited traffic exposure or misclassification is defensible, but not proven.

Not awarded:

* **No generic memory corruption**. The patch changes permission checks and hardware register programming, not memory lifetime or bounds handling.
* **No LPE signal**. There is no UAF, arbitrary write, refcount takeover, callback control, or host privilege escalation primitive.
* **No remote reachable signal**. Ordinary external packets do not directly trigger the vulnerable control path.

Call-site confidence: **high**, because the patch includes the relevant callers in `rvu_mbox_handler_nix_lf_alloc()` and `rvu_npc_set_parse_mode()`.

## 3. Reachability analysis

The realistic attacker is a local actor, guest, or delegated administrator with access to an assigned VF and the ability to trigger VF mailbox or NIX LF allocation/configuration paths. This should not be treated as full host-root access in SR-IOV deployments, because the issue crosses the intended VF/PF isolation boundary. Namespaces are less central here than hardware virtualization and VF assignment. The path is not remotely reachable through normal packet traffic. Exploitation also depends on specific hardware and on HiGig2 or EDSA parsing being active on a shared CGX LMAC.

## 4. Severity interpretation

This behaves more like an **actionable Moderate** than an ordinary low-risk driver bug. It is not a memory-corruption or direct privilege-escalation issue, but it allows a VF to clobber PF-owned shared parser state, which is a meaningful isolation and network-policy concern. The conservative score stays below Important because the affected configuration is hardware-specific and no kernel memory corruption primitive is shown. The paranoid score reaches Actionable Moderate because limited confidentiality and integrity impact are plausible in shared-LMAC parser configurations.

## 5. One-sentence report phrase

A VF on octeontx2 can overwrite shared CGX LMAC PKIND and TX parse configuration owned by the PF when HiGig2 or EDSA parsing is active, causing VF/PF isolation breakage and possible traffic disruption or policy misclassification.

## 6. Manual review recommendation

**MANUAL CHECK REQUIRED**

Manual review is required because this affects SR-IOV VF/PF isolation and shared hardware parser state. It should not be auto-closed as a simple correctness fix, even though it does not show a memory-corruption or direct LPE primitive.

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

Patch: octeontx2-af: Block VFs from clobbering special CGX PKIND state [ Upstream
Commit: d3c6b0f48f126a36955b3fb4154a59d0b3621d97
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d3c6b0f48f126a36955b3fb4154a59d0b3621d97

Changed files:
  drivers/net/ethernet/marvell/octeontx2/af/cgx.c
  drivers/net/ethernet/marvell/octeontx2/af/cgx.h
  drivers/net/ethernet/marvell/octeontx2/af/rvu.h
  drivers/net/ethernet/marvell/octeontx2/af/rvu_cgx.c
  drivers/net/ethernet/marvell/octeontx2/af/rvu_nix.c
  drivers/net/ethernet/marvell/octeontx2/af/rvu_npc.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=d3c6b0f48f126a36955b3fb4154a59d0b3621d97

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

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

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:N/I:L/A:H
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:H
  The Best / paranoid CVSS score: 7

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: 5

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: NO
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).