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)
References
Configurations
Configuration 1 (hide)
|
History
06 Nov 2025, 21:58
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://git.kernel.org/stable/c/296ab4a813841ba1d5f40b03190fd1bd8f25aab0 - Patch | |
| References | () https://git.kernel.org/stable/c/43bbadb7e4636dc02f6a283c2a39e6438e6173cd - Patch | |
| References | () https://git.kernel.org/stable/c/717b9b4f38703d7f5293059e3a242d16f76fa045 - Patch | |
| First Time |
Linux
Linux linux Kernel |
|
| CVSS |
v2 : v3 : |
v2 : unknown
v3 : 5.5 |
| CPE | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | |
| Summary |
|
|
| CWE | CWE-667 |
01 May 2025, 15:15
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2025-05-01 15:15
Updated : 2025-11-06 21:58
NVD link : CVE-2022-49765
Mitre link : CVE-2022-49765
CVE.ORG link : CVE-2022-49765
JSON object : View
Products Affected
linux
- linux_kernel
CWE
CWE-667
Improper Locking
