CVE-2026-43226: net/rds: No shortcut out of RDS_CONN_ERROR
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."
Security readout for executives and security teams
Plain-English summary
A Linux kernel flaw in RDS/TCP connection handling can leave failed connections stuck during shutdown. A remote, unauthenticated trigger is reflected in the supplied CVSS assessment, and the documented impact is service availability rather than data theft or modification. Exposure depends on whether affected systems use reachable RDS/TCP functionality.
Executive priority
Treat this as an expedited availability-risk update for exposed or business-critical RDS deployments. Systems not using RDS/TCP are lower priority after verification. Because active exploitation is not established and affected-version data is ambiguous, prioritize using confirmed feature usage, network reachability, vendor package status, and service criticality.
Technical view
RDS/TCP multipath can transition a connection directly from RDS_CONN_ERROR to RDS_CONN_CONNECTING. Later callback reset processing may enter RDS_CONN_RESETTING while shutdown work is queued. The shutdown handler rejects that state, drops the connection, and can leave RDS_SHUTDOWN_WORK_QUEUED set indefinitely. The kernel fixes enforce the shutdown path and accept RESETTING during shutdown initialization.
Likely exposure
The supplied assessment rates exploitation as network-based, low-complexity, unauthenticated, and requiring no user interaction. Practical exposure is greatest on affected Linux systems using RDS over TCP, particularly multipath, where relevant connectivity is reachable. The bundle's version data is irregular, so distribution-specific kernel status should be verified rather than inferred solely from version numbers.
Exploitation context
The bundle does not report known active exploitation, and CVE-2026-43226 is not marked as CISA KEV. It provides no public proof-of-concept evidence. The high rating comes from potential remotely triggered availability loss, not demonstrated attacks. Real-world exploitability remains dependent on RDS/TCP deployment and reachability.
Researcher notes
The vulnerable path involves an unexpected state-machine sequence and permanently queued shutdown work, suggesting connection handling or service degradation rather than confidentiality or integrity compromise. The bundle lists duplicated commit identifiers, unusual version entries, and conflicting default-status groupings. Researchers should rely on vendor backport records and cited stable commits for exact build applicability.
Mitigation direction
Apply a vendor-supported kernel update containing the applicable cited stable fix.
Confirm the distribution advisory maps its packaged kernel to CVE-2026-43226.
Prioritize reachable systems actively using RDS over TCP or multipath.
If patching is delayed, consult the vendor for supported mitigations; the bundle names none.
Validation and detection
Inventory kernel versions and identify systems where RDS networking is enabled or used.
Determine whether RDS/TCP and multipath connectivity is reachable from untrusted networks.
Check vendor advisories or changelogs for CVE-2026-43226 or the cited fix commits.
After updating, confirm the running kernel includes the fix and dependent RDS services operate normally.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-43226 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
9Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.