CVE-2026-46108

NONECVSS 0.0

0.0

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

ipmi:si: Return state to normal if message allocation fails

There were places where nothing would get started if a message allocation failed, so the driver needs to return to normal state.

CVSS v3: —
EG Score: 0.0(none)
EPSS: 5.1%
KEV: Not listed

Published

May 28, 2026

Last Modified

May 28, 2026

References (5)

416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/09dd798270ff582d7309f285d4aaf5dbebae01cb
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/88881dc1da86064f479378bc9d0a4956c3d0bb12
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/ba60140d4133231b49185ac8bf6e54f318d3134e
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/bc13fce9eeec88c4950924754c3347c6dc66ff4c
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/ce905b65e649eee378a0f37e8219f1d70efb3007

Vendor Advisories for CVE-2026-46108(1)

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

GHSA-49qj-cwh3-6453
GitHub Security Advisoriesunknown
In the Linux kernel, the following vulnerability has been resolved: ipmi:si: Return state to...

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(4)

What is CVE-2026-46108?

CVE-2026-46108 is a none vulnerability published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: ipmi:si: Return state to normal if message allocation fails There were places where nothing would get started if a message allocation failed, so the driver needs to return to normal state.

When was CVE-2026-46108 disclosed?

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

Is CVE-2026-46108 actively exploited?

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

How do I remediate CVE-2026-46108?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46108, 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-46108

Explore →

Is Your Infrastructure Affected by CVE-2026-46108?

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

Start Free Scan →Browse All CVEs

CVE-2026-46108

📅 Published

🔄 Last Modified

🔗 References (5)

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