BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-64159High confidence

netfs: Fix zeropoint update where i_size > remote_i_size

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

13 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
Ubuntu 24.04 LTSnoble · standard archivelinux-aws-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fde-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidia-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcp-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatency-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracle-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-64159 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: netfs: Fix zeropoint update where i_size > remote_i_size
76 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the Linux kernel's network file system (netfs) component. This vulnerability occurs when the local file size is larger than the size reported by the remote server, leading to an incorrect update of the 'zero point' (a file position used to optimize reads). An attacker could potentially exploit this to cause unexpected read errors, where the system expects zero-filled data but encounters an End-Of-File (EOF) prematurely.
Remediation
Fix deferred
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-45844

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: netfs: Fix zeropoint update where i_size > remote_i_size Fix the update of the zero point[*] by netfs_release_folio() when there is uncommitted data in the pagecache beyond the folio being released but the on-server EOF is in this folio (ie. i_size > remote_i_size). The update needs to limit zero_point to remote_i_size, not i_size as i_size is a local phenomenon reflecting updates made locally to the pagecache, not stuff written to the server. remote_i_size tracks the server's i_size. [*] The zero point is the file position from which we can assume that the server will just return zeros, so we can avoid generating reads. Note that netfs_invalidate_folio() probably doesn't need fixing as zero_point should be updated by setattr after truncation or fallocate. Found with: fsx -q -N 1000000 -p 10000 -o 128000 -l 600000 \ /xfstest.test/junk --replay-ops=junk.fsxops using the following as junk.fsxops: truncate 0x0 0x1bbae 0x82864 write 0x3ef2e 0xf9c8 0x1bbae write 0x67e05 0xcb5a 0x4e8f6 mapread 0x57781 0x85b6 0x7495f copy_range 0x5d3d 0x10329 0x54fac 0x7495f write 0x64710 0x1c2b 0x7495f mapread 0x64000 0x1000 0x7495f on cifs with the default cache option. It shows read-gaps on folio 0x64 failing with a short read (ie. it hits EOF) if the FMODE_READ check is commented out in netfs_perform_write(): if (//(file->f_mode & FMODE_READ) || netfs_is_cache_enabled(ctx)) { and no fscache. This was initially found with the generic/522 xfstest.

What

In the Linux kernel, the following vulnerability has been resolved: netfs: Fix zeropoint update where i_size > remote_i_size Fix the update of the zero point[*] by netfs_release_folio() when there is uncommitted data in the pagecache beyond the folio being released but the on-server EOF is in this folio (ie. i_size > remote_i_size). The update needs to limit zero_point to remote_i_size, not i_size as i_size is a local phenomenon reflecting updates made locally to the pagecache, not stuff written to the server. remote_i_size tracks the server's i_size. [*] The zero point is the file position from which we can assume that the server will just return zeros, so we can avoid generating reads. Note that netfs_invalidate_folio() probably doesn't need fixing as zero_point should be updated by setattr after truncation or fallocate. Found with: fsx -q -N 1000000 -p 10000 -o 128000 -l 600000 \ /xfstest.test/junk --replay-ops=junk.fsxops using the following as junk.fsxops: truncate 0x0 0x1bbae 0x82864 write 0x3ef2e 0xf9c8 0x1bbae write 0x67e05 0xcb5a 0x4e8f6 mapread 0x57781 0x85b6 0x7495f copy_range 0x5d3d 0x10329 0x54fac 0x7495f write 0x64710 0x1c2b 0x7495f mapread 0x64000 0x1000 0x7495f on cifs with the default cache option. It shows read-gaps on folio 0x64 failing with a short read (ie. it hits EOF) if the FMODE_READ check is commented out in netfs_perform_write(): if (//(file->f_mode & FMODE_READ) || netfs_is_cache_enabled(ctx)) { and no fscache. This was initially found with the generic/522 xfstest.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: netfs: Fix zeropoint update where i_size > remote_i_size Fix the update of the zero point[*] by netfs_release_folio() when there is uncommitted data in the pagecache beyond the folio being released but the on-server EOF is in this folio (ie. i_size > remote_i_size). The update needs to limit zero_point to remote_i_size, not i_size as i_size is a local phenomenon reflecting updates made locally to the pagecache, not stuff written to the server. remote_i_size tracks the server's i_size. [*] The zero point is the file position from which we can assume that the server will just return zeros, so we can avoid generating reads. Note that netfs_invalidate_folio() probably doesn't need fixing as zero_point should be updated by setattr after truncation or fallocate. Found with: fsx -q -N 1000000 -p 10000 -o 128000 -l 600000 \ /xfstest.test/junk --replay-ops=junk.fsxops using the following as junk.fsxops: truncate 0x0 0x1bbae 0x82864 write 0x3ef2e 0xf9c8 0x1bbae write 0x67e05 0xcb5a 0x4e8f6 mapread 0x57781 0x85b6 0x7495f copy_range 0x5d3d 0x10329 0x54fac 0x7495f write 0x64710 0x1c2b 0x7495f mapread 0x64000 0x1000 0x7495f on cifs with the default cache option. It shows read-gaps on folio 0x64 failing with a short read (ie. it hits EOF) if the FMODE_READ check is commented out in netfs_perform_write(): if (//(file->f_mode & FMODE_READ) || netfs_is_cache_enabled(ctx)) { and no fscache. This was initially found with the generic/522 xfstest.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-2403Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260722Security Bulletin 22 Jul 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 Jul 2026, published on 22 July 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1162Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64149 Référence CVE CVE-2026-64150 https://www.cve.org/CVERecord?id=CVE-2026-64150 Référence CVE CVE-2026-64151 https://www.cve.org/CVERecord?id=CVE-2026-64151 Référence CVE CVE-2026-64152 https://www.cve.org/CVERecord?id=CVE-2026-64152 Référence CVE CVE-2026-64153 https://www.cve.org/CVERecord?id=CVE-2026-64153 Référence CVE CVE-2026-64154 https://www.cve.org/CVERecord?id=CVE-2026-64154 Référence CVE CVE-2026-64155 https://www.cve.org/CVERecord?id=CVE-2026-64155 Référence CVE CVE-2026-64156 https://www.cve.org/CVERecord?id=CVE-2026-64156 Référence CVE CVE-2026-64157 https://www.cve.org/CVERecord?id=CVE-2026-64157 Référence CVE CVE-2026-64159 https://www.cve.org/CVERecord?id=CVE-2026-64159 Référence CVE CVE-2026-64160 https://www.cve.org/CVERecord?id=CVE-2026-64160 Référence CVE CVE-2026-64161 https://www.cve.org/CVERecord?id=CVE-2026-64161 Référence CVE CVE-2026-64162 https://www.cve.org/CVERecord?id=CVE-2026-64162 Référence CVE CVE-2026-64163 https://www.cve.org/CVERecord?id=CVE-2026-64163 Référence CVE CVE-2026-64164 https://www.cve.org/CVERecord?id=CVE-2026-64164 Référence CVE CVE-2026-64165 https://www.cve.org/CVERecord?id=CVE-2026-64165 Référence CVE CVE-2026-64166 https://www.cve.org/CVERecord?id=CVE-2026-64166 Référence CVE CVE-2026-64167 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1066Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64150 Référence CVE CVE-2026-64151 https://www.cve.org/CVERecord?id=CVE-2026-64151 Référence CVE CVE-2026-64152 https://www.cve.org/CVERecord?id=CVE-2026-64152 Référence CVE CVE-2026-64153 https://www.cve.org/CVERecord?id=CVE-2026-64153 Référence CVE CVE-2026-64154 https://www.cve.org/CVERecord?id=CVE-2026-64154 Référence CVE CVE-2026-64155 https://www.cve.org/CVERecord?id=CVE-2026-64155 Référence CVE CVE-2026-64156 https://www.cve.org/CVERecord?id=CVE-2026-64156 Référence CVE CVE-2026-64157 https://www.cve.org/CVERecord?id=CVE-2026-64157 Référence CVE CVE-2026-64158 https://www.cve.org/CVERecord?id=CVE-2026-64158 Référence CVE CVE-2026-64159 https://www.cve.org/CVERecord?id=CVE-2026-64159 Référence CVE CVE-2026-64160 https://www.cve.org/CVERecord?id=CVE-2026-64160 Référence CVE CVE-2026-64161 https://www.cve.org/CVERecord?id=CVE-2026-64161 Référence CVE CVE-2026-64162 https://www.cve.org/CVERecord?id=CVE-2026-64162 Référence CVE CVE-2026-64163 https://www.cve.org/CVERecord?id=CVE-2026-64163 Référence CVE CVE-2026-64164 https://www.cve.org/CVERecord?id=CVE-2026-64164 Référence CVE CVE-2026-64165 https://www.cve.org/CVERecord?id=CVE-2026-64165 Référence CVE CVE-2026-64166 https://www.cve.org/CVERecord?id=CVE-2026-64166 Référence CVE CVE-2026-64167 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0954Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64150 Référence CVE CVE-2026-64151 https://www.cve.org/CVERecord?id=CVE-2026-64151 Référence CVE CVE-2026-64152 https://www.cve.org/CVERecord?id=CVE-2026-64152 Référence CVE CVE-2026-64153 https://www.cve.org/CVERecord?id=CVE-2026-64153 Référence CVE CVE-2026-64154 https://www.cve.org/CVERecord?id=CVE-2026-64154 Référence CVE CVE-2026-64155 https://www.cve.org/CVERecord?id=CVE-2026-64155 Référence CVE CVE-2026-64156 https://www.cve.org/CVERecord?id=CVE-2026-64156 Référence CVE CVE-2026-64157 https://www.cve.org/CVERecord?id=CVE-2026-64157 Référence CVE CVE-2026-64158 https://www.cve.org/CVERecord?id=CVE-2026-64158 Référence CVE CVE-2026-64159 https://www.cve.org/CVERecord?id=CVE-2026-64159 Référence CVE CVE-2026-64160 https://www.cve.org/CVERecord?id=CVE-2026-64160 Référence CVE CVE-2026-64161 https://www.cve.org/CVERecord?id=CVE-2026-64161 Référence CVE CVE-2026-64162 https://www.cve.org/CVERecord?id=CVE-2026-64162 Référence CVE CVE-2026-64163 https://www.cve.org/CVERecord?id=CVE-2026-64163 Référence CVE CVE-2026-64164 https://www.cve.org/CVERecord?id=CVE-2026-64164 Référence CVE CVE-2026-64165 https://www.cve.org/CVERecord?id=CVE-2026-64165 Référence CVE CVE-2026-64166 https://www.cve.org/CVERecord?id=CVE-2026-64166 Référence CVE CVE-2026-64167 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0926Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64150 Référence CVE CVE-2026-64151 https://www.cve.org/CVERecord?id=CVE-2026-64151 Référence CVE CVE-2026-64152 https://www.cve.org/CVERecord?id=CVE-2026-64152 Référence CVE CVE-2026-64153 https://www.cve.org/CVERecord?id=CVE-2026-64153 Référence CVE CVE-2026-64154 https://www.cve.org/CVERecord?id=CVE-2026-64154 Référence CVE CVE-2026-64155 https://www.cve.org/CVERecord?id=CVE-2026-64155 Référence CVE CVE-2026-64156 https://www.cve.org/CVERecord?id=CVE-2026-64156 Référence CVE CVE-2026-64157 https://www.cve.org/CVERecord?id=CVE-2026-64157 Référence CVE CVE-2026-64158 https://www.cve.org/CVERecord?id=CVE-2026-64158 Référence CVE CVE-2026-64159 https://www.cve.org/CVERecord?id=CVE-2026-64159 Référence CVE CVE-2026-64160 https://www.cve.org/CVERecord?id=CVE-2026-64160 Référence CVE CVE-2026-64161 https://www.cve.org/CVERecord?id=CVE-2026-64161 Référence CVE CVE-2026-64162 https://www.cve.org/CVERecord?id=CVE-2026-64162 Référence CVE CVE-2026-64163 https://www.cve.org/CVERecord?id=CVE-2026-64163 Référence CVE CVE-2026-64164 https://www.cve.org/CVERecord?id=CVE-2026-64164 Référence CVE CVE-2026-64165 https://www.cve.org/CVERecord?id=CVE-2026-64165 Référence CVE CVE-2026-64166 https://www.cve.org/CVERecord?id=CVE-2026-64166 Référence CVE CVE-2026-64167 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-028672LinuxのLinux Kernelにおける不特定の脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。netfs：i_size ＞ remote_i_sizeの場合のゼロポイント更新に関する修正です。netfs_release_folio()によるゼロポイントの更新において、解放されるフォリオ以降のページキャッシュにコミットされていないデータが存在し、かつオンザサーバーのEOFがこのフォリオ内にある場合（すなわち i_size ＞ remote_i_size）、ゼロポイントの更新を修正しました。更新はローカルな現象であり、ページキャッシュ内のローカルの更新を反映するi_sizeではなく、サーバーに書き込まれた内容を追跡するremote_i_sizeに制限する必要があります。remote_i_sizeはサーバーのi_sizeを追跡します。ゼロポイントとは、サーバーが単にゼロを返すと想定できるファイル位置であり、これにより読み込みを回避できます。なお、netfs_invalidate_folio()はトランケートやfallocate後のsetattrによってゼロポイントが更新されるため、修正は不要と思われます。以下の方法で発見されました。fsx -q -N 1000000 -p 10000 -o 128000 -l 600000 /xfstest.test/junk --replay-ops=junk.fsxops以下のjunk.fsxopsを使用しました。truncate 0x0 0x1bbae 0x82864、write 0x3ef2e 0xf9c8 0x1bbae、write 0x67e05 0xcb5a 0x4e8f6、mapread 0x57781 0x85b6 0x7495f、copy_range 0x5d3d 0x10329 0x54fac 0x7495f、write 0x64710 0x1c2b 0x7495f、mapread 0x64000 0x1000 0x7495fc。cifsをデフォルトのキャッシュオプションで使用しました。これにより、フォリオ0x64で読み込みギャップが短い読み込みによって失敗（EOFに到達）することが示されました。これはnetfs_perform_write()内のFMODE_READチェックがコメントアウトされている場合に発生します。具体的には、if (//(file-＞f_mode & FMODE_READ) || netfs_is_cache_enabled(ctx)) {である状態です。fscacheを使用しない場合の問題です。この問題は最初にgeneric/522のxfstestで発見されました。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
Linux: < 6.11, 7.0.11 ≤ 7.0.*, 7.1 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 19 Jul 2026 · Last source change 19 Jul 2026, 15:40 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-45844
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceUnavailable
NVD statusNVD enriched

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed from authoritative remediation link to authoritative remediation link · patch.
    Before
    authoritative remediation link
    After
    authoritative remediation link · patch
    416baaa9-dc9f-4396-8d5f-8c081fb06d67 ↗
  2. SeveritySeverity changed from Unknown to Medium.
    Before
    Unknown
    After
    Medium
    NIST NVD ↗
  3. CVSS scoreCVSS score changed from not recorded to 5.5 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).
    Before
    not recorded
    After
    5.5 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
    NIST NVD ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-45844↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-64159 · cve.blacktree.nl