CVE-2026-63946
What it is
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: fix UAF in iso_recv_frame iso_recv_frame reads conn->sk under iso_conn_lock but releases the lock before using sk, with no reference held. A concurrent iso_sock_kill() can free sk in that window, causing use-after-free on sk->sk_state and sock_queue_rcv_skb(). Fix by replacing the bare pointer read with iso_sock_hold(conn), which calls sock_hold() while the spinlock is held, atomically elevating the refcount before the lock drops. Add a drop_put label so sock_put() is called on all exit paths where the hold succeeded.
At a glance
- Exploitability
- Can be exploited from the same network segment without logging in. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 8.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Weakness
- CWE-362 · Race condition
- Record status
- Analyzed
Affected
- Linux Kernel < 6.1.176
- Linux Kernel < 6.6.143
- Linux Kernel < 6.12.93
- Linux Kernel < 6.18.35
- Linux Kernel < 7.0.12
- Linux Kernel 7.1
Attack profile CVSS 3.1 · 8.8
- Attack vector
- Adjacent network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-63946.md and follow it. Check whether this project is affected by CVE-2026-63946. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/119fb6f80c44dc1c65d604cf28e64c56bd9b6568
- https://git.kernel.org/stable/c/1a6b803b00ccdd7666506adbe01ddae1c72d1ca9
- https://git.kernel.org/stable/c/47f23a259517abbdb8032c057a1e8a6bf3734878
- https://git.kernel.org/stable/c/b04ec131325baf4ea4577d6c6e6b86cf092e3731
- https://git.kernel.org/stable/c/c318aa51830a3d2cc1229968fe521441c97356cd
- https://git.kernel.org/stable/c/c57ea90f203c8b8b41a474f19a09000d0f841436
References
- https://git.kernel.org/stable/c/119fb6f80c44dc1c65d604cf28e64c56bd9b6568
- https://git.kernel.org/stable/c/1a6b803b00ccdd7666506adbe01ddae1c72d1ca9
- https://git.kernel.org/stable/c/47f23a259517abbdb8032c057a1e8a6bf3734878
- https://git.kernel.org/stable/c/b04ec131325baf4ea4577d6c6e6b86cf092e3731
- https://git.kernel.org/stable/c/c318aa51830a3d2cc1229968fe521441c97356cd
- https://git.kernel.org/stable/c/c57ea90f203c8b8b41a474f19a09000d0f841436