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

Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref

Linux · Linux

8.8HighCVSS 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 17 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:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.26% 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: Within 30 daysRemediation target: Within 180 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 17 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.

22 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 17 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.100-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.187-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.100-1~deb12u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.4-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-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-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
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-64434 · CSAF 2.0 · revision 14 · interimSUSE Product Security TeamCVE-2026-64434
75 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.1
Summary
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref l2cap_chan_timeout() runs asynchronously and accesses chan->conn. If the connection is torn down while the timer is running or pending, chan->conn can be freed, leading to a use-after-free when the timer worker attempts to lock conn->lock: | BUG: KASAN: slab-use-after-free in instrument_atomic_read_write include/linux/instrumented.h:112 [inline] | BUG: KASAN: slab-use-after-free in atomic_long_try_cmpxchg_acquire include/linux/atomic/atomic-instrumented.h:4456 [inline] | BUG: KASAN: slab-use-after-free in __mutex_trylock_fast kernel/locking/mutex.c:161 [inline] | BUG: KASAN: slab-use-after-free in mutex_lock+0x4f/0xa0 kernel/locking/mutex.c:318 | Write of size 8 at addr ffff8881298d9550 by task kworker/2:1/83 | | CPU: 2 UID: 0 PID: 83 Comm: kworker/2:1 Not tainted 7.1.0-rc6-next-20260601-dirty #6 PREEMPT(full) | Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014 | Workqueue: events l2cap_chan_timeout | Call Trace: | | instrument_atomic_read_write include/linux/instrumented.h:112 [inline] | atomic_long_try_cmpxchg_acquire include/linux/atomic/atomic-instrumented.h:4456 [inline] | __mutex_trylock_fast kernel/locking/mutex.c:161 [inline] | mutex_lock+0x4f/0xa0 kernel/locking/mutex.c:318 | l2cap_chan_timeout+0x5d/0x1b0 net/bluetooth/l2cap_core.c:422 | process_one_work kernel/workqueue.c:3326 [inline] | process_scheduled_works+0x7c8/0xfb0 kernel/workqueue.c:3409 | worker_thread+0x8a9/0xcf0 kernel/workqueue.c:3490 | kthread+0x346/0x430 kernel/kthread.c:436 | ret_from_fork+0x1a3/0x470 arch/x86/kernel/process.c:158 | ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 | | | Allocated by task 320: | l2cap_conn_add+0xa7/0x820 net/bluetooth/l2cap_core.c:7075 | l2cap_connect_cfm+0xdb/0xd70 net/bluetooth/l2cap_core.c:7452 | hci_connect_cfm include/net/bluetooth/hci_core.h:2139 [inline] | hci_remote_features_evt+0x52f/0x9f0 net/bluetooth/hci_event.c:3760 | hci_event_func net/bluetooth/hci_event.c:7796 [inline] | hci_event_packet+0x561/0xa70 net/bluetooth/hci_event.c:7847 | hci_rx_work+0x370/0x890 net/bluetooth/hci_core.c:4040 | process_one_work kernel/workqueue.c:3326 [inline] | process_scheduled_works+0x7c8/0xfb0 kernel/workqueue.c:3409 | worker_thread+0x8a9/0xcf0 kernel/workqueue.c:3490 | kthread+0x346/0x430 kernel/kthread.c:436 | ret_from_fork+0x1a3/0x470 arch/x86/kernel/process.c:158 | ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 | | Freed by task 322: | hci_disconn_cfm include/net/bluetooth/hci_core.h:2154 [inline] | hci_conn_hash_flush+0x101/0x1f0 net/bluetooth/hci_conn.c:2736 | hci_dev_close_sync+0x889/0xde0 net/bluetooth/hci_sync.c:5405 | hci_dev_do_close net/bluetooth/hci_core.c:502 [inline] | hci_unregister_dev+0x1f7/0x370 net/bluetooth/hci_core.c:2679 | vhci_release+0x12a/0x180 drivers/bluetooth/hci_vhci.c:690 | __fput+0x369/0x890 fs/file_table.c:510 | task_work_run+0x160/0x1d0 kernel/task_work.c:233 | get_signal+0xf5b/0x1120 kernel/signal.c:2810 | arch_do_signal_or_restart+0x4d/0x600 arch/x86/kernel/signal.c:337 | __exit_to_user_mode_loop kernel/entry/common.c:64 [inline] | exit_to_user_mode_loop+0x85/0x510 kernel/entry/common.c:98 | do_syscall_64+0x263/0x3d0 arch/x86/entry/syscall_64.c:100 | entry_SYSCALL_64_after_hwframe+0x77/0x7f | | The buggy address belongs to the object at ffff8881298d9400 | which belongs to the cache kmalloc-512 of size 512 | The buggy address is located 336 bytes inside of | freed 512-byte region [ffff8881298d9400, ffff8881298d9600) Fix it by having chan->conn hold a reference to l2cap_conn (via l2cap_conn_get) when the channel is added to the connection, and releasing it in the channel destructor. This ensures the l2cap_conn remains alive as long as the channel exists. A new FLAG_DEL channel flag is introduced to indicate that the ch ---truncated---
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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-48778

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref l2cap_chan_timeout() runs asynchronously and accesses chan->conn. If the connection is torn down while the timer is running or pending, chan->conn can be freed, leading to a use-after-free when the timer worker attempts to lock conn->lock: | BUG: KASAN: slab-use-after-free in instrument_atomic_read_write include/linux/instrumented.h:112 [inline] | BUG: KASAN: slab-use-after-free in atomic_long_try_cmpxchg_acquire include/linux/atomic/atomic-instrumented.h:4456 [inline] | BUG: KASAN: slab-use-after-free in __mutex_trylock_fast kernel/locking/mutex.c:161 [inline] | BUG: KASAN: slab-use-after-free in mutex_lock+0x4f/0xa0 kernel/locking/mutex.c:318 | Write of size 8 at addr ffff8881298d9550 by task kworker/2:1/83 | | CPU: 2 UID: 0 PID: 83 Comm: kworker/2:1 Not tainted 7.1.0-rc6-next-20260601-dirty #6 PREEMPT(full) | Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014 | Workqueue: events l2cap_chan_timeout | Call Trace: | <TASK> | instrument_atomic_read_write include/linux/instrumented.h:112 [inline] | atomic_long_try_cmpxchg_acquire include/linux/atomic/atomic-instrumented.h:4456 [inline] | __mutex_trylock_fast kernel/locking/mutex.c:161 [inline] | mutex_lock+0x4f/0xa0 kernel/locking/mutex.c:318 | l2cap_chan_timeout+0x5d/0x1b0 net/bluetooth/l2cap_core.c:422 | process_one_work kernel/workqueue.c:3326 [inline] | process_scheduled_works+0x7c8/0xfb0 kernel/workqueue.c:3409 | worker_thread+0x8a9/0xcf0 kernel/workqueue.c:3490 | kthread+0x346/0x430 kernel/kthread.c:436 | ret_from_fork+0x1a3/0x470 arch/x86/kernel/process.c:158 | ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 | </TASK> | | Allocated by task 320: | l2cap_conn_add+0xa7/0x820 net/bluetooth/l2cap_core.c:7075 | l2cap_connect_cfm+0xdb/0xd70 net/bluetooth/l2cap_core.c:7452 | hci_connect_cfm include/net/bluetooth/hci_core.h:2139 [inline] | hci_remote_features_evt+0x52f/0x9f0 net/bluetooth/hci_event.c:3760 | hci_event_func net/bluetooth/hci_event.c:7796 [inline] | hci_event_packet+0x561/0xa70 net/bluetooth/hci_event.c:7847 | hci_rx_work+0x370/0x890 net/bluetooth/hci_core.c:4040 | process_one_work kernel/workqueue.c:3326 [inline] | process_scheduled_works+0x7c8/0xfb0 kernel/workqueue.c:3409 | worker_thread+0x8a9/0xcf0 kernel/workqueue.c:3490 | kthread+0x346/0x430 kernel/kthread.c:436 | ret_from_fork+0x1a3/0x470 arch/x86/kernel/process.c:158 | ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 | | Freed by task 322: | hci_disconn_cfm include/net/bluetooth/hci_core.h:2154 [inline] | hci_conn_hash_flush+0x101/0x1f0 net/bluetooth/hci_conn.c:2736 | hci_dev_close_sync+0x889/0xde0 net/bluetooth/hci_sync.c:5405 | hci_dev_do_close net/bluetooth/hci_core.c:502 [inline] | hci_unregister_dev+0x1f7/0x370 net/bluetooth/hci_core.c:2679 | vhci_release+0x12a/0x180 drivers/bluetooth/hci_vhci.c:690 | __fput+0x369/0x890 fs/file_table.c:510 | task_work_run+0x160/0x1d0 kernel/task_work.c:233 | get_signal+0xf5b/0x1120 kernel/signal.c:2810 | arch_do_signal_or_restart+0x4d/0x600 arch/x86/kernel/signal.c:337 | __exit_to_user_mode_loop kernel/entry/common.c:64 [inline] | exit_to_user_mode_loop+0x85/0x510 kernel/entry/common.c:98 | do_syscall_64+0x263/0x3d0 arch/x86/entry/syscall_64.c:100 | entry_SYSCALL_64_after_hwframe+0x77/0x7f | | The buggy address belongs to the object at ffff8881298d9400 | which belongs to the cache kmalloc-512 of size 512 | The buggy address is located 336 bytes inside of | freed 512-byte region [ffff8881298d9400, ffff8881298d9600) Fix it by having chan->conn hold a reference to l2cap_conn (via l2cap_conn_get) when the channel is added to the connection, and releasing it in the channel destructor. This ensures the l2cap_conn remains alive as long as the channel exists. A new FLAG_DEL channel flag is introduced to indicate that the ch ---truncated---

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
8.8 · CVSS 3.1
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 17 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: Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref l2cap_chan_timeout() runs asynchronously and accesses chan->conn. If the connection is torn down while the timer is running or pending, chan->conn can be freed, leading to a use-after-free when the timer worker attempts to lock conn->lock: | BUG: KASAN: slab-use-after-free in instrument_atomic_read_write include/linux/instrumented.h:112 [inline] | BUG: KASAN: slab-use-after-free in atomic_long_try_cmpxchg_acquire include/linux/atomic/atomic-instrumented.h:4456 [inline] | BUG: KASAN: slab-use-after-free in __mutex_trylock_fast kernel/locking/mutex.c:161 [inline] | BUG: KASAN: slab-use-after-free in mutex_lock+0x4f/0xa0 kernel/locking/mutex.c:318 | Write of size 8 at addr ffff8881298d9550 by task kworker/2:1/83 | | CPU: 2 UID: 0 PID: 83 Comm: kworker/2:1 Not tainted 7.1.0-rc6-next-20260601-dirty #6 PREEMPT(full) | Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014 | Workqueue: events l2cap_chan_timeout | Call Trace: | <TASK> | instrument_atomic_read_write include/linux/instrumented.h:112 [inline] | atomic_long_try_cmpxchg_acquire include/linux/atomic/atomic-instrumented.h:4456 [inline] | __mutex_trylock_fast kernel/locking/mutex.c:161 [inline] | mutex_lock+0x4f/0xa0 kernel/locking/mutex.c:318 | l2cap_chan_timeout+0x5d/0x1b0 net/bluetooth/l2cap_core.c:422 | process_one_work kernel/workqueue.c:3326 [inline] | process_scheduled_works+0x7c8/0xfb0 kernel/workqueue.c:3409 | worker_thread+0x8a9/0xcf0 kernel/workqueue.c:3490 | kthread+0x346/0x430 kernel/kthread.c:436 | ret_from_fork+0x1a3/0x470 arch/x86/kernel/process.c:158 | ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 | </TASK> | | Allocated by task 320: | l2cap_conn_add+0xa7/0x820 net/bluetooth/l2cap_core.c:7075 | l2cap_connect_cfm+0xdb/0xd70 net/bluetooth/l2cap_core.c:7452 | hci_connect_cfm include/net/bluetooth/hci_core.h:2139 [inline] | hci_remote_features_evt+0x52f/0x9f0 net/bluetooth/hci_event.c:3760 | hci_event_func net/bluetooth/hci_event.c:7796 [inline] | hci_event_packet+0x561/0xa70 net/bluetooth/hci_event.c:7847 | hci_rx_work+0x370/0x890 net/bluetooth/hci_core.c:4040 | process_one_work kernel/workqueue.c:3326 [inline] | process_scheduled_works+0x7c8/0xfb0 kernel/workqueue.c:3409 | worker_thread+0x8a9/0xcf0 kernel/workqueue.c:3490 | kthread+0x346/0x430 kernel/kthread.c:436 | ret_from_fork+0x1a3/0x470 arch/x86/kernel/process.c:158 | ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 | | Freed by task 322: | hci_disconn_cfm include/net/bluetooth/hci_core.h:2154 [inline] | hci_conn_hash_flush+0x101/0x1f0 net/bluetooth/hci_conn.c:2736 | hci_dev_close_sync+0x889/0xde0 net/bluetooth/hci_sync.c:5405 | hci_dev_do_close net/bluetooth/hci_core.c:502 [inline] | hci_unregister_dev+0x1f7/0x370 net/bluetooth/hci_core.c:2679 | vhci_release+0x12a/0x180 drivers/bluetooth/hci_vhci.c:690 | __fput+0x369/0x890 fs/file_table.c:510 | task_work_run+0x160/0x1d0 kernel/task_work.c:233 | get_signal+0xf5b/0x1120 kernel/signal.c:2810 | arch_do_signal_or_restart+0x4d/0x600 arch/x86/kernel/signal.c:337 | __exit_to_user_mode_loop kernel/entry/common.c:64 [inline] | exit_to_user_mode_loop+0x85/0x510 kernel/entry/common.c:98 | do_syscall_64+0x263/0x3d0 arch/x86/entry/syscall_64.c:100 | entry_SYSCALL_64_after_hwframe+0x77/0x7f | | The buggy address belongs to the object at ffff8881298d9400 | which belongs to the cache kmalloc-512 of size 512 | The buggy address is located 336 bytes inside of | freed 512-byte region [ffff8881298d9400, ffff8881298d9600) Fix it by having chan->conn hold a reference to l2cap_conn (via l2cap_conn_get) when the channel is added to the connection, and releasing it in the channel destructor. This ensures the l2cap_conn remains alive as long as the channel exists. A new FLAG_DEL channel flag is introduced to indicate that the ch ---truncated---

What

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref l2cap_chan_timeout() runs asynchronously and accesses chan->conn. If the connection is torn down while the timer is running or pending, chan->conn can be freed, leading to a use-after-free when the timer worker attempts to lock conn->lock: | BUG: KASAN: slab-use-after-free in instrument_atomic_read_write include/linux/instrumented.h:112 [inline] | BUG: KASAN: slab-use-after-free in atomic_long_try_cmpxchg_acquire include/linux/atomic/atomic-instrumented.h:4456 [inline] | BUG: KASAN: slab-use-after-free in __mutex_trylock_fast kernel/locking/mutex.c:161 [inline] | BUG: KASAN: slab-use-after-free in mutex_lock+0x4f/0xa0 kernel/locking/mutex.c:318 | Write of size 8 at addr ffff8881298d9550 by task kworker/2:1/83 | | CPU: 2 UID: 0 PID: 83 Comm: kworker/2:1 Not tainted 7.1.0-rc6-next-20260601-dirty #6 PREEMPT(full) | Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014 | Workqueue: events l2cap_chan_timeout | Call Trace: | <TASK> | instrument_atomic_read_write include/linux/instrumented.h:112 [inline] | atomic_long_try_cmpxchg_acquire include/linux/atomic/atomic-instrumented.h:4456 [inline] | __mutex_trylock_fast kernel/locking/mutex.c:161 [inline] | mutex_lock+0x4f/0xa0 kernel/locking/mutex.c:318 | l2cap_chan_timeout+0x5d/0x1b0 net/bluetooth/l2cap_core.c:422 | process_one_work kernel/workqueue.c:3326 [inline] | process_scheduled_works+0x7c8/0xfb0 kernel/workqueue.c:3409 | worker_thread+0x8a9/0xcf0 kernel/workqueue.c:3490 | kthread+0x346/0x430 kernel/kthread.c:436 | ret_from_fork+0x1a3/0x470 arch/x86/kernel/process.c:158 | ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 | </TASK> | | Allocated by task 320: | l2cap_conn_add+0xa7/0x820 net/bluetooth/l2cap_core.c:7075 | l2cap_connect_cfm+0xdb/0xd70 net/bluetooth/l2cap_core.c:7452 | hci_connect_cfm include/net/bluetooth/hci_core.h:2139 [inline] | hci_remote_features_evt+0x52f/0x9f0 net/bluetooth/hci_event.c:3760 | hci_event_func net/bluetooth/hci_event.c:7796 [inline] | hci_event_packet+0x561/0xa70 net/bluetooth/hci_event.c:7847 | hci_rx_work+0x370/0x890 net/bluetooth/hci_core.c:4040 | process_one_work kernel/workqueue.c:3326 [inline] | process_scheduled_works+0x7c8/0xfb0 kernel/workqueue.c:3409 | worker_thread+0x8a9/0xcf0 kernel/workqueue.c:3490 | kthread+0x346/0x430 kernel/kthread.c:436 | ret_from_fork+0x1a3/0x470 arch/x86/kernel/process.c:158 | ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 | | Freed by task 322: | hci_disconn_cfm include/net/bluetooth/hci_core.h:2154 [inline] | hci_conn_hash_flush+0x101/0x1f0 net/bluetooth/hci_conn.c:2736 | hci_dev_close_sync+0x889/0xde0 net/bluetooth/hci_sync.c:5405 | hci_dev_do_close net/bluetooth/hci_core.c:502 [inline] | hci_unregister_dev+0x1f7/0x370 net/bluetooth/hci_core.c:2679 | vhci_release+0x12a/0x180 drivers/bluetooth/hci_vhci.c:690 | __fput+0x369/0x890 fs/file_table.c:510 | task_work_run+0x160/0x1d0 kernel/task_work.c:233 | get_signal+0xf5b/0x1120 kernel/signal.c:2810 | arch_do_signal_or_restart+0x4d/0x600 arch/x86/kernel/signal.c:337 | __exit_to_user_mode_loop kernel/entry/common.c:64 [inline] | exit_to_user_mode_loop+0x85/0x510 kernel/entry/common.c:98 | do_syscall_64+0x263/0x3d0 arch/x86/entry/syscall_64.c:100 | entry_SYSCALL_64_after_hwframe+0x77/0x7f | | The buggy address belongs to the object at ffff8881298d9400 | which belongs to the cache kmalloc-512 of size 512 | The buggy address is located 336 bytes inside of | freed 512-byte region [ffff8881298d9400, ffff8881298d9600) Fix it by having chan->conn hold a reference to l2cap_conn (via l2cap_conn_get) when the channel is added to the connection, and releasing it in the channel destructor. This ensures the l2cap_conn remains alive as long as the channel exists. A new FLAG_DEL channel flag is introduced to indicate that the ch ---truncated---

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through an adjacent network may attempt exploitation without authentication or user interaction. 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: Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref l2cap_chan_timeout() runs asynchronously and accesses chan->conn. If the connection is torn down while the timer is running or pending, chan->conn can be freed, leading to a use-after-free when the timer worker attempts to lock conn->lock: | BUG: KASAN: slab-use-after-free in instrument_atomic_read_write include/linux/instrumented.h:112 [inline] | BUG: KASAN: slab-use-after-free in atomic_long_try_cmpxchg_acquire include/linux/atomic/atomic-instrumented.h:4456 [inline] | BUG: KASAN: slab-use-after-free in __mutex_trylock_fast kernel/locking/mutex.c:161 [inline] | BUG: KASAN: slab-use-after-free in mutex_lock+0x4f/0xa0 kernel/locking/mutex.c:318 | Write of size 8 at addr ffff8881298d9550 by task kworker/2:1/83 | | CPU: 2 UID: 0 PID: 83 Comm: kworker/2:1 Not tainted 7.1.0-rc6-next-20260601-dirty #6 PREEMPT(full) | Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014 | Workqueue: events l2cap_chan_timeout | Call Trace: | <TASK> | instrument_atomic_read_write include/linux/instrumented.h:112 [inline] | atomic_long_try_cmpxchg_acquire include/linux/atomic/atomic-instrumented.h:4456 [inline] | __mutex_trylock_fast kernel/locking/mutex.c:161 [inline] | mutex_lock+0x4f/0xa0 kernel/locking/mutex.c:318 | l2cap_chan_timeout+0x5d/0x1b0 net/bluetooth/l2cap_core.c:422 | process_one_work kernel/workqueue.c:3326 [inline] | process_scheduled_works+0x7c8/0xfb0 kernel/workqueue.c:3409 | worker_thread+0x8a9/0xcf0 kernel/workqueue.c:3490 | kthread+0x346/0x430 kernel/kthread.c:436 | ret_from_fork+0x1a3/0x470 arch/x86/kernel/process.c:158 | ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 | </TASK> | | Allocated by task 320: | l2cap_conn_add+0xa7/0x820 net/bluetooth/l2cap_core.c:7075 | l2cap_connect_cfm+0xdb/0xd70 net/bluetooth/l2cap_core.c:7452 | hci_connect_cfm include/net/bluetooth/hci_core.h:2139 [inline] | hci_remote_features_evt+0x52f/0x9f0 net/bluetooth/hci_event.c:3760 | hci_event_func net/bluetooth/hci_event.c:7796 [inline] | hci_event_packet+0x561/0xa70 net/bluetooth/hci_event.c:7847 | hci_rx_work+0x370/0x890 net/bluetooth/hci_core.c:4040 | process_one_work kernel/workqueue.c:3326 [inline] | process_scheduled_works+0x7c8/0xfb0 kernel/workqueue.c:3409 | worker_thread+0x8a9/0xcf0 kernel/workqueue.c:3490 | kthread+0x346/0x430 kernel/kthread.c:436 | ret_from_fork+0x1a3/0x470 arch/x86/kernel/process.c:158 | ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 | | Freed by task 322: | hci_disconn_cfm include/net/bluetooth/hci_core.h:2154 [inline] | hci_conn_hash_flush+0x101/0x1f0 net/bluetooth/hci_conn.c:2736 | hci_dev_close_sync+0x889/0xde0 net/bluetooth/hci_sync.c:5405 | hci_dev_do_close net/bluetooth/hci_core.c:502 [inline] | hci_unregister_dev+0x1f7/0x370 net/bluetooth/hci_core.c:2679 | vhci_release+0x12a/0x180 drivers/bluetooth/hci_vhci.c:690 | __fput+0x369/0x890 fs/file_table.c:510 | task_work_run+0x160/0x1d0 kernel/task_work.c:233 | get_signal+0xf5b/0x1120 kernel/signal.c:2810 | arch_do_signal_or_restart+0x4d/0x600 arch/x86/kernel/signal.c:337 | __exit_to_user_mode_loop kernel/entry/common.c:64 [inline] | exit_to_user_mode_loop+0x85/0x510 kernel/entry/common.c:98 | do_syscall_64+0x263/0x3d0 arch/x86/entry/syscall_64.c:100 | entry_SYSCALL_64_after_hwframe+0x77/0x7f | | The buggy address belongs to the object at ffff8881298d9400 | which belongs to the cache kmalloc-512 of size 512 | The buggy address is located 336 bytes inside of | freed 512-byte region [ffff8881298d9400, ffff8881298d9600) Fix it by having chan->conn hold a reference to l2cap_conn (via l2cap_conn_get) when the channel is added to the connection, and releasing it in the channel destructor. This ensures the l2cap_conn remains alive as long as the channel exists. A new FLAG_DEL channel flag is introduced to indicate that the ch ---truncated---

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through an adjacent network may attempt exploitation without authentication or user interaction. 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
an adjacent network → Use After Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Adjacent
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
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-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:A/AC:L/PR:N/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.

AVAdjacentAttack vector: The attacker must be on an adjacent or logically close network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing 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
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
UnauthenticatedCWE-416
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-48778Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref l2cap_chan_timeout() runs asynchronously and accesses chan->conn. If the connection is torn down while the timer is running or pending, chan->conn can be freed, leading to a use-after-free when the timer worker attempts to lock conn->lock: | BUG: KASAN: slab-use-after-free in instrument_atomic_read_write include/linux/instrumented.h:112 [inline] | BUG: KASAN: slab-use-after-free in atomic_long_try_cmpxchg_acquire include/linux/atomic/atomic-instrumented.h:4456 [inline] | BUG: KASAN: slab-use-after-free in __mutex_trylock_fast kernel/locking/mutex.c:161 [inline] | BUG: KASAN: slab-use-after-free in mutex_lock+0x4f/0xa0 kernel/locking/mutex.c:318 | Write of size 8 at addr ffff8881298d9550 by task kworker/2:1/83 | | CPU: 2 UID: 0 PID: 83 Comm: kworker/2:1 Not tainted 7.1.0-rc6-next-20260601-dirty #6 PREEMPT(full) | Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014 | Workqueue: events l2cap_chan_timeout | Call Trace: | <TASK> | instrument_atomic_read_write include/linux/instrumented.h:112 [inline] | atomic_long_try_cmpxchg_acquire include/linux/atomic/atomic-instrumented.h:4456 [inline] | __mutex_trylock_fast kernel/locking/mutex.c:161 [inline] | mutex_lock+0x4f/0xa0 kernel/locking/mutex.c:318 | l2cap_chan_timeout+0x5d/0x1b0 net/bluetooth/l2cap_core.c:422 | process_one_work kernel/workqueue.c:3326 [inline] | process_scheduled_works+0x7c8/0xfb0 kernel/workqueue.c:3409 | worker_thread+0x8a9/0xcf0 kernel/workqueue.c:3490 | kthread+0x346/0x430 kernel/kthread.c:436 | ret_from_fork+0x1a3/0x470 arch/x86/kernel/process.c:158 | ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 | </TASK> | | Allocated by task 320: | l2cap_conn_add+0xa7/0x820 net/bluetooth/l2cap_core.c:7075 | l2cap_connect_cfm+0xdb/0xd70 net/bluetooth/l2cap_core.c:7452 | hci_connect_cfm include/net/bluetooth/hci_core.h:2139 [inline] | hci_remote_features_evt+0x52f/0x9f0 net/bluetooth/hci_event.c:3760 | hci_event_func net/bluetooth/hci_event.c:7796 [inline] | hci_event_packet+0x561/0xa70 net/bluetooth/hci_event.c:7847 | hci_rx_work+0x370/0x890 net/bluetooth/hci_core.c:4040 | process_one_work kernel/workqueue.c:3326 [inline] | process_scheduled_works+0x7c8/0xfb0 kernel/workqueue.c:3409 | worker_thread+0x8a9/0xcf0 kernel/workqueue.c:3490 | kthread+0x346/0x430 kernel/kthread.c:436 | ret_from_fork+0x1a3/0x470 arch/x86/kernel/process.c:158 | ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 | | Freed by task 322: | hci_disconn_cfm include/net/bluetooth/hci_core.h:2154 [inline] | hci_conn_hash_flush+0x101/0x1f0 net/bluetooth/hci_conn.c:2736 | hci_dev_close_sync+0x889/0xde0 net/bluetooth/hci_sync.c:5405 | hci_dev_do_close net/bluetooth/hci_core.c:502 [inline] | hci_unregister_dev+0x1f7/0x370 net/bluetooth/hci_core.c:2679 | vhci_release+0x12a/0x180 drivers/bluetooth/hci_vhci.c:690 | __fput+0x369/0x890 fs/file_table.c:510 | task_work_run+0x160/0x1d0 kernel/task_work.c:233 | get_signal+0xf5b/0x1120 kernel/signal.c:2810 | arch_do_signal_or_restart+0x4d/0x600 arch/x86/kernel/signal.c:337 | __exit_to_user_mode_loop kernel/entry/common.c:64 [inline] | exit_to_user_mode_loop+0x85/0x510 kernel/entry/common.c:98 | do_syscall_64+0x263/0x3d0 arch/x86/entry/syscall_64.c:100 | entry_SYSCALL_64_after_hwframe+0x77/0x7f | | The buggy address belongs to the object at ffff8881298d9400 | which belongs to the cache kmalloc-512 of size 512 | The buggy address is located 336 bytes inside of | freed 512-byte region [ffff8881298d9400, ffff8881298d9600) Fix it by having chan->conn hold a reference to l2cap_conn (via l2cap_conn_get) when the channel is added to the connection, and releasing it in the channel destructor. This ensures the l2cap_conn remains alive as long as the channel exists. A new FLAG_DEL channel flag is introduced to indicate that the ch ---truncated---

Official EUVD record ↗
BSI · German · WID-SEC-2026-2527Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260729Security Bulletin 29 Jul 2026

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

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

d?id=CVE-2026-64412 Référence CVE CVE-2026-64415 https://www.cve.org/CVERecord?id=CVE-2026-64415 Référence CVE CVE-2026-64416 https://www.cve.org/CVERecord?id=CVE-2026-64416 Référence CVE CVE-2026-64420 https://www.cve.org/CVERecord?id=CVE-2026-64420 Référence CVE CVE-2026-64421 https://www.cve.org/CVERecord?id=CVE-2026-64421 Référence CVE CVE-2026-64423 https://www.cve.org/CVERecord?id=CVE-2026-64423 Référence CVE CVE-2026-64427 https://www.cve.org/CVERecord?id=CVE-2026-64427 Référence CVE CVE-2026-64429 https://www.cve.org/CVERecord?id=CVE-2026-64429 Référence CVE CVE-2026-64433 https://www.cve.org/CVERecord?id=CVE-2026-64433 Référence CVE CVE-2026-64434 https://www.cve.org/CVERecord?id=CVE-2026-64434 Référence CVE CVE-2026-64436 https://www.cve.org/CVERecord?id=CVE-2026-64436 Référence CVE CVE-2026-64440 https://www.cve.org/CVERecord?id=CVE-2026-64440 Référence CVE CVE-2026-64442 https://www.cve.org/CVERecord?id=CVE-2026-64442 Référence CVE CVE-2026-64443 https://www.cve.org/CVERecord?id=CVE-2026-64443 Référence CVE CVE-2026-64444 https://www.cve.org/CVERecord?id=CVE-2026-64444 Référence CVE CVE-2026-64445 https://www.cve.org/CVERecord?id=CVE-2026-64445 Référence CVE CVE-2026-64446 https://www.cve.org/CVERecord?id=CVE-2026-64446 Référence CVE CVE-2026-64450 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-64423 Référence CVE CVE-2026-64424 https://www.cve.org/CVERecord?id=CVE-2026-64424 Référence CVE CVE-2026-64425 https://www.cve.org/CVERecord?id=CVE-2026-64425 Référence CVE CVE-2026-64426 https://www.cve.org/CVERecord?id=CVE-2026-64426 Référence CVE CVE-2026-64428 https://www.cve.org/CVERecord?id=CVE-2026-64428 Référence CVE CVE-2026-64429 https://www.cve.org/CVERecord?id=CVE-2026-64429 Référence CVE CVE-2026-64430 https://www.cve.org/CVERecord?id=CVE-2026-64430 Référence CVE CVE-2026-64432 https://www.cve.org/CVERecord?id=CVE-2026-64432 Référence CVE CVE-2026-64433 https://www.cve.org/CVERecord?id=CVE-2026-64433 Référence CVE CVE-2026-64434 https://www.cve.org/CVERecord?id=CVE-2026-64434 Référence CVE CVE-2026-64435 https://www.cve.org/CVERecord?id=CVE-2026-64435 Référence CVE CVE-2026-64436 https://www.cve.org/CVERecord?id=CVE-2026-64436 Référence CVE CVE-2026-64438 https://www.cve.org/CVERecord?id=CVE-2026-64438 Référence CVE CVE-2026-64439 https://www.cve.org/CVERecord?id=CVE-2026-64439 Référence CVE CVE-2026-64440 https://www.cve.org/CVERecord?id=CVE-2026-64440 Référence CVE CVE-2026-64441 https://www.cve.org/CVERecord?id=CVE-2026-64441 Référence CVE CVE-2026-64442 https://www.cve.org/CVERecord?id=CVE-2026-64442 Référence CVE CVE-2026-64443 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64409 Référence CVE CVE-2026-64411 https://www.cve.org/CVERecord?id=CVE-2026-64411 Référence CVE CVE-2026-64412 https://www.cve.org/CVERecord?id=CVE-2026-64412 Référence CVE CVE-2026-64420 https://www.cve.org/CVERecord?id=CVE-2026-64420 Référence CVE CVE-2026-64421 https://www.cve.org/CVERecord?id=CVE-2026-64421 Référence CVE CVE-2026-64423 https://www.cve.org/CVERecord?id=CVE-2026-64423 Référence CVE CVE-2026-64427 https://www.cve.org/CVERecord?id=CVE-2026-64427 Référence CVE CVE-2026-64429 https://www.cve.org/CVERecord?id=CVE-2026-64429 Référence CVE CVE-2026-64433 https://www.cve.org/CVERecord?id=CVE-2026-64433 Référence CVE CVE-2026-64434 https://www.cve.org/CVERecord?id=CVE-2026-64434 Référence CVE CVE-2026-64436 https://www.cve.org/CVERecord?id=CVE-2026-64436 Référence CVE CVE-2026-64440 https://www.cve.org/CVERecord?id=CVE-2026-64440 Référence CVE CVE-2026-64442 https://www.cve.org/CVERecord?id=CVE-2026-64442 Référence CVE CVE-2026-64443 https://www.cve.org/CVERecord?id=CVE-2026-64443 Référence CVE CVE-2026-64444 https://www.cve.org/CVERecord?id=CVE-2026-64444 Référence CVE CVE-2026-64445 https://www.cve.org/CVERecord?id=CVE-2026-64445 Référence CVE CVE-2026-64448 https://www.cve.org/CVERecord?id=CVE-2026-64448 Référence CVE CVE-2026-64450 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64423 Référence CVE CVE-2026-64424 https://www.cve.org/CVERecord?id=CVE-2026-64424 Référence CVE CVE-2026-64425 https://www.cve.org/CVERecord?id=CVE-2026-64425 Référence CVE CVE-2026-64426 https://www.cve.org/CVERecord?id=CVE-2026-64426 Référence CVE CVE-2026-64428 https://www.cve.org/CVERecord?id=CVE-2026-64428 Référence CVE CVE-2026-64429 https://www.cve.org/CVERecord?id=CVE-2026-64429 Référence CVE CVE-2026-64430 https://www.cve.org/CVERecord?id=CVE-2026-64430 Référence CVE CVE-2026-64432 https://www.cve.org/CVERecord?id=CVE-2026-64432 Référence CVE CVE-2026-64433 https://www.cve.org/CVERecord?id=CVE-2026-64433 Référence CVE CVE-2026-64434 https://www.cve.org/CVERecord?id=CVE-2026-64434 Référence CVE CVE-2026-64435 https://www.cve.org/CVERecord?id=CVE-2026-64435 Référence CVE CVE-2026-64436 https://www.cve.org/CVERecord?id=CVE-2026-64436 Référence CVE CVE-2026-64438 https://www.cve.org/CVERecord?id=CVE-2026-64438 Référence CVE CVE-2026-64439 https://www.cve.org/CVERecord?id=CVE-2026-64439 Référence CVE CVE-2026-64440 https://www.cve.org/CVERecord?id=CVE-2026-64440 Référence CVE CVE-2026-64441 https://www.cve.org/CVERecord?id=CVE-2026-64441 Référence CVE CVE-2026-64442 https://www.cve.org/CVERecord?id=CVE-2026-64442 Référence CVE CVE-2026-64443 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-64423 Référence CVE CVE-2026-64424 https://www.cve.org/CVERecord?id=CVE-2026-64424 Référence CVE CVE-2026-64425 https://www.cve.org/CVERecord?id=CVE-2026-64425 Référence CVE CVE-2026-64426 https://www.cve.org/CVERecord?id=CVE-2026-64426 Référence CVE CVE-2026-64428 https://www.cve.org/CVERecord?id=CVE-2026-64428 Référence CVE CVE-2026-64429 https://www.cve.org/CVERecord?id=CVE-2026-64429 Référence CVE CVE-2026-64430 https://www.cve.org/CVERecord?id=CVE-2026-64430 Référence CVE CVE-2026-64432 https://www.cve.org/CVERecord?id=CVE-2026-64432 Référence CVE CVE-2026-64433 https://www.cve.org/CVERecord?id=CVE-2026-64433 Référence CVE CVE-2026-64434 https://www.cve.org/CVERecord?id=CVE-2026-64434 Référence CVE CVE-2026-64435 https://www.cve.org/CVERecord?id=CVE-2026-64435 Référence CVE CVE-2026-64436 https://www.cve.org/CVERecord?id=CVE-2026-64436 Référence CVE CVE-2026-64438 https://www.cve.org/CVERecord?id=CVE-2026-64438 Référence CVE CVE-2026-64439 https://www.cve.org/CVERecord?id=CVE-2026-64439 Référence CVE CVE-2026-64440 https://www.cve.org/CVERecord?id=CVE-2026-64440 Référence CVE CVE-2026-64441 https://www.cve.org/CVERecord?id=CVE-2026-64441 Référence CVE CVE-2026-64442 https://www.cve.org/CVERecord?id=CVE-2026-64442 Référence CVE CVE-2026-64443 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53090 Référence CVE CVE-2026-53361 https://www.cve.org/CVERecord?id=CVE-2026-53361 Référence CVE CVE-2026-64082 https://www.cve.org/CVERecord?id=CVE-2026-64082 Référence CVE CVE-2026-64139 https://www.cve.org/CVERecord?id=CVE-2026-64139 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=CVE-2026-64192 Référence CVE CVE-2026-64270 https://www.cve.org/CVERecord?id=CVE-2026-64270 Référence CVE CVE-2026-64272 https://www.cve.org/CVERecord?id=CVE-2026-64272 Référence CVE CVE-2026-64280 https://www.cve.org/CVERecord?id=CVE-2026-64280 Référence CVE CVE-2026-64294 https://www.cve.org/CVERecord?id=CVE-2026-64294 Référence CVE CVE-2026-64434 https://www.cve.org/CVERecord?id=CVE-2026-64434 Référence CVE CVE-2026-64507 https://www.cve.org/CVERecord?id=CVE-2026-64507 Référence CVE CVE-2026-64508 https://www.cve.org/CVERecord?id=CVE-2026-64508 Référence CVE CVE-2026-64542 https://www.cve.org/CVERecord?id=CVE-2026-64542 Référence CVE CVE-2026-64543 https://www.cve.org/CVERecord?id=CVE-2026-64543 Référence CVE CVE-2026-64561 https://www.cve.org/CVERecord?id=CVE-2026-64561 Référence CVE CVE-2026-64562 https://www.cve.org/CVERecord?id=CVE-2026-64562 Référence CVE CVE-2026-64563 https://www.cve.org/CVERecord?id=CVE-2026-64563 Référence CVE CVE-2026-64564 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64409 Référence CVE CVE-2026-64411 https://www.cve.org/CVERecord?id=CVE-2026-64411 Référence CVE CVE-2026-64412 https://www.cve.org/CVERecord?id=CVE-2026-64412 Référence CVE CVE-2026-64420 https://www.cve.org/CVERecord?id=CVE-2026-64420 Référence CVE CVE-2026-64421 https://www.cve.org/CVERecord?id=CVE-2026-64421 Référence CVE CVE-2026-64423 https://www.cve.org/CVERecord?id=CVE-2026-64423 Référence CVE CVE-2026-64427 https://www.cve.org/CVERecord?id=CVE-2026-64427 Référence CVE CVE-2026-64429 https://www.cve.org/CVERecord?id=CVE-2026-64429 Référence CVE CVE-2026-64433 https://www.cve.org/CVERecord?id=CVE-2026-64433 Référence CVE CVE-2026-64434 https://www.cve.org/CVERecord?id=CVE-2026-64434 Référence CVE CVE-2026-64436 https://www.cve.org/CVERecord?id=CVE-2026-64436 Référence CVE CVE-2026-64440 https://www.cve.org/CVERecord?id=CVE-2026-64440 Référence CVE CVE-2026-64442 https://www.cve.org/CVERecord?id=CVE-2026-64442 Référence CVE CVE-2026-64443 https://www.cve.org/CVERecord?id=CVE-2026-64443 Référence CVE CVE-2026-64444 https://www.cve.org/CVERecord?id=CVE-2026-64444 Référence CVE CVE-2026-64445 https://www.cve.org/CVERecord?id=CVE-2026-64445 Référence CVE CVE-2026-64448 https://www.cve.org/CVERecord?id=CVE-2026-64448 Référence CVE CVE-2026-64450 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64422 Référence CVE CVE-2026-64423 https://www.cve.org/CVERecord?id=CVE-2026-64423 Référence CVE CVE-2026-64424 https://www.cve.org/CVERecord?id=CVE-2026-64424 Référence CVE CVE-2026-64425 https://www.cve.org/CVERecord?id=CVE-2026-64425 Référence CVE CVE-2026-64428 https://www.cve.org/CVERecord?id=CVE-2026-64428 Référence CVE CVE-2026-64429 https://www.cve.org/CVERecord?id=CVE-2026-64429 Référence CVE CVE-2026-64430 https://www.cve.org/CVERecord?id=CVE-2026-64430 Référence CVE CVE-2026-64432 https://www.cve.org/CVERecord?id=CVE-2026-64432 Référence CVE CVE-2026-64433 https://www.cve.org/CVERecord?id=CVE-2026-64433 Référence CVE CVE-2026-64434 https://www.cve.org/CVERecord?id=CVE-2026-64434 Référence CVE CVE-2026-64435 https://www.cve.org/CVERecord?id=CVE-2026-64435 Référence CVE CVE-2026-64436 https://www.cve.org/CVERecord?id=CVE-2026-64436 Référence CVE CVE-2026-64437 https://www.cve.org/CVERecord?id=CVE-2026-64437 Référence CVE CVE-2026-64438 https://www.cve.org/CVERecord?id=CVE-2026-64438 Référence CVE CVE-2026-64440 https://www.cve.org/CVERecord?id=CVE-2026-64440 Référence CVE CVE-2026-64441 https://www.cve.org/CVERecord?id=CVE-2026-64441 Référence CVE CVE-2026-64442 https://www.cve.org/CVERecord?id=CVE-2026-64442 Référence CVE CVE-2026-64443 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64371 Référence CVE CVE-2026-64375 https://www.cve.org/CVERecord?id=CVE-2026-64375 Référence CVE CVE-2026-64390 https://www.cve.org/CVERecord?id=CVE-2026-64390 Référence CVE CVE-2026-64401 https://www.cve.org/CVERecord?id=CVE-2026-64401 Référence CVE CVE-2026-64405 https://www.cve.org/CVERecord?id=CVE-2026-64405 Référence CVE CVE-2026-64413 https://www.cve.org/CVERecord?id=CVE-2026-64413 Référence CVE CVE-2026-64416 https://www.cve.org/CVERecord?id=CVE-2026-64416 Référence CVE CVE-2026-64421 https://www.cve.org/CVERecord?id=CVE-2026-64421 Référence CVE CVE-2026-64428 https://www.cve.org/CVERecord?id=CVE-2026-64428 Référence CVE CVE-2026-64434 https://www.cve.org/CVERecord?id=CVE-2026-64434 Référence CVE CVE-2026-64438 https://www.cve.org/CVERecord?id=CVE-2026-64438 Référence CVE CVE-2026-64441 https://www.cve.org/CVERecord?id=CVE-2026-64441 Référence CVE CVE-2026-64461 https://www.cve.org/CVERecord?id=CVE-2026-64461 Référence CVE CVE-2026-64462 https://www.cve.org/CVERecord?id=CVE-2026-64462 Référence CVE CVE-2026-64472 https://www.cve.org/CVERecord?id=CVE-2026-64472 Référence CVE CVE-2026-64481 https://www.cve.org/CVERecord?id=CVE-2026-64481 Référence CVE CVE-2026-64488 https://www.cve.org/CVERecord?id=CVE-2026-64488 Référence CVE CVE-2026-64493 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-032018LinuxのLinux Kernelにおける解放済みメモリの使用に関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。Bluetooth: L2CAPにおいて、connの参照を保持することでチャネルタイムアウト時のUse-After-Free（UAF）が修正されました。l2cap_chan_timeout()は非同期で動作し、chan-＞connへアクセスします。タイマーが実行中または保留中に接続が切断されると、chan-＞connが解放され、タイマーワーカーがconn-＞lockをロックしようとした際にUse-After-Freeが発生する可能性があります。| BUG: KASAN: slab-use-after-free in instrument_atomic_read_write include/linux/instrumented.h:112 [inline]| BUG: KASAN: slab-use-after-free in atomic_long_try_cmpxchg_acquire include/linux/atomic/atomic-instrumented.h:4456 [inline]| BUG: KASAN: slab-use-after-free in __mutex_trylock_fast kernel/locking/mutex.c:161 [inline]| BUG: KASAN: slab-use-after-free in mutex_lock+0x4f/0xa0 kernel/locking/mutex.c:318| ・・・（省略）この問題は、チャネルが接続に追加される際にchan-＞connがl2cap_connの参照を保持（l2cap_conn_get経由）し、チャネルのデストラクタでそれを解放することで修正されました。これにより、チャネルが存在する限りl2cap_connが生存し続けることが保証されます。新たにFLAG_DELチャネルフラグが導入され、チャネルが削除中であることを示します。---以下省略---

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
Fixed
Linux: < 7.1, 5.10.265 ≤ 5.10.*, 5.15.216 ≤ 5.15.*, 6.1.183 ≤ 6.1.*, 6.6.145 ≤ 6.6.*, 6.12.97 ≤ 6.12.*, 6.18.39 ≤ 6.18.*, 7.1.4 ≤ 7.1.*, 7.2 ≤ *
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 25 Jul 2026 · Last source change 19 Aug 2026, 16:28 UTC · CWE-416 · Use After Free

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-48778
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
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 ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: added patch: git.kernel.org/0b0e2bf39cf99e458d991b9df253727e036a7d7d; added patch: git.kernel.org/32d783cafb46ff3ca58e6f9fd62c9c5f35eaf26b; 6 further additions.
    Before
    remediation: git.kernel.org/8f90405a4a6f1f1880dc07996b47bf57c712bd8a
    After
    patch: git.kernel.org/0b0e2bf39cf99e458d991b9df253727e036a7d7d · patch: git.kernel.org/32d783cafb46ff3ca58e6f9fd62c9c5f35eaf26b · patch: git.kernel.org/50c38d9f42a529691e4e67ea9cedf4f0bfc8d277 · 6 more references
    git.kernel.org ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/8f90405a4a6f1f1880dc07996b47bf57c712bd8a; removed remediation: git.kernel.org/91047a4396a8b1857a6f712a90cf33ec0012b189.
    Before
    remediation: git.kernel.org/91047a4396a8b1857a6f712a90cf33ec0012b189
    After
    remediation: git.kernel.org/8f90405a4a6f1f1880dc07996b47bf57c712bd8a
    CNA ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    89dec92041717b027216e110599e4f6d6c921b79 < 91047a4396a8b1857a6f712a90cf33ec0012b189; 50dfec218808b148ab4247b1858031b7a32015c5 < 0b0e2bf39cf99e458d991b9df253727e036a7d7d; 859d3ace791ed878ae9ba5522c7844d960da8f88 < d3b739db5dc6f688a60d56da872fabaf65246032; 8c8e620467a7b51562dbcefbd1f09f288d7d710d < 50c38d9f42a529691e4e67ea9cedf4f0bfc8d277; 8c8e620467a7b51562dbcefbd1f09f288d7d710d < b66774b48dd98f07254951f74ea6f513efe7ff8b; 3634cbdc2eb414b69ffa752ddbe5e0458518e321; e1c100e2d61bd8c718b7d91fe3e050780a9bf72d; deb8493a8fa599f6c95e2465b12bfdfb7f94a1d9 · Fixed: < 7.1; 6.6.145 ≤ 6.6.*; 6.12.97 ≤ 6.12.*; 6.18.39 ≤ 6.18.*; 7.1.4 ≤ 7.1.*; 7.2 ≤ *
    After
    3634cbdc2eb414b69ffa752ddbe5e0458518e321 < 8f90405a4a6f1f1880dc07996b47bf57c712bd8a; e1c100e2d61bd8c718b7d91fe3e050780a9bf72d < 32d783cafb46ff3ca58e6f9fd62c9c5f35eaf26b; deb8493a8fa599f6c95e2465b12bfdfb7f94a1d9 < 8922c7940bae9ce4b1736dddb6362370793835c2; 89dec92041717b027216e110599e4f6d6c921b79 < 91047a4396a8b1857a6f712a90cf33ec0012b189; 50dfec218808b148ab4247b1858031b7a32015c5 < 0b0e2bf39cf99e458d991b9df253727e036a7d7d; 859d3ace791ed878ae9ba5522c7844d960da8f88 < d3b739db5dc6f688a60d56da872fabaf65246032; 8c8e620467a7b51562dbcefbd1f09f288d7d710d < 50c38d9f42a529691e4e67ea9cedf4f0bfc8d277; 8c8e620467a7b51562dbcefbd1f09f288d7d710d < b66774b48dd98f07254951f74ea6f513efe7ff8b · Fixed: < 7.1; 5.10.265 ≤ 5.10.*; 5.15.216 ≤ 5.15.*; 6.1.183 ≤ 6.1.*; 6.6.145 ≤ 6.6.*; 6.12.97 ≤ 6.12.*; 6.18.39 ≤ 6.18.*; 7.1.4 ≤ 7.1.*
    CNA ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    89dec92041717b027216e110599e4f6d6c921b79 < 91047a4396a8b1857a6f712a90cf33ec0012b189; 50dfec218808b148ab4247b1858031b7a32015c5 < 0b0e2bf39cf99e458d991b9df253727e036a7d7d; 859d3ace791ed878ae9ba5522c7844d960da8f88 < d3b739db5dc6f688a60d56da872fabaf65246032; 8c8e620467a7b51562dbcefbd1f09f288d7d710d < 50c38d9f42a529691e4e67ea9cedf4f0bfc8d277; 8c8e620467a7b51562dbcefbd1f09f288d7d710d < b66774b48dd98f07254951f74ea6f513efe7ff8b; 3634cbdc2eb414b69ffa752ddbe5e0458518e321; e1c100e2d61bd8c718b7d91fe3e050780a9bf72d; deb8493a8fa599f6c95e2465b12bfdfb7f94a1d9 · Fixed: < 7.1; 6.6.145 ≤ 6.6.*; 6.12.97 ≤ 6.12.*; 6.18.39 ≤ 6.18.*; 7.1.4 ≤ 7.1.*; 7.2-rc1 ≤ *
    After
    89dec92041717b027216e110599e4f6d6c921b79 < 91047a4396a8b1857a6f712a90cf33ec0012b189; 50dfec218808b148ab4247b1858031b7a32015c5 < 0b0e2bf39cf99e458d991b9df253727e036a7d7d; 859d3ace791ed878ae9ba5522c7844d960da8f88 < d3b739db5dc6f688a60d56da872fabaf65246032; 8c8e620467a7b51562dbcefbd1f09f288d7d710d < 50c38d9f42a529691e4e67ea9cedf4f0bfc8d277; 8c8e620467a7b51562dbcefbd1f09f288d7d710d < b66774b48dd98f07254951f74ea6f513efe7ff8b; 3634cbdc2eb414b69ffa752ddbe5e0458518e321; e1c100e2d61bd8c718b7d91fe3e050780a9bf72d; deb8493a8fa599f6c95e2465b12bfdfb7f94a1d9 · Fixed: < 7.1; 6.6.145 ≤ 6.6.*; 6.12.97 ≤ 6.12.*; 6.18.39 ≤ 6.18.*; 7.1.4 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
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-48778↗Vendor CSAF · SUSE Product Security Team↗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-64434 · cve.blacktree.nl