CVE-2023-54130 — hfs/hfsplus: avoid WARN_ON() for sanity check, use proper error handling
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).
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ c886c10a6eddb99923b315f42bf63f448883ef9a and < cc2164ada548addfa8ee215196661c3afe0c5154≥ 2344f17c0a89c181ab1a9fef57fd8c3bddfd6e30 and < 82725be426bce0a425cc5e26fbad61ffd29cff03≥ 90103ccb6e60aa4efe48993d23d6a528472f2233 and < da23752d9660ba7a8ca6c5768fd8776f67f59ee7≥ 4fd3a11804c8877ff11fec59c5c53f1635331e3e and < be01f35efa876eb81cebab2cb0add068b7280ef4≥ 48d9e2e6de01ed35e965eb549758a837c07b601d and < f10defb0be6ac42fb6a97b45920d32da6bd6fde8≥ 55d1cbbbb29e6656c662ee8f73ba1fc4777532eb and < 90e019006644dad35862cb4aa270f561b0732066≥ 55d1cbbbb29e6656c662ee8f73ba1fc4777532eb and < 45917be9f0af339a45b4619f31c902d37b8aed59≥ 55d1cbbbb29e6656c662ee8f73ba1fc4777532eb and < cb7a95af78d29442b8294683eca4897544b8ef46 and 4 moreversion 8c40f2dbae603ef0bd21e87c63f54ec59fd88256version 367296925c7625c3969d2a78d7a3e1dee161beb5≥ 4.9.337 and < 4.10version 5.16 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.17%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- CVSS changed · 7.8
- Source status changed · → Deferred
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
8 on the record
- git.kernel.org/stable/c/82725be426bce0a425cc5e26fbad61ffd29cff03
- git.kernel.org/stable/c/cc2164ada548addfa8ee215196661c3afe0c5154
- git.kernel.org/stable/c/f10defb0be6ac42fb6a97b45920d32da6bd6fde8
- git.kernel.org/stable/c/cb7a95af78d29442b8294683eca4897544b8ef46
- git.kernel.org/stable/c/45917be9f0af339a45b4619f31c902d37b8aed59
- git.kernel.org/stable/c/da23752d9660ba7a8ca6c5768fd8776f67f59ee7
- git.kernel.org/stable/c/90e019006644dad35862cb4aa270f561b0732066
- git.kernel.org/stable/c/be01f35efa876eb81cebab2cb0add068b7280ef4
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 9h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 9h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2023-54130 is "hfs/hfsplus: avoid WARN_ON() for sanity check, use proper error handling", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.