dbcve.org
Linux KernelOperating system · Linux

CVE-2026-64157

MEDIUM · 5.5 CVSS v3.1 Published 2026-07-19
Fix available
A fix is available. Upgrade to 6.11 / 6.12.92 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click 4 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: netfs: Fix partial invalidation of streaming-write folio In netfs_invalidate_folio(), if the region of a partial invalidation overlaps the front (but not all) of a dirty write cached in a streaming write page (dirty, but not uptodate, with the dirty region tracked by a netfs_folio struct), the function modifies the dirty region - but incorrectly as it moves the region forward by setting the start to the start, not the end, of the invalidation region. Fix this by setting finfo->dirty_offset to the end of the invalidation region (iend).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 6.10.8, < 6.11>= 6.11.1, < 6.12.92>= 6.13, < 6.18.34>= 6.19, < 7.0.11= 6.11= 7.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.11 / 6.12.92 / 6.18.34 or later
Fixed in 6.116.12.926.18.34
Recommended fix High confidence

Upgrade to 6.11 (for 6.10.x), 6.12.92 (for 6.11.x), 6.18.34 (for 6.13-6.17.x), or 7.0.11 (for 6.19-7.0.x) depending on which branch you are on

  1. 1. Identify the currently running kernel version using `uname -r`
  2. 2. Determine which version range your current kernel falls into from the affected versions
  3. 3. Upgrade the Linux kernel to a version that includes the fix: for 6.10.x upgrade to 6.11 or later, for 6.11.x upgrade to 6.12.92 or later, for 6.13.x-6.17.x upgrade to 6.18.34 or later, for 6.19.x-7.0.x upgrade to 7.0.11 or later
  4. 4. Reboot the system to load the fixed kernel
  5. 5. Verify the fix is applied by checking the kernel version with `uname -r` and confirming the version is at or above the appropriate fixed release
Caveat Kernel upgrades may require rebuilding external kernel modules; ensure compatibility of proprietary drivers (e.g., NVIDIA, VirtualBox) with the new kernel version

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-64157 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-64157 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data