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.
Published: 2026-08-15
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The Linux kernel contains a design flaw in its Bluetooth ISO socket handling logic. When an ISO socket is closed, the reference to the socket object may not be released correctly, causing a stale reference to accumulate as sockets are repeatedly created and destroyed. While the description does not indicate an immediate denial‑of‑service, a steady leak could exhaust kernel memory or leave orphaned socket descriptors, potentially destabilizing the system.

Affected Systems

The defect resides in the core Linux kernel image, specifically within the Bluetooth ISO implementation. All kernel packages that include the affected source code are potentially impacted. Because the CPE indicates a kernel‑wide scope and no specific version range is listed, any kernel built with the default Bluetooth ISO stack should be considered vulnerable until the upstream changes are incorporated.

Risk and Exploitability

Based on the description, it is inferred that the attack vector requires a local user with permission to create Bluetooth ISO sockets. The flaw can be exercised by any such process. The CVSS score of 5.5 reflects a moderate impact. The EPSS score is less than 1%, indicating a low likelihood of exploitation. The vulnerability is not listed in the CISA KEV catalog. An attacker would need to repeatedly open and close ISO connections to manifest a memory leak, which is more likely to degrade system stability than directly compromise confidentiality or integrity. Thus, the overall risk is low to moderate.

Generated by OpenCVE AI on August 21, 2026 at 21:45 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Patch the kernel to incorporate the Bluetooth ISO socket reference‑leak fix found in the commits referenced in the advisory (e.g., 96ed3c772c08e7a91c399567f412618e43231023, ce57442a379212fe3fda59c9437ee8217eceb5b1, e30e5ca63c8fbe3cd505fbb419bb547760cda633, e76a0ae6542ae43241b2147bacf4990e7ae5316a).
  • If an immediate kernel upgrade is not available, disable the Bluetooth ISO socket functionality via module options or kernel configuration (e.g., set CONFIG_BT_ISOC to n).
  • Monitor kernel memory usage and socket counts regularly; if abnormal growth is detected, plan a reboot or apply the patch as soon as possible.

Generated by OpenCVE AI on August 21, 2026 at 21:45 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DSA Debian DSA DSA-6466-1 linux security update
History

Thu, 20 Aug 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-911
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Low


Sat, 15 Aug 2026 12:45:00 +0000

Type Values Removed Values Added
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.
Title Bluetooth: ISO: fix leaking sk after socket release
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-17T05:21:20.361Z

Reserved: 2026-08-15T05:44:03.913Z

Link: CVE-2026-74536

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-15T13:17:58.940

Modified: 2026-08-17T06:19:50.720

Link: CVE-2026-74536

cve-icon Redhat

Severity : Low

Publid Date: 2026-08-15T00:00:00Z

Links: CVE-2026-74536 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-21T22:00:15Z

Weaknesses
  • CWE-911

    Improper Update of Reference Count