In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: Fix possible deadlock in rfcomm_sk_state_change
syzbot reports a possible deadlock in rfcomm_sk_state_change [1]. While rfcomm_sock_connect acquires the sk lock and waits for the rfcomm lock, rfcomm_sock_release could have the rfcomm lock and hit a deadlock for acquiring the sk lock. Here's a simplified flow:
rfcomm_sock_connect: lock_sock(sk) rfcomm_dlc_open: rfcomm_lock()
rfcomm_sock_release: rfcomm_sock_shutdown: rfcomm_lock() __rfcomm_dlc_close: rfcomm_k_state_change: lock_sock(sk)
This patch drops the sk lock before calling rfcomm_dlc_open to avoid the possible deadlock and holds sk's reference count to prevent use-after-free after rfcomm_dlc_open completes.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Debian | — | Upgrade linux | Mar 31, 2025 | Mar 27, 2025 |
| Redhat_linux | — | Upgrade kernelNo solution existsUpgrade kernel-rt | Jul 9, 2025 | Mar 27, 2025 |
| Ubuntu | — | Upgrade linux-intel-iot-realtimeUpgrade linux-azure-5.15Upgrade linux-gcpUpgrade linux-intel-iotg-5.15Upgrade linuxUpgrade linux-ibmUpgrade linux-gkeopUpgrade linux-nvidiaUpgrade linux-oracleUpgrade linux-kvmUpgrade linux-aws-5.15Upgrade linux-riscv-5.15Upgrade linux-intel-iotgUpgrade linux-oracle-5.15Upgrade linux-nvidia-tegra-5.15Upgrade linux-gcp-5.15Upgrade linux-lowlatencyUpgrade linux-bluefieldUpgrade linux-azure-fdeUpgrade linux-lowlatency-hwe-5.15Upgrade linux-raspiUpgrade linux-gkeUpgrade linux-azureUpgrade linux-realtimeUpgrade linux-awsUpgrade linux-hwe-5.15 | Apr 1, 2025 | Mar 27, 2025 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub