CVE-2026-46299

HIGHPre-NVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-06-08. the CNA's CVSS baseline 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
7.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.0Exploit: None knownExposed: 0

A fix is available — apply it.

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 PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

June 8, 2026

Last Modified

August 5, 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.

Patch Availability(22)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-25ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-25ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1056.57~22.04.2) @ jammy2026-08-25ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-25ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-25ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-25ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-25ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1061.64~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-25ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-25ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-25ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.88-1~bpo12+1 (21 versions)6.12.88-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.7-1~bpo13+1 (133 versions)7.0.7-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(22)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 23× in last 7d / 116× 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 262 total refreshes for this CVE.

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

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 August 5, 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% probability of exploitation in the next 30 days, which ranks it in the top 99.5% of all scored CVEs.
What is the CVSS score of CVE-2026-46299?
CVE-2026-46299 has a CVSS v4.0 base score of 7.0 (CNA self-assessment; NVD's own analysis pending).
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

See which npm, PyPI, Go, and Maven packages are affected by 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