CVE-2026-89700

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=*, <=6.12.*, 6.12.111, 6.10, <=6.18.*, 6.18.50, <2aca70c18c5f5d06004122861fb151d5fcc57faf, <22d0e4752ca88fd84196d22ebeedc905e6540440, 0, <6.10, <=7.2.*, 7.2.4, <bdcc85c2b05a9378d8bd2d65f9fc41440a3cf464, <bf85a0f1e45258f90ceeec14772b5769697dfd75, 16a471177496c8e04a9793812c187a2c1a2192fa, 7.3

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.

Gravité et risque d'exploitation

CVE-2026-89700 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.17 %, ce qui la place devant 5.7 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=*, <=6.12.*, 6.12.111, 6.10, <=6.18.*, 6.18.50, <2aca70c18c5f5d06004122861fb151d5fcc57faf, <22d0e4752ca88fd84196d22ebeedc905e6540440, 0, <6.10, <=7.2.*, 7.2.4, <bdcc85c2b05a9378d8bd2d65f9fc41440a3cf464, <bf85a0f1e45258f90ceeec14772b5769697dfd75, 16a471177496c8e04a9793812c187a2c1a2192fa, 7.3) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références