CVE-2025-68811: svcrdma: use rc_pageoff for memcpy byte offset
In the Linux kernel, the following vulnerability has been resolved:
svcrdma: use rc_pageoff for memcpy byte offset
svc_rdma_copy_inline_range added rc_curpage (page index) to the page
base instead of the byte offset rc_pageoff. Use rc_pageoff so copies
land within the current page.
Found by ZeroPath (https://zeropath.com)
Security readout for executives and security teams
Plain-English summary
CVE-2025-68811 is a Linux kernel svcrdma bug where data could be copied to the wrong location within a page. Public sources show it has been resolved in stable kernel commits, but they do not provide CVSS, CWE, or confirmed impact. Treat exposure as kernel- and feature-dependent.
Executive priority
Prioritize assessment on Linux servers using RDMA-related kernel services. Without public severity or exploitation evidence, this is not clearly an emergency, but kernel memory handling bugs should be remediated during normal high-priority patch cycles.
Technical view
In svc_rdma_copy_inline_range, the code used rc_curpage, a page index, as the memcpy byte offset instead of rc_pageoff. The fix changes the copy offset so inline data lands within the current page. The CVE record lists Linux kernel versions and stable commits but gives no exploitability detail.
Likely exposure
Likely limited to Linux systems running affected kernel versions where the svcrdma server-side RDMA code path is present and reachable. Distribution backport status must be checked with the OS vendor.
Exploitation context
No active exploitation is cited, and the CVE is not marked KEV. Public sources do not describe attacker prerequisites, remote reachability, or practical impact beyond the kernel memory copy offset defect.
Researcher notes
Evidence is incomplete: no CVSS, CWE, exploit status, or impact class is published in the supplied sources. The bug was found by ZeroPath and fixed through Linux stable commits addressing rc_pageoff versus rc_curpage usage.
Mitigation direction
Apply Linux kernel updates that include the referenced stable fixes.
Check your Linux distribution advisory for backported fixes and affected package versions.
If svcrdma is unnecessary, follow vendor guidance on reducing exposure.
Validation and detection
Inventory Linux kernel versions across exposed servers.
Compare running kernels against vendor advisories for CVE-2025-68811.
Verify updated kernels include the referenced stable fix commits.
Confirm whether svcrdma-related functionality is enabled or required.
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.
cve · low confidence lookup
CVE-2025-68811 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.