CVE-2026-46117

HIGHNVD 7.8

7.8

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

RDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss()

Sashiko points out that the user can specify WQs sharing the same CQ as a part of the uAPI and this will trigger the WARN_ON() then go on to corrupt the kernel.

Just reject it outright and fail the QP creation.

CVSS v3: 7.8
EG Score: 0.0(none)
EPSS: 1.8%
KEV: Not listed

Published

May 28, 2026

Last Modified

May 30, 2026

References (4)

416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/159f2efabc89d3f931d38f2d35876535d4abf0a3
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/9cc0c6b1ba8cd5c55aef043e1384de0a8b4efa71
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/9ef65af26b2a6738bf15812042e84b3112402d3a
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/db991ba50087ad99fa12a2c483aa3be19671ea73

Vendor Advisories for CVE-2026-46117(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

GHSA-c74j-26pg-r222
GitHub Security AdvisoriesHigh
In the Linux kernel, the following vulnerability has been resolved: RDMA/mana: Remove user...

Data Freshness Timeline

(refreshed 9× in last 7d / 9× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-29 13:44 UTCepss_batch
2026-05-29 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 10:14 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-46117?

CVE-2026-46117 is a high vulnerability published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/mana: Remove user triggerable WARNON() in manaibcreateqp_rss() Sashiko points out that the user can specify WQs sharing the same CQ as a part of the uAPI and this will trigger the WARN_ON() then go on to corrupt the kernel.…

When was CVE-2026-46117 disclosed?

CVE-2026-46117 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on May 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2026-46117 actively exploited?

CVE-2026-46117 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2026-46117?

CVE-2026-46117 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 0.0.

How do I remediate CVE-2026-46117?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46117, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46117

Explore →

Is Your Infrastructure Affected by CVE-2026-46117?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2026-46117

📅 Published

🔄 Last Modified

🔗 References (4)

📣 Vendor Advisories for CVE-2026-46117(1)