CVE-2025-71230
Received Received - Intake
Memory Leak in Linux Kernel HFS Filesystem Superblock Handling

Publication date: 2026-02-18

Last updated on: 2026-03-18

Assigner: kernel.org

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().
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-18
Last Modified
2026-03-18
Generated
2026-05-07
AI Q&A
2026-02-18
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
linux linux_kernel From 6.19 (inc) to 6.19.1 (exc)
linux linux_kernel From 6.13 (inc) to 6.18.11 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability exists in the Linux kernel's HFS filesystem implementation. When the HFS filesystem was converted to use a new mount API, a bug was introduced related to the allocation and cleanup of the sb->s_fs_info data structure. Specifically, if the function setup_bdev_super() fails after a new superblock is allocated by sget_fc(), but before hfs_fill_super() takes ownership of the filesystem-specific s_fs_info data, the s_fs_info data is leaked and not properly freed.

The issue was fixed by ensuring that sb->s_fs_info is always freed in the hfs_kill_super() function, preventing the memory leak.


What immediate steps should I take to mitigate this vulnerability?

I don't know


How can this vulnerability impact me? :

This vulnerability can lead to a memory leak in the Linux kernel when mounting HFS filesystems under certain failure conditions. Over time, repeated failures could cause increased memory usage, potentially leading to resource exhaustion or degraded system performance.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart