GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel net/rds: a blanket cp_flags store in the connection reset races atomic bitops and discards updates

UnscoredCVE-2026-98071Kernel, userspace & hypervisorcurated

Impact

rds_conn_path_reset() wiped the whole flag word with a plain cp->cp_flags = 0 store while every other accessor uses atomic bitops, and some of those run concurrently with the reset - RDS_LL_SEND_FULL is set from rds_send_xmit() and cleared from transport completion paths, neither of which excludes the shutdown worker. A plain store racing an atomic read-modify-write on the same word is a data race, and the losing side's update is silently dropped, leaving flow-control state on an RDS path inconsistent after a reset. On a fabric that carries cluster messaging this reads as a stuck or mis-flow-controlled connection rather than a memory-safety problem. The fix also matters structurally: later patches turn RDS_IN_XMIT and RDS_RECV_REFILL into bit locks held across teardown, and a blanket store mid-teardown would destroy that lock ownership. Only affects nodes that load the rds module.

Who can reach it

Local/on-fabric race, not a directed attack: requires a connection reset in the shutdown worker concurrent with send or completion processing on the same RDS path. No authentication element is described in the record.

What to do

Update to a stable kernel where the reset clears only the two bits it owns with atomic ops instead of storing zero over the word. Requires a node reboot after drain. Where RDS is not in use, unloading or blacklisting the rds modules removes the exposure.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.