GHSA-GGMC-FHXW-V94J
Vulnerability from github – Published: 2026-09-11 21:31 – Updated: 2026-09-13 09:32In the Linux kernel, the following vulnerability has been resolved:
misc: nsm: bound the device-reported response length
nsm_sendrecv_msg_locked() stores the virtqueue used-ring length reported by the NSM device into msg->resp.len without bounding it to the response buffer. A malicious or buggy backend can report a length larger than the response buffer; parse_resp_raw() then copies that many bytes out of the fixed buffer to user space, disclosing adjacent kernel heap (an out-of-bounds read). The request path already floors its length in fill_req_raw(); the response path lacks the symmetric check.
Clamp the stored length to the size of the response buffer. Well-behaved devices report no more than the posted buffer size, so conforming traffic is unaffected.
{
"affected": [],
"aliases": [
"CVE-2026-89743"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-11T20:20:04Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmisc: nsm: bound the device-reported response length\n\nnsm_sendrecv_msg_locked() stores the virtqueue used-ring length reported\nby the NSM device into msg-\u003eresp.len without bounding it to the response\nbuffer. A malicious or buggy backend can report a length larger than the\nresponse buffer; parse_resp_raw() then copies that many bytes out of the\nfixed buffer to user space, disclosing adjacent kernel heap (an\nout-of-bounds read). The request path already floors its length in\nfill_req_raw(); the response path lacks the symmetric check.\n\nClamp the stored length to the size of the response buffer. Well-behaved\ndevices report no more than the posted buffer size, so conforming traffic\nis unaffected.",
"id": "GHSA-ggmc-fhxw-v94j",
"modified": "2026-09-13T09:32:29Z",
"published": "2026-09-11T21:31:39Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89743"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/29e634a18957acda11383a15ab98a91c4ae9e294"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2aa0fb9c96f894a9c179a48e7522ea6705800adf"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/339f19b9a6171289b0e797deb8bda80b9a1fcc30"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/808e530654a5354e6df78863a5d61e4d44e67235"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H",
"type": "CVSS_V3"
}
]
}
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.