CVE-2026-46177 — ipmi: Add limits to event and receive message requests
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.7% (30-day exploitation probability)+8
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
version 2.6.12≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < c4cca236968683eb0d59abfb12d5c7e4d8514227≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < c024167fb00489baee08c72182ca2e7dc5fb9f20≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 3d37d2165df9504ea99d9e6181552dc4d2d1ab37≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < e20212b431bef217d3886b86bbc90cc3ed00de68≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 67c44e0deba936d5edaebea356b4589eb43acb5c≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 9059dc94421e1d4f8e5844204608b37ebfddb3da≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 304b56883b7eff73eb606c35d062c8101aaf5471 and 1 more≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 112df8e631636cafda64dcee4561daf09ce74a4a |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel |
version 2.6.12-rc5version 7.1-rc2version 7.1-rc1≥ 2.6.12.1 and < 5.10.258version 2.6.12-rc4version 2.6.12-rc3version 2.6.12-rc2version 2.6.12 and 6 more≥ 6.19 and < 7.0.7≥ 6.13 and < 6.18.30≥ 6.7 and < 6.12.88≥ 6.2 and < 6.6.140≥ 5.16 and < 6.1.175≥ 5.11 and < 5.15.209 |
Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.5 | CVSS 3.1 | High | 3.9 | 3.6 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.5 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 7.5 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.72%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Timeline
What happened to this CVE, newest first.
- 2026
- Source status changed · Analyzed → Modified
- Affected products added · linux/linux
- Record published
- Fix documented
- CVSS changed · 7.5
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
11 on the record
- git.kernel.org/stable/c/3d37d2165df9504ea99d9e6181552dc4d2d1ab37
- git.kernel.org/stable/c/c4cca236968683eb0d59abfb12d5c7e4d8514227
- git.kernel.org/stable/c/304b56883b7eff73eb606c35d062c8101aaf5471
- git.kernel.org/stable/c/e20212b431bef217d3886b86bbc90cc3ed00de68
- git.kernel.org/stable/c/9059dc94421e1d4f8e5844204608b37ebfddb3da
- git.kernel.org/stable/c/c024167fb00489baee08c72182ca2e7dc5fb9f20
- git.kernel.org/stable/c/67c44e0deba936d5edaebea356b4589eb43acb5c
- git.kernel.org/stable/c/112df8e631636cafda64dcee4561daf09ce74a4a
- github.com/advisories/GHSA-h4pv-4jh4-mxpf
- cert-portal.siemens.com/productcert/html/ssa-784472.html
- nvd.nist.gov/vuln/detail/CVE-2026-46177
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 13h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 13h
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-46177 is "ipmi: Add limits to event and receive message requests", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. EPSS 0.72% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.