CVE-2023-54130hfs/hfsplus: avoid WARN_ON() for sanity check, use proper error handling
- 7.8HighCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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).
Timeline
ID reserved
By Linux
Published
- 7 months later
· 7 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Deferred | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected c886c10a6eddb99923b315f42bf63f448883ef9a – < cc2164ada548addfa8ee215196661c3afe0c5154
- affected 2344f17c0a89c181ab1a9fef57fd8c3bddfd6e30 – < 82725be426bce0a425cc5e26fbad61ffd29cff03
- affected 90103ccb6e60aa4efe48993d23d6a528472f2233 – < da23752d9660ba7a8ca6c5768fd8776f67f59ee7
- affected 4fd3a11804c8877ff11fec59c5c53f1635331e3e – < be01f35efa876eb81cebab2cb0add068b7280ef4
- affected 48d9e2e6de01ed35e965eb549758a837c07b601d – < f10defb0be6ac42fb6a97b45920d32da6bd6fde8
- affected 55d1cbbbb29e6656c662ee8f73ba1fc4777532eb – < 90e019006644dad35862cb4aa270f561b0732066
- affected 55d1cbbbb29e6656c662ee8f73ba1fc4777532eb – < 45917be9f0af339a45b4619f31c902d37b8aed59
- affected 55d1cbbbb29e6656c662ee8f73ba1fc4777532eb – < cb7a95af78d29442b8294683eca4897544b8ef46
- affected 8c40f2dbae603ef0bd21e87c63f54ec59fd88256
- affected 367296925c7625c3969d2a78d7a3e1dee161beb5
- affected 4.9.337 – < 4.10
- affected 5.16
- unaffected < 5.16
- unaffected 6.0.19 – ≤ 6.0.*
- unaffected 6.1.5 – ≤ 6.1.*
- unaffected 6.2 – ≤ *
References
References8
- https://git.kernel.org/stable/c/cc2164ada548addfa8ee215196661c3afe0c5154 (opens in a new tab)
- https://git.kernel.org/stable/c/82725be426bce0a425cc5e26fbad61ffd29cff03 (opens in a new tab)
- https://git.kernel.org/stable/c/da23752d9660ba7a8ca6c5768fd8776f67f59ee7 (opens in a new tab)
- https://git.kernel.org/stable/c/be01f35efa876eb81cebab2cb0add068b7280ef4 (opens in a new tab)
- https://git.kernel.org/stable/c/f10defb0be6ac42fb6a97b45920d32da6bd6fde8 (opens in a new tab)
- https://git.kernel.org/stable/c/90e019006644dad35862cb4aa270f561b0732066 (opens in a new tab)
- https://git.kernel.org/stable/c/45917be9f0af339a45b4619f31c902d37b8aed59 (opens in a new tab)
- https://git.kernel.org/stable/c/cb7a95af78d29442b8294683eca4897544b8ef46 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2023-60315 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2023-54130)Record last updated .