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

ALSA: pcm: oss: Fix setup list UAF on proc write error

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 219 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.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 219 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 21 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 · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

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

2 current
CVE-2026-64001 · CSAF 2.0 · revision 13 · interimSUSE Product Security TeamCVE-2026-64001
240 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP2
Summary
In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: oss: Fix setup list UAF on proc write error snd_pcm_oss_proc_write() links a newly allocated setup entry into the OSS setup list before duplicating the task name. If the task-name allocation fails, the error path frees the already linked entry and leaves setup_list pointing at freed memory. A later OSS device open can then walk the stale list entry in snd_pcm_oss_look_for_setup() and dereference freed memory. Allocate the task name and initialize the setup entry before publishing the entry on setup_list. Also fetch the initial proc read iterator only after taking setup_mutex, so all setup_list traversal follows the same list lifetime rules.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-64001 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: ALSA: pcm: oss: Fix setup list UAF on proc write error
198 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 ALSA (Advanced Linux Sound Architecture) PCM (Pulse Code Modulation) OSS (Open Sound System) component. A local user could exploit a Use-After-Free (UAF) vulnerability in the `snd_pcm_oss_proc_write()` function. This occurs when a setup entry is prematurely linked into the OSS setup list, and a subsequent task-name allocation failure leads to the entry being freed while still referenced. A later attempt to open an OSS device could then access this freed memory, potentially leading to memory corruption or system instability.
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-45574

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 219 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: ALSA: pcm: oss: Fix setup list UAF on proc write error snd_pcm_oss_proc_write() links a newly allocated setup entry into the OSS setup list before duplicating the task name. If the task-name allocation fails, the error path frees the already linked entry and leaves setup_list pointing at freed memory. A later OSS device open can then walk the stale list entry in snd_pcm_oss_look_for_setup() and dereference freed memory. Allocate the task name and initialize the setup entry before publishing the entry on setup_list. Also fetch the initial proc read iterator only after taking setup_mutex, so all setup_list traversal follows the same list lifetime rules.

What

In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: oss: Fix setup list UAF on proc write error snd_pcm_oss_proc_write() links a newly allocated setup entry into the OSS setup list before duplicating the task name. If the task-name allocation fails, the error path frees the already linked entry and leaves setup_list pointing at freed memory. A later OSS device open can then walk the stale list entry in snd_pcm_oss_look_for_setup() and dereference freed memory. Allocate the task name and initialize the setup entry before publishing the entry on setup_list. Also fetch the initial proc read iterator only after taking setup_mutex, so all setup_list traversal follows the same list lifetime rules.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

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: ALSA: pcm: oss: Fix setup list UAF on proc write error snd_pcm_oss_proc_write() links a newly allocated setup entry into the OSS setup list before duplicating the task name. If the task-name allocation fails, the error path frees the already linked entry and leaves setup_list pointing at freed memory. A later OSS device open can then walk the stale list entry in snd_pcm_oss_look_for_setup() and dereference freed memory. Allocate the task name and initialize the setup entry before publishing the entry on setup_list. Also fetch the initial proc read iterator only after taking setup_mutex, so all setup_list traversal follows the same list lifetime rules.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

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 → Use After 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-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

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-416
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-63992 Référence CVE CVE-2026-63993 https://www.cve.org/CVERecord?id=CVE-2026-63993 Référence CVE CVE-2026-63994 https://www.cve.org/CVERecord?id=CVE-2026-63994 Référence CVE CVE-2026-63995 https://www.cve.org/CVERecord?id=CVE-2026-63995 Référence CVE CVE-2026-63996 https://www.cve.org/CVERecord?id=CVE-2026-63996 Référence CVE CVE-2026-63997 https://www.cve.org/CVERecord?id=CVE-2026-63997 Référence CVE CVE-2026-63998 https://www.cve.org/CVERecord?id=CVE-2026-63998 Référence CVE CVE-2026-63999 https://www.cve.org/CVERecord?id=CVE-2026-63999 Référence CVE CVE-2026-64000 https://www.cve.org/CVERecord?id=CVE-2026-64000 Référence CVE CVE-2026-64001 https://www.cve.org/CVERecord?id=CVE-2026-64001 Référence CVE CVE-2026-64002 https://www.cve.org/CVERecord?id=CVE-2026-64002 Référence CVE CVE-2026-64003 https://www.cve.org/CVERecord?id=CVE-2026-64003 Référence CVE CVE-2026-64004 https://www.cve.org/CVERecord?id=CVE-2026-64004 Référence CVE CVE-2026-64005 https://www.cve.org/CVERecord?id=CVE-2026-64005 Référence CVE CVE-2026-64006 https://www.cve.org/CVERecord?id=CVE-2026-64006 Référence CVE CVE-2026-64007 https://www.cve.org/CVERecord?id=CVE-2026-64007 Référence CVE CVE-2026-64008 https://www.cve.org/CVERecord?id=CVE-2026-64008 Référence CVE CVE-2026-64009 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-63990 Référence CVE CVE-2026-63992 https://www.cve.org/CVERecord?id=CVE-2026-63992 Référence CVE CVE-2026-63993 https://www.cve.org/CVERecord?id=CVE-2026-63993 Référence CVE CVE-2026-63995 https://www.cve.org/CVERecord?id=CVE-2026-63995 Référence CVE CVE-2026-63996 https://www.cve.org/CVERecord?id=CVE-2026-63996 Référence CVE CVE-2026-63997 https://www.cve.org/CVERecord?id=CVE-2026-63997 Référence CVE CVE-2026-63998 https://www.cve.org/CVERecord?id=CVE-2026-63998 Référence CVE CVE-2026-63999 https://www.cve.org/CVERecord?id=CVE-2026-63999 Référence CVE CVE-2026-64000 https://www.cve.org/CVERecord?id=CVE-2026-64000 Référence CVE CVE-2026-64001 https://www.cve.org/CVERecord?id=CVE-2026-64001 Référence CVE CVE-2026-64002 https://www.cve.org/CVERecord?id=CVE-2026-64002 Référence CVE CVE-2026-64003 https://www.cve.org/CVERecord?id=CVE-2026-64003 Référence CVE CVE-2026-64004 https://www.cve.org/CVERecord?id=CVE-2026-64004 Référence CVE CVE-2026-64005 https://www.cve.org/CVERecord?id=CVE-2026-64005 Référence CVE CVE-2026-64006 https://www.cve.org/CVERecord?id=CVE-2026-64006 Référence CVE CVE-2026-64007 https://www.cve.org/CVERecord?id=CVE-2026-64007 Référence CVE CVE-2026-64010 https://www.cve.org/CVERecord?id=CVE-2026-64010 Référence CVE CVE-2026-64011 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-63890 Référence CVE CVE-2026-63891 https://www.cve.org/CVERecord?id=CVE-2026-63891 Référence CVE CVE-2026-63892 https://www.cve.org/CVERecord?id=CVE-2026-63892 Référence CVE CVE-2026-63898 https://www.cve.org/CVERecord?id=CVE-2026-63898 Référence CVE CVE-2026-63920 https://www.cve.org/CVERecord?id=CVE-2026-63920 Référence CVE CVE-2026-63928 https://www.cve.org/CVERecord?id=CVE-2026-63928 Référence CVE CVE-2026-63962 https://www.cve.org/CVERecord?id=CVE-2026-63962 Référence CVE CVE-2026-63990 https://www.cve.org/CVERecord?id=CVE-2026-63990 Référence CVE CVE-2026-63992 https://www.cve.org/CVERecord?id=CVE-2026-63992 Référence CVE CVE-2026-64001 https://www.cve.org/CVERecord?id=CVE-2026-64001 Référence CVE CVE-2026-64002 https://www.cve.org/CVERecord?id=CVE-2026-64002 Référence CVE CVE-2026-64005 https://www.cve.org/CVERecord?id=CVE-2026-64005 Référence CVE CVE-2026-64007 https://www.cve.org/CVERecord?id=CVE-2026-64007 Référence CVE CVE-2026-64010 https://www.cve.org/CVERecord?id=CVE-2026-64010 Référence CVE CVE-2026-64011 https://www.cve.org/CVERecord?id=CVE-2026-64011 Référence CVE CVE-2026-64015 https://www.cve.org/CVERecord?id=CVE-2026-64015 Référence CVE CVE-2026-64047 https://www.cve.org/CVERecord?id=CVE-2026-64047 Référence CVE CVE-2026-64048 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-63992 Référence CVE CVE-2026-63993 https://www.cve.org/CVERecord?id=CVE-2026-63993 Référence CVE CVE-2026-63994 https://www.cve.org/CVERecord?id=CVE-2026-63994 Référence CVE CVE-2026-63995 https://www.cve.org/CVERecord?id=CVE-2026-63995 Référence CVE CVE-2026-63996 https://www.cve.org/CVERecord?id=CVE-2026-63996 Référence CVE CVE-2026-63997 https://www.cve.org/CVERecord?id=CVE-2026-63997 Référence CVE CVE-2026-63998 https://www.cve.org/CVERecord?id=CVE-2026-63998 Référence CVE CVE-2026-63999 https://www.cve.org/CVERecord?id=CVE-2026-63999 Référence CVE CVE-2026-64000 https://www.cve.org/CVERecord?id=CVE-2026-64000 Référence CVE CVE-2026-64001 https://www.cve.org/CVERecord?id=CVE-2026-64001 Référence CVE CVE-2026-64002 https://www.cve.org/CVERecord?id=CVE-2026-64002 Référence CVE CVE-2026-64003 https://www.cve.org/CVERecord?id=CVE-2026-64003 Référence CVE CVE-2026-64004 https://www.cve.org/CVERecord?id=CVE-2026-64004 Référence CVE CVE-2026-64005 https://www.cve.org/CVERecord?id=CVE-2026-64005 Référence CVE CVE-2026-64006 https://www.cve.org/CVERecord?id=CVE-2026-64006 Référence CVE CVE-2026-64007 https://www.cve.org/CVERecord?id=CVE-2026-64007 Référence CVE CVE-2026-64008 https://www.cve.org/CVERecord?id=CVE-2026-64008 Référence CVE CVE-2026-64009 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-63985 Référence CVE CVE-2026-63990 https://www.cve.org/CVERecord?id=CVE-2026-63990 Référence CVE CVE-2026-63992 https://www.cve.org/CVERecord?id=CVE-2026-63992 Référence CVE CVE-2026-63995 https://www.cve.org/CVERecord?id=CVE-2026-63995 Référence CVE CVE-2026-63996 https://www.cve.org/CVERecord?id=CVE-2026-63996 Référence CVE CVE-2026-63997 https://www.cve.org/CVERecord?id=CVE-2026-63997 Référence CVE CVE-2026-63998 https://www.cve.org/CVERecord?id=CVE-2026-63998 Référence CVE CVE-2026-63999 https://www.cve.org/CVERecord?id=CVE-2026-63999 Référence CVE CVE-2026-64000 https://www.cve.org/CVERecord?id=CVE-2026-64000 Référence CVE CVE-2026-64001 https://www.cve.org/CVERecord?id=CVE-2026-64001 Référence CVE CVE-2026-64002 https://www.cve.org/CVERecord?id=CVE-2026-64002 Référence CVE CVE-2026-64004 https://www.cve.org/CVERecord?id=CVE-2026-64004 Référence CVE CVE-2026-64005 https://www.cve.org/CVERecord?id=CVE-2026-64005 Référence CVE CVE-2026-64006 https://www.cve.org/CVERecord?id=CVE-2026-64006 Référence CVE CVE-2026-64007 https://www.cve.org/CVERecord?id=CVE-2026-64007 Référence CVE CVE-2026-64010 https://www.cve.org/CVERecord?id=CVE-2026-64010 Référence CVE CVE-2026-64011 https://www.cve.org/CVERecord?id=CVE-2026-64011 Référence CVE CVE-2026-64014 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-63992 Référence CVE CVE-2026-63993 https://www.cve.org/CVERecord?id=CVE-2026-63993 Référence CVE CVE-2026-63994 https://www.cve.org/CVERecord?id=CVE-2026-63994 Référence CVE CVE-2026-63995 https://www.cve.org/CVERecord?id=CVE-2026-63995 Référence CVE CVE-2026-63996 https://www.cve.org/CVERecord?id=CVE-2026-63996 Référence CVE CVE-2026-63997 https://www.cve.org/CVERecord?id=CVE-2026-63997 Référence CVE CVE-2026-63998 https://www.cve.org/CVERecord?id=CVE-2026-63998 Référence CVE CVE-2026-63999 https://www.cve.org/CVERecord?id=CVE-2026-63999 Référence CVE CVE-2026-64000 https://www.cve.org/CVERecord?id=CVE-2026-64000 Référence CVE CVE-2026-64001 https://www.cve.org/CVERecord?id=CVE-2026-64001 Référence CVE CVE-2026-64002 https://www.cve.org/CVERecord?id=CVE-2026-64002 Référence CVE CVE-2026-64003 https://www.cve.org/CVERecord?id=CVE-2026-64003 Référence CVE CVE-2026-64004 https://www.cve.org/CVERecord?id=CVE-2026-64004 Référence CVE CVE-2026-64005 https://www.cve.org/CVERecord?id=CVE-2026-64005 Référence CVE CVE-2026-64006 https://www.cve.org/CVERecord?id=CVE-2026-64006 Référence CVE CVE-2026-64007 https://www.cve.org/CVERecord?id=CVE-2026-64007 Référence CVE CVE-2026-64008 https://www.cve.org/CVERecord?id=CVE-2026-64008 Référence CVE CVE-2026-64009 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-63985 Référence CVE CVE-2026-63990 https://www.cve.org/CVERecord?id=CVE-2026-63990 Référence CVE CVE-2026-63992 https://www.cve.org/CVERecord?id=CVE-2026-63992 Référence CVE CVE-2026-63995 https://www.cve.org/CVERecord?id=CVE-2026-63995 Référence CVE CVE-2026-63996 https://www.cve.org/CVERecord?id=CVE-2026-63996 Référence CVE CVE-2026-63997 https://www.cve.org/CVERecord?id=CVE-2026-63997 Référence CVE CVE-2026-63998 https://www.cve.org/CVERecord?id=CVE-2026-63998 Référence CVE CVE-2026-63999 https://www.cve.org/CVERecord?id=CVE-2026-63999 Référence CVE CVE-2026-64000 https://www.cve.org/CVERecord?id=CVE-2026-64000 Référence CVE CVE-2026-64001 https://www.cve.org/CVERecord?id=CVE-2026-64001 Référence CVE CVE-2026-64002 https://www.cve.org/CVERecord?id=CVE-2026-64002 Référence CVE CVE-2026-64004 https://www.cve.org/CVERecord?id=CVE-2026-64004 Référence CVE CVE-2026-64005 https://www.cve.org/CVERecord?id=CVE-2026-64005 Référence CVE CVE-2026-64006 https://www.cve.org/CVERecord?id=CVE-2026-64006 Référence CVE CVE-2026-64007 https://www.cve.org/CVERecord?id=CVE-2026-64007 Référence CVE CVE-2026-64010 https://www.cve.org/CVERecord?id=CVE-2026-64010 Référence CVE CVE-2026-64011 https://www.cve.org/CVERecord?id=CVE-2026-64011 Référence CVE CVE-2026-64014 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-63992 Référence CVE CVE-2026-63993 https://www.cve.org/CVERecord?id=CVE-2026-63993 Référence CVE CVE-2026-63994 https://www.cve.org/CVERecord?id=CVE-2026-63994 Référence CVE CVE-2026-63995 https://www.cve.org/CVERecord?id=CVE-2026-63995 Référence CVE CVE-2026-63996 https://www.cve.org/CVERecord?id=CVE-2026-63996 Référence CVE CVE-2026-63997 https://www.cve.org/CVERecord?id=CVE-2026-63997 Référence CVE CVE-2026-63998 https://www.cve.org/CVERecord?id=CVE-2026-63998 Référence CVE CVE-2026-63999 https://www.cve.org/CVERecord?id=CVE-2026-63999 Référence CVE CVE-2026-64000 https://www.cve.org/CVERecord?id=CVE-2026-64000 Référence CVE CVE-2026-64001 https://www.cve.org/CVERecord?id=CVE-2026-64001 Référence CVE CVE-2026-64002 https://www.cve.org/CVERecord?id=CVE-2026-64002 Référence CVE CVE-2026-64003 https://www.cve.org/CVERecord?id=CVE-2026-64003 Référence CVE CVE-2026-64004 https://www.cve.org/CVERecord?id=CVE-2026-64004 Référence CVE CVE-2026-64005 https://www.cve.org/CVERecord?id=CVE-2026-64005 Référence CVE CVE-2026-64006 https://www.cve.org/CVERecord?id=CVE-2026-64006 Référence CVE CVE-2026-64007 https://www.cve.org/CVERecord?id=CVE-2026-64007 Référence CVE CVE-2026-64008 https://www.cve.org/CVERecord?id=CVE-2026-64008 Référence CVE CVE-2026-64009 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-63992 Référence CVE CVE-2026-63993 https://www.cve.org/CVERecord?id=CVE-2026-63993 Référence CVE CVE-2026-63994 https://www.cve.org/CVERecord?id=CVE-2026-63994 Référence CVE CVE-2026-63995 https://www.cve.org/CVERecord?id=CVE-2026-63995 Référence CVE CVE-2026-63996 https://www.cve.org/CVERecord?id=CVE-2026-63996 Référence CVE CVE-2026-63997 https://www.cve.org/CVERecord?id=CVE-2026-63997 Référence CVE CVE-2026-63998 https://www.cve.org/CVERecord?id=CVE-2026-63998 Référence CVE CVE-2026-63999 https://www.cve.org/CVERecord?id=CVE-2026-63999 Référence CVE CVE-2026-64000 https://www.cve.org/CVERecord?id=CVE-2026-64000 Référence CVE CVE-2026-64001 https://www.cve.org/CVERecord?id=CVE-2026-64001 Référence CVE CVE-2026-64002 https://www.cve.org/CVERecord?id=CVE-2026-64002 Référence CVE CVE-2026-64003 https://www.cve.org/CVERecord?id=CVE-2026-64003 Référence CVE CVE-2026-64004 https://www.cve.org/CVERecord?id=CVE-2026-64004 Référence CVE CVE-2026-64005 https://www.cve.org/CVERecord?id=CVE-2026-64005 Référence CVE CVE-2026-64006 https://www.cve.org/CVERecord?id=CVE-2026-64006 Référence CVE CVE-2026-64007 https://www.cve.org/CVERecord?id=CVE-2026-64007 Référence CVE CVE-2026-64008 https://www.cve.org/CVERecord?id=CVE-2026-64008 Référence CVE CVE-2026-64009 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-63992 Référence CVE CVE-2026-63993 https://www.cve.org/CVERecord?id=CVE-2026-63993 Référence CVE CVE-2026-63994 https://www.cve.org/CVERecord?id=CVE-2026-63994 Référence CVE CVE-2026-63995 https://www.cve.org/CVERecord?id=CVE-2026-63995 Référence CVE CVE-2026-63996 https://www.cve.org/CVERecord?id=CVE-2026-63996 Référence CVE CVE-2026-63997 https://www.cve.org/CVERecord?id=CVE-2026-63997 Référence CVE CVE-2026-63998 https://www.cve.org/CVERecord?id=CVE-2026-63998 Référence CVE CVE-2026-63999 https://www.cve.org/CVERecord?id=CVE-2026-63999 Référence CVE CVE-2026-64000 https://www.cve.org/CVERecord?id=CVE-2026-64000 Référence CVE CVE-2026-64001 https://www.cve.org/CVERecord?id=CVE-2026-64001 Référence CVE CVE-2026-64002 https://www.cve.org/CVERecord?id=CVE-2026-64002 Référence CVE CVE-2026-64003 https://www.cve.org/CVERecord?id=CVE-2026-64003 Référence CVE CVE-2026-64004 https://www.cve.org/CVERecord?id=CVE-2026-64004 Référence CVE CVE-2026-64005 https://www.cve.org/CVERecord?id=CVE-2026-64005 Référence CVE CVE-2026-64006 https://www.cve.org/CVERecord?id=CVE-2026-64006 Référence CVE CVE-2026-64007 https://www.cve.org/CVERecord?id=CVE-2026-64007 Référence CVE CVE-2026-64008 https://www.cve.org/CVERecord?id=CVE-2026-64008 Référence CVE CVE-2026-64009 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-036479LinuxのLinux Kernelにおける解放済みメモリの使用に関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。ALSA: pcm: oss: proc書き込みエラー時のsetupリストのUse-After-Free(UAF)修正についてです。snd_pcm_oss_proc_write()は、新たに割り当てられたsetupエントリをタスク名を複製する前にOSSのsetupリストにリンクします。もしタスク名の割り当てが失敗した場合、エラー処理はすでにリンクされたエントリを解放し、その結果setup_listが解放済みメモリを指す状態になってしまいます。後のOSSデバイスのオープン処理でsnd_pcm_oss_look_for_setup()がこの古いリストエントリを辿り、解放済みのメモリを逆参照してしまう可能性があります。対策としては、task名を割り当ててsetupエントリを初期化してから、setup_listにエントリを公開するように変更しました。また、setup_mutexを取得してから初期のproc読み取りイテレータを取得することで、すべてのsetup_listの走査が同一のリスト寿命ルールに従うようにしています。

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: < 2.6.17, 6.12.93 ≤ 6.12.*, 6.18.35 ≤ 6.18.*, 7.0.12 ≤ 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, 14:56 UTC · CWE-416 · Use After 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-45574
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/4cc54bdd54b337e77115be5b55577d1c58608eae; added patch: git.kernel.org/8be4efd0dc0093eb7a02ad1aac936bca2a1f04ce; 2 further additions.
    Before
    remediation: git.kernel.org/8be4efd0dc0093eb7a02ad1aac936bca2a1f04ce
    After
    patch: git.kernel.org/4cc54bdd54b337e77115be5b55577d1c58608eae · patch: git.kernel.org/8be4efd0dc0093eb7a02ad1aac936bca2a1f04ce · patch: git.kernel.org/be387230dc22d870afd0e5d35912b07c2bc323bd · 2 more references
    git.kernel.org ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    060d77b9c04acd7aef60790398a53f731db8c8fe < 8be4efd0dc0093eb7a02ad1aac936bca2a1f04ce; 060d77b9c04acd7aef60790398a53f731db8c8fe < e13922bb97b4e6f94f8ac02d034f2d4bd65eeb3c; 060d77b9c04acd7aef60790398a53f731db8c8fe < be387230dc22d870afd0e5d35912b07c2bc323bd; 060d77b9c04acd7aef60790398a53f731db8c8fe < 4cc54bdd54b337e77115be5b55577d1c58608eae; 2.6.17 · Fixed: < 2.6.17; 6.12.93 ≤ 6.12.*; 6.18.35 ≤ 6.18.*; 7.0.12 ≤ 7.0.*; 7.1 ≤ *
    After
    Linux: 060d77b9c04acd7aef60790398a53f731db8c8fe < 8be4efd0dc0093eb7a02ad1aac936bca2a1f04ce, 060d77b9c04acd7aef60790398a53f731db8c8fe < e13922bb97b4e6f94f8ac02d034f2d4bd65eeb3c, 060d77b9c04acd7aef60790398a53f731db8c8fe < be387230dc22d870afd0e5d35912b07c2bc323bd, 060d77b9c04acd7aef60790398a53f731db8c8fe < 4cc54bdd54b337e77115be5b55577d1c58608eae, 2.6.17 · Fixed: Linux: < 2.6.17, 6.12.93 ≤ 6.12.*, 6.18.35 ≤ 6.18.*, 7.0.12 ≤ 7.0.*, 7.1 ≤ *
    CNA ↗
  3. SeveritySeverity changed from Unknown to High.
    Before
    Unknown
    After
    High
    NIST NVD ↗
  4. 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
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-64001 · cve.blacktree.nl