CPU hang via unchecked transmit-consumer index
Published Oct 18, 2026 · Updated Oct 18, 2026
An infinite loop in Linux's atl1e driver allows attackers to hang a CPU when a PCIe link or MAC reset yields an invalid index. The atl1e_clean_tx_irq routine reads hw_next_to_clean without checking the transmit-ring bounds, then loops toward a value the software index cannot reach. Affected systems must use the Atheros L1E Ethernet driver; attacker control over the reset is not established, and the documented consequence is a CPU soft lockup.
Summary
What happened
An infinite loop in Linux's atl1e driver allows attackers to hang a CPU when a PCIe link or MAC reset yields an invalid index. The atl1e_clean_tx_irq routine reads hw_next_to_clean without checking the transmit-ring bounds, then loops toward a value the software index cannot reach. Affected systems must use the Atheros L1E Ethernet driver; attacker control over the reset is not established, and the documented consequence is a CPU soft lockup.
The record
- CVE
- CVE-2026-98488
- 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.27
- Affected versionversion=a6a5325239c20202e18e21e94291bccc659fbf9e <1d8c85359b5075c7937925b673add7ed00e57ec8
- Affected versionversion=a6a5325239c20202e18e21e94291bccc659fbf9e <34bc747a61bef572244b01b095552b629cd8d2a2
- Affected versionversion=a6a5325239c20202e18e21e94291bccc659fbf9e <374bf9e4b90f979e052332c4faca2d745c491a12
- Affected versionversion=a6a5325239c20202e18e21e94291bccc659fbf9e <3a7d9271b37c80fb7db04aff3bc5621cfdaf9bee
- Affected versionversion=a6a5325239c20202e18e21e94291bccc659fbf9e <4b7161804d8f31227551901f93947bb4eea4690b
- Affected versionversion=a6a5325239c20202e18e21e94291bccc659fbf9e <4bbb44075bd3e773d61706882ab923ece8b3b519
- Affected versionversion=a6a5325239c20202e18e21e94291bccc659fbf9e <a277422d194c62daa1b961f5f739689e53fe7301
- Affected versionversion=a6a5325239c20202e18e21e94291bccc659fbf9e <ca862b1a4af7eac19429ca7ab92625f94ff4a46c
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