Answer in brief
CVE-2026-43226 records a Unknown severity vulnerability in net/rds: No shortcut out of RDS_CONN_ERROR. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-43226 records a Unknown severity vulnerability in net/rds: No shortcut out of RDS_CONN_ERROR. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5916e2c1554f3e36f770401c989c3c7fadf619ca <9bcd7c00691a2db9745817d5ea79262a503b135c || >=5916e2c1554f3e36f770401c989c3c7fadf619ca <a179ac7be8f5a650d0068040705f4cddd6ca369c || >=5916e2c1554f3e36f770401c989c3c7fadf619ca <19e384a7d00d888303a8285977cdf1970c6cccd6 || >=5916e2c1554f3e36f770401c989c3c7fadf619ca <f0f729bdffb08af32e0f54521b81b8a9e0321f16 || >=5916e2c1554f3e36f770401c989c3c7fadf619ca <81248b1eb3c5954cc1fc7b33b7c03e34d20cb8c8 || >=5916e2c1554f3e36f770401c989c3c7fadf619ca <899ef00963ce76f9fc421a7d02335fe4ead6389b || >=5916e2c1554f3e36f770401c989c3c7fadf619ca <9ff599a9be784a808c36765086e3db2144aa3b66 || >=5916e2c1554f3e36f770401c989c3c7fadf619ca <ad22d24be635c6beab6a1fdd3f8b1f3c478d15da | 9bcd7c00691a2db9745817d5ea79262a503b135c, a179ac7be8f5a650d0068040705f4cddd6ca369c, 19e384a7d00d888303a8285977cdf1970c6cccd6, f0f729bdffb08af32e0f54521b81b8a9e0321f16, 81248b1eb3c5954cc1fc7b33b7c03e34d20cb8c8, 899ef00963ce76f9fc421a7d02335fe4ead6389b, 9ff599a9be784a808c36765086e3db2144aa3b66, ad22d24be635c6beab6a1fdd3f8b1f3c478d15da |
| Linux/Linuxgeneric | 4.8 | Not reported |
Published upstream
May 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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."
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5916e2c1554f3e36f770401c989c3c7fadf619ca <9bcd7c00691a2db9745817d5ea79262a503b135c || >=5916e2c1554f3e36f770401c989c3c7fadf619ca <a179ac7be8f5a650d0068040705f4cddd6ca369c || >=5916e2c1554f3e36f770401c989c3c7fadf619ca <19e384a7d00d888303a8285977cdf1970c6cccd6 || >=5916e2c1554f3e36f770401c989c3c7fadf619ca <f0f729bdffb08af32e0f54521b81b8a9e0321f16 || >=5916e2c1554f3e36f770401c989c3c7fadf619ca <81248b1eb3c5954cc1fc7b33b7c03e34d20cb8c8 || >=5916e2c1554f3e36f770401c989c3c7fadf619ca <899ef00963ce76f9fc421a7d02335fe4ead6389b || >=5916e2c1554f3e36f770401c989c3c7fadf619ca <9ff599a9be784a808c36765086e3db2144aa3b66 || >=5916e2c1554f3e36f770401c989c3c7fadf619ca <ad22d24be635c6beab6a1fdd3f8b1f3c478d15da | 9bcd7c00691a2db9745817d5ea79262a503b135c, a179ac7be8f5a650d0068040705f4cddd6ca369c, 19e384a7d00d888303a8285977cdf1970c6cccd6, f0f729bdffb08af32e0f54521b81b8a9e0321f16, 81248b1eb3c5954cc1fc7b33b7c03e34d20cb8c8, 899ef00963ce76f9fc421a7d02335fe4ead6389b, 9ff599a9be784a808c36765086e3db2144aa3b66, ad22d24be635c6beab6a1fdd3f8b1f3c478d15da |
| Linux/Linuxgeneric | 4.8 | Not reported |
Published upstream
May 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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."
Quoted source text, attributed separately from HOL analysis.