The Linux kernel Bluetooth ISO socket code had a race condition where iso_sock_clear_timer() read iso_pi(sk)->conn twice without holding the socket lock. Concurrent execution of iso_conn_del() under the socket lock could set iso_pi(sk)->conn to NULL, causing iso_sock_clear_timer() to dereference a NULL pointer or use freed memory. The fix involved moving iso_sock_clear_timer() inside the lock_sock()/release_sock() critical section to ensure serialization and prevent the race.

This vulnerability could lead to kernel NULL pointer dereference or use-after-free conditions, potentially causing kernel crashes or instability. There is no indication of known exploits in the wild. The impact is limited to denial of service or system instability rather than privilege escalation or code execution based on the provided data.

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability was resolved by serializing iso_sock_clear_timer() with the socket lock in the Linux kernel source code. Users should apply the official Linux kernel updates once available to address this issue.