[CVE-2026-72410][LOW] octeontx2-af: Validate NIX maximum LFs correctly [ Upstream

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-72410
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: octeontx2-af: Validate NIX maximum LFs correctly [ Upstream
Commit: 0933fe0130eb71af0c3ab481b40f543b458a8c54
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0933fe0130eb71af0c3ab481b40f543b458a8c54
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72410
Analysis date: Sun, 16 Aug 2026 05:49:28 -0400
ActionableScore: 1
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
An incorrect octeontx2 AF devlink validation check could allow a privileged or delegated local device-management user to resize the maximum NIX LF limit after PF/VF LFs were already assigned, potentially causing resource-policy inconsistency but with no evidence of memory corruption or privilege escalation.

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

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

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: LOW
Manual review required: NO

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

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

CVE-2026-72410	LOW	CHECK WITH IMPACT FROM ORIG NN IMPORTANT	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L';*CWE-20;CWE-754;CWE-840;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L';BEST CVSS score: '4.4';DESCR 'The octeontx2 AF devlink validation used the wrong resource state when deciding whether the maximum number of NIX LFs could be changed. A local administrator or delegated network management process could resize the NIX LF limit after PF/VF LFs were already assigned, which may leave resource allocation policy inconsistent for the affected device. For the CVSS the PR:L value is used for the paranoid view because some deployments may delegate devlink or CAP_NET_ADMIN access to a reduced capability root, container root, or service account, although the typical host case is PR:H. The issue is not directly network reachable and is triggered through a local devlink control plane operation. Impact is limited to configuration integrity loss and possible device availability impact, with no evidence of memory corruption, information disclosure, or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1)	YES	REMOTE INIT NETWORK LINUS  LOWERED_FROM_HIGH_BASED_ON_GUESSCVSS  DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5 DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	YES	NO	checked

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

ActionableScore=1
ActionableScoreLower=0

## 1. ActionableScore

* Conservative score: 0
* Paranoid score: 1
* Final recommended bucket: **Ordinary Moderate / Low-like**::

## 2. Signal breakdown

Triggered signals:

* Integrity impact plausible: +1
  The incorrect validation may allow resizing the maximum NIX LF limit after PF/VF LFs have already been assigned, creating an inconsistent device resource policy.
* Availability impact possible but weak: +0 to +1 paranoid only
  A bad LF limit may plausibly affect device operation or PF/VF resource assignment, but the patch does not show a reliable crash, hang, memory corruption, or system-wide DoS.
* Requires admin/root/CAP_NET_ADMIN in typical deployments: -2 conservative
  The affected operation is a devlink control-plane configuration command, normally restricted to privileged network/device administrators.
* Rare and hardware-specific subsystem: -1 conservative
  This is specific to Marvell octeontx2 AF hardware and its devlink NIX LF management path.

Not triggered:

* No remote reachability.
* No local unprivileged trigger in typical deployments.
* No UAF, OOB write, double free, stale pointer, refcount issue, or arbitrary write.
* No demonstrated privilege escalation.
* No security-boundary bypass beyond privileged device resource misconfiguration.

## 3. Reachability analysis

The bug is reachable through a local devlink configuration path for octeontx2 AF devices. In normal deployments this requires CAP_NET_ADMIN or equivalent administrative control over the device. Namespaces or delegated management services could reduce the practical privilege level, but the attacker still needs access to the local device-management control plane. The path is not network-triggerable by packet traffic and depends on specific Marvell hardware being present.

Call-site confidence: medium-high. The changed function is clearly a devlink validation path, but the full devlink parameter registration and all operational consequences are not included in the snippet.

## 4. Severity interpretation

This behaves like an ordinary Moderate or Low-like configuration validation issue. The patch corrects the condition used to decide whether NIX LFs have already been assigned before allowing resize. There is no concrete evidence of memory corruption, privilege escalation, information disclosure, or reliable kernel crash. The paranoid score only preserves a small concern for inconsistent PF/VF resource assignment in delegated device-management environments.

## 5. One-sentence report phrase

An incorrect octeontx2 AF devlink validation check could allow a privileged or delegated local device-management user to resize the maximum NIX LF limit after PF/VF LFs were already assigned, potentially causing resource-policy inconsistency but with no evidence of memory corruption or privilege escalation.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

This is a privileged local validation-only fix in a hardware-specific devlink path, with no concrete corruption primitive, no remote trigger, and no demonstrated security-boundary bypass.

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

Patch: octeontx2-af: Validate NIX maximum LFs correctly [ Upstream
Commit: 0933fe0130eb71af0c3ab481b40f543b458a8c54
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0933fe0130eb71af0c3ab481b40f543b458a8c54

Changed files:
  drivers/net/ethernet/marvell/octeontx2/af/rvu_devlink.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=0933fe0130eb71af0c3ab481b40f543b458a8c54

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

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

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

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: 0
  Paranoid ActionableScore: 1

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: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

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