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

usb: gadget: f_fs: Initialize epfile->in early to fix endpoint direction checks

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 13 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 17 Aug 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 13 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.

18 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.96-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.100-1~deb12u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.4-1Debian Security Tracker ↗Source updated 5 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.

2 current
CVE-2026-64327 · CSAF 2.0 · revision 9 · interimSUSE Product Security TeamCVE-2026-64327
31 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.1
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.1
  • kernel-default as component of SUSE Linux Enterprise Server 16.0
  • kernel-devel as component of SUSE Linux Enterprise Server 16.0
  • kernel-macros as component of SUSE Linux Enterprise Server 16.0
  • kernel-source as component of SUSE Linux Enterprise Server 16.0
  • kernel-source-vanilla as component of SUSE Linux Enterprise Server 16.0
  • kernel-default as component of SUSE Linux Enterprise Server 16.1
  • kernel-devel as component of SUSE Linux Enterprise Server 16.1
  • kernel-macros as component of SUSE Linux Enterprise Server 16.1
Summary
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_fs: Initialize epfile->in early to fix endpoint direction checks When parsing endpoint descriptors, ffs_data_got_descs() generates the eps_addrmap which contains the endpoint direction. However, epfile->in was previously only populated in ffs_func_eps_enable() which executes upon USB host connection. As a result, early userspace ioctls like FUNCTIONFS_DMABUF_ATTACH that run before the host connects would see epfile->in as 0, leading to incorrect DMA directions. By moving the initialization to ffs_epfiles_create(), epfile->in is accurate before userspace opens the endpoint files.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-64327 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: usb: gadget: f_fs: Initialize epfile->in early to fix endpoint direction checks
274 known not affected

The vendor explicitly states that these products are not 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 FunctionFS (f_fs) module, which handles USB gadget functionality. This vulnerability occurs because the endpoint direction (`epfile->in`) was not correctly initialized until a USB host connected. Consequently, early operations initiated by userspace programs could encounter incorrect data transfer directions, potentially leading to unintended data access or corruption.
Remediation
No remediation text is recorded.
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-48871

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 13 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: usb: gadget: f_fs: Initialize epfile->in early to fix endpoint direction checks When parsing endpoint descriptors, ffs_data_got_descs() generates the eps_addrmap which contains the endpoint direction. However, epfile->in was previously only populated in ffs_func_eps_enable() which executes upon USB host connection. As a result, early userspace ioctls like FUNCTIONFS_DMABUF_ATTACH that run before the host connects would see epfile->in as 0, leading to incorrect DMA directions. By moving the initialization to ffs_epfiles_create(), epfile->in is accurate before userspace opens the endpoint files.

What

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_fs: Initialize epfile->in early to fix endpoint direction checks When parsing endpoint descriptors, ffs_data_got_descs() generates the eps_addrmap which contains the endpoint direction. However, epfile->in was previously only populated in ffs_func_eps_enable() which executes upon USB host connection. As a result, early userspace ioctls like FUNCTIONFS_DMABUF_ATTACH that run before the host connects would see epfile->in as 0, leading to incorrect DMA directions. By moving the initialization to ffs_epfiles_create(), epfile->in is accurate before userspace opens the endpoint files.

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: usb: gadget: f_fs: Initialize epfile->in early to fix endpoint direction checks When parsing endpoint descriptors, ffs_data_got_descs() generates the eps_addrmap which contains the endpoint direction. However, epfile->in was previously only populated in ffs_func_eps_enable() which executes upon USB host connection. As a result, early userspace ioctls like FUNCTIONFS_DMABUF_ATTACH that run before the host connects would see epfile->in as 0, leading to incorrect DMA directions. By moving the initialization to ffs_epfiles_create(), epfile->in is accurate before userspace opens the endpoint files.

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-2527Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.

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

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 29 Jul 2026, published on 29 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-64318 Référence CVE CVE-2026-64319 https://www.cve.org/CVERecord?id=CVE-2026-64319 Référence CVE CVE-2026-64320 https://www.cve.org/CVERecord?id=CVE-2026-64320 Référence CVE CVE-2026-64321 https://www.cve.org/CVERecord?id=CVE-2026-64321 Référence CVE CVE-2026-64322 https://www.cve.org/CVERecord?id=CVE-2026-64322 Référence CVE CVE-2026-64323 https://www.cve.org/CVERecord?id=CVE-2026-64323 Référence CVE CVE-2026-64324 https://www.cve.org/CVERecord?id=CVE-2026-64324 Référence CVE CVE-2026-64325 https://www.cve.org/CVERecord?id=CVE-2026-64325 Référence CVE CVE-2026-64326 https://www.cve.org/CVERecord?id=CVE-2026-64326 Référence CVE CVE-2026-64327 https://www.cve.org/CVERecord?id=CVE-2026-64327 Référence CVE CVE-2026-64328 https://www.cve.org/CVERecord?id=CVE-2026-64328 Référence CVE CVE-2026-64329 https://www.cve.org/CVERecord?id=CVE-2026-64329 Référence CVE CVE-2026-64330 https://www.cve.org/CVERecord?id=CVE-2026-64330 Référence CVE CVE-2026-64331 https://www.cve.org/CVERecord?id=CVE-2026-64331 Référence CVE CVE-2026-64332 https://www.cve.org/CVERecord?id=CVE-2026-64332 Référence CVE CVE-2026-64333 https://www.cve.org/CVERecord?id=CVE-2026-64333 Référence CVE CVE-2026-64334 https://www.cve.org/CVERecord?id=CVE-2026-64334 Référence CVE CVE-2026-64335 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1255Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-64315 Référence CVE CVE-2026-64316 https://www.cve.org/CVERecord?id=CVE-2026-64316 Référence CVE CVE-2026-64317 https://www.cve.org/CVERecord?id=CVE-2026-64317 Référence CVE CVE-2026-64319 https://www.cve.org/CVERecord?id=CVE-2026-64319 Référence CVE CVE-2026-64320 https://www.cve.org/CVERecord?id=CVE-2026-64320 Référence CVE CVE-2026-64321 https://www.cve.org/CVERecord?id=CVE-2026-64321 Référence CVE CVE-2026-64322 https://www.cve.org/CVERecord?id=CVE-2026-64322 Référence CVE CVE-2026-64323 https://www.cve.org/CVERecord?id=CVE-2026-64323 Référence CVE CVE-2026-64326 https://www.cve.org/CVERecord?id=CVE-2026-64326 Référence CVE CVE-2026-64327 https://www.cve.org/CVERecord?id=CVE-2026-64327 Référence CVE CVE-2026-64328 https://www.cve.org/CVERecord?id=CVE-2026-64328 Référence CVE CVE-2026-64329 https://www.cve.org/CVERecord?id=CVE-2026-64329 Référence CVE CVE-2026-64331 https://www.cve.org/CVERecord?id=CVE-2026-64331 Référence CVE CVE-2026-64332 https://www.cve.org/CVERecord?id=CVE-2026-64332 Référence CVE CVE-2026-64333 https://www.cve.org/CVERecord?id=CVE-2026-64333 Référence CVE CVE-2026-64334 https://www.cve.org/CVERecord?id=CVE-2026-64334 Référence CVE CVE-2026-64335 https://www.cve.org/CVERecord?id=CVE-2026-64335 Référence CVE CVE-2026-64337 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-64318 Référence CVE CVE-2026-64319 https://www.cve.org/CVERecord?id=CVE-2026-64319 Référence CVE CVE-2026-64320 https://www.cve.org/CVERecord?id=CVE-2026-64320 Référence CVE CVE-2026-64321 https://www.cve.org/CVERecord?id=CVE-2026-64321 Référence CVE CVE-2026-64322 https://www.cve.org/CVERecord?id=CVE-2026-64322 Référence CVE CVE-2026-64323 https://www.cve.org/CVERecord?id=CVE-2026-64323 Référence CVE CVE-2026-64324 https://www.cve.org/CVERecord?id=CVE-2026-64324 Référence CVE CVE-2026-64325 https://www.cve.org/CVERecord?id=CVE-2026-64325 Référence CVE CVE-2026-64326 https://www.cve.org/CVERecord?id=CVE-2026-64326 Référence CVE CVE-2026-64327 https://www.cve.org/CVERecord?id=CVE-2026-64327 Référence CVE CVE-2026-64328 https://www.cve.org/CVERecord?id=CVE-2026-64328 Référence CVE CVE-2026-64329 https://www.cve.org/CVERecord?id=CVE-2026-64329 Référence CVE CVE-2026-64330 https://www.cve.org/CVERecord?id=CVE-2026-64330 Référence CVE CVE-2026-64331 https://www.cve.org/CVERecord?id=CVE-2026-64331 Référence CVE CVE-2026-64332 https://www.cve.org/CVERecord?id=CVE-2026-64332 Référence CVE CVE-2026-64333 https://www.cve.org/CVERecord?id=CVE-2026-64333 Référence CVE CVE-2026-64334 https://www.cve.org/CVERecord?id=CVE-2026-64334 Référence CVE CVE-2026-64335 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-64318 Référence CVE CVE-2026-64319 https://www.cve.org/CVERecord?id=CVE-2026-64319 Référence CVE CVE-2026-64320 https://www.cve.org/CVERecord?id=CVE-2026-64320 Référence CVE CVE-2026-64321 https://www.cve.org/CVERecord?id=CVE-2026-64321 Référence CVE CVE-2026-64322 https://www.cve.org/CVERecord?id=CVE-2026-64322 Référence CVE CVE-2026-64323 https://www.cve.org/CVERecord?id=CVE-2026-64323 Référence CVE CVE-2026-64324 https://www.cve.org/CVERecord?id=CVE-2026-64324 Référence CVE CVE-2026-64325 https://www.cve.org/CVERecord?id=CVE-2026-64325 Référence CVE CVE-2026-64326 https://www.cve.org/CVERecord?id=CVE-2026-64326 Référence CVE CVE-2026-64327 https://www.cve.org/CVERecord?id=CVE-2026-64327 Référence CVE CVE-2026-64328 https://www.cve.org/CVERecord?id=CVE-2026-64328 Référence CVE CVE-2026-64329 https://www.cve.org/CVERecord?id=CVE-2026-64329 Référence CVE CVE-2026-64330 https://www.cve.org/CVERecord?id=CVE-2026-64330 Référence CVE CVE-2026-64331 https://www.cve.org/CVERecord?id=CVE-2026-64331 Référence CVE CVE-2026-64332 https://www.cve.org/CVERecord?id=CVE-2026-64332 Référence CVE CVE-2026-64333 https://www.cve.org/CVERecord?id=CVE-2026-64333 Référence CVE CVE-2026-64334 https://www.cve.org/CVERecord?id=CVE-2026-64334 Référence CVE CVE-2026-64335 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-64318 Référence CVE CVE-2026-64319 https://www.cve.org/CVERecord?id=CVE-2026-64319 Référence CVE CVE-2026-64320 https://www.cve.org/CVERecord?id=CVE-2026-64320 Référence CVE CVE-2026-64321 https://www.cve.org/CVERecord?id=CVE-2026-64321 Référence CVE CVE-2026-64322 https://www.cve.org/CVERecord?id=CVE-2026-64322 Référence CVE CVE-2026-64323 https://www.cve.org/CVERecord?id=CVE-2026-64323 Référence CVE CVE-2026-64324 https://www.cve.org/CVERecord?id=CVE-2026-64324 Référence CVE CVE-2026-64325 https://www.cve.org/CVERecord?id=CVE-2026-64325 Référence CVE CVE-2026-64326 https://www.cve.org/CVERecord?id=CVE-2026-64326 Référence CVE CVE-2026-64327 https://www.cve.org/CVERecord?id=CVE-2026-64327 Référence CVE CVE-2026-64328 https://www.cve.org/CVERecord?id=CVE-2026-64328 Référence CVE CVE-2026-64329 https://www.cve.org/CVERecord?id=CVE-2026-64329 Référence CVE CVE-2026-64330 https://www.cve.org/CVERecord?id=CVE-2026-64330 Référence CVE CVE-2026-64331 https://www.cve.org/CVERecord?id=CVE-2026-64331 Référence CVE CVE-2026-64332 https://www.cve.org/CVERecord?id=CVE-2026-64332 Référence CVE CVE-2026-64333 https://www.cve.org/CVERecord?id=CVE-2026-64333 Référence CVE CVE-2026-64334 https://www.cve.org/CVERecord?id=CVE-2026-64334 Référence CVE CVE-2026-64335 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1031Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-64317 Référence CVE CVE-2026-64318 https://www.cve.org/CVERecord?id=CVE-2026-64318 Référence CVE CVE-2026-64319 https://www.cve.org/CVERecord?id=CVE-2026-64319 Référence CVE CVE-2026-64320 https://www.cve.org/CVERecord?id=CVE-2026-64320 Référence CVE CVE-2026-64321 https://www.cve.org/CVERecord?id=CVE-2026-64321 Référence CVE CVE-2026-64322 https://www.cve.org/CVERecord?id=CVE-2026-64322 Référence CVE CVE-2026-64323 https://www.cve.org/CVERecord?id=CVE-2026-64323 Référence CVE CVE-2026-64324 https://www.cve.org/CVERecord?id=CVE-2026-64324 Référence CVE CVE-2026-64326 https://www.cve.org/CVERecord?id=CVE-2026-64326 Référence CVE CVE-2026-64327 https://www.cve.org/CVERecord?id=CVE-2026-64327 Référence CVE CVE-2026-64328 https://www.cve.org/CVERecord?id=CVE-2026-64328 Référence CVE CVE-2026-64329 https://www.cve.org/CVERecord?id=CVE-2026-64329 Référence CVE CVE-2026-64330 https://www.cve.org/CVERecord?id=CVE-2026-64330 Référence CVE CVE-2026-64331 https://www.cve.org/CVERecord?id=CVE-2026-64331 Référence CVE CVE-2026-64332 https://www.cve.org/CVERecord?id=CVE-2026-64332 Référence CVE CVE-2026-64333 https://www.cve.org/CVERecord?id=CVE-2026-64333 Référence CVE CVE-2026-64334 https://www.cve.org/CVERecord?id=CVE-2026-64334 Référence CVE CVE-2026-64335 https://www.cve.org/CVERecord?id=

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.9, 6.12.96 ≤ 6.12.*, 6.18.39 ≤ 6.18.*, 7.1.4 ≤ 7.1.*, 7.2 ≤ *
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 25 Jul 2026 · Last source change 17 Aug 2026, 04:53 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-48871
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
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/82cf1142e5ccf2b6d6d22ef713aaf3e5f2b5716b; added patch: git.kernel.org/82cfd4739011bdc7e87b5d585703427e89ddfaa5; 2 further additions.
    Before
    remediation: git.kernel.org/82cf1142e5ccf2b6d6d22ef713aaf3e5f2b5716b
    After
    patch: git.kernel.org/82cf1142e5ccf2b6d6d22ef713aaf3e5f2b5716b · patch: git.kernel.org/82cfd4739011bdc7e87b5d585703427e89ddfaa5 · patch: git.kernel.org/9e04055ab5fc0470a0031ee6934739f9aa8f34a5 · 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 ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    7b07a2a7ca02a20124b552be96c5a56910795488 < 82cf1142e5ccf2b6d6d22ef713aaf3e5f2b5716b; 7b07a2a7ca02a20124b552be96c5a56910795488 < 9e04055ab5fc0470a0031ee6934739f9aa8f34a5; 7b07a2a7ca02a20124b552be96c5a56910795488 < f99f32ea9aa976afcbec20647ed33b50a52002c1; 7b07a2a7ca02a20124b552be96c5a56910795488 < 82cfd4739011bdc7e87b5d585703427e89ddfaa5; 6.9 · Fixed: < 6.9; 6.12.96 ≤ 6.12.*; 6.18.39 ≤ 6.18.*; 7.1.4 ≤ 7.1.*; 7.2-rc3 ≤ *
    After
    7b07a2a7ca02a20124b552be96c5a56910795488 < 82cf1142e5ccf2b6d6d22ef713aaf3e5f2b5716b; 7b07a2a7ca02a20124b552be96c5a56910795488 < 9e04055ab5fc0470a0031ee6934739f9aa8f34a5; 7b07a2a7ca02a20124b552be96c5a56910795488 < f99f32ea9aa976afcbec20647ed33b50a52002c1; 7b07a2a7ca02a20124b552be96c5a56910795488 < 82cfd4739011bdc7e87b5d585703427e89ddfaa5; 6.9 · Fixed: < 6.9; 6.12.96 ≤ 6.12.*; 6.18.39 ≤ 6.18.*; 7.1.4 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
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-48871↗Vendor CSAF · SUSE Product Security Team↗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-64327 · cve.blacktree.nl