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

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

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 204 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.18% 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 204 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 5 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).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.0.12-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-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-64134 · CSAF 2.0 · revision 7 · interimSUSE Product Security TeamCVE-2026-64134
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: 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.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-64134 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: ALSA: pcm: Don't setup bogus iov_iter for silencing
184 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) Pulse Code Modulation (PCM) subsystem. During PCM data transfer, an incorrect setup of the `iov_iter` for silencing (when data is null) could lead to a NULL pointer dereference. This vulnerability can be triggered by a local user, potentially causing a system crash (Denial of Service).
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-45819

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

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: 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.

What

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.

Why

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

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: 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.

Why

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

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 → NULL Pointer Dereference → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-476 ↗

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-476
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-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 https://www.cve.org/CVERecord?id=CVE-2026-64127 Référence CVE CVE-2026-64128 https://www.cve.org/CVERecord?id=CVE-2026-64128 Référence CVE CVE-2026-64129 https://www.cve.org/CVERecord?id=CVE-2026-64129 Référence CVE CVE-2026-64130 https://www.cve.org/CVERecord?id=CVE-2026-64130 Référence CVE CVE-2026-64131 https://www.cve.org/CVERecord?id=CVE-2026-64131 Référence CVE CVE-2026-64132 https://www.cve.org/CVERecord?id=CVE-2026-64132 Référence CVE CVE-2026-64133 https://www.cve.org/CVERecord?id=CVE-2026-64133 Référence CVE CVE-2026-64134 https://www.cve.org/CVERecord?id=CVE-2026-64134 Référence CVE CVE-2026-64135 https://www.cve.org/CVERecord?id=CVE-2026-64135 Référence CVE CVE-2026-64136 https://www.cve.org/CVERecord?id=CVE-2026-64136 Référence CVE CVE-2026-64137 https://www.cve.org/CVERecord?id=CVE-2026-64137 Référence CVE CVE-2026-64138 https://www.cve.org/CVERecord?id=CVE-2026-64138 Référence CVE CVE-2026-64139 https://www.cve.org/CVERecord?id=CVE-2026-64139 Référence CVE CVE-2026-64140 https://www.cve.org/CVERecord?id=CVE-2026-64140 Référence CVE CVE-2026-64141 https://www.cve.org/CVERecord?id=CVE-2026-64141 Référence CVE CVE-2026-64142 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-64118 Référence CVE CVE-2026-64119 https://www.cve.org/CVERecord?id=CVE-2026-64119 Référence CVE CVE-2026-64121 https://www.cve.org/CVERecord?id=CVE-2026-64121 Référence CVE CVE-2026-64125 https://www.cve.org/CVERecord?id=CVE-2026-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 https://www.cve.org/CVERecord?id=CVE-2026-64127 Référence CVE CVE-2026-64128 https://www.cve.org/CVERecord?id=CVE-2026-64128 Référence CVE CVE-2026-64131 https://www.cve.org/CVERecord?id=CVE-2026-64131 Référence CVE CVE-2026-64133 https://www.cve.org/CVERecord?id=CVE-2026-64133 Référence CVE CVE-2026-64134 https://www.cve.org/CVERecord?id=CVE-2026-64134 Référence CVE CVE-2026-64135 https://www.cve.org/CVERecord?id=CVE-2026-64135 Référence CVE CVE-2026-64137 https://www.cve.org/CVERecord?id=CVE-2026-64137 Référence CVE CVE-2026-64144 https://www.cve.org/CVERecord?id=CVE-2026-64144 Référence CVE CVE-2026-64146 https://www.cve.org/CVERecord?id=CVE-2026-64146 Référence CVE CVE-2026-64147 https://www.cve.org/CVERecord?id=CVE-2026-64147 Référence CVE CVE-2026-64148 https://www.cve.org/CVERecord?id=CVE-2026-64148 Référence CVE CVE-2026-64155 https://www.cve.org/CVERecord?id=CVE-2026-64155 Référence CVE CVE-2026-64162 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-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 https://www.cve.org/CVERecord?id=CVE-2026-64127 Référence CVE CVE-2026-64128 https://www.cve.org/CVERecord?id=CVE-2026-64128 Référence CVE CVE-2026-64129 https://www.cve.org/CVERecord?id=CVE-2026-64129 Référence CVE CVE-2026-64130 https://www.cve.org/CVERecord?id=CVE-2026-64130 Référence CVE CVE-2026-64131 https://www.cve.org/CVERecord?id=CVE-2026-64131 Référence CVE CVE-2026-64132 https://www.cve.org/CVERecord?id=CVE-2026-64132 Référence CVE CVE-2026-64133 https://www.cve.org/CVERecord?id=CVE-2026-64133 Référence CVE CVE-2026-64134 https://www.cve.org/CVERecord?id=CVE-2026-64134 Référence CVE CVE-2026-64135 https://www.cve.org/CVERecord?id=CVE-2026-64135 Référence CVE CVE-2026-64136 https://www.cve.org/CVERecord?id=CVE-2026-64136 Référence CVE CVE-2026-64137 https://www.cve.org/CVERecord?id=CVE-2026-64137 Référence CVE CVE-2026-64138 https://www.cve.org/CVERecord?id=CVE-2026-64138 Référence CVE CVE-2026-64139 https://www.cve.org/CVERecord?id=CVE-2026-64139 Référence CVE CVE-2026-64140 https://www.cve.org/CVERecord?id=CVE-2026-64140 Référence CVE CVE-2026-64141 https://www.cve.org/CVERecord?id=CVE-2026-64141 Référence CVE CVE-2026-64142 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-64115 Référence CVE CVE-2026-64118 https://www.cve.org/CVERecord?id=CVE-2026-64118 Référence CVE CVE-2026-64121 https://www.cve.org/CVERecord?id=CVE-2026-64121 Référence CVE CVE-2026-64125 https://www.cve.org/CVERecord?id=CVE-2026-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 https://www.cve.org/CVERecord?id=CVE-2026-64127 Référence CVE CVE-2026-64128 https://www.cve.org/CVERecord?id=CVE-2026-64128 Référence CVE CVE-2026-64131 https://www.cve.org/CVERecord?id=CVE-2026-64131 Référence CVE CVE-2026-64133 https://www.cve.org/CVERecord?id=CVE-2026-64133 Référence CVE CVE-2026-64134 https://www.cve.org/CVERecord?id=CVE-2026-64134 Référence CVE CVE-2026-64135 https://www.cve.org/CVERecord?id=CVE-2026-64135 Référence CVE CVE-2026-64136 https://www.cve.org/CVERecord?id=CVE-2026-64136 Référence CVE CVE-2026-64137 https://www.cve.org/CVERecord?id=CVE-2026-64137 Référence CVE CVE-2026-64144 https://www.cve.org/CVERecord?id=CVE-2026-64144 Référence CVE CVE-2026-64146 https://www.cve.org/CVERecord?id=CVE-2026-64146 Référence CVE CVE-2026-64148 https://www.cve.org/CVERecord?id=CVE-2026-64148 Référence CVE CVE-2026-64155 https://www.cve.org/CVERecord?id=CVE-2026-64155 Référence CVE CVE-2026-64164 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-64116 Référence CVE CVE-2026-64117 https://www.cve.org/CVERecord?id=CVE-2026-64117 Référence CVE CVE-2026-64118 https://www.cve.org/CVERecord?id=CVE-2026-64118 Référence CVE CVE-2026-64121 https://www.cve.org/CVERecord?id=CVE-2026-64121 Référence CVE CVE-2026-64125 https://www.cve.org/CVERecord?id=CVE-2026-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 https://www.cve.org/CVERecord?id=CVE-2026-64127 Référence CVE CVE-2026-64128 https://www.cve.org/CVERecord?id=CVE-2026-64128 Référence CVE CVE-2026-64133 https://www.cve.org/CVERecord?id=CVE-2026-64133 Référence CVE CVE-2026-64134 https://www.cve.org/CVERecord?id=CVE-2026-64134 Référence CVE CVE-2026-64135 https://www.cve.org/CVERecord?id=CVE-2026-64135 Référence CVE CVE-2026-64136 https://www.cve.org/CVERecord?id=CVE-2026-64136 Référence CVE CVE-2026-64137 https://www.cve.org/CVERecord?id=CVE-2026-64137 Référence CVE CVE-2026-64138 https://www.cve.org/CVERecord?id=CVE-2026-64138 Référence CVE CVE-2026-64144 https://www.cve.org/CVERecord?id=CVE-2026-64144 Référence CVE CVE-2026-64147 https://www.cve.org/CVERecord?id=CVE-2026-64147 Référence CVE CVE-2026-64148 https://www.cve.org/CVERecord?id=CVE-2026-64148 Référence CVE CVE-2026-64153 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-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 https://www.cve.org/CVERecord?id=CVE-2026-64127 Référence CVE CVE-2026-64128 https://www.cve.org/CVERecord?id=CVE-2026-64128 Référence CVE CVE-2026-64129 https://www.cve.org/CVERecord?id=CVE-2026-64129 Référence CVE CVE-2026-64130 https://www.cve.org/CVERecord?id=CVE-2026-64130 Référence CVE CVE-2026-64131 https://www.cve.org/CVERecord?id=CVE-2026-64131 Référence CVE CVE-2026-64132 https://www.cve.org/CVERecord?id=CVE-2026-64132 Référence CVE CVE-2026-64133 https://www.cve.org/CVERecord?id=CVE-2026-64133 Référence CVE CVE-2026-64134 https://www.cve.org/CVERecord?id=CVE-2026-64134 Référence CVE CVE-2026-64135 https://www.cve.org/CVERecord?id=CVE-2026-64135 Référence CVE CVE-2026-64136 https://www.cve.org/CVERecord?id=CVE-2026-64136 Référence CVE CVE-2026-64137 https://www.cve.org/CVERecord?id=CVE-2026-64137 Référence CVE CVE-2026-64138 https://www.cve.org/CVERecord?id=CVE-2026-64138 Référence CVE CVE-2026-64139 https://www.cve.org/CVERecord?id=CVE-2026-64139 Référence CVE CVE-2026-64140 https://www.cve.org/CVERecord?id=CVE-2026-64140 Référence CVE CVE-2026-64141 https://www.cve.org/CVERecord?id=CVE-2026-64141 Référence CVE CVE-2026-64142 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-64115 Référence CVE CVE-2026-64118 https://www.cve.org/CVERecord?id=CVE-2026-64118 Référence CVE CVE-2026-64121 https://www.cve.org/CVERecord?id=CVE-2026-64121 Référence CVE CVE-2026-64125 https://www.cve.org/CVERecord?id=CVE-2026-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 https://www.cve.org/CVERecord?id=CVE-2026-64127 Référence CVE CVE-2026-64128 https://www.cve.org/CVERecord?id=CVE-2026-64128 Référence CVE CVE-2026-64131 https://www.cve.org/CVERecord?id=CVE-2026-64131 Référence CVE CVE-2026-64133 https://www.cve.org/CVERecord?id=CVE-2026-64133 Référence CVE CVE-2026-64134 https://www.cve.org/CVERecord?id=CVE-2026-64134 Référence CVE CVE-2026-64135 https://www.cve.org/CVERecord?id=CVE-2026-64135 Référence CVE CVE-2026-64136 https://www.cve.org/CVERecord?id=CVE-2026-64136 Référence CVE CVE-2026-64137 https://www.cve.org/CVERecord?id=CVE-2026-64137 Référence CVE CVE-2026-64144 https://www.cve.org/CVERecord?id=CVE-2026-64144 Référence CVE CVE-2026-64146 https://www.cve.org/CVERecord?id=CVE-2026-64146 Référence CVE CVE-2026-64148 https://www.cve.org/CVERecord?id=CVE-2026-64148 Référence CVE CVE-2026-64155 https://www.cve.org/CVERecord?id=CVE-2026-64155 Référence CVE CVE-2026-64164 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-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 https://www.cve.org/CVERecord?id=CVE-2026-64127 Référence CVE CVE-2026-64128 https://www.cve.org/CVERecord?id=CVE-2026-64128 Référence CVE CVE-2026-64129 https://www.cve.org/CVERecord?id=CVE-2026-64129 Référence CVE CVE-2026-64130 https://www.cve.org/CVERecord?id=CVE-2026-64130 Référence CVE CVE-2026-64131 https://www.cve.org/CVERecord?id=CVE-2026-64131 Référence CVE CVE-2026-64132 https://www.cve.org/CVERecord?id=CVE-2026-64132 Référence CVE CVE-2026-64133 https://www.cve.org/CVERecord?id=CVE-2026-64133 Référence CVE CVE-2026-64134 https://www.cve.org/CVERecord?id=CVE-2026-64134 Référence CVE CVE-2026-64135 https://www.cve.org/CVERecord?id=CVE-2026-64135 Référence CVE CVE-2026-64136 https://www.cve.org/CVERecord?id=CVE-2026-64136 Référence CVE CVE-2026-64137 https://www.cve.org/CVERecord?id=CVE-2026-64137 Référence CVE CVE-2026-64138 https://www.cve.org/CVERecord?id=CVE-2026-64138 Référence CVE CVE-2026-64139 https://www.cve.org/CVERecord?id=CVE-2026-64139 Référence CVE CVE-2026-64140 https://www.cve.org/CVERecord?id=CVE-2026-64140 Référence CVE CVE-2026-64141 https://www.cve.org/CVERecord?id=CVE-2026-64141 Référence CVE CVE-2026-64142 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-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 https://www.cve.org/CVERecord?id=CVE-2026-64127 Référence CVE CVE-2026-64128 https://www.cve.org/CVERecord?id=CVE-2026-64128 Référence CVE CVE-2026-64129 https://www.cve.org/CVERecord?id=CVE-2026-64129 Référence CVE CVE-2026-64130 https://www.cve.org/CVERecord?id=CVE-2026-64130 Référence CVE CVE-2026-64131 https://www.cve.org/CVERecord?id=CVE-2026-64131 Référence CVE CVE-2026-64132 https://www.cve.org/CVERecord?id=CVE-2026-64132 Référence CVE CVE-2026-64133 https://www.cve.org/CVERecord?id=CVE-2026-64133 Référence CVE CVE-2026-64134 https://www.cve.org/CVERecord?id=CVE-2026-64134 Référence CVE CVE-2026-64135 https://www.cve.org/CVERecord?id=CVE-2026-64135 Référence CVE CVE-2026-64136 https://www.cve.org/CVERecord?id=CVE-2026-64136 Référence CVE CVE-2026-64137 https://www.cve.org/CVERecord?id=CVE-2026-64137 Référence CVE CVE-2026-64138 https://www.cve.org/CVERecord?id=CVE-2026-64138 Référence CVE CVE-2026-64139 https://www.cve.org/CVERecord?id=CVE-2026-64139 Référence CVE CVE-2026-64140 https://www.cve.org/CVERecord?id=CVE-2026-64140 Référence CVE CVE-2026-64141 https://www.cve.org/CVERecord?id=CVE-2026-64141 Référence CVE CVE-2026-64142 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-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 https://www.cve.org/CVERecord?id=CVE-2026-64127 Référence CVE CVE-2026-64128 https://www.cve.org/CVERecord?id=CVE-2026-64128 Référence CVE CVE-2026-64129 https://www.cve.org/CVERecord?id=CVE-2026-64129 Référence CVE CVE-2026-64130 https://www.cve.org/CVERecord?id=CVE-2026-64130 Référence CVE CVE-2026-64131 https://www.cve.org/CVERecord?id=CVE-2026-64131 Référence CVE CVE-2026-64132 https://www.cve.org/CVERecord?id=CVE-2026-64132 Référence CVE CVE-2026-64133 https://www.cve.org/CVERecord?id=CVE-2026-64133 Référence CVE CVE-2026-64134 https://www.cve.org/CVERecord?id=CVE-2026-64134 Référence CVE CVE-2026-64135 https://www.cve.org/CVERecord?id=CVE-2026-64135 Référence CVE CVE-2026-64136 https://www.cve.org/CVERecord?id=CVE-2026-64136 Référence CVE CVE-2026-64137 https://www.cve.org/CVERecord?id=CVE-2026-64137 Référence CVE CVE-2026-64138 https://www.cve.org/CVERecord?id=CVE-2026-64138 Référence CVE CVE-2026-64139 https://www.cve.org/CVERecord?id=CVE-2026-64139 Référence CVE CVE-2026-64140 https://www.cve.org/CVERecord?id=CVE-2026-64140 Référence CVE CVE-2026-64141 https://www.cve.org/CVERecord?id=CVE-2026-64141 Référence CVE CVE-2026-64142 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-028273LinuxのLinux KernelにおけるNULL ポインタデリファレンスに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。ALSAのpcmにおいて、サイレンシング時に不正なiov_iterを設定しないように修正が行われました。PCMデータ転送のためのiov_iterへの移行時に、サイレンシング(データがNULLの場合)であっても無条件にiov_iterの設定を適用しており、不正なiov_iterの計算を引き起こしていました。幸い、多くのアーキテクチャでは問題が発生しませんでしたが、RISC-Vではこの問題が発生し、NULL参照が起きていました。この不具合に対処するため、interleaved_copy()関数でNULLデータの場合を適切に処理し、サイレンシングのケースを正しく扱うようにしました。noninterleaved_copy()関数では既にNULLデータの処理が実装されていたため、変更は必要ありませんでした。

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.6, 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:39 UTC · CWE-476 · NULL Pointer Dereference

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-45819
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-64134 · cve.blacktree.nl