BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-27399High confidence

Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan_timeout

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 13 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 severityMediumOperational priority:Low, lowered one band.downgradedsince 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.30% 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: No default targetRemediation target: Normal maintenance

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 13 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.

17 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 13 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.8.11-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.94-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.8.11-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.8.11-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-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-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.8Affected, 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-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.

2 current
CVE-2024-27399 · CSAF 2.0 · revision 103 · interimSUSE Product Security TeamCVE-2024-27399
291 known affected

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

  • kernel-default as component of SUSE Enterprise Storage 7.1
  • kernel-default-devel as component of SUSE Enterprise Storage 7.1
  • kernel-devel as component of SUSE Enterprise Storage 7.1
  • kernel-macros as component of SUSE Enterprise Storage 7.1
  • kernel-source as component of SUSE Enterprise Storage 7.1
  • reiserfs-kmp-default as component of SUSE Enterprise Storage 7.1
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan_timeout There is a race condition between l2cap_chan_timeout() and l2cap_chan_del(). When we use l2cap_chan_del() to delete the channel, the chan->conn will be set to null. But the conn could be dereferenced again in the mutex_lock() of l2cap_chan_timeout(). As a result the null pointer dereference bug will happen. The KASAN report triggered by POC is shown below: [ 472.074580] ================================================================== [ 472.075284] BUG: KASAN: null-ptr-deref in mutex_lock+0x68/0xc0 [ 472.075308] Write of size 8 at addr 0000000000000158 by task kworker/0:0/7 [ 472.075308] [ 472.075308] CPU: 0 PID: 7 Comm: kworker/0:0 Not tainted 6.9.0-rc5-00356-g78c0094a146b #36 [ 472.075308] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu4 [ 472.075308] Workqueue: events l2cap_chan_timeout [ 472.075308] Call Trace: [ 472.075308] [ 472.075308] dump_stack_lvl+0x137/0x1a0 [ 472.075308] print_report+0x101/0x250 [ 472.075308] ? __virt_addr_valid+0x77/0x160 [ 472.075308] ? mutex_lock+0x68/0xc0 [ 472.075308] kasan_report+0x139/0x170 [ 472.075308] ? mutex_lock+0x68/0xc0 [ 472.075308] kasan_check_range+0x2c3/0x2e0 [ 472.075308] mutex_lock+0x68/0xc0 [ 472.075308] l2cap_chan_timeout+0x181/0x300 [ 472.075308] process_one_work+0x5d2/0xe00 [ 472.075308] worker_thread+0xe1d/0x1660 [ 472.075308] ? pr_cont_work+0x5e0/0x5e0 [ 472.075308] kthread+0x2b7/0x350 [ 472.075308] ? pr_cont_work+0x5e0/0x5e0 [ 472.075308] ? kthread_blkcg+0xd0/0xd0 [ 472.075308] ret_from_fork+0x4d/0x80 [ 472.075308] ? kthread_blkcg+0xd0/0xd0 [ 472.075308] ret_from_fork_asm+0x11/0x20 [ 472.075308] [ 472.075308] ================================================================== [ 472.094860] Disabling lock debugging due to kernel taint [ 472.096136] BUG: kernel NULL pointer dereference, address: 0000000000000158 [ 472.096136] #PF: supervisor write access in kernel mode [ 472.096136] #PF: error_code(0x0002) - not-present page [ 472.096136] PGD 0 P4D 0 [ 472.096136] Oops: 0002 [#1] PREEMPT SMP KASAN NOPTI [ 472.096136] CPU: 0 PID: 7 Comm: kworker/0:0 Tainted: G B 6.9.0-rc5-00356-g78c0094a146b #36 [ 472.096136] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu4 [ 472.096136] Workqueue: events l2cap_chan_timeout [ 472.096136] RIP: 0010:mutex_lock+0x88/0xc0 [ 472.096136] Code: be 08 00 00 00 e8 f8 23 1f fd 4c 89 f7 be 08 00 00 00 e8 eb 23 1f fd 42 80 3c 23 00 74 08 48 88 [ 472.096136] RSP: 0018:ffff88800744fc78 EFLAGS: 00000246 [ 472.096136] RAX: 0000000000000000 RBX: 1ffff11000e89f8f RCX: ffffffff8457c865 [ 472.096136] RDX: 0000000000000001 RSI: 0000000000000008 RDI: ffff88800744fc78 [ 472.096136] RBP: 0000000000000158 R08: ffff88800744fc7f R09: 1ffff11000e89f8f [ 472.096136] R10: dffffc0000000000 R11: ffffed1000e89f90 R12: dffffc0000000000 [ 472.096136] R13: 0000000000000158 R14: ffff88800744fc78 R15: ffff888007405a00 [ 472.096136] FS: 0000000000000000(0000) GS:ffff88806d200000(0000) knlGS:0000000000000000 [ 472.096136] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 472.096136] CR2: 0000000000000158 CR3: 000000000da32000 CR4: 00000000000006f0 [ 472.096136] Call Trace: [ 472.096136] [ 472.096136] ? __die_body+0x8d/0xe0 [ 472.096136] ? page_fault_oops+0x6b8/0x9a0 [ 472.096136] ? kernelmode_fixup_or_oops+0x20c/0x2a0 [ 472.096136] ? do_user_addr_fault+0x1027/0x1340 [ 472.096136] ? _printk+0x7a/0xa0 [ 472.096136] ? mutex_lock+0x68/0xc0 [ 472.096136] ? add_taint+0x42/0xd0 [ 472.096136] ? exc_page_fault+0x6a/0x1b0 [ 472.096136] ? asm_exc_page_fault+0x26/0x30 [ 472.096136] ? mutex_lock+0x75/0xc0 [ 472.096136] ? mutex_lock+0x88/0xc0 [ 472.096136] ? mutex_lock+0x75/0xc0 [ 472.096136] l2cap_chan_timeo ---truncated---
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2024-27399 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan_timeout
66 known affected

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

  • bpftool as a component of Red Hat Enterprise Linux 7
  • kernel as a component of Red Hat Enterprise Linux 7
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 7
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 7
  • kernel-debug as a component of Red Hat Enterprise Linux 7
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 7
  • kernel-devel as a component of Red Hat Enterprise Linux 7
  • kernel-doc as a component of Red Hat Enterprise Linux 7
  • kernel-headers as a component of Red Hat Enterprise Linux 7
  • kernel-kdump as a component of Red Hat Enterprise Linux 7
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 7
  • kernel-rt as a component of Red Hat Enterprise Linux 7
Summary
A flaw was found in the Linux kernel's Bluetooth L2CAP (Logical Link Control and Adaptation Protocol) component. A race condition between channel deletion and timeout handling can lead to a null-pointer dereference in the `l2cap_chan_timeout` function. A local attacker with low privileges could exploit this vulnerability, causing a kernel panic and resulting in a denial of service.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
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-2024-24603

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 13 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 null-ptr-deref in l2cap_chan_timeout There is a race condition between l2cap_chan_timeout() and l2cap_chan_del(). When we use l2cap_chan_del() to delete the channel, the chan->conn will be set to null. But the conn could be dereferenced again in the mutex_lock() of l2cap_chan_timeout(). As a result the null pointer dereference bug will happen. The KASAN report triggered by POC is shown below: [ 472.074580] ================================================================== [ 472.075284] BUG: KASAN: null-ptr-deref in mutex_lock+0x68/0xc0 [ 472.075308] Write of size 8 at addr 0000000000000158 by task kworker/0:0/7 [ 472.075308] [ 472.075308] CPU: 0 PID: 7 Comm: kworker/0:0 Not tainted 6.9.0-rc5-00356-g78c0094a146b #36 [ 472.075308] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu4 [ 472.075308] Workqueue: events l2cap_chan_timeout [ 472.075308] Call Trace: [ 472.075308] <TASK> [ 472.075308] dump_stack_lvl+0x137/0x1a0 [ 472.075308] print_report+0x101/0x250 [ 472.075308] ? __virt_addr_valid+0x77/0x160 [ 472.075308] ? mutex_lock+0x68/0xc0 [ 472.075308] kasan_report+0x139/0x170 [ 472.075308] ? mutex_lock+0x68/0xc0 [ 472.075308] kasan_check_range+0x2c3/0x2e0 [ 472.075308] mutex_lock+0x68/0xc0 [ 472.075308] l2cap_chan_timeout+0x181/0x300 [ 472.075308] process_one_work+0x5d2/0xe00 [ 472.075308] worker_thread+0xe1d/0x1660 [ 472.075308] ? pr_cont_work+0x5e0/0x5e0 [ 472.075308] kthread+0x2b7/0x350 [ 472.075308] ? pr_cont_work+0x5e0/0x5e0 [ 472.075308] ? kthread_blkcg+0xd0/0xd0 [ 472.075308] ret_from_fork+0x4d/0x80 [ 472.075308] ? kthread_blkcg+0xd0/0xd0 [ 472.075308] ret_from_fork_asm+0x11/0x20 [ 472.075308] </TASK> [ 472.075308] ================================================================== [ 472.094860] Disabling lock debugging due to kernel taint [ 472.096136] BUG: kernel NULL pointer dereference, address: 0000000000000158 [ 472.096136] #PF: supervisor write access in kernel mode [ 472.096136] #PF: error_code(0x0002) - not-present page [ 472.096136] PGD 0 P4D 0 [ 472.096136] Oops: 0002 [#1] PREEMPT SMP KASAN NOPTI [ 472.096136] CPU: 0 PID: 7 Comm: kworker/0:0 Tainted: G B 6.9.0-rc5-00356-g78c0094a146b #36 [ 472.096136] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu4 [ 472.096136] Workqueue: events l2cap_chan_timeout [ 472.096136] RIP: 0010:mutex_lock+0x88/0xc0 [ 472.096136] Code: be 08 00 00 00 e8 f8 23 1f fd 4c 89 f7 be 08 00 00 00 e8 eb 23 1f fd 42 80 3c 23 00 74 08 48 88 [ 472.096136] RSP: 0018:ffff88800744fc78 EFLAGS: 00000246 [ 472.096136] RAX: 0000000000000000 RBX: 1ffff11000e89f8f RCX: ffffffff8457c865 [ 472.096136] RDX: 0000000000000001 RSI: 0000000000000008 RDI: ffff88800744fc78 [ 472.096136] RBP: 0000000000000158 R08: ffff88800744fc7f R09: 1ffff11000e89f8f [ 472.096136] R10: dffffc0000000000 R11: ffffed1000e89f90 R12: dffffc0000000000 [ 472.096136] R13: 0000000000000158 R14: ffff88800744fc78 R15: ffff888007405a00 [ 472.096136] FS: 0000000000000000(0000) GS:ffff88806d200000(0000) knlGS:0000000000000000 [ 472.096136] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 472.096136] CR2: 0000000000000158 CR3: 000000000da32000 CR4: 00000000000006f0 [ 472.096136] Call Trace: [ 472.096136] <TASK> [ 472.096136] ? __die_body+0x8d/0xe0 [ 472.096136] ? page_fault_oops+0x6b8/0x9a0 [ 472.096136] ? kernelmode_fixup_or_oops+0x20c/0x2a0 [ 472.096136] ? do_user_addr_fault+0x1027/0x1340 [ 472.096136] ? _printk+0x7a/0xa0 [ 472.096136] ? mutex_lock+0x68/0xc0 [ 472.096136] ? add_taint+0x42/0xd0 [ 472.096136] ? exc_page_fault+0x6a/0x1b0 [ 472.096136] ? asm_exc_page_fault+0x26/0x30 [ 472.096136] ? mutex_lock+0x75/0xc0 [ 472.096136] ? mutex_lock+0x88/0xc0 [ 472.096136] ? mutex_lock+0x75/0xc0 [ 472.096136] l2cap_chan_timeo ---truncated---

What

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan_timeout There is a race condition between l2cap_chan_timeout() and l2cap_chan_del(). When we use l2cap_chan_del() to delete the channel, the chan->conn will be set to null. But the conn could be dereferenced again in the mutex_lock() of l2cap_chan_timeout(). As a result the null pointer dereference bug will happen. The KASAN report triggered by POC is shown below: [ 472.074580] ================================================================== [ 472.075284] BUG: KASAN: null-ptr-deref in mutex_lock+0x68/0xc0 [ 472.075308] Write of size 8 at addr 0000000000000158 by task kworker/0:0/7 [ 472.075308] [ 472.075308] CPU: 0 PID: 7 Comm: kworker/0:0 Not tainted 6.9.0-rc5-00356-g78c0094a146b #36 [ 472.075308] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu4 [ 472.075308] Workqueue: events l2cap_chan_timeout [ 472.075308] Call Trace: [ 472.075308] <TASK> [ 472.075308] dump_stack_lvl+0x137/0x1a0 [ 472.075308] print_report+0x101/0x250 [ 472.075308] ? __virt_addr_valid+0x77/0x160 [ 472.075308] ? mutex_lock+0x68/0xc0 [ 472.075308] kasan_report+0x139/0x170 [ 472.075308] ? mutex_lock+0x68/0xc0 [ 472.075308] kasan_check_range+0x2c3/0x2e0 [ 472.075308] mutex_lock+0x68/0xc0 [ 472.075308] l2cap_chan_timeout+0x181/0x300 [ 472.075308] process_one_work+0x5d2/0xe00 [ 472.075308] worker_thread+0xe1d/0x1660 [ 472.075308] ? pr_cont_work+0x5e0/0x5e0 [ 472.075308] kthread+0x2b7/0x350 [ 472.075308] ? pr_cont_work+0x5e0/0x5e0 [ 472.075308] ? kthread_blkcg+0xd0/0xd0 [ 472.075308] ret_from_fork+0x4d/0x80 [ 472.075308] ? kthread_blkcg+0xd0/0xd0 [ 472.075308] ret_from_fork_asm+0x11/0x20 [ 472.075308] </TASK> [ 472.075308] ================================================================== [ 472.094860] Disabling lock debugging due to kernel taint [ 472.096136] BUG: kernel NULL pointer dereference, address: 0000000000000158 [ 472.096136] #PF: supervisor write access in kernel mode [ 472.096136] #PF: error_code(0x0002) - not-present page [ 472.096136] PGD 0 P4D 0 [ 472.096136] Oops: 0002 [#1] PREEMPT SMP KASAN NOPTI [ 472.096136] CPU: 0 PID: 7 Comm: kworker/0:0 Tainted: G B 6.9.0-rc5-00356-g78c0094a146b #36 [ 472.096136] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu4 [ 472.096136] Workqueue: events l2cap_chan_timeout [ 472.096136] RIP: 0010:mutex_lock+0x88/0xc0 [ 472.096136] Code: be 08 00 00 00 e8 f8 23 1f fd 4c 89 f7 be 08 00 00 00 e8 eb 23 1f fd 42 80 3c 23 00 74 08 48 88 [ 472.096136] RSP: 0018:ffff88800744fc78 EFLAGS: 00000246 [ 472.096136] RAX: 0000000000000000 RBX: 1ffff11000e89f8f RCX: ffffffff8457c865 [ 472.096136] RDX: 0000000000000001 RSI: 0000000000000008 RDI: ffff88800744fc78 [ 472.096136] RBP: 0000000000000158 R08: ffff88800744fc7f R09: 1ffff11000e89f8f [ 472.096136] R10: dffffc0000000000 R11: ffffed1000e89f90 R12: dffffc0000000000 [ 472.096136] R13: 0000000000000158 R14: ffff88800744fc78 R15: ffff888007405a00 [ 472.096136] FS: 0000000000000000(0000) GS:ffff88806d200000(0000) knlGS:0000000000000000 [ 472.096136] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 472.096136] CR2: 0000000000000158 CR3: 000000000da32000 CR4: 00000000000006f0 [ 472.096136] Call Trace: [ 472.096136] <TASK> [ 472.096136] ? __die_body+0x8d/0xe0 [ 472.096136] ? page_fault_oops+0x6b8/0x9a0 [ 472.096136] ? kernelmode_fixup_or_oops+0x20c/0x2a0 [ 472.096136] ? do_user_addr_fault+0x1027/0x1340 [ 472.096136] ? _printk+0x7a/0xa0 [ 472.096136] ? mutex_lock+0x68/0xc0 [ 472.096136] ? add_taint+0x42/0xd0 [ 472.096136] ? exc_page_fault+0x6a/0x1b0 [ 472.096136] ? asm_exc_page_fault+0x26/0x30 [ 472.096136] ? mutex_lock+0x75/0xc0 [ 472.096136] ? mutex_lock+0x88/0xc0 [ 472.096136] ? mutex_lock+0x75/0xc0 [ 472.096136] l2cap_chan_timeo ---truncated---

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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: Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan_timeout There is a race condition between l2cap_chan_timeout() and l2cap_chan_del(). When we use l2cap_chan_del() to delete the channel, the chan->conn will be set to null. But the conn could be dereferenced again in the mutex_lock() of l2cap_chan_timeout(). As a result the null pointer dereference bug will happen. The KASAN report triggered by POC is shown below: [ 472.074580] ================================================================== [ 472.075284] BUG: KASAN: null-ptr-deref in mutex_lock+0x68/0xc0 [ 472.075308] Write of size 8 at addr 0000000000000158 by task kworker/0:0/7 [ 472.075308] [ 472.075308] CPU: 0 PID: 7 Comm: kworker/0:0 Not tainted 6.9.0-rc5-00356-g78c0094a146b #36 [ 472.075308] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu4 [ 472.075308] Workqueue: events l2cap_chan_timeout [ 472.075308] Call Trace: [ 472.075308] <TASK> [ 472.075308] dump_stack_lvl+0x137/0x1a0 [ 472.075308] print_report+0x101/0x250 [ 472.075308] ? __virt_addr_valid+0x77/0x160 [ 472.075308] ? mutex_lock+0x68/0xc0 [ 472.075308] kasan_report+0x139/0x170 [ 472.075308] ? mutex_lock+0x68/0xc0 [ 472.075308] kasan_check_range+0x2c3/0x2e0 [ 472.075308] mutex_lock+0x68/0xc0 [ 472.075308] l2cap_chan_timeout+0x181/0x300 [ 472.075308] process_one_work+0x5d2/0xe00 [ 472.075308] worker_thread+0xe1d/0x1660 [ 472.075308] ? pr_cont_work+0x5e0/0x5e0 [ 472.075308] kthread+0x2b7/0x350 [ 472.075308] ? pr_cont_work+0x5e0/0x5e0 [ 472.075308] ? kthread_blkcg+0xd0/0xd0 [ 472.075308] ret_from_fork+0x4d/0x80 [ 472.075308] ? kthread_blkcg+0xd0/0xd0 [ 472.075308] ret_from_fork_asm+0x11/0x20 [ 472.075308] </TASK> [ 472.075308] ================================================================== [ 472.094860] Disabling lock debugging due to kernel taint [ 472.096136] BUG: kernel NULL pointer dereference, address: 0000000000000158 [ 472.096136] #PF: supervisor write access in kernel mode [ 472.096136] #PF: error_code(0x0002) - not-present page [ 472.096136] PGD 0 P4D 0 [ 472.096136] Oops: 0002 [#1] PREEMPT SMP KASAN NOPTI [ 472.096136] CPU: 0 PID: 7 Comm: kworker/0:0 Tainted: G B 6.9.0-rc5-00356-g78c0094a146b #36 [ 472.096136] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu4 [ 472.096136] Workqueue: events l2cap_chan_timeout [ 472.096136] RIP: 0010:mutex_lock+0x88/0xc0 [ 472.096136] Code: be 08 00 00 00 e8 f8 23 1f fd 4c 89 f7 be 08 00 00 00 e8 eb 23 1f fd 42 80 3c 23 00 74 08 48 88 [ 472.096136] RSP: 0018:ffff88800744fc78 EFLAGS: 00000246 [ 472.096136] RAX: 0000000000000000 RBX: 1ffff11000e89f8f RCX: ffffffff8457c865 [ 472.096136] RDX: 0000000000000001 RSI: 0000000000000008 RDI: ffff88800744fc78 [ 472.096136] RBP: 0000000000000158 R08: ffff88800744fc7f R09: 1ffff11000e89f8f [ 472.096136] R10: dffffc0000000000 R11: ffffed1000e89f90 R12: dffffc0000000000 [ 472.096136] R13: 0000000000000158 R14: ffff88800744fc78 R15: ffff888007405a00 [ 472.096136] FS: 0000000000000000(0000) GS:ffff88806d200000(0000) knlGS:0000000000000000 [ 472.096136] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 472.096136] CR2: 0000000000000158 CR3: 000000000da32000 CR4: 00000000000006f0 [ 472.096136] Call Trace: [ 472.096136] <TASK> [ 472.096136] ? __die_body+0x8d/0xe0 [ 472.096136] ? page_fault_oops+0x6b8/0x9a0 [ 472.096136] ? kernelmode_fixup_or_oops+0x20c/0x2a0 [ 472.096136] ? do_user_addr_fault+0x1027/0x1340 [ 472.096136] ? _printk+0x7a/0xa0 [ 472.096136] ? mutex_lock+0x68/0xc0 [ 472.096136] ? add_taint+0x42/0xd0 [ 472.096136] ? exc_page_fault+0x6a/0x1b0 [ 472.096136] ? asm_exc_page_fault+0x26/0x30 [ 472.096136] ? mutex_lock+0x75/0xc0 [ 472.096136] ? mutex_lock+0x88/0xc0 [ 472.096136] ? mutex_lock+0x75/0xc0 [ 472.096136] l2cap_chan_timeo ---truncated---

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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 → NULL Pointer Dereference → 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
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-476 ↗

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

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:L/PR:L/UI:N/S:U/C:N/I:N/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.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.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.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.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-476
A

Official authority intelligence

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

BSI · German · WID-SEC-2024-1108Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240515Security Bulletin 15 May 2024

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

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1165Multiples vulnérabilités dans les produits IBM

d?id=CVE-2024-27020 Référence CVE CVE-2024-27025 https://www.cve.org/CVERecord?id=CVE-2024-27025 Référence CVE CVE-2024-27042 https://www.cve.org/CVERecord?id=CVE-2024-27042 Référence CVE CVE-2024-27043 https://www.cve.org/CVERecord?id=CVE-2024-27043 Référence CVE CVE-2024-27062 https://www.cve.org/CVERecord?id=CVE-2024-27062 Référence CVE CVE-2024-27065 https://www.cve.org/CVERecord?id=CVE-2024-27065 Référence CVE CVE-2024-27388 https://www.cve.org/CVERecord?id=CVE-2024-27388 Référence CVE CVE-2024-27395 https://www.cve.org/CVERecord?id=CVE-2024-27395 Référence CVE CVE-2024-27397 https://www.cve.org/CVERecord?id=CVE-2024-27397 Référence CVE CVE-2024-27399 https://www.cve.org/CVERecord?id=CVE-2024-27399 Référence CVE CVE-2024-27410 https://www.cve.org/CVERecord?id=CVE-2024-27410 Référence CVE CVE-2024-27434 https://www.cve.org/CVERecord?id=CVE-2024-27434 Référence CVE CVE-2024-28757 https://www.cve.org/CVERecord?id=CVE-2024-28757 Référence CVE CVE-2024-28762 https://www.cve.org/CVERecord?id=CVE-2024-28762 Référence CVE CVE-2024-29025 https://www.cve.org/CVERecord?id=CVE-2024-29025 Référence CVE CVE-2024-29131 https://www.cve.org/CVERecord?id=CVE-2024-29131 Référence CVE CVE-2024-29133 https://www.cve.org/CVERecord?id=CVE-2024-29133 Référence CVE CVE-2024-29857 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1050Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2023-52749 Référence CVE CVE-2023-52775 https://www.cve.org/CVERecord?id=CVE-2023-52775 Référence CVE CVE-2023-52811 https://www.cve.org/CVERecord?id=CVE-2023-52811 Référence CVE CVE-2023-52881 https://www.cve.org/CVERecord?id=CVE-2023-52881 Référence CVE CVE-2024-26601 https://www.cve.org/CVERecord?id=CVE-2024-26601 Référence CVE CVE-2024-26615 https://www.cve.org/CVERecord?id=CVE-2024-26615 Référence CVE CVE-2024-26686 https://www.cve.org/CVERecord?id=CVE-2024-26686 Référence CVE CVE-2024-26704 https://www.cve.org/CVERecord?id=CVE-2024-26704 Référence CVE CVE-2024-26984 https://www.cve.org/CVERecord?id=CVE-2024-26984 Référence CVE CVE-2024-27399 https://www.cve.org/CVERecord?id=CVE-2024-27399 Référence CVE CVE-2024-36920 https://www.cve.org/CVERecord?id=CVE-2024-36920 Référence CVE CVE-2024-36928 https://www.cve.org/CVERecord?id=CVE-2024-36928 Référence CVE CVE-2024-36960 https://www.cve.org/CVERecord?id=CVE-2024-36960 Référence CVE CVE-2024-37356 https://www.cve.org/CVERecord?id=CVE-2024-37356 Référence CVE CVE-2024-38384 https://www.cve.org/CVERecord?id=CVE-2024-38384 Référence CVE CVE-2024-38541 https://www.cve.org/CVERecord?id=CVE-2024-38541 Référence CVE CVE-2024-38555 https://www.cve.org/CVERecord?id=CVE-2024-38555 Référence CVE CVE-2024-39507 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1032Multiples vulnérabilités dans le noyau Linux de Red Hat

ord?id=CVE-2022-48686 Référence CVE CVE-2022-48773 https://www.cve.org/CVERecord?id=CVE-2022-48773 Référence CVE CVE-2022-48786 https://www.cve.org/CVERecord?id=CVE-2022-48786 Référence CVE CVE-2022-48929 https://www.cve.org/CVERecord?id=CVE-2022-48929 Référence CVE CVE-2023-0597 https://www.cve.org/CVERecord?id=CVE-2023-0597 Référence CVE CVE-2023-52489 https://www.cve.org/CVERecord?id=CVE-2023-52489 Référence CVE CVE-2024-26671 https://www.cve.org/CVERecord?id=CVE-2024-26671 Référence CVE CVE-2024-26961 https://www.cve.org/CVERecord?id=CVE-2024-26961 Référence CVE CVE-2024-27043 https://www.cve.org/CVERecord?id=CVE-2024-27043 Référence CVE CVE-2024-27399 https://www.cve.org/CVERecord?id=CVE-2024-27399 Référence CVE CVE-2024-31076 https://www.cve.org/CVERecord?id=CVE-2024-31076 Référence CVE CVE-2024-35823 https://www.cve.org/CVERecord?id=CVE-2024-35823 Référence CVE CVE-2024-36889 https://www.cve.org/CVERecord?id=CVE-2024-36889 Référence CVE CVE-2024-36920 https://www.cve.org/CVERecord?id=CVE-2024-36920 Référence CVE CVE-2024-38564 https://www.cve.org/CVERecord?id=CVE-2024-38564 Référence CVE CVE-2024-40988 https://www.cve.org/CVERecord?id=CVE-2024-40988 Référence CVE CVE-2024-41009 https://www.cve.org/CVERecord?id=CVE-2024-41009 Référence CVE CVE-2024-41014 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-27017 Référence CVE CVE-2024-27018 https://www.cve.org/CVERecord?id=CVE-2024-27018 Référence CVE CVE-2024-27019 https://www.cve.org/CVERecord?id=CVE-2024-27019 Référence CVE CVE-2024-27020 https://www.cve.org/CVERecord?id=CVE-2024-27020 Référence CVE CVE-2024-27059 https://www.cve.org/CVERecord?id=CVE-2024-27059 Référence CVE CVE-2024-27393 https://www.cve.org/CVERecord?id=CVE-2024-27393 Référence CVE CVE-2024-27395 https://www.cve.org/CVERecord?id=CVE-2024-27395 Référence CVE CVE-2024-27396 https://www.cve.org/CVERecord?id=CVE-2024-27396 Référence CVE CVE-2024-27398 https://www.cve.org/CVERecord?id=CVE-2024-27398 Référence CVE CVE-2024-27399 https://www.cve.org/CVERecord?id=CVE-2024-27399 Référence CVE CVE-2024-27401 https://www.cve.org/CVERecord?id=CVE-2024-27401 Référence CVE CVE-2024-27437 https://www.cve.org/CVERecord?id=CVE-2024-27437 Référence CVE CVE-2024-31076 https://www.cve.org/CVERecord?id=CVE-2024-31076 Référence CVE CVE-2024-32936 https://www.cve.org/CVERecord?id=CVE-2024-32936 Référence CVE CVE-2024-33619 https://www.cve.org/CVERecord?id=CVE-2024-33619 Référence CVE CVE-2024-33621 https://www.cve.org/CVERecord?id=CVE-2024-33621 Référence CVE CVE-2024-33847 https://www.cve.org/CVERecord?id=CVE-2024-33847 Référence CVE CVE-2024-34027 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-27064 Référence CVE CVE-2024-27065 https://www.cve.org/CVERecord?id=CVE-2024-27065 Référence CVE CVE-2024-27067 https://www.cve.org/CVERecord?id=CVE-2024-27067 Référence CVE CVE-2024-27080 https://www.cve.org/CVERecord?id=CVE-2024-27080 Référence CVE CVE-2024-27388 https://www.cve.org/CVERecord?id=CVE-2024-27388 Référence CVE CVE-2024-27389 https://www.cve.org/CVERecord?id=CVE-2024-27389 Référence CVE CVE-2024-27393 https://www.cve.org/CVERecord?id=CVE-2024-27393 Référence CVE CVE-2024-27395 https://www.cve.org/CVERecord?id=CVE-2024-27395 Référence CVE CVE-2024-27396 https://www.cve.org/CVERecord?id=CVE-2024-27396 Référence CVE CVE-2024-27399 https://www.cve.org/CVERecord?id=CVE-2024-27399 Référence CVE CVE-2024-27400 https://www.cve.org/CVERecord?id=CVE-2024-27400 Référence CVE CVE-2024-27401 https://www.cve.org/CVERecord?id=CVE-2024-27401 Référence CVE CVE-2024-27402 https://www.cve.org/CVERecord?id=CVE-2024-27402 Référence CVE CVE-2024-27404 https://www.cve.org/CVERecord?id=CVE-2024-27404 Référence CVE CVE-2024-27405 https://www.cve.org/CVERecord?id=CVE-2024-27405 Référence CVE CVE-2024-27408 https://www.cve.org/CVERecord?id=CVE-2024-27408 Référence CVE CVE-2024-27410 https://www.cve.org/CVERecord?id=CVE-2024-27410 Référence CVE CVE-2024-27411 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26900 Référence CVE CVE-2024-26903 https://www.cve.org/CVERecord?id=CVE-2024-26903 Référence CVE CVE-2024-26907 https://www.cve.org/CVERecord?id=CVE-2024-26907 Référence CVE CVE-2024-26921 https://www.cve.org/CVERecord?id=CVE-2024-26921 Référence CVE CVE-2024-26929 https://www.cve.org/CVERecord?id=CVE-2024-26929 Référence CVE CVE-2024-26936 https://www.cve.org/CVERecord?id=CVE-2024-26936 Référence CVE CVE-2024-26980 https://www.cve.org/CVERecord?id=CVE-2024-26980 Référence CVE CVE-2024-27019 https://www.cve.org/CVERecord?id=CVE-2024-27019 Référence CVE CVE-2024-27398 https://www.cve.org/CVERecord?id=CVE-2024-27398 Référence CVE CVE-2024-27399 https://www.cve.org/CVERecord?id=CVE-2024-27399 Référence CVE CVE-2024-27401 https://www.cve.org/CVERecord?id=CVE-2024-27401 Référence CVE CVE-2024-31076 https://www.cve.org/CVERecord?id=CVE-2024-31076 Référence CVE CVE-2024-33621 https://www.cve.org/CVERecord?id=CVE-2024-33621 Référence CVE CVE-2024-35835 https://www.cve.org/CVERecord?id=CVE-2024-35835 Référence CVE CVE-2024-35848 https://www.cve.org/CVERecord?id=CVE-2024-35848 Référence CVE CVE-2024-35947 https://www.cve.org/CVERecord?id=CVE-2024-35947 Référence CVE CVE-2024-35955 https://www.cve.org/CVERecord?id=CVE-2024-35955 Référence CVE CVE-2024-35976 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26980 Référence CVE CVE-2024-27013 https://www.cve.org/CVERecord?id=CVE-2024-27013 Référence CVE CVE-2024-27017 https://www.cve.org/CVERecord?id=CVE-2024-27017 Référence CVE CVE-2024-27019 https://www.cve.org/CVERecord?id=CVE-2024-27019 Référence CVE CVE-2024-27020 https://www.cve.org/CVERecord?id=CVE-2024-27020 Référence CVE CVE-2024-27394 https://www.cve.org/CVERecord?id=CVE-2024-27394 Référence CVE CVE-2024-27395 https://www.cve.org/CVERecord?id=CVE-2024-27395 Référence CVE CVE-2024-27396 https://www.cve.org/CVERecord?id=CVE-2024-27396 Référence CVE CVE-2024-27398 https://www.cve.org/CVERecord?id=CVE-2024-27398 Référence CVE CVE-2024-27399 https://www.cve.org/CVERecord?id=CVE-2024-27399 Référence CVE CVE-2024-27400 https://www.cve.org/CVERecord?id=CVE-2024-27400 Référence CVE CVE-2024-27401 https://www.cve.org/CVERecord?id=CVE-2024-27401 Référence CVE CVE-2024-31076 https://www.cve.org/CVERecord?id=CVE-2024-31076 Référence CVE CVE-2024-33621 https://www.cve.org/CVERecord?id=CVE-2024-33621 Référence CVE CVE-2024-35846 https://www.cve.org/CVERecord?id=CVE-2024-35846 Référence CVE CVE-2024-35847 https://www.cve.org/CVERecord?id=CVE-2024-35847 Référence CVE CVE-2024-35848 https://www.cve.org/CVERecord?id=CVE-2024-35848 Référence CVE CVE-2024-35849 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26936 Référence CVE CVE-2024-26980 https://www.cve.org/CVERecord?id=CVE-2024-26980 Référence CVE CVE-2024-27013 https://www.cve.org/CVERecord?id=CVE-2024-27013 Référence CVE CVE-2024-27019 https://www.cve.org/CVERecord?id=CVE-2024-27019 Référence CVE CVE-2024-27020 https://www.cve.org/CVERecord?id=CVE-2024-27020 Référence CVE CVE-2024-27394 https://www.cve.org/CVERecord?id=CVE-2024-27394 Référence CVE CVE-2024-27395 https://www.cve.org/CVERecord?id=CVE-2024-27395 Référence CVE CVE-2024-27396 https://www.cve.org/CVERecord?id=CVE-2024-27396 Référence CVE CVE-2024-27398 https://www.cve.org/CVERecord?id=CVE-2024-27398 Référence CVE CVE-2024-27399 https://www.cve.org/CVERecord?id=CVE-2024-27399 Référence CVE CVE-2024-27400 https://www.cve.org/CVERecord?id=CVE-2024-27400 Référence CVE CVE-2024-27401 https://www.cve.org/CVERecord?id=CVE-2024-27401 Référence CVE CVE-2024-27416 https://www.cve.org/CVERecord?id=CVE-2024-27416 Référence CVE CVE-2024-31076 https://www.cve.org/CVERecord?id=CVE-2024-31076 Référence CVE CVE-2024-33621 https://www.cve.org/CVERecord?id=CVE-2024-33621 Référence CVE CVE-2024-35833 https://www.cve.org/CVERecord?id=CVE-2024-35833 Référence CVE CVE-2024-35846 https://www.cve.org/CVERecord?id=CVE-2024-35846 Référence CVE CVE-2024-35847 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26845 Référence CVE CVE-2024-26852 https://www.cve.org/CVERecord?id=CVE-2024-26852 Référence CVE CVE-2024-26863 https://www.cve.org/CVERecord?id=CVE-2024-26863 Référence CVE CVE-2024-26880 https://www.cve.org/CVERecord?id=CVE-2024-26880 Référence CVE CVE-2024-26894 https://www.cve.org/CVERecord?id=CVE-2024-26894 Référence CVE CVE-2024-26923 https://www.cve.org/CVERecord?id=CVE-2024-26923 Référence CVE CVE-2024-26928 https://www.cve.org/CVERecord?id=CVE-2024-26928 Référence CVE CVE-2024-26930 https://www.cve.org/CVERecord?id=CVE-2024-26930 Référence CVE CVE-2024-26973 https://www.cve.org/CVERecord?id=CVE-2024-26973 Référence CVE CVE-2024-27399 https://www.cve.org/CVERecord?id=CVE-2024-27399 Référence CVE CVE-2024-27410 https://www.cve.org/CVERecord?id=CVE-2024-27410 Référence CVE CVE-2024-35247 https://www.cve.org/CVERecord?id=CVE-2024-35247 Référence CVE CVE-2024-35789 https://www.cve.org/CVERecord?id=CVE-2024-35789 Référence CVE CVE-2024-35805 https://www.cve.org/CVERecord?id=CVE-2024-35805 Référence CVE CVE-2024-35807 https://www.cve.org/CVERecord?id=CVE-2024-35807 Référence CVE CVE-2024-35819 https://www.cve.org/CVERecord?id=CVE-2024-35819 Référence CVE CVE-2024-35822 https://www.cve.org/CVERecord?id=CVE-2024-35822 Référence CVE CVE-2024-35828 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26845 Référence CVE CVE-2024-26852 https://www.cve.org/CVERecord?id=CVE-2024-26852 Référence CVE CVE-2024-26863 https://www.cve.org/CVERecord?id=CVE-2024-26863 Référence CVE CVE-2024-26894 https://www.cve.org/CVERecord?id=CVE-2024-26894 Référence CVE CVE-2024-26921 https://www.cve.org/CVERecord?id=CVE-2024-26921 Référence CVE CVE-2024-26923 https://www.cve.org/CVERecord?id=CVE-2024-26923 Référence CVE CVE-2024-26928 https://www.cve.org/CVERecord?id=CVE-2024-26928 Référence CVE CVE-2024-26930 https://www.cve.org/CVERecord?id=CVE-2024-26930 Référence CVE CVE-2024-26973 https://www.cve.org/CVERecord?id=CVE-2024-26973 Référence CVE CVE-2024-27399 https://www.cve.org/CVERecord?id=CVE-2024-27399 Référence CVE CVE-2024-27410 https://www.cve.org/CVERecord?id=CVE-2024-27410 Référence CVE CVE-2024-27432 https://www.cve.org/CVERecord?id=CVE-2024-27432 Référence CVE CVE-2024-33619 https://www.cve.org/CVERecord?id=CVE-2024-33619 Référence CVE CVE-2024-35247 https://www.cve.org/CVERecord?id=CVE-2024-35247 Référence CVE CVE-2024-35789 https://www.cve.org/CVERecord?id=CVE-2024-35789 Référence CVE CVE-2024-35790 https://www.cve.org/CVERecord?id=CVE-2024-35790 Référence CVE CVE-2024-35807 https://www.cve.org/CVERecord?id=CVE-2024-35807 Référence CVE CVE-2024-35814 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-27074 Référence CVE CVE-2024-27075 https://www.cve.org/CVERecord?id=CVE-2024-27075 Référence CVE CVE-2024-27076 https://www.cve.org/CVERecord?id=CVE-2024-27076 Référence CVE CVE-2024-27077 https://www.cve.org/CVERecord?id=CVE-2024-27077 Référence CVE CVE-2024-27078 https://www.cve.org/CVERecord?id=CVE-2024-27078 Référence CVE CVE-2024-27388 https://www.cve.org/CVERecord?id=CVE-2024-27388 Référence CVE CVE-2024-27395 https://www.cve.org/CVERecord?id=CVE-2024-27395 Référence CVE CVE-2024-27396 https://www.cve.org/CVERecord?id=CVE-2024-27396 Référence CVE CVE-2024-27398 https://www.cve.org/CVERecord?id=CVE-2024-27398 Référence CVE CVE-2024-27399 https://www.cve.org/CVERecord?id=CVE-2024-27399 Référence CVE CVE-2024-27401 https://www.cve.org/CVERecord?id=CVE-2024-27401 Référence CVE CVE-2024-27405 https://www.cve.org/CVERecord?id=CVE-2024-27405 Référence CVE CVE-2024-27410 https://www.cve.org/CVERecord?id=CVE-2024-27410 Référence CVE CVE-2024-27412 https://www.cve.org/CVERecord?id=CVE-2024-27412 Référence CVE CVE-2024-27413 https://www.cve.org/CVERecord?id=CVE-2024-27413 Référence CVE CVE-2024-27414 https://www.cve.org/CVERecord?id=CVE-2024-27414 Référence CVE CVE-2024-27416 https://www.cve.org/CVERecord?id=CVE-2024-27416 Référence CVE CVE-2024-27417 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-27077 Référence CVE CVE-2024-27078 https://www.cve.org/CVERecord?id=CVE-2024-27078 Référence CVE CVE-2024-27080 https://www.cve.org/CVERecord?id=CVE-2024-27080 Référence CVE CVE-2024-27388 https://www.cve.org/CVERecord?id=CVE-2024-27388 Référence CVE CVE-2024-27389 https://www.cve.org/CVERecord?id=CVE-2024-27389 Référence CVE CVE-2024-27393 https://www.cve.org/CVERecord?id=CVE-2024-27393 Référence CVE CVE-2024-27395 https://www.cve.org/CVERecord?id=CVE-2024-27395 Référence CVE CVE-2024-27396 https://www.cve.org/CVERecord?id=CVE-2024-27396 Référence CVE CVE-2024-27398 https://www.cve.org/CVERecord?id=CVE-2024-27398 Référence CVE CVE-2024-27399 https://www.cve.org/CVERecord?id=CVE-2024-27399 Référence CVE CVE-2024-27400 https://www.cve.org/CVERecord?id=CVE-2024-27400 Référence CVE CVE-2024-27401 https://www.cve.org/CVERecord?id=CVE-2024-27401 Référence CVE CVE-2024-27405 https://www.cve.org/CVERecord?id=CVE-2024-27405 Référence CVE CVE-2024-27408 https://www.cve.org/CVERecord?id=CVE-2024-27408 Référence CVE CVE-2024-27410 https://www.cve.org/CVERecord?id=CVE-2024-27410 Référence CVE CVE-2024-27411 https://www.cve.org/CVERecord?id=CVE-2024-27411 Référence CVE CVE-2024-27412 https://www.cve.org/CVERecord?id=CVE-2024-27412 Référence CVE CVE-2024-27413 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-27075 Référence CVE CVE-2024-27076 https://www.cve.org/CVERecord?id=CVE-2024-27076 Référence CVE CVE-2024-27077 https://www.cve.org/CVERecord?id=CVE-2024-27077 Référence CVE CVE-2024-27078 https://www.cve.org/CVERecord?id=CVE-2024-27078 Référence CVE CVE-2024-27388 https://www.cve.org/CVERecord?id=CVE-2024-27388 Référence CVE CVE-2024-27393 https://www.cve.org/CVERecord?id=CVE-2024-27393 Référence CVE CVE-2024-27395 https://www.cve.org/CVERecord?id=CVE-2024-27395 Référence CVE CVE-2024-27396 https://www.cve.org/CVERecord?id=CVE-2024-27396 Référence CVE CVE-2024-27398 https://www.cve.org/CVERecord?id=CVE-2024-27398 Référence CVE CVE-2024-27399 https://www.cve.org/CVERecord?id=CVE-2024-27399 Référence CVE CVE-2024-27400 https://www.cve.org/CVERecord?id=CVE-2024-27400 Référence CVE CVE-2024-27401 https://www.cve.org/CVERecord?id=CVE-2024-27401 Référence CVE CVE-2024-27405 https://www.cve.org/CVERecord?id=CVE-2024-27405 Référence CVE CVE-2024-27410 https://www.cve.org/CVERecord?id=CVE-2024-27410 Référence CVE CVE-2024-27412 https://www.cve.org/CVERecord?id=CVE-2024-27412 Référence CVE CVE-2024-27413 https://www.cve.org/CVERecord?id=CVE-2024-27413 Référence CVE CVE-2024-27416 https://www.cve.org/CVERecord?id=CVE-2024-27416 Référence CVE CVE-2024-27417 https://www.cve.org/CVERecord?id=

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

ons Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Debian DSA-5703-1 du 02 juin 2024 https://lists.debian.org/debian-security-announce/2024/msg00113.html Référence CVE CVE-2022-48655 https://www.cve.org/CVERecord?id=CVE-2022-48655 Référence CVE CVE-2023-52585 https://www.cve.org/CVERecord?id=CVE-2023-52585 Référence CVE CVE-2023-52882 https://www.cve.org/CVERecord?id=CVE-2023-52882 Référence CVE CVE-2024-26900 https://www.cve.org/CVERecord?id=CVE-2024-26900 Référence CVE CVE-2024-27398 https://www.cve.org/CVERecord?id=CVE-2024-27398 Référence CVE CVE-2024-27399 https://www.cve.org/CVERecord?id=CVE-2024-27399 Référence CVE CVE-2024-27401 https://www.cve.org/CVERecord?id=CVE-2024-27401 Référence CVE CVE-2024-35848 https://www.cve.org/CVERecord?id=CVE-2024-35848 Référence CVE CVE-2024-35947 https://www.cve.org/CVERecord?id=CVE-2024-35947 Référence CVE CVE-2024-36017 https://www.cve.org/CVERecord?id=CVE-2024-36017 Référence CVE CVE-2024-36031 https://www.cve.org/CVERecord?id=CVE-2024-36031 Référence CVE CVE-2024-36883 https://www.cve.org/CVERecord?id=CVE-2024-36883 Référence CVE CVE-2024-36886 https://www.cve.org/CVERecord?id=CVE-2024-36886 Référence CVE CVE-2024-36889 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-030018Debian等の複数ベンダの製品におけるNULL ポインタデリファレンスに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました：Bluetoothのl2capにおけるl2cap_chan_timeout関数のヌルポインタ参照の問題です。l2cap_chan_timeout()とl2cap_chan_del()の間で競合状態が発生します。チャネル削除時にl2cap_chan_del()がchan-connをnullに設定しますが、l2cap_chan_timeout()のmutex_lock()内でconnが再度参照される可能性があります。その結果、ヌルポインタ参照のバグが発生します。POCによりトリガーされたKASANレポートは以下の通りです：[省略]。

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: < 3.4, 4.19.314 ≤ 4.19.*, 5.4.276 ≤ 5.4.*, 5.10.217 ≤ 5.10.*, 5.15.159 ≤ 5.15.*, 6.1.91 ≤ 6.1.*, 6.6.31 ≤ 6.6.*, 6.8.10 ≤ 6.8.*, 6.9 ≤ *
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 13 May 2024 · Last source change 11 May 2026, 20:10 UTC · CWE-476 · NULL Pointer Dereference

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
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-2024-24603
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 ↗

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-2024-24603↗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-2024-27399 · cve.blacktree.nl