LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50410: NFSD: Protect against send buffer overflow in NFSv2 READ

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.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Linux kernel NFSD flaw can cause a send buffer overflow during NFSv2 READ handling. Systems running the kernel NFS server are the concern. The source describes a crafted, oversized RPC record causing reply-buffer shrinkage. Impact is rated high because memory corruption could affect confidentiality, integrity, and availability.

Executive priority

Prioritize remediation for Linux NFS servers, especially shared infrastructure or systems reachable by untrusted users or networks. Business urgency is high but not emergency-level from the provided evidence because active exploitation is not shown.

Technical view

NFSD reuses one page array for RPC receive and send buffers. After receiving a large TCP RPC record, svc_process() can reduce rq_res space for the reply. In NFSv2 READ handling, that can overflow the send buffer. The issue is classified as CWE-787 with CVSS 3.1 score 7.8.

Likely exposure

Exposure is most likely on Linux systems running affected kernel versions with NFSD serving NFSv2. The bundle does not provide distribution package names, enabled-by-default status, or exact environmental prerequisites beyond NFSD, NFSv2 READ, TCP RPC behavior, and affected Linux kernel ranges.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. The CVSS vector says local access with low privileges, while the description discusses a client influencing TCP RPC record sizing. Treat exploitability details as incomplete without vendor advisories.

Researcher notes

Key uncertainty is exposure semantics: CVSS lists local, but the description centers on a crafted TCP RPC record from a client. Avoid assuming remote unauthenticated exploitation without more source evidence. Focus analysis on NFSD NFSv2 READ reply construction and referenced stable commits.

Mitigation direction

  • Apply a Linux kernel update containing the referenced stable fixes.
  • Check distribution vendor advisories for exact fixed kernel packages.
  • Disable unnecessary NFSD or NFSv2 support where operationally possible.
  • Restrict NFS/RPC access to trusted hosts and networks.
  • Prioritize exposed or multi-user NFS servers before isolated systems.

Validation and detection

  • Inventory Linux hosts running the kernel NFS server.
  • Check kernel versions against vendor advisories and referenced stable commits.
  • Confirm whether NFSv2 service is enabled or required.
  • Review firewall exposure for NFS and RPC services.
  • Verify patched kernels are booted after maintenance.
Prepared
Confidence
medium
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-787: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-50410 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2022-50410Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4452435948424e5322c2a2fefbdc2cf3732cc45d, 4452435948424e5322c2a2fefbdc2cf3732cc45d, 4452435948424e5322c2a2fefbdc2cf3732cc45d, 4452435948424e5322c2a2fefbdc2cf3732cc45d, 4452435948424e5322c2a2fefbdc2cf3732cc45dunaffected
LinuxLinux2.6.19, 0, 5.10.220, 5.15.75, 5.19.17, 6.0.3, 6.1affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.