---
id: CVE-2025-68770
title: 'bnxt_en: Fix XDP_TX path'
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  bnxt_en: Fix XDP_TX path

  For XDP_TX action in bnxt_rx_xdp(), clearing of the event flags is not
  correct.  __bnxt_poll_work() -> bnxt_rx_pkt() -> bnxt_rx_xdp() may be
  l…
severity: high
cvss: 7.5
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'
cvssSource: cna
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 7f0a168b0441ef7fd6b46563efb2706c58ac2a4c <
    4b83902a1e67ff327ab5c6c65021a03e72c081d6
  - >-
    Linux >= 7f0a168b0441ef7fd6b46563efb2706c58ac2a4c <
    f17e0c1208485b24d61271bc1ddc8f2087e71561
  - >-
    Linux >= 7f0a168b0441ef7fd6b46563efb2706c58ac2a4c <
    0373d5c387f24de749cc22e694a14b3a7c7eb515
  - Linux 6.8
ssvc:
  exploitation: none
  automatable: 'yes'
  technicalImpact: partial
  timestamp: '2026-10-16T15:05:09.771100Z'
published: '2026-01-13'
updated: '2026-10-16'
sourceUpdated: '2026-10-16T15:09:44.479Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2025-68770'
references:
  - url: 'https://git.kernel.org/stable/c/4b83902a1e67ff327ab5c6c65021a03e72c081d6'
  - url: 'https://git.kernel.org/stable/c/f17e0c1208485b24d61271bc1ddc8f2087e71561'
  - url: 'https://git.kernel.org/stable/c/0373d5c387f24de749cc22e694a14b3a7c7eb515'
tags:
  - cve.org
epss: 0.00511
epssPercentile: 0.42241
ingestedAt: '2026-10-16T17:24:46.632Z'
---

## Overview

In the Linux kernel, the following vulnerability has been resolved:

bnxt_en: Fix XDP_TX path

For XDP_TX action in bnxt_rx_xdp(), clearing of the event flags is not
correct.  __bnxt_poll_work() -> bnxt_rx_pkt() -> bnxt_rx_xdp() may be
looping within NAPI and some event flags may be set in earlier
iterations.  In particular, if BNXT_TX_EVENT is set earlier indicating
some XDP_TX packets are ready and pending, it will be cleared if it is
XDP_TX action again.  Normally, we will set BNXT_TX_EVENT again when we
successfully call __bnxt_xmit_xdp().  But if the TX ring has no more
room, the flag will not be set.  This will cause the TX producer to be
ahead but the driver will not hit the TX doorbell.

For multi-buf XDP_TX, there is no need to clear the event flags and set
BNXT_AGG_EVENT.  The BNXT_AGG_EVENT flag should have been set earlier in
bnxt_rx_pkt().

The visible symptom of this is that the RX ring associated with the
TX XDP ring will eventually become empty and all packets will be dropped.
Because this condition will cause the driver to not refill the RX ring
seeing that the TX ring has forever pending XDP_TX packets.

The fix is to only clear BNXT_RX_EVENT when we have successfully
called __bnxt_xmit_xdp().

## Affected

- `Linux >= 7f0a168b0441ef7fd6b46563efb2706c58ac2a4c < 4b83902a1e67ff327ab5c6c65021a03e72c081d6`
- `Linux >= 7f0a168b0441ef7fd6b46563efb2706c58ac2a4c < f17e0c1208485b24d61271bc1ddc8f2087e71561`
- `Linux >= 7f0a168b0441ef7fd6b46563efb2706c58ac2a4c < 0373d5c387f24de749cc22e694a14b3a7c7eb515`
- `Linux 6.8`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.