Vulnerability · CVE-2022-49765
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
Published May 1, 2025 · catalog updated May 11, 2026 · Linux Linux
Check this week
CVE-2022-49765 is not in CISA KEV. FIRST estimates a 15.00% chance of exploitation in the next 30 days. Check whether you run Linux Linux.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- None0.0
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 15.00%
- Remediation
- Version ranges on file
- Affected products
- vendor Linux Linux 673d62cdaac6ffbce980a349d3174b3929ceb9e5 <43bbadb7e4636dc02f6a283c2a39e6438e6173cd
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 (clie
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor Linux Linux 673d62cdaac6ffbce980a349d3174b3929ceb9e5 <43bbadb7e4636dc02f6a283c2a39e6438e6173cd673d62cdaac6ffbce980a349d3174b3929ceb9e5 <43bbadb7e4636dc02f6a283c2a39e6438e6173cd
How to fix CVE-2022-49765
Recommended remediation
Affected version ranges suggest a fixed boundary. Verify against the vendor advisory for your release.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
CVE-2022-49765 is not in CISA KEV. FIRST estimates a 15.00% chance of exploitation in the next 30 days. Check whether you run Linux Linux.
Which versions are affected?
Compare what you have installed with Linux Linux 673d62cdaac6ffbce980a349d3174b3929ceb9e5 <43bbadb7e4636dc02f6a283c2a39e6438e6173cd 673d62cdaac6ffbce980a349d3174b3929ceb9e5 <43bbadb7e4636dc02f6a283c2a39e6438e6173cd. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 15.00%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
May 1, 2025 · EUVD
Detected
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 (
May 11, 2026 · EUVD
Updated
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 (
Sources
- CVE.orgVulnerability recordCVE-2022-49765
Official CVE identifier
cve.org - EUVDVulnerability recordEUVD-2025-13022
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
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog Oct 17, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.