CVE-2026-98488 json
net: atl1e: fix soft lockup on out-of-range hw_next_to_clean read
published 24d ago modified 23d ago also EUVD-2026-103728
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
net: atl1e: fix soft lockup on out-of-range hw_next_to_clean read
Same issue as atl1c (see the first commit in this series, "net: atl1c: fix soft lockup on out-of-range tpd_cons read"): the hardware can report an out-of-range hw_next_to_clean (seen as 0xffff) while the PCIe link/MAC is resetting. An out-of-range value can never be reached and the loop below would spin forever. Treat it as "nothing new to clean" instead.
Patch / fix
- Linux Linux 7.3
- linux Debian 12 6.1.190-1
- linux Debian 13 6.12.113-1
- linux Debian 14 7.2.9-1
- linux-6.12 Debian 12 6.12.113-1~deb12u1
debian advisories DEBIAN-CVE-2026-98488
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 24.04 LTS 6.8.0-149.149
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 24.04 LTS 6.8.0-1069.74
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1073.81
ubuntu advisories UBUNTU-CVE-2026-98488
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel Azure Linux 3.0 6.6.159.1-1
azure linux advisories AZL-108692
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/ca862b1a4af7eac19429ca7ab92625f94ff4a46c commit
- git.kernel.org/stable/c/4bbb44075bd3e773d61706882ab923ece8b3b519 commit
- git.kernel.org/stable/c/34bc747a61bef572244b01b095552b629cd8d2a2 commit
- git.kernel.org/stable/c/1d8c85359b5075c7937925b673add7ed00e57ec8 commit
- git.kernel.org/stable/c/a277422d194c62daa1b961f5f739689e53fe7301 commit
- git.kernel.org/stable/c/4b7161804d8f31227551901f93947bb4eea4690b commit
- git.kernel.org/stable/c/3a7d9271b37c80fb7db04aff3bc5621cfdaf9bee commit
- git.kernel.org/stable/c/374bf9e4b90f979e052332c4faca2d745c491a12 commit
Is CVE-2026-98488 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-98488 updated cvss 4.1
kernel: net: atl1e: fix soft lockup on out-of-range hw_next_to_clean read
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/ca862b1a4af7eac19429ca7ab92625f94ff4a46c
- git.kernel.org /stable/c/4bbb44075bd3e773d61706882ab923ece8b3b519
- git.kernel.org /stable/c/34bc747a61bef572244b01b095552b629cd8d2a2
- git.kernel.org /stable/c/1d8c85359b5075c7937925b673add7ed00e57ec8
- git.kernel.org /stable/c/a277422d194c62daa1b961f5f739689e53fe7301
- git.kernel.org /stable/c/4b7161804d8f31227551901f93947bb4eea4690b
- git.kernel.org /stable/c/3a7d9271b37c80fb7db04aff3bc5621cfdaf9bee
- git.kernel.org /stable/c/374bf9e4b90f979e052332c4faca2d745c491a12
Sources
- CVE List CVE-2026-98488
- NVD CVE-2026-98488
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.