CVE-2025-71230

hfs: ensure sb->s_fs_info is always cleaned up

Published Feb 18, 2026 CVSS 3.1 · 5.5 Medium EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

hfs: ensure sb->s_fs_info is always cleaned up

When hfs was converted to the new mount api a bug was introduced by
changing the allocation pattern of sb->s_fs_info. If setup_bdev_super()
fails after a new superblock has been allocated by sget_fc(), but before
hfs_fill_super() takes ownership of the filesystem-specific s_fs_info
data it was leaked.

Fix this by freeing sb->s_fs_info in hfs_kill_super().

Analysis

AI-generated

Technical impact

When the HFS filesystem was migrated to the new mount API, a bug was introduced that incorrectly managed the allocation of sb->s_fs_info. If the superblock setup fails after allocation but before ownership is transferred by hfs_fill_super(), the allocated structure is never freed and a memory leak occurs. The object remains allocated in kernel memory, leading to gradual exhaustion of free memory with repeated failed mount attempts. The vulnerability does not directly provide code execution or data disclosure, but persistent leaks can degrade system stability over time.

Affected Systems

The flaw affects all Linux kernel releases that include the HFS filesystem implementation. Since the CPE string references the entire Linux kernel and no specific version is listed, any kernel containing the buggy HFS mounting logic is potentially vulnerable.

Risk and Exploitability

The CVSS score of 5.5 classifies the issue as moderate, reflecting that the leak requires local action involving a failed mount operation. The EPSS score of <1% suggests exploitation is unlikely in the wild at the time of this analysis. The vulnerability is not currently listed in the CISA KEV catalog. The attack likely requires a user with the ability to trigger mount operations, potentially elevating privileges through repeated exhaustion, but no direct remote exploitation path is documented. The risk is increased for systems that mount HFS images frequently from untrusted sources or that operate under tight memory constraints.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest kernel update that includes the hfs_kill_super() fix to eliminate the memory leak
  • Reboot the system after installing the updated kernel to ensure all kernel memory is cleared
  • If an immediate kernel update is not possible, consider disabling HFS support or preventing mount attempts of HFS filesystems from untrusted sources

Generated by OpenCVE AI on April 21, 2026 at 15:59 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses NVD-CWE-noinfo
Metrics cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: hfs: ensure sb->s_fs_info is always cleaned up When hfs was converted to the new mount api a bug was introduced by changing the allocation pattern of sb->s_fs_info. If setup_bdev_super() fails after a new superblock has been allocated by sget_fc(), but before hfs_fill_super() takes ownership of the filesystem-specific s_fs_info data it was leaked. Fix this by freeing sb->s_fs_info in hfs_kill_super().
Title hfs: ensure sb->s_fs_info is always cleaned up
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
May 11, 2026, 9:56 PM
Reserved
Feb 18, 2026, 2:25 PM
Status
Analyzed
Published
Feb 18, 2026, 4:22 PM
Modified
Jun 17, 2026, 10:03 AM
Severity
Public date
Feb 18, 2026, 12:00 AM