Network transmit lockup via cross-queue timeout recovery
Published Jun 24, 2026 · Updated Jun 24, 2026
Race condition in the Linux Kernel bcmgenet driver allows remote attackers to lock all transmit queues via sustained network traffic. The bcmgenet_timeout handler responds to one timed-out queue by reclaiming descriptors, re-enabling interrupts, and waking every transmit queue while other queues remain active. Reachability requires an active bcmgenet interface and traffic that times out one queue while others are transmitting; the resulting races can lock the interface's entire transmit path.
Summary
What happened
Race condition in the Linux Kernel bcmgenet driver allows remote attackers to lock all transmit queues via sustained network traffic. The bcmgenet_timeout handler responds to one timed-out queue by reclaiming descriptors, re-enabling interrupts, and waking every transmit queue while other queues remain active. Reachability requires an active bcmgenet interface and traffic that times out one queue while others are transmitting; the resulting races can lock the interface's entire transmit path.
The record
- CVE
- CVE-2026-53086
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-362, T1498
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 24, 2026CVE publishedPublication date reported by the CVE source.
- Jun 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=13ea657806cf73b379a0109f7042182f47c351a7 <5393b2b5bee2ac51a0043dc7f4ac3475f053d08d
- Affected versionversion=13ea657806cf73b379a0109f7042182f47c351a7 <681fdfe823b4f1036ed50b58b8838c7917ea389c
- Affected versionversion=13ea657806cf73b379a0109f7042182f47c351a7 <7ce1c26aac3b318886a57425f64b522da7389153
- Affected versionversion=13ea657806cf73b379a0109f7042182f47c351a7 <c270e2bec3e55a716d25c35341091339457ac883
- Affected versionversion=13ea657806cf73b379a0109f7042182f47c351a7 <e8206538cbaf4f4068e99a4cb1138690a1e00499
- Affected versionversion=13ea657806cf73b379a0109f7042182f47c351a7 <e85b0c0a12e967930044608311471b665baa315c
- Affected versionversion=4.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo