CVE-2026-98488: Linux kernel · net: atl1e: fix soft lockup on out-of-range hw_next_to_clean read
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ca862b1a4af7eac19429ca7ab92625f94ff4a46c : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:16 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in ca862b1a4af7eac19429ca7ab92625f94ff4a46c, a277422d194c62daa1b961f5f739689e53fe7301, 374bf9e4b90f979e052332c4faca2d745c491a12 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
The issue has been fixed in multiple Linux kernel commits. Users should apply the official patches or update to a Linux kernel version that includes these fixes. No additional mitigation is required once the fix is applied.
Description
A vulnerability in the Linux kernel's atl1e network driver could cause a soft lockup due to an out-of-range hardware pointer read during PCIe link or MAC reset. This issue results from the hardware reporting an invalid hw_next_to_clean value, causing an infinite loop in the driver code. The problem has been fixed in several commits.
References
- git.kernel.org/stable/c/ca862b1a4af7eac19429ca7ab92625f94ff4a46c (opens in a new tab)
- git.kernel.org/stable/c/4bbb44075bd3e773d61706882ab923ece8b3b519 (opens in a new tab)
- git.kernel.org/stable/c/34bc747a61bef572244b01b095552b629cd8d2a2 (opens in a new tab)
- git.kernel.org/stable/c/1d8c85359b5075c7937925b673add7ed00e57ec8 (opens in a new tab)
- git.kernel.org/stable/c/a277422d194c62daa1b961f5f739689e53fe7301 (opens in a new tab)
- git.kernel.org/stable/c/4b7161804d8f31227551901f93947bb4eea4690b (opens in a new tab)
- git.kernel.org/stable/c/3a7d9271b37c80fb7db04aff3bc5621cfdaf9bee (opens in a new tab)
- git.kernel.org/stable/c/374bf9e4b90f979e052332c4faca2d745c491a12 (opens in a new tab)