# CVE-2026-98901: ksmbd: fix lease break and ack state handling


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** AZL-110659, BELL-CVE-2026-98901, DEBIAN-CVE-2026-98901, GHSA-6w2x-j37m-r6r9, UBUNTU-CVE-2026-98901

## What is CVE-2026-98901?

CVE-2026-98901 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official description

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

ksmbd: fix lease break and ack state handling

Do not skip valid lease states containing WRITE_CACHING when breaking
level-II/read leases for writes and truncates.

Handle lease break acknowledgments according to the SMB2 rule that the
acknowledged state must be a subset of the server's break target. Apply
the acknowledged state directly and keep the break pending on failed ACKs.

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


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

Upgrade to a fixed version.

## Is CVE-2026-98901 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98901 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-98901 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-98901/ (Markdown: https://insights.sbomify.com/CVE-2026-98901/index.md)
```

## Sources

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

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