CVE-2023-53083: nfsd: don't replace page in rq_pages if it's a continuation of last page
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.51% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0101067f376eb7b9afd00279270f25d5111a091d, 12eca509234acb6b666802edf77408bb70d7bfca, 27c934dd8832dd40fd34776f916dc201e18b319b.
- Severity is disputed: the assigning authority (CNA) scores it 9.8, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 0101067f376eb7b9afd00279270f25d5111a091d, 12eca509234acb6b666802edf77408bb70d7bfca, 27c934dd8832dd40fd34776f916dc201e18b319b or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: nfsd: don't replace page in rq_pages if it's a continuation of last page The splice read calls nfsd_splice_actor to put the pages containing file data into the svc_rqst->rq_pages array. It's possible however to get a splice result that only has a partial page at the end, if (e.g.) the filesystem hands back a short read that doesn't cover the whole page. nfsd_splice_actor will plop the partial page into its rq_pages array and return. Then later, when nfsd_splice_actor is called again, the remainder of the page may end up being filled out. At this point, nfsd_splice_actor will put the page into the array _again_ corrupting the reply. If this is done enough times, rq_next_page will overrun the array and corrupt the trailing fields -- the rq_respages and rq_next_page pointers themselves. If we've already added the page to the array in the last pass, don't add it to the array a second time when dealing with a splice continuation. This was originally handled properly in nfsd_splice_actor, but commit 91e23b1c3982 ("NFSD: Clean up nfsd_splice_actor()") removed the check for it.
- Published
- May 2, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.5% · 44th percentile
- CWE
- —
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 9.8
- 4.3 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.19affected
- bf1cbe2f3650b4f4a8add6af933c6d7f6af1f361 and later · before 8235cd619db6e67f1d7d26c55f1f3e4e575c947daffected · git
- 56bc7e3821e847a6cc8027ddaba32e9a440225a5 and later · before 12eca509234acb6b666802edf77408bb70d7bfcaaffected · git
- 91e23b1c39820bfed642119ff6b6ef9f43cf09ce and later · before 51ddb84baff6f09ad62b5999ece3ec172e4e3568affected · git
- 91e23b1c39820bfed642119ff6b6ef9f43cf09ce and later · before 0101067f376eb7b9afd00279270f25d5111a091daffected · git
- 91e23b1c39820bfed642119ff6b6ef9f43cf09ce and later · before 27c934dd8832dd40fd34776f916dc201e18b319baffected · git
- before 5.19not affected · semver
- 6.1.22 and later · up to and including 6.1.*not affected · semver
- 6.2.9 and later · up to and including 6.2.*not affected · semver
- 6.3 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.19 and later · before 6.1.22
- linux linux kernel6.2 and later · before 6.2.9
- linux linux kernel6.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.25-1 | 6.1.25-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-53068May 2, 2025 · net: usb: lan78xx: Limit packet length to skb->len22Monitor
- ← EarlierCVE-2023-53081May 2, 2025 · ocfs2: fix data corruption after failed write31Monitor
- Later →CVE-2023-53092May 2, 2025 · interconnect: exynos: fix node leak in probe PM QoS error path22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0101067f376eb7b9afd00279270f25d5111a091d | Vendor (CNA) |
| Linux Linux | 12eca509234acb6b666802edf77408bb70d7bfca | Vendor (CNA) |
| Linux Linux | 27c934dd8832dd40fd34776f916dc201e18b319b | Vendor (CNA) |
| Linux Linux | 51ddb84baff6f09ad62b5999ece3ec172e4e3568 | Vendor (CNA) |
| Linux Linux | 8235cd619db6e67f1d7d26c55f1f3e4e575c947d | Vendor (CNA) |
| debian:linux | 6.1.25-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.