# CVE-2026-64160: netfs: Fix potential for tearing in ->remote_i_size and ->zero_point

> A race condition in the Linux kernel netfs subsystem allows potential data tearing in file size tracking, leading to data corruption or incorrect reads.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jul 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-92733, BELL-CVE-2026-64160, DEBIAN-CVE-2026-64160, GHSA-83gv-5w7g-5pv2, ROOT-OS-DEBIAN-12-CVE-2026-64160, ROOT-OS-DEBIAN-13-CVE-2026-64160, UBUNTU-CVE-2026-64160

## What is CVE-2026-64160?

CVE-2026-64160 is a critical vulnerability in Linux kernel, published on 19 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

netfs: Fix potential for tearing in ->remote_i_size and ->zero_point

Fix potential tearing in using ->remote_i_size and ->zero_point by copying
i_size_read() and i_size_write() and using the same seqcount as for i_size.

We need to make sure that netfslib and the filesystems that use it always
hold i_lock whilst updating any of the sizes to prevent i_size_seqcount
from getting corrupted.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2026-64160?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-64160?

Apply the vendor's patch.

## Is CVE-2026-64160 being exploited?

There is no known exploitation of CVE-2026-64160 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-64160 and fix it if it is affected.

What it is: CVE-2026-64160 is a critical vulnerability in Linux kernel, published on 19 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-64160 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-64160/ (Markdown: https://insights.sbomify.com/CVE-2026-64160/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-64160
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-64160
- OSV: https://osv.dev/vulnerability/CVE-2026-64160

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-64160/
Summaries are generated and may contain mistakes; the official description above is the record.