The Quarterly Threat Landscape Report is out. See what attackers are targeting now.Read report
In the Linux kernel, the following vulnerability has been resolved:
net/9p: use a dedicated spinlock for trans_fd
Shamelessly copying the explanation from Tetsuo Handa's suggested patch[1] (slightly reworded): syzbot is reporting inconsistent lock state in p9_req_put()[2], for p9_tag_remove() from p9_req_put() from IRQ context is using spin_lock_irqsave() on "struct p9_client"->lock but trans_fd (not from IRQ context) is using spin_lock().
Since the locks actually protect different things in client.c and in trans_fd.c, just replace trans_fd.c's lock by a new one specific to the transport (client.c's protect the idr for fid/tag allocations, while trans_fd.c's protects its own req list and request status field that acts as the transport's state machine)
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Debian | — | Upgrade linux | May 5, 2025 | May 1, 2025 |
| Redhat_linux | — | No solution exists | Jul 9, 2025 | May 1, 2025 |
| Ubuntu | — | Upgrade linux-gkeUpgrade linux-gcp-5.15Upgrade linux-lowlatency-hwe-5.15Upgrade linux-nvidiaUpgrade linux-kvmUpgrade linux-azureUpgrade linux-raspiUpgrade linux-intel-iotg-5.15Upgrade linux-riscv-5.15Upgrade linux-bluefieldUpgrade linux-intel-iotgUpgrade linux-azure-fdeUpgrade linux-aws-5.15Upgrade linux-gcpUpgrade linux-awsUpgrade linux-hwe-5.15Upgrade linux-oracleUpgrade linux-realtimeUpgrade linux-lowlatencyUpgrade linux-ibmUpgrade linux-azure-5.15Upgrade linuxUpgrade linux-nvidia-tegra-5.15Upgrade linux-azure-fde-5.15Upgrade linux-gkeopUpgrade linux-oracle-5.15Upgrade linux-intel-iot-realtime | May 8, 2025 | May 1, 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