CVE-2025-68770VulnerabilityPublished 13 Jan 2026Updated 30 Jul 2026

CVE-2025-68770: Linux kernel · bnxt_en: Fix XDP_TX path For XDP_TX action in bnxt_rx_xdp(), clearing of the

Source GCVE Database

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-j6rg-wxjc-pxj8

What to do

AI-suggested

A fix for this vulnerability has been implemented in the Linux kernel bnxt_en driver. Users should apply the official kernel updates that include this patch. Since no vendor advisory or patch links are provided, check the Linux kernel mailing lists or distribution security advisories for the relevant fixed kernel versions.

Description

A vulnerability in the Linux kernel's bnxt_en driver affects the handling of XDP_TX action in the bnxt_rx_xdp() function. Incorrect clearing of event flags can cause the TX producer to advance without notifying the hardware, leading to the RX ring becoming empty and packet drops. The issue arises when the TX ring is full and the BNXT_TX_EVENT flag is cleared improperly, preventing the driver from refilling the RX ring. The fix involves only clearing the BNXT_RX_EVENT flag after successful transmission calls.

Impact

This vulnerability causes a denial of service condition where the RX ring becomes empty and incoming packets are dropped, impacting network traffic handling on affected systems. There is no confidentiality or integrity impact reported. The issue leads to availability degradation due to dropped packets and stalled network processing.

Summary

The Linux kernel bnxt_en driver had a flaw in the XDP_TX path where event flags were cleared incorrectly during the bnxt_rx_xdp() processing. Specifically, if the BNXT_TX_EVENT flag was set indicating pending XDP_TX packets, it could be cleared prematurely if the TX ring was full, causing the TX producer to advance without ringing the TX doorbell. This results in the RX ring associated with the TX XDP ring becoming empty and packets being dropped because the driver stops refilling the RX ring. The fix ensures BNXT_RX_EVENT is only cleared after a successful __bnxt_xmit_xdp() call, preventing this deadlock condition.

References

Community reviews

Loading reviews…