Answer in brief
CVE-2026-46177 records a Unknown severity vulnerability in ipmi: Add limits to event and receive message requests. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-46177 records a Unknown severity vulnerability in ipmi: Add limits to event and receive message requests. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <112df8e631636cafda64dcee4561daf09ce74a4a || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <304b56883b7eff73eb606c35d062c8101aaf5471 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9059dc94421e1d4f8e5844204608b37ebfddb3da || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <67c44e0deba936d5edaebea356b4589eb43acb5c || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e20212b431bef217d3886b86bbc90cc3ed00de68 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3d37d2165df9504ea99d9e6181552dc4d2d1ab37 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c024167fb00489baee08c72182ca2e7dc5fb9f20 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c4cca236968683eb0d59abfb12d5c7e4d8514227 | 112df8e631636cafda64dcee4561daf09ce74a4a, 304b56883b7eff73eb606c35d062c8101aaf5471, 9059dc94421e1d4f8e5844204608b37ebfddb3da, 67c44e0deba936d5edaebea356b4589eb43acb5c, e20212b431bef217d3886b86bbc90cc3ed00de68, 3d37d2165df9504ea99d9e6181552dc4d2d1ab37, c024167fb00489baee08c72182ca2e7dc5fb9f20, c4cca236968683eb0d59abfb12d5c7e4d8514227 |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
May 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 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 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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <112df8e631636cafda64dcee4561daf09ce74a4a || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <304b56883b7eff73eb606c35d062c8101aaf5471 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9059dc94421e1d4f8e5844204608b37ebfddb3da || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <67c44e0deba936d5edaebea356b4589eb43acb5c || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e20212b431bef217d3886b86bbc90cc3ed00de68 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3d37d2165df9504ea99d9e6181552dc4d2d1ab37 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c024167fb00489baee08c72182ca2e7dc5fb9f20 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c4cca236968683eb0d59abfb12d5c7e4d8514227 | 112df8e631636cafda64dcee4561daf09ce74a4a, 304b56883b7eff73eb606c35d062c8101aaf5471, 9059dc94421e1d4f8e5844204608b37ebfddb3da, 67c44e0deba936d5edaebea356b4589eb43acb5c, e20212b431bef217d3886b86bbc90cc3ed00de68, 3d37d2165df9504ea99d9e6181552dc4d2d1ab37, c024167fb00489baee08c72182ca2e7dc5fb9f20, c4cca236968683eb0d59abfb12d5c7e4d8514227 |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
May 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 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 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.
Quoted source text, attributed separately from HOL analysis.