Skip to main content

Linux Kernel EUVDEUVD-2026-45845

| CVE-2026-64160 CRITICAL
2026-07-19 Linux GHSA-83gv-5w7g-5pv2
Critical
Disputed · 9.8 Vendor: Linux
Share

Severity by source

Sources disagree (Medium–Critical)
Vendor (Linux) PRIMARY
9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
3.6 LOW

Local, timing-dependent kernel race needing an unprivileged local process, so AV:L/AC:H/PR:L; torn size reads give at most minor info disclosure and transient misbehavior, so C:L/A:L, I:N.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:L
4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N
SUSE
CRITICAL
qualitative
Red Hat
7.0 MEDIUM
qualitative

vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.

CVSS VectorVendor: Linux

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jul 20, 2026 - 17:46 vuln.today
CVSS changed
Jul 20, 2026 - 15:22 NVD
9.8 (CRITICAL)
Patch available
Jul 19, 2026 - 17:03 EUVD
CVE Published
Jul 19, 2026 - 15:40 cve.org
UNKNOWN (no severity yet)
CVE Published
Jul 19, 2026 - 15:40 cve.org
CRITICAL 9.8

DescriptionCVE.org

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.

AnalysisAI

Data-race tearing in the Linux kernel's netfs library allows the ->remote_i_size and ->zero_point fields to be read or written non-atomically, potentially yielding torn/inconsistent file-size values for network filesystems built on netfslib (e.g., AFS, Ceph, 9p, cifs/SMB). The fix mirrors the existing i_size_read()/i_size_write() pattern, reusing the i_size seqcount under i_lock to serialize updates. Despite an input CVSS of 9.8, this is a local race-condition hardening fix with no public exploit identified at time of analysis and a low EPSS (0.16%, 6th percentile); the tag set even reclassifies impact as Information Disclosure rather than RCE.

Technical ContextAI

netfslib is the shared Linux kernel infrastructure layer that network/cache-backed filesystems use to manage buffered I/O, readahead, and size bookkeeping. Two of its per-inode size trackers, ->remote_i_size (the server-reported size) and ->zero_point (the offset beyond which data is treated as zero), were being updated without the same protection given to the VFS i_size field. Because these are multi-word/ordering-sensitive updates on some architectures, concurrent readers could observe a partially-updated ('torn') value. The remedy copies the i_size_read()/i_size_write() approach - a seqcount (i_size_seqcount) taken under i_lock - so all three size values are updated atomically with respect to readers. The root cause class is a concurrency/data-race defect (CWE-362 family: race condition; the input lists CWE as N/A). CPE data identifies the affected product only generically as cpe:2.3:a:linux:linux, i.e., the Linux kernel itself rather than a specific subsystem package.

RemediationAI

Patch available per vendor advisory: apply the upstream stable fixes at https://git.kernel.org/stable/c/55970f238d495517edc961d55c44c772594d0969 and https://git.kernel.org/stable/c/2c8f4742bb76117d735f92a3932d85239b16c494, or update to a distribution kernel that has backported them (stable series around 7.0.11 and 7.1 per EUVD; released tagged version not independently confirmed here). The primary remediation is a kernel upgrade/reboot - there is no meaningful runtime workaround for an internal locking fix. As a partial risk-reduction measure only, environments not using netfslib-backed network filesystems (AFS, Ceph, 9p, cifs/SMB with fscache) are effectively not exposed, so avoiding or unmounting those filesystems removes the trigger path at the cost of losing that filesystem functionality; this is not a substitute for patching. Given low EPSS and no known exploitation, schedule the update in a normal maintenance window rather than out-of-band.

Vendor StatusVendor

SUSE

Severity: Critical
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

EUVD-2026-45845 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy