Skip to main content
VulnerabilityPublished Updated

CVE-2026-98071: Linux kernel · net/rds: clear cp_flags bits individually in rds_conn_path_reset()

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in ed3ee0ac4aafda50c2f4381eb973beefeb7879ac : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in ed3ee0ac4aafda50c2f4381eb973beefeb7879ac, cb62aa8f04655a4df487913949719c0a1266ed73, c9a7c1eb0ad41dcf004a9e870e452cafedcd9172 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 00e0f34c616603ba6500f41943cbf89eb4a8a5be, < ed3ee0ac4aafda50c2f4381eb973beefeb7879ac
Fixed in
  • ed3ee0ac4aafda50c2f4381eb973beefeb7879ac
LinuxLinuxAffected
  • ≥ 00e0f34c616603ba6500f41943cbf89eb4a8a5be, < cb62aa8f04655a4df487913949719c0a1266ed73
Fixed in
  • cb62aa8f04655a4df487913949719c0a1266ed73
LinuxLinuxAffected
  • ≥ 00e0f34c616603ba6500f41943cbf89eb4a8a5be, < c9a7c1eb0ad41dcf004a9e870e452cafedcd9172
Fixed in
  • c9a7c1eb0ad41dcf004a9e870e452cafedcd9172
LinuxLinuxAffected
  • ≥ 00e0f34c616603ba6500f41943cbf89eb4a8a5be, < b767b48614c38687d717082860de7aa46f3b142c
Fixed in
  • b767b48614c38687d717082860de7aa46f3b142c
LinuxLinuxAffected
  • ≥ 00e0f34c616603ba6500f41943cbf89eb4a8a5be, < b8a8b6d25e7426a638c60eaba2129c0664131e84
Fixed in
  • b8a8b6d25e7426a638c60eaba2129c0664131e84
LinuxLinuxAffected
  • ≥ 00e0f34c616603ba6500f41943cbf89eb4a8a5be, < b7dc5da660eb5ffa7f7b4d33f2c74cb71c6edd6c
Fixed in
  • b7dc5da660eb5ffa7f7b4d33f2c74cb71c6edd6c

AI-suggested

A fix for this issue is available and included in the Linux kernel commits identified by the fixedVersions hashes. Users should update to a Linux kernel version that includes these commits to resolve the data race in rds_conn_path_reset(). No additional mitigation actions are specified or required.

Description

A data race vulnerability in the Linux kernel's RDS subsystem was fixed by changing how connection path flags are cleared in rds_conn_path_reset(). The original code cleared all flags with a plain store, which could race with concurrent atomic operations on individual bits, causing lost updates. The fix clears only specific bits individually, preserving atomicity and lock ownership semantics during connection teardown.

References

Community reviews

Loading reviews…