CVE-2026-74536

CVE CVE-2026-74536EUVD EUVD-2026-59729Published 2026-08-15T12:27:49.000ZLast changed 2026-08-17T05:21:20.000Z

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux patch: 6.18.44; ccf74f2390d60a2f9a75ef496d2564abb478f46a <ce57442a379212fe3fda59c9437ee8217eceb5b1; patch: 0; patch: 6.12.103; ccf74f2390d60a2f9a75ef496d2564abb478f46a <e30e5ca63c8fbe3cd505fbb419bb547760cda633; patch: 7.2; 6.0; ccf74f2390d60a2f9a75ef496d2564abb478f46a <e76a0ae6542ae43241b2147bacf4990e7ae5316a; patch: 7.1.8; ccf74f2390d60a2f9a75ef496d2564abb478f46a <96ed3c772c08e7a91c399567f412618e43231023

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.