BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-46299High confidence

hfsplus: fix held lock freed on hfsplus_fill_super()

Linux · Linux

7.0HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.12% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.88-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.176-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.7-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.7-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-35165

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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: <TASK> 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---

What

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: <TASK> 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---

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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: <TASK> 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---

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Improper Locking → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-667 ↗

CWE-667: Improper Locking. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-667
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-1827Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht bekannte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260610Security Bulletin 10 Jun 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 10 Jun 2026, published on 10 June 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46290 Référence CVE CVE-2026-46291 https://www.cve.org/CVERecord?id=CVE-2026-46291 Référence CVE CVE-2026-46292 https://www.cve.org/CVERecord?id=CVE-2026-46292 Référence CVE CVE-2026-46293 https://www.cve.org/CVERecord?id=CVE-2026-46293 Référence CVE CVE-2026-46294 https://www.cve.org/CVERecord?id=CVE-2026-46294 Référence CVE CVE-2026-46295 https://www.cve.org/CVERecord?id=CVE-2026-46295 Référence CVE CVE-2026-46296 https://www.cve.org/CVERecord?id=CVE-2026-46296 Référence CVE CVE-2026-46297 https://www.cve.org/CVERecord?id=CVE-2026-46297 Référence CVE CVE-2026-46298 https://www.cve.org/CVERecord?id=CVE-2026-46298 Référence CVE CVE-2026-46299 https://www.cve.org/CVERecord?id=CVE-2026-46299 Référence CVE CVE-2026-46301 https://www.cve.org/CVERecord?id=CVE-2026-46301 Référence CVE CVE-2026-46302 https://www.cve.org/CVERecord?id=CVE-2026-46302 Référence CVE CVE-2026-46303 https://www.cve.org/CVERecord?id=CVE-2026-46303 Référence CVE CVE-2026-46304 https://www.cve.org/CVERecord?id=CVE-2026-46304 Référence CVE CVE-2026-46305 https://www.cve.org/CVERecord?id=CVE-2026-46305 Référence CVE CVE-2026-46306 https://www.cve.org/CVERecord?id=CVE-2026-46306 Référence CVE CVE-2026-46307 https://www.cve.org/CVERecord?id=CVE-2026-46307 Référence CVE CVE-2026-46308 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46290 Référence CVE CVE-2026-46291 https://www.cve.org/CVERecord?id=CVE-2026-46291 Référence CVE CVE-2026-46292 https://www.cve.org/CVERecord?id=CVE-2026-46292 Référence CVE CVE-2026-46293 https://www.cve.org/CVERecord?id=CVE-2026-46293 Référence CVE CVE-2026-46294 https://www.cve.org/CVERecord?id=CVE-2026-46294 Référence CVE CVE-2026-46295 https://www.cve.org/CVERecord?id=CVE-2026-46295 Référence CVE CVE-2026-46296 https://www.cve.org/CVERecord?id=CVE-2026-46296 Référence CVE CVE-2026-46297 https://www.cve.org/CVERecord?id=CVE-2026-46297 Référence CVE CVE-2026-46298 https://www.cve.org/CVERecord?id=CVE-2026-46298 Référence CVE CVE-2026-46299 https://www.cve.org/CVERecord?id=CVE-2026-46299 Référence CVE CVE-2026-46301 https://www.cve.org/CVERecord?id=CVE-2026-46301 Référence CVE CVE-2026-46302 https://www.cve.org/CVERecord?id=CVE-2026-46302 Référence CVE CVE-2026-46303 https://www.cve.org/CVERecord?id=CVE-2026-46303 Référence CVE CVE-2026-46304 https://www.cve.org/CVERecord?id=CVE-2026-46304 Référence CVE CVE-2026-46305 https://www.cve.org/CVERecord?id=CVE-2026-46305 Référence CVE CVE-2026-46306 https://www.cve.org/CVERecord?id=CVE-2026-46306 Référence CVE CVE-2026-46307 https://www.cve.org/CVERecord?id=CVE-2026-46307 Référence CVE CVE-2026-46308 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1162Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46290 Référence CVE CVE-2026-46291 https://www.cve.org/CVERecord?id=CVE-2026-46291 Référence CVE CVE-2026-46292 https://www.cve.org/CVERecord?id=CVE-2026-46292 Référence CVE CVE-2026-46293 https://www.cve.org/CVERecord?id=CVE-2026-46293 Référence CVE CVE-2026-46294 https://www.cve.org/CVERecord?id=CVE-2026-46294 Référence CVE CVE-2026-46295 https://www.cve.org/CVERecord?id=CVE-2026-46295 Référence CVE CVE-2026-46296 https://www.cve.org/CVERecord?id=CVE-2026-46296 Référence CVE CVE-2026-46297 https://www.cve.org/CVERecord?id=CVE-2026-46297 Référence CVE CVE-2026-46298 https://www.cve.org/CVERecord?id=CVE-2026-46298 Référence CVE CVE-2026-46299 https://www.cve.org/CVERecord?id=CVE-2026-46299 Référence CVE CVE-2026-46301 https://www.cve.org/CVERecord?id=CVE-2026-46301 Référence CVE CVE-2026-46302 https://www.cve.org/CVERecord?id=CVE-2026-46302 Référence CVE CVE-2026-46303 https://www.cve.org/CVERecord?id=CVE-2026-46303 Référence CVE CVE-2026-46304 https://www.cve.org/CVERecord?id=CVE-2026-46304 Référence CVE CVE-2026-46305 https://www.cve.org/CVERecord?id=CVE-2026-46305 Référence CVE CVE-2026-46306 https://www.cve.org/CVERecord?id=CVE-2026-46306 Référence CVE CVE-2026-46307 https://www.cve.org/CVERecord?id=CVE-2026-46307 Référence CVE CVE-2026-46308 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1066Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46290 Référence CVE CVE-2026-46291 https://www.cve.org/CVERecord?id=CVE-2026-46291 Référence CVE CVE-2026-46292 https://www.cve.org/CVERecord?id=CVE-2026-46292 Référence CVE CVE-2026-46293 https://www.cve.org/CVERecord?id=CVE-2026-46293 Référence CVE CVE-2026-46294 https://www.cve.org/CVERecord?id=CVE-2026-46294 Référence CVE CVE-2026-46295 https://www.cve.org/CVERecord?id=CVE-2026-46295 Référence CVE CVE-2026-46296 https://www.cve.org/CVERecord?id=CVE-2026-46296 Référence CVE CVE-2026-46297 https://www.cve.org/CVERecord?id=CVE-2026-46297 Référence CVE CVE-2026-46298 https://www.cve.org/CVERecord?id=CVE-2026-46298 Référence CVE CVE-2026-46299 https://www.cve.org/CVERecord?id=CVE-2026-46299 Référence CVE CVE-2026-46301 https://www.cve.org/CVERecord?id=CVE-2026-46301 Référence CVE CVE-2026-46302 https://www.cve.org/CVERecord?id=CVE-2026-46302 Référence CVE CVE-2026-46303 https://www.cve.org/CVERecord?id=CVE-2026-46303 Référence CVE CVE-2026-46304 https://www.cve.org/CVERecord?id=CVE-2026-46304 Référence CVE CVE-2026-46305 https://www.cve.org/CVERecord?id=CVE-2026-46305 Référence CVE CVE-2026-46306 https://www.cve.org/CVERecord?id=CVE-2026-46306 Référence CVE CVE-2026-46307 https://www.cve.org/CVERecord?id=CVE-2026-46307 Référence CVE CVE-2026-46308 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0954Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46290 Référence CVE CVE-2026-46291 https://www.cve.org/CVERecord?id=CVE-2026-46291 Référence CVE CVE-2026-46292 https://www.cve.org/CVERecord?id=CVE-2026-46292 Référence CVE CVE-2026-46293 https://www.cve.org/CVERecord?id=CVE-2026-46293 Référence CVE CVE-2026-46294 https://www.cve.org/CVERecord?id=CVE-2026-46294 Référence CVE CVE-2026-46295 https://www.cve.org/CVERecord?id=CVE-2026-46295 Référence CVE CVE-2026-46296 https://www.cve.org/CVERecord?id=CVE-2026-46296 Référence CVE CVE-2026-46297 https://www.cve.org/CVERecord?id=CVE-2026-46297 Référence CVE CVE-2026-46298 https://www.cve.org/CVERecord?id=CVE-2026-46298 Référence CVE CVE-2026-46299 https://www.cve.org/CVERecord?id=CVE-2026-46299 Référence CVE CVE-2026-46301 https://www.cve.org/CVERecord?id=CVE-2026-46301 Référence CVE CVE-2026-46302 https://www.cve.org/CVERecord?id=CVE-2026-46302 Référence CVE CVE-2026-46303 https://www.cve.org/CVERecord?id=CVE-2026-46303 Référence CVE CVE-2026-46304 https://www.cve.org/CVERecord?id=CVE-2026-46304 Référence CVE CVE-2026-46305 https://www.cve.org/CVERecord?id=CVE-2026-46305 Référence CVE CVE-2026-46306 https://www.cve.org/CVERecord?id=CVE-2026-46306 Référence CVE CVE-2026-46307 https://www.cve.org/CVERecord?id=CVE-2026-46307 Référence CVE CVE-2026-46308 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0926Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46290 Référence CVE CVE-2026-46291 https://www.cve.org/CVERecord?id=CVE-2026-46291 Référence CVE CVE-2026-46292 https://www.cve.org/CVERecord?id=CVE-2026-46292 Référence CVE CVE-2026-46293 https://www.cve.org/CVERecord?id=CVE-2026-46293 Référence CVE CVE-2026-46294 https://www.cve.org/CVERecord?id=CVE-2026-46294 Référence CVE CVE-2026-46295 https://www.cve.org/CVERecord?id=CVE-2026-46295 Référence CVE CVE-2026-46296 https://www.cve.org/CVERecord?id=CVE-2026-46296 Référence CVE CVE-2026-46297 https://www.cve.org/CVERecord?id=CVE-2026-46297 Référence CVE CVE-2026-46298 https://www.cve.org/CVERecord?id=CVE-2026-46298 Référence CVE CVE-2026-46299 https://www.cve.org/CVERecord?id=CVE-2026-46299 Référence CVE CVE-2026-46300 https://www.cve.org/CVERecord?id=CVE-2026-46300 Référence CVE CVE-2026-46301 https://www.cve.org/CVERecord?id=CVE-2026-46301 Référence CVE CVE-2026-46302 https://www.cve.org/CVERecord?id=CVE-2026-46302 Référence CVE CVE-2026-46303 https://www.cve.org/CVERecord?id=CVE-2026-46303 Référence CVE CVE-2026-46304 https://www.cve.org/CVERecord?id=CVE-2026-46304 Référence CVE CVE-2026-46305 https://www.cve.org/CVERecord?id=CVE-2026-46305 Référence CVE CVE-2026-46306 https://www.cve.org/CVERecord?id=CVE-2026-46306 Référence CVE CVE-2026-46307 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0900Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-46197 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46229 https://www.cve.org/CVERecord?id=CVE-2026-46229 Référence CVE CVE-2026-46243 https://www.cve.org/CVERecord?id=CVE-2026-46243 Référence CVE CVE-2026-46253 https://www.cve.org/CVERecord?id=CVE-2026-46253 Référence CVE CVE-2026-46254 https://www.cve.org/CVERecord?id=CVE-2026-46254 Référence CVE CVE-2026-46266 https://www.cve.org/CVERecord?id=CVE-2026-46266 Référence CVE CVE-2026-46274 https://www.cve.org/CVERecord?id=CVE-2026-46274 Référence CVE CVE-2026-46275 https://www.cve.org/CVERecord?id=CVE-2026-46275 Référence CVE CVE-2026-46299 https://www.cve.org/CVERecord?id=CVE-2026-46299 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-46320 https://www.cve.org/CVERecord?id=CVE-2026-46320 Référence CVE CVE-2026-46328 https://www.cve.org/CVERecord?id=CVE-2026-46328 Référence CVE CVE-2026-46330 https://www.cve.org/CVERecord?id=CVE-2026-46330 Référence CVE CVE-2026-46331 https://www.cve.org/CVERecord?id=CVE-2026-46331 Référence CVE CVE-2026-52909 https://www.cve.org/CVERecord?id=CVE-2026-52909 Référence CVE CVE-2026-52918 https://www.cve.org/CVERecord?id=CVE-2026-52918 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0862Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-46273 Référence CVE CVE-2026-46275 https://www.cve.org/CVERecord?id=CVE-2026-46275 Référence CVE CVE-2026-46276 https://www.cve.org/CVERecord?id=CVE-2026-46276 Référence CVE CVE-2026-46280 https://www.cve.org/CVERecord?id=CVE-2026-46280 Référence CVE CVE-2026-46285 https://www.cve.org/CVERecord?id=CVE-2026-46285 Référence CVE CVE-2026-46291 https://www.cve.org/CVERecord?id=CVE-2026-46291 Référence CVE CVE-2026-46292 https://www.cve.org/CVERecord?id=CVE-2026-46292 Référence CVE CVE-2026-46294 https://www.cve.org/CVERecord?id=CVE-2026-46294 Référence CVE CVE-2026-46296 https://www.cve.org/CVERecord?id=CVE-2026-46296 Référence CVE CVE-2026-46299 https://www.cve.org/CVERecord?id=CVE-2026-46299 Référence CVE CVE-2026-46301 https://www.cve.org/CVERecord?id=CVE-2026-46301 Référence CVE CVE-2026-46303 https://www.cve.org/CVERecord?id=CVE-2026-46303 Référence CVE CVE-2026-46304 https://www.cve.org/CVERecord?id=CVE-2026-46304 Référence CVE CVE-2026-46306 https://www.cve.org/CVERecord?id=CVE-2026-46306 Référence CVE CVE-2026-46307 https://www.cve.org/CVERecord?id=CVE-2026-46307 Référence CVE CVE-2026-46314 https://www.cve.org/CVERecord?id=CVE-2026-46314 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-46320 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0783Multiples vulnérabilités dans Microsoft Azure

ulletin de sécurité Microsoft CVE-2026-10275 du 05 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46274 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46280 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46285 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46287 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46289 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46291 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46292 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46293 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46296 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46299 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46301 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46303 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46304 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46306 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46307 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46312 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46319 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-34180 du 13 juin 2026 Bulletin de sécurité Microsoft CVE-2026-42766 du 13 juin 2026 Bulletin de sécurité Microsoft CVE-2026-42767 du 13 juin 2026 Bulletin de s

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-023175LinuxのLinux Kernelにおけるリソースのロックに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。hfsplus: hfsplus_fill_super()での解放済みロック解放の修正です。hfsplus_fill_super()は検索構造体を初期化するためにhfs_find_init()を呼び出し、この関数内でtree-＞tree_lockを取得します。その後、hfsplus_cat_build_key()の呼び出しが失敗した場合、関数はロックを解放せずにout_put_rootエラーラベルへジャンプします。後続のクリーンアップ処理ではロックが保持されたままtreeデータ構造を解放し、「held lock freed（保持されたロックの解放）」の警告が引き起こされます。この問題は、out_put_rootエラーラベルへジャンプする前に不足していたhfs_find_exit(&fd)の呼び出しを追加することで修正しました。これにより、エラー経路でtree-＞tree_lockが適切に解放されることが保証されます。このバグはv6.13-rc1で開発中の実験的静的解析ツールを用いて最初に検出されており、最新のメインラインカーネルでも持続していることを確認しています。このツールはメモリ管理問題の検出に特化しており、現在も活発に開発中で、一般公開はまだされていません。QEMU上でx86_64 defconfig、lockdep有効、CONFIG_HFSPLUS_FS=yの構成にてランタイムテストを行い、バグの再現を確認しました。エラー経路を誘発するためにGDBを使いhfsplus_asc2uni()の呼び出し前にmax_unistr_lenパラメータを動的に1に縮小しました。これによりhfsplus_asc2uni()は自然に-ENAMETOOLONGを返し、hfsplus_cat_build_key()に伝播して誤ったエラー経路を通る結果となります。マウント処理中に以下の警告が観測されました。=========================WARNING: held lock freed!7.0.0-rc3-00016-gb4f0dd314b39 #4 Not tainted-------------------------mount/174はロックが保持されたままfff...からfff...までのメモリを解放しています！（中略）この問題により、ロックの保持状態に関わる不整合が発生し、システムの安定性や信頼性に影響を及ぼす可能性がありましたが、上記の修正により正常なロック解放が保証されるようになりました。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Linux: 89ac9b4d3d1a049ae1054f99b1aed81092cd0a82 < e890656accee4c26d932ea388eb8936a6e22184d, 89ac9b4d3d1a049ae1054f99b1aed81092cd0a82 < 6499c9c8ec437a369e7e221dad91f6122b50759d, 89ac9b4d3d1a049ae1054f99b1aed81092cd0a82 < c554ddc87af4d4e4be42f8aed1baec9e1c7588e0, 89ac9b4d3d1a049ae1054f99b1aed81092cd0a82 < 3ca80e3012c8be85b4f8d0d20eac8d3b17ff257e, 89ac9b4d3d1a049ae1054f99b1aed81092cd0a82 < 041acda6d9f96006703466449c10c9a69590c8b9, 89ac9b4d3d1a049ae1054f99b1aed81092cd0a82 < d309d3308de658d87c42d97e044c89a226327526, 89ac9b4d3d1a049ae1054f99b1aed81092cd0a82 < bfbcce6a7b0552a390620d9b2c4d2bcb1825cbdc, 89ac9b4d3d1a049ae1054f99b1aed81092cd0a82 < 90c500e4fd83fa33c09bc7ee23b6d9cc487ac733, 3.19
Fixed
Linux: < 3.19, 5.10.259 ≤ 5.10.*, 5.15.210 ≤ 5.15.*, 6.1.176 ≤ 6.1.*, 6.6.140 ≤ 6.6.*, 6.12.88 ≤ 6.12.*, 6.18.30 ≤ 6.18.*, 7.0.7 ≤ 7.0.*, 7.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 8 Jun 2026 · Last source change 5 Aug 2026, 12:31 UTC · CWE-667 · Improper Locking

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-35165
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-35165↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-46299 · cve.blacktree.nl