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

ALSA: seq: oss: Fix UAF at handling events with embedded SysEx data

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 17 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.17% 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 296 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 22 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 · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

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

2 current
CVE-2026-74388 · CSAF 2.0 · revision 7 · interimSUSE Product Security TeamCVE-2026-74388
271 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
Summary
In the Linux kernel, the following vulnerability has been resolved: ALSA: seq: oss: Fix UAF at handling events with embedded SysEx data The OSS sequencer processes the input MIDI bytes into a sequencer event to be dispatched later (in snd_seq_oss_midi_putc() called from snd_seq_oss_process_event()). When it's a SysEx data, the event record contains data.ext.ptr pointer to the original SysEx bytes, and the referred data is copied into the pool afterwards at dispatching. The problem is that, if the sequencer port gets closed concurrently before the dispatch, the OSS sequencer core also releases the resources (in snd_seq_oss_midi_check_exit_port()), while the pending event may hold a stale pointer, eventually leading to a UAF at a later dispatch. Fortunately, there is already a refcounting mechanism (snd_use_lock_t) for the OSS MIDI device access, and for addressing the issue above, we just need to extend the refcount until the event gets dispatched. This patch extends snd_seq_oss_process_event() to give back the refcount object, which is in turn released after calling the sequencer dispatcher with the given event in the caller side. According to the original report, KASAN report as below: KASAN slab-use-after-free in snd_seq_event_dup+0x40c/0x470 RIP: 0033:0x7f2cb66a6340 Read of size 6 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_seq_event_dup+0x40c/0x470 (?:?) kasan_check_range+0x10c/0x1c0 (?:?) __asan_memcpy+0x27/0x70 (?:?) snd_seq_event_dup+0x9/0x470 (?:?) snd_seq_client_enqueue_event+0x139/0x240 (?:?) _raw_spin_unlock_irqrestore+0x4b/0x60 (?:?) snd_seq_kernel_client_enqueue+0x102/0x120 (?:?) snd_seq_oss_write+0x416/0x4e0 (?:?) apparmor_file_permission+0x20/0x30 (?:?) odev_write+0x3b/0x60 (?:?) vfs_write+0x1ce/0x850 (?:?) lock_release+0xc8/0x2a0 (?:?) __kasan_check_write+0x18/0x20 (?:?) __mutex_unlock_slowpath+0x129/0x510 (?:?) ksys_write+0xe1/0x180 (?:?) mutex_unlock+0x16/0x20 (?:?) odev_ioctl+0x65/0xc0 (?:?) __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-74388 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: ALSA: seq: oss: Fix UAF at handling events with embedded SysEx data
274 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 Advanced Linux Sound Architecture (ALSA) Open Sound System (OSS) sequencer. A local attacker could exploit a Use-After-Free (UAF) vulnerability by concurrently closing a sequencer port while an event containing System Exclusive (SysEx) data is pending dispatch. This could lead to a denial of service or potentially arbitrary code execution.
Remediation
Fix deferred
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-59535

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 296 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: oss: Fix UAF at handling events with embedded SysEx data The OSS sequencer processes the input MIDI bytes into a sequencer event to be dispatched later (in snd_seq_oss_midi_putc() called from snd_seq_oss_process_event()). When it's a SysEx data, the event record contains data.ext.ptr pointer to the original SysEx bytes, and the referred data is copied into the pool afterwards at dispatching. The problem is that, if the sequencer port gets closed concurrently before the dispatch, the OSS sequencer core also releases the resources (in snd_seq_oss_midi_check_exit_port()), while the pending event may hold a stale pointer, eventually leading to a UAF at a later dispatch. Fortunately, there is already a refcounting mechanism (snd_use_lock_t) for the OSS MIDI device access, and for addressing the issue above, we just need to extend the refcount until the event gets dispatched. This patch extends snd_seq_oss_process_event() to give back the refcount object, which is in turn released after calling the sequencer dispatcher with the given event in the caller side. According to the original report, KASAN report as below: KASAN slab-use-after-free in snd_seq_event_dup+0x40c/0x470 RIP: 0033:0x7f2cb66a6340 Read of size 6 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_seq_event_dup+0x40c/0x470 (?:?) kasan_check_range+0x10c/0x1c0 (?:?) __asan_memcpy+0x27/0x70 (?:?) snd_seq_event_dup+0x9/0x470 (?:?) snd_seq_client_enqueue_event+0x139/0x240 (?:?) _raw_spin_unlock_irqrestore+0x4b/0x60 (?:?) snd_seq_kernel_client_enqueue+0x102/0x120 (?:?) snd_seq_oss_write+0x416/0x4e0 (?:?) apparmor_file_permission+0x20/0x30 (?:?) odev_write+0x3b/0x60 (?:?) vfs_write+0x1ce/0x850 (?:?) lock_release+0xc8/0x2a0 (?:?) __kasan_check_write+0x18/0x20 (?:?) __mutex_unlock_slowpath+0x129/0x510 (?:?) ksys_write+0xe1/0x180 (?:?) mutex_unlock+0x16/0x20 (?:?) odev_ioctl+0x65/0xc0 (?:?) __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: oss: Fix UAF at handling events with embedded SysEx data The OSS sequencer processes the input MIDI bytes into a sequencer event to be dispatched later (in snd_seq_oss_midi_putc() called from snd_seq_oss_process_event()). When it's a SysEx data, the event record contains data.ext.ptr pointer to the original SysEx bytes, and the referred data is copied into the pool afterwards at dispatching. The problem is that, if the sequencer port gets closed concurrently before the dispatch, the OSS sequencer core also releases the resources (in snd_seq_oss_midi_check_exit_port()), while the pending event may hold a stale pointer, eventually leading to a UAF at a later dispatch. Fortunately, there is already a refcounting mechanism (snd_use_lock_t) for the OSS MIDI device access, and for addressing the issue above, we just need to extend the refcount until the event gets dispatched. This patch extends snd_seq_oss_process_event() to give back the refcount object, which is in turn released after calling the sequencer dispatcher with the given event in the caller side. According to the original report, KASAN report as below: KASAN slab-use-after-free in snd_seq_event_dup+0x40c/0x470 RIP: 0033:0x7f2cb66a6340 Read of size 6 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_seq_event_dup+0x40c/0x470 (?:?) kasan_check_range+0x10c/0x1c0 (?:?) __asan_memcpy+0x27/0x70 (?:?) snd_seq_event_dup+0x9/0x470 (?:?) snd_seq_client_enqueue_event+0x139/0x240 (?:?) _raw_spin_unlock_irqrestore+0x4b/0x60 (?:?) snd_seq_kernel_client_enqueue+0x102/0x120 (?:?) snd_seq_oss_write+0x416/0x4e0 (?:?) apparmor_file_permission+0x20/0x30 (?:?) odev_write+0x3b/0x60 (?:?) vfs_write+0x1ce/0x850 (?:?) lock_release+0xc8/0x2a0 (?:?) __kasan_check_write+0x18/0x20 (?:?) __mutex_unlock_slowpath+0x129/0x510 (?:?) ksys_write+0xe1/0x180 (?:?) mutex_unlock+0x16/0x20 (?:?) odev_ioctl+0x65/0xc0 (?:?) __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: oss: Fix UAF at handling events with embedded SysEx data The OSS sequencer processes the input MIDI bytes into a sequencer event to be dispatched later (in snd_seq_oss_midi_putc() called from snd_seq_oss_process_event()). When it's a SysEx data, the event record contains data.ext.ptr pointer to the original SysEx bytes, and the referred data is copied into the pool afterwards at dispatching. The problem is that, if the sequencer port gets closed concurrently before the dispatch, the OSS sequencer core also releases the resources (in snd_seq_oss_midi_check_exit_port()), while the pending event may hold a stale pointer, eventually leading to a UAF at a later dispatch. Fortunately, there is already a refcounting mechanism (snd_use_lock_t) for the OSS MIDI device access, and for addressing the issue above, we just need to extend the refcount until the event gets dispatched. This patch extends snd_seq_oss_process_event() to give back the refcount object, which is in turn released after calling the sequencer dispatcher with the given event in the caller side. According to the original report, KASAN report as below: KASAN slab-use-after-free in snd_seq_event_dup+0x40c/0x470 RIP: 0033:0x7f2cb66a6340 Read of size 6 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_seq_event_dup+0x40c/0x470 (?:?) kasan_check_range+0x10c/0x1c0 (?:?) __asan_memcpy+0x27/0x70 (?:?) snd_seq_event_dup+0x9/0x470 (?:?) snd_seq_client_enqueue_event+0x139/0x240 (?:?) _raw_spin_unlock_irqrestore+0x4b/0x60 (?:?) snd_seq_kernel_client_enqueue+0x102/0x120 (?:?) snd_seq_oss_write+0x416/0x4e0 (?:?) apparmor_file_permission+0x20/0x30 (?:?) odev_write+0x3b/0x60 (?:?) vfs_write+0x1ce/0x850 (?:?) lock_release+0xc8/0x2a0 (?:?) __kasan_check_write+0x18/0x20 (?:?) __mutex_unlock_slowpath+0x129/0x510 (?:?) ksys_write+0xe1/0x180 (?:?) mutex_unlock+0x16/0x20 (?:?) odev_ioctl+0x65/0xc0 (?:?) __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-2852Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260819Security Bulletin 19 Aug 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 19 Aug 2026, published on 19 August 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2026-74334 Référence CVE CVE-2026-74345 https://www.cve.org/CVERecord?id=CVE-2026-74345 Référence CVE CVE-2026-74346 https://www.cve.org/CVERecord?id=CVE-2026-74346 Référence CVE CVE-2026-74349 https://www.cve.org/CVERecord?id=CVE-2026-74349 Référence CVE CVE-2026-74363 https://www.cve.org/CVERecord?id=CVE-2026-74363 Référence CVE CVE-2026-74375 https://www.cve.org/CVERecord?id=CVE-2026-74375 Référence CVE CVE-2026-74377 https://www.cve.org/CVERecord?id=CVE-2026-74377 Référence CVE CVE-2026-74378 https://www.cve.org/CVERecord?id=CVE-2026-74378 Référence CVE CVE-2026-74382 https://www.cve.org/CVERecord?id=CVE-2026-74382 Référence CVE CVE-2026-74388 https://www.cve.org/CVERecord?id=CVE-2026-74388 Référence CVE CVE-2026-74390 https://www.cve.org/CVERecord?id=CVE-2026-74390 Référence CVE CVE-2026-74394 https://www.cve.org/CVERecord?id=CVE-2026-74394 Référence CVE CVE-2026-74395 https://www.cve.org/CVERecord?id=CVE-2026-74395 Référence CVE CVE-2026-74397 https://www.cve.org/CVERecord?id=CVE-2026-74397 Référence CVE CVE-2026-74406 https://www.cve.org/CVERecord?id=CVE-2026-74406 Référence CVE CVE-2026-74464 https://www.cve.org/CVERecord?id=CVE-2026-74464 Référence CVE CVE-2026-74474 https://www.cve.org/CVERecord?id=CVE-2026-74474 Référence CVE CVE-2026-74475 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-74296 Référence CVE CVE-2026-74297 https://www.cve.org/CVERecord?id=CVE-2026-74297 Référence CVE CVE-2026-74302 https://www.cve.org/CVERecord?id=CVE-2026-74302 Référence CVE CVE-2026-74334 https://www.cve.org/CVERecord?id=CVE-2026-74334 Référence CVE CVE-2026-74341 https://www.cve.org/CVERecord?id=CVE-2026-74341 Référence CVE CVE-2026-74345 https://www.cve.org/CVERecord?id=CVE-2026-74345 Référence CVE CVE-2026-74377 https://www.cve.org/CVERecord?id=CVE-2026-74377 Référence CVE CVE-2026-74378 https://www.cve.org/CVERecord?id=CVE-2026-74378 Référence CVE CVE-2026-74382 https://www.cve.org/CVERecord?id=CVE-2026-74382 Référence CVE CVE-2026-74388 https://www.cve.org/CVERecord?id=CVE-2026-74388 Référence CVE CVE-2026-74390 https://www.cve.org/CVERecord?id=CVE-2026-74390 Référence CVE CVE-2026-74394 https://www.cve.org/CVERecord?id=CVE-2026-74394 Référence CVE CVE-2026-74406 https://www.cve.org/CVERecord?id=CVE-2026-74406 Référence CVE CVE-2026-74416 https://www.cve.org/CVERecord?id=CVE-2026-74416 Référence CVE CVE-2026-74417 https://www.cve.org/CVERecord?id=CVE-2026-74417 Référence CVE CVE-2026-74454 https://www.cve.org/CVERecord?id=CVE-2026-74454 Référence CVE CVE-2026-74479 https://www.cve.org/CVERecord?id=CVE-2026-74479 Référence CVE CVE-2026-74482 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: < 2.6.12, 6.18.40 ≤ 6.18.*, 7.1.5 ≤ 7.1.*, 7.2 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 15 Aug 2026 · Last source change 17 Aug 2026, 05:46 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-23
European sourceENISA EUVD · EUVD-2026-59535
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD received

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
    kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7; cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7; ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0; kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0; kernel-default as component of SUSE Linux Enterprise High 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; kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP2; reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2; kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP3; kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP3; and 239 more · 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
    kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7; cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7; ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0; kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0; kernel-default as component of SUSE Linux Enterprise High 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; kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP2; reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2; kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP3; kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP3; and 241 more
    SUSE Product Security Team ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 6dc781778b595be94c31395b2cb167f65145d91f; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 7aad70cabd8f34cf11a9593fcd3f2ac3f5496943; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 7c349b4f2a603202fb8c363bd2774a22ac2fddf3; 2.6.12 · Fixed: < 2.6.12; 6.18.40 ≤ 6.18.*; 7.1.5 ≤ 7.1.*; 7.2-rc1 ≤ *
    After
    1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 6dc781778b595be94c31395b2cb167f65145d91f; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 7aad70cabd8f34cf11a9593fcd3f2ac3f5496943; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 7c349b4f2a603202fb8c363bd2774a22ac2fddf3; 2.6.12 · Fixed: < 2.6.12; 6.18.40 ≤ 6.18.*; 7.1.5 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
  3. SeveritySeverity changed from Unknown to High.
    Before
    Unknown
    After
    High
    CNA ↗
  4. CVSS scoreCVSS score changed from not recorded to 7.8 (CVSS 3.1 · CNA · 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 · CNA · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)
    CNA ↗
  5. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-59535↗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-74388 · cve.blacktree.nl