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

netfs: Fix netfs_invalidate_folio() to clear dirty bit if all changes gone

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 96 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 19 Jul 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.16% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 96 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

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.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.94-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, 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 Ubuntu Security ↗Source updated 5 Oct 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-64064 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: netfs: Fix netfs_invalidate_folio() to clear dirty bit if all changes gone
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 `netfs` component. When a streaming write operation is performed, a memory page (folio) can remain marked as 'dirty' even after the associated data is removed by a file truncation. If this dirty page is subsequently accessed through a memory-mapped file (`mmap()`), the kernel attempts to read non-existent data, leading to a system crash (denial of service). This vulnerability can be triggered by a local user.
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.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

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-45637

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 actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 96 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: netfs: Fix netfs_invalidate_folio() to clear dirty bit if all changes gone If a streaming write is made, this will leave the relevant modified folio in a not-uptodate, but dirty state with a netfs_folio struct hung off of folio->private indicating the dirty range. Subsequently truncating the file such that the dirty data in the folio is removed, but the first part of the folio theoretically remains will cause the netfs_folio struct to be discarded... but will leave the dirty flag set. If the folio is then read via mmap(), netfs_read_folio() will see that the page is dirty and jump to netfs_read_gaps() to fill in the missing bits. netfs_read_gaps(), however, expects there to be a netfs_folio struct present and can oops because truncate removed it. Fix this by calling folio_cancel_dirty() in netfs_invalidate_folio() in the event that all the dirty data in the folio is erased (as nfs does). Also add some tracepoints to log modifications to a dirty page. This can be reproduced with something like: dd if=/dev/zero of=/xfstest.test/foo bs=1M count=1 umount /xfstest.test mount /xfstest.test xfs_io -c "w 0xbbbf 0xf96c" \ -c "truncate 0xbbbf" \ -c "mmap -r 0xb000 0x11000" \ -c "mr 0xb000 0x11000" \ /xfstest.test/foo with fscaching disabled (otherwise streaming writes are suppressed) and a change to netfs_perform_write() to disallow streaming writes if the fd is open O_RDWR: if (//(file->f_mode & FMODE_READ) || <--- comment this out netfs_is_cache_enabled(ctx)) { It should be reproducible even without this change, but if prevents the above trivial xfs_io command from reproducing it. Note that the initial dd is important: the file must start out sufficiently large that the zero-point logic doesn't just clear the gaps because it knows there's nothing in the file to read yet. Unmounting and mounting is needed to clear the pagecache (there are other ways to do that that may also work). This was initially reproduced with the generic/522 xfstest on some patches that remove the FMODE_READ restriction.

What

In the Linux kernel, the following vulnerability has been resolved: netfs: Fix netfs_invalidate_folio() to clear dirty bit if all changes gone If a streaming write is made, this will leave the relevant modified folio in a not-uptodate, but dirty state with a netfs_folio struct hung off of folio->private indicating the dirty range. Subsequently truncating the file such that the dirty data in the folio is removed, but the first part of the folio theoretically remains will cause the netfs_folio struct to be discarded... but will leave the dirty flag set. If the folio is then read via mmap(), netfs_read_folio() will see that the page is dirty and jump to netfs_read_gaps() to fill in the missing bits. netfs_read_gaps(), however, expects there to be a netfs_folio struct present and can oops because truncate removed it. Fix this by calling folio_cancel_dirty() in netfs_invalidate_folio() in the event that all the dirty data in the folio is erased (as nfs does). Also add some tracepoints to log modifications to a dirty page. This can be reproduced with something like: dd if=/dev/zero of=/xfstest.test/foo bs=1M count=1 umount /xfstest.test mount /xfstest.test xfs_io -c "w 0xbbbf 0xf96c" \ -c "truncate 0xbbbf" \ -c "mmap -r 0xb000 0x11000" \ -c "mr 0xb000 0x11000" \ /xfstest.test/foo with fscaching disabled (otherwise streaming writes are suppressed) and a change to netfs_perform_write() to disallow streaming writes if the fd is open O_RDWR: if (//(file->f_mode & FMODE_READ) || <--- comment this out netfs_is_cache_enabled(ctx)) { It should be reproducible even without this change, but if prevents the above trivial xfs_io command from reproducing it. Note that the initial dd is important: the file must start out sufficiently large that the zero-point logic doesn't just clear the gaps because it knows there's nothing in the file to read yet. Unmounting and mounting is needed to clear the pagecache (there are other ways to do that that may also work). This was initially reproduced with the generic/522 xfstest on some patches that remove the FMODE_READ restriction.

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 netfs_invalidate_folio() to clear dirty bit if all changes gone If a streaming write is made, this will leave the relevant modified folio in a not-uptodate, but dirty state with a netfs_folio struct hung off of folio->private indicating the dirty range. Subsequently truncating the file such that the dirty data in the folio is removed, but the first part of the folio theoretically remains will cause the netfs_folio struct to be discarded... but will leave the dirty flag set. If the folio is then read via mmap(), netfs_read_folio() will see that the page is dirty and jump to netfs_read_gaps() to fill in the missing bits. netfs_read_gaps(), however, expects there to be a netfs_folio struct present and can oops because truncate removed it. Fix this by calling folio_cancel_dirty() in netfs_invalidate_folio() in the event that all the dirty data in the folio is erased (as nfs does). Also add some tracepoints to log modifications to a dirty page. This can be reproduced with something like: dd if=/dev/zero of=/xfstest.test/foo bs=1M count=1 umount /xfstest.test mount /xfstest.test xfs_io -c "w 0xbbbf 0xf96c" \ -c "truncate 0xbbbf" \ -c "mmap -r 0xb000 0x11000" \ -c "mr 0xb000 0x11000" \ /xfstest.test/foo with fscaching disabled (otherwise streaming writes are suppressed) and a change to netfs_perform_write() to disallow streaming writes if the fd is open O_RDWR: if (//(file->f_mode & FMODE_READ) || <--- comment this out netfs_is_cache_enabled(ctx)) { It should be reproducible even without this change, but if prevents the above trivial xfs_io command from reproducing it. Note that the initial dd is important: the file must start out sufficiently large that the zero-point logic doesn't just clear the gaps because it knows there's nothing in the file to read yet. Unmounting and mounting is needed to clear the pagecache (there are other ways to do that that may also work). This was initially reproduced with the generic/522 xfstest on some patches that remove the FMODE_READ restriction.

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-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64055 Référence CVE CVE-2026-64056 https://www.cve.org/CVERecord?id=CVE-2026-64056 Référence CVE CVE-2026-64057 https://www.cve.org/CVERecord?id=CVE-2026-64057 Référence CVE CVE-2026-64058 https://www.cve.org/CVERecord?id=CVE-2026-64058 Référence CVE CVE-2026-64059 https://www.cve.org/CVERecord?id=CVE-2026-64059 Référence CVE CVE-2026-64060 https://www.cve.org/CVERecord?id=CVE-2026-64060 Référence CVE CVE-2026-64061 https://www.cve.org/CVERecord?id=CVE-2026-64061 Référence CVE CVE-2026-64062 https://www.cve.org/CVERecord?id=CVE-2026-64062 Référence CVE CVE-2026-64063 https://www.cve.org/CVERecord?id=CVE-2026-64063 Référence CVE CVE-2026-64064 https://www.cve.org/CVERecord?id=CVE-2026-64064 Référence CVE CVE-2026-64065 https://www.cve.org/CVERecord?id=CVE-2026-64065 Référence CVE CVE-2026-64066 https://www.cve.org/CVERecord?id=CVE-2026-64066 Référence CVE CVE-2026-64067 https://www.cve.org/CVERecord?id=CVE-2026-64067 Référence CVE CVE-2026-64068 https://www.cve.org/CVERecord?id=CVE-2026-64068 Référence CVE CVE-2026-64069 https://www.cve.org/CVERecord?id=CVE-2026-64069 Référence CVE CVE-2026-64070 https://www.cve.org/CVERecord?id=CVE-2026-64070 Référence CVE CVE-2026-64071 https://www.cve.org/CVERecord?id=CVE-2026-64071 Référence CVE CVE-2026-64072 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64055 Référence CVE CVE-2026-64056 https://www.cve.org/CVERecord?id=CVE-2026-64056 Référence CVE CVE-2026-64057 https://www.cve.org/CVERecord?id=CVE-2026-64057 Référence CVE CVE-2026-64058 https://www.cve.org/CVERecord?id=CVE-2026-64058 Référence CVE CVE-2026-64059 https://www.cve.org/CVERecord?id=CVE-2026-64059 Référence CVE CVE-2026-64060 https://www.cve.org/CVERecord?id=CVE-2026-64060 Référence CVE CVE-2026-64061 https://www.cve.org/CVERecord?id=CVE-2026-64061 Référence CVE CVE-2026-64062 https://www.cve.org/CVERecord?id=CVE-2026-64062 Référence CVE CVE-2026-64063 https://www.cve.org/CVERecord?id=CVE-2026-64063 Référence CVE CVE-2026-64064 https://www.cve.org/CVERecord?id=CVE-2026-64064 Référence CVE CVE-2026-64065 https://www.cve.org/CVERecord?id=CVE-2026-64065 Référence CVE CVE-2026-64066 https://www.cve.org/CVERecord?id=CVE-2026-64066 Référence CVE CVE-2026-64067 https://www.cve.org/CVERecord?id=CVE-2026-64067 Référence CVE CVE-2026-64068 https://www.cve.org/CVERecord?id=CVE-2026-64068 Référence CVE CVE-2026-64069 https://www.cve.org/CVERecord?id=CVE-2026-64069 Référence CVE CVE-2026-64070 https://www.cve.org/CVERecord?id=CVE-2026-64070 Référence CVE CVE-2026-64071 https://www.cve.org/CVERecord?id=CVE-2026-64071 Référence CVE CVE-2026-64072 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64033 Référence CVE CVE-2026-64034 https://www.cve.org/CVERecord?id=CVE-2026-64034 Référence CVE CVE-2026-64039 https://www.cve.org/CVERecord?id=CVE-2026-64039 Référence CVE CVE-2026-64046 https://www.cve.org/CVERecord?id=CVE-2026-64046 Référence CVE CVE-2026-64047 https://www.cve.org/CVERecord?id=CVE-2026-64047 Référence CVE CVE-2026-64048 https://www.cve.org/CVERecord?id=CVE-2026-64048 Référence CVE CVE-2026-64051 https://www.cve.org/CVERecord?id=CVE-2026-64051 Référence CVE CVE-2026-64055 https://www.cve.org/CVERecord?id=CVE-2026-64055 Référence CVE CVE-2026-64056 https://www.cve.org/CVERecord?id=CVE-2026-64056 Référence CVE CVE-2026-64064 https://www.cve.org/CVERecord?id=CVE-2026-64064 Référence CVE CVE-2026-64073 https://www.cve.org/CVERecord?id=CVE-2026-64073 Référence CVE CVE-2026-64076 https://www.cve.org/CVERecord?id=CVE-2026-64076 Référence CVE CVE-2026-64077 https://www.cve.org/CVERecord?id=CVE-2026-64077 Référence CVE CVE-2026-64082 https://www.cve.org/CVERecord?id=CVE-2026-64082 Référence CVE CVE-2026-64083 https://www.cve.org/CVERecord?id=CVE-2026-64083 Référence CVE CVE-2026-64084 https://www.cve.org/CVERecord?id=CVE-2026-64084 Référence CVE CVE-2026-64085 https://www.cve.org/CVERecord?id=CVE-2026-64085 Référence CVE CVE-2026-64086 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64055 Référence CVE CVE-2026-64056 https://www.cve.org/CVERecord?id=CVE-2026-64056 Référence CVE CVE-2026-64057 https://www.cve.org/CVERecord?id=CVE-2026-64057 Référence CVE CVE-2026-64058 https://www.cve.org/CVERecord?id=CVE-2026-64058 Référence CVE CVE-2026-64059 https://www.cve.org/CVERecord?id=CVE-2026-64059 Référence CVE CVE-2026-64060 https://www.cve.org/CVERecord?id=CVE-2026-64060 Référence CVE CVE-2026-64061 https://www.cve.org/CVERecord?id=CVE-2026-64061 Référence CVE CVE-2026-64062 https://www.cve.org/CVERecord?id=CVE-2026-64062 Référence CVE CVE-2026-64063 https://www.cve.org/CVERecord?id=CVE-2026-64063 Référence CVE CVE-2026-64064 https://www.cve.org/CVERecord?id=CVE-2026-64064 Référence CVE CVE-2026-64065 https://www.cve.org/CVERecord?id=CVE-2026-64065 Référence CVE CVE-2026-64066 https://www.cve.org/CVERecord?id=CVE-2026-64066 Référence CVE CVE-2026-64067 https://www.cve.org/CVERecord?id=CVE-2026-64067 Référence CVE CVE-2026-64068 https://www.cve.org/CVERecord?id=CVE-2026-64068 Référence CVE CVE-2026-64069 https://www.cve.org/CVERecord?id=CVE-2026-64069 Référence CVE CVE-2026-64070 https://www.cve.org/CVERecord?id=CVE-2026-64070 Référence CVE CVE-2026-64071 https://www.cve.org/CVERecord?id=CVE-2026-64071 Référence CVE CVE-2026-64072 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-64055 Référence CVE CVE-2026-64056 https://www.cve.org/CVERecord?id=CVE-2026-64056 Référence CVE CVE-2026-64057 https://www.cve.org/CVERecord?id=CVE-2026-64057 Référence CVE CVE-2026-64058 https://www.cve.org/CVERecord?id=CVE-2026-64058 Référence CVE CVE-2026-64059 https://www.cve.org/CVERecord?id=CVE-2026-64059 Référence CVE CVE-2026-64060 https://www.cve.org/CVERecord?id=CVE-2026-64060 Référence CVE CVE-2026-64061 https://www.cve.org/CVERecord?id=CVE-2026-64061 Référence CVE CVE-2026-64062 https://www.cve.org/CVERecord?id=CVE-2026-64062 Référence CVE CVE-2026-64063 https://www.cve.org/CVERecord?id=CVE-2026-64063 Référence CVE CVE-2026-64064 https://www.cve.org/CVERecord?id=CVE-2026-64064 Référence CVE CVE-2026-64065 https://www.cve.org/CVERecord?id=CVE-2026-64065 Référence CVE CVE-2026-64066 https://www.cve.org/CVERecord?id=CVE-2026-64066 Référence CVE CVE-2026-64067 https://www.cve.org/CVERecord?id=CVE-2026-64067 Référence CVE CVE-2026-64068 https://www.cve.org/CVERecord?id=CVE-2026-64068 Référence CVE CVE-2026-64069 https://www.cve.org/CVERecord?id=CVE-2026-64069 Référence CVE CVE-2026-64070 https://www.cve.org/CVERecord?id=CVE-2026-64070 Référence CVE CVE-2026-64071 https://www.cve.org/CVERecord?id=CVE-2026-64071 Référence CVE CVE-2026-64072 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-64055 Référence CVE CVE-2026-64056 https://www.cve.org/CVERecord?id=CVE-2026-64056 Référence CVE CVE-2026-64057 https://www.cve.org/CVERecord?id=CVE-2026-64057 Référence CVE CVE-2026-64058 https://www.cve.org/CVERecord?id=CVE-2026-64058 Référence CVE CVE-2026-64059 https://www.cve.org/CVERecord?id=CVE-2026-64059 Référence CVE CVE-2026-64060 https://www.cve.org/CVERecord?id=CVE-2026-64060 Référence CVE CVE-2026-64061 https://www.cve.org/CVERecord?id=CVE-2026-64061 Référence CVE CVE-2026-64062 https://www.cve.org/CVERecord?id=CVE-2026-64062 Référence CVE CVE-2026-64063 https://www.cve.org/CVERecord?id=CVE-2026-64063 Référence CVE CVE-2026-64064 https://www.cve.org/CVERecord?id=CVE-2026-64064 Référence CVE CVE-2026-64065 https://www.cve.org/CVERecord?id=CVE-2026-64065 Référence CVE CVE-2026-64066 https://www.cve.org/CVERecord?id=CVE-2026-64066 Référence CVE CVE-2026-64067 https://www.cve.org/CVERecord?id=CVE-2026-64067 Référence CVE CVE-2026-64068 https://www.cve.org/CVERecord?id=CVE-2026-64068 Référence CVE CVE-2026-64069 https://www.cve.org/CVERecord?id=CVE-2026-64069 Référence CVE CVE-2026-64070 https://www.cve.org/CVERecord?id=CVE-2026-64070 Référence CVE CVE-2026-64071 https://www.cve.org/CVERecord?id=CVE-2026-64071 Référence CVE CVE-2026-64072 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-64055 Référence CVE CVE-2026-64056 https://www.cve.org/CVERecord?id=CVE-2026-64056 Référence CVE CVE-2026-64057 https://www.cve.org/CVERecord?id=CVE-2026-64057 Référence CVE CVE-2026-64058 https://www.cve.org/CVERecord?id=CVE-2026-64058 Référence CVE CVE-2026-64059 https://www.cve.org/CVERecord?id=CVE-2026-64059 Référence CVE CVE-2026-64060 https://www.cve.org/CVERecord?id=CVE-2026-64060 Référence CVE CVE-2026-64061 https://www.cve.org/CVERecord?id=CVE-2026-64061 Référence CVE CVE-2026-64062 https://www.cve.org/CVERecord?id=CVE-2026-64062 Référence CVE CVE-2026-64063 https://www.cve.org/CVERecord?id=CVE-2026-64063 Référence CVE CVE-2026-64064 https://www.cve.org/CVERecord?id=CVE-2026-64064 Référence CVE CVE-2026-64065 https://www.cve.org/CVERecord?id=CVE-2026-64065 Référence CVE CVE-2026-64066 https://www.cve.org/CVERecord?id=CVE-2026-64066 Référence CVE CVE-2026-64067 https://www.cve.org/CVERecord?id=CVE-2026-64067 Référence CVE CVE-2026-64068 https://www.cve.org/CVERecord?id=CVE-2026-64068 Référence CVE CVE-2026-64069 https://www.cve.org/CVERecord?id=CVE-2026-64069 Référence CVE CVE-2026-64070 https://www.cve.org/CVERecord?id=CVE-2026-64070 Référence CVE CVE-2026-64071 https://www.cve.org/CVERecord?id=CVE-2026-64071 Référence CVE CVE-2026-64072 https://www.cve.org/CVERecord?id=

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

Linuxカーネルにおいて、以下の脆弱性が修正されました。netfs: netfs_invalidate_folio() の修正により、変更がすべて消失した場合にダーティビットをクリアするようになりました。対応ストリーミング書き込みが行われると、関連する変更済みのフォリオが「最新でないがダーティ状態」に残り、folio-＞private にnetfs_folio構造体がぶら下がってダーティ範囲を示していました。その後、ファイルをトランケートしてフォリオ内のダーティデータが消失しても、フォリオの最初の部分は理論上残るためnetfs_folio構造体は破棄されますが、ダーティフラグはセットされたままになります。その結果、mmap()を介してフォリオが読み込まれると、netfs_read_folio()はページがダーティであることを検出し、欠落部分を埋めるためにnetfs_read_gaps()にジャンプします。しかしnetfs_read_gaps()はnetfs_folio構造体が存在することを想定しているため、トランケートにより構造体が削除されている場合、カーネルパニック（oops）を引き起こす可能性がありました。この問題は、フォリオ内のすべてのダーティデータが消去された場合にnetfs_invalidate_folio()内でfolio_cancel_dirty()を呼び出す（nfsと同様の方法で）ことによって修正されました。また、ダーティページの変更をログ出力するためのトレースポイントも追加されています。この問題は、以下のような手順で再現できます。 dd if=/dev/zero of=/xfstest.test/foo bs=1M count=1 umount /xfstest.test mount /xfstest.test xfs_io -c "w 0xbbbf 0xf96c" \ -c "truncate 0xbbbf" \ -c "mmap -r 0xb000 0x11000" \ -c "mr 0xb000 0x11000" \ /xfstest.test/foo fscachingが無効の場合（さもなければストリーミング書き込みは抑制されます）、netfs_perform_write()に対してファイルディスクリプタがO_RDWRの場合はストリーミング書き込みを禁止する変更も併せて行われました。 if (//(file-＞f_mode & FMODE_READ) || ＜--- この行をコメントアウト netfs_is_cache_enabled(ctx)) {この変更がなくても再現可能ですが、この変更により、上記の単純なxfs_ioコマンドでの再現が防止されます。なお、最初のddコマンドは重要で、ファイルが十分に大きくなければゼロ点ロジックがギャップをクリアしてしまい、ファイル内にまだ読み込む部分がないと判断してしまいます。ページキャッシュをクリアするためにはアンマウントとマウントが必要です（他にも同様の手段があります）。この問題は当初、generic/522のxfstestで、FMODE_READ制限を削除するパッチを適用した環境で再現されました。

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.
Fix availability varies by product
Affected
Fixed
Linux: < 6.8, 6.12.92 ≤ 6.12.*, 6.18.34 ≤ 6.18.*, 7.0.11 ≤ 7.0.*, 7.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
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:39 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-45637
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: added patch: git.kernel.org/156ac2ec2ee77c44c4eb7439d6d165247ba12247; added patch: git.kernel.org/31ba145faceb378fa01afcb8349e15ea7d95e542; 2 further additions.
    Before
    remediation: git.kernel.org/31ba145faceb378fa01afcb8349e15ea7d95e542
    After
    patch: git.kernel.org/156ac2ec2ee77c44c4eb7439d6d165247ba12247 · patch: git.kernel.org/31ba145faceb378fa01afcb8349e15ea7d95e542 · patch: git.kernel.org/65ae8717abf36202fef02260b64b781d2d44a9bf · 2 more references
    git.kernel.org ↗
  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-45637↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Patch or update reference↗Patch or update 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-64064 · cve.blacktree.nl