Unknown

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

In the Linux kernel, the following vulnerability has been resolved: net/rds: clear cp_flags bits individually in rds_conn_path_reset() rds_conn_path_reset() wipes the whole flag word with a plain cp->cp_flags = 0 store. Every other accessor of that word uses atomic bitops, and some of them can run concurrently with the reset: RDS_LL_SEND_FULL is set from rds_send_xmit() and cleared from the transport completion paths, neither of which holds anything that excludes the shutdown worker. A plain store racing an atomic read-modify-write on the same word is a data race, and whichever side loses has its update silently discarded. Clear the two bits the reset is actually responsible for instead. RDS_IN_XMIT and RDS_RECV_REFILL need no store at all here: they belong to the caller, rds_conn_shutdown(), which waits for both to be clear before calling the transport shutdown and this reset. This also gives every bit in cp_flags a single well-defined writer discipline, which the following patches rely on when they turn RDS_IN_XMIT and RDS_RECV_REFILL into bit locks held across the teardown: a blanket store mid-teardown would destroy lock ownership that an atomic clear preserves. Oracle UEK carries the same conversion ("net/rds: Preserve essential connection state flags"), motivated by its asynchronous shutdown state machine, whose progress and destroy flags must survive the reset. UEK's variant also clears RDS_IN_XMIT and RDS_RECV_REFILL because there the reset runs as the final step of a teardown that owns both bits, making those clears its unlock. Upstream that release belongs in rds_conn_shutdown(): once a later patch in this series turns the two bits into locks held across the teardown, ending ownership needs release semantics and a wake-up that a plain clear inside the reset would not provide. Based on Oracle UEK commit "net/rds: Preserve essential connection state flags" by Gerd Rausch.

Published Sep 25, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+1

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.18%

ahead of 7% of scored CVEs · Oct 15, 2026

Affects

Linux

CVSS base

—

Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	≥ 00e0f34c616603ba6500f41943cbf89eb4a8a5be and < c9a7c1eb0ad41dcf004a9e870e452cafedcd9172≥ 00e0f34c616603ba6500f41943cbf89eb4a8a5be and < b767b48614c38687d717082860de7aa46f3b142c≥ 00e0f34c616603ba6500f41943cbf89eb4a8a5be and < b7dc5da660eb5ffa7f7b4d33f2c74cb71c6edd6c≥ 00e0f34c616603ba6500f41943cbf89eb4a8a5be and < b8a8b6d25e7426a638c60eaba2129c0664131e84≥ 00e0f34c616603ba6500f41943cbf89eb4a8a5be and < ed3ee0ac4aafda50c2f4381eb973beefeb7879ac≥ 00e0f34c616603ba6500f41943cbf89eb4a8a5be and < 6b8d7563c28b8112e6e54abe413b028ef3f8c549≥ 00e0f34c616603ba6500f41943cbf89eb4a8a5be and < cb62aa8f04655a4df487913949719c0a1266ed73≥ 00e0f34c616603ba6500f41943cbf89eb4a8a5be and < 103c4b13c4f50322910078d1c02f29334a574122 and 1 more version 2.6.30	Vulnerable	CVE Program (cve.org) e CISA ADP

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Not enough vector or weakness data: use the affected application’s logs as a starting point.

application logs

Timeline

What happened to this CVE, newest first.

2026
Record published
Oct 15, 2026
Affected products added · linux/linux
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Undergoing Analysis
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Sep 25, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

8 on the record

git.kernel.org/stable/c/6b8d7563c28b8112e6e54abe413b028ef3f8c549
NIST National Vulnerability Database
git.kernel.org/stable/c/cb62aa8f04655a4df487913949719c0a1266ed73
NIST National Vulnerability Database
git.kernel.org/stable/c/b767b48614c38687d717082860de7aa46f3b142c
NIST National Vulnerability Database
git.kernel.org/stable/c/b7dc5da660eb5ffa7f7b4d33f2c74cb71c6edd6c
NIST National Vulnerability Database
git.kernel.org/stable/c/b8a8b6d25e7426a638c60eaba2129c0664131e84
NIST National Vulnerability Database
git.kernel.org/stable/c/103c4b13c4f50322910078d1c02f29334a574122
NIST National Vulnerability Database
git.kernel.org/stable/c/c9a7c1eb0ad41dcf004a9e870e452cafedcd9172
NIST National Vulnerability Database
git.kernel.org/stable/c/ed3ee0ac4aafda50c2f4381eb973beefeb7879ac
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 1d
Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 1d
Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 2d
Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 2d
Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 2d
Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No CVSS score published by NVD, the CNA, CISA or GitHub so far.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-98071 is "net/rds: clear cp_flags bits individually in rds_conn_path_reset()", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.