CVE-2022-49765
net/9p: use a dedicated spinlock for trans_fd
We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.
Please see our statement on Data Privacy.
net/9p: use a dedicated spinlock for trans_fd
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)
Reserved 2025-04-16 | Published 2025-05-01 | Updated 2025-05-04 | Assigner Linuxgit.kernel.org/...c/43bbadb7e4636dc02f6a283c2a39e6438e6173cd
git.kernel.org/...c/717b9b4f38703d7f5293059e3a242d16f76fa045
git.kernel.org/...c/296ab4a813841ba1d5f40b03190fd1bd8f25aab0
Support options
