A recent flaw in the Linux kernel causes a deadlock when the function skb_may_tx_timestamp() acquires the sock::sk_callback_lock while operating in interrupt context. Because this lock should only be taken in softirq or main context, the kernel may block when it is already write‑locked on the same CPU, leading to a halt in socket activity. The weakness corresponds to CWE‑665, Improper Lock Handling and is mitigated by dropping the lock and accessing the socket pointer safely with READ_ONCE()/WRITE_ONCE().

The vulnerability applies to any Linux kernel that implements skb_may_tx_timestamp() and uses drivers that obtain timestamps via dedicated interrupts. No specific kernel version is listed, so all current kernels enabling transmit timestamping features may be affected.

The EPSS score is not available and the CVE is not yet listed in the CISA KEV catalog, indicating no known active exploits. An attacker who can open sockets that request transmit timestamps or otherwise trigger the timestamp handler might induce a deadlock, causing a local denial‑of‑service. The likely attack vector is a local user or privileged process interacting with network sockets, as the exploit requires engaging the kernel’s transmit timestamping path.