CVE-2026-46299: hfsplus: fix held lock freed on hfsplus_fill_super()

Published Jun 8, 2026
·
Updated

hfsplus: fix held lock freed on hfsplusfillsuper()

Affected Software

9 affected componentsFixes available
Linux Linux kernel (hfsplus)>=6.13-rc1
Microsoft azl3 kernel 6.6.139.1-1<6.6.141.1-1
6.6.141.1-1
Linux Linux kernel>=3.19<5.10.259
Linux Linux kernel>=5.11<5.15.210
Linux Linux kernel>=5.16<6.1.176
Linux Linux kernel>=6.2<6.6.140
Linux Linux kernel>=6.7<6.12.88
Linux Linux kernel>=6.13<6.18.30
Linux Linux kernel>=6.19<7.0.7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.141.1-1
  2. Upgrade

    Upgrade Linux kernel (HFSPlus) to a version that resolves this vulnerability.

    Patch hfsplus: fix held lock freed on hfsplus_fill_super()
  3. Configuration

    In the hfsplus_fill_super() error path, ensure the missing hfs_find_exit(&fd) is called before jumping to the out_put_root label, so tree->tree_lock is properly released and the held lock freed warning is avoided.

    Linux kernel HFSPlus (fs/hfsplus) Add missing hfs_find_exit(&fd) call = before jumping from error label without releasing the lock

Event History

Jun 8, 2026
CVE Published
via MITRE·03:46 PM
Data Sourced
via MITRE·03:46 PM
DescriptionSeverity
Data Sourced
via NVD·05:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jun 10, 2026
Data Sourced
via Microsoft·08:05 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-46299?

CVE-2026-46299 has a risk rating of 12, indicating a critical vulnerability.

2

How do I fix CVE-2026-46299?

To fix CVE-2026-46299, you should apply the latest security updates and patches provided for the Linux kernel.

3

What systems are affected by CVE-2026-46299?

CVE-2026-46299 affects systems running the Linux kernel with hfsplus file system support.

4

What are the potential consequences of CVE-2026-46299?

Exploitation of CVE-2026-46299 could lead to system instability or unauthorized access due to improper lock handling.

5

When was CVE-2026-46299 published?

CVE-2026-46299 was published on June 8, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203