CVE-2026-99212

Invalid memory access via stale RDMA identifier

Published Oct 28, 2026 · Updated Oct 28, 2026

Use-after-free in Linux RDS allows attackers to trigger invalid kernel-memory accesses after RDMA route resolution fails. rds_rdma_cm_event_handler_cmn() propagates a synchronous error from rdma_resolve_route(), causing RDMA CM to free an identifier that RDS retains and reuses during shutdown. This requires an RDS RDMA connection attempt and a synchronous route-resolution error; attacker control and further security impact are not established in the published patch.

CVSS severityUnavailable
Unscored
EPSS probability0.12%
Next 30 days · Nov 1, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Contact us

Summary

What happened

Use-after-free in Linux RDS allows attackers to trigger invalid kernel-memory accesses after RDMA route resolution fails. rds_rdma_cm_event_handler_cmn() propagates a synchronous error from rdma_resolve_route(), causing RDMA CM to free an identifier that RDS retains and reuses during shutdown. This requires an RDS RDMA connection attempt and a synchronous route-resolution error; attacker control and further security impact are not established in the published patch.

The record

CVE
CVE-2026-99212
Published
Oct 28, 2026
Updated
Oct 28, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
Unavailable
Privileges
Unavailable

Timeline

How it unfolded

  1. Oct 28, 2026CVE publishedPublication date reported by the CVE source.
  2. Oct 28, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=2.6.30
  2. Affected versionversion=55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea <91ece3efa064f0b3b3c67b9b045d9eeb4a034e43
  3. Affected versionversion=55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea <98d446b7c013254a8a7b49720557676a3a851fde
  4. Affected versionversion=55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea <a7c7d0ff876377fea7ae876a28d6df8d9349df57

What conditions does exploitation require?

Attack vectorUnavailable in this record.
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=2.6.30; version=55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea <91ece3efa064f0b3b3c67b9b045d9eeb4a034e43; version=55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea <98d446b7c013254a8a7b49720557676a3a851fde; version=55b7ed0b582f9ff4bf3b9b44969cddda8c6763ea <a7c7d0ff876377fea7ae876a28d6df8d9349df57

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
VectorUnavailable
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Contact us