Linux Kernel up to 6.0.18/6.1.4 hfsplus memory leak

Summaryinfo

A vulnerability described as critical has been identified in Linux Kernel up to 6.0.18/6.1.4. This affects an unknown part of the component hfsplus. Executing a manipulation can lead to memory leak. This vulnerability appears as CVE-2023-54130. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability has been found in Linux Kernel up to 6.0.18/6.1.4 and classified as critical. This vulnerability affects an unknown code block of the component hfsplus. The manipulation with an unknown input leads to a memory leak vulnerability. The CWE definition for the vulnerability is CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. As an impact it is known to affect availability. CVE summarizes:

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

The advisory is available at git.kernel.org. This vulnerability was named CVE-2023-54130 since 12/24/2025. The technical details are unknown and an exploit is not available.

The vulnerability scanner Nessus provides a plugin with the ID 280041 (Linux Distros Unpatched Vulnerability : CVE-2023-54130), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.0.19 or 6.1.5 eliminates this vulnerability. Applying the patch cc2164ada548addfa8ee215196661c3afe0c5154/82725be426bce0a425cc5e26fbad61ffd29cff03/da23752d9660ba7a8ca6c5768fd8776f67f59ee7/be01f35efa876eb81cebab2cb0add068b7280ef4/f10defb0be6ac42fb6a97b45920d32da6bd6fde8/90e019006644dad35862cb4aa270f561b0732066/45917be9f0af339a45b4619f31c902d37b8aed59/cb7a95af78d29442b8294683eca4897544b8ef46 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (280041) and CERT Bund (WID-SEC-2025-2929). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Affected

• Open Source Linux Kernel

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 6.0.0
• 6.0.1
• 6.0.2
• 6.0.3
• 6.0.4
• 6.0.5
• 6.0.6
• 6.0.7
• 6.0.8
• 6.0.9
• 6.0.10
• 6.0.11
• 6.0.12
• 6.0.13
• 6.0.14
• 6.0.15
• 6.0.16
• 6.0.17
• 6.0.18
• 6.1.0
• 6.1.1
• 6.1.2
• 6.1.3
• 6.1.4

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion