CVE-2026-64062: netfs: Fix potential deadlock in write-through mode
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.09% (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 003aa0dd26c964025acd6d1213bcdbd674db2ca9, 1468f39243ccb155b6d97f9a9932f610d1205d75, b6a4ae1634b3ad2aaa05222e53d36da532852faf.
Low priority for now. Upgrade to Linux Linux 003aa0dd26c964025acd6d1213bcdbd674db2ca9, 1468f39243ccb155b6d97f9a9932f610d1205d75, b6a4ae1634b3ad2aaa05222e53d36da532852faf 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: netfs: Fix potential deadlock in write-through mode Fix netfs_advance_writethrough() to always unlock the supplied folio and to mark it dirty if it isn't yet written to the end. Unfortunately, it can't be marked for writeback until the folio is done with as that may cause a deadlock against mmapped reads and writes. Even though it has been marked dirty, premature writeback can't occur as the caller is holding both inode->i_rwsem (which will prevent concurrent truncation, fallocation, DIO and other writes) and ictx->wb_lock (which will cause flushing to wait and writeback to skip or wait). Note that this may be easier to deal with once the queuing of folios is split from the generation of subrequests.
- Published
- Jul 19, 2026
- Updated
- Sep 2, 2026
- EPSS
- 0.0% · 0th percentile
- CWE
- CWE-667
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.0%
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
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
- 6.10affected
- 288ace2f57c9d06dd2e42bd80d03747d879a4068 and later · before 1468f39243ccb155b6d97f9a9932f610d1205d75affected · git
- 288ace2f57c9d06dd2e42bd80d03747d879a4068 and later · before 003aa0dd26c964025acd6d1213bcdbd674db2ca9affected · git
- 288ace2f57c9d06dd2e42bd80d03747d879a4068 and later · before e40e9cbf3ee4d30ee9a97bd128c85500b6ad0da1affected · git
- 288ace2f57c9d06dd2e42bd80d03747d879a4068 and later · before b6a4ae1634b3ad2aaa05222e53d36da532852fafaffected · git
- before 6.10not affected · semver
- 6.12.92 and later · up to and including 6.12.*not affected · semver
- 6.18.34 and later · up to and including 6.18.*not affected · semver
- 7.0.11 and later · up to and including 7.0.*not affected · semver
- 7.1 and laternot affected · original_commit_for_fix
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.10 and later · before 6.12.92
- linux linux kernel6.13 and later · before 6.18.34
- linux linux kernel6.19 and later · before 7.0.11
- linux linux kernel7.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.94-1 | 6.12.94-1 |
| Debian:14 | linux | before 7.0.12-1 | 7.0.12-1 |
| openSUSE:Leap 16.0 | dtb-aarch64 | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| openSUSE:Leap 16.0 | kernel-64kb | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| openSUSE:Leap 16.0 | kernel-azure | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| openSUSE:Leap 16.0 | kernel-default | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| openSUSE:Leap 16.0 | kernel-default-base | before 6.12.0-160000.40.1.160000.2.29 | 6.12.0-160000.40.1.160000.2.29 |
| openSUSE:Leap 16.0 | kernel-docs | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| openSUSE:Leap 16.0 | kernel-kvmsmall | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| openSUSE:Leap 16.0 | kernel-obs-build | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| openSUSE:Leap 16.0 | kernel-obs-qa | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| openSUSE:Leap 16.0 | kernel-rt | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| openSUSE:Leap 16.0 | kernel-source | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| openSUSE:Leap 16.0 | kernel-syms | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| openSUSE:Leap 16.0 | kernel-zfcpdump | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-azure | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-docs | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-kvmsmall | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-obs-qa | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-zfcpdump | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| SUSE:Linux Micro 6.2 | kernel-64kb | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| SUSE:Linux Micro 6.2 | kernel-default | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| SUSE:Linux Micro 6.2 | kernel-default-base | before 6.12.0-160000.40.1.160000.2.29 | 6.12.0-160000.40.1.160000.2.29 |
| SUSE:Linux Micro 6.2 | kernel-rt | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
+3
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-64059Jul 19, 2026 · netfs: Fix folio->private handling in netfs_perform_write()22Monitor
- ← EarlierCVE-2026-64061Jul 19, 2026 · netfs: Fix early put of sink folio in netfs_read_gaps()39Monitor
- Later →CVE-2026-64063Jul 19, 2026 · netfs: Fix streaming write being overwritten31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 003aa0dd26c964025acd6d1213bcdbd674db2ca9 | Vendor (CNA) |
| Linux Linux | 1468f39243ccb155b6d97f9a9932f610d1205d75 | Vendor (CNA) |
| Linux Linux | b6a4ae1634b3ad2aaa05222e53d36da532852faf | Vendor (CNA) |
| Linux Linux | e40e9cbf3ee4d30ee9a97bd128c85500b6ad0da1 | Vendor (CNA) |
| debian:linux | 6.12.94-1 · Debian:13 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.12.0-160000.40.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.12.0-160000.40.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-azure | 6.12.0-160000.40.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default | 6.12.0-160000.40.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.12.0-160000.40.1.160000.2.29 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-docs | 6.12.0-160000.40.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.12.0-160000.40.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.12.0-160000.40.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-qa | 6.12.0-160000.40.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-rt | 6.12.0-160000.40.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-source | 6.12.0-160000.40.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-syms | 6.12.0-160000.40.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| suse:kernel-64kb | 6.12.0-160000.40.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-azure | 6.12.0-160000.40.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-default | 6.12.0-160000.40.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-default-base | 6.12.0-160000.40.1.160000.2.29 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-docs | 6.12.0-160000.40.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-kvmsmall | 6.12.0-160000.40.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-obs-build | 6.12.0-160000.40.1 · SUSE:Linux Micro Extras 6.2 | Package registry (OSV) |
| suse:kernel-obs-qa | 6.12.0-160000.40.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-rt | 6.12.0-160000.40.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-source | 6.12.0-160000.40.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-syms | 6.12.0-160000.40.1 · SUSE:Linux Micro Extras 6.2 | Package registry (OSV) |
| suse:kernel-zfcpdump | 6.12.0-160000.40.1 · SUSE:Linux Enterprise Server 16.0 | Package 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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)
CWE-667 · Improper LockingCVSS 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.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.