CVE-2026-99353: Linux kernel · SUNRPC: Reject a socket that already has an svc_sock attached
Source GCVE Database
Not known to be exploited · fixed in f44daa50489fede01012c575d9f5e7b11a212fe4 : patch Linux kernel soon.
Data as of 19 Nov 2026, 16:20 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in f44daa50489fede01012c575d9f5e7b11a212fe4, 0995447b8059c4d23853cdcddbe789c4a2b6bb88, 42923e0fc817a7e78d1a5e7cb82966d27919e332 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 f44daa50489fede01012c575d9f5e7b11a212fe4, 0995447b8059c4d23853cdcddbe789c4a2b6bb88, 42923e0fc817a7e78d1a5e7cb82966d27919e332 or 514ce838b4f26780fa31da7d7f1e30d696ea6a9e.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: SUNRPC: Reject a socket that already has an svc_sock attached Writing the same socket descriptor to /proc/fs/nfsd/portlist twice attaches a second svc_sock to one socket. svc_setup_socket() saves the socket's callbacks before installing its own, so the second attach records svc_write_space() as the old write_space callback. svc_udp_init() invokes that callback by way of svc_sock_setbufsize(), and svc_write_space() then calls itself until the kernel stack is exhausted: BUG: TASK stack guard page was hit at ffffc900037d7ff8 svc_write_space+0x90/0x2b0 net/sunrpc/svcsock.c:429 svc_write_space+0xe6/0x2b0 net/sunrpc/svcsock.c:430 ... 700 more ... svc_sock_setbufsize+0x18d/0x220 net/sunrpc/svcsock.c:386 svc_udp_init net/sunrpc/svcsock.c:854 [inline] svc_setup_socket+0xb2f/0x1090 net/sunrpc/svcsock.c:1498 svc_addsock+0x2fd/0x760 net/sunrpc/svcsock.c:1547 __write_ports_addfd fs/nfsd/nfsctl.c:742 [inline] write_ports+0xa5b/0xcc0 fs/nfsd/nfsctl.c:861 nfsctl_transaction_write+0x106/0x1a0 fs/nfsd/nfsctl.c:112 svc_data_ready() and svc_tcp_state_change() chain through their saved callbacks the same way, so a TCP descriptor added twice recurses on the next incoming segment instead. Reaching any of this takes a writer on portlist, and the nfsd filesystem sets no FS_USERNS_MOUNT, so the reproducer needs CAP_SYS_ADMIN in the initial user namespace. Reject a socket that already carries sk_user_data. svc_setup_socket() overwrites that field unconditionally, so a socket some other consumer has claimed is one NFSD would corrupt whether or not the callbacks recurse.
References
- nvd.nist.gov/vuln/detail/CVE-2026-99353 (opens in a new tab)
- git.kernel.org/stable/c/0995447b8059c4d23853cdcddbe789c4a2b6bb88 (opens in a new tab)
- git.kernel.org/stable/c/42923e0fc817a7e78d1a5e7cb82966d27919e332 (opens in a new tab)
- git.kernel.org/stable/c/514ce838b4f26780fa31da7d7f1e30d696ea6a9e (opens in a new tab)
- git.kernel.org/stable/c/f44daa50489fede01012c575d9f5e7b11a212fe4 (opens in a new tab)