[CVE-2026-72399][MODERATE 7.0] net: enetc: check the number of BDs needed for xdp_frame [ Upstream

[CVE-2026-72399][MODERATE 7.0] net: enetc: check the number of BDs needed for xdp_frame [ Upstream

[AL-KERNEL]

CVE: CVE-2026-72399
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: net: enetc: check the number of BDs needed for xdp_frame [ Upstream
Commit: 1ecb199b0e6d12ab6c26c0b7edf1a8f4472d9aed
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1ecb199b0e6d12ab6c26c0b7edf1a8f4472d9aed
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72399
Analysis date: Sat, 15 Aug 2026 21:51:36 -0400
ActionableScore: 7
ActionableScore lower bound: 5
Actionable bucket: Strong Important candidate / Actionable Moderate at minimum
Manual review required: YES

Summary:
An ENETC XDP_REDIRECT fragment-count bug can overrun a stack BD array when a multi-fragment xdp_frame needs more descriptors than ENETC_MAX_SKB_FRAGS, creating a device-specific but actionable kernel memory-corruption and DoS risk.

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

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

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-72399	MODERATE	CHECK WITH IMPACT FROM ORIG NN IMPORTANT	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H';*CWE-787;CWE-121;CWE-129;Other CVSS 'AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H';BEST CVSS score: '7.5';DESCR 'An out of bounds access in the ENETC XDP_REDIRECT transmit path can occur because xdp_redirect_arr is sized as ENETC_MAX_SKB_FRAGS while an xdp_frame may require more BDs when it carries too many fragments. A crafted or unusual multi fragment XDP frame can make enetc_xdp_frame_to_xdp_tx_swbd operate past the stack array boundary, which makes this a kernel memory corruption candidate rather than a pure resource exhaustion issue. For the CVSS the PR:N is used in the paranoid score because a remote or adjacent sender may not need privileges on the target if an XDP_REDIRECT setup is already active. The issue is best treated as adjacent network reachable because exploitation depends on a specific NIC and XDP redirect data path, often in the same L2 or controlled network segment. Impact is at least denial of service via kernel crash and in the worst case may allow confidentiality or integrity impact due to kernel stack memory corruption.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Strong Important candidate / Actionable Moderate at minimum (with actual score 7)	YES	REMOTE OOB SIMPLEFIX NETWORK SKB LINUS KPANIC  DECREASED_TO_MODERATE7_BASED_ON_FALSEPOSCHECKOFKP	YES	NO	checked

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

ActionableScore=7
ActionableScoreLower=5

## 1. ActionableScore

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

## 2. Signal breakdown

Conservative scoring:

* +2 Remote reachable / network-triggerable: the vulnerable path is in ENETC XDP_REDIRECT transmit handling and may be reached by network-fed XDP frames if XDP redirect is already configured.
* +1 Constrained kernel buffer overwrite: `xdp_redirect_arr` is a fixed-size stack array and excessive fragments can make the helper access beyond it, but the written data is likely driver or frame metadata rather than an arbitrary attacker-chosen payload.
* +1 Memory layout invariant restoration: the patch restores consistency between `nr_frags + 1` and the local BD array capacity.
* +1 Reliable kernel crash / strong DoS: stack OOB access in a NIC transmit path is a credible kernel crash source.
* +1 Integrity impact plausible: stack corruption in kernel context can corrupt adjacent state, even if no controlled overwrite primitive is demonstrated.
* -1 Rare AND difficult-to-reach configuration: requires ENETC hardware, XDP_REDIRECT, and fragmented or multi-buffer XDP frames.

Paranoid scoring differences:

* Upgrade constrained overwrite to +2 Generic memory corruption: in the worst still-defensible interpretation this is a stack OOB write in kernel context.
* Add +1 Weak LPE concern: not a demonstrated LPE primitive, but kernel stack memory corruption in a packet-driven path deserves manual review.
* Keep the -1 configuration penalty because the exposure is device-specific and depends on XDP_REDIRECT setup.

Call-site confidence: medium. The changed function and immediate call into `enetc_xdp_frame_to_xdp_tx_swbd()` are visible, but the helper body is not included in the supplied patch.

## 3. Reachability analysis

The bug is not a default generic TCP/IP path. It requires an ENETC NIC and an active XDP_REDIRECT setup capable of producing `xdp_frame` objects with fragments. Loading or attaching XDP programs is normally privileged, especially when unprivileged BPF is disabled, so a local unprivileged user should not automatically be assumed able to configure the vulnerable path.

However, once the XDP redirect path is already configured by an administrator or appliance policy, a remote or adjacent sender may be able to influence packet shape and drive multi-fragment XDP frames through the vulnerable transmit path. This makes the issue more actionable than a purely local privileged driver bug, but less broadly exposed than a common networking-core receive parser.

Namespaces and containers do not substantially lower the setup requirement unless the environment delegates XDP or network administration capabilities. In such delegated environments, practical reachability could be higher.

## 4. Severity interpretation

This is not an ordinary Moderate resource leak or validation-only cleanup. The patch prevents an out-of-bounds access to a kernel stack array in a network driver transmit path. Realistic exploitation is constrained by hardware and XDP configuration, but the bug class is memory corruption rather than simple DoS.

The conservative interpretation is Actionable Moderate because the primitive is constrained and device-specific. The paranoid interpretation is a Strong Important candidate because a packet-driven kernel stack OOB write can plausibly lead to more than a crash, even though no reliable privilege-escalation primitive is demonstrated by the patch.

## 5. One-sentence report phrase

An ENETC XDP_REDIRECT fragment-count bug can overrun a stack BD array when a multi-fragment xdp_frame needs more descriptors than ENETC_MAX_SKB_FRAGS, creating a device-specific but actionable kernel memory-corruption and DoS risk.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: this is a kernel stack out-of-bounds access in a network-driven XDP path. Even with device and configuration constraints, the memory-corruption class and possible packet influence make it unsafe to auto-close.

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

Patch: net: enetc: check the number of BDs needed for xdp_frame [ Upstream
Commit: 1ecb199b0e6d12ab6c26c0b7edf1a8f4472d9aed
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1ecb199b0e6d12ab6c26c0b7edf1a8f4472d9aed

Changed files:
  drivers/net/ethernet/freescale/enetc/enetc.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=1ecb199b0e6d12ab6c26c0b7edf1a8f4472d9aed

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

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

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

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