[CVE-2026-53229][MODERATE 7.0] net/mlx5e: xsk: Fix DMA and xdp_frame leak on XDP_TX xmit failure [ Upstream

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

CVE: CVE-2026-53229
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: net/mlx5e: xsk: Fix DMA and xdp_frame leak on XDP_TX xmit failure [ Upstream
Commit: 7b3eeba50fbc3b45f279037c29a87a90e8bac1e1
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7b3eeba50fbc3b45f279037c29a87a90e8bac1e1
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53229
Analysis date: Thu, 25 Jun 2026 17:25:04 -0400
ActionableScore: 5
ActionableScore lower bound: 0
Actionable bucket: Actionable Moderate under paranoid deployment assumptions / Borderline Moderate conservatively
Manual review required: NO

Summary:
A missing cleanup path in mlx5e XSK XDP_TX can leak DMA mappings and xdp_frame objects when transmit fails, causing a configuration-dependent denial of service in systems using mlx5 AF_XDP zero-copy and XDP_TX workloads.

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

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

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

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

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

CVE-2026-53229	MODERATE	CHECK	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:A/AC:H/PR:N/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: '5.3';DESCR 'A DMA mapping and xdp_frame resource leak in the mlx5e XSK XDP_TX path can occur when xmit_xdp_frame fails, for example when the XDPSQ is full. The failure path returns without dma_unmap_single and xdp_return_frame, while the xdpi_fifo entry is pushed only on success, so the normal completion path cannot reclaim the leaked resources. For the CVSS the PR:N is used in the paranoid score because a remote packet source may be sufficient when the target is already configured with mlx5 AF_XDP zero copy and an XDP_TX workload. The issue is not generally Internet exposed by default and practical triggering depends on a specific NIC, driver, XDP program, XSK setup, and sustained traffic that can drive transmit failures. Impact is denial of service through DMA mapping leaks, frame leaks, device warnings on unbind, and possible resource exhaustion. No evidence supports confidentiality impact, integrity impact, UAF, or privilege escalation.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate under paranoid deployment assumptions / Borderline Moderate conservatively (with actual score 3)  SKIP CVE-2026-53229  SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	REMOTE OOB LEAK NETWORK DMAorINTERRUPT HARDWARE MEMORY  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH	-	-	checked

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

ActionableScore=5
ActionableScoreLower=0

## 1. ActionableScore

* Conservative score: 0
* Paranoid score: 5
* Final recommended bucket: **Actionable Moderate under paranoid deployment assumptions / Borderline Moderate conservatively**

## 2. Signal breakdown

Paranoid score signals:

* Remote reachable / network-triggerable: +2
  The affected code is in the mlx5e XSK XDP_TX packet path. If the system is already configured with mlx5 AF_XDP zero-copy and an XDP_TX workload, external traffic may help drive the failing transmit path.

* Reliable kernel crash / strong DoS: +1
  The bug leaks DMA mappings and xdp_frame objects when xmit_xdp_frame fails. Sustained triggering may exhaust resources or leave pending DMA allocations.

* Availability impact realistic: +1
  The impact is availability-oriented: DMA/resource leakage, warnings on driver unbind, and potential device or system degradation.

* Common packet-processing / high-performance networking path: +1
  mlx5e is common in data-center deployments, and XDP/AF_XDP paths are performance-critical packet-processing paths.

* Rare and configuration-dependent path: -1
  Triggering requires mlx5 hardware, XSK/AF_XDP zero-copy, XDP_TX behavior, and transmit failure such as a full XDPSQ.

* Privileged DMA/device-management context: +1
  The leak occurs in a trusted NIC driver DMA path. This does not imply memory corruption, but it increases triage interest compared with a generic userspace resource leak.

Conservative score signals:

* Reliable DoS/resource leak: +1
* Availability impact plausible: +1
* DMA/device driver context: +1
* Requires privileged setup in typical deployments: -2
* Rare configuration-dependent path: -1

Total conservative result: 0.

## 3. Reachability analysis

A normal remote attacker cannot trigger this on arbitrary systems. The path requires a Mellanox mlx5 device, AF_XDP/XSK zero-copy setup, an XDP_TX workload, and a condition where sq->xmit_xdp_frame() fails. In typical deployments, configuring XDP/AF_XDP requires elevated privileges such as CAP_NET_ADMIN or equivalent administrative control.

However, once such a datapath is already configured by an administrator, a remote or adjacent packet source may be able to contribute traffic that exercises the XDP_TX failure path. This supports a paranoid network-influenced interpretation, but not a default Internet-reachable one.

Namespaces or containers may matter if CAP_NET_ADMIN or AF_XDP setup is delegated to less-trusted workloads. Without such delegation, practical attacker control is limited.

## 4. Severity interpretation

This behaves primarily like a resource leak / DoS issue, not like a memory corruption or privilege escalation vulnerability. The patch shows missing cleanup of DMA mapping and xdp_frame resources on an error path. It does not show UAF, double-free, OOB write, arbitrary write, information disclosure, or a Dirty-Pipe-like ownership violation.

Conservatively, this is ordinary Moderate or Low-like because exploitation requires a specialized NIC and privileged XDP/XSK configuration. Under paranoid deployment assumptions where the datapath is already exposed to untrusted traffic, it becomes an Actionable Moderate candidate because sustained traffic may cause DMA/resource exhaustion in a kernel network driver path.

## 5. One-sentence report phrase

A missing cleanup path in mlx5e XSK XDP_TX can leak DMA mappings and xdp_frame objects when transmit fails, causing a configuration-dependent denial of service in systems using mlx5 AF_XDP zero-copy and XDP_TX workloads.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Manual review is recommended because this is a DMA-adjacent networking driver resource leak with possible external traffic influence after privileged setup. It is not strong enough for Important by itself because no memory corruption, confidentiality impact, integrity impact, or privilege escalation primitive is supported by the patch.

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

Patch: net/mlx5e: xsk: Fix DMA and xdp_frame leak on XDP_TX xmit failure [ Upstream
Commit: 7b3eeba50fbc3b45f279037c29a87a90e8bac1e1
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7b3eeba50fbc3b45f279037c29a87a90e8bac1e1

Changed files:
  kernel/dma/debug.c
  drivers/net/ethernet/mellanox/mlx5/core/en/xdp.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=7b3eeba50fbc3b45f279037c29a87a90e8bac1e1

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

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

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

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