# CVE-2026-97565: smb: client: reject short READ responses in CIFSSMBRead()

> A malicious SMB1 server can trigger a buffer over-read in the Linux kernel SMB client, potentially causing a crash or code execution.

- **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:** 25 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-104462, BELL-CVE-2026-97565, DEBIAN-CVE-2026-97565, GHSA-c543-5m5v-x4wf, UBUNTU-CVE-2026-97565

## What is CVE-2026-97565?

CVE-2026-97565 is a memory corruption vulnerability in Linux, published on 25 Sep 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:

smb: client: reject short READ responses in CIFSSMBRead()

CIFSSMBRead() reads DataLengthHigh, DataLength and DataOffset out of
the READ_RSP returned by the server without first checking that a
whole READ_RSP was actually received. The length of the response is
recorded in rsp_iov.iov_len, but nothing constrains it to be at least
read_rsp_size before those fields are dereferenced.

A malicious or compromised SMB1 server can return a response shorter
than the READ_RSP header, so that parsing the header itself reads past
the end of the receive buffer. SMB1 is not negotiated by default;
reaching this code requires an explicit vers=1.0 mount.

Reject the response unless it is at least read_rsp_size bytes long.

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


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

Apply the vendor's patch.

## Is CVE-2026-97565 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97565 is a memory corruption vulnerability in Linux, published on 25 Sep 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-97565 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-97565/ (Markdown: https://insights.sbomify.com/CVE-2026-97565/index.md)
```

## Sources

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

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