Answer in brief
CVE-2026-80624 records a Unknown severity vulnerability in mfd: cs42l43: Sanity check firmware size. 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 | >=ace6d14481386ec6c1b63cc2b24c71433a583dc2 <2ce02059ceb6311a33026b62e6e4dc4ed22a3aef || >=ace6d14481386ec6c1b63cc2b24c71433a583dc2 <197a4c54d8a94fe2fb7829661b29f0859c10feb5 || >=ace6d14481386ec6c1b63cc2b24c71433a583dc2 <d35e4032f16d7621468c8b56816e7935ebf590a7 || >=ace6d14481386ec6c1b63cc2b24c71433a583dc2 <17d79248b4f370663f9d351409a130fc1ed9416d || >=ace6d14481386ec6c1b63cc2b24c71433a583dc2 <b6ef1a74b3ec254f87a6a3c554fe8f8083ebd37c | 2ce02059ceb6311a33026b62e6e4dc4ed22a3aef, 197a4c54d8a94fe2fb7829661b29f0859c10feb5, d35e4032f16d7621468c8b56816e7935ebf590a7, 17d79248b4f370663f9d351409a130fc1ed9416d, b6ef1a74b3ec254f87a6a3c554fe8f8083ebd37c |
| Linux/Linuxgeneric | 6.6 | Not reported |
Published upstream
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 28, 2026
In the Linux kernel, the following vulnerability has been resolved: mfd: cs42l43: Sanity check firmware size Currently the code checks if a firmware was received, however it does not verify that the firmware size is larger than the firmware header. As the firmware pointer is dereferenced as a pointer to the header structure this could lead to an out of bounds memory access. Add the missing check.
Quoted source text, attributed separately from HOL analysis.