# CVE-2026-98494: net: atl1: fix soft lockup on out-of-range cmb_tpd_next_to_clean read

> A local attacker can cause a system hang in the atl1 network driver by triggering a soft lockup during hardware reset conditions.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-108857, BELL-CVE-2026-98494, DEBIAN-CVE-2026-98494, GHSA-9q2h-qvmx-46mv, UBUNTU-CVE-2026-98494

## What is CVE-2026-98494?

CVE-2026-98494 is a denial of service vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

net: atl1: fix soft lockup on out-of-range cmb_tpd_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 cmb_tpd_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.

## Which versions are affected by CVE-2026-98494?


## How do I fix CVE-2026-98494?

Apply the vendor's patch.

## Is CVE-2026-98494 being exploited?

There is no known exploitation of CVE-2026-98494 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98494 and fix it if it is affected.

What it is: CVE-2026-98494 is a denial of service vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98494 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98494/ (Markdown: https://insights.sbomify.com/CVE-2026-98494/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98494
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98494
- OSV: https://osv.dev/vulnerability/CVE-2026-98494

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98494/
Summaries are generated and may contain mistakes; the official description above is the record.