High 7.5Published May 6, 2026

CVE-2026-43226net/rds: No shortcut out of RDS_CONN_ERROR

Updated under an hour ago (Oct 28, 2026, 2:30 AM ET)

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

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."

CVSS: 7.5 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE): Not given
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Analyzed
Record last updated: Aug 5, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	5916e2c1554f3e36f770401c989c3c7fadf619ca builds before 9bcd7c00691a2db9745817d5ea79262a503b135c; from 5916e2c1554f3e36f770401c989c3c7fadf619ca before a179ac7be8f5a650d0068040705f4cddd6ca369c; 5916e2c1554f3e36f770401c989c3c7fadf619ca builds before 19e384a7d00d888303a8285977cdf1970c6cccd6; from 5916e2c1554f3e36f770401c989c3c7fadf619ca before f0f729bdffb08af32e0f54521b81b8a9e0321f16; from 5916e2c1554f3e36f770401c989c3c7fadf619ca before 81248b1eb3c5954cc1fc7b33b7c03e34d20cb8c8; 5916e2c1554f3e36f770401c989c3c7fadf619ca builds before 899ef00963ce76f9fc421a7d02335fe4ead6389b; 5916e2c1554f3e36f770401c989c3c7fadf619ca builds before 9ff599a9be784a808c36765086e3db2144aa3b66; from 5916e2c1554f3e36f770401c989c3c7fadf619ca before ad22d24be635c6beab6a1fdd3f8b1f3c478d15da	CNA record
linux linux_kernel linux:linux_kernel	from 4.8 before 5.10.252; from 5.11 before 5.15.202; from 5.16 before 6.1.165; from 6.2 before 6.6.128; from 6.7 before 6.12.75; from 6.13 before 6.18.16; from 6.19 before 6.19.6	NVD

References

References

https://git.kernel.org/stable/c/9bcd7c00691a2db9745817d5ea79262a503b135c	patch
https://git.kernel.org/stable/c/a179ac7be8f5a650d0068040705f4cddd6ca369c	patch
https://git.kernel.org/stable/c/19e384a7d00d888303a8285977cdf1970c6cccd6	patch
https://git.kernel.org/stable/c/f0f729bdffb08af32e0f54521b81b8a9e0321f16	patch
https://git.kernel.org/stable/c/81248b1eb3c5954cc1fc7b33b7c03e34d20cb8c8	patch
https://git.kernel.org/stable/c/899ef00963ce76f9fc421a7d02335fe4ead6389b	patch
https://git.kernel.org/stable/c/9ff599a9be784a808c36765086e3db2144aa3b66	patch
https://git.kernel.org/stable/c/ad22d24be635c6beab6a1fdd3f8b1f3c478d15da	patch

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.