Heimdall Security Logo

CVE-2026-43226

Vulnérabilité élevée dans Linux (Linux)

CVSS 7.5 · Élevée
EPSS 0.7%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, <19e384a7d00d888303a8285977cdf1970c6cccd6, <81248b1eb3c5954cc1fc7b33b7c03e34d20cb8c8, <a179ac7be8f5a650d0068040705f4cddd6ca369c, 0, 7.0, 6.1.165, 6.12.75, <=5.10.*, <=6.6.*, <=6.19.*, <9bcd7c00691a2db9745817d5ea79262a503b135c, 5916e2c1554f3e36f770401c989c3c7fadf619ca, <899ef00963ce76f9fc421a7d02335fe4ead6389b, <9ff599a9be784a808c36765086e3db2144aa3b66, <=6.18.*, 6.19.6, 6.6.128, 5.10.252, 4.8, 6.18.16, <=*, <=5.15.*, <4.8, <f0f729bdffb08af32e0f54521b81b8a9e0321f16, 5.15.202, <ad22d24be635c6beab6a1fdd3f8b1f3c478d15da

Description

In the Linux kernel, the following vulnerability has been resolved: net/rds: No shortcut out of RDS_CONN_ERROR RDS connections carry a state "rds_conn_path::cp_state" and transitions from one state to another and are conditional upon an expected state: "rds_conn_path_transition." There is one exception to this conditionality, which is "RDS_CONN_ERROR" that can be enforced by "rds_conn_path_drop" regardless of what state the condition is currently in. But as soon as a connection enters state "RDS_CONN_ERROR", the connection handling code expects it to go through the shutdown-path. The RDS/TCP multipath changes added a shortcut out of "RDS_CONN_ERROR" straight back to "RDS_CONN_CONNECTING" via "rds_tcp_accept_one_path" (e.g. after "rds_tcp_state_change"). A subsequent "rds_tcp_reset_callbacks" can then transition the state to "RDS_CONN_RESETTING" with a shutdown-worker queued. That'll trip up "rds_conn_init_shutdown", which was never adjusted to handle "RDS_CONN_RESETTING" and subsequently drops the connection with the dreaded "DR_INV_CONN_STATE", which leaves "RDS_SHUTDOWN_WORK_QUEUED" on forever. So we do two things here: a) Don't shortcut "RDS_CONN_ERROR", but take the longer path through the shutdown code. b) Add "RDS_CONN_RESETTING" to the expected states in "rds_conn_init_shutdown" so that we won't error out and get stuck, if we ever hit weird state transitions like this again."

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, <19e384a7d00d888303a8285977cdf1970c6cccd6, <81248b1eb3c5954cc1fc7b33b7c03e34d20cb8c8, <a179ac7be8f5a650d0068040705f4cddd6ca369c, 0, 7.0, 6.1.165, 6.12.75, <=5.10.*, <=6.6.*, <=6.19.*, <9bcd7c00691a2db9745817d5ea79262a503b135c, 5916e2c1554f3e36f770401c989c3c7fadf619ca, <899ef00963ce76f9fc421a7d02335fe4ead6389b, <9ff599a9be784a808c36765086e3db2144aa3b66, <=6.18.*, 6.19.6, 6.6.128, 5.10.252, 4.8, 6.18.16, <=*, <=5.15.*, <4.8, <f0f729bdffb08af32e0f54521b81b8a9e0321f16, 5.15.202, <ad22d24be635c6beab6a1fdd3f8b1f3c478d15da) 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

Rechercher une autre CVE