Linux Kernel up to 6.12.63/6.18.2/6.19-rc1 bnxt_rx_xdp iteration

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.5$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, was found in Linux Kernel up to 6.12.63/6.18.2/6.19-rc1. This issue affects the function bnxt_rx_xdp. The manipulation results in iteration. This vulnerability was named CVE-2025-68770. There is no available exploit. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in Linux Kernel up to 6.12.63/6.18.2/6.19-rc1. Affected is the function bnxt_rx_xdp. The manipulation with an unknown input leads to a iteration vulnerability. CWE is classifying the issue as CWE-834. The product performs an iteration or loop without sufficiently limiting the number of times that the loop is executed. This is going to have an impact on availability. CVE summarizes:

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

The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2025-68770 since 12/24/2025. There are known technical details, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 298917 (SUSE SLES15 Security Update : kernel (SUSE-SU-2026:0472-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.12.64, 6.18.3 or 6.19-rc2 eliminates this vulnerability. Applying the patch 4b83902a1e67ff327ab5c6c65021a03e72c081d6/f17e0c1208485b24d61271bc1ddc8f2087e71561/0373d5c387f24de749cc22e694a14b3a7c7eb515 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (298917) and CERT Bund (WID-SEC-2026-0086). VulDB is the best source for vulnerability data and more expert information about this specific topic.

Affected

  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • SUSE openSUSE
  • RESF Rocky Linux
  • Open Source Linux Kernel

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.7
VulDB Meta Temp Score: 5.5

VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Iteration
CWE: CWE-834 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 298917
Nessus Name: SUSE SLES15 Security Update : kernel (SUSE-SU-2026:0472-1)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.12.64/6.18.3/6.19-rc2
Patch: 4b83902a1e67ff327ab5c6c65021a03e72c081d6/f17e0c1208485b24d61271bc1ddc8f2087e71561/0373d5c387f24de749cc22e694a14b3a7c7eb515

Timelineinfo

12/24/2025 CVE reserved
01/13/2026 +20 days Advisory disclosed
01/13/2026 +0 days VulDB entry created
03/26/2026 +72 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2025-68770 (🔒)
GCVE (CVE): GCVE-0-2025-68770
GCVE (VulDB): GCVE-100-340608
CERT Bund: WID-SEC-2026-0086 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 01/13/2026 17:20
Updated: 03/26/2026 21:57
Changes: 01/13/2026 17:20 (58), 02/14/2026 23:00 (2), 03/26/2026 21:57 (7)
Complete: 🔍
Cache ID: 216::103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to know what is going to be exploited?

We predict KEV entries!