CVE-2022-50410: Linux Kernel buffer overflow (CVSS 9.8)

Description

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.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Linux Kernel≥ 5.11 < 5.15.75 · ≥ 5.16 < 5.19.17 · ≥ 6.0 < 6.0.3 · < 5.10.220

Remediation

Fixed in

Linux Kernel≥ 5.15.75

Patch & vendor advisories

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2022-50410 being actively exploited?

CVE-2022-50410 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.43%.

How severe is CVE-2022-50410?

CVE-2022-50410 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.43% probability of exploitation.

Which products are affected by CVE-2022-50410?

Affected products include Linux Kernel.

How do I fix CVE-2022-50410?

Upgrade affected software to a fixed version, for example Linux Kernel 5.15.75 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2022-50410 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo