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

Bluetooth: fix UAF in l2cap_sock_cleanup_listen() vs l2cap_conn_del()

Linux · Linux

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

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.41% 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 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

24 package states
Package result overrides the generic status

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

Repository candidate not checked

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

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.94-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.176-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
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-53357 · CSAF 2.0 · revision 24 · interimSUSE Product Security TeamCVE-2026-53357
168 known affected

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

  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
Summary
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: fix UAF in l2cap_sock_cleanup_listen() vs l2cap_conn_del() bt_accept_dequeue() unlinks a not-yet-accepted child from the parent accept queue and release_sock()s it before returning, so the returned sk has no caller reference and is unlocked. l2cap_sock_cleanup_listen() walks these children on listening-socket close. A concurrent HCI disconnect drives hci_rx_work -> l2cap_conn_del() which runs l2cap_chan_del() + l2cap_sock_kill() and frees the child sk and its l2cap_chan; cleanup_listen() then uses both: BUG: KASAN: slab-use-after-free in l2cap_sock_kill l2cap_sock_kill / l2cap_sock_cleanup_listen / __x64_sys_close Freed by: l2cap_conn_del -> l2cap_sock_close_cb -> l2cap_sock_kill This is distinct from the two fixes already in this area: commit e83f5e24da741 ("Bluetooth: serialize accept_q access") serialises the accept_q list/poll and takes temporary refs inside bt_accept_dequeue(), and CVE-2025-39860 serialises the userspace close()/accept() race by calling cleanup_listen() under lock_sock() in l2cap_sock_release(). Neither covers l2cap_conn_del() running from hci_rx_work, so this UAF still reproduces on current bluetooth/master. Take the reference at the source: bt_accept_dequeue() does sock_hold() while sk is still locked, before release_sock(); callers sock_put(). cleanup_listen() pins the chan with l2cap_chan_hold_unless_zero() under a brief child sk lock (serialising vs l2cap_sock_teardown_cb()), drops it before l2cap_chan_lock(), and skips a duplicate l2cap_sock_kill() on SOCK_DEAD. conn->lock is not taken here: cleanup_listen() runs under the parent sk lock and that would invert conn->lock -> chan->lock -> sk_lock (lockdep). KASAN/SMP: an unprivileged listen/close vs HCI-disconnect race produced 12 use-after-free reports per run before this change; 0, and no lockdep report, over 1600+ raced iterations after it on bluetooth/master.
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-41372

No EUVD known-exploited evidence

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

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

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

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: fix UAF in l2cap_sock_cleanup_listen() vs l2cap_conn_del() bt_accept_dequeue() unlinks a not-yet-accepted child from the parent accept queue and release_sock()s it before returning, so the returned sk has no caller reference and is unlocked. l2cap_sock_cleanup_listen() walks these children on listening-socket close. A concurrent HCI disconnect drives hci_rx_work -> l2cap_conn_del() which runs l2cap_chan_del() + l2cap_sock_kill() and frees the child sk and its l2cap_chan; cleanup_listen() then uses both: BUG: KASAN: slab-use-after-free in l2cap_sock_kill l2cap_sock_kill / l2cap_sock_cleanup_listen / __x64_sys_close Freed by: l2cap_conn_del -> l2cap_sock_close_cb -> l2cap_sock_kill This is distinct from the two fixes already in this area: commit e83f5e24da741 ("Bluetooth: serialize accept_q access") serialises the accept_q list/poll and takes temporary refs inside bt_accept_dequeue(), and CVE-2025-39860 serialises the userspace close()/accept() race by calling cleanup_listen() under lock_sock() in l2cap_sock_release(). Neither covers l2cap_conn_del() running from hci_rx_work, so this UAF still reproduces on current bluetooth/master. Take the reference at the source: bt_accept_dequeue() does sock_hold() while sk is still locked, before release_sock(); callers sock_put(). cleanup_listen() pins the chan with l2cap_chan_hold_unless_zero() under a brief child sk lock (serialising vs l2cap_sock_teardown_cb()), drops it before l2cap_chan_lock(), and skips a duplicate l2cap_sock_kill() on SOCK_DEAD. conn->lock is not taken here: cleanup_listen() runs under the parent sk lock and that would invert conn->lock -> chan->lock -> sk_lock (lockdep). KASAN/SMP: an unprivileged listen/close vs HCI-disconnect race produced 12 use-after-free reports per run before this change; 0, and no lockdep report, over 1600+ raced iterations after it on bluetooth/master.

What

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: fix UAF in l2cap_sock_cleanup_listen() vs l2cap_conn_del() bt_accept_dequeue() unlinks a not-yet-accepted child from the parent accept queue and release_sock()s it before returning, so the returned sk has no caller reference and is unlocked. l2cap_sock_cleanup_listen() walks these children on listening-socket close. A concurrent HCI disconnect drives hci_rx_work -> l2cap_conn_del() which runs l2cap_chan_del() + l2cap_sock_kill() and frees the child sk and its l2cap_chan; cleanup_listen() then uses both: BUG: KASAN: slab-use-after-free in l2cap_sock_kill l2cap_sock_kill / l2cap_sock_cleanup_listen / __x64_sys_close Freed by: l2cap_conn_del -> l2cap_sock_close_cb -> l2cap_sock_kill This is distinct from the two fixes already in this area: commit e83f5e24da741 ("Bluetooth: serialize accept_q access") serialises the accept_q list/poll and takes temporary refs inside bt_accept_dequeue(), and CVE-2025-39860 serialises the userspace close()/accept() race by calling cleanup_listen() under lock_sock() in l2cap_sock_release(). Neither covers l2cap_conn_del() running from hci_rx_work, so this UAF still reproduces on current bluetooth/master. Take the reference at the source: bt_accept_dequeue() does sock_hold() while sk is still locked, before release_sock(); callers sock_put(). cleanup_listen() pins the chan with l2cap_chan_hold_unless_zero() under a brief child sk lock (serialising vs l2cap_sock_teardown_cb()), drops it before l2cap_chan_lock(), and skips a duplicate l2cap_sock_kill() on SOCK_DEAD. conn->lock is not taken here: cleanup_listen() runs under the parent sk lock and that would invert conn->lock -> chan->lock -> sk_lock (lockdep). KASAN/SMP: an unprivileged listen/close vs HCI-disconnect race produced 12 use-after-free reports per run before this change; 0, and no lockdep report, over 1600+ raced iterations after it on bluetooth/master.

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 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: fix UAF in l2cap_sock_cleanup_listen() vs l2cap_conn_del() bt_accept_dequeue() unlinks a not-yet-accepted child from the parent accept queue and release_sock()s it before returning, so the returned sk has no caller reference and is unlocked. l2cap_sock_cleanup_listen() walks these children on listening-socket close. A concurrent HCI disconnect drives hci_rx_work -> l2cap_conn_del() which runs l2cap_chan_del() + l2cap_sock_kill() and frees the child sk and its l2cap_chan; cleanup_listen() then uses both: BUG: KASAN: slab-use-after-free in l2cap_sock_kill l2cap_sock_kill / l2cap_sock_cleanup_listen / __x64_sys_close Freed by: l2cap_conn_del -> l2cap_sock_close_cb -> l2cap_sock_kill This is distinct from the two fixes already in this area: commit e83f5e24da741 ("Bluetooth: serialize accept_q access") serialises the accept_q list/poll and takes temporary refs inside bt_accept_dequeue(), and CVE-2025-39860 serialises the userspace close()/accept() race by calling cleanup_listen() under lock_sock() in l2cap_sock_release(). Neither covers l2cap_conn_del() running from hci_rx_work, so this UAF still reproduces on current bluetooth/master. Take the reference at the source: bt_accept_dequeue() does sock_hold() while sk is still locked, before release_sock(); callers sock_put(). cleanup_listen() pins the chan with l2cap_chan_hold_unless_zero() under a brief child sk lock (serialising vs l2cap_sock_teardown_cb()), drops it before l2cap_chan_lock(), and skips a duplicate l2cap_sock_kill() on SOCK_DEAD. conn->lock is not taken here: cleanup_listen() runs under the parent sk lock and that would invert conn->lock -> chan->lock -> sk_lock (lockdep). KASAN/SMP: an unprivileged listen/close vs HCI-disconnect race produced 12 use-after-free reports per run before this change; 0, and no lockdep report, over 1600+ raced iterations after it on bluetooth/master.

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 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
an adjacent network → Use After Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Adjacent
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-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:L/UI:N/S:U/C:H/I:H/A:H

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

AVAdjacentAttack vector: The attacker must be on an adjacent or logically close network.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.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.
CWE-416
A

Official authority intelligence

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

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

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260708Security Bulletin 8 July 2026 [PDF, 1MB]]

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 8 July 2026 [PDF, 1MB]], published on 8 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-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53348 Référence CVE CVE-2026-53349 https://www.cve.org/CVERecord?id=CVE-2026-53349 Référence CVE CVE-2026-53350 https://www.cve.org/CVERecord?id=CVE-2026-53350 Référence CVE CVE-2026-53351 https://www.cve.org/CVERecord?id=CVE-2026-53351 Référence CVE CVE-2026-53352 https://www.cve.org/CVERecord?id=CVE-2026-53352 Référence CVE CVE-2026-53353 https://www.cve.org/CVERecord?id=CVE-2026-53353 Référence CVE CVE-2026-53354 https://www.cve.org/CVERecord?id=CVE-2026-53354 Référence CVE CVE-2026-53355 https://www.cve.org/CVERecord?id=CVE-2026-53355 Référence CVE CVE-2026-53356 https://www.cve.org/CVERecord?id=CVE-2026-53356 Référence CVE CVE-2026-53357 https://www.cve.org/CVERecord?id=CVE-2026-53357 Référence CVE CVE-2026-53358 https://www.cve.org/CVERecord?id=CVE-2026-53358 Référence CVE CVE-2026-53359 https://www.cve.org/CVERecord?id=CVE-2026-53359 Référence CVE CVE-2026-53360 https://www.cve.org/CVERecord?id=CVE-2026-53360 Référence CVE CVE-2026-53361 https://www.cve.org/CVERecord?id=CVE-2026-53361 Référence CVE CVE-2026-53362 https://www.cve.org/CVERecord?id=CVE-2026-53362 Référence CVE CVE-2026-53363 https://www.cve.org/CVERecord?id=CVE-2026-53363 Référence CVE CVE-2026-53364 https://www.cve.org/CVERecord?id=CVE-2026-53364 Référence CVE CVE-2026-53365 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-53348 Référence CVE CVE-2026-53349 https://www.cve.org/CVERecord?id=CVE-2026-53349 Référence CVE CVE-2026-53350 https://www.cve.org/CVERecord?id=CVE-2026-53350 Référence CVE CVE-2026-53351 https://www.cve.org/CVERecord?id=CVE-2026-53351 Référence CVE CVE-2026-53352 https://www.cve.org/CVERecord?id=CVE-2026-53352 Référence CVE CVE-2026-53353 https://www.cve.org/CVERecord?id=CVE-2026-53353 Référence CVE CVE-2026-53354 https://www.cve.org/CVERecord?id=CVE-2026-53354 Référence CVE CVE-2026-53355 https://www.cve.org/CVERecord?id=CVE-2026-53355 Référence CVE CVE-2026-53356 https://www.cve.org/CVERecord?id=CVE-2026-53356 Référence CVE CVE-2026-53357 https://www.cve.org/CVERecord?id=CVE-2026-53357 Référence CVE CVE-2026-53358 https://www.cve.org/CVERecord?id=CVE-2026-53358 Référence CVE CVE-2026-53359 https://www.cve.org/CVERecord?id=CVE-2026-53359 Référence CVE CVE-2026-53360 https://www.cve.org/CVERecord?id=CVE-2026-53360 Référence CVE CVE-2026-53361 https://www.cve.org/CVERecord?id=CVE-2026-53361 Référence CVE CVE-2026-53362 https://www.cve.org/CVERecord?id=CVE-2026-53362 Référence CVE CVE-2026-53363 https://www.cve.org/CVERecord?id=CVE-2026-53363 Référence CVE CVE-2026-53364 https://www.cve.org/CVERecord?id=CVE-2026-53364 Référence CVE CVE-2026-53365 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-53348 Référence CVE CVE-2026-53349 https://www.cve.org/CVERecord?id=CVE-2026-53349 Référence CVE CVE-2026-53350 https://www.cve.org/CVERecord?id=CVE-2026-53350 Référence CVE CVE-2026-53351 https://www.cve.org/CVERecord?id=CVE-2026-53351 Référence CVE CVE-2026-53352 https://www.cve.org/CVERecord?id=CVE-2026-53352 Référence CVE CVE-2026-53353 https://www.cve.org/CVERecord?id=CVE-2026-53353 Référence CVE CVE-2026-53354 https://www.cve.org/CVERecord?id=CVE-2026-53354 Référence CVE CVE-2026-53355 https://www.cve.org/CVERecord?id=CVE-2026-53355 Référence CVE CVE-2026-53356 https://www.cve.org/CVERecord?id=CVE-2026-53356 Référence CVE CVE-2026-53357 https://www.cve.org/CVERecord?id=CVE-2026-53357 Référence CVE CVE-2026-53358 https://www.cve.org/CVERecord?id=CVE-2026-53358 Référence CVE CVE-2026-53359 https://www.cve.org/CVERecord?id=CVE-2026-53359 Référence CVE CVE-2026-53361 https://www.cve.org/CVERecord?id=CVE-2026-53361 Référence CVE CVE-2026-53362 https://www.cve.org/CVERecord?id=CVE-2026-53362 Référence CVE CVE-2026-53363 https://www.cve.org/CVERecord?id=CVE-2026-53363 Référence CVE CVE-2026-53366 https://www.cve.org/CVERecord?id=CVE-2026-53366 Référence CVE CVE-2026-53368 https://www.cve.org/CVERecord?id=CVE-2026-53368 Référence CVE CVE-2026-53381 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-53348 Référence CVE CVE-2026-53349 https://www.cve.org/CVERecord?id=CVE-2026-53349 Référence CVE CVE-2026-53350 https://www.cve.org/CVERecord?id=CVE-2026-53350 Référence CVE CVE-2026-53351 https://www.cve.org/CVERecord?id=CVE-2026-53351 Référence CVE CVE-2026-53352 https://www.cve.org/CVERecord?id=CVE-2026-53352 Référence CVE CVE-2026-53353 https://www.cve.org/CVERecord?id=CVE-2026-53353 Référence CVE CVE-2026-53354 https://www.cve.org/CVERecord?id=CVE-2026-53354 Référence CVE CVE-2026-53355 https://www.cve.org/CVERecord?id=CVE-2026-53355 Référence CVE CVE-2026-53356 https://www.cve.org/CVERecord?id=CVE-2026-53356 Référence CVE CVE-2026-53357 https://www.cve.org/CVERecord?id=CVE-2026-53357 Référence CVE CVE-2026-53358 https://www.cve.org/CVERecord?id=CVE-2026-53358 Référence CVE CVE-2026-53359 https://www.cve.org/CVERecord?id=CVE-2026-53359 Référence CVE CVE-2026-53360 https://www.cve.org/CVERecord?id=CVE-2026-53360 Référence CVE CVE-2026-53361 https://www.cve.org/CVERecord?id=CVE-2026-53361 Référence CVE CVE-2026-53362 https://www.cve.org/CVERecord?id=CVE-2026-53362 Référence CVE CVE-2026-53363 https://www.cve.org/CVERecord?id=CVE-2026-53363 Référence CVE CVE-2026-53364 https://www.cve.org/CVERecord?id=CVE-2026-53364 Référence CVE CVE-2026-53365 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53316 Référence CVE CVE-2026-53317 https://www.cve.org/CVERecord?id=CVE-2026-53317 Référence CVE CVE-2026-53318 https://www.cve.org/CVERecord?id=CVE-2026-53318 Référence CVE CVE-2026-53319 https://www.cve.org/CVERecord?id=CVE-2026-53319 Référence CVE CVE-2026-53320 https://www.cve.org/CVERecord?id=CVE-2026-53320 Référence CVE CVE-2026-53321 https://www.cve.org/CVERecord?id=CVE-2026-53321 Référence CVE CVE-2026-53322 https://www.cve.org/CVERecord?id=CVE-2026-53322 Référence CVE CVE-2026-53323 https://www.cve.org/CVERecord?id=CVE-2026-53323 Référence CVE CVE-2026-53324 https://www.cve.org/CVERecord?id=CVE-2026-53324 Référence CVE CVE-2026-53357 https://www.cve.org/CVERecord?id=CVE-2026-53357 Référence CVE CVE-2026-53358 https://www.cve.org/CVERecord?id=CVE-2026-53358 Référence CVE CVE-2026-53359 https://www.cve.org/CVERecord?id=CVE-2026-53359 Référence CVE CVE-2026-53360 https://www.cve.org/CVERecord?id=CVE-2026-53360 Référence CVE CVE-2026-53364 https://www.cve.org/CVERecord?id=CVE-2026-53364 Référence CVE CVE-2026-53365 https://www.cve.org/CVERecord?id=CVE-2026-53365 Référence CVE CVE-2026-53367 https://www.cve.org/CVERecord?id=CVE-2026-53367 Référence CVE CVE-2026-53368 https://www.cve.org/CVERecord?id=CVE-2026-53368 Référence CVE CVE-2026-53369 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53329 Référence CVE CVE-2026-53331 https://www.cve.org/CVERecord?id=CVE-2026-53331 Référence CVE CVE-2026-53332 https://www.cve.org/CVERecord?id=CVE-2026-53332 Référence CVE CVE-2026-53339 https://www.cve.org/CVERecord?id=CVE-2026-53339 Référence CVE CVE-2026-53345 https://www.cve.org/CVERecord?id=CVE-2026-53345 Référence CVE CVE-2026-53347 https://www.cve.org/CVERecord?id=CVE-2026-53347 Référence CVE CVE-2026-53350 https://www.cve.org/CVERecord?id=CVE-2026-53350 Référence CVE CVE-2026-53355 https://www.cve.org/CVERecord?id=CVE-2026-53355 Référence CVE CVE-2026-53356 https://www.cve.org/CVERecord?id=CVE-2026-53356 Référence CVE CVE-2026-53357 https://www.cve.org/CVERecord?id=CVE-2026-53357 Référence CVE CVE-2026-53358 https://www.cve.org/CVERecord?id=CVE-2026-53358 Référence CVE CVE-2026-53359 https://www.cve.org/CVERecord?id=CVE-2026-53359 Référence CVE CVE-2026-53360 https://www.cve.org/CVERecord?id=CVE-2026-53360 Référence CVE CVE-2026-53366 https://www.cve.org/CVERecord?id=CVE-2026-53366 Référence CVE CVE-2026-53369 https://www.cve.org/CVERecord?id=CVE-2026-53369 Référence CVE CVE-2026-53374 https://www.cve.org/CVERecord?id=CVE-2026-53374 Référence CVE CVE-2026-53375 https://www.cve.org/CVERecord?id=CVE-2026-53375 Référence CVE CVE-2026-53376 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53270 Référence CVE CVE-2026-53273 https://www.cve.org/CVERecord?id=CVE-2026-53273 Référence CVE CVE-2026-53275 https://www.cve.org/CVERecord?id=CVE-2026-53275 Référence CVE CVE-2026-53297 https://www.cve.org/CVERecord?id=CVE-2026-53297 Référence CVE CVE-2026-53306 https://www.cve.org/CVERecord?id=CVE-2026-53306 Référence CVE CVE-2026-53324 https://www.cve.org/CVERecord?id=CVE-2026-53324 Référence CVE CVE-2026-53325 https://www.cve.org/CVERecord?id=CVE-2026-53325 Référence CVE CVE-2026-53354 https://www.cve.org/CVERecord?id=CVE-2026-53354 Référence CVE CVE-2026-53355 https://www.cve.org/CVERecord?id=CVE-2026-53355 Référence CVE CVE-2026-53357 https://www.cve.org/CVERecord?id=CVE-2026-53357 Référence CVE CVE-2026-53359 https://www.cve.org/CVERecord?id=CVE-2026-53359 Référence CVE CVE-2026-53366 https://www.cve.org/CVERecord?id=CVE-2026-53366 Référence CVE CVE-2026-53369 https://www.cve.org/CVERecord?id=CVE-2026-53369 Référence CVE CVE-2026-53374 https://www.cve.org/CVERecord?id=CVE-2026-53374 Référence CVE CVE-2026-53375 https://www.cve.org/CVERecord?id=CVE-2026-53375 Référence CVE CVE-2026-53376 https://www.cve.org/CVERecord?id=CVE-2026-53376 Référence CVE CVE-2026-53388 https://www.cve.org/CVERecord?id=CVE-2026-53388 Référence CVE CVE-2026-53391 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53263 Référence CVE CVE-2026-53266 https://www.cve.org/CVERecord?id=CVE-2026-53266 Référence CVE CVE-2026-53272 https://www.cve.org/CVERecord?id=CVE-2026-53272 Référence CVE CVE-2026-53274 https://www.cve.org/CVERecord?id=CVE-2026-53274 Référence CVE CVE-2026-53281 https://www.cve.org/CVERecord?id=CVE-2026-53281 Référence CVE CVE-2026-53285 https://www.cve.org/CVERecord?id=CVE-2026-53285 Référence CVE CVE-2026-53286 https://www.cve.org/CVERecord?id=CVE-2026-53286 Référence CVE CVE-2026-53287 https://www.cve.org/CVERecord?id=CVE-2026-53287 Référence CVE CVE-2026-53306 https://www.cve.org/CVERecord?id=CVE-2026-53306 Référence CVE CVE-2026-53357 https://www.cve.org/CVERecord?id=CVE-2026-53357 Référence CVE CVE-2026-53359 https://www.cve.org/CVERecord?id=CVE-2026-53359 Référence CVE CVE-2026-53362 https://www.cve.org/CVERecord?id=CVE-2026-53362 Référence CVE CVE-2026-53366 https://www.cve.org/CVERecord?id=CVE-2026-53366 Gestion détaillée du document le 31 juillet 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des

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

d?id=CVE-2026-53317 Référence CVE CVE-2026-53318 https://www.cve.org/CVERecord?id=CVE-2026-53318 Référence CVE CVE-2026-53319 https://www.cve.org/CVERecord?id=CVE-2026-53319 Référence CVE CVE-2026-53320 https://www.cve.org/CVERecord?id=CVE-2026-53320 Référence CVE CVE-2026-53321 https://www.cve.org/CVERecord?id=CVE-2026-53321 Référence CVE CVE-2026-53322 https://www.cve.org/CVERecord?id=CVE-2026-53322 Référence CVE CVE-2026-53323 https://www.cve.org/CVERecord?id=CVE-2026-53323 Référence CVE CVE-2026-53324 https://www.cve.org/CVERecord?id=CVE-2026-53324 Référence CVE CVE-2026-53354 https://www.cve.org/CVERecord?id=CVE-2026-53354 Référence CVE CVE-2026-53357 https://www.cve.org/CVERecord?id=CVE-2026-53357 Référence CVE CVE-2026-53358 https://www.cve.org/CVERecord?id=CVE-2026-53358 Référence CVE CVE-2026-53360 https://www.cve.org/CVERecord?id=CVE-2026-53360 Référence CVE CVE-2026-53364 https://www.cve.org/CVERecord?id=CVE-2026-53364 Référence CVE CVE-2026-53365 https://www.cve.org/CVERecord?id=CVE-2026-53365 Référence CVE CVE-2026-53367 https://www.cve.org/CVERecord?id=CVE-2026-53367 Référence CVE CVE-2026-53368 https://www.cve.org/CVERecord?id=CVE-2026-53368 Référence CVE CVE-2026-53369 https://www.cve.org/CVERecord?id=CVE-2026-53369 Référence CVE CVE-2026-53370 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53306 Référence CVE CVE-2026-53313 https://www.cve.org/CVERecord?id=CVE-2026-53313 Référence CVE CVE-2026-53325 https://www.cve.org/CVERecord?id=CVE-2026-53325 Référence CVE CVE-2026-53329 https://www.cve.org/CVERecord?id=CVE-2026-53329 Référence CVE CVE-2026-53339 https://www.cve.org/CVERecord?id=CVE-2026-53339 Référence CVE CVE-2026-53347 https://www.cve.org/CVERecord?id=CVE-2026-53347 Référence CVE CVE-2026-53350 https://www.cve.org/CVERecord?id=CVE-2026-53350 Référence CVE CVE-2026-53355 https://www.cve.org/CVERecord?id=CVE-2026-53355 Référence CVE CVE-2026-53356 https://www.cve.org/CVERecord?id=CVE-2026-53356 Référence CVE CVE-2026-53357 https://www.cve.org/CVERecord?id=CVE-2026-53357 Référence CVE CVE-2026-53358 https://www.cve.org/CVERecord?id=CVE-2026-53358 Référence CVE CVE-2026-53359 https://www.cve.org/CVERecord?id=CVE-2026-53359 Référence CVE CVE-2026-53360 https://www.cve.org/CVERecord?id=CVE-2026-53360 Référence CVE CVE-2026-53362 https://www.cve.org/CVERecord?id=CVE-2026-53362 Référence CVE CVE-2026-53366 https://www.cve.org/CVERecord?id=CVE-2026-53366 Gestion détaillée du document le 24 juillet 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gou

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

d?id=CVE-2026-53317 Référence CVE CVE-2026-53318 https://www.cve.org/CVERecord?id=CVE-2026-53318 Référence CVE CVE-2026-53319 https://www.cve.org/CVERecord?id=CVE-2026-53319 Référence CVE CVE-2026-53320 https://www.cve.org/CVERecord?id=CVE-2026-53320 Référence CVE CVE-2026-53321 https://www.cve.org/CVERecord?id=CVE-2026-53321 Référence CVE CVE-2026-53322 https://www.cve.org/CVERecord?id=CVE-2026-53322 Référence CVE CVE-2026-53323 https://www.cve.org/CVERecord?id=CVE-2026-53323 Référence CVE CVE-2026-53324 https://www.cve.org/CVERecord?id=CVE-2026-53324 Référence CVE CVE-2026-53354 https://www.cve.org/CVERecord?id=CVE-2026-53354 Référence CVE CVE-2026-53357 https://www.cve.org/CVERecord?id=CVE-2026-53357 Référence CVE CVE-2026-53358 https://www.cve.org/CVERecord?id=CVE-2026-53358 Référence CVE CVE-2026-53360 https://www.cve.org/CVERecord?id=CVE-2026-53360 Référence CVE CVE-2026-53364 https://www.cve.org/CVERecord?id=CVE-2026-53364 Référence CVE CVE-2026-53365 https://www.cve.org/CVERecord?id=CVE-2026-53365 Référence CVE CVE-2026-53367 https://www.cve.org/CVERecord?id=CVE-2026-53367 Référence CVE CVE-2026-53368 https://www.cve.org/CVERecord?id=CVE-2026-53368 Référence CVE CVE-2026-53369 https://www.cve.org/CVERecord?id=CVE-2026-53369 Référence CVE CVE-2026-53370 https://www.cve.org/CVERecord?id=

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

de sécurité Microsoft Azure Linux CVE-2026-53347 du 02 juillet 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53349 du 02 juillet 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53352 du 02 juillet 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53353 du 02 juillet 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53355 du 02 juillet 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53356 du 02 juillet 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-12912 du 03 juillet 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-14164 du 03 juillet 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53357 du 03 juillet 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-12413 du 04 juillet 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-50721 du 04 juillet 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-50722 du 04 juillet 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53223 du 04 juillet 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53269 du 09 juillet 2026 Une gestion de version détaillée se trouve à la fin de ce document. Risque Non spécifié par l'éditeur Systèmes affectés azl3 kernel 6.6.139.1-1 versions antérieures à 6.6.143.1-1 azl3 libarchive 3.7.7-6 versions antérieures à 3.7.7-7 azl3 libres

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

d?id=CVE-2026-53339 Référence CVE CVE-2026-53341 https://www.cve.org/CVERecord?id=CVE-2026-53341 Référence CVE CVE-2026-53343 https://www.cve.org/CVERecord?id=CVE-2026-53343 Référence CVE CVE-2026-53349 https://www.cve.org/CVERecord?id=CVE-2026-53349 Référence CVE CVE-2026-53350 https://www.cve.org/CVERecord?id=CVE-2026-53350 Référence CVE CVE-2026-53352 https://www.cve.org/CVERecord?id=CVE-2026-53352 Référence CVE CVE-2026-53354 https://www.cve.org/CVERecord?id=CVE-2026-53354 Référence CVE CVE-2026-53355 https://www.cve.org/CVERecord?id=CVE-2026-53355 Référence CVE CVE-2026-53356 https://www.cve.org/CVERecord?id=CVE-2026-53356 Référence CVE CVE-2026-53357 https://www.cve.org/CVERecord?id=CVE-2026-53357 Référence CVE CVE-2026-53359 https://www.cve.org/CVERecord?id=CVE-2026-53359 Référence CVE CVE-2026-53361 https://www.cve.org/CVERecord?id=CVE-2026-53361 Référence CVE CVE-2026-53362 https://www.cve.org/CVERecord?id=CVE-2026-53362 Gestion détaillée du document le 10 juillet 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des

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

Linuxカーネルにおいて、以下の脆弱性が修正されました。Bluetoothに関するもので、l2cap_sock_cleanup_listen()とl2cap_conn_del()間のUse-After-Free（UAF）に関する修正です。bt_accept_dequeue()は、まだ受け入れられていない子ソケットを親のacceptキューから切り離し、リターン前にrelease_sock()を呼び出します。そのため、戻り値のskは呼び出し元の参照を持たず、ロックが解除された状態になります。l2cap_sock_cleanup_listen()は、リスニングソケットのクローズ時にこれらの子ソケットを処理します。一方で、並行して発生するHCI切断によりhci_rx_work -＞ l2cap_conn_del()が呼ばれ、l2cap_chan_del()およびl2cap_sock_kill()が実行され、子ソケットとそのl2capチャネルが解放されます。cleanup_listen()はその後、これら解放済みのオブジェクトを使用してしまいます。BUG: KASAN: slab-use-after-free in l2cap_sock_kill l2cap_sock_kill / l2cap_sock_cleanup_listen / __x64_sys_close 解放元: l2cap_conn_del -＞ l2cap_sock_close_cb -＞ l2cap_sock_kill。この問題は、この領域で既に行われている2つの修正とは異なります。コミットe83f5e24da741（"Bluetooth: serialize accept_q access"）はaccept_qのリスト/ポーリングを直列化し、bt_accept_dequeue()内で一時的参照を取得しています。また、CVE-2025-39860ではl2cap_sock_release()でlock_sock()のもとにcleanup_listen()を呼び、ユーザースペースのclose()/accept()競合を直列化しています。しかしどちらもhci_rx_workから実行されるl2cap_conn_del()はカバーしておらず、このUAFは現行のbluetooth/masterブランチ上で再現可能でした。ソース側で参照を取得する部分は、bt_accept_dequeue()がskをロックした状態でsock_hold()を行い、その後release_sock()を呼び出すことです。呼び出し元はsock_put()を行います。cleanup_listen()は子skを短時間ロックした状態でl2cap_chan_hold_unless_zero()によりチャネルを固定し（l2cap_sock_teardown_cb()との直列化を図り）、その後l2cap_chan_lock()の前にロックを解除し、SOCK_DEAD状態に対する重複したl2cap_sock_kill()をスキップします。conn-＞lockは取得せず、cleanup_listen()は親skロック下で実行されるため、conn-＞lock -＞ chan-＞lock -＞ sk_lockのデッドロックを避けています。KASAN/SMP環境において、権限のないリスニング/クローズとHCI切断の競合は、この修正前には1回の実行あたり12件のUse-After-Freeレポートを生成していました。しかしこの修正後は、bluetooth/masterブランチ上で1600回以上の競合試行にもかかわらず0件のレポートとなり、かつlockdepレポートも発生していません。

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: < 5.7, 5.10.259 ≤ 5.10.*, 5.15.210 ≤ 5.15.*, 6.1.175 ≤ 6.1.*, 6.6.142 ≤ 6.6.*, 6.12.92 ≤ 6.12.*, 6.18.34 ≤ 6.18.*, 7.0.11 ≤ 7.0.*, 7.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 2 Jul 2026 · Last source change 5 Aug 2026, 12:35 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-41372
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-2026-41372↗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-53357 · cve.blacktree.nl