Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-53393: nfsd: reset write verifier on deferred writeback errors

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 1dd664b39774a9c89b72de8e59bf9ef4b3aaff2e, 2090b05803faab8a9fa62fbff871007862cac1b7, 4367afc119c51e17a616f6908772b7e2c2c4013f; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 1dd664b39774a9c89b72de8e59bf9ef4b3aaff2e, 2090b05803faab8a9fa62fbff871007862cac1b7, 4367afc119c51e17a616f6908772b7e2c2c4013f; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: nfsd: reset write verifier on deferred writeback errors nfsd_vfs_write() and nfsd_commit() both call filemap_check_wb_err() to detect deferred writeback errors, but neither rotates the server's write verifier (nn->writeverf) when this check fails. Every other durable-storage-failure path in these functions calls commit_reset_write_verifier() before returning an error. The missing rotation means clients holding UNSTABLE write data under the current verifier will COMMIT, receive the unchanged verifier back, and conclude their data is durable — silently dropping data that failed writeback. This violates the UNSTABLE+COMMIT durability contract (RFC 1813 §3.3.7, RFC 8881 §18.32). Add commit_reset_write_verifier() calls at both filemap_check_wb_err() error sites, matching the pattern used by adjacent error paths in the same functions. The helper already filters -EAGAIN and -ESTALE internally, so the calls are unconditionally safe.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jul 19, 2026
Updated
Aug 17, 2026
EPSS
0.1% · 2th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-53393

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.10.124 and later · before 5.10.261
  • linux linux kernel5.15.49 and later · before 5.15.212
  • linux linux kernel5.17 and later · before 6.1.178
  • linux linux kernel6.2 and later · before 6.6.145
  • linux linux kernel6.7 and later · before 6.12.95
  • linux linux kernel6.13 and later · before 6.18.38
  • linux linux kernel6.19 and later · before 7.1.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.17affected
    • f14816f2f928c560d28ba344af689f56efcd6f55 and later · before b8e5894e56cff70fa245628fe16f0ad6367f8090affected · git
    • 3145fe0ebb16e1715ad541a301bc6675c8375fcd and later · before bc2baca02ec56da7707a74ed5d340b0a1dff1841affected · git
    • 555dbf1a9aac6d3150c8b52fa35f768a692f4eeb and later · before 43b65d2997963e80e8d8d86520bcb1e0751227deaffected · git
    • 555dbf1a9aac6d3150c8b52fa35f768a692f4eeb and later · before 666e837b247fcadf2d8d508b9b0e49d720393eb4affected · git
    • 555dbf1a9aac6d3150c8b52fa35f768a692f4eeb and later · before 1dd664b39774a9c89b72de8e59bf9ef4b3aaff2eaffected · git
    • 555dbf1a9aac6d3150c8b52fa35f768a692f4eeb and later · before 4367afc119c51e17a616f6908772b7e2c2c4013faffected · git
    • 555dbf1a9aac6d3150c8b52fa35f768a692f4eeb and later · before b027cca33c97354149fcc0ddeede4525c41093cdaffected · git
    • 555dbf1a9aac6d3150c8b52fa35f768a692f4eeb and later · before 2090b05803faab8a9fa62fbff871007862cac1b7affected · git
    • 5.10.124 and later · before 5.10.261affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:13linuxbefore 6.12.95-16.12.95-1
Debian:14linuxbefore 7.1.3-17.1.3-1
openSUSE:Tumbleweedkernel-sourcebefore 7.1.4-1.17.1.4-1.1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-53389Jul 19, 2026 · net/tcp-ao: fix use-after-free of key in del_async path
    31Monitor
  • ← EarlierCVE-2026-53390Jul 19, 2026 · ksmbd: fix out-of-bounds read in smb_check_perm_dacl()
    32Monitor
  • Later →CVE-2026-53395Jul 19, 2026 · nfsd: fix dead ACL conflict guard in nfsd4_create
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1dd664b39774a9c89b72de8e59bf9ef4b3aaff2eVendor (CNA)
Linux Linux2090b05803faab8a9fa62fbff871007862cac1b7Vendor (CNA)
Linux Linux4367afc119c51e17a616f6908772b7e2c2c4013fVendor (CNA)
Linux Linux43b65d2997963e80e8d8d86520bcb1e0751227deVendor (CNA)
Linux Linux5.10.261Vendor (CNA)
Linux Linux5.15.212Vendor (CNA)
Linux Linux666e837b247fcadf2d8d508b9b0e49d720393eb4Vendor (CNA)
Linux Linuxb027cca33c97354149fcc0ddeede4525c41093cdVendor (CNA)
Linux Linuxb8e5894e56cff70fa245628fe16f0ad6367f8090Vendor (CNA)
Linux Linuxbc2baca02ec56da7707a74ed5d340b0a1dff1841Vendor (CNA)
azl3 kernel 6.6.144.1-1 on Azure Linux 3.06.6.145.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)
opensuse:kernel-source7.1.4-1.1 · openSUSE:TumbleweedPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records