{ "schema_version": "1.6.1", "id": "RPI-CVE-2023-53711", "modified": "2026-10-09T11:39:44Z", "upstream": [ "CVE-2023-53711" ], "published": "2025-10-22T13:24:27Z", "summary": "NFS: Fix a potential data corruption", "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Fix a potential data corruption\n\nWe must ensure that the subrequests are joined back into the head before\nwe can retransmit a request. If the head was not on the commit lists,\nbecause the server wrote it synchronously, we still need to add it back\nto the retransmission list.\nAdd a call that mirrors the effect of nfs_cancel_remove_inode() for\nO_DIRECT.", "severity": [ { "type": "CVSS_V3", "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L" } ], "affected": [ { "package": { "ecosystem": "Raspberry Pi OS:12", "name": "linux" }, "versions": [ "1:6.1.21-1+rpt1", "1:6.1.47-1+rpt2", "1:6.1.47-1+rpt4" ], "ecosystem_specific": { "binaries": [ { "binary_name": "linux-image-6.1.0-rpi1-rpi-v6", "binary_version": "1:6.1.21-1+rpt1" }, { "binary_name": "linux-image-6.1.0-rpi1-rpi-v7", "binary_version": "1:6.1.21-1+rpt1" }, { "binary_name": "linux-image-6.1.0-rpi1-rpi-v7l", "binary_version": "1:6.1.21-1+rpt1" }, { "binary_name": "linux-image-6.1.0-rpi1-rpi-v8", "binary_version": "1:6.1.21-1+rpt1" }, { "binary_name": "linux-image-6.1.0-rpi2-rpi-v6", "binary_version": "1:6.1.47-1+rpt2" }, { "binary_name": "linux-image-6.1.0-rpi2-rpi-v7", "binary_version": "1:6.1.47-1+rpt2" }, { "binary_name": "linux-image-6.1.0-rpi2-rpi-v7l", "binary_version": "1:6.1.47-1+rpt2" }, { "binary_name": "linux-image-6.1.0-rpi2-rpi-v8", "binary_version": "1:6.1.47-1+rpt2" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-2712", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v6", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v7", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v8", "binary_version": "1:6.1.47-1+rpt4" } ] }, "database_specific": { "per_version": { "1:6.1.21-1+rpt1": { "linux_commit": "0afb5e98488aed7017b9bf321b575d0177feb7ed", "upstream_version": "6.1.21", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.1.54" }, "1:6.1.47-1+rpt2": { "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e", "upstream_version": "6.1.47", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.1.54" }, "1:6.1.47-1+rpt4": { "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e", "upstream_version": "6.1.47", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.1.54", "compiled_filter": false } } } } ], "references": [ { "type": "ADVISORY", "url": "https://www.cve.org/CVERecord?id=CVE-2023-53711" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/4185605cd0f72ec8bf8b423aacd94cd5ee13bbcf" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/da302f1d476a44245823a74546debb5d160bf5bd" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/dac14a1dbe20e003215dacb8a3a1a7e4ca4e0ad0" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/0ec26716e45d615edfff46012e7dedcc0ac5f7ab" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/88975a55969e11f26fe3846bf4fbf8e7dc8cbbd4" } ], "database_specific": { "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git", "upstream_modified": "2026-08-05T11:24:39Z", "severity": { "source": "kernel CNA", "cvss_v3_score": 8.2, "cvss_v3_severity": "High", "scenario": "AV:N - The bug lives in the NFS client's O_DIRECT write path and is driven entirely by data from a remote peer \u2014 the server's per-WRITE `committed` level, the negotiated wsize that forces the page-group split, and the COMMIT write verifier that triggers `nfs_direct_write_reschedule()`. A malicious/compromised NFS server or an on-path attacker on unauthenticated AUTH_SYS NFS traffic reaches it over the network with no local access.\nAC:L - All three preconditions are server-controlled and can be produced deterministically and repeatedly: advertise a wsize that forces `__nfs_pageio_add_request()` to split a request into head+subrequest across two RPCs, answer one FILE_SYNC and the other UNSTABLE so only the subrequest lands on the commit list, then return a changed write verifier on COMMIT to force the reschedule.\nPR:N - The attacker is the remote NFS server (or an on-path attacker), which needs no credentials or privileges on the victim client; the vulnerable path runs in the client's normal write-completion/reschedule machinery.\nUI:N - No victim action is required beyond an already-mounted export carrying an ordinary O_DIRECT workload \u2014 the databases, VM images and backup jobs NFS O_DIRECT exists for. The reschedule runs asynchronously from `nfsiod` with no user involvement.\nS:U - The defect and its consequences are confined to the NFS client within the same kernel security authority; no VM, sandbox, or IOMMU boundary is crossed.\nC:N - Tracing the path shows no out-of-bounds read, no kernel-memory disclosure and no read primitive \u2014 subrequests hold krefs on the head and `nfs_page_group_destroy()`'s deferred teardown prevents any use-after-free. The impact is confined to what gets written back.\nI:H - Retransmitting subrequests without rejoining them to the head means an O_DIRECT write is not faithfully re-driven to stable storage after the server discards its unstable cache, so file contents silently diverge from what the application wrote while `write()` still reports success \u2014 unbounded, undetected corruption of stored data on a shared network filesystem.\nA:L - The un-joined group never collapses, so each attacker-forced reschedule round re-splits requests and grafts more members onto a page-group ring that cannot be reclaimed until the whole dreq dies, degrading memory and lengthening the O(N) ring walks while the write fails to converge. I found no reachable panic, BUG_ON, or hang, so this is degradation rather than a full availability loss." } } }