BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-40097High confidence

ALSA: hda: Fix missing pointer check in hda_component_manager_init function

Linux · Linux

…UnscoredAssess manually
Recommended action
Patch only the product branches with a verified fix

No CVSS base score is available from the CNA, CISA ADP or NIST. Absence of a score is not evidence of low risk; review the vendor advisory, affected exposure and exploit evidence. 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 severityUnscoredOperational priority:Needs assessment, manual assessment needed.unscored

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.20% 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: Manual assessmentRemediation target: Manual assessment

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.63-1Debian 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.6.17.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.17.6-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.

1 current
CVE-2025-40097 · CSAF 2.0 · revision 35 · interimSUSE Product Security TeamCVE-2025-40097
192 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
Summary
In the Linux kernel, the following vulnerability has been resolved: ALSA: hda: Fix missing pointer check in hda_component_manager_init function The __component_match_add function may assign the 'matchptr' pointer the value ERR_PTR(-ENOMEM), which will subsequently be dereferenced. The call stack leading to the error looks like this: hda_component_manager_init |-> component_match_add |-> component_match_add_release |-> __component_match_add ( ... ,**matchptr, ... ) |-> *matchptr = ERR_PTR(-ENOMEM); // assign |-> component_master_add_with_match( ... match) |-> component_match_realloc(match, match->num); // dereference Add IS_ERR() check to prevent the crash. Found by Linux Verification Center (linuxtesting.org) with SVACE.
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-2025-36981

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: ALSA: hda: Fix missing pointer check in hda_component_manager_init function The __component_match_add function may assign the 'matchptr' pointer the value ERR_PTR(-ENOMEM), which will subsequently be dereferenced. The call stack leading to the error looks like this: hda_component_manager_init |-> component_match_add |-> component_match_add_release |-> __component_match_add ( ... ,**matchptr, ... ) |-> *matchptr = ERR_PTR(-ENOMEM); // assign |-> component_master_add_with_match( ... match) |-> component_match_realloc(match, match->num); // dereference Add IS_ERR() check to prevent the crash. Found by Linux Verification Center (linuxtesting.org) with SVACE.

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
0.0
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

No CVSS base score is available from the CNA, CISA ADP or NIST. Absence of a score is not evidence of low risk; review the vendor advisory, affected exposure and exploit evidence. 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: hda: Fix missing pointer check in hda_component_manager_init function The __component_match_add function may assign the 'matchptr' pointer the value ERR_PTR(-ENOMEM), which will subsequently be dereferenced. The call stack leading to the error looks like this: hda_component_manager_init |-> component_match_add |-> component_match_add_release |-> __component_match_add ( ... ,**matchptr, ... ) |-> *matchptr = ERR_PTR(-ENOMEM); // assign |-> component_master_add_with_match( ... match) |-> component_match_realloc(match, match->num); // dereference Add IS_ERR() check to prevent the crash. Found by Linux Verification Center (linuxtesting.org) with SVACE.

What

In the Linux kernel, the following vulnerability has been resolved: ALSA: hda: Fix missing pointer check in hda_component_manager_init function The __component_match_add function may assign the 'matchptr' pointer the value ERR_PTR(-ENOMEM), which will subsequently be dereferenced. The call stack leading to the error looks like this: hda_component_manager_init |-> component_match_add |-> component_match_add_release |-> __component_match_add ( ... ,**matchptr, ... ) |-> *matchptr = ERR_PTR(-ENOMEM); // assign |-> component_master_add_with_match( ... match) |-> component_match_realloc(match, match->num); // dereference Add IS_ERR() check to prevent the crash. Found by Linux Verification Center (linuxtesting.org) with SVACE.

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 the affected interface may attempt exploitation when the stated preconditions are met. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: ALSA: hda: Fix missing pointer check in hda_component_manager_init function The __component_match_add function may assign the 'matchptr' pointer the value ERR_PTR(-ENOMEM), which will subsequently be dereferenced. The call stack leading to the error looks like this: hda_component_manager_init |-> component_match_add |-> component_match_add_release |-> __component_match_add ( ... ,**matchptr, ... ) |-> *matchptr = ERR_PTR(-ENOMEM); // assign |-> component_master_add_with_match( ... match) |-> component_match_realloc(match, match->num); // dereference Add IS_ERR() check to prevent the crash. Found by Linux Verification Center (linuxtesting.org) with SVACE.

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 the affected interface may attempt exploitation when the stated preconditions are met. If successful, the issue may disrupt the affected service.

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
the affected interface → vulnerable operation → disrupt the affected service
Attack surface
Unspecified
Privileges required
Not stated in the selected CVSS metric
User interaction
Not stated in the selected CVSS metric
Attack complexity
Not stated in the selected CVSS metric
Security boundary
Not stated in the selected CVSS metric
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.
Not available from the selected scoring authority.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
Denial of service
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2025-36981Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: ALSA: hda: Fix missing pointer check in hda_component_manager_init function The __component_match_add function may assign the 'matchptr' pointer the value ERR_PTR(-ENOMEM), which will subsequently be dereferenced. The call stack leading to the error looks like this: hda_component_manager_init |-> component_match_add |-> component_match_add_release |-> __component_match_add ( ... ,**matchptr, ... ) |-> *matchptr = ERR_PTR(-ENOMEM); // assign |-> component_master_add_with_match( ... match) |-> component_match_realloc(match, match->num); // dereference Add IS_ERR() check to prevent the crash. Found by Linux Verification Center (linuxtesting.org) with SVACE.

Official EUVD record ↗
BSI · German · WID-SEC-2025-2450Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service-Situation führen oder eine Speicherbeschädigung verursachen können.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20251105Security Bulletin 05 Nov 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 05 Nov 2025, published on 5 November 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2025-39964 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=CVE-2025-39977 Référence CVE CVE-2025-39998 https://www.cve.org/CVERecord?id=CVE-2025-39998 Référence CVE CVE-2025-40006 https://www.cve.org/CVERecord?id=CVE-2025-40006 Référence CVE CVE-2025-40024 https://www.cve.org/CVERecord?id=CVE-2025-40024 Référence CVE CVE-2025-40033 https://www.cve.org/CVERecord?id=CVE-2025-40033 Référence CVE CVE-2025-40042 https://www.cve.org/CVERecord?id=CVE-2025-40042 Référence CVE CVE-2025-40053 https://www.cve.org/CVERecord?id=CVE-2025-40053 Référence CVE CVE-2025-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40097 https://www.cve.org/CVERecord?id=CVE-2025-40097 Référence CVE CVE-2025-40099 https://www.cve.org/CVERecord?id=CVE-2025-40099 Référence CVE CVE-2025-40102 https://www.cve.org/CVERecord?id=CVE-2025-40102 Référence CVE CVE-2025-40103 https://www.cve.org/CVERecord?id=CVE-2025-40103 Référence CVE CVE-2025-40106 https://www.cve.org/CVERecord?id=CVE-2025-40106 Référence CVE CVE-2025-40123 https://www.cve.org/CVERecord?id=CVE-2025-40123 Référence CVE CVE-2025-40134 https://www.cve.org/CVERecord?id=CVE-2025-40134 Référence CVE CVE-2025-40135 https://www.cve.org/CVERecord?id=CVE-2025-40135 Référence CVE CVE-2025-40153 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-40074 Référence CVE CVE-2025-40075 https://www.cve.org/CVERecord?id=CVE-2025-40075 Référence CVE CVE-2025-40077 https://www.cve.org/CVERecord?id=CVE-2025-40077 Référence CVE CVE-2025-40080 https://www.cve.org/CVERecord?id=CVE-2025-40080 Référence CVE CVE-2025-40082 https://www.cve.org/CVERecord?id=CVE-2025-40082 Référence CVE CVE-2025-40083 https://www.cve.org/CVERecord?id=CVE-2025-40083 Référence CVE CVE-2025-40084 https://www.cve.org/CVERecord?id=CVE-2025-40084 Référence CVE CVE-2025-40093 https://www.cve.org/CVERecord?id=CVE-2025-40093 Référence CVE CVE-2025-40095 https://www.cve.org/CVERecord?id=CVE-2025-40095 Référence CVE CVE-2025-40097 https://www.cve.org/CVERecord?id=CVE-2025-40097 Référence CVE CVE-2025-40099 https://www.cve.org/CVERecord?id=CVE-2025-40099 Référence CVE CVE-2025-40100 https://www.cve.org/CVERecord?id=CVE-2025-40100 Référence CVE CVE-2025-40102 https://www.cve.org/CVERecord?id=CVE-2025-40102 Référence CVE CVE-2025-40103 https://www.cve.org/CVERecord?id=CVE-2025-40103 Référence CVE CVE-2025-40104 https://www.cve.org/CVERecord?id=CVE-2025-40104 Référence CVE CVE-2025-40107 https://www.cve.org/CVERecord?id=CVE-2025-40107 Référence CVE CVE-2025-40110 https://www.cve.org/CVERecord?id=CVE-2025-40110 Référence CVE CVE-2025-40123 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-40074 Référence CVE CVE-2025-40075 https://www.cve.org/CVERecord?id=CVE-2025-40075 Référence CVE CVE-2025-40077 https://www.cve.org/CVERecord?id=CVE-2025-40077 Référence CVE CVE-2025-40080 https://www.cve.org/CVERecord?id=CVE-2025-40080 Référence CVE CVE-2025-40082 https://www.cve.org/CVERecord?id=CVE-2025-40082 Référence CVE CVE-2025-40083 https://www.cve.org/CVERecord?id=CVE-2025-40083 Référence CVE CVE-2025-40084 https://www.cve.org/CVERecord?id=CVE-2025-40084 Référence CVE CVE-2025-40093 https://www.cve.org/CVERecord?id=CVE-2025-40093 Référence CVE CVE-2025-40095 https://www.cve.org/CVERecord?id=CVE-2025-40095 Référence CVE CVE-2025-40097 https://www.cve.org/CVERecord?id=CVE-2025-40097 Référence CVE CVE-2025-40099 https://www.cve.org/CVERecord?id=CVE-2025-40099 Référence CVE CVE-2025-40100 https://www.cve.org/CVERecord?id=CVE-2025-40100 Référence CVE CVE-2025-40102 https://www.cve.org/CVERecord?id=CVE-2025-40102 Référence CVE CVE-2025-40103 https://www.cve.org/CVERecord?id=CVE-2025-40103 Référence CVE CVE-2025-40104 https://www.cve.org/CVERecord?id=CVE-2025-40104 Référence CVE CVE-2025-40107 https://www.cve.org/CVERecord?id=CVE-2025-40107 Référence CVE CVE-2025-40110 https://www.cve.org/CVERecord?id=CVE-2025-40110 Référence CVE CVE-2025-40123 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40053 Référence CVE CVE-2025-40055 https://www.cve.org/CVERecord?id=CVE-2025-40055 Référence CVE CVE-2025-40059 https://www.cve.org/CVERecord?id=CVE-2025-40059 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40074 https://www.cve.org/CVERecord?id=CVE-2025-40074 Référence CVE CVE-2025-40075 https://www.cve.org/CVERecord?id=CVE-2025-40075 Référence CVE CVE-2025-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40083 https://www.cve.org/CVERecord?id=CVE-2025-40083 Référence CVE CVE-2025-40097 https://www.cve.org/CVERecord?id=CVE-2025-40097 Référence CVE CVE-2025-40098 https://www.cve.org/CVERecord?id=CVE-2025-40098 Référence CVE CVE-2025-40102 https://www.cve.org/CVERecord?id=CVE-2025-40102 Référence CVE CVE-2025-40105 https://www.cve.org/CVERecord?id=CVE-2025-40105 Référence CVE CVE-2025-40106 https://www.cve.org/CVERecord?id=CVE-2025-40106 Référence CVE CVE-2025-40107 https://www.cve.org/CVERecord?id=CVE-2025-40107 Référence CVE CVE-2025-40109 https://www.cve.org/CVERecord?id=CVE-2025-40109 Référence CVE CVE-2025-40110 https://www.cve.org/CVERecord?id=CVE-2025-40110 Référence CVE CVE-2025-40111 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40053 Référence CVE CVE-2025-40055 https://www.cve.org/CVERecord?id=CVE-2025-40055 Référence CVE CVE-2025-40059 https://www.cve.org/CVERecord?id=CVE-2025-40059 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40074 https://www.cve.org/CVERecord?id=CVE-2025-40074 Référence CVE CVE-2025-40075 https://www.cve.org/CVERecord?id=CVE-2025-40075 Référence CVE CVE-2025-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40083 https://www.cve.org/CVERecord?id=CVE-2025-40083 Référence CVE CVE-2025-40097 https://www.cve.org/CVERecord?id=CVE-2025-40097 Référence CVE CVE-2025-40098 https://www.cve.org/CVERecord?id=CVE-2025-40098 Référence CVE CVE-2025-40102 https://www.cve.org/CVERecord?id=CVE-2025-40102 Référence CVE CVE-2025-40105 https://www.cve.org/CVERecord?id=CVE-2025-40105 Référence CVE CVE-2025-40106 https://www.cve.org/CVERecord?id=CVE-2025-40106 Référence CVE CVE-2025-40107 https://www.cve.org/CVERecord?id=CVE-2025-40107 Référence CVE CVE-2025-40109 https://www.cve.org/CVERecord?id=CVE-2025-40109 Référence CVE CVE-2025-40110 https://www.cve.org/CVERecord?id=CVE-2025-40110 Référence CVE CVE-2025-40111 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40087 Référence CVE CVE-2025-40088 https://www.cve.org/CVERecord?id=CVE-2025-40088 Référence CVE CVE-2025-40089 https://www.cve.org/CVERecord?id=CVE-2025-40089 Référence CVE CVE-2025-40091 https://www.cve.org/CVERecord?id=CVE-2025-40091 Référence CVE CVE-2025-40092 https://www.cve.org/CVERecord?id=CVE-2025-40092 Référence CVE CVE-2025-40093 https://www.cve.org/CVERecord?id=CVE-2025-40093 Référence CVE CVE-2025-40094 https://www.cve.org/CVERecord?id=CVE-2025-40094 Référence CVE CVE-2025-40095 https://www.cve.org/CVERecord?id=CVE-2025-40095 Référence CVE CVE-2025-40096 https://www.cve.org/CVERecord?id=CVE-2025-40096 Référence CVE CVE-2025-40097 https://www.cve.org/CVERecord?id=CVE-2025-40097 Référence CVE CVE-2025-40098 https://www.cve.org/CVERecord?id=CVE-2025-40098 Référence CVE CVE-2025-40099 https://www.cve.org/CVERecord?id=CVE-2025-40099 Référence CVE CVE-2025-40100 https://www.cve.org/CVERecord?id=CVE-2025-40100 Référence CVE CVE-2025-40101 https://www.cve.org/CVERecord?id=CVE-2025-40101 Référence CVE CVE-2025-40102 https://www.cve.org/CVERecord?id=CVE-2025-40102 Référence CVE CVE-2025-40103 https://www.cve.org/CVERecord?id=CVE-2025-40103 Référence CVE CVE-2025-40104 https://www.cve.org/CVERecord?id=CVE-2025-40104 Référence CVE CVE-2025-40105 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40087 Référence CVE CVE-2025-40088 https://www.cve.org/CVERecord?id=CVE-2025-40088 Référence CVE CVE-2025-40089 https://www.cve.org/CVERecord?id=CVE-2025-40089 Référence CVE CVE-2025-40091 https://www.cve.org/CVERecord?id=CVE-2025-40091 Référence CVE CVE-2025-40092 https://www.cve.org/CVERecord?id=CVE-2025-40092 Référence CVE CVE-2025-40093 https://www.cve.org/CVERecord?id=CVE-2025-40093 Référence CVE CVE-2025-40094 https://www.cve.org/CVERecord?id=CVE-2025-40094 Référence CVE CVE-2025-40095 https://www.cve.org/CVERecord?id=CVE-2025-40095 Référence CVE CVE-2025-40096 https://www.cve.org/CVERecord?id=CVE-2025-40096 Référence CVE CVE-2025-40097 https://www.cve.org/CVERecord?id=CVE-2025-40097 Référence CVE CVE-2025-40098 https://www.cve.org/CVERecord?id=CVE-2025-40098 Référence CVE CVE-2025-40099 https://www.cve.org/CVERecord?id=CVE-2025-40099 Référence CVE CVE-2025-40100 https://www.cve.org/CVERecord?id=CVE-2025-40100 Référence CVE CVE-2025-40101 https://www.cve.org/CVERecord?id=CVE-2025-40101 Référence CVE CVE-2025-40102 https://www.cve.org/CVERecord?id=CVE-2025-40102 Référence CVE CVE-2025-40103 https://www.cve.org/CVERecord?id=CVE-2025-40103 Référence CVE CVE-2025-40104 https://www.cve.org/CVERecord?id=CVE-2025-40104 Référence CVE CVE-2025-40105 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39829 Référence CVE CVE-2025-39836 https://www.cve.org/CVERecord?id=CVE-2025-39836 Référence CVE CVE-2025-39880 https://www.cve.org/CVERecord?id=CVE-2025-39880 Référence CVE CVE-2025-39913 https://www.cve.org/CVERecord?id=CVE-2025-39913 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=CVE-2025-39977 Référence CVE CVE-2025-40019 https://www.cve.org/CVERecord?id=CVE-2025-40019 Référence CVE CVE-2025-40044 https://www.cve.org/CVERecord?id=CVE-2025-40044 Référence CVE CVE-2025-40087 https://www.cve.org/CVERecord?id=CVE-2025-40087 Référence CVE CVE-2025-40088 https://www.cve.org/CVERecord?id=CVE-2025-40088 Référence CVE CVE-2025-40097 https://www.cve.org/CVERecord?id=CVE-2025-40097 Référence CVE CVE-2025-40106 https://www.cve.org/CVERecord?id=CVE-2025-40106 Référence CVE CVE-2025-40115 https://www.cve.org/CVERecord?id=CVE-2025-40115 Référence CVE CVE-2025-40132 https://www.cve.org/CVERecord?id=CVE-2025-40132 Référence CVE CVE-2025-40136 https://www.cve.org/CVERecord?id=CVE-2025-40136 Référence CVE CVE-2025-40139 https://www.cve.org/CVERecord?id=CVE-2025-40139 Référence CVE CVE-2025-40142 https://www.cve.org/CVERecord?id=CVE-2025-40142 Référence CVE CVE-2025-40166 https://www.cve.org/CVERecord?id=CVE-2025-40166 Référence CVE CVE-2025-40177 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40087 Référence CVE CVE-2025-40088 https://www.cve.org/CVERecord?id=CVE-2025-40088 Référence CVE CVE-2025-40089 https://www.cve.org/CVERecord?id=CVE-2025-40089 Référence CVE CVE-2025-40091 https://www.cve.org/CVERecord?id=CVE-2025-40091 Référence CVE CVE-2025-40092 https://www.cve.org/CVERecord?id=CVE-2025-40092 Référence CVE CVE-2025-40093 https://www.cve.org/CVERecord?id=CVE-2025-40093 Référence CVE CVE-2025-40094 https://www.cve.org/CVERecord?id=CVE-2025-40094 Référence CVE CVE-2025-40095 https://www.cve.org/CVERecord?id=CVE-2025-40095 Référence CVE CVE-2025-40096 https://www.cve.org/CVERecord?id=CVE-2025-40096 Référence CVE CVE-2025-40097 https://www.cve.org/CVERecord?id=CVE-2025-40097 Référence CVE CVE-2025-40098 https://www.cve.org/CVERecord?id=CVE-2025-40098 Référence CVE CVE-2025-40099 https://www.cve.org/CVERecord?id=CVE-2025-40099 Référence CVE CVE-2025-40100 https://www.cve.org/CVERecord?id=CVE-2025-40100 Référence CVE CVE-2025-40101 https://www.cve.org/CVERecord?id=CVE-2025-40101 Référence CVE CVE-2025-40102 https://www.cve.org/CVERecord?id=CVE-2025-40102 Référence CVE CVE-2025-40103 https://www.cve.org/CVERecord?id=CVE-2025-40103 Référence CVE CVE-2025-40104 https://www.cve.org/CVERecord?id=CVE-2025-40104 Référence CVE CVE-2025-40105 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0966Multiples vulnérabilités dans les produits Microsoft

CVE-2025-12058 du 31 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40083 du 31 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40084 du 31 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40085 du 31 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40087 du 31 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40088 du 31 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40092 du 31 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40094 du 31 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40095 du 31 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40096 du 31 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40097 du 31 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40099 du 31 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40100 du 31 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40102 du 31 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40103 du 31 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40104 du 31 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40105 du 31 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-47912 du 31 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-58183 du 31 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-58185 du 31 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-58186

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: < 5.17, 6.1.189 ≤ 6.1.*, 6.6.158 ≤ 6.6.*, 6.12.59 ≤ 6.12.*, 6.17.5 ≤ 6.17.*, 6.18 ≤ *
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 30 Oct 2025 · Last source change 3 Oct 2026, 10:55 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceUnavailable
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-2025-36981
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD not scheduled

Missing structured fields: CVSS base score, 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. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/b044aa6ae63391ba40c93ca5d476d276cb17db1b; removed remediation: git.kernel.org/218a8504e62fc2c8a1fd12523346b7a2b9bd2474.
    Before
    remediation: git.kernel.org/218a8504e62fc2c8a1fd12523346b7a2b9bd2474
    After
    remediation: git.kernel.org/b044aa6ae63391ba40c93ca5d476d276cb17db1b
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    ae7abe36e352eddf8e30d3b1ea3fb402514ba13b < 218a8504e62fc2c8a1fd12523346b7a2b9bd2474; ae7abe36e352eddf8e30d3b1ea3fb402514ba13b < 47d1b9ca923b55c3f407788f1f15b04957e0e027; ae7abe36e352eddf8e30d3b1ea3fb402514ba13b < 1cf11d80db5df805b538c942269e05a65bcaf5bc; 5.17 · Fixed: < 5.17; 6.12.59 ≤ 6.12.*; 6.17.5 ≤ 6.17.*; 6.18 ≤ *
    After
    Linux: ae7abe36e352eddf8e30d3b1ea3fb402514ba13b < b044aa6ae63391ba40c93ca5d476d276cb17db1b, ae7abe36e352eddf8e30d3b1ea3fb402514ba13b < 1c3f4b15eb1850558d7d4da74b98cffbb8121721, ae7abe36e352eddf8e30d3b1ea3fb402514ba13b < 218a8504e62fc2c8a1fd12523346b7a2b9bd2474, ae7abe36e352eddf8e30d3b1ea3fb402514ba13b < 47d1b9ca923b55c3f407788f1f15b04957e0e027, ae7abe36e352eddf8e30d3b1ea3fb402514ba13b < 1cf11d80db5df805b538c942269e05a65bcaf5bc, 5.17 · Fixed: Linux: < 5.17, 6.1.189 ≤ 6.1.*, 6.6.158 ≤ 6.6.*, 6.12.59 ≤ 6.12.*, 6.17.5 ≤ 6.17.*, 6.18 ≤ *
    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-2025-36981↗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-2025-40097 · cve.blacktree.nl