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 WARNON() for sanity check, use proper error handling
Commit 55d1cbbbb29e ("hfs/hfsplus: use WARNON for sanity check") fixed a build warning by turning a comment into a WARNON(), 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 WARNON).
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2023-54130?
CVE-2023-54130 has a moderate severity level based on its potential impact in the Linux kernel.
How do I fix CVE-2023-54130?
To address CVE-2023-54130, ensure you update to the latest patched version of the Linux kernel.
What systems are affected by CVE-2023-54130?
CVE-2023-54130 affects various versions of the Linux kernel that utilize the hfs/hfsplus file systems.
What is the nature of the flaw in CVE-2023-54130?
The flaw in CVE-2023-54130 involves a misuse of the WARN_ON() function, which could lead to improper error handling.
Is CVE-2023-54130 a remote code execution vulnerability?
No, CVE-2023-54130 is not classified as a remote code execution vulnerability.