net/9p: use a dedicated spinlock for trans_fd
Published May 1, 2025
5.5
MEDIUMCVSS 3.1
EPSS 0.15%
Description
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 products
-
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version
-
- Version 2.6.28StatusaffectedConstraints-
- Version 0StatusunaffectedConstraints<2.6.28
- Version 5.15.80StatusunaffectedConstraints<=5.15.*
- Version 6.0.10StatusunaffectedConstraints<=6.0.*
- Version 6.1StatusunaffectedConstraints<=*
- Version
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
- < 5.15.80
- ≥ 5.16 · < 6.0.10
No data.
Red Hat Enterprise Linux 10
kernel
Not affected
Red Hat Enterprise Linux 6
kernel
Out of support scope
Red Hat Enterprise Linux 7
kernel
Not affected
Red Hat Enterprise Linux 7
kernel-rt
Not affected
Red Hat Enterprise Linux 8
kernel
Not affected
Red Hat Enterprise Linux 8
kernel-rt
Not affected
Red Hat Enterprise Linux 9
kernel
Not affected
Red Hat Enterprise Linux 9
kernel-rt
Not affected
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Not affected | n/a |
| Red Hat Enterprise Linux 6 | kernel | Out of support scope | n/a |
| Red Hat Enterprise Linux 7 | kernel | Not affected | n/a |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | n/a |
| Red Hat Enterprise Linux 8 | kernel | Not affected | n/a |
| Red Hat Enterprise Linux 8 | kernel-rt | Not affected | n/a |
| Red Hat Enterprise Linux 9 | kernel | Not affected | n/a |
| Red Hat Enterprise Linux 9 | kernel-rt | Not affected | n/a |
No package ranges for this CVE.
Remediation
No remediation recorded yet.
References (9)
- https://access.redhat.com/security/cve/CVE-2022-49765 Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=2363479 Issue Tracking
- https://euvd.enisa.europa.eu/vulnerability/EUVD-2025-13022 Advisory
- https://git.kernel.org/stable/c/296ab4a813841ba1d5f40b03190fd1bd8f25aab0 Patch
- https://git.kernel.org/stable/c/43bbadb7e4636dc02f6a283c2a39e6438e6173cd Patch
- https://git.kernel.org/stable/c/717b9b4f38703d7f5293059e3a242d16f76fa045 Patch
- https://lore.kernel.org/linux-cve-announce/2025050113-CVE-2022-49765-731b@gregkh/T
- https://nvd.nist.gov/vuln/detail/CVE-2022-49765
- https://www.cve.org/CVERecord?id=CVE-2022-49765
Change history (0)
No recorded changes yet.