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

ALSA: seq: Serialize UMP output teardown with event_input

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

Distribution package intelligence

Release-specific package status

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

24 package states
Package result overrides the generic status

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

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.94-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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-64029 · CSAF 2.0 · revision 14 · interimSUSE Product Security TeamCVE-2026-64029
17 known affected

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

  • SUSE Linux Micro Extras 6.2:kernel-obs-build
  • SUSE Linux Micro Extras 6.2:kernel-syms
  • SLES 15 SP1 CHOST Images for Amazon EC2
  • SLES 15 SP2 CHOST Images for Amazon EC2
  • SLES 15 SP3 CHOST Images for Amazon EC2
  • SLES 15 SP4 CHOST Images for Amazon EC2
  • SLES 15 SP5 CHOST Images for Amazon EC2
  • SLES 15 SP1 CHOST Images for Google
  • SLES 15 SP2 CHOST Images for Google
  • SLES 15 SP3 CHOST Images for Google
  • SLES 15 SP4 CHOST Images for Google
  • SLES 15 SP5 CHOST Images for Google
Summary
In the Linux kernel, the following vulnerability has been resolved: ALSA: seq: Serialize UMP output teardown with event_input seq_ump_process_event() borrows client->out_rfile.output without synchronizing with the first-open and last-close transition in seq_ump_client_open() and seq_ump_client_close(). The last output unuse can therefore drop opened[STR_OUT] to zero and release the rawmidi file while an in-flight event_input callback is still inside snd_rawmidi_kernel_write(). That leaves the rawmidi substream runtime exposed to teardown before the write path has taken its own buffer reference. Add a per-client rwlock for the event_input-visible output file. Publish a newly opened output file under the write side, and hold the read side from the output lookup through snd_rawmidi_kernel_write(). The last output close copies and clears the visible output file under the write side, then drops the lock and releases the saved rawmidi file. Use IRQ-safe rwlock guards because event_input can also be reached from atomic sequencer delivery. The buggy scenario involves two paths, with each column showing the order within that path: path A label: event_input path path B label: last unuse path 1. seq_ump_process_event() reads 1. seq_ump_client_close() client->out_rfile.output. drops opened[STR_OUT] to zero. 2. snd_rawmidi_kernel_write1() 2. snd_rawmidi_kernel_release() has not yet pinned runtime. closes the output file. 3. The writer continues using 3. close_substream() frees the borrowed substream. substream->runtime. This keeps the output substream and runtime alive for the full event_input write while keeping rawmidi release outside the rwlock. KASAN reproduced this as a slab-use-after-free in snd_rawmidi_kernel_write1(), with allocation through seq_ump_use()/snd_seq_port_connect() and free through seq_ump_unuse()/snd_seq_port_disconnect(). Validation reproduced this kernel report: KASAN slab-use-after-free in snd_rawmidi_kernel_write1+0x9d/0x400 RIP: 0033:0x7f5528af837f Read of size 8 Call trace: dump_stack_lvl+0x73/0xb0 (?:?) print_report+0xd1/0x650 (?:?) srso_alias_return_thunk+0x5/0xfbef5 (?:?) __virt_addr_valid+0x1a7/0x340 (?:?) kasan_complete_mode_report_info+0x64/0x200 (?:?) kasan_report+0xf7/0x130 (?:?) snd_rawmidi_kernel_write1+0x9d/0x400 (?:?) __asan_load8+0x82/0xb0 (?:?) update_stack_state+0x1ef/0x2d0 (?:?) snd_rawmidi_kernel_write+0x1a/0x20 (?:?) seq_ump_process_event+0xd4/0x120 (sound/core/seq/seq_ump_client.c:82) __snd_seq_deliver_single_event+0x8a/0xe0 (?:?) snd_seq_deliver_from_ump+0x2b2/0xd60 (?:?) lock_acquire+0x14e/0x2e0 (?:?) find_held_lock+0x31/0x90 (?:?) snd_seq_port_use_ptr+0xa6/0xe0 (?:?) __kasan_check_write+0x18/0x20 (?:?) do_raw_read_unlock+0x32/0xa0 (?:?) _raw_read_unlock+0x26/0x50 (?:?) snd_seq_deliver_single_event+0x45c/0x4b0 (?:?) snd_seq_deliver_event+0x10d/0x1b0 (?:?) snd_seq_client_enqueue_event+0x192/0x240 (?:?) snd_seq_write+0x2cd/0x450 (?:?) apparmor_file_permission+0x20/0x30 (?:?) security_file_permission+0x51/0x60 (?:?) vfs_write+0x1ce/0x850 (?:?) __fget_files+0x12b/0x220 (?:?) lock_release+0xc8/0x2a0 (?:?) __rcu_read_unlock+0x74/0x2d0 (?:?) __fget_files+0x135/0x220 (?:?) ksys_write+0x15a/0x180 (?:?) rcu_is_watching+0x24/0x60 (?:?) __x64_sys_write+0x46/0x60 (?:?) x64_sys_call+0x7d/0x20d0 (?:?) do_syscall_64+0xc1/0x360 (arch/x86/entry/syscall_64.c:87) entry_SYSCALL_64_after_hwframe+0x77/0x7f (?:?)
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-64029 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: ALSA: seq: Serialize UMP output teardown with event_input
22 known affected

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

  • kernel-rt as a component of Red Hat Enterprise Linux 9
  • kernel-rt-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-devel-matched as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-internal as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-partner as a component of Red Hat Enterprise Linux 9
Summary
A flaw was found in the Advanced Linux Sound Architecture (ALSA) sequencer component of the Linux kernel. This vulnerability, a use-after-free, occurs because of improper synchronization when handling Universal MIDI Packet (UMP) output. A local attacker could exploit this by creating a specific timing issue, which may lead to a system crash, resulting in a denial of service, or potentially allow for increased privileges on the system.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available.
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-45602

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 20 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: seq: Serialize UMP output teardown with event_input seq_ump_process_event() borrows client->out_rfile.output without synchronizing with the first-open and last-close transition in seq_ump_client_open() and seq_ump_client_close(). The last output unuse can therefore drop opened[STR_OUT] to zero and release the rawmidi file while an in-flight event_input callback is still inside snd_rawmidi_kernel_write(). That leaves the rawmidi substream runtime exposed to teardown before the write path has taken its own buffer reference. Add a per-client rwlock for the event_input-visible output file. Publish a newly opened output file under the write side, and hold the read side from the output lookup through snd_rawmidi_kernel_write(). The last output close copies and clears the visible output file under the write side, then drops the lock and releases the saved rawmidi file. Use IRQ-safe rwlock guards because event_input can also be reached from atomic sequencer delivery. The buggy scenario involves two paths, with each column showing the order within that path: path A label: event_input path path B label: last unuse path 1. seq_ump_process_event() reads 1. seq_ump_client_close() client->out_rfile.output. drops opened[STR_OUT] to zero. 2. snd_rawmidi_kernel_write1() 2. snd_rawmidi_kernel_release() has not yet pinned runtime. closes the output file. 3. The writer continues using 3. close_substream() frees the borrowed substream. substream->runtime. This keeps the output substream and runtime alive for the full event_input write while keeping rawmidi release outside the rwlock. KASAN reproduced this as a slab-use-after-free in snd_rawmidi_kernel_write1(), with allocation through seq_ump_use()/snd_seq_port_connect() and free through seq_ump_unuse()/snd_seq_port_disconnect(). Validation reproduced this kernel report: KASAN slab-use-after-free in snd_rawmidi_kernel_write1+0x9d/0x400 RIP: 0033:0x7f5528af837f Read of size 8 Call trace: dump_stack_lvl+0x73/0xb0 (?:?) print_report+0xd1/0x650 (?:?) srso_alias_return_thunk+0x5/0xfbef5 (?:?) __virt_addr_valid+0x1a7/0x340 (?:?) kasan_complete_mode_report_info+0x64/0x200 (?:?) kasan_report+0xf7/0x130 (?:?) snd_rawmidi_kernel_write1+0x9d/0x400 (?:?) __asan_load8+0x82/0xb0 (?:?) update_stack_state+0x1ef/0x2d0 (?:?) snd_rawmidi_kernel_write+0x1a/0x20 (?:?) seq_ump_process_event+0xd4/0x120 (sound/core/seq/seq_ump_client.c:82) __snd_seq_deliver_single_event+0x8a/0xe0 (?:?) snd_seq_deliver_from_ump+0x2b2/0xd60 (?:?) lock_acquire+0x14e/0x2e0 (?:?) find_held_lock+0x31/0x90 (?:?) snd_seq_port_use_ptr+0xa6/0xe0 (?:?) __kasan_check_write+0x18/0x20 (?:?) do_raw_read_unlock+0x32/0xa0 (?:?) _raw_read_unlock+0x26/0x50 (?:?) snd_seq_deliver_single_event+0x45c/0x4b0 (?:?) snd_seq_deliver_event+0x10d/0x1b0 (?:?) snd_seq_client_enqueue_event+0x192/0x240 (?:?) snd_seq_write+0x2cd/0x450 (?:?) apparmor_file_permission+0x20/0x30 (?:?) security_file_permission+0x51/0x60 (?:?) vfs_write+0x1ce/0x850 (?:?) __fget_files+0x12b/0x220 (?:?) lock_release+0xc8/0x2a0 (?:?) __rcu_read_unlock+0x74/0x2d0 (?:?) __fget_files+0x135/0x220 (?:?) ksys_write+0x15a/0x180 (?:?) rcu_is_watching+0x24/0x60 (?:?) __x64_sys_write+0x46/0x60 (?:?) x64_sys_call+0x7d/0x20d0 (?:?) do_syscall_64+0xc1/0x360 (arch/x86/entry/syscall_64.c:87) entry_SYSCALL_64_after_hwframe+0x77/0x7f (?:?)

What

In the Linux kernel, the following vulnerability has been resolved: ALSA: seq: Serialize UMP output teardown with event_input seq_ump_process_event() borrows client->out_rfile.output without synchronizing with the first-open and last-close transition in seq_ump_client_open() and seq_ump_client_close(). The last output unuse can therefore drop opened[STR_OUT] to zero and release the rawmidi file while an in-flight event_input callback is still inside snd_rawmidi_kernel_write(). That leaves the rawmidi substream runtime exposed to teardown before the write path has taken its own buffer reference. Add a per-client rwlock for the event_input-visible output file. Publish a newly opened output file under the write side, and hold the read side from the output lookup through snd_rawmidi_kernel_write(). The last output close copies and clears the visible output file under the write side, then drops the lock and releases the saved rawmidi file. Use IRQ-safe rwlock guards because event_input can also be reached from atomic sequencer delivery. The buggy scenario involves two paths, with each column showing the order within that path: path A label: event_input path path B label: last unuse path 1. seq_ump_process_event() reads 1. seq_ump_client_close() client->out_rfile.output. drops opened[STR_OUT] to zero. 2. snd_rawmidi_kernel_write1() 2. snd_rawmidi_kernel_release() has not yet pinned runtime. closes the output file. 3. The writer continues using 3. close_substream() frees the borrowed substream. substream->runtime. This keeps the output substream and runtime alive for the full event_input write while keeping rawmidi release outside the rwlock. KASAN reproduced this as a slab-use-after-free in snd_rawmidi_kernel_write1(), with allocation through seq_ump_use()/snd_seq_port_connect() and free through seq_ump_unuse()/snd_seq_port_disconnect(). Validation reproduced this kernel report: KASAN slab-use-after-free in snd_rawmidi_kernel_write1+0x9d/0x400 RIP: 0033:0x7f5528af837f Read of size 8 Call trace: dump_stack_lvl+0x73/0xb0 (?:?) print_report+0xd1/0x650 (?:?) srso_alias_return_thunk+0x5/0xfbef5 (?:?) __virt_addr_valid+0x1a7/0x340 (?:?) kasan_complete_mode_report_info+0x64/0x200 (?:?) kasan_report+0xf7/0x130 (?:?) snd_rawmidi_kernel_write1+0x9d/0x400 (?:?) __asan_load8+0x82/0xb0 (?:?) update_stack_state+0x1ef/0x2d0 (?:?) snd_rawmidi_kernel_write+0x1a/0x20 (?:?) seq_ump_process_event+0xd4/0x120 (sound/core/seq/seq_ump_client.c:82) __snd_seq_deliver_single_event+0x8a/0xe0 (?:?) snd_seq_deliver_from_ump+0x2b2/0xd60 (?:?) lock_acquire+0x14e/0x2e0 (?:?) find_held_lock+0x31/0x90 (?:?) snd_seq_port_use_ptr+0xa6/0xe0 (?:?) __kasan_check_write+0x18/0x20 (?:?) do_raw_read_unlock+0x32/0xa0 (?:?) _raw_read_unlock+0x26/0x50 (?:?) snd_seq_deliver_single_event+0x45c/0x4b0 (?:?) snd_seq_deliver_event+0x10d/0x1b0 (?:?) snd_seq_client_enqueue_event+0x192/0x240 (?:?) snd_seq_write+0x2cd/0x450 (?:?) apparmor_file_permission+0x20/0x30 (?:?) security_file_permission+0x51/0x60 (?:?) vfs_write+0x1ce/0x850 (?:?) __fget_files+0x12b/0x220 (?:?) lock_release+0xc8/0x2a0 (?:?) __rcu_read_unlock+0x74/0x2d0 (?:?) __fget_files+0x135/0x220 (?:?) ksys_write+0x15a/0x180 (?:?) rcu_is_watching+0x24/0x60 (?:?) __x64_sys_write+0x46/0x60 (?:?) x64_sys_call+0x7d/0x20d0 (?:?) do_syscall_64+0xc1/0x360 (arch/x86/entry/syscall_64.c:87) entry_SYSCALL_64_after_hwframe+0x77/0x7f (?:?)

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: ALSA: seq: Serialize UMP output teardown with event_input seq_ump_process_event() borrows client->out_rfile.output without synchronizing with the first-open and last-close transition in seq_ump_client_open() and seq_ump_client_close(). The last output unuse can therefore drop opened[STR_OUT] to zero and release the rawmidi file while an in-flight event_input callback is still inside snd_rawmidi_kernel_write(). That leaves the rawmidi substream runtime exposed to teardown before the write path has taken its own buffer reference. Add a per-client rwlock for the event_input-visible output file. Publish a newly opened output file under the write side, and hold the read side from the output lookup through snd_rawmidi_kernel_write(). The last output close copies and clears the visible output file under the write side, then drops the lock and releases the saved rawmidi file. Use IRQ-safe rwlock guards because event_input can also be reached from atomic sequencer delivery. The buggy scenario involves two paths, with each column showing the order within that path: path A label: event_input path path B label: last unuse path 1. seq_ump_process_event() reads 1. seq_ump_client_close() client->out_rfile.output. drops opened[STR_OUT] to zero. 2. snd_rawmidi_kernel_write1() 2. snd_rawmidi_kernel_release() has not yet pinned runtime. closes the output file. 3. The writer continues using 3. close_substream() frees the borrowed substream. substream->runtime. This keeps the output substream and runtime alive for the full event_input write while keeping rawmidi release outside the rwlock. KASAN reproduced this as a slab-use-after-free in snd_rawmidi_kernel_write1(), with allocation through seq_ump_use()/snd_seq_port_connect() and free through seq_ump_unuse()/snd_seq_port_disconnect(). Validation reproduced this kernel report: KASAN slab-use-after-free in snd_rawmidi_kernel_write1+0x9d/0x400 RIP: 0033:0x7f5528af837f Read of size 8 Call trace: dump_stack_lvl+0x73/0xb0 (?:?) print_report+0xd1/0x650 (?:?) srso_alias_return_thunk+0x5/0xfbef5 (?:?) __virt_addr_valid+0x1a7/0x340 (?:?) kasan_complete_mode_report_info+0x64/0x200 (?:?) kasan_report+0xf7/0x130 (?:?) snd_rawmidi_kernel_write1+0x9d/0x400 (?:?) __asan_load8+0x82/0xb0 (?:?) update_stack_state+0x1ef/0x2d0 (?:?) snd_rawmidi_kernel_write+0x1a/0x20 (?:?) seq_ump_process_event+0xd4/0x120 (sound/core/seq/seq_ump_client.c:82) __snd_seq_deliver_single_event+0x8a/0xe0 (?:?) snd_seq_deliver_from_ump+0x2b2/0xd60 (?:?) lock_acquire+0x14e/0x2e0 (?:?) find_held_lock+0x31/0x90 (?:?) snd_seq_port_use_ptr+0xa6/0xe0 (?:?) __kasan_check_write+0x18/0x20 (?:?) do_raw_read_unlock+0x32/0xa0 (?:?) _raw_read_unlock+0x26/0x50 (?:?) snd_seq_deliver_single_event+0x45c/0x4b0 (?:?) snd_seq_deliver_event+0x10d/0x1b0 (?:?) snd_seq_client_enqueue_event+0x192/0x240 (?:?) snd_seq_write+0x2cd/0x450 (?:?) apparmor_file_permission+0x20/0x30 (?:?) security_file_permission+0x51/0x60 (?:?) vfs_write+0x1ce/0x850 (?:?) __fget_files+0x12b/0x220 (?:?) lock_release+0xc8/0x2a0 (?:?) __rcu_read_unlock+0x74/0x2d0 (?:?) __fget_files+0x135/0x220 (?:?) ksys_write+0x15a/0x180 (?:?) rcu_is_watching+0x24/0x60 (?:?) __x64_sys_write+0x46/0x60 (?:?) x64_sys_call+0x7d/0x20d0 (?:?) do_syscall_64+0xc1/0x360 (arch/x86/entry/syscall_64.c:87) entry_SYSCALL_64_after_hwframe+0x77/0x7f (?:?)

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: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.
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-64019 Référence CVE CVE-2026-64020 https://www.cve.org/CVERecord?id=CVE-2026-64020 Référence CVE CVE-2026-64021 https://www.cve.org/CVERecord?id=CVE-2026-64021 Référence CVE CVE-2026-64022 https://www.cve.org/CVERecord?id=CVE-2026-64022 Référence CVE CVE-2026-64023 https://www.cve.org/CVERecord?id=CVE-2026-64023 Référence CVE CVE-2026-64024 https://www.cve.org/CVERecord?id=CVE-2026-64024 Référence CVE CVE-2026-64025 https://www.cve.org/CVERecord?id=CVE-2026-64025 Référence CVE CVE-2026-64026 https://www.cve.org/CVERecord?id=CVE-2026-64026 Référence CVE CVE-2026-64027 https://www.cve.org/CVERecord?id=CVE-2026-64027 Référence CVE CVE-2026-64029 https://www.cve.org/CVERecord?id=CVE-2026-64029 Référence CVE CVE-2026-64030 https://www.cve.org/CVERecord?id=CVE-2026-64030 Référence CVE CVE-2026-64031 https://www.cve.org/CVERecord?id=CVE-2026-64031 Référence CVE CVE-2026-64032 https://www.cve.org/CVERecord?id=CVE-2026-64032 Référence CVE CVE-2026-64033 https://www.cve.org/CVERecord?id=CVE-2026-64033 Référence CVE CVE-2026-64034 https://www.cve.org/CVERecord?id=CVE-2026-64034 Référence CVE CVE-2026-64035 https://www.cve.org/CVERecord?id=CVE-2026-64035 Référence CVE CVE-2026-64036 https://www.cve.org/CVERecord?id=CVE-2026-64036 Référence CVE CVE-2026-64037 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-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=CVE-2026-64014 Référence CVE CVE-2026-64015 https://www.cve.org/CVERecord?id=CVE-2026-64015 Référence CVE CVE-2026-64017 https://www.cve.org/CVERecord?id=CVE-2026-64017 Référence CVE CVE-2026-64024 https://www.cve.org/CVERecord?id=CVE-2026-64024 Référence CVE CVE-2026-64029 https://www.cve.org/CVERecord?id=CVE-2026-64029 Référence CVE CVE-2026-64033 https://www.cve.org/CVERecord?id=CVE-2026-64033 Référence CVE CVE-2026-64039 https://www.cve.org/CVERecord?id=CVE-2026-64039 Référence CVE CVE-2026-64047 https://www.cve.org/CVERecord?id=CVE-2026-64047 Référence CVE CVE-2026-64048 https://www.cve.org/CVERecord?id=CVE-2026-64048 Référence CVE CVE-2026-64051 https://www.cve.org/CVERecord?id=CVE-2026-64051 Référence CVE CVE-2026-64052 https://www.cve.org/CVERecord?id=CVE-2026-64052 Référence CVE CVE-2026-64053 https://www.cve.org/CVERecord?id=CVE-2026-64053 Référence CVE CVE-2026-64054 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-64019 Référence CVE CVE-2026-64020 https://www.cve.org/CVERecord?id=CVE-2026-64020 Référence CVE CVE-2026-64021 https://www.cve.org/CVERecord?id=CVE-2026-64021 Référence CVE CVE-2026-64022 https://www.cve.org/CVERecord?id=CVE-2026-64022 Référence CVE CVE-2026-64023 https://www.cve.org/CVERecord?id=CVE-2026-64023 Référence CVE CVE-2026-64024 https://www.cve.org/CVERecord?id=CVE-2026-64024 Référence CVE CVE-2026-64025 https://www.cve.org/CVERecord?id=CVE-2026-64025 Référence CVE CVE-2026-64026 https://www.cve.org/CVERecord?id=CVE-2026-64026 Référence CVE CVE-2026-64027 https://www.cve.org/CVERecord?id=CVE-2026-64027 Référence CVE CVE-2026-64029 https://www.cve.org/CVERecord?id=CVE-2026-64029 Référence CVE CVE-2026-64030 https://www.cve.org/CVERecord?id=CVE-2026-64030 Référence CVE CVE-2026-64031 https://www.cve.org/CVERecord?id=CVE-2026-64031 Référence CVE CVE-2026-64032 https://www.cve.org/CVERecord?id=CVE-2026-64032 Référence CVE CVE-2026-64033 https://www.cve.org/CVERecord?id=CVE-2026-64033 Référence CVE CVE-2026-64034 https://www.cve.org/CVERecord?id=CVE-2026-64034 Référence CVE CVE-2026-64035 https://www.cve.org/CVERecord?id=CVE-2026-64035 Référence CVE CVE-2026-64036 https://www.cve.org/CVERecord?id=CVE-2026-64036 Référence CVE CVE-2026-64037 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-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=CVE-2026-64014 Référence CVE CVE-2026-64015 https://www.cve.org/CVERecord?id=CVE-2026-64015 Référence CVE CVE-2026-64018 https://www.cve.org/CVERecord?id=CVE-2026-64018 Référence CVE CVE-2026-64021 https://www.cve.org/CVERecord?id=CVE-2026-64021 Référence CVE CVE-2026-64029 https://www.cve.org/CVERecord?id=CVE-2026-64029 Référence CVE CVE-2026-64033 https://www.cve.org/CVERecord?id=CVE-2026-64033 Référence CVE CVE-2026-64034 https://www.cve.org/CVERecord?id=CVE-2026-64034 Référence CVE CVE-2026-64039 https://www.cve.org/CVERecord?id=CVE-2026-64039 Référence CVE CVE-2026-64047 https://www.cve.org/CVERecord?id=CVE-2026-64047 Référence CVE CVE-2026-64048 https://www.cve.org/CVERecord?id=CVE-2026-64048 Référence CVE CVE-2026-64051 https://www.cve.org/CVERecord?id=CVE-2026-64051 Référence CVE CVE-2026-64052 https://www.cve.org/CVERecord?id=CVE-2026-64052 Référence CVE CVE-2026-64055 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-63993 Référence CVE CVE-2026-63994 https://www.cve.org/CVERecord?id=CVE-2026-63994 Référence CVE CVE-2026-64000 https://www.cve.org/CVERecord?id=CVE-2026-64000 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-64018 https://www.cve.org/CVERecord?id=CVE-2026-64018 Référence CVE CVE-2026-64025 https://www.cve.org/CVERecord?id=CVE-2026-64025 Référence CVE CVE-2026-64029 https://www.cve.org/CVERecord?id=CVE-2026-64029 Référence CVE CVE-2026-64032 https://www.cve.org/CVERecord?id=CVE-2026-64032 Référence CVE CVE-2026-64033 https://www.cve.org/CVERecord?id=CVE-2026-64033 Référence CVE CVE-2026-64034 https://www.cve.org/CVERecord?id=CVE-2026-64034 Référence CVE CVE-2026-64039 https://www.cve.org/CVERecord?id=CVE-2026-64039 Référence CVE CVE-2026-64046 https://www.cve.org/CVERecord?id=CVE-2026-64046 Référence CVE CVE-2026-64047 https://www.cve.org/CVERecord?id=CVE-2026-64047 Référence CVE CVE-2026-64048 https://www.cve.org/CVERecord?id=CVE-2026-64048 Référence CVE CVE-2026-64051 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-63887 Référence CVE CVE-2026-63888 https://www.cve.org/CVERecord?id=CVE-2026-63888 Référence CVE CVE-2026-63889 https://www.cve.org/CVERecord?id=CVE-2026-63889 Référence CVE CVE-2026-63917 https://www.cve.org/CVERecord?id=CVE-2026-63917 Référence CVE CVE-2026-63919 https://www.cve.org/CVERecord?id=CVE-2026-63919 Référence CVE CVE-2026-63921 https://www.cve.org/CVERecord?id=CVE-2026-63921 Référence CVE CVE-2026-63923 https://www.cve.org/CVERecord?id=CVE-2026-63923 Référence CVE CVE-2026-64002 https://www.cve.org/CVERecord?id=CVE-2026-64002 Référence CVE CVE-2026-64015 https://www.cve.org/CVERecord?id=CVE-2026-64015 Référence CVE CVE-2026-64029 https://www.cve.org/CVERecord?id=CVE-2026-64029 Référence CVE CVE-2026-64111 https://www.cve.org/CVERecord?id=CVE-2026-64111 Référence CVE CVE-2026-64117 https://www.cve.org/CVERecord?id=CVE-2026-64117 Référence CVE CVE-2026-64175 https://www.cve.org/CVERecord?id=CVE-2026-64175 Référence CVE CVE-2026-64176 https://www.cve.org/CVERecord?id=CVE-2026-64176 Référence CVE CVE-2026-64268 https://www.cve.org/CVERecord?id=CVE-2026-64268 Référence CVE CVE-2026-64304 https://www.cve.org/CVERecord?id=CVE-2026-64304 Référence CVE CVE-2026-64387 https://www.cve.org/CVERecord?id=CVE-2026-64387 Référence CVE CVE-2026-64414 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-64019 Référence CVE CVE-2026-64020 https://www.cve.org/CVERecord?id=CVE-2026-64020 Référence CVE CVE-2026-64021 https://www.cve.org/CVERecord?id=CVE-2026-64021 Référence CVE CVE-2026-64022 https://www.cve.org/CVERecord?id=CVE-2026-64022 Référence CVE CVE-2026-64023 https://www.cve.org/CVERecord?id=CVE-2026-64023 Référence CVE CVE-2026-64024 https://www.cve.org/CVERecord?id=CVE-2026-64024 Référence CVE CVE-2026-64025 https://www.cve.org/CVERecord?id=CVE-2026-64025 Référence CVE CVE-2026-64026 https://www.cve.org/CVERecord?id=CVE-2026-64026 Référence CVE CVE-2026-64027 https://www.cve.org/CVERecord?id=CVE-2026-64027 Référence CVE CVE-2026-64029 https://www.cve.org/CVERecord?id=CVE-2026-64029 Référence CVE CVE-2026-64030 https://www.cve.org/CVERecord?id=CVE-2026-64030 Référence CVE CVE-2026-64031 https://www.cve.org/CVERecord?id=CVE-2026-64031 Référence CVE CVE-2026-64032 https://www.cve.org/CVERecord?id=CVE-2026-64032 Référence CVE CVE-2026-64033 https://www.cve.org/CVERecord?id=CVE-2026-64033 Référence CVE CVE-2026-64034 https://www.cve.org/CVERecord?id=CVE-2026-64034 Référence CVE CVE-2026-64035 https://www.cve.org/CVERecord?id=CVE-2026-64035 Référence CVE CVE-2026-64036 https://www.cve.org/CVERecord?id=CVE-2026-64036 Référence CVE CVE-2026-64037 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-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=CVE-2026-64014 Référence CVE CVE-2026-64015 https://www.cve.org/CVERecord?id=CVE-2026-64015 Référence CVE CVE-2026-64018 https://www.cve.org/CVERecord?id=CVE-2026-64018 Référence CVE CVE-2026-64021 https://www.cve.org/CVERecord?id=CVE-2026-64021 Référence CVE CVE-2026-64029 https://www.cve.org/CVERecord?id=CVE-2026-64029 Référence CVE CVE-2026-64033 https://www.cve.org/CVERecord?id=CVE-2026-64033 Référence CVE CVE-2026-64034 https://www.cve.org/CVERecord?id=CVE-2026-64034 Référence CVE CVE-2026-64039 https://www.cve.org/CVERecord?id=CVE-2026-64039 Référence CVE CVE-2026-64047 https://www.cve.org/CVERecord?id=CVE-2026-64047 Référence CVE CVE-2026-64048 https://www.cve.org/CVERecord?id=CVE-2026-64048 Référence CVE CVE-2026-64051 https://www.cve.org/CVERecord?id=CVE-2026-64051 Référence CVE CVE-2026-64052 https://www.cve.org/CVERecord?id=CVE-2026-64052 Référence CVE CVE-2026-64055 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-64019 Référence CVE CVE-2026-64020 https://www.cve.org/CVERecord?id=CVE-2026-64020 Référence CVE CVE-2026-64021 https://www.cve.org/CVERecord?id=CVE-2026-64021 Référence CVE CVE-2026-64022 https://www.cve.org/CVERecord?id=CVE-2026-64022 Référence CVE CVE-2026-64023 https://www.cve.org/CVERecord?id=CVE-2026-64023 Référence CVE CVE-2026-64024 https://www.cve.org/CVERecord?id=CVE-2026-64024 Référence CVE CVE-2026-64025 https://www.cve.org/CVERecord?id=CVE-2026-64025 Référence CVE CVE-2026-64026 https://www.cve.org/CVERecord?id=CVE-2026-64026 Référence CVE CVE-2026-64027 https://www.cve.org/CVERecord?id=CVE-2026-64027 Référence CVE CVE-2026-64029 https://www.cve.org/CVERecord?id=CVE-2026-64029 Référence CVE CVE-2026-64030 https://www.cve.org/CVERecord?id=CVE-2026-64030 Référence CVE CVE-2026-64031 https://www.cve.org/CVERecord?id=CVE-2026-64031 Référence CVE CVE-2026-64032 https://www.cve.org/CVERecord?id=CVE-2026-64032 Référence CVE CVE-2026-64033 https://www.cve.org/CVERecord?id=CVE-2026-64033 Référence CVE CVE-2026-64034 https://www.cve.org/CVERecord?id=CVE-2026-64034 Référence CVE CVE-2026-64035 https://www.cve.org/CVERecord?id=CVE-2026-64035 Référence CVE CVE-2026-64036 https://www.cve.org/CVERecord?id=CVE-2026-64036 Référence CVE CVE-2026-64037 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-64019 Référence CVE CVE-2026-64020 https://www.cve.org/CVERecord?id=CVE-2026-64020 Référence CVE CVE-2026-64021 https://www.cve.org/CVERecord?id=CVE-2026-64021 Référence CVE CVE-2026-64022 https://www.cve.org/CVERecord?id=CVE-2026-64022 Référence CVE CVE-2026-64023 https://www.cve.org/CVERecord?id=CVE-2026-64023 Référence CVE CVE-2026-64024 https://www.cve.org/CVERecord?id=CVE-2026-64024 Référence CVE CVE-2026-64025 https://www.cve.org/CVERecord?id=CVE-2026-64025 Référence CVE CVE-2026-64026 https://www.cve.org/CVERecord?id=CVE-2026-64026 Référence CVE CVE-2026-64027 https://www.cve.org/CVERecord?id=CVE-2026-64027 Référence CVE CVE-2026-64029 https://www.cve.org/CVERecord?id=CVE-2026-64029 Référence CVE CVE-2026-64030 https://www.cve.org/CVERecord?id=CVE-2026-64030 Référence CVE CVE-2026-64031 https://www.cve.org/CVERecord?id=CVE-2026-64031 Référence CVE CVE-2026-64032 https://www.cve.org/CVERecord?id=CVE-2026-64032 Référence CVE CVE-2026-64033 https://www.cve.org/CVERecord?id=CVE-2026-64033 Référence CVE CVE-2026-64034 https://www.cve.org/CVERecord?id=CVE-2026-64034 Référence CVE CVE-2026-64035 https://www.cve.org/CVERecord?id=CVE-2026-64035 Référence CVE CVE-2026-64036 https://www.cve.org/CVERecord?id=CVE-2026-64036 Référence CVE CVE-2026-64037 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-64019 Référence CVE CVE-2026-64020 https://www.cve.org/CVERecord?id=CVE-2026-64020 Référence CVE CVE-2026-64021 https://www.cve.org/CVERecord?id=CVE-2026-64021 Référence CVE CVE-2026-64022 https://www.cve.org/CVERecord?id=CVE-2026-64022 Référence CVE CVE-2026-64023 https://www.cve.org/CVERecord?id=CVE-2026-64023 Référence CVE CVE-2026-64024 https://www.cve.org/CVERecord?id=CVE-2026-64024 Référence CVE CVE-2026-64025 https://www.cve.org/CVERecord?id=CVE-2026-64025 Référence CVE CVE-2026-64026 https://www.cve.org/CVERecord?id=CVE-2026-64026 Référence CVE CVE-2026-64027 https://www.cve.org/CVERecord?id=CVE-2026-64027 Référence CVE CVE-2026-64029 https://www.cve.org/CVERecord?id=CVE-2026-64029 Référence CVE CVE-2026-64030 https://www.cve.org/CVERecord?id=CVE-2026-64030 Référence CVE CVE-2026-64031 https://www.cve.org/CVERecord?id=CVE-2026-64031 Référence CVE CVE-2026-64032 https://www.cve.org/CVERecord?id=CVE-2026-64032 Référence CVE CVE-2026-64033 https://www.cve.org/CVERecord?id=CVE-2026-64033 Référence CVE CVE-2026-64034 https://www.cve.org/CVERecord?id=CVE-2026-64034 Référence CVE CVE-2026-64035 https://www.cve.org/CVERecord?id=CVE-2026-64035 Référence CVE CVE-2026-64036 https://www.cve.org/CVERecord?id=CVE-2026-64036 Référence CVE CVE-2026-64037 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.5, 6.6.142 ≤ 6.6.*, 6.12.92 ≤ 6.12.*, 6.18.34 ≤ 6.18.*, 7.0.11 ≤ 7.0.*, 7.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 19 Jul 2026 · Last source change 5 Aug 2026, 12:38 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
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-45602
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD awaiting enrichment

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. Affected versionsThe structured affected or fixed version information changed.
    Before
    SLES 15 SP1 CHOST Images for Amazon EC2; SLES 15 SP2 CHOST Images for Amazon EC2; SLES 15 SP3 CHOST Images for Amazon EC2; SLES 15 SP4 CHOST Images for Amazon EC2; SLES 15 SP5 CHOST Images for Amazon EC2; SLES 15 SP1 CHOST Images for Google; SLES 15 SP2 CHOST Images for Google; SLES 15 SP3 CHOST Images for Google; SLES 15 SP4 CHOST Images for Google; SLES 15 SP5 CHOST Images for Google; SLES 15 SP1 CHOST Images for Microsoft Azure; SLES 15 SP2 CHOST Images for Microsoft Azure; SLES 15 SP3 CHOST Images for Microsoft Azure; SLES 15 SP4 CHOST Images for Microsoft Azure; SLES 15 SP5 CHOST Images for Microsoft Azure · Fixed: kernel-64kb-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-64kb-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-64kb-extra-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-azure-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-azure-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-azure-extra-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-azure-vdso-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-default-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-default-base-6.12.0-160000.38.1.160000.2.24 as component of SUSE Linux Enterprise Server 16.0; kernel-default-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-default-extra-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-default-livepatch-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-default-vdso-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-docs-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-docs-html-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-kvmsmall-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-kvmsmall-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-kvmsmall-vdso-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-macros-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-obs-qa-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-source-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-source-vanilla-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-syms-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-zfcpdump-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; cluster-md-kmp-default-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server for SAP applications 16.0; dlm-kmp-default-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server for SAP applications 16.0; gfs2-kmp-default-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server for SAP applications 16.0; kernel-64kb-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server for SAP applications 16.0; kernel-64kb-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server for SAP applications 16.0; and 38 more
    After
    SUSE Linux Micro Extras 6.2:kernel-obs-build; SUSE Linux Micro Extras 6.2:kernel-syms; SLES 15 SP1 CHOST Images for Amazon EC2; SLES 15 SP2 CHOST Images for Amazon EC2; SLES 15 SP3 CHOST Images for Amazon EC2; SLES 15 SP4 CHOST Images for Amazon EC2; SLES 15 SP5 CHOST Images for Amazon EC2; SLES 15 SP1 CHOST Images for Google; SLES 15 SP2 CHOST Images for Google; SLES 15 SP3 CHOST Images for Google; SLES 15 SP4 CHOST Images for Google; SLES 15 SP5 CHOST Images for Google; SLES 15 SP1 CHOST Images for Microsoft Azure; SLES 15 SP2 CHOST Images for Microsoft Azure; SLES 15 SP3 CHOST Images for Microsoft Azure; SLES 15 SP4 CHOST Images for Microsoft Azure; SLES 15 SP5 CHOST Images for Microsoft Azure
    SUSE Product Security Team ↗
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-45602↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor 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-64029 · cve.blacktree.nl