Skip to main content

Linux EUVDEUVD-2026-93337

| CVE-2026-98352
2026-10-06 Linux GHSA-qh4j-6f7w-8997
View
Monitor Track and reassess. Why: No CVSS yet + weak signal (CWE or non-zero EPSS).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisCVE.org

In the Linux kernel, the following vulnerability has been resolved:

RDMA/rtrs-clt: Fix CQ pool leak when connect is interrupted

The client borrows shared CQ credits in the ADDR_RESOLVED handler via ib_cq_pool_get(), before the peer is connected. create_cm() can return -ERESTARTSYS from wait_event_interruptible_timeout() without destroying the CM ID. The init_conns() and stop-and-destroy paths then call destroy_con_cq_qp() while cq is still NULL (no PUT) and only afterwards rdma_destroy_id().

CMA serializes the handler against rdma_destroy_id() with handler_mutex, but that does not order the GET against destroy_con_cq_qp(). If ADDR_RESOLVED has already passed the DESTROYING check, it can take con_mutex, GET credits, and then lose the con to kfree. Device unregister later hits WARN_ON(cq->cqe_used) in ib_cq_pool_cleanup().

Set a per-connection flag under con_mutex before CQ/QP teardown so a racing ADDR_RESOLVED cannot borrow credits after teardown has begun.

Affected VersionsENISA

Linux 3b89e92c2a95a39c38a3808f4528e502a39bd94d <8f253d5893f991742464b9e7203c43fc08d0aa11
Linux 3b89e92c2a95a39c38a3808f4528e502a39bd94d <6f8020fe7465f49e234a576c04e415e9d08c7878
Linux patch: 7.2.8
Linux 3b89e92c2a95a39c38a3808f4528e502a39bd94d <74c4ed55e61f1b65ddbebc5b635d136461a1c3da
Linux patch: 0
Linux patch: 6.18.54
Linux 5.13
Linux patch: 7.3-rc4
Linux patch: 6.1.189
Linux 3b89e92c2a95a39c38a3808f4528e502a39bd94d <a82cca40139d9fcae8208901856bd5bb4051f097
Linux patch: 5.15.222
Linux 3b89e92c2a95a39c38a3808f4528e502a39bd94d <bf88ac4867050112a6c819c8d1a7209bf48ef427
Linux patch: 6.12.112
Linux 3b89e92c2a95a39c38a3808f4528e502a39bd94d <2ae16aaa78b5edc6e6d0904c84fd9cdfb762bcda
Linux patch: 6.6.158
Linux 3b89e92c2a95a39c38a3808f4528e502a39bd94d <31024e158b45358370a0a14ed96589e6aa62d6cb

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Lifecycle Timeline

2
Patch available
Oct 06, 2026 - 10:02 EUVD
CVE Published
Oct 06, 2026 - 08:46 cve.org
UNKNOWN (no severity yet)

Threat Intelligence Overview

EPSS Score
0.2%
Top 95% exploitable
Threat Intel
1
1 sources
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity Not scored yet
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
No CVSS yet + weak signal (CWE or non-zero EPSS)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy