LiveActive security incident?Get immediate response
CVE Record

CVE-2025-71230: hfs: ensure sb->s_fs_info is always cleaned up

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

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2025-71230 is a Linux kernel HFS filesystem cleanup bug. In a failed mount path, kernel filesystem data can be leaked instead of freed. The public record does not provide CVSS, severity, or active exploitation evidence, so urgency should be based on HFS usage and vendor kernel exposure.

Executive priority

Treat as a kernel maintenance item unless HFS mounting is common or exposed in your environment. There is no source-backed active exploitation signal, but kernel flaws should not remain untracked.

Technical view

The bug was introduced during HFS conversion to the new mount API. If setup_bdev_super() fails after sget_fc() allocates a superblock but before hfs_fill_super() owns sb->s_fs_info, that filesystem-specific data leaks. The fix frees sb->s_fs_info in hfs_kill_super().

Likely exposure

Likely limited to Linux systems running affected kernels with HFS filesystem support and workflows that mount HFS volumes or images. Exact exposure requires mapping distribution kernel packages to the referenced upstream stable fixes.

Exploitation context

The bundle shows no KEV listing and no cited evidence of active exploitation. It describes a kernel memory leak in an HFS mount failure path, but does not provide exploitability, privileges required, or impact beyond the leak.

Researcher notes

Primary evidence is the Linux kernel fix description and stable commit references. The record lacks CVSS, CWE, exploit status, and distro package mapping. Validate impact through kernel configuration, HFS usage, and whether the stable commits are present.

Mitigation direction

  • Check Linux distribution advisories for CVE-2025-71230 fixed kernel packages.
  • Update to a kernel containing the referenced upstream stable fixes.
  • Review whether HFS support is enabled or needed on exposed systems.
  • Avoid mounting untrusted HFS media until vendor guidance is applied.

Validation and detection

  • Inventory Linux kernels and identify systems with HFS filesystem support.
  • Map running kernel packages to vendor advisories or referenced stable commits.
  • Review mount workflows for HFS volumes, images, or removable media.
  • Confirm remediation after patching with vendor package metadata.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-71230 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxffcd06b6d13b72823aba0d7c871f7e4876e7916b, ffcd06b6d13b72823aba0d7c871f7e4876e7916b, ffcd06b6d13b72823aba0d7c871f7e4876e7916bunaffected
LinuxLinux6.13, 0, 6.18.11, 6.19.1, 7.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.