GHSA-C543-5M5V-X4WF
Vulnerability from github – Published: 2026-09-25 12:31 – Updated: 2026-09-25 12:31In 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.
{
"affected": [],
"aliases": [
"CVE-2026-97565"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-25T11:17:07Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: reject short READ responses in CIFSSMBRead()\n\nCIFSSMBRead() reads DataLengthHigh, DataLength and DataOffset out of\nthe READ_RSP returned by the server without first checking that a\nwhole READ_RSP was actually received. The length of the response is\nrecorded in rsp_iov.iov_len, but nothing constrains it to be at least\nread_rsp_size before those fields are dereferenced.\n\nA malicious or compromised SMB1 server can return a response shorter\nthan the READ_RSP header, so that parsing the header itself reads past\nthe end of the receive buffer. SMB1 is not negotiated by default;\nreaching this code requires an explicit vers=1.0 mount.\n\nReject the response unless it is at least read_rsp_size bytes long.",
"id": "GHSA-c543-5m5v-x4wf",
"modified": "2026-09-25T12:31:24Z",
"published": "2026-09-25T12:31:24Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-97565"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0f1f77b821506a4dacab6ce7d29cf9e0c26f14cd"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/aaa221c1b1d288845b55e9c366e5ef608dfff49d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e6142a8bfc230c7263eb8b0475249c958ce49367"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.