Answer in brief
CVE-2022-50410 records a Critical severity (CVSS 9.8) vulnerability in NFSD: Protect against send buffer overflow in NFSv2 READ. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4452435948424e5322c2a2fefbdc2cf3732cc45d <2007867c5874134f2271eb276398208070049dd3 || >=4452435948424e5322c2a2fefbdc2cf3732cc45d <2be9331ca6061bc6ea32247266f45b8b21030244 || >=4452435948424e5322c2a2fefbdc2cf3732cc45d <ea4c3eee0fd72fcedaa238556044825639cd3607 || >=4452435948424e5322c2a2fefbdc2cf3732cc45d <1868332032eccbab8c1878a0d918193058c0a905 || >=4452435948424e5322c2a2fefbdc2cf3732cc45d <401bc1f90874280a80b93f23be33a0e7e2d1f912 | 2007867c5874134f2271eb276398208070049dd3, 2be9331ca6061bc6ea32247266f45b8b21030244, ea4c3eee0fd72fcedaa238556044825639cd3607, 1868332032eccbab8c1878a0d918193058c0a905, 401bc1f90874280a80b93f23be33a0e7e2d1f912 |
| Linux/Linuxgeneric | 2.6.19 | Not reported |
Published upstream
Sep 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2022-50410 records a Critical severity (CVSS 9.8) vulnerability in NFSD: Protect against send buffer overflow in NFSv2 READ. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4452435948424e5322c2a2fefbdc2cf3732cc45d <2007867c5874134f2271eb276398208070049dd3 || >=4452435948424e5322c2a2fefbdc2cf3732cc45d <2be9331ca6061bc6ea32247266f45b8b21030244 || >=4452435948424e5322c2a2fefbdc2cf3732cc45d <ea4c3eee0fd72fcedaa238556044825639cd3607 || >=4452435948424e5322c2a2fefbdc2cf3732cc45d <1868332032eccbab8c1878a0d918193058c0a905 || >=4452435948424e5322c2a2fefbdc2cf3732cc45d <401bc1f90874280a80b93f23be33a0e7e2d1f912 | 2007867c5874134f2271eb276398208070049dd3, 2be9331ca6061bc6ea32247266f45b8b21030244, ea4c3eee0fd72fcedaa238556044825639cd3607, 1868332032eccbab8c1878a0d918193058c0a905, 401bc1f90874280a80b93f23be33a0e7e2d1f912 |
| Linux/Linuxgeneric | 2.6.19 | Not reported |
Published upstream
Sep 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.