CVE-2026-74536

Bluetooth: ISO: fix leaking sk after socket release

N/A
Published: August 15, 2026 at 12:27 PM UTC
Updated: August 17, 2026 at 06:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: fix leaking sk after socket release iso_sock_kill() tests !sock_flag(sk, SOCK_ZAPPED) || sk->sk_socket || sock_flag(sk, SOCK_DEAD) for early return, but this is always true since sock_orphan(sk) sets SOCK_DEAD, so the sk reference released by socket always leaks, iso_sock_destruct is never called. The socket reference also leaks when __iso_sock_close() does not set SOCK_ZAPPED, since iso_conn_del() does not call iso_sock_kill() after zapping. Fix by replacing SOCK_DEAD by BT_SK_KILLED flag that is not used for something else, and lock_sock to ensure iso_sock_kill() puts sk only after socket release only once. Release and iso_conn_del may run concurrently. Call iso_sock_kill() from iso_conn_del() to clean sk up after zapping. Remove call to iso_sock_kill() from iso_sock_close(), as it's generally no-op there.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.0 ≤ v < 6.12.1036.0 ≤ v < 6.18.446.0 ≤ v < 7.1.86.0 ≤ v < 7.26.0ccf74f2390d60a2f9a75ef496d2564abb478f46a
Vendor states this is fixed in 96ed3c772c08e7a91c399567f412618e43231023 (fixed)
Vendor states this is fixed in ce57442a379212fe3fda59c9437ee8217eceb5b1 (fixed)
Vendor states this is fixed in e30e5ca63c8fbe3cd505fbb419bb547760cda633 (fixed)
Vendor states this is fixed in e76a0ae6542ae43241b2147bacf4990e7ae5316a (fixed)
Vendor states this is fixed in 6.0 (unaffected)
Vendor states this is fixed in 6.12.103 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card