[CVE-2026-74269][IMPORTANT] bnxt: fix head underflow on XDP head-grow [ Upstream

[CVE-2026-74269][IMPORTANT] bnxt: fix head underflow on XDP head-grow [ Upstream

[AL-KERNEL]

CVE: CVE-2026-74269
Priority: IMPORTANT
AL-KERNEL base severity: IMPORTANT
KPANIC flag: YES
Patch: bnxt: fix head underflow on XDP head-grow [ Upstream
Commit: bb72b1c6755631c74b7e0878ee55bb81c06776c0
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bb72b1c6755631c74b7e0878ee55bb81c06776c0
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74269
Analysis date: Sat, 15 Aug 2026 09:18:27 -0400
ActionableScore: 7
ActionableScore lower bound: 4
Actionable bucket: Strong Important candidate / Actionable Moderate at minimum
Manual review required: YES

Summary:
A bnxt XDP head-grow underflow can build an skb from the wrong fragment base, corrupt page_pool reference accounting, prematurely recycle pages still in use, and later cause a double free or kernel crash.

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

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

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: IMPORTANT
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-74269	IMPORTANT	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H';CWE-191;*CWE-416;CWE-415;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '7.1';DESCR 'A head underflow in the bnxt RX path can occur when native XDP grows the packet head and bnxt_rx_multi_page_skb builds the skb from data_ptr minus rx_offset instead of the real fragment start. The computed skb head can point before the current fragment, which can make skb teardown drop a page pool fragment reference for the wrong page or the wrong fragment. This can prematurely recycle memory that is still in use and can later result in a double free during driver teardown. For the CVSS the PR:L is used in the paranoid score because a reduced capability local user, container root, or service account with delegated XDP or network administration ability may be able to attach or influence the required XDP path without full host root. The vulnerable RX path may then be exercised by packets arriving on the bnxt interface, so the paranoid vector treats it as adjacent network reachable rather than public Internet reachable. Impact is at least denial of service via kernel crash and in worst case may allow confidentiality or integrity impact due to memory corruption and 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 OOB DANGER NETWORK SKB KERNEL_PANIC_PLUS_UAF TEST KPANIC MEMORY  KPANIC INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN6	YES	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:

* Generic memory corruption / strong corruption primitive: +2
  The patch describes wrong skb head construction, corrupted page pool fragment reference counts, premature page recycle, and later double free.
* Real lifetime corruption: +1
  The issue directly affects page pool lifetime and reference accounting.
* Reliable kernel crash / strong DoS: +1
  The reproducer crashes on bnxt hardware and in NIPA testing.
* Memory layout invariant restoration: +1
  The fix restores consistency between fragment offset, data_ptr, rx_offset, skb base, and skb_reserve layout.
* Privileged kernel/device-management memory corruption path: +1
  Corruption occurs inside a trusted NIC RX/page_pool path.
* Requires admin/root/CAP_* in typical deployments: -2
  Native XDP attachment normally requires CAP_BPF/CAP_NET_ADMIN or root-controlled configuration.
* Hardware/configuration specific: -1
  Requires bnxt hardware and the affected XDP head-grow/page-mode path.
* Corruption primitive constrained / no demonstrated attacker-controlled replacement: -1
  The patch shows refcount/lifetime corruption, but not a demonstrated controlled reclaim or arbitrary write.

Paranoid additional/changed signals:

* Weak LPE concern: +1
  Premature recycle and double free create a plausible memory-corruption concern, but controlled reclaim or object replacement is not demonstrated.
* Local low-privileged/delegated trigger concern: +1
  In containerized or delegated networking setups, a reduced-capability user or service account may control XDP attachment without full host root.
* Confidentiality impact plausible: +1
  Only for paranoid scoring, because recycled page pool memory could theoretically expose stale data if reuse becomes attacker-influenced.
* Integrity impact plausible: +1
  Only for paranoid scoring, because wrong-page lifetime corruption and double free can theoretically corrupt kernel-owned data.

## 3. Reachability analysis

The conservative trigger requires local administrative capability to attach or manage the XDP program on a bnxt interface. A purely remote attacker sending packets is not sufficient unless the vulnerable XDP head-grow program is already installed by someone else. Namespaces and containers matter because CAP_NET_ADMIN or CAP_BPF can be delegated to container root or service accounts, which lowers practical privilege in some deployments without granting full host root. The path is not universal, but it is in a real NIC RX packet-processing path with page_pool lifetime management, so it should not be treated as a simple driver crash.

## 4. Severity interpretation

Conservatively this is a borderline/manual-review Moderate because reliable triggering usually requires privileged XDP setup and bnxt-specific conditions. Paranoid interpretation is stronger because the patch explicitly describes page pool reference corruption, premature recycle while still in use, and double free. That is real lifetime memory corruption, not just a warning or validation bug. Practical LPE is not demonstrated, but the corruption class and skb/page_pool context justify Important-candidate manual triage.

## 5. One-sentence report phrase

A bnxt XDP head-grow underflow can build an skb from the wrong fragment base, corrupt page_pool reference accounting, prematurely recycle pages still in use, and later cause a double free or kernel crash.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

This is required because the bug involves page_pool lifetime corruption with premature recycle and double-free potential in a network RX path, even though the normal trigger is gated by privileged XDP configuration.

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

Patch: bnxt: fix head underflow on XDP head-grow [ Upstream
Commit: bb72b1c6755631c74b7e0878ee55bb81c06776c0
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bb72b1c6755631c74b7e0878ee55bb81c06776c0

Changed files:
  drivers/net/ethernet/broadcom/bnxt/bnxt.c
  drivers/net/ethernet/broadcom/bnxt/bnxt.h

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=bb72b1c6755631c74b7e0878ee55bb81c06776c0

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

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

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:H
  The Best / paranoid CVSS vector: AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
  The Best / paranoid CVSS score: 7.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: 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: IMPORTANT
KPANIC detected for this report: YES
Published priority for this report (same as in Subject): IMPORTANT

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