CVE-2026-43230

net/rds: Clear reconnect pending bit

HIGH

7.5

CVSS Score

Published: May 6, 2026 at 11:28 AM UTC

Updated: August 5, 2026 at 01:24 PM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.5

Exploit prediction

EPSS 0.5%

Description

In the Linux kernel, the following vulnerability has been resolved: net/rds: Clear reconnect pending bit When canceling the reconnect worker, care must be taken to reset the reconnect-pending bit. If the reconnect worker has not yet been scheduled before it is canceled, the reconnect-pending bit will stay on forever.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

2.6.30 ≤ v < 5.10.2522.6.30 ≤ v < 5.15.2022.6.30 ≤ v < 6.1.1652.6.30 ≤ v < 6.12.752.6.30 ≤ v < 6.18.162.6.30 ≤ v < 6.19.62.6.30 ≤ v < 6.6.1282.6.30 ≤ v < 7.05.11 ≤ v < 5.15.2025.16 ≤ v < 6.1.1656.13 ≤ v < 6.18.166.19 ≤ v < 6.19.66.2 ≤ v < 6.6.1286.7 ≤ v < 6.12.750e0f34c616603ba6500f41943cbf89eb4a8a5be2.6.30

Vendor states this is fixed in 14eae5564053ac3973b9369dc674638f22f4765e (fixed)

Vendor states this is fixed in 391200c274e90c34071b909ba12e3390b81b767f (fixed)

Vendor states this is fixed in 3cf001aff71b1db1b4732a5381b012a114720664 (fixed)

Vendor states this is fixed in 597c46a42930c963f448720aaf5001dd4ed98af4 (fixed)

Vendor states this is fixed in 60b347333ec259ac7352f62cbbc365b04c065ff8 (fixed)

Vendor states this is fixed in b89fc7c2523b2b0750d91840f4e52521270d70ed (fixed)

Vendor states this is fixed in ba2e3472022f44baddf000621fed150d7a599ea3 (fixed)

Vendor states this is fixed in bcf034fa5f66b6a3e787f765a917934a2045cf7a (fixed)

Vendor states this is fixed in 2.6.30 (unaffected)

Vendor states this is fixed in 5.10.252 (unaffected)

Vendor states this is fixed in 5.15.202 (unaffected)

Vendor states this is fixed in 6.1.165 (unaffected)