dbcve.org
VulnerabilityAwaiting classification

CVE-2025-68811

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A memory corruption vulnerability in the Linux kernel's svcrdma (SVG RPC over RDMA) module where svc_rdma_copy_inline_range incorrectly uses rc_curpage (page index) instead of rc_pageoff (byte offset) when calculating memory copies, causing data to be written to incorrect memory locations potentially outside the intended page boundary.

MitigationApply the upstream Linux kernel patch that replaces rc_curpage with rc_pageoff in svc_rdma_copy_inline_range; this requires a kernel update and system reboot to remediate.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify kernel version
    Run 'uname -r' to get the running kernel version, then check against the version that includes the fix for this CVE (consult your Linux distribution's security advisory)
    Affected if The kernel version is older than the fixed version and contains the vulnerable svcrdma code path
  2. Verify RDMA kernel modules are loaded
    Run 'lsmod | grep -E "rdma|svcrdma|ib_" ' to list loaded RDMA-related kernel modules
    Affected if Any RDMA modules (svcrdma, ib_core, rdma_ucm, etc.) are loaded, indicating RDMA support is enabled
  3. Check for active RDMA transport services
    Run 'ss -x | grep svc_rdma' or 'ps aux | grep -E "rpc"|svcrdma"' to look for RPC over RDMA server processes
    Affected if svcrdma or rpcbind processes handling RDMA transports are running, indicating the vulnerable code path is active
  4. Inspect RDMA device configuration
    Run 'rdma link' or check '/sys/class/infiniband/' to enumerate RDMA devices
    Affected if RDMA hardware or software RDMA devices exist and are configured, making the system a potential target
  5. Check for RDMA-enabled NFS exports
    Examine /etc/exports and running 'showmount -e localhost' for NFS exports configured with 'rdma=' option or mount.nfs entries using RDMA
    Affected if NFS or other file systems are exported or mounted over RDMA, which actively uses the svcrdma code

The system is affected if it runs a vulnerable kernel version AND has RDMA/svcrdma functionality enabled with active RDMA services or configured RDMA exports.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the upstream Linux kernel patch that replaces rc_curpage with rc_pageoff in svc_rdma_copy_inline_range; this requires a kernel update and system reboot to remediate.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-68811 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-68811 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data