# CVE-2026-46177: ipmi: Add limits to event and receive message requests

> A malicious or buggy BMC can cause the Linux kernel IPMI driver to hang by never signaling completion, leading to a denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2026
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-89081, BELL-CVE-2026-46177, DEBIAN-CVE-2026-46177, GHSA-h4pv-4jh4-mxpf, ROOT-OS-DEBIAN-11-CVE-2026-46177, ROOT-OS-DEBIAN-12-CVE-2026-46177, ROOT-OS-UBUNTU-2204-CVE-2026-46177, ROOT-OS-UBUNTU-2404-CVE-2026-46177, UBUNTU-CVE-2026-46177

## What is CVE-2026-46177?

CVE-2026-46177 is a high-severity denial of service vulnerability in Linux kernel, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-46177?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-46177?

Apply the vendor's patch.

## Is CVE-2026-46177 being exploited?

There is no known exploitation of CVE-2026-46177 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46177 and fix it if it is affected.

What it is: CVE-2026-46177 is a high-severity denial of service vulnerability in Linux kernel, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46177 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46177/ (Markdown: https://insights.sbomify.com/CVE-2026-46177/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46177
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46177
- OSV: https://osv.dev/vulnerability/CVE-2026-46177

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46177/
Summaries are generated and may contain mistakes; the official description above is the record.