CVE-2026-46177

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-28. the CNA's CVSS baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

ipmi: Add limits to event and receive message requests

The driver would just fetch events and receive messages until the BMC said it was done. To avoid issues with BMCs that never say they are done, add a limit of 10 fetches at a time.

In addition, an si interface has an attn state it can return from the hardware which is supposed to cause a flag fetch to see if the driver needs to fetch events or message or a few other things. If the attn bit gets stuck, it's a similar problem. So allow messages in between flag fetches so the driver itself doesn't get stuck.

This is a more general fix than the previous fix for the specific bad BMC, but should fix the more general issue of a BMC that won't stop saying it has data.

This has been there from the beginning of the driver. It's not a bug per-se, but it is accounting for bugs in BMCs.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
39.5%
KEV
Not listed

Published

May 28, 2026

Last Modified

June 14, 2026

Advisory Details (8)

Auto-updated Jun 4, 2026
No patch confirmed yet.
generic

ipmi: Add limits to event and receive message requests - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e20212b431bef217d3886b86bbc90cc3ed00de68
generic

ipmi: Add limits to event and receive message requests - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c4cca236968683eb0d59abfb12d5c7e4d8514227
generic

ipmi: Add limits to event and receive message requests - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c024167fb00489baee08c72182ca2e7dc5fb9f20
generic

ipmi: Add limits to event and receive message requests - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9059dc94421e1d4f8e5844204608b37ebfddb3da
generic

ipmi: Add limits to event and receive message requests - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/67c44e0deba936d5edaebea356b4589eb43acb5c
generic

ipmi: Add limits to event and receive message requests - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3d37d2165df9504ea99d9e6181552dc4d2d1ab37
generic

ipmi: Add limits to event and receive message requests - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/304b56883b7eff73eb606c35d062c8101aaf5471
generic

ipmi: Add limits to event and receive message requests - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/112df8e631636cafda64dcee4561daf09ce74a4a

Vendor Advisories for CVE-2026-46177(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 91× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 205 total refreshes for this CVE.

  1. 2026-07-16 10:20 UTCEG score recompute
  2. 2026-07-16 10:20 UTCGHSA enrichment
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-13 22:30 UTCEPSS rescore
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-12 05:46 UTCEPSS rescore
  8. 2026-07-11 21:15 UTCEG score recompute
  9. 2026-07-11 21:15 UTCVendor advisory
  10. 2026-07-11 21:15 UTCGHSA enrichment
  11. 2026-07-11 08:27 UTCEPSS rescore
  12. 2026-07-09 19:10 UTCEPSS rescore
  13. 2026-07-08 18:24 UTCEG score recompute
  14. 2026-07-08 18:24 UTCVendor advisory
  15. 2026-07-08 18:24 UTCGHSA enrichment
  16. 2026-07-08 15:16 UTCEPSS rescore
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-06 16:27 UTCEPSS rescore
  19. 2026-07-06 02:23 UTCEPSS rescore
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-02 14:14 UTCEG score recompute
  23. 2026-07-02 14:14 UTCVendor advisory
  24. 2026-07-02 14:14 UTCGHSA enrichment
  25. 2026-07-01 15:07 UTCEPSS rescore
Show 75 more
  1. 2026-07-01 14:20 UTCEG score recompute
  2. 2026-07-01 14:20 UTCVendor advisory
  3. 2026-07-01 14:20 UTCGHSA enrichment
  4. 2026-07-01 03:07 UTCEG score recompute
  5. 2026-07-01 03:07 UTCVendor advisory
  6. 2026-07-01 03:07 UTCGHSA enrichment
  7. 2026-06-30 23:22 UTCEPSS rescore
  8. 2026-06-30 01:59 UTCEG score recompute
  9. 2026-06-30 01:59 UTCVendor advisory
  10. 2026-06-30 01:59 UTCGHSA enrichment
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-29 13:45 UTCEG score recompute
  14. 2026-06-29 13:45 UTCVendor advisory
  15. 2026-06-29 13:45 UTCGHSA enrichment
  16. 2026-06-28 16:29 UTCEG score recompute
  17. 2026-06-28 16:29 UTCVendor advisory
  18. 2026-06-28 16:29 UTCGHSA enrichment
  19. 2026-06-28 14:07 UTCEPSS rescore
  20. 2026-06-28 05:22 UTCEG score recompute
  21. 2026-06-28 05:22 UTCVendor advisory
  22. 2026-06-28 05:22 UTCGHSA enrichment
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-27 18:15 UTCEG score recompute
  26. 2026-06-27 18:15 UTCVendor advisory
  27. 2026-06-27 18:14 UTCGHSA enrichment
  28. 2026-06-27 05:28 UTCEG score recompute
  29. 2026-06-27 05:28 UTCVendor advisory
  30. 2026-06-27 05:28 UTCGHSA enrichment
  31. 2026-06-27 03:08 UTCEPSS rescore
  32. 2026-06-26 16:52 UTCEG score recompute
  33. 2026-06-26 16:52 UTCVendor advisory
  34. 2026-06-26 16:51 UTCGHSA enrichment
  35. 2026-06-25 21:08 UTCEG score recompute
  36. 2026-06-25 21:08 UTCVendor advisory
  37. 2026-06-25 21:08 UTCGHSA enrichment
  38. 2026-06-25 13:49 UTCEPSS rescore
  39. 2026-06-25 09:53 UTCEG score recompute
  40. 2026-06-25 09:53 UTCVendor advisory
  41. 2026-06-25 09:53 UTCGHSA enrichment
  42. 2026-06-24 22:44 UTCEG score recompute
  43. 2026-06-24 22:44 UTCVendor advisory
  44. 2026-06-24 22:44 UTCGHSA enrichment
  45. 2026-06-24 14:05 UTCEPSS rescore
  46. 2026-06-23 21:33 UTCEPSS rescore
  47. 2026-06-23 21:33 UTCEPSS rescore
  48. 2026-06-22 14:25 UTCEPSS rescore
  49. 2026-06-22 14:25 UTCEPSS rescore
  50. 2026-06-21 14:56 UTCEPSS rescore
  51. 2026-06-21 14:56 UTCEPSS rescore
  52. 2026-06-21 01:59 UTCEPSS rescore
  53. 2026-06-21 01:59 UTCEPSS rescore
  54. 2026-06-19 19:26 UTCEPSS rescore
  55. 2026-06-19 19:26 UTCEPSS rescore
  56. 2026-06-18 17:52 UTCEPSS rescore
  57. 2026-06-18 17:52 UTCEPSS rescore
  58. 2026-06-17 20:40 UTCEG score recompute
  59. 2026-06-17 20:40 UTCVendor advisory
  60. 2026-06-17 20:40 UTCGHSA enrichment
  61. 2026-06-17 17:53 UTCEPSS rescore
  62. 2026-06-17 09:33 UTCEG score recompute
  63. 2026-06-17 09:32 UTCGHSA enrichment
  64. 2026-06-16 22:23 UTCEG score recompute
  65. 2026-06-16 22:23 UTCGHSA enrichment
  66. 2026-06-16 17:52 UTCEPSS rescore
  67. 2026-06-16 11:17 UTCEG score recompute
  68. 2026-06-16 11:17 UTCVendor advisory
  69. 2026-06-16 11:16 UTCGHSA enrichment
  70. 2026-06-16 00:09 UTCEG score recompute
  71. 2026-06-16 00:09 UTCVendor advisory
  72. 2026-06-16 00:09 UTCGHSA enrichment
  73. 2026-06-15 17:49 UTCEPSS rescore
  74. 2026-06-15 13:01 UTCEG score recompute
  75. 2026-06-15 13:01 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-46177?
CVE-2026-46177 is a high vulnerability published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: ipmi: Add limits to event and receive message requests The driver would just fetch events and receive messages until the BMC said it was done. To avoid issues with BMCs that never say they are done, add a limit of 10 fetches at a…
When was CVE-2026-46177 disclosed?
CVE-2026-46177 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on June 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46177 actively exploited?
CVE-2026-46177 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 39.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46177?
CVE-2026-46177 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-46177?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46177, 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

Explore the affected products and dependency analysis for CVE-2026-46177

Explore →

Is Your Infrastructure Affected by CVE-2026-46177?

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

Start Free Scan →Browse All CVEs