Linux
sunrpc: xprtsock: annotate shared socket callbacks with READ_ONCE/WRITE_ONCE
In the Linux kernel, the following vulnerability has been resolved: sunrpc: xprtsock: annotate shared socket callbacks with READ_ONCE/WRITE_ONCE xprtsock replaces and restores sk->sk_data_ready and sk->sk_write_space on live sockets with plain stores, and xs_udp_do_set_buffer_size() invokes sk->sk_write_space via a plain load. These callback pointers are shared with generic socket and protocol paths that may read or invoke them concurrently, so xprtsock needs the same READ_ONCE()/WRITE_ONCE() callback visibility contract that the validated 4022 family applied elsewhere. When SUNRPC takes over an AF_LOCAL, UDP, or TCP socket and later restores the lower-socket callbacks during teardown, another CPU may still hold an earlier callback snapshot. The plain replace/restore pattern leaves the same visibility hole as the validated 4022 family, so a stale snapshot can still invoke xs_data_ready() or xs_udp_write_space() after the live callback fields have already been restored to the lower-socket handlers. Use WRITE_ONCE() for the shared sk_data_ready and sk_write_space stores in xs_local_finish_connecting(), xs_udp_finish_connecting(), xs_tcp_finish_connecting(), and xs_restore_old_callbacks(). Use READ_ONCE() for the direct sk_write_space invocation in xs_udp_do_set_buffer_size(). This matches the required callback visibility contract while leaving adjacent sk_state_change and sk_error_report handling unchanged.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= a246b0105bbd9a70a698f69baae2042996f2a0e9, < 6b79b5a0f1c566f0aa6e08c7981826015a0acc4d
- >= a246b0105bbd9a70a698f69baae2042996f2a0e9, < ed80d009b154aa204f541d390884851b3d4f15ae
- >= a246b0105bbd9a70a698f69baae2042996f2a0e9, < 589f761236e05ff9de1bdfd6a5258f113e6457fe
- >= a246b0105bbd9a70a698f69baae2042996f2a0e9, < da652cb17f9faeea1fa44b7215e8869a0b10b664
- >= a246b0105bbd9a70a698f69baae2042996f2a0e9, < d8f0b83753809761a560c4b33249388548ba6e43
- >= a246b0105bbd9a70a698f69baae2042996f2a0e9, < 33930840b5f0a79f826e7c69dc6cd78f72a67481
Fixed in 6b79b5a0f1c566f0aa6e08c7981826015a0acc4d, ed80d009b154aa204f541d390884851b3d4f15ae, 589f761236e05ff9de1bdfd6a5258f113e6457fe, da652cb17f9faeea1fa44b7215e8869a0b10b664, d8f0b83753809761a560c4b33249388548ba6e43, 33930840b5f0a79f826e7c69dc6cd78f72a67481
- 2.6.15
Fixed in 0, 6.1.191, 6.6.157, 6.12.110, 6.18.52, 7.2.6, 7.3
Mitigation
Upgrade Linux to 6b79b5a0f1c566f0aa6e08c7981826015a0acc4d or ed80d009b154aa204f541d390884851b3d4f15ae or 589f761236e05ff9de1bdfd6a5258f113e6457fe or da652cb17f9faeea1fa44b7215e8869a0b10b664 or d8f0b83753809761a560c4b33249388548ba6e43 or 33930840b5f0a79f826e7c69dc6cd78f72a67481 or later.
Upgrade Linux to 0 or 6.1.191 or 6.6.157 or 6.12.110 or 6.18.52 or 7.2.6 or 7.3 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.