high · 8.8

Bluetooth: ISO: hold sk properly in iso_conn_ready

CVE-2026-74537 · published 15 Aug 2026

How serious is it

  • Severity: high, CVSS score 8.8 out of 10.
  • No exploit prediction (EPSS) score yet.
  • Not on the CISA list of exploited vulnerabilities.
  • No public exploit in Exploit-DB.

Is your app affected by CVE-2026-74537?

Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.

Who is affected

  • Linux Linux: 27c24fda62b601d6f9ca5e992502578c4310876f to < 44590dc53c9e949d2fed399a571a89c3d7d0b245, 27c24fda62b601d6f9ca5e992502578c4310876f to < 99b65f0ea3370c13687ff870330c425b6ca44e89, 27c24fda62b601d6f9ca5e992502578c4310876f to < 4e9b5e8669b3602a4e01b6d1e9539b72e42c84d5, 27c24fda62b601d6f9ca5e992502578c4310876f to < 1308d72903d792d10b82bc4ef08b8a4452308b04
  • Linux Linux: 5.15

How to check

  1. Find out whether you run the affected product and which version, then compare it with the versions above.

How to fix

Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
  1. Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
  2. If a vulnerable version was live, check your logs and rotate the secrets that server could read.

The advisory

In 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.

Check your whole app

Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.

References

Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON