Unknown

CVE-2026-99212 — net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure

In the Linux kernel, the following vulnerability has been resolved: net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure rds_rdma_cm_event_handler_cmn() hands the return value of rdma_resolve_route() straight back to the rdma_cm on RDMA_CM_EVENT_ADDR_RESOLVED. A synchronous failure there - -ENOMEM from the route work allocation, an SA query that cannot be set up, a RoCE route with no usable device - makes addr_handler() destroy the id the event was delivered on. That id is ic->i_cm_id, and nothing clears the pointer: the connection sits in RDS_CONN_CONNECTING with a freed id until its shutdown calls rdma_disconnect() and rdma_destroy_id() on it. The ROUTE_RESOLVED case already avoids this: rds_ib_cm_initiate_connect() forces a zero return while ic->i_cm_id == cm_id, as the comment there explains. Do the same here - drop the connection and return 0 - so the id stays RDS's to destroy from the shutdown, and the reconnect gets a fresh one.

Published Oct 28, 2026 · Updated Oct 28, 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

No scoring signals.

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

—

No EPSS score.

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	≥ 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea and < a7c7d0ff876377fea7ae876a28d6df8d9349df57≥ 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea and < 91ece3efa064f0b3b3c67b9b045d9eeb4a034e43≥ 55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea and < 98d446b7c013254a8a7b49720557676a3a851fdeversion 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 28, 2026
Affected products added · linux/linux
Oct 28, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 28, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 28, 2026 · Alertas do Telegram
CVE published
Oct 28, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 28, 2026 – Oct 28, 2026
1× Official description updated · Oct 28, 2026 – Oct 28, 2026

References

3 on the record

git.kernel.org/stable/c/a7c7d0ff876377fea7ae876a28d6df8d9349df57
NIST National Vulnerability Database
git.kernel.org/stable/c/98d446b7c013254a8a7b49720557676a3a851fde
NIST National Vulnerability Database
git.kernel.org/stable/c/91ece3efa064f0b3b3c67b9b045d9eeb4a034e43
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 5h
Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 5h
Unknown CVE-2026-99214 drm/vc4: hdmi: Move packet RAM enable to PM runtime 5h
Unknown CVE-2026-99213 vsock: treat TCP_CLOSING as once-established 5h
Unknown CVE-2026-99211 netlink: reset skb headers before unicast and multicast filtering 5h
Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 5h

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 FIRST EPSS score.
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-99212 is "net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. 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.