net/9p: use a dedicated spinlock for trans_fd
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 296ab4a813841ba1d5f40b03190fd1bd8f25aab0, Kernel 43bbadb7e4636dc02f6a283c2a39e6438e6173cd and Kernel 717b9b4f38703d7f5293059e3a242d16f76fa045.
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)
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =2.6.28, >=673d62cdaac6ffbce980a349d3174b3929ceb9e5 <296ab4a813841ba1d5f40b03190fd1bd8f25aab0, >=673d62cdaac6ffbce980a349d3174b3929ceb9e5 <43bbadb7e4636dc02f6a283c2a39e6438e6173cd, >=673d62cdaac6ffbce980a349d3174b3929ceb9e5 <717b9b4f38703d7f5293059e3a242d16f76fa045 | 296ab4a813841ba1d5f40b03190fd1bd8f25aab0, 43bbadb7e4636dc02f6a283c2a39e6438e6173cd, 717b9b4f38703d7f5293059e3a242d16f76fa045 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket