CPU hang via unchecked transmit consumer index
Published Oct 18, 2026 · Updated Oct 18, 2026
An infinite loop in Linux atl1 transmit cleanup allows attackers to hang a CPU via an invalid hardware consumer index. The atl1_intr_tx function uses cmb_tpd_next_to_clean without checking ring bounds, so its cleanup loop never reaches an out-of-range value such as 0xffff. Exposure requires the atl1 driver and an invalid hardware report during PCIe link or MAC reset; attacker control over that event is not established.
Summary
What happened
An infinite loop in Linux atl1 transmit cleanup allows attackers to hang a CPU via an invalid hardware consumer index. The atl1_intr_tx function uses cmb_tpd_next_to_clean without checking ring bounds, so its cleanup loop never reaches an out-of-range value such as 0xffff. Exposure requires the atl1 driver and an invalid hardware report during PCIe link or MAC reset; attacker control over that event is not established.
The record
- CVE
- CVE-2026-98494
- Published
- Oct 18, 2026
- Updated
- Oct 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 18, 2026CVE publishedPublication date reported by the CVE source.
- Oct 18, 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=2.6.21
- Affected versionversion=f3cc28c797604fa1cda4aef3f250f465de54a0ca <0f573b0576252d44fb27ab8470ea873bc6408ef3
- Affected versionversion=f3cc28c797604fa1cda4aef3f250f465de54a0ca <43e746821f5f5afbbf68e388bf9fbe221e03bfca
- Affected versionversion=f3cc28c797604fa1cda4aef3f250f465de54a0ca <5d7ac337d37cb97d77e4c910d37746694b606661
- Affected versionversion=f3cc28c797604fa1cda4aef3f250f465de54a0ca <6285919d4c06254d257d24dc980f6332e1984a82
- Affected versionversion=f3cc28c797604fa1cda4aef3f250f465de54a0ca <632cd7b81cb7bab36112f02eb2ee7f7cc1214fb1
- Affected versionversion=f3cc28c797604fa1cda4aef3f250f465de54a0ca <6ab9f61ca851f02ae4398cebaf00735a22e1d6ca
- Affected versionversion=f3cc28c797604fa1cda4aef3f250f465de54a0ca <79e2447b11322c27ef9ac423be0a94efc7691f02
- Affected versionversion=f3cc28c797604fa1cda4aef3f250f465de54a0ca <c55e51d5899e80f9593b26985ed0b89e0c828a5e
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started