CVE Catalog

CVE-2026-63945

HighCVSS 7.8
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.16%

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

Summary

In the Linux kernel's Bluetooth ISO subsystem, a race condition was found in iso_sock_clear_timer(). The function reads the connection pointer without holding the socket lock, which can lead to a NULL pointer dereference or use-after-free (UAF) when the socket is being closed concurrently.

Risk Assessment

A local attacker could exploit this vulnerability to cause a system crash (kernel panic) or potentially escalate privileges if they can control the freed memory.

Recommendation

Apply the Linux kernel patch immediately, which moves iso_sock_clear_timer() inside lock_sock() to ensure safe access to the connection structure.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: serialize iso_sock_clear_timer with socket lock iso_sock_close() calls iso_sock_clear_timer() before acquiring lock_sock(sk). iso_sock_clear_timer() reads iso_pi(sk)->conn twice without the socket lock held: if (!iso_pi(sk)->conn) return; cancel_delayed_work(&iso_pi(sk)->conn->timeout_work); Concurrently, iso_conn_del() executes under lock_sock(sk) and calls iso_chan_del(), which sets iso_pi(sk)->conn to NULL and may result in the final reference to the connection being dropped: CPU0 CPU1 ---- ---- iso_sock_clear_timer() if (conn != NULL) ... lock_sock(sk) iso_chan_del() iso_pi(sk)->conn = NULL cancel_delayed_work(conn) /* NULL deref or UAF */ iso_pi(sk)->conn is not stable across the unlock window, causing a NULL pointer dereference or use-after-free. Serialize iso_sock_clear_timer() with the socket lock by moving it inside lock_sock()/release_sock(), matching the pattern used in iso_conn_del() and all other call sites.

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