CVE-2023-54130

hfs/hfsplus: avoid WARN_ON() for sanity check, use proper error handling

HIGH
7.8
CVSS Score
Published: December 24, 2025 at 01:06 PM UTC
Updated: August 5, 2026 at 10:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%

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).

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 4.9.3374.9.337 ≤ v < 4.105.16 ≤ v < 6.0.195.16 ≤ v < 6.1.55.16 ≤ v < 6.22344f17c0a89c181ab1a9fef57fd8c3bddfd6e30367296925c7625c3969d2a78d7a3e1dee161beb54.9.33748d9e2e6de01ed35e965eb549758a837c07b601d4fd3a11804c8877ff11fec59c5c53f1635331e3e5.1655d1cbbbb29e6656c662ee8f73ba1fc4777532eb8c40f2dbae603ef0bd21e87c63f54ec59fd8825690103ccb6e60aa4efe48993d23d6a528472f2233c886c10a6eddb99923b315f42bf63f448883ef9a
Vendor states this is fixed in 45917be9f0af339a45b4619f31c902d37b8aed59 (fixed)
Vendor states this is fixed in 82725be426bce0a425cc5e26fbad61ffd29cff03 (fixed)
Vendor states this is fixed in 90e019006644dad35862cb4aa270f561b0732066 (fixed)
Vendor states this is fixed in be01f35efa876eb81cebab2cb0add068b7280ef4 (fixed)
Vendor states this is fixed in cb7a95af78d29442b8294683eca4897544b8ef46 (fixed)
Vendor states this is fixed in cc2164ada548addfa8ee215196661c3afe0c5154 (fixed)
Vendor states this is fixed in da23752d9660ba7a8ca6c5768fd8776f67f59ee7 (fixed)
Vendor states this is fixed in f10defb0be6ac42fb6a97b45920d32da6bd6fde8 (fixed)
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.16 (unaffected)
Vendor states this is fixed in 6.0.19 (unaffected)
Vendor states this is fixed in 6.1.5 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card