nfsd: sample writeback error cursor before async COPY loop
Summary
| CVE | CVE-2026-89704 |
|---|
| State | PUBLISHED |
|---|
| Assigner | Linux |
|---|
| Source Priority | CVE Program / NVD first with legacy fallback |
|---|
| Published | 2026-09-11 20:19:57 UTC |
|---|
| Updated | 2026-09-11 20:19:57 UTC |
|---|
| Description | In the Linux kernel, the following vulnerability has been resolved:
nfsd: sample writeback error cursor before async COPY loop
_nfsd_copy_file_range() samples dst->f_wb_err into "since"
after the copy loop, then uses it to detect writeback errors
via filemap_check_wb_err() once vfs_fsync_range() returns.
Because the nfsd_file cache reuses a single struct file
across requests targeting the same inode, a concurrent
COMMIT or stable WRITE on dst advances dst->f_wb_err to the
current mapping->wb_err via file_check_and_advance_wb_err()
during its own vfs_fsync_range(). If that advancement lands
between the writeback error appearing in mapping->wb_err
and the COPY worker sampling "since", the worker captures
the already-advanced cursor, errseq_check() sees cur ==
since and returns zero, and NFSD4_COPY_F_COMMITTED is set
even though writeback failed. CB_OFFLOAD then encodes
wr_stable_how = FILE_SYNC4, the client treats the copied
data as durable, and the failure becomes silent data loss.
Sample since once at the start of the function. The cursor
then reflects state in effect before this COPY issues any
writes, and filemap_check_wb_err() detects any error that
occurs during the copy regardless of which thread first
observes it. This matches the pattern used by
nfsd_vfs_write() and nfsd4_clone_file_range(). |
|---|
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 555dbf1a9aac6d3150c8b52fa35f768a692f4eeb 52b2db7a72e19ac2686fa4b2a52406661e7bf9e2 git |
Not specified |
| CNA |
Linux |
Linux |
affected 555dbf1a9aac6d3150c8b52fa35f768a692f4eeb 8277d4a11ae2cb5495842be558fd946032c24363 git |
Not specified |
| CNA |
Linux |
Linux |
affected 555dbf1a9aac6d3150c8b52fa35f768a692f4eeb a1cbafe756cd5e6ab0e099062f37da7a5b081169 git |
Not specified |
| CNA |
Linux |
Linux |
affected 555dbf1a9aac6d3150c8b52fa35f768a692f4eeb 20a67a7d18221af736f124770c2c5e859b479046 git |
Not specified |
| CNA |
Linux |
Linux |
affected f14816f2f928c560d28ba344af689f56efcd6f55 git |
Not specified |
| CNA |
Linux |
Linux |
affected 3145fe0ebb16e1715ad541a301bc6675c8375fcd git |
Not specified |
| CNA |
Linux |
Linux |
affected 5.10.124 5.11 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 5.15.49 5.16 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 5.17 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.17 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.109 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.50 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.4 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/8277d4a11ae2cb5495842be558fd946032c24363 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/52b2db7a72e19ac2686fa4b2a52406661e7bf9e2 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/a1cbafe756cd5e6ab0e099062f37da7a5b081169 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/20a67a7d18221af736f124770c2c5e859b479046 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.