CVE-2026-90235

Vulnérabilité critique dans Linux (Linux)

CVSS 9.8 · Critique
EPSS 0.6%
Linux•Linux•Versions : <=6.12.*, 0, 6.18.52, <d8f0b83753809761a560c4b33249388548ba6e43, <589f761236e05ff9de1bdfd6a5258f113e6457fe, <=6.6.*, 6.6.157, a246b0105bbd9a70a698f69baae2042996f2a0e9, <da652cb17f9faeea1fa44b7215e8869a0b10b664, 7.2.6, <2.6.15, <=6.18.*, <=7.2.*, 6.12.110, 2.6.15, <=*, <ed80d009b154aa204f541d390884851b3d4f15ae, <33930840b5f0a79f826e7c69dc6cd78f72a67481, 7.3

Description

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.

Gravité et risque d'exploitation

CVE-2026-90235 obtient un score CVSS de 9.8/10, soit une gravité critique. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.62 %, ce qui la place devant 48.6 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.12.*, 0, 6.18.52, <d8f0b83753809761a560c4b33249388548ba6e43, <589f761236e05ff9de1bdfd6a5258f113e6457fe, <=6.6.*, 6.6.157, a246b0105bbd9a70a698f69baae2042996f2a0e9, <da652cb17f9faeea1fa44b7215e8869a0b10b664, 7.2.6, <2.6.15, <=6.18.*, <=7.2.*, 6.12.110, 2.6.15, <=*, <ed80d009b154aa204f541d390884851b3d4f15ae, <33930840b5f0a79f826e7c69dc6cd78f72a67481, 7.3) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références