CVE-2026-74537
HighIn the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: hold sk properly in iso_conn_ready sk deref in iso_conn_ready must be done either under conn->lock, or holding a refcount, to avoid concurrent close. conn->sk is currently accessed without either: [Task 1] [Task 2] iso_sock_release iso_conn_ready sk = conn->sk lock_sock(sk) conn->sk = NULL lock_sock(sk) release_sock(sk) iso_sock_kill(sk) UAF on sk deref Fix possible UAF by holding sk refcount in iso_conn_ready(). Also recheck after lock_sock that the socket is still valid. Adjust locking so conn->sk is cleared only under lock_sock.
CVSS 3.1 score
8.8
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected versions
Linux kernel versions
5.15
and later are affected. Fixed in
6.18.44,
7.1.8,
7.2
and their respective stable series.
References
3 totalFrequently asked questions
-
What is CVE-2026-74537?
CVE-2026-74537 is a High severity Linux kernel vulnerability with a CVSS score of 8.8 out of 10 . It affects Linux kernel versions from 5.15 onward and has been patched in 6.18.44, 7.1.8 and 7.2. CVE-2026-74537 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2026-74537?
CVE-2026-74537 has a CVSS score of 8.8 out of 10, rated High severity (CVSS 3.1). The vector string is
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. -
Is there a patch available for CVE-2026-74537?
Yes. CVE-2026-74537 has been patched. Fixed versions include 6.18.44, 7.1.8 and 7.2. If you are running Linux kernel 5.15 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-74537 actively exploited?
No. CVE-2026-74537 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.