CVE-2026-46299

HIGHPre-NVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-06-08. a secondary CVSS source baseline 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

hfsplus: fix held lock freed on hfsplus_fill_super()

hfsplus_fill_super() calls hfs_find_init() to initialize a search structure, which acquires tree->tree_lock. If the subsequent call to hfsplus_cat_build_key() fails, the function jumps to the out_put_root error label without releasing the lock. The later cleanup path then frees the tree data structure with the lock still held, triggering a held lock freed warning.

Fix this by adding the missing hfs_find_exit(&fd) call before jumping to the out_put_root error label. This ensures that tree->tree_lock is properly released on the error path.

The bug was originally detected on v6.13-rc1 using an experimental static analysis tool we are developing, and we have verified that the issue persists in the latest mainline kernel. The tool is specifically designed to detect memory management issues. It is currently under active development and not yet publicly available.

We confirmed the bug by runtime testing under QEMU with x86_64 defconfig, lockdep enabled, and CONFIG_HFSPLUS_FS=y. To trigger the error path, we used GDB to dynamically shrink the max_unistr_len parameter to 1 before hfsplus_asc2uni() is called. This forces hfsplus_asc2uni() to naturally return -ENAMETOOLONG, which propagates to hfsplus_cat_build_key() and exercises the faulty error path. The following warning was observed during mount:

========================= WARNING: held lock freed! 7.0.0-rc3-00016-gb4f0dd314b39 #4 Not tainted ------------------------- mount/174 is freeing memory ffff888103f92000-ffff888103f92fff, with a lock still held there! ffff888103f920b0 (&tree->tree_lock){+.+.}-{4:4}, at: hfsplus_find_init+0x154/0x1e0 2 locks held by mount/174: #0: ffff888103f960e0 (&type->s_umount_key#42/1){+.+.}-{4:4}, at: alloc_super.constprop.0+0x167/0xa40 #1: ffff888103f920b0 (&tree->tree_lock){+.+.}-{4:4}, at: hfsplus_find_init+0x154/0x1e0

stack backtrace: CPU: 2 UID: 0 PID: 174 Comm: mount Not tainted 7.0.0-rc3-00016-gb4f0dd314b39 #4 PREEMPT(lazy) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014 Call Trace: dump_stack_lvl+0x82/0xd0 debug_check_no_locks_freed+0x13a/0x180 kfree+0x16b/0x510 ? hfsplus_fill_super+0xcb4/0x18a0 hfsplus_fill_super+0xcb4/0x18a0 ? __pfx_hfsplus_fill_super+0x10/0x10 ? srso_return_thunk+0x5/0x5f ? bdev_open+0x65f/0xc30 ? srso_return_thunk+0x5/0x5f ? pointer+0x4ce/0xbf0 ? trace_contention_end+0x11c/0x150 ? __pfx_pointer+0x10/0x10 ? srso_return_thunk+0x5/0x5f ? bdev_open+0x79b/0xc30 ? srso_return_thunk+0x5/0x5f ? srso_return_thunk+0x5/0x5f ? vsnprintf+0x6da/0x1270 ? srso_return_thunk+0x5/0x5f ? __mutex_unlock_slowpath+0x157/0x740 ? __pfx_vsnprintf+0x10/0x10 ? srso_return_thunk+0x5/0x5f ? srso_return_thunk+0x5/0x5f ? mark_held_locks+0x49/0x80 ? srso_return_thunk+0x5/0x5f ? srso_return_thunk+0x5/0x5f ? irqentry_exit+0x17b/0x5e0 ? trace_irq_disable.constprop.0+0x116/0x150 ? __pfx_hfsplus_fill_super+0x10/0x10 ? __pfx_hfsplus_fill_super+0x10/0x10 get_tree_bdev_flags+0x302/0x580 ? __pfx_get_tree_bdev_flags+0x10/0x10 ? vfs_parse_fs_qstr+0x129/0x1a0 ? __pfx_vfs_parse_fs_qstr+0x3/0x10 vfs_get_tree+0x89/0x320 fc_mount+0x10/0x1d0 path_mount+0x5c5/0x21c0 ? __pfx_path_mount+0x10/0x10 ? trace_irq_enable.constprop.0+0x116/0x150 ? trace_irq_enable.constprop.0+0x116/0x150 ? srso_return_thunk+0x5/0x5f ? srso_return_thunk+0x5/0x5f ? kmem_cache_free+0x307/0x540 ? user_path_at+0x51/0x60 ? __x64_sys_mount+0x212/0x280 ? srso_return_thunk+0x5/0x5f __x64_sys_mount+0x212/0x280 ? __pfx___x64_sys_mount+0x10/0x10 ? srso_return_thunk+0x5/0x5f ? trace_irq_enable.constprop.0+0x116/0x150 ? srso_return_thunk+0x5/0x5f do_syscall_64+0x111/0x680 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7ffacad55eae Code: 48 8b 0d 85 1f 0f 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 8 RSP: 002b ---truncated---

CVSS v3
7.0
EG Score
7.0(medium)
EG Risk
36(Track)
EG Risk 36/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity70% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
0.6%
KEV
Not listed

Published

June 8, 2026

Last Modified

July 8, 2026

Advisory Details (5)

Auto-updated Jun 14, 2026
No patch confirmed yet.
generic

hfsplus: fix held lock freed on hfsplus_fill_super() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d309d3308de658d87c42d97e044c89a226327526
generic

hfsplus: fix held lock freed on hfsplus_fill_super() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bfbcce6a7b0552a390620d9b2c4d2bcb1825cbdc
generic

hfsplus: fix held lock freed on hfsplus_fill_super() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/90c500e4fd83fa33c09bc7ee23b6d9cc487ac733
generic

hfsplus: fix held lock freed on hfsplus_fill_super() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3ca80e3012c8be85b4f8d0d20eac8d3b17ff257e
generic

hfsplus: fix held lock freed on hfsplus_fill_super() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/041acda6d9f96006703466449c10c9a69590c8b9

Vendor Advisories for CVE-2026-46299(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 84× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 138 total refreshes for this CVE.

  1. 2026-07-24 14:17 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:17 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-16 17:03 UTCEPSS rescore
  8. 2026-07-16 11:53 UTCVendor advisory
  9. 2026-07-16 11:53 UTCGHSA enrichment
  10. 2026-07-15 22:24 UTCVendor advisory
  11. 2026-07-15 22:24 UTCGHSA enrichment
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-14 16:02 UTCVendor advisory
  14. 2026-07-14 16:02 UTCGHSA enrichment
  15. 2026-07-14 02:47 UTCVendor advisory
  16. 2026-07-14 02:47 UTCGHSA enrichment
  17. 2026-07-13 22:30 UTCEPSS rescore
  18. 2026-07-13 06:13 UTCEPSS rescore
  19. 2026-07-12 12:54 UTCVendor advisory
  20. 2026-07-12 12:54 UTCGHSA enrichment
  21. 2026-07-12 05:46 UTCEPSS rescore
  22. 2026-07-11 23:48 UTCVendor advisory
  23. 2026-07-11 23:48 UTCGHSA enrichment
  24. 2026-07-11 10:41 UTCVendor advisory
  25. 2026-07-11 10:41 UTCGHSA enrichment
Show 75 more
  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-10 21:28 UTCVendor advisory
  3. 2026-07-10 21:28 UTCGHSA enrichment
  4. 2026-07-09 19:10 UTCEPSS rescore
  5. 2026-07-09 05:45 UTCVendor advisory
  6. 2026-07-09 05:45 UTCGHSA enrichment
  7. 2026-07-08 16:29 UTCVendor advisory
  8. 2026-07-08 16:29 UTCGHSA enrichment
  9. 2026-07-08 15:16 UTCEPSS rescore
  10. 2026-07-08 03:24 UTCVendor advisory
  11. 2026-07-08 03:24 UTCGHSA enrichment
  12. 2026-07-07 13:46 UTCEPSS rescore
  13. 2026-07-06 02:23 UTCEPSS rescore
  14. 2026-07-05 17:32 UTCVendor advisory
  15. 2026-07-05 17:31 UTCGHSA enrichment
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 14:58 UTCVendor advisory
  18. 2026-07-04 14:58 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-03 16:25 UTCVendor advisory
  21. 2026-07-03 16:24 UTCGHSA enrichment
  22. 2026-07-03 03:19 UTCVendor advisory
  23. 2026-07-03 03:19 UTCGHSA enrichment
  24. 2026-07-02 14:12 UTCVendor advisory
  25. 2026-07-02 14:12 UTCGHSA enrichment
  26. 2026-07-02 01:08 UTCVendor advisory
  27. 2026-07-02 01:08 UTCGHSA enrichment
  28. 2026-07-01 11:56 UTCVendor advisory
  29. 2026-07-01 11:56 UTCGHSA enrichment
  30. 2026-06-30 23:22 UTCEPSS rescore
  31. 2026-06-30 22:51 UTCVendor advisory
  32. 2026-06-30 22:51 UTCGHSA enrichment
  33. 2026-06-30 09:46 UTCVendor advisory
  34. 2026-06-30 09:45 UTCGHSA enrichment
  35. 2026-06-29 20:40 UTCVendor advisory
  36. 2026-06-29 20:40 UTCGHSA enrichment
  37. 2026-06-29 14:06 UTCEPSS rescore
  38. 2026-06-29 14:06 UTCEPSS rescore
  39. 2026-06-29 07:35 UTCVendor advisory
  40. 2026-06-29 07:34 UTCGHSA enrichment
  41. 2026-06-28 17:09 UTCVendor advisory
  42. 2026-06-28 17:08 UTCGHSA enrichment
  43. 2026-06-28 14:07 UTCEPSS rescore
  44. 2026-06-28 04:56 UTCEPSS rescore
  45. 2026-06-28 04:56 UTCEPSS rescore
  46. 2026-06-28 04:03 UTCVendor advisory
  47. 2026-06-28 04:03 UTCGHSA enrichment
  48. 2026-06-27 14:58 UTCVendor advisory
  49. 2026-06-27 14:58 UTCGHSA enrichment
  50. 2026-06-27 03:08 UTCEPSS rescore
  51. 2026-06-27 01:53 UTCVendor advisory
  52. 2026-06-27 01:53 UTCGHSA enrichment
  53. 2026-06-26 12:47 UTCVendor advisory
  54. 2026-06-26 12:46 UTCGHSA enrichment
  55. 2026-06-25 23:26 UTCVendor advisory
  56. 2026-06-25 23:26 UTCGHSA enrichment
  57. 2026-06-25 13:49 UTCEPSS rescore
  58. 2026-06-25 10:21 UTCVendor advisory
  59. 2026-06-25 10:21 UTCGHSA enrichment
  60. 2026-06-24 21:17 UTCVendor advisory
  61. 2026-06-24 21:17 UTCGHSA enrichment
  62. 2026-06-24 08:05 UTCVendor advisory
  63. 2026-06-24 08:05 UTCGHSA enrichment
  64. 2026-06-23 21:33 UTCEPSS rescore
  65. 2026-06-23 21:33 UTCEPSS rescore
  66. 2026-06-23 16:01 UTCVendor advisory
  67. 2026-06-23 16:01 UTCGHSA enrichment
  68. 2026-06-22 22:44 UTCVendor advisory
  69. 2026-06-22 22:44 UTCGHSA enrichment
  70. 2026-06-22 14:25 UTCEPSS rescore
  71. 2026-06-22 14:25 UTCEPSS rescore
  72. 2026-06-22 05:43 UTCVendor advisory
  73. 2026-06-22 05:43 UTCGHSA enrichment
  74. 2026-06-21 14:56 UTCEPSS rescore
  75. 2026-06-21 14:56 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-46299?
CVE-2026-46299 is a high vulnerability published on June 8, 2026. In the Linux kernel, the following vulnerability has been resolved: hfsplus: fix held lock freed on hfsplusfillsuper() hfsplusfillsuper() calls hfsfindinit() to initialize a search structure, which acquires tree->tree_lock. If the subsequent call to hfspluscatbuildkey() fails, the function jumps to…
When was CVE-2026-46299 disclosed?
CVE-2026-46299 was first published in the National Vulnerability Database on June 8, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46299 actively exploited?
CVE-2026-46299 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46299?
CVE-2026-46299 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-46299?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46299, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-46299

Explore →

Is Your Infrastructure Affected by CVE-2026-46299?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs