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

netfs: Fix streaming write being overwritten

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 89 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 severityHighOperational priority:Medium, 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.18% 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: As exposure requiresRemediation target: Within 365 days

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 89 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.

17 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 13 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 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 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-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 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
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-64063 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: netfs: Fix streaming write being overwritten
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. This vulnerability occurs when the netfslib performs a 'streaming write' where dirty data is stored directly into folios without prior reading. If a partially written streaming write page is entirely or partially overwritten by a subsequent write operation, the system may not correctly handle the dirty data, leading to data integrity issues. This could allow an attacker to cause data corruption.
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-45636

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 89 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 streaming write being overwritten In order to avoid reading whilst writing, netfslib will allow "streaming writes" in which dirty data is stored directly into folios without reading them first. Such folios are marked dirty but may not be marked uptodate. If a folio is entirely written by a streaming write, uptodate will be set, otherwise it will have a netfs_folio struct attached to ->private recording the dirty region. In the event that a partially written streaming write page is to be overwritten entirely by a single write(), netfs_perform_write() will try to copy over it, but doesn't discard the netfs_folio if it succeeds; further, it doesn't correctly handle a partial copy that overwrites some of the dirty data. Fix this by the following: (1) If the folio is successfully overwritten, free the netfs_folio struct before marking the page uptodate. (2) If the copy to the folio partially fails, but short of the dirty data, just ignore the copy. (3) If the copy partially fails and overwrites some of the dirty data, accept the copy, update the netfs_folio struct to record the new data. If the folio is now filled, free the netfs_folio and set uptodate, otherwise return a partial write. 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 0 0x927c0 write 0x63fb8 0x53c8 0 copy_range 0xb704 0x19b9 0x24429 0x79380 write 0x2402b 0x144a2 0x90660 * write 0x204d5 0x140a0 0x927c0 * copy_range 0x1f72c 0x137d0 0x7a906 0x927c0 * read 0x00000 0x20000 0x9157c read 0x20000 0x20000 0x9157c read 0x40000 0x20000 0x9157c read 0x60000 0x20000 0x9157c read 0x7e1a0 0xcfb9 0x9157c on cifs with the default cache option. It shows folio 0x24 misbehaving 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 streaming write being overwritten In order to avoid reading whilst writing, netfslib will allow "streaming writes" in which dirty data is stored directly into folios without reading them first. Such folios are marked dirty but may not be marked uptodate. If a folio is entirely written by a streaming write, uptodate will be set, otherwise it will have a netfs_folio struct attached to ->private recording the dirty region. In the event that a partially written streaming write page is to be overwritten entirely by a single write(), netfs_perform_write() will try to copy over it, but doesn't discard the netfs_folio if it succeeds; further, it doesn't correctly handle a partial copy that overwrites some of the dirty data. Fix this by the following: (1) If the folio is successfully overwritten, free the netfs_folio struct before marking the page uptodate. (2) If the copy to the folio partially fails, but short of the dirty data, just ignore the copy. (3) If the copy partially fails and overwrites some of the dirty data, accept the copy, update the netfs_folio struct to record the new data. If the folio is now filled, free the netfs_folio and set uptodate, otherwise return a partial write. 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 0 0x927c0 write 0x63fb8 0x53c8 0 copy_range 0xb704 0x19b9 0x24429 0x79380 write 0x2402b 0x144a2 0x90660 * write 0x204d5 0x140a0 0x927c0 * copy_range 0x1f72c 0x137d0 0x7a906 0x927c0 * read 0x00000 0x20000 0x9157c read 0x20000 0x20000 0x9157c read 0x40000 0x20000 0x9157c read 0x60000 0x20000 0x9157c read 0x7e1a0 0xcfb9 0x9157c on cifs with the default cache option. It shows folio 0x24 misbehaving 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

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

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 streaming write being overwritten In order to avoid reading whilst writing, netfslib will allow "streaming writes" in which dirty data is stored directly into folios without reading them first. Such folios are marked dirty but may not be marked uptodate. If a folio is entirely written by a streaming write, uptodate will be set, otherwise it will have a netfs_folio struct attached to ->private recording the dirty region. In the event that a partially written streaming write page is to be overwritten entirely by a single write(), netfs_perform_write() will try to copy over it, but doesn't discard the netfs_folio if it succeeds; further, it doesn't correctly handle a partial copy that overwrites some of the dirty data. Fix this by the following: (1) If the folio is successfully overwritten, free the netfs_folio struct before marking the page uptodate. (2) If the copy to the folio partially fails, but short of the dirty data, just ignore the copy. (3) If the copy partially fails and overwrites some of the dirty data, accept the copy, update the netfs_folio struct to record the new data. If the folio is now filled, free the netfs_folio and set uptodate, otherwise return a partial write. 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 0 0x927c0 write 0x63fb8 0x53c8 0 copy_range 0xb704 0x19b9 0x24429 0x79380 write 0x2402b 0x144a2 0x90660 * write 0x204d5 0x140a0 0x927c0 * copy_range 0x1f72c 0x137d0 0x7a906 0x927c0 * read 0x00000 0x20000 0x9157c read 0x20000 0x20000 0x9157c read 0x40000 0x20000 0x9157c read 0x60000 0x20000 0x9157c read 0x7e1a0 0xcfb9 0x9157c on cifs with the default cache option. It shows folio 0x24 misbehaving 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

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

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 → Out-of-bounds Write → 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: a standard category for the underlying weakness.
CWE-787 ↗

CWE-787: Out-of-bounds Write. The product writes data past the end, or before the beginning, of the intended buffer.

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:H/I:H/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.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.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.
CWE-787
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-64054 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-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=

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

d?id=CVE-2026-64054 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-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=

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

d?id=CVE-2026-64054 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-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=

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

d?id=CVE-2026-64054 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-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=

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

d?id=CVE-2026-64054 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-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=

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

d?id=CVE-2026-64054 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-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=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-031731LinuxのLinux Kernelにおける境界外書き込みに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。netfsでは、ストリーミング書き込みが上書きされる問題が修正されました。書き込み中の読み取りを回避するために、netfslibは「ストリーミング書き込み」を許可しており、これは汚れたデータをまず読み取らずに直接folioに格納します。このようなfolioはdirtyとしてマークされますが、必ずしもuptodateとは限りません。folioが完全にストリーミング書き込みで書き込まれた場合はuptodateが設定されますが、そうでない場合はnetfs_folio構造体が-＞privateに付随し、汚れた領域を記録します。部分的に書き込まれたストリーミング書き込みページ全体を単一のwrite()で上書きしようとすると、netfs_perform_write()はコピーを試みますが、成功してもnetfs_folioを破棄せず、さらに汚れたデータの一部を上書きする部分コピーを正しく処理しません。この問題は以下の方法で修正されました。 (1) folioが正常に上書きされた場合は、ページをuptodateに設定する前にnetfs_folio構造体を解放します。 (2) コピーが部分的に失敗したが汚れたデータには達しなかった場合は、コピーを無視します。 (3) コピーが部分的に失敗して汚れたデータの一部を上書きした場合は、コピーを受け入れ、netfs_folio構造体を新しいデータで更新します。folioが満たされた場合はnetfs_folioを解放しuptodateを設定し、そうでなければ部分的書き込みを返します。以下のコマンドで問題が検出されました。 fsx -q -N 1000000 -p 10000 -o 128000 -l 600000 /xfstest.test/junk --replay-ops=junk.fsxopsjunk.fsxopsの内容は以下の通りです。 truncate 0x0 0 0x927c0 write 0x63fb8 0x53c8 0 copy_range 0xb704 0x19b9 0x24429 0x79380 write 0x2402b 0x144a2 0x90660 * write 0x204d5 0x140a0 0x927c0 * copy_range 0x1f72c 0x137d0 0x7a906 0x927c0 * read 0x00000 0x20000 0x9157c read 0x20000 0x20000 0x9157c read 0x40000 0x20000 0x9157c read 0x60000 0x20000 0x9157c read 0x7e1a0 0xcfb9 0x9157c。cifsのデフォルトキャッシュオプションで実行されました。netfs_perform_write()内でFMODE_READのチェックをコメントアウトするとfolio 0x24が不正動作を示しました。具体的には、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.
Fix availability varies by product
Affected
Fixed
Linux: < 6.12, 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-787 · Out-of-bounds Write

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-45636
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceNIST NVD
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: added patch: git.kernel.org/20195925c768626dc901a4781a51e508702c88ad; added patch: git.kernel.org/7b4dcf1b9455a6e52ac7478b4057dbe10359576d; 2 further additions.
    Before
    remediation: git.kernel.org/20195925c768626dc901a4781a51e508702c88ad
    After
    patch: git.kernel.org/20195925c768626dc901a4781a51e508702c88ad · patch: git.kernel.org/7b4dcf1b9455a6e52ac7478b4057dbe10359576d · patch: git.kernel.org/cdae00e8e215d95911d95f100599e187b6560de5 · 2 more references
    git.kernel.org ↗
  2. SeveritySeverity changed from Unknown to High.
    Before
    Unknown
    After
    High
    NIST NVD ↗
  3. CVSS scoreCVSS score changed from not recorded to 7.8 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).
    Before
    not recorded
    After
    7.8 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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-45636↗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-64063 · cve.blacktree.nl