CVE-2026-99353
Severity unknownNo known exploitationFix availableSUNRPC: Reject a socket that already has an svc_sock attached
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 10% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
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.
Patching and mitigation
- Patch status
- Fix available (source: CVE record (Linux))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from b41b66d63c730cc45a1024e1f1e67439e507e40f before f44daa50489fede01012c575d9f5e7b11a212fe4 | f44daa50489fede01012c575d9f5e7b11a212fe4 | CVE Program |
| Linux | Linux | from b41b66d63c730cc45a1024e1f1e67439e507e40f before 0995447b8059c4d23853cdcddbe789c4a2b6bb88 | 0995447b8059c4d23853cdcddbe789c4a2b6bb88 | CVE Program |
| Linux | Linux | from b41b66d63c730cc45a1024e1f1e67439e507e40f before 42923e0fc817a7e78d1a5e7cb82966d27919e332 | 42923e0fc817a7e78d1a5e7cb82966d27919e332 | CVE Program |
| Linux | Linux | from b41b66d63c730cc45a1024e1f1e67439e507e40f before 514ce838b4f26780fa31da7d7f1e30d696ea6a9e | 514ce838b4f26780fa31da7d7f1e30d696ea6a9e | CVE Program |
| Linux | Linux | 2.6.19 | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.12.117 up to and including 6.12.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.18.61 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.3.2 up to and including 7.3.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.4-rc1 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 2.6.19 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (Linux)
Vendor guidance and references
- https://git.kernel.org/stable/c/0995447b8059c4d23853cdcddbe789c4a2b6bb88 (opens in a new tab)
- https://git.kernel.org/stable/c/42923e0fc817a7e78d1a5e7cb82966d27919e332 (opens in a new tab)
- https://git.kernel.org/stable/c/514ce838b4f26780fa31da7d7f1e30d696ea6a9e (opens in a new tab)
- https://git.kernel.org/stable/c/f44daa50489fede01012c575d9f5e7b11a212fe4 (opens in a new tab)