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

ALSA: mixer: oss: Add card disconnect checkpoints

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 21 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 21 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 21 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.85-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.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.6.19.6-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.6-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 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.

1 current
CVE-2026-43126 · CSAF 2.0 · revision 24 · interimSUSE Product Security TeamCVE-2026-43126
128 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • 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
Summary
In the Linux kernel, the following vulnerability has been resolved: ALSA: mixer: oss: Add card disconnect checkpoints ALSA OSS mixer layer calls the kcontrol ops rather individually, and pending calls might be not always caught at disconnecting the device. For avoiding the potential UAF scenarios, add sanity checks of the card disconnection at each entry point of OSS mixer accesses. The rwsem is taken just before that check, hence the rest context should be covered by that properly.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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-27687

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 21 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: mixer: oss: Add card disconnect checkpoints ALSA OSS mixer layer calls the kcontrol ops rather individually, and pending calls might be not always caught at disconnecting the device. For avoiding the potential UAF scenarios, add sanity checks of the card disconnection at each entry point of OSS mixer accesses. The rwsem is taken just before that check, hence the rest context should be covered by that properly.

What

In the Linux kernel, the following vulnerability has been resolved: ALSA: mixer: oss: Add card disconnect checkpoints ALSA OSS mixer layer calls the kcontrol ops rather individually, and pending calls might be not always caught at disconnecting the device. For avoiding the potential UAF scenarios, add sanity checks of the card disconnection at each entry point of OSS mixer accesses. The rwsem is taken just before that check, hence the rest context should be covered by that properly.

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: mixer: oss: Add card disconnect checkpoints ALSA OSS mixer layer calls the kcontrol ops rather individually, and pending calls might be not always caught at disconnecting the device. For avoiding the potential UAF scenarios, add sanity checks of the card disconnection at each entry point of OSS mixer accesses. The rwsem is taken just before that check, hence the rest context should be covered by that properly.

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-1405Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht spezifizierte Angriffe durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1203Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-31668 Référence CVE CVE-2026-31771 https://www.cve.org/CVERecord?id=CVE-2026-31771 Référence CVE CVE-2026-43009 https://www.cve.org/CVERecord?id=CVE-2026-43009 Référence CVE CVE-2026-43029 https://www.cve.org/CVERecord?id=CVE-2026-43029 Référence CVE CVE-2026-43042 https://www.cve.org/CVERecord?id=CVE-2026-43042 Référence CVE CVE-2026-43048 https://www.cve.org/CVERecord?id=CVE-2026-43048 Référence CVE CVE-2026-43071 https://www.cve.org/CVERecord?id=CVE-2026-43071 Référence CVE CVE-2026-43101 https://www.cve.org/CVERecord?id=CVE-2026-43101 Référence CVE CVE-2026-43116 https://www.cve.org/CVERecord?id=CVE-2026-43116 Référence CVE CVE-2026-43126 https://www.cve.org/CVERecord?id=CVE-2026-43126 Référence CVE CVE-2026-43172 https://www.cve.org/CVERecord?id=CVE-2026-43172 Référence CVE CVE-2026-43198 https://www.cve.org/CVERecord?id=CVE-2026-43198 Référence CVE CVE-2026-43213 https://www.cve.org/CVERecord?id=CVE-2026-43213 Référence CVE CVE-2026-43263 https://www.cve.org/CVERecord?id=CVE-2026-43263 Référence CVE CVE-2026-43303 https://www.cve.org/CVERecord?id=CVE-2026-43303 Référence CVE CVE-2026-43352 https://www.cve.org/CVERecord?id=CVE-2026-43352 Référence CVE CVE-2026-43353 https://www.cve.org/CVERecord?id=CVE-2026-43353 Référence CVE CVE-2026-43464 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43108 Référence CVE CVE-2026-43110 https://www.cve.org/CVERecord?id=CVE-2026-43110 Référence CVE CVE-2026-43111 https://www.cve.org/CVERecord?id=CVE-2026-43111 Référence CVE CVE-2026-43113 https://www.cve.org/CVERecord?id=CVE-2026-43113 Référence CVE CVE-2026-43114 https://www.cve.org/CVERecord?id=CVE-2026-43114 Référence CVE CVE-2026-43117 https://www.cve.org/CVERecord?id=CVE-2026-43117 Référence CVE CVE-2026-43118 https://www.cve.org/CVERecord?id=CVE-2026-43118 Référence CVE CVE-2026-43120 https://www.cve.org/CVERecord?id=CVE-2026-43120 Référence CVE CVE-2026-43123 https://www.cve.org/CVERecord?id=CVE-2026-43123 Référence CVE CVE-2026-43126 https://www.cve.org/CVERecord?id=CVE-2026-43126 Référence CVE CVE-2026-43129 https://www.cve.org/CVERecord?id=CVE-2026-43129 Référence CVE CVE-2026-43133 https://www.cve.org/CVERecord?id=CVE-2026-43133 Référence CVE CVE-2026-43134 https://www.cve.org/CVERecord?id=CVE-2026-43134 Référence CVE CVE-2026-43135 https://www.cve.org/CVERecord?id=CVE-2026-43135 Référence CVE CVE-2026-43136 https://www.cve.org/CVERecord?id=CVE-2026-43136 Référence CVE CVE-2026-43137 https://www.cve.org/CVERecord?id=CVE-2026-43137 Référence CVE CVE-2026-43138 https://www.cve.org/CVERecord?id=CVE-2026-43138 Référence CVE CVE-2026-43140 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31729 Référence CVE CVE-2026-31736 https://www.cve.org/CVERecord?id=CVE-2026-31736 Référence CVE CVE-2026-31758 https://www.cve.org/CVERecord?id=CVE-2026-31758 Référence CVE CVE-2026-43009 https://www.cve.org/CVERecord?id=CVE-2026-43009 Référence CVE CVE-2026-43012 https://www.cve.org/CVERecord?id=CVE-2026-43012 Référence CVE CVE-2026-43013 https://www.cve.org/CVERecord?id=CVE-2026-43013 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43054 https://www.cve.org/CVERecord?id=CVE-2026-43054 Référence CVE CVE-2026-43112 https://www.cve.org/CVERecord?id=CVE-2026-43112 Référence CVE CVE-2026-43126 https://www.cve.org/CVERecord?id=CVE-2026-43126 Référence CVE CVE-2026-43190 https://www.cve.org/CVERecord?id=CVE-2026-43190 Référence CVE CVE-2026-43206 https://www.cve.org/CVERecord?id=CVE-2026-43206 Référence CVE CVE-2026-43234 https://www.cve.org/CVERecord?id=CVE-2026-43234 Référence CVE CVE-2026-43252 https://www.cve.org/CVERecord?id=CVE-2026-43252 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43325 https://www.cve.org/CVERecord?id=CVE-2026-43325 Référence CVE CVE-2026-43328 https://www.cve.org/CVERecord?id=CVE-2026-43328 Référence CVE CVE-2026-43333 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43038 Référence CVE CVE-2026-43044 https://www.cve.org/CVERecord?id=CVE-2026-43044 Référence CVE CVE-2026-43045 https://www.cve.org/CVERecord?id=CVE-2026-43045 Référence CVE CVE-2026-43050 https://www.cve.org/CVERecord?id=CVE-2026-43050 Référence CVE CVE-2026-43060 https://www.cve.org/CVERecord?id=CVE-2026-43060 Référence CVE CVE-2026-43082 https://www.cve.org/CVERecord?id=CVE-2026-43082 Référence CVE CVE-2026-43088 https://www.cve.org/CVERecord?id=CVE-2026-43088 Référence CVE CVE-2026-43110 https://www.cve.org/CVERecord?id=CVE-2026-43110 Référence CVE CVE-2026-43120 https://www.cve.org/CVERecord?id=CVE-2026-43120 Référence CVE CVE-2026-43126 https://www.cve.org/CVERecord?id=CVE-2026-43126 Référence CVE CVE-2026-43153 https://www.cve.org/CVERecord?id=CVE-2026-43153 Référence CVE CVE-2026-43190 https://www.cve.org/CVERecord?id=CVE-2026-43190 Référence CVE CVE-2026-43214 https://www.cve.org/CVERecord?id=CVE-2026-43214 Référence CVE CVE-2026-43265 https://www.cve.org/CVERecord?id=CVE-2026-43265 Référence CVE CVE-2026-43329 https://www.cve.org/CVERecord?id=CVE-2026-43329 Référence CVE CVE-2026-43330 https://www.cve.org/CVERecord?id=CVE-2026-43330 Référence CVE CVE-2026-43334 https://www.cve.org/CVERecord?id=CVE-2026-43334 Référence CVE CVE-2026-43365 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31675 Référence CVE CVE-2026-31681 https://www.cve.org/CVERecord?id=CVE-2026-31681 Référence CVE CVE-2026-31685 https://www.cve.org/CVERecord?id=CVE-2026-31685 Référence CVE CVE-2026-31700 https://www.cve.org/CVERecord?id=CVE-2026-31700 Référence CVE CVE-2026-31738 https://www.cve.org/CVERecord?id=CVE-2026-31738 Référence CVE CVE-2026-31787 https://www.cve.org/CVERecord?id=CVE-2026-31787 Référence CVE CVE-2026-43025 https://www.cve.org/CVERecord?id=CVE-2026-43025 Référence CVE CVE-2026-43088 https://www.cve.org/CVERecord?id=CVE-2026-43088 Référence CVE CVE-2026-43110 https://www.cve.org/CVERecord?id=CVE-2026-43110 Référence CVE CVE-2026-43126 https://www.cve.org/CVERecord?id=CVE-2026-43126 Référence CVE CVE-2026-43190 https://www.cve.org/CVERecord?id=CVE-2026-43190 Référence CVE CVE-2026-43255 https://www.cve.org/CVERecord?id=CVE-2026-43255 Référence CVE CVE-2026-43264 https://www.cve.org/CVERecord?id=CVE-2026-43264 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43334 https://www.cve.org/CVERecord?id=CVE-2026-43334 Référence CVE CVE-2026-43437 https://www.cve.org/CVERecord?id=CVE-2026-43437 Référence CVE CVE-2026-46333 https://www.cve.org/CVERecord?id=CVE-2026-46333 Gestion détaillée du document le 29 mai 2026 Version initiale

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-014960LinuxのLinux Kernelにおける不特定の脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。ALSAミキサーのOSSカード切断に関するチェックポイントが追加されました。ALSA OSSミキサーレイヤーはkcontrol opsを個別に呼び出すため、デバイス切断時に保留中の呼び出しが常に検出されるわけではありません。この問題を解決するために、潜在的なUse-After-Free(UAF)シナリオを回避するために、OSSミキサーアクセスの各エントリーポイントでカード切断の整合性チェックを追加しました。rwsemはそのチェック直前に取得されるため、それ以降のコンテキストは適切にカバーされるはずです。

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.12.75 ≤ 6.12.*, 6.18.16 ≤ 6.18.*, 6.19.6 ≤ 6.19.*, 7.0 ≤ *
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 6 May 2026 · Last source change 5 Aug 2026, 12:26 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-27687
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD enriched

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 ↗

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-43126 · cve.blacktree.nl