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

cpufreq: qcom-cpufreq-hw: Fix possible double free

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 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 severityHighOperational priority:Medium, 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.13% 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 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.

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

2 current
CVE-2026-64377 · CSAF 2.0 · revision 8 · interimSUSE Product Security TeamCVE-2026-64377
125 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
Summary
In the Linux kernel, the following vulnerability has been resolved: cpufreq: qcom-cpufreq-hw: Fix possible double free qcom_cpufreq.data is allocated with devm_kzalloc() in probe() as an array of per-domain data. qcom_cpufreq_hw_cpu_init() stores a pointer to one element of this array in policy->driver_data. qcom_cpufreq_hw_cpu_exit() currently calls kfree() on policy->driver_data. This is not valid because the memory is devm-managed. For the first domain, this can free the devm-managed allocation while the devres entry is still active, leading to a possible double free when the platform device is later detached. For other domains, the pointer may refer to an element inside the array rather than the allocation base. Remove the kfree(data) call and let devres release qcom_cpufreq.data. This issue was found by a static analysis tool I am developing.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-64377 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: cpufreq: qcom-cpufreq-hw: Fix possible double free
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 `qcom-cpufreq-hw` driver. This vulnerability, a double free, occurs due to incorrect memory handling when a device is detached. Specifically, the system attempts to release memory that is already managed, leading to a potential double free. This can result in system instability, memory corruption, or a denial of service (DoS), making the system unavailable to legitimate users.
Remediation
Affected
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-48921

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 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: cpufreq: qcom-cpufreq-hw: Fix possible double free qcom_cpufreq.data is allocated with devm_kzalloc() in probe() as an array of per-domain data. qcom_cpufreq_hw_cpu_init() stores a pointer to one element of this array in policy->driver_data. qcom_cpufreq_hw_cpu_exit() currently calls kfree() on policy->driver_data. This is not valid because the memory is devm-managed. For the first domain, this can free the devm-managed allocation while the devres entry is still active, leading to a possible double free when the platform device is later detached. For other domains, the pointer may refer to an element inside the array rather than the allocation base. Remove the kfree(data) call and let devres release qcom_cpufreq.data. This issue was found by a static analysis tool I am developing.

What

In the Linux kernel, the following vulnerability has been resolved: cpufreq: qcom-cpufreq-hw: Fix possible double free qcom_cpufreq.data is allocated with devm_kzalloc() in probe() as an array of per-domain data. qcom_cpufreq_hw_cpu_init() stores a pointer to one element of this array in policy->driver_data. qcom_cpufreq_hw_cpu_exit() currently calls kfree() on policy->driver_data. This is not valid because the memory is devm-managed. For the first domain, this can free the devm-managed allocation while the devres entry is still active, leading to a possible double free when the platform device is later detached. For other domains, the pointer may refer to an element inside the array rather than the allocation base. Remove the kfree(data) call and let devres release qcom_cpufreq.data. This issue was found by a static analysis tool I am developing.

Why

The product calls free() twice on the same memory address.

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: cpufreq: qcom-cpufreq-hw: Fix possible double free qcom_cpufreq.data is allocated with devm_kzalloc() in probe() as an array of per-domain data. qcom_cpufreq_hw_cpu_init() stores a pointer to one element of this array in policy->driver_data. qcom_cpufreq_hw_cpu_exit() currently calls kfree() on policy->driver_data. This is not valid because the memory is devm-managed. For the first domain, this can free the devm-managed allocation while the devres entry is still active, leading to a possible double free when the platform device is later detached. For other domains, the pointer may refer to an element inside the array rather than the allocation base. Remove the kfree(data) call and let devres release qcom_cpufreq.data. This issue was found by a static analysis tool I am developing.

Why

The product calls free() twice on the same memory address.

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 → Double Free → 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-415 ↗

CWE-415: Double Free. The product calls free() twice on the same memory address.

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-415
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-64368 Référence CVE CVE-2026-64369 https://www.cve.org/CVERecord?id=CVE-2026-64369 Référence CVE CVE-2026-64370 https://www.cve.org/CVERecord?id=CVE-2026-64370 Référence CVE CVE-2026-64371 https://www.cve.org/CVERecord?id=CVE-2026-64371 Référence CVE CVE-2026-64372 https://www.cve.org/CVERecord?id=CVE-2026-64372 Référence CVE CVE-2026-64373 https://www.cve.org/CVERecord?id=CVE-2026-64373 Référence CVE CVE-2026-64374 https://www.cve.org/CVERecord?id=CVE-2026-64374 Référence CVE CVE-2026-64375 https://www.cve.org/CVERecord?id=CVE-2026-64375 Référence CVE CVE-2026-64376 https://www.cve.org/CVERecord?id=CVE-2026-64376 Référence CVE CVE-2026-64377 https://www.cve.org/CVERecord?id=CVE-2026-64377 Référence CVE CVE-2026-64378 https://www.cve.org/CVERecord?id=CVE-2026-64378 Référence CVE CVE-2026-64379 https://www.cve.org/CVERecord?id=CVE-2026-64379 Référence CVE CVE-2026-64380 https://www.cve.org/CVERecord?id=CVE-2026-64380 Référence CVE CVE-2026-64381 https://www.cve.org/CVERecord?id=CVE-2026-64381 Référence CVE CVE-2026-64382 https://www.cve.org/CVERecord?id=CVE-2026-64382 Référence CVE CVE-2026-64383 https://www.cve.org/CVERecord?id=CVE-2026-64383 Référence CVE CVE-2026-64384 https://www.cve.org/CVERecord?id=CVE-2026-64384 Référence CVE CVE-2026-64385 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-64368 Référence CVE CVE-2026-64369 https://www.cve.org/CVERecord?id=CVE-2026-64369 Référence CVE CVE-2026-64370 https://www.cve.org/CVERecord?id=CVE-2026-64370 Référence CVE CVE-2026-64371 https://www.cve.org/CVERecord?id=CVE-2026-64371 Référence CVE CVE-2026-64372 https://www.cve.org/CVERecord?id=CVE-2026-64372 Référence CVE CVE-2026-64373 https://www.cve.org/CVERecord?id=CVE-2026-64373 Référence CVE CVE-2026-64374 https://www.cve.org/CVERecord?id=CVE-2026-64374 Référence CVE CVE-2026-64375 https://www.cve.org/CVERecord?id=CVE-2026-64375 Référence CVE CVE-2026-64376 https://www.cve.org/CVERecord?id=CVE-2026-64376 Référence CVE CVE-2026-64377 https://www.cve.org/CVERecord?id=CVE-2026-64377 Référence CVE CVE-2026-64378 https://www.cve.org/CVERecord?id=CVE-2026-64378 Référence CVE CVE-2026-64379 https://www.cve.org/CVERecord?id=CVE-2026-64379 Référence CVE CVE-2026-64380 https://www.cve.org/CVERecord?id=CVE-2026-64380 Référence CVE CVE-2026-64381 https://www.cve.org/CVERecord?id=CVE-2026-64381 Référence CVE CVE-2026-64382 https://www.cve.org/CVERecord?id=CVE-2026-64382 Référence CVE CVE-2026-64383 https://www.cve.org/CVERecord?id=CVE-2026-64383 Référence CVE CVE-2026-64384 https://www.cve.org/CVERecord?id=CVE-2026-64384 Référence CVE CVE-2026-64385 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-64368 Référence CVE CVE-2026-64369 https://www.cve.org/CVERecord?id=CVE-2026-64369 Référence CVE CVE-2026-64370 https://www.cve.org/CVERecord?id=CVE-2026-64370 Référence CVE CVE-2026-64371 https://www.cve.org/CVERecord?id=CVE-2026-64371 Référence CVE CVE-2026-64372 https://www.cve.org/CVERecord?id=CVE-2026-64372 Référence CVE CVE-2026-64373 https://www.cve.org/CVERecord?id=CVE-2026-64373 Référence CVE CVE-2026-64374 https://www.cve.org/CVERecord?id=CVE-2026-64374 Référence CVE CVE-2026-64375 https://www.cve.org/CVERecord?id=CVE-2026-64375 Référence CVE CVE-2026-64376 https://www.cve.org/CVERecord?id=CVE-2026-64376 Référence CVE CVE-2026-64377 https://www.cve.org/CVERecord?id=CVE-2026-64377 Référence CVE CVE-2026-64378 https://www.cve.org/CVERecord?id=CVE-2026-64378 Référence CVE CVE-2026-64379 https://www.cve.org/CVERecord?id=CVE-2026-64379 Référence CVE CVE-2026-64380 https://www.cve.org/CVERecord?id=CVE-2026-64380 Référence CVE CVE-2026-64381 https://www.cve.org/CVERecord?id=CVE-2026-64381 Référence CVE CVE-2026-64382 https://www.cve.org/CVERecord?id=CVE-2026-64382 Référence CVE CVE-2026-64383 https://www.cve.org/CVERecord?id=CVE-2026-64383 Référence CVE CVE-2026-64384 https://www.cve.org/CVERecord?id=CVE-2026-64384 Référence CVE CVE-2026-64385 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-64368 Référence CVE CVE-2026-64369 https://www.cve.org/CVERecord?id=CVE-2026-64369 Référence CVE CVE-2026-64370 https://www.cve.org/CVERecord?id=CVE-2026-64370 Référence CVE CVE-2026-64371 https://www.cve.org/CVERecord?id=CVE-2026-64371 Référence CVE CVE-2026-64372 https://www.cve.org/CVERecord?id=CVE-2026-64372 Référence CVE CVE-2026-64373 https://www.cve.org/CVERecord?id=CVE-2026-64373 Référence CVE CVE-2026-64374 https://www.cve.org/CVERecord?id=CVE-2026-64374 Référence CVE CVE-2026-64375 https://www.cve.org/CVERecord?id=CVE-2026-64375 Référence CVE CVE-2026-64376 https://www.cve.org/CVERecord?id=CVE-2026-64376 Référence CVE CVE-2026-64377 https://www.cve.org/CVERecord?id=CVE-2026-64377 Référence CVE CVE-2026-64378 https://www.cve.org/CVERecord?id=CVE-2026-64378 Référence CVE CVE-2026-64379 https://www.cve.org/CVERecord?id=CVE-2026-64379 Référence CVE CVE-2026-64380 https://www.cve.org/CVERecord?id=CVE-2026-64380 Référence CVE CVE-2026-64381 https://www.cve.org/CVERecord?id=CVE-2026-64381 Référence CVE CVE-2026-64382 https://www.cve.org/CVERecord?id=CVE-2026-64382 Référence CVE CVE-2026-64383 https://www.cve.org/CVERecord?id=CVE-2026-64383 Référence CVE CVE-2026-64384 https://www.cve.org/CVERecord?id=CVE-2026-64384 Référence CVE CVE-2026-64385 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-64368 Référence CVE CVE-2026-64369 https://www.cve.org/CVERecord?id=CVE-2026-64369 Référence CVE CVE-2026-64370 https://www.cve.org/CVERecord?id=CVE-2026-64370 Référence CVE CVE-2026-64371 https://www.cve.org/CVERecord?id=CVE-2026-64371 Référence CVE CVE-2026-64372 https://www.cve.org/CVERecord?id=CVE-2026-64372 Référence CVE CVE-2026-64373 https://www.cve.org/CVERecord?id=CVE-2026-64373 Référence CVE CVE-2026-64374 https://www.cve.org/CVERecord?id=CVE-2026-64374 Référence CVE CVE-2026-64375 https://www.cve.org/CVERecord?id=CVE-2026-64375 Référence CVE CVE-2026-64376 https://www.cve.org/CVERecord?id=CVE-2026-64376 Référence CVE CVE-2026-64377 https://www.cve.org/CVERecord?id=CVE-2026-64377 Référence CVE CVE-2026-64378 https://www.cve.org/CVERecord?id=CVE-2026-64378 Référence CVE CVE-2026-64379 https://www.cve.org/CVERecord?id=CVE-2026-64379 Référence CVE CVE-2026-64380 https://www.cve.org/CVERecord?id=CVE-2026-64380 Référence CVE CVE-2026-64381 https://www.cve.org/CVERecord?id=CVE-2026-64381 Référence CVE CVE-2026-64382 https://www.cve.org/CVERecord?id=CVE-2026-64382 Référence CVE CVE-2026-64383 https://www.cve.org/CVERecord?id=CVE-2026-64383 Référence CVE CVE-2026-64384 https://www.cve.org/CVERecord?id=CVE-2026-64384 Référence CVE CVE-2026-64385 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.2, 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:54 UTC · CWE-415 · Double Free

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-48921
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
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/28a03a3f6e6cda0b0da3b43761d175dec5d14d13; added patch: git.kernel.org/9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d; 2 further additions.
    Before
    remediation: git.kernel.org/28a03a3f6e6cda0b0da3b43761d175dec5d14d13
    After
    patch: git.kernel.org/28a03a3f6e6cda0b0da3b43761d175dec5d14d13 · patch: git.kernel.org/9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d · patch: git.kernel.org/bcb8889c4981fdde42d4fd2c29a77d510fe21da2 · 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 ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    054a3ef683a176a509cc9b37f762029aae942495 < 28a03a3f6e6cda0b0da3b43761d175dec5d14d13; 054a3ef683a176a509cc9b37f762029aae942495 < e904961332801c87355f5d11c65bb433e717c489; 054a3ef683a176a509cc9b37f762029aae942495 < 9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d; 054a3ef683a176a509cc9b37f762029aae942495 < bcb8889c4981fdde42d4fd2c29a77d510fe21da2; 6.2 · Fixed: < 6.2; 6.12.96 ≤ 6.12.*; 6.18.39 ≤ 6.18.*; 7.1.4 ≤ 7.1.*; 7.2-rc1 ≤ *
    After
    054a3ef683a176a509cc9b37f762029aae942495 < 28a03a3f6e6cda0b0da3b43761d175dec5d14d13; 054a3ef683a176a509cc9b37f762029aae942495 < e904961332801c87355f5d11c65bb433e717c489; 054a3ef683a176a509cc9b37f762029aae942495 < 9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d; 054a3ef683a176a509cc9b37f762029aae942495 < bcb8889c4981fdde42d4fd2c29a77d510fe21da2; 6.2 · Fixed: < 6.2; 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-48921↗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-64377 · cve.blacktree.nl