{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2023-53711","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2025-10-22T13:21:37.346Z","datePublished":"2025-10-22T13:23:46.458Z","dateUpdated":"2026-08-05T09:15:39.362Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-08-05T09:15:39.362Z"},"descriptions":[{"lang":"en","value":"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."}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L","baseScore":8.2,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:N - The bug lives in the NFS client's O_DIRECT write path and is driven entirely by data from a remote peer — 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 — 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 — 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 — 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."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["fs/nfs/direct.c"],"versions":[{"version":"ed5d588fe47feef290f271022820e255d8371561","lessThan":"4185605cd0f72ec8bf8b423aacd94cd5ee13bbcf","status":"affected","versionType":"git"},{"version":"ed5d588fe47feef290f271022820e255d8371561","lessThan":"da302f1d476a44245823a74546debb5d160bf5bd","status":"affected","versionType":"git"},{"version":"ed5d588fe47feef290f271022820e255d8371561","lessThan":"dac14a1dbe20e003215dacb8a3a1a7e4ca4e0ad0","status":"affected","versionType":"git"},{"version":"ed5d588fe47feef290f271022820e255d8371561","lessThan":"0ec26716e45d615edfff46012e7dedcc0ac5f7ab","status":"affected","versionType":"git"},{"version":"ed5d588fe47feef290f271022820e255d8371561","lessThan":"88975a55969e11f26fe3846bf4fbf8e7dc8cbbd4","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["fs/nfs/direct.c"],"versions":[{"version":"5.7","status":"affected"},{"version":"0","lessThan":"5.7","status":"unaffected","versionType":"semver"},{"version":"5.10.195","lessThanOrEqual":"5.10.*","status":"unaffected","versionType":"semver"},{"version":"5.15.132","lessThanOrEqual":"5.15.*","status":"unaffected","versionType":"semver"},{"version":"6.1.54","lessThanOrEqual":"6.1.*","status":"unaffected","versionType":"semver"},{"version":"6.5.4","lessThanOrEqual":"6.5.*","status":"unaffected","versionType":"semver"},{"version":"6.6","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.7","versionEndExcluding":"5.10.195"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.7","versionEndExcluding":"5.15.132"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.7","versionEndExcluding":"6.1.54"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.7","versionEndExcluding":"6.5.4"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.7","versionEndExcluding":"6.6"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/4185605cd0f72ec8bf8b423aacd94cd5ee13bbcf"},{"url":"https://git.kernel.org/stable/c/da302f1d476a44245823a74546debb5d160bf5bd"},{"url":"https://git.kernel.org/stable/c/dac14a1dbe20e003215dacb8a3a1a7e4ca4e0ad0"},{"url":"https://git.kernel.org/stable/c/0ec26716e45d615edfff46012e7dedcc0ac5f7ab"},{"url":"https://git.kernel.org/stable/c/88975a55969e11f26fe3846bf4fbf8e7dc8cbbd4"}],"title":"NFS: Fix a potential data corruption","x_generator":{"engine":"bippy-1.2.0"}}}}