CVE-2026-99352
What it is
In the Linux kernel, the following vulnerability has been resolved: SUNRPC: trace an accepted transport before publishing it svc_handle_xprt() publishes a newly accepted transport before tracing it. svc_add_new_temp_xprt() places the transport on sv_tempsocks and clears XPT_BUSY, so another nfsd thread can dequeue it at once. If the peer has already closed the connection, that thread runs svc_delete_xprt(), which drops the list reference, the only reference the new transport holds. trace_svc_xprt_accept() then reads the transport's addresses and network namespace from freed memory. Before publication the accepting thread owns the transport exclusively: XPT_BUSY is still set from svc_xprt_init() and the transport is on no list. Emit the tracepoint there. [ cel: trace before publication instead of taking an extra reference ]
At a glance
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: not scored yet.
- Severity: not scored yet.
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Record status
- Received
Affected
- Linux < 4d20ecd289ede2487ee5a23962fa78fcb47c0500
- Linux < fd7b12865b2078f16406834631c4a68262d28346
- Linux < 86f3078ed2bd6645f5d44fa41917453b774808c1
- Linux < 06f90cf104fc21ee01e7ef1eb80e092173089b9f
- Linux 5.8
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-99352.md and follow it. Check whether this project is affected by CVE-2026-99352. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.