In the Linux kernel, the following vulnerability has been resolved: hfsplus: ensure sb->s_fs_info is always cleaned up When hfsplus was converted to the new mount api…

Code

The project this record applies to. Exploit listings stay in References.

• Repository · git.kernel.org
• Repository · git.kernel.org
• Repository · git.kernel.org

Timeline

Detection, updates, and resolution for this record.

1. May 6, 2026 · NIST NVD

   Detected

   In the Linux kernel, the following vulnerability has been resolved: hfsplus: ensure sb->s_fs_info is always cleaned up When hfsplus 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 hfsplus_fill_super() takes ownership of the filesystem-specific

2. Oct 14, 2026 · NIST NVD

   Updated

   In the Linux kernel, the following vulnerability has been resolved: hfsplus: ensure sb->s_fs_info is always cleaned up When hfsplus 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 hfsplus_fill_super() takes ownership of the filesystem-specific

Affected

• cpe linux/linux kernelversion unspecified

Sources

• CVE.orgVulnerability recordCVE-2025-71271

  Official CVE identifier

  cve.org
• FIRST EPSSExploitation probabilityCVE-2025-71271

  30-day exploitation probability 0.1%

  first.org
• NIST NVDVulnerability recordCVE-2025-71271

  In the Linux kernel, the following vulnerability has been resolved: hfsplus: ensure sb->s_fs_info is always cleaned up When hfsplus 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 n

  nvd.nist.gov

References

• Patch · git.kernel.org
• Patch · git.kernel.org
• Patch · git.kernel.org