Skip to main content

Linux Kernel CVE-2026-64134

| EUVDEUVD-2026-45819 HIGH
NULL Pointer Dereference (CWE-476)
2026-07-19 Linux GHSA-g8p3-wvvx-m6mf
High
Disputed · 7.8 Vendor: Linux
Share

Severity by source

Sources disagree (Low–High)
Vendor (Linux) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
5.5 MEDIUM

Local audio-device access (AV:L, PR:L) with a NULL dereference that crashes the kernel gives A:H; the description shows no data read or modification, so C:N/I:N.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
HIGH
qualitative
Red Hat
5.5 LOW
qualitative

vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jul 20, 2026 - 17:39 vuln.today
CVSS changed
Jul 20, 2026 - 15:22 NVD
7.8 (HIGH)
Patch available
Jul 19, 2026 - 17:03 EUVD
CVE Published
Jul 19, 2026 - 15:40 cve.org
UNKNOWN (no severity yet)
CVE Published
Jul 19, 2026 - 15:40 cve.org
HIGH 7.8

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

ALSA: pcm: Don't setup bogus iov_iter for silencing

At transition to the iov_iter for PCM data transfer, we blindly applied the iov_iter setup also for silencing (i.e. data = NULL), and it leads to a calculation of bogus iov_iter. Fortunately this didn't cause troubles on most of architectures but it goes wrong on RISC-V now, causing a NULL dereference.

Handle the NULL data case to treat the silencing in interleaved_copy() for addressing the bug above. noninterleaved_copy() has already the NULL data handling, so it doesn't need changes.

AnalysisAI

Denial of service in the Linux kernel ALSA PCM subsystem allows a local low-privileged user with sound-device access to crash the system on RISC-V hardware. During the transition to iov_iter for PCM data transfer, the silencing path (data = NULL) reused the interleaved iov_iter setup, producing a bogus iterator that triggers a NULL pointer dereference; on most other architectures it was benign, but RISC-V faults. No public exploit is identified at time of analysis, and EPSS risk is low at 0.17% (6th percentile). The kernel tags flag potential information disclosure, though the concretely described symptom is a crash.

Technical ContextAI

The flaw lives in the ALSA (Advanced Linux Sound Architecture) PCM core, specifically interleaved_copy() in the sound/core/pcm code path that moves audio frames between user and kernel buffers. A refactor migrated PCM data transfer to the kernel's iov_iter abstraction but applied the same iov_iter construction to the 'silencing' operation, which passes data = NULL to fill a buffer with silence rather than copying real user data. With a NULL source, the length/base math produces an invalid iov_iter and the subsequent access dereferences NULL. This is effectively an improper NULL/pointer handling bug (CWE-476 class, though CWE is unlisted in the feed); noninterleaved_copy() already special-cased NULL data and was unaffected. The affected component is the mainline Linux kernel (cpe:2.3:a:linux:linux), and the fault surfaces on RISC-V due to differing memory-access behavior versus x86/ARM.

RemediationAI

Vendor-released patch: upgrade to a fixed stable kernel - 6.6.142, 6.12.92, 6.18.34, 7.0.11, or 7.1 (or later), whichever matches your branch. The upstream fix adds NULL-data handling to interleaved_copy() so the silencing path no longer builds a bogus iov_iter; corresponding stable commits are 41a766c647294842c9b17672449f8e011048cba9, ce836587e594af39ff048d9b29dee0f5f10692c9, feff0251386aa6bb180a0a1cf7c1f91ba868113d, c9f6768515818d71bdfc20119a81f3332c53b9c6, and e4d3386b74fba8e01280484b67ee481ece00201e (git.kernel.org/stable/c/<hash>). If immediate kernel upgrade is not possible, restrict access to ALSA PCM devices by tightening permissions on /dev/snd/* (e.g. remove untrusted users from the 'audio' group), which prevents unprivileged triggering at the cost of blocking legitimate local audio for those users; on servers without an audio workload, blacklisting/unloading snd_pcm and related sound modules removes the attack surface entirely with no functional trade-off. These controls are most relevant on RISC-V deployments where the crash is confirmed.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

CVE-2026-64134 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy