Skip to main content
VulnerabilityPublished

CVE-2026-99359: Linux kernel · NFSD: validate transport name in listener_set before serv creation

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in f5a336ad931afdd609c809cea4b3d910e781bd6f : update Linux kernel when convenient.

Data as of 19 Nov 2026, 14:34 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in f5a336ad931afdd609c809cea4b3d910e781bd6f, 90202cf720f47d4183b4da8ef43bed7dfec0c572, 421becdc5cf4d7d2fbda393e78ca76d25d277c0f +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade Linux kernel to f5a336ad931afdd609c809cea4b3d910e781bd6f, 90202cf720f47d4183b4da8ef43bed7dfec0c572, 421becdc5cf4d7d2fbda393e78ca76d25d277c0f or 49f6570e1a8989268cfb71448e3d301c5c850c2d.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 16a471177496c8e04a9793812c187a2c1a2192fa, < f5a336ad931afdd609c809cea4b3d910e781bd6f
Fixed in
  • f5a336ad931afdd609c809cea4b3d910e781bd6f
LinuxLinuxAffected
  • ≥ 16a471177496c8e04a9793812c187a2c1a2192fa, < 90202cf720f47d4183b4da8ef43bed7dfec0c572
Fixed in
  • 90202cf720f47d4183b4da8ef43bed7dfec0c572
LinuxLinuxAffected
  • ≥ 16a471177496c8e04a9793812c187a2c1a2192fa, < 421becdc5cf4d7d2fbda393e78ca76d25d277c0f
Fixed in
  • 421becdc5cf4d7d2fbda393e78ca76d25d277c0f
LinuxLinuxAffected
  • ≥ 16a471177496c8e04a9793812c187a2c1a2192fa, < 49f6570e1a8989268cfb71448e3d301c5c850c2d
Fixed in
  • 49f6570e1a8989268cfb71448e3d301c5c850c2d
LinuxLinuxAffected
  • =6.10
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: NFSD: validate transport name in listener_set before serv creation nfsd_nl_listener_set_doit() holds nfsd_mutex for the whole listener teardown and rebuild. The code checks NFSD_A_SOCK_TRANSPORT_NAME for presence only, and not for content. An arbitrary name therefore reaches svc_xprt_create_from_sa(). There, a name that matches no registered class calls request_module("svc%s", name). That call is a TASK_KILLABLE usermode helper upcall, and it runs under nfsd_mutex. Check the name against the classes that NFSD can create: tcp, udp and rdma. The check goes in nfsd_nl_validate_listeners(), which runs before the code takes nfsd_mutex. The rejection names the offending attribute through extack, since -EPROTONOSUPPORT on its own does not say which entry carried the bad name. This narrows the upcall. It does not remove it. NFSD accepts "rdma" without a condition, so on a kernel that does not build svcrdma the name still reaches request_module("svcrdma") under nfsd_mutex. That is necessary for the modular case, where the autoload is legitimate.

References

Community reviews

Loading reviews…