HIGH 7.5

CVE-2026-53087: Linux bcmgenet Driver Memory Leak Causes Network DoS

A memory leak exists in the Linux kernel's Broadcom GENET network driver. When the driver cleans up the transmit queue during error recovery or shutdown, it discards frames still in flight but fails to return the associated memory buffers back to the free pool. This causes those buffers to become unavailable for reuse, gradually depleting the driver's ability to transmit new data until the system may become unresponsive or crash.

Source data · NVD / CISA · public domain

CVSS
3.1 · 7.5 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weaknesses (CWE)
CWE-401
Affected products
1 configuration(s)
Published / Modified
2026-06-24 / 2026-07-23

NVD description (verbatim)

In the Linux kernel, the following vulnerability has been resolved: net: bcmgenet: fix leaking free_bds While reclaiming the tx queue we fast forward the write pointer to drop any data in flight. These dropped frames are not added back to the pool of free bds. We also need to tell the netdev that we are dropping said data.

6 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-53087 is a resource exhaustion vulnerability in the bcmgenet driver within the Linux kernel. The vulnerability occurs in the transmit queue reclamation logic. When frames are dropped by fast-forwarding the write pointer during queue cleanup, the corresponding buffer descriptors (free_bds) are not returned to the available pool, nor is the netdev layer notified of the dropped packets. This violates the driver's resource accounting and leads to CWE-401 (Missing Release of Memory after Effective Lifetime). Over time, repeated queue reclamation events can exhaust transmable buffer resources, causing denial of service.

Business impact

Organizations running Linux systems with Broadcom GENET network interfaces face potential denial of service on affected machines. Repeated or sustained network queue cleanup events can leak memory buffers, eventually starving legitimate network traffic transmission. This is particularly concerning in data center, embedded, or IoT deployments where Broadcom network hardware is prevalent. Service degradation may manifest as network timeouts, dropped connections, or system unresponsiveness, impacting availability and user experience.

Affected systems

The vulnerability affects Linux kernel versions running the bcmgenet driver. This driver is used in systems with Broadcom GENET network interface controllers, commonly found in ARM-based embedded systems, some server platforms, and network appliances. Affected parties should verify their kernel version and confirm whether bcmgenet is active in their network stack (via lsmod or similar kernel module inspection tools).

Exploitability

This is a memory leak triggered through normal network operations rather than requiring direct attacker interaction. The vulnerability manifests when the driver reclaims the transmit queue—a routine operation that may occur during network resets, error recovery, or driver unload. No special privileges, network access controls, or user interaction are required to trigger the condition. The CVSS 3.1 score of 7.5 (HIGH, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) reflects the ease of exploitation and the availability impact, though neither confidentiality nor integrity is directly compromised.

Remediation

The kernel developers have resolved this issue by ensuring that when the transmit queue is reclaimed, buffer descriptors are properly returned to the free pool and the netdev layer is notified of dropped packets. Organizations should apply the patched kernel version from their Linux distribution. Verify the patch status through your vendor's advisory and test the update in a staging environment before production deployment.

Patch guidance

Obtain and install the patched Linux kernel from your distribution's repository or the official Linux kernel project. The fix modifies the transmit queue cleanup routine in the bcmgenet driver to correctly account for released buffers. Distributions typically provide kernel updates via their package manager (apt, yum, zypper, etc.). After patching, reboot the affected system to activate the fix. Confirm bcmgenet is loaded with the new kernel version using 'modinfo bcmgenet' or kernel log inspection.

Detection guidance

Monitor kernel logs and system metrics for signs of buffer exhaustion: watch for repeated 'out of memory' errors tied to network driver operations, or persistent warnings from the bcmgenet driver about queue state. Use 'ethtool -S <interface>' to inspect bcmgenet interface statistics for anomalies in dropped packets or transmit errors. Correlate timestamp spikes in tx_dropped counters with network resets or driver state changes. Kernel debugging tools (e.g., 'cat /proc/net/dev' or network monitoring with 'ip' and 'ss' commands) can reveal reduced network performance or stalled connections on affected interfaces.

Why prioritize this

This vulnerability merits prompt patching because it affects availability through a mechanism that does not require special attack sophistication—ordinary network operations can trigger buffer exhaustion. The HIGH CVSS score reflects the straightforward exploitability and direct availability impact. Organizations with Broadcom GENET hardware should prioritize this over lower-severity issues, particularly if they operate critical network services or embedded systems where downtime is costly. The lack of KEV status does not diminish urgency; exploitation may simply not yet be weaponized in public attack campaigns.

Risk score, explained

CVE-2026-53087 receives a CVSS 3.1 score of 7.5 (HIGH) because: (1) Network vector (AV:N) means remote triggering is possible through normal network traffic patterns; (2) Low complexity (AC:L) indicates no special attack prerequisites; (3) No privileges (PR:N) or user interaction (UI:N) required; (4) Availability impact is High (A:H) due to resource exhaustion leading to denial of service. Confidentiality and Integrity are not affected, keeping the score below Critical. The vulnerability is practically exploitable by any actor with network reachability to a system running the vulnerable driver.

Frequently asked questions

Does this vulnerability require remote code execution or data exfiltration?

No. This is a denial-of-service vulnerability focused on resource exhaustion. It does not provide attackers with the ability to execute arbitrary code, read sensitive data, or modify system state. The impact is limited to availability—the affected system may become unresponsive or unreliable for network communication.

Which versions of the Linux kernel are affected?

The vulnerability exists in kernel versions running the bcmgenet driver. Consult your Linux distribution's official security advisory for specific affected kernel versions and the recommended patched version. Check your current kernel version with 'uname -r' and cross-reference it against your vendor's CVE advisory.

Can I mitigate this without rebooting?

A kernel memory leak typically cannot be fully mitigated without reboot, as the fix is in kernel code. Temporary mitigation might include limiting network traffic intensity or scheduling periodic network driver resets if supported by your hardware, but these are workarounds, not solutions. The proper remedy is to patch and reboot.

Why is this vulnerability relevant if it is not yet in the KEV catalog?

The KEV (Known Exploited Vulnerabilities) catalog tracks vulnerabilities actively exploited in the wild. Absence from KEV does not mean a vulnerability is unimportant or unexploitable—it may simply mean public exploit development or attack campaigns have not yet targeted it widely. A HIGH-severity availability vulnerability should still be prioritized based on CVSS, affected system criticality, and patch availability.

This analysis is provided for informational purposes to assist security teams in vulnerability assessment and remediation planning. The information is derived from published CVE data and is accurate as of the modification date (2026-07-23). Organizations must independently verify patch availability and compatibility with their specific kernel versions and distributions before deployment. Actual exploitation scenarios may vary based on system configuration, network topology, and driver state. Consult official vendor advisories and security bulletins for authoritative guidance on affected versions and patches. Source: NVD (public-domain), retrieved 2026-08-01. Analysis generated by SEC.co (claude-haiku-4-5).