CVE Catalog

CVE-2026-74536

Low risk· EPSS 7%
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.17%

7th percentile - higher than 7% of all known CVEs

Summary

In the Linux kernel, in the Bluetooth ISO subsystem, a socket reference leak was found after socket release. The early return condition in iso_sock_kill() is always true because sock_orphan() sets SOCK_DEAD, so the reference is never released and the socket destructor is never called. Additionally, the reference leaks when __iso_sock_close() does not set SOCK_ZAPPED, since iso_conn_del() does not call iso_sock_kill() after zapping.

Risk Assessment

Memory leak in the kernel can lead to gradual exhaustion of system resources, potentially causing system instability or denial of service (DoS) over time.

Recommendation

Apply the kernel patch that replaces SOCK_DEAD with the new BT_SK_KILLED flag and ensures proper reference release. Update the system to a kernel version containing this fix.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS