CVE-2022-50410
What it is
In the Linux kernel, the following vulnerability has been resolved: NFSD: Protect against send buffer overflow in NFSv2 READ Since before the git era, NFSD has conserved the number of pages held by each nfsd thread by combining the RPC receive and send buffers into a single array of pages. This works because there are no cases where an operation needs a large RPC Call message and a large RPC Reply at the same time. Once an RPC Call has been received, svc_process() updates svc_rqst::rq_res to describe the part of rq_pages that can be used for constructing the Reply. This means that the send buffer (rq_res) shrinks when the received RPC record containing the RPC Call is large. A client can force this shrinkage on TCP by sending a correctly- formed RPC Call header contained in an RPC record that is excessively large. The full maximum payload size cannot be constructed in that case.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.4% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.4% in the next 30 days (EPSS).
- Severity: 9.8 CRITICAL (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.4% · EPSS, next 30 days
- Weakness
- CWE-787 · Out-of-bounds write
- Record status
- Modified
Affected
- Linux Kernel < 5.10.220
- Linux Kernel < 5.15.75
- Linux Kernel < 5.19.17
- Linux Kernel < 6.0.3
Attack profile CVSS 3.1 · 9.8
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2022-50410.md and follow it. Check whether this project is affected by CVE-2022-50410. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/1868332032eccbab8c1878a0d918193058c0a905
- https://git.kernel.org/stable/c/2007867c5874134f2271eb276398208070049dd3
- https://git.kernel.org/stable/c/2be9331ca6061bc6ea32247266f45b8b21030244
- https://git.kernel.org/stable/c/401bc1f90874280a80b93f23be33a0e7e2d1f912
- https://git.kernel.org/stable/c/ea4c3eee0fd72fcedaa238556044825639cd3607
References
- https://git.kernel.org/stable/c/1868332032eccbab8c1878a0d918193058c0a905
- https://git.kernel.org/stable/c/2007867c5874134f2271eb276398208070049dd3
- https://git.kernel.org/stable/c/2be9331ca6061bc6ea32247266f45b8b21030244
- https://git.kernel.org/stable/c/401bc1f90874280a80b93f23be33a0e7e2d1f912
- https://git.kernel.org/stable/c/ea4c3eee0fd72fcedaa238556044825639cd3607