CVE-2026-99353: SUNRPC: Reject a socket that already has an svc_sock attached

Published Nov 19, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

SUNRPC: Reject a socket that already has an svcsock attached

Writing the same socket descriptor to /proc/fs/nfsd/portlist twice attaches a second svcsock to one socket. svcsetupsocket() saves the socket's callbacks before installing its own, so the second attach records svcwritespace() as the old writespace callback. svcudpinit() invokes that callback by way of svcsocksetbufsize(), and svcwritespace() then calls itself until the kernel stack is exhausted:

BUG: TASK stack guard page was hit at ffffc900037d7ff8 svcwritespace+0x90/0x2b0 net/sunrpc/svcsock.c:429 svcwritespace+0xe6/0x2b0 net/sunrpc/svcsock.c:430 ... 700 more ... svcsocksetbufsize+0x18d/0x220 net/sunrpc/svcsock.c:386 svcudpinit net/sunrpc/svcsock.c:854 [inline] svcsetupsocket+0xb2f/0x1090 net/sunrpc/svcsock.c:1498 svcaddsock+0x2fd/0x760 net/sunrpc/svcsock.c:1547 writeportsaddfd fs/nfsd/nfsctl.c:742 [inline] writeports+0xa5b/0xcc0 fs/nfsd/nfsctl.c:861 nfsctltransactionwrite+0x106/0x1a0 fs/nfsd/nfsctl.c:112

svcdataready() and svctcpstatechange() 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 FSUSERNSMOUNT, so the reproducer needs CAPSYSADMIN in the initial user namespace.

Reject a socket that already carries skuserdata. svcsetupsocket() overwrites that field unconditionally, so a socket some other consumer has claimed is one NFSD would corrupt whether or not the callbacks recurse.

Affected Software

3 affected componentsFixes available
linux/kernel>=2.6.19<6.12.117
6.12.117
linux/kernel>=6.13.0<6.18.61
6.18.61
linux/kernel>=6.19.0<7.3.2
7.3.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.117
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.61
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.2

Event History

Nov 19, 2026
CVE Published
via MITRE·02:22 PM
Data Sourced
via MITRE·02:22 PM
Description
Data Sourced
via OSV·02:22 PM
DescriptionAffected Software
Data Sourced
via NVD·03:17 PM
Description

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203