CyberSecBulletin
CVE-2026-64134NVD status: Modified

Linux: NULL Pointer Dereference

Published Updated By the CyberSecBulletin desk

CVE-2026-64134 is a high-severity NULL pointer dereference vulnerability in Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 41a766c647294842c9b17672449f8e011048cba9, ce836587e594af39ff048d9b29dee0f5f10692c9, feff0251386aa6bb180a0a1cf7c1f91ba868113d as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.13% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 41a766c647294842c9b17672449f8e011048cba9 or ce836587e594af39ff048d9b29dee0f5f10692c9 or feff0251386aa6bb180a0a1cf7c1f91ba868113d or c9f6768515818d71bdfc20119a81f3332c53b9c6, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.6.142 or 6.12.92 or 6.18.34 or 7.0.11, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxcf393babb37a1679a1ec1d864df1090353465e23 up to, but not including, 41a766c647294842c9b17672449f8e011048cba9; cf393babb37a1679a1ec1d864df1090353465e23 up to, but not including, ce836587e594af39ff048d9b29dee0f5f10692c9; cf393babb37a1679a1ec1d864df1090353465e23 up to, but not including, feff0251386aa6bb180a0a1cf7c1f91ba868113d; cf393babb37a1679a1ec1d864df1090353465e23 up to, but not including, c9f6768515818d71bdfc20119a81f3332c53b9c6; cf393babb37a1679a1ec1d864df1090353465e23 up to, but not including, e4d3386b74fba8e01280484b67ee481ece00201e; 6.641a766c647294842c9b17672449f8e011048cba9, ce836587e594af39ff048d9b29dee0f5f10692c9, feff0251386aa6bb180a0a1cf7c1f91ba868113d, c9f6768515818d71bdfc20119a81f3332c53b9c6, e4d3386b74fba8e01280484b67ee481ece00201e
LinuxLinux Kernel6.6 up to, but not including, 6.6.142; 6.7 up to, but not including, 6.12.92; 6.13 up to, but not including, 6.18.34; 6.19 up to, but not including, 7.0.11; 7.16.6.142, 6.12.92, 6.18.34, 7.0.11

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.

Official description

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: NULL Pointer Dereference

The product dereferences a pointer that it expects to be valid but is NULL.

How developers prevent this class of flaw

  • For any pointers that could have been modified or provided from a function that can return NULL, check the pointer for NULL before use. When working with a multithreaded or otherwise asynchronous environment, ensure that proper locking APIs are used to lock before the check, and unlock when it has finished.
  • Select a programming language that is not susceptible to these issues.
  • Check the results of all functions that return a value and verify that the value is non-null before acting upon it.

More NULL Pointer Dereference vulnerabilities (CWE-476)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent NULL Pointer Dereference vulnerabilities

Spotted an error? Tell us.