CVE-2026-46177

Description

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.1 Score

7.5

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS — Exploit Prediction

0.0053

Probability of exploitation

0.41%

Percentile rank

EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.

References

Other References

https://git.kernel.org/stable/c/112df8e631636cafda64dcee4561daf09ce74a4a https://git.kernel.org/stable/c/304b56883b7eff73eb606c35d062c8101aaf5471 https://git.kernel.org/stable/c/3d37d2165df9504ea99d9e6181552dc4d2d1ab37 https://git.kernel.org/stable/c/67c44e0deba936d5edaebea356b4589eb43acb5c https://git.kernel.org/stable/c/9059dc94421e1d4f8e5844204608b37ebfddb3da https://git.kernel.org/stable/c/c024167fb00489baee08c72182ca2e7dc5fb9f20 https://git.kernel.org/stable/c/c4cca236968683eb0d59abfb12d5c7e4d8514227 https://git.kernel.org/stable/c/e20212b431bef217d3886b86bbc90cc3ed00de68

Frequently Asked Questions

What is CVE-2026-46177? +

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. It has a CVSS v3.1 base score of 7.5 (HIGH).

How severe is CVE-2026-46177? +

CVE-2026-46177 has a CVSS v3.1 score of 7.5 out of 10, rated HIGH. This is a high-severity vulnerability that should be prioritized for patching. The EPSS score is 0.0053, placing it in the 0th percentile for exploitation probability.

How do I check if I'm vulnerable to CVE-2026-46177? +

You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.