CVE-2025-21682: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: eth: bnxt: always recalculate features after XDP clearing, fix null-deref Recalculate features when XDP is detached. Before: # ip li set dev eth0 xdp obj xdp_dummy.bpf.o sec xdp # ip li set dev eth0 xdp off # ethtool -k eth0 | grep gro rx-gro-hw: off [requested on] After: # ip li set dev eth0 xdp obj xdp_dummy.bpf.o sec xdp # ip li set dev eth0 xdp off # ethtool -k eth0 | grep gro rx-gro-hw: on The fact that HW-GRO doesn't get re-enabled automatically is just a minor annoyance. The real issue is that the features will randomly come back during another reconfiguration which just happens to invoke netdev_update_features(). The driver doesn't handle reconfiguring two things at a time very robustly. Starting with commit 98ba1d931f61 ("bnxt_en: Fix RSS logic in __bnxt_reserve_rings()") we only reconfigure the RSS hash table if the "effective" number of Rx rings has changed. If HW-GRO is enabled "effective" number of rings is 2x what user sees. So if we are in the bad state, with HW-GRO re-enablement "pending" after XDP off, and we lower the rings by / 2 - the HW-GRO rings doing 2x and the ethtool -L doing / 2 may cancel each other out, and the: if (old_rx_rings != bp->hw_resc.resv_rx_rings && condition in __bnxt_reserve_rings() will be false. The RSS map won't get updated, and we'll crash with: BUG: kernel NULL pointer dereference, address: 0000000000000168 RIP: 0010:__bnxt_hwrm_vnic_set_rss+0x13a/0x1a0 bnxt_hwrm_vnic_rss_cfg_p5+0x47/0x180 __bnxt_setup_vnic_p5+0x58/0x110 bnxt_init_nic+0xb72/0xf50 __bnxt_open_nic+0x40d/0xab0 bnxt_open_nic+0x2b/0x60 ethtool_set_channels+0x18c/0x1d0 As we try to access a freed ring. The issue is present since XDP support was added, really, but prior to commit 98ba1d931f61 ("bnxt_en: Fix RSS logic in __bnxt_reserve_rings()") it wasn't causing major issues.
AI Analysis
Technical Summary
CVE-2025-21682 is a vulnerability in the Linux kernel's Broadcom NetXtreme (bnxt) Ethernet driver related to the handling of features recalculation after detaching eXpress Data Path (XDP) programs from network interfaces. Specifically, the vulnerability arises because the driver fails to properly re-enable hardware Generic Receive Offload (HW-GRO) after XDP is turned off, leading to inconsistent internal state management. This inconsistency manifests when the driver attempts to reconfigure the Receive Side Scaling (RSS) hash table and ring buffers. The problem is exacerbated by the logic introduced in commit 98ba1d931f61, which optimizes RSS reconfiguration only when the effective number of receive rings changes. Due to HW-GRO doubling the effective number of rings, lowering the rings by half can cause the condition to skip RSS map updates. Consequently, the driver may attempt to access freed memory (freed ring buffers), resulting in a NULL pointer dereference and kernel crash (BUG). The crash occurs in the __bnxt_hwrm_vnic_set_rss function during NIC initialization or reconfiguration, potentially causing denial of service (DoS) on affected systems. This vulnerability has existed since XDP support was introduced but became more impactful after the referenced commit. The issue is triggered by sequences of commands detaching XDP programs and adjusting network interface parameters, which are common in environments using advanced packet processing or network function virtualization. No known exploits are reported in the wild, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to systems running Linux kernels with the vulnerable bnxt driver, typically found in servers and network appliances using Broadcom NetXtreme Ethernet hardware. The impact includes potential denial of service due to kernel crashes triggered by routine network interface reconfigurations involving XDP. This can disrupt critical network services, affecting availability and operational continuity. Organizations relying on high-performance networking, such as data centers, cloud providers, and telecom operators, may experience service interruptions or degraded performance. Although the vulnerability does not directly expose confidentiality or integrity risks, the resulting instability could be exploited as part of a broader attack chain or cause significant operational disruption. The lack of known exploits reduces immediate risk, but the complexity of the issue and its presence in widely used Linux kernels necessitate prompt attention. European entities with extensive Linux infrastructure, especially those using Broadcom NICs and advanced networking features like XDP, are at higher risk.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should: 1) Apply the latest Linux kernel patches that address this bnxt driver issue as soon as they become available, ensuring the fix for proper feature recalculation after XDP detachment is included. 2) Temporarily avoid detaching XDP programs or reconfiguring network interfaces in ways that trigger the problematic code path until patched. 3) Monitor kernel logs for signs of NULL pointer dereferences or crashes related to bnxt driver functions. 4) Use kernel live patching solutions if available to minimize downtime during patch deployment. 5) Validate network driver versions and hardware compatibility in their environments, prioritizing updates on systems with Broadcom NetXtreme NICs. 6) Implement robust system monitoring and automated recovery mechanisms to quickly detect and respond to kernel crashes. 7) Coordinate with hardware and Linux distribution vendors for timely updates and advisories. These steps go beyond generic advice by focusing on the specific driver and feature interactions involved in the vulnerability.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain
CVE-2025-21682: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: eth: bnxt: always recalculate features after XDP clearing, fix null-deref Recalculate features when XDP is detached. Before: # ip li set dev eth0 xdp obj xdp_dummy.bpf.o sec xdp # ip li set dev eth0 xdp off # ethtool -k eth0 | grep gro rx-gro-hw: off [requested on] After: # ip li set dev eth0 xdp obj xdp_dummy.bpf.o sec xdp # ip li set dev eth0 xdp off # ethtool -k eth0 | grep gro rx-gro-hw: on The fact that HW-GRO doesn't get re-enabled automatically is just a minor annoyance. The real issue is that the features will randomly come back during another reconfiguration which just happens to invoke netdev_update_features(). The driver doesn't handle reconfiguring two things at a time very robustly. Starting with commit 98ba1d931f61 ("bnxt_en: Fix RSS logic in __bnxt_reserve_rings()") we only reconfigure the RSS hash table if the "effective" number of Rx rings has changed. If HW-GRO is enabled "effective" number of rings is 2x what user sees. So if we are in the bad state, with HW-GRO re-enablement "pending" after XDP off, and we lower the rings by / 2 - the HW-GRO rings doing 2x and the ethtool -L doing / 2 may cancel each other out, and the: if (old_rx_rings != bp->hw_resc.resv_rx_rings && condition in __bnxt_reserve_rings() will be false. The RSS map won't get updated, and we'll crash with: BUG: kernel NULL pointer dereference, address: 0000000000000168 RIP: 0010:__bnxt_hwrm_vnic_set_rss+0x13a/0x1a0 bnxt_hwrm_vnic_rss_cfg_p5+0x47/0x180 __bnxt_setup_vnic_p5+0x58/0x110 bnxt_init_nic+0xb72/0xf50 __bnxt_open_nic+0x40d/0xab0 bnxt_open_nic+0x2b/0x60 ethtool_set_channels+0x18c/0x1d0 As we try to access a freed ring. The issue is present since XDP support was added, really, but prior to commit 98ba1d931f61 ("bnxt_en: Fix RSS logic in __bnxt_reserve_rings()") it wasn't causing major issues.
AI-Powered Analysis
Technical Analysis
CVE-2025-21682 is a vulnerability in the Linux kernel's Broadcom NetXtreme (bnxt) Ethernet driver related to the handling of features recalculation after detaching eXpress Data Path (XDP) programs from network interfaces. Specifically, the vulnerability arises because the driver fails to properly re-enable hardware Generic Receive Offload (HW-GRO) after XDP is turned off, leading to inconsistent internal state management. This inconsistency manifests when the driver attempts to reconfigure the Receive Side Scaling (RSS) hash table and ring buffers. The problem is exacerbated by the logic introduced in commit 98ba1d931f61, which optimizes RSS reconfiguration only when the effective number of receive rings changes. Due to HW-GRO doubling the effective number of rings, lowering the rings by half can cause the condition to skip RSS map updates. Consequently, the driver may attempt to access freed memory (freed ring buffers), resulting in a NULL pointer dereference and kernel crash (BUG). The crash occurs in the __bnxt_hwrm_vnic_set_rss function during NIC initialization or reconfiguration, potentially causing denial of service (DoS) on affected systems. This vulnerability has existed since XDP support was introduced but became more impactful after the referenced commit. The issue is triggered by sequences of commands detaching XDP programs and adjusting network interface parameters, which are common in environments using advanced packet processing or network function virtualization. No known exploits are reported in the wild, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to systems running Linux kernels with the vulnerable bnxt driver, typically found in servers and network appliances using Broadcom NetXtreme Ethernet hardware. The impact includes potential denial of service due to kernel crashes triggered by routine network interface reconfigurations involving XDP. This can disrupt critical network services, affecting availability and operational continuity. Organizations relying on high-performance networking, such as data centers, cloud providers, and telecom operators, may experience service interruptions or degraded performance. Although the vulnerability does not directly expose confidentiality or integrity risks, the resulting instability could be exploited as part of a broader attack chain or cause significant operational disruption. The lack of known exploits reduces immediate risk, but the complexity of the issue and its presence in widely used Linux kernels necessitate prompt attention. European entities with extensive Linux infrastructure, especially those using Broadcom NICs and advanced networking features like XDP, are at higher risk.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should: 1) Apply the latest Linux kernel patches that address this bnxt driver issue as soon as they become available, ensuring the fix for proper feature recalculation after XDP detachment is included. 2) Temporarily avoid detaching XDP programs or reconfiguring network interfaces in ways that trigger the problematic code path until patched. 3) Monitor kernel logs for signs of NULL pointer dereferences or crashes related to bnxt driver functions. 4) Use kernel live patching solutions if available to minimize downtime during patch deployment. 5) Validate network driver versions and hardware compatibility in their environments, prioritizing updates on systems with Broadcom NetXtreme NICs. 6) Implement robust system monitoring and automated recovery mechanisms to quickly detect and respond to kernel crashes. 7) Coordinate with hardware and Linux distribution vendors for timely updates and advisories. These steps go beyond generic advice by focusing on the specific driver and feature interactions involved in the vulnerability.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-12-29T08:45:45.739Z
- Cisa Enriched
- false
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9834c4522896dcbe97e8
Added to database: 5/21/2025, 9:09:08 AM
Last enriched: 6/30/2025, 5:13:13 PM
Last updated: 7/21/2025, 10:51:49 PM
Views: 5
Related Threats
CVE-2025-54455: CWE-798 Use of Hard-coded Credentials in Samsung Electronics MagicINFO 9 Server
CriticalCVE-2025-54454: CWE-798 Use of Hard-coded Credentials in Samsung Electronics MagicINFO 9 Server
CriticalCVE-2025-54450: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in Samsung Electronics MagicINFO 9 Server
HighCVE-2025-54449: CWE-434 Unrestricted Upload of File with Dangerous Type in Samsung Electronics MagicINFO 9 Server
CriticalCVE-2025-8022: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in bun
HighActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.