[CVE-2026-72050][LOW] octeontx2-af: Free BPID bitmap on setup failure

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

CVE: CVE-2026-72050
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: octeontx2-af: Free BPID bitmap on setup failure
Commit: 7a939b683a74bd7d7ce4e3b7f696b491c8d71af4
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7a939b683a74bd7d7ce4e3b7f696b491c8d71af4
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72050
Analysis date: Sat, 15 Aug 2026 07:41:40 -0400
ActionableScore: 0
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
No one-sentence report phrase was found.

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

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

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-72050	LOW	CHECK WITH IMPACT FROM ORIG NN IMPORTANT	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';*CWE-401;*CWE-772;**CWE-400;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.1';DESCR 'octeontx2-af can leak the BPID bitmap when nix_setup_bpids allocates bpids and then fails one of the following mapping array allocations. The bug is an error path resource leak rather than memory corruption because the leaked object is not shown to be reused through a stale pointer. For the CVSS the PR:H is used because reliable triggering normally requires administrative control over driver setup, device reprobe, or comparable hardware management operations. The issue is not network reachable and cannot be triggered by normal packet traffic alone. Impact is mainly denial of service through resource exhaustion, but practical exploitation is limited because the leak depends on setup failure and likely needs repeated attempts.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 0)	YES	REMOTE INIT NOMEMCHK SIMPLEFIX ERRORPATH 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=0

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

2. Signal breakdown
* Resource leak only: BPID bitmap allocated with `kcalloc()` is not freed on later setup allocation failure.
* No memory corruption signal: no UAF, double-free, OOB write, stale pointer reuse, refcount abuse, or attacker-controlled overwrite is shown.
* No reliable strong DoS: resource exhaustion would require repeated setup failures and is not a direct crash primitive.
* Requires admin/root/CAP_* in typical deployments: -2, because reliable triggering normally requires driver/device setup, reprobe, or comparable privileged hardware management.
* Rare hardware/device-specific path: -1, because this is limited to Marvell OcteonTX2 AF driver setup.
* Final score is floored at 0.

3. Reachability analysis
This is a local privileged setup/error-path issue in the `octeontx2-af` driver. Normal packet traffic does not appear to reach this path. Namespaces or containers do not normally lower the requirement because physical device setup and reprobe are host-administrative operations. Practical exploitation requires both access to the affected hardware/driver path and repeated allocation-failure conditions.

4. Severity interpretation
This behaves like a Low or ordinary Moderate resource leak, not an Important-class kernel vulnerability. Theoretical impact is memory exhaustion, but realistic exploitation is weak because the leak occurs only on setup failure and requires privileged device-management control. There is no supported privilege escalation or memory corruption primitive.

5. One-sentence report phrase
`octeontx2-af leaks the BPID bitmap on setup allocation failure, but triggering is local privileged and impact is limited to potential resource exhaustion under repeated failure conditions.`

6. Manual review recommendation
NO MANUAL CHECK NEEDED. This can be auto-closed for urgent triage because it is a privileged driver setup memory leak without evidence of memory corruption, network reachability, or privilege escalation.

Call-site confidence: high, because the affected allocation and cleanup error paths are visible in the patch.

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

Patch: octeontx2-af: Free BPID bitmap on setup failure
Commit: 7a939b683a74bd7d7ce4e3b7f696b491c8d71af4
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7a939b683a74bd7d7ce4e3b7f696b491c8d71af4

Commit description:

nix_setup_bpids() allocates bp->bpids with rvu_alloc_bitmap(), which uses
a plain kcalloc(). If any of the following devm_kcalloc() allocations for
the BPID mapping arrays fails, the function returns without freeing the
bitmap. Free the BPID bitmap before returning from those error paths.

Fixes: d6212d2 ("octeontx2-af: Create BPIDs free pool")
Cc: stable@vger.kernel.org
Signed-off-by: Haoxiang Li <haoxiang_li2024@163.com>
Reviewed-by: Simon Horman <horms@kernel.org>
Link: https://patch.msgid.link/20260623114316.2182271-1-haoxiang_li2024@163.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

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

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

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

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

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

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