Answer in brief
CVE-2023-54130 records a High severity (CVSS 7.8) vulnerability in hfs/hfsplus: avoid WARN_ON() for sanity check, use proper error handling. 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-2023-54130 records a High severity (CVSS 7.8) vulnerability in hfs/hfsplus: avoid WARN_ON() for sanity check, use proper error handling. 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.
CVSS is 7.8. 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 | >=c886c10a6eddb99923b315f42bf63f448883ef9a <cc2164ada548addfa8ee215196661c3afe0c5154 || >=2344f17c0a89c181ab1a9fef57fd8c3bddfd6e30 <82725be426bce0a425cc5e26fbad61ffd29cff03 || >=90103ccb6e60aa4efe48993d23d6a528472f2233 <da23752d9660ba7a8ca6c5768fd8776f67f59ee7 || >=4fd3a11804c8877ff11fec59c5c53f1635331e3e <be01f35efa876eb81cebab2cb0add068b7280ef4 || >=48d9e2e6de01ed35e965eb549758a837c07b601d <f10defb0be6ac42fb6a97b45920d32da6bd6fde8 || >=55d1cbbbb29e6656c662ee8f73ba1fc4777532eb <90e019006644dad35862cb4aa270f561b0732066 || >=55d1cbbbb29e6656c662ee8f73ba1fc4777532eb <45917be9f0af339a45b4619f31c902d37b8aed59 || >=55d1cbbbb29e6656c662ee8f73ba1fc4777532eb <cb7a95af78d29442b8294683eca4897544b8ef46 || 8c40f2dbae603ef0bd21e87c63f54ec59fd88256 || 367296925c7625c3969d2a78d7a3e1dee161beb5 || >=4.9.337 <4.10 | cc2164ada548addfa8ee215196661c3afe0c5154, 82725be426bce0a425cc5e26fbad61ffd29cff03, da23752d9660ba7a8ca6c5768fd8776f67f59ee7, be01f35efa876eb81cebab2cb0add068b7280ef4, f10defb0be6ac42fb6a97b45920d32da6bd6fde8, 90e019006644dad35862cb4aa270f561b0732066, 45917be9f0af339a45b4619f31c902d37b8aed59, cb7a95af78d29442b8294683eca4897544b8ef46, 4.10 |
| Linux/Linuxgeneric | 5.16 | Not reported |
Published upstream
Dec 24, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: hfs/hfsplus: avoid WARN_ON() for sanity check, use proper error handling Commit 55d1cbbbb29e ("hfs/hfsplus: use WARN_ON for sanity check") fixed a build warning by turning a comment into a WARN_ON(), but it turns out that syzbot then complains because it can trigger said warning with a corrupted hfs image. The warning actually does warn about a bad situation, but we are much better off just handling it as the error it is. So rather than warn about us doing bad things, stop doing the bad things and return -EIO. While at it, also fix a memory leak that was introduced by an earlier fix for a similar syzbot warning situation, and add a check for one case that historically wasn't handled at all (ie neither comment nor subsequent WARN_ON).
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. 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 | >=c886c10a6eddb99923b315f42bf63f448883ef9a <cc2164ada548addfa8ee215196661c3afe0c5154 || >=2344f17c0a89c181ab1a9fef57fd8c3bddfd6e30 <82725be426bce0a425cc5e26fbad61ffd29cff03 || >=90103ccb6e60aa4efe48993d23d6a528472f2233 <da23752d9660ba7a8ca6c5768fd8776f67f59ee7 || >=4fd3a11804c8877ff11fec59c5c53f1635331e3e <be01f35efa876eb81cebab2cb0add068b7280ef4 || >=48d9e2e6de01ed35e965eb549758a837c07b601d <f10defb0be6ac42fb6a97b45920d32da6bd6fde8 || >=55d1cbbbb29e6656c662ee8f73ba1fc4777532eb <90e019006644dad35862cb4aa270f561b0732066 || >=55d1cbbbb29e6656c662ee8f73ba1fc4777532eb <45917be9f0af339a45b4619f31c902d37b8aed59 || >=55d1cbbbb29e6656c662ee8f73ba1fc4777532eb <cb7a95af78d29442b8294683eca4897544b8ef46 || 8c40f2dbae603ef0bd21e87c63f54ec59fd88256 || 367296925c7625c3969d2a78d7a3e1dee161beb5 || >=4.9.337 <4.10 | cc2164ada548addfa8ee215196661c3afe0c5154, 82725be426bce0a425cc5e26fbad61ffd29cff03, da23752d9660ba7a8ca6c5768fd8776f67f59ee7, be01f35efa876eb81cebab2cb0add068b7280ef4, f10defb0be6ac42fb6a97b45920d32da6bd6fde8, 90e019006644dad35862cb4aa270f561b0732066, 45917be9f0af339a45b4619f31c902d37b8aed59, cb7a95af78d29442b8294683eca4897544b8ef46, 4.10 |
| Linux/Linuxgeneric | 5.16 | Not reported |
Published upstream
Dec 24, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: hfs/hfsplus: avoid WARN_ON() for sanity check, use proper error handling Commit 55d1cbbbb29e ("hfs/hfsplus: use WARN_ON for sanity check") fixed a build warning by turning a comment into a WARN_ON(), but it turns out that syzbot then complains because it can trigger said warning with a corrupted hfs image. The warning actually does warn about a bad situation, but we are much better off just handling it as the error it is. So rather than warn about us doing bad things, stop doing the bad things and return -EIO. While at it, also fix a memory leak that was introduced by an earlier fix for a similar syzbot warning situation, and add a check for one case that historically wasn't handled at all (ie neither comment nor subsequent WARN_ON).
Quoted source text, attributed separately from HOL analysis.