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

dlm: prevent NPD when writing a positive value to event_done

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. 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 severityMediumOperational priority:Low, lowered one band.downgradedsince 4 Jul 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.19% 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: No default targetRemediation target: Normal maintenance

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.

25 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.95-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.177-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.16.3-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.16.3-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-intelAffected, 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-23131 · CSAF 2.0 · revision 46 · interimSUSE Product Security TeamCVE-2025-23131
351 known affected

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

  • kernel-default as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-source as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • 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
Summary
In the Linux kernel, the following vulnerability has been resolved: dlm: prevent NPD when writing a positive value to event_done do_uevent returns the value written to event_done. In case it is a positive value, new_lockspace would undo all the work, and lockspace would not be set. __dlm_new_lockspace, however, would treat that positive value as a success due to commit 8511a2728ab8 ("dlm: fix use count with multiple joins"). Down the line, device_create_lockspace would pass that NULL lockspace to dlm_find_lockspace_local, leading to a NULL pointer dereference. Treating such positive values as successes prevents the problem. Given this has been broken for so long, this is unlikely to break userspace expectations.
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-11172

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. 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: dlm: prevent NPD when writing a positive value to event_done do_uevent returns the value written to event_done. In case it is a positive value, new_lockspace would undo all the work, and lockspace would not be set. __dlm_new_lockspace, however, would treat that positive value as a success due to commit 8511a2728ab8 ("dlm: fix use count with multiple joins"). Down the line, device_create_lockspace would pass that NULL lockspace to dlm_find_lockspace_local, leading to a NULL pointer dereference. Treating such positive values as successes prevents the problem. Given this has been broken for so long, this is unlikely to break userspace expectations.

What

In the Linux kernel, the following vulnerability has been resolved: dlm: prevent NPD when writing a positive value to event_done do_uevent returns the value written to event_done. In case it is a positive value, new_lockspace would undo all the work, and lockspace would not be set. __dlm_new_lockspace, however, would treat that positive value as a success due to commit 8511a2728ab8 ("dlm: fix use count with multiple joins"). Down the line, device_create_lockspace would pass that NULL lockspace to dlm_find_lockspace_local, leading to a NULL pointer dereference. Treating such positive values as successes prevents the problem. Given this has been broken for so long, this is unlikely to break userspace expectations.

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: dlm: prevent NPD when writing a positive value to event_done do_uevent returns the value written to event_done. In case it is a positive value, new_lockspace would undo all the work, and lockspace would not be set. __dlm_new_lockspace, however, would treat that positive value as a success due to commit 8511a2728ab8 ("dlm: fix use count with multiple joins"). Down the line, device_create_lockspace would pass that NULL lockspace to dlm_find_lockspace_local, leading to a NULL pointer dereference. Treating such positive values as successes prevents the problem. Given this has been broken for so long, this is unlikely to break userspace expectations.

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:N/I:N/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.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.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-2025-0844Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht genauer beschriebene Auswirkungen erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250430Security Bulletin 30 Apr 2020

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 30 Apr 2020, published on 30 April 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250423Security Bulletin 23 Apr 2025

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

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250417Security Bulletin 17 April 2025

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

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

teur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Debian LTS msg00007 du 05 août 2026 https://lists.debian.org/debian-lts-announce/2026/08/msg00007.html Bulletin de sécurité Debian LTS msg00008 du 05 août 2026 https://lists.debian.org/debian-lts-announce/2026/08/msg00008.html Référence CVE CVE-2022-49803 https://www.cve.org/CVERecord?id=CVE-2022-49803 Référence CVE CVE-2022-50114 https://www.cve.org/CVERecord?id=CVE-2022-50114 Référence CVE CVE-2023-52494 https://www.cve.org/CVERecord?id=CVE-2023-52494 Référence CVE CVE-2024-36013 https://www.cve.org/CVERecord?id=CVE-2024-36013 Référence CVE CVE-2025-23131 https://www.cve.org/CVERecord?id=CVE-2025-23131 Référence CVE CVE-2025-39931 https://www.cve.org/CVERecord?id=CVE-2025-39931 Référence CVE CVE-2025-40196 https://www.cve.org/CVERecord?id=CVE-2025-40196 Référence CVE CVE-2026-23204 https://www.cve.org/CVERecord?id=CVE-2026-23204 Référence CVE CVE-2026-31451 https://www.cve.org/CVERecord?id=CVE-2026-31451 Référence CVE CVE-2026-31610 https://www.cve.org/CVERecord?id=CVE-2026-31610 Référence CVE CVE-2026-31755 https://www.cve.org/CVERecord?id=CVE-2026-31755 Référence CVE CVE-2026-43216 https://www.cve.org/CVERecord?id=CVE-2026-43216 Référence CVE CVE-2026-43219 https://www.cve.org/CVERecord?id=

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

spécifié par l'éditeur Élévation de privilèges Systèmes affectés Debian 11 bullseye versions antérieures à 6.1.177-1~deb11u1 Résumé De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à un attaquant de provoquer une élévation de privilèges, une atteinte à la confidentialité des données et un déni de service. Solutions Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Debian LTS msg00042 du 26 juillet 2026 https://lists.debian.org/debian-lts-announce/2026/07/msg00042.html Référence CVE CVE-2025-23131 https://www.cve.org/CVERecord?id=CVE-2025-23131 Référence CVE CVE-2026-23272 https://www.cve.org/CVERecord?id=CVE-2026-23272 Référence CVE CVE-2026-23278 https://www.cve.org/CVERecord?id=CVE-2026-23278 Référence CVE CVE-2026-23302 https://www.cve.org/CVERecord?id=CVE-2026-23302 Référence CVE CVE-2026-31451 https://www.cve.org/CVERecord?id=CVE-2026-31451 Référence CVE CVE-2026-46252 https://www.cve.org/CVERecord?id=CVE-2026-46252 Référence CVE CVE-2026-52928 https://www.cve.org/CVERecord?id=CVE-2026-52928 Référence CVE CVE-2026-53138 https://www.cve.org/CVERecord?id=CVE-2026-53138 Référence CVE CVE-2026-53139 https://www.cve.org/CVERecord?id=

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de provoquer une élévation de privilèges, une atteinte à la confidentialité des données et une atteinte à l'intégrité des données.

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

d?id=CVE-2024-43902 Référence CVE CVE-2024-53221 https://www.cve.org/CVERecord?id=CVE-2024-53221 Référence CVE CVE-2024-56657 https://www.cve.org/CVERecord?id=CVE-2024-56657 Référence CVE CVE-2025-10263 https://www.cve.org/CVERecord?id=CVE-2025-10263 Référence CVE CVE-2025-21739 https://www.cve.org/CVERecord?id=CVE-2025-21739 Référence CVE CVE-2025-21863 https://www.cve.org/CVERecord?id=CVE-2025-21863 Référence CVE CVE-2025-22026 https://www.cve.org/CVERecord?id=CVE-2025-22026 Référence CVE CVE-2025-22105 https://www.cve.org/CVERecord?id=CVE-2025-22105 Référence CVE CVE-2025-22107 https://www.cve.org/CVERecord?id=CVE-2025-22107 Référence CVE CVE-2025-23131 https://www.cve.org/CVERecord?id=CVE-2025-23131 Référence CVE CVE-2025-37864 https://www.cve.org/CVERecord?id=CVE-2025-37864 Référence CVE CVE-2025-38129 https://www.cve.org/CVERecord?id=CVE-2025-38129 Référence CVE CVE-2025-38250 https://www.cve.org/CVERecord?id=CVE-2025-38250 Référence CVE CVE-2025-38584 https://www.cve.org/CVERecord?id=CVE-2025-38584 Référence CVE CVE-2025-38627 https://www.cve.org/CVERecord?id=CVE-2025-38627 Référence CVE CVE-2025-38710 https://www.cve.org/CVERecord?id=CVE-2025-38710 Référence CVE CVE-2025-39929 https://www.cve.org/CVERecord?id=CVE-2025-39929 Référence CVE CVE-2025-39997 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-22868 Référence CVE CVE-2025-22869 https://www.cve.org/CVERecord?id=CVE-2025-22869 Référence CVE CVE-2025-22870 https://www.cve.org/CVERecord?id=CVE-2025-22870 Référence CVE CVE-2025-22871 https://www.cve.org/CVERecord?id=CVE-2025-22871 Référence CVE CVE-2025-22872 https://www.cve.org/CVERecord?id=CVE-2025-22872 Référence CVE CVE-2025-22873 https://www.cve.org/CVERecord?id=CVE-2025-22873 Référence CVE CVE-2025-22874 https://www.cve.org/CVERecord?id=CVE-2025-22874 Référence CVE CVE-2025-23085 https://www.cve.org/CVERecord?id=CVE-2025-23085 Référence CVE CVE-2025-23130 https://www.cve.org/CVERecord?id=CVE-2025-23130 Référence CVE CVE-2025-23131 https://www.cve.org/CVERecord?id=CVE-2025-23131 Référence CVE CVE-2025-23132 https://www.cve.org/CVERecord?id=CVE-2025-23132 Référence CVE CVE-2025-23133 https://www.cve.org/CVERecord?id=CVE-2025-23133 Référence CVE CVE-2025-23141 https://www.cve.org/CVERecord?id=CVE-2025-23141 Référence CVE CVE-2025-23155 https://www.cve.org/CVERecord?id=CVE-2025-23155 Référence CVE CVE-2025-23160 https://www.cve.org/CVERecord?id=CVE-2025-23160 Référence CVE CVE-2025-23162 https://www.cve.org/CVERecord?id=CVE-2025-23162 Référence CVE CVE-2025-25184 https://www.cve.org/CVERecord?id=CVE-2025-25184 Référence CVE CVE-2025-2668 https://www.cve.org/CVERecord?id=C

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

d?id=CVE-2025-22868 Référence CVE CVE-2025-22869 https://www.cve.org/CVERecord?id=CVE-2025-22869 Référence CVE CVE-2025-22870 https://www.cve.org/CVERecord?id=CVE-2025-22870 Référence CVE CVE-2025-22871 https://www.cve.org/CVERecord?id=CVE-2025-22871 Référence CVE CVE-2025-22872 https://www.cve.org/CVERecord?id=CVE-2025-22872 Référence CVE CVE-2025-22873 https://www.cve.org/CVERecord?id=CVE-2025-22873 Référence CVE CVE-2025-22874 https://www.cve.org/CVERecord?id=CVE-2025-22874 Référence CVE CVE-2025-23085 https://www.cve.org/CVERecord?id=CVE-2025-23085 Référence CVE CVE-2025-23130 https://www.cve.org/CVERecord?id=CVE-2025-23130 Référence CVE CVE-2025-23131 https://www.cve.org/CVERecord?id=CVE-2025-23131 Référence CVE CVE-2025-23132 https://www.cve.org/CVERecord?id=CVE-2025-23132 Référence CVE CVE-2025-23133 https://www.cve.org/CVERecord?id=CVE-2025-23133 Référence CVE CVE-2025-23141 https://www.cve.org/CVERecord?id=CVE-2025-23141 Référence CVE CVE-2025-23155 https://www.cve.org/CVERecord?id=CVE-2025-23155 Référence CVE CVE-2025-23160 https://www.cve.org/CVERecord?id=CVE-2025-23160 Référence CVE CVE-2025-23162 https://www.cve.org/CVERecord?id=CVE-2025-23162 Référence CVE CVE-2025-2668 https://www.cve.org/CVERecord?id=CVE-2025-2668 Référence CVE CVE-2025-27516 https://www.cve.org/CVERecord?id=CV

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

ord?id=CVE-2025-22123 Référence CVE CVE-2025-22124 https://www.cve.org/CVERecord?id=CVE-2025-22124 Référence CVE CVE-2025-22125 https://www.cve.org/CVERecord?id=CVE-2025-22125 Référence CVE CVE-2025-22126 https://www.cve.org/CVERecord?id=CVE-2025-22126 Référence CVE CVE-2025-22127 https://www.cve.org/CVERecord?id=CVE-2025-22127 Référence CVE CVE-2025-22128 https://www.cve.org/CVERecord?id=CVE-2025-22128 Référence CVE CVE-2025-2312 https://www.cve.org/CVERecord?id=CVE-2025-2312 Référence CVE CVE-2025-23129 https://www.cve.org/CVERecord?id=CVE-2025-23129 Référence CVE CVE-2025-23130 https://www.cve.org/CVERecord?id=CVE-2025-23130 Référence CVE CVE-2025-23131 https://www.cve.org/CVERecord?id=CVE-2025-23131 Référence CVE CVE-2025-23132 https://www.cve.org/CVERecord?id=CVE-2025-23132 Référence CVE CVE-2025-23133 https://www.cve.org/CVERecord?id=CVE-2025-23133 Référence CVE CVE-2025-23134 https://www.cve.org/CVERecord?id=CVE-2025-23134 Référence CVE CVE-2025-23135 https://www.cve.org/CVERecord?id=CVE-2025-23135 Référence CVE CVE-2025-23136 https://www.cve.org/CVERecord?id=CVE-2025-23136 Référence CVE CVE-2025-23137 https://www.cve.org/CVERecord?id=CVE-2025-23137 Référence CVE CVE-2025-23138 https://www.cve.org/CVERecord?id=CVE-2025-23138 Référence CVE CVE-2025-23140 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2025-22123 Référence CVE CVE-2025-22124 https://www.cve.org/CVERecord?id=CVE-2025-22124 Référence CVE CVE-2025-22125 https://www.cve.org/CVERecord?id=CVE-2025-22125 Référence CVE CVE-2025-22126 https://www.cve.org/CVERecord?id=CVE-2025-22126 Référence CVE CVE-2025-22127 https://www.cve.org/CVERecord?id=CVE-2025-22127 Référence CVE CVE-2025-22128 https://www.cve.org/CVERecord?id=CVE-2025-22128 Référence CVE CVE-2025-2312 https://www.cve.org/CVERecord?id=CVE-2025-2312 Référence CVE CVE-2025-23129 https://www.cve.org/CVERecord?id=CVE-2025-23129 Référence CVE CVE-2025-23130 https://www.cve.org/CVERecord?id=CVE-2025-23130 Référence CVE CVE-2025-23131 https://www.cve.org/CVERecord?id=CVE-2025-23131 Référence CVE CVE-2025-23132 https://www.cve.org/CVERecord?id=CVE-2025-23132 Référence CVE CVE-2025-23133 https://www.cve.org/CVERecord?id=CVE-2025-23133 Référence CVE CVE-2025-23134 https://www.cve.org/CVERecord?id=CVE-2025-23134 Référence CVE CVE-2025-23135 https://www.cve.org/CVERecord?id=CVE-2025-23135 Référence CVE CVE-2025-23136 https://www.cve.org/CVERecord?id=CVE-2025-23136 Référence CVE CVE-2025-23137 https://www.cve.org/CVERecord?id=CVE-2025-23137 Référence CVE CVE-2025-23138 https://www.cve.org/CVERecord?id=CVE-2025-23138 Référence CVE CVE-2025-23140 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2025-22118 Référence CVE CVE-2025-22119 https://www.cve.org/CVERecord?id=CVE-2025-22119 Référence CVE CVE-2025-22121 https://www.cve.org/CVERecord?id=CVE-2025-22121 Référence CVE CVE-2025-22124 https://www.cve.org/CVERecord?id=CVE-2025-22124 Référence CVE CVE-2025-22125 https://www.cve.org/CVERecord?id=CVE-2025-22125 Référence CVE CVE-2025-22126 https://www.cve.org/CVERecord?id=CVE-2025-22126 Référence CVE CVE-2025-22128 https://www.cve.org/CVERecord?id=CVE-2025-22128 Référence CVE CVE-2025-2312 https://www.cve.org/CVERecord?id=CVE-2025-2312 Référence CVE CVE-2025-23129 https://www.cve.org/CVERecord?id=CVE-2025-23129 Référence CVE CVE-2025-23131 https://www.cve.org/CVERecord?id=CVE-2025-23131 Référence CVE CVE-2025-23133 https://www.cve.org/CVERecord?id=CVE-2025-23133 Référence CVE CVE-2025-23134 https://www.cve.org/CVERecord?id=CVE-2025-23134 Référence CVE CVE-2025-23136 https://www.cve.org/CVERecord?id=CVE-2025-23136 Référence CVE CVE-2025-23138 https://www.cve.org/CVERecord?id=CVE-2025-23138 Référence CVE CVE-2025-23140 https://www.cve.org/CVERecord?id=CVE-2025-23140 Référence CVE CVE-2025-23141 https://www.cve.org/CVERecord?id=CVE-2025-23141 Référence CVE CVE-2025-23142 https://www.cve.org/CVERecord?id=CVE-2025-23142 Référence CVE CVE-2025-23144 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2025-22109 Référence CVE CVE-2025-22115 https://www.cve.org/CVERecord?id=CVE-2025-22115 Référence CVE CVE-2025-22116 https://www.cve.org/CVERecord?id=CVE-2025-22116 Référence CVE CVE-2025-22121 https://www.cve.org/CVERecord?id=CVE-2025-22121 Référence CVE CVE-2025-22125 https://www.cve.org/CVERecord?id=CVE-2025-22125 Référence CVE CVE-2025-22126 https://www.cve.org/CVERecord?id=CVE-2025-22126 Référence CVE CVE-2025-22128 https://www.cve.org/CVERecord?id=CVE-2025-22128 Référence CVE CVE-2025-2312 https://www.cve.org/CVERecord?id=CVE-2025-2312 Référence CVE CVE-2025-23129 https://www.cve.org/CVERecord?id=CVE-2025-23129 Référence CVE CVE-2025-23131 https://www.cve.org/CVERecord?id=CVE-2025-23131 Référence CVE CVE-2025-23133 https://www.cve.org/CVERecord?id=CVE-2025-23133 Référence CVE CVE-2025-23136 https://www.cve.org/CVERecord?id=CVE-2025-23136 Référence CVE CVE-2025-23138 https://www.cve.org/CVERecord?id=CVE-2025-23138 Référence CVE CVE-2025-23140 https://www.cve.org/CVERecord?id=CVE-2025-23140 Référence CVE CVE-2025-23145 https://www.cve.org/CVERecord?id=CVE-2025-23145 Référence CVE CVE-2025-23150 https://www.cve.org/CVERecord?id=CVE-2025-23150 Référence CVE CVE-2025-23160 https://www.cve.org/CVERecord?id=CVE-2025-23160 Référence CVE CVE-2025-37748 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-22106 Référence CVE CVE-2025-22107 https://www.cve.org/CVERecord?id=CVE-2025-22107 Référence CVE CVE-2025-22108 https://www.cve.org/CVERecord?id=CVE-2025-22108 Référence CVE CVE-2025-22109 https://www.cve.org/CVERecord?id=CVE-2025-22109 Référence CVE CVE-2025-22115 https://www.cve.org/CVERecord?id=CVE-2025-22115 Référence CVE CVE-2025-22116 https://www.cve.org/CVERecord?id=CVE-2025-22116 Référence CVE CVE-2025-22121 https://www.cve.org/CVERecord?id=CVE-2025-22121 Référence CVE CVE-2025-22128 https://www.cve.org/CVERecord?id=CVE-2025-22128 Référence CVE CVE-2025-23129 https://www.cve.org/CVERecord?id=CVE-2025-23129 Référence CVE CVE-2025-23131 https://www.cve.org/CVERecord?id=CVE-2025-23131 Référence CVE CVE-2025-23133 https://www.cve.org/CVERecord?id=CVE-2025-23133 Référence CVE CVE-2025-23136 https://www.cve.org/CVERecord?id=CVE-2025-23136 Référence CVE CVE-2025-23138 https://www.cve.org/CVERecord?id=CVE-2025-23138 Référence CVE CVE-2025-23145 https://www.cve.org/CVERecord?id=CVE-2025-23145 Référence CVE CVE-2025-37785 https://www.cve.org/CVERecord?id=CVE-2025-37785 Référence CVE CVE-2025-37798 https://www.cve.org/CVERecord?id=CVE-2025-37798 Référence CVE CVE-2025-37799 https://www.cve.org/CVERecord?id=CVE-2025-37799 Référence CVE CVE-2025-37860 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2025-22107 Référence CVE CVE-2025-22108 https://www.cve.org/CVERecord?id=CVE-2025-22108 Référence CVE CVE-2025-22109 https://www.cve.org/CVERecord?id=CVE-2025-22109 Référence CVE CVE-2025-22115 https://www.cve.org/CVERecord?id=CVE-2025-22115 Référence CVE CVE-2025-22116 https://www.cve.org/CVERecord?id=CVE-2025-22116 Référence CVE CVE-2025-22121 https://www.cve.org/CVERecord?id=CVE-2025-22121 Référence CVE CVE-2025-22128 https://www.cve.org/CVERecord?id=CVE-2025-22128 Référence CVE CVE-2025-2312 https://www.cve.org/CVERecord?id=CVE-2025-2312 Référence CVE CVE-2025-23129 https://www.cve.org/CVERecord?id=CVE-2025-23129 Référence CVE CVE-2025-23131 https://www.cve.org/CVERecord?id=CVE-2025-23131 Référence CVE CVE-2025-23133 https://www.cve.org/CVERecord?id=CVE-2025-23133 Référence CVE CVE-2025-23136 https://www.cve.org/CVERecord?id=CVE-2025-23136 Référence CVE CVE-2025-23138 https://www.cve.org/CVERecord?id=CVE-2025-23138 Référence CVE CVE-2025-23145 https://www.cve.org/CVERecord?id=CVE-2025-23145 Référence CVE CVE-2025-37785 https://www.cve.org/CVERecord?id=CVE-2025-37785 Référence CVE CVE-2025-37798 https://www.cve.org/CVERecord?id=CVE-2025-37798 Référence CVE CVE-2025-37799 https://www.cve.org/CVERecord?id=CVE-2025-37799 Référence CVE CVE-2025-37860 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2025-22107 Référence CVE CVE-2025-22108 https://www.cve.org/CVERecord?id=CVE-2025-22108 Référence CVE CVE-2025-22109 https://www.cve.org/CVERecord?id=CVE-2025-22109 Référence CVE CVE-2025-22115 https://www.cve.org/CVERecord?id=CVE-2025-22115 Référence CVE CVE-2025-22116 https://www.cve.org/CVERecord?id=CVE-2025-22116 Référence CVE CVE-2025-22121 https://www.cve.org/CVERecord?id=CVE-2025-22121 Référence CVE CVE-2025-22128 https://www.cve.org/CVERecord?id=CVE-2025-22128 Référence CVE CVE-2025-2312 https://www.cve.org/CVERecord?id=CVE-2025-2312 Référence CVE CVE-2025-23129 https://www.cve.org/CVERecord?id=CVE-2025-23129 Référence CVE CVE-2025-23131 https://www.cve.org/CVERecord?id=CVE-2025-23131 Référence CVE CVE-2025-23133 https://www.cve.org/CVERecord?id=CVE-2025-23133 Référence CVE CVE-2025-23136 https://www.cve.org/CVERecord?id=CVE-2025-23136 Référence CVE CVE-2025-23138 https://www.cve.org/CVERecord?id=CVE-2025-23138 Référence CVE CVE-2025-23145 https://www.cve.org/CVERecord?id=CVE-2025-23145 Référence CVE CVE-2025-37785 https://www.cve.org/CVERecord?id=CVE-2025-37785 Référence CVE CVE-2025-37798 https://www.cve.org/CVERecord?id=CVE-2025-37798 Référence CVE CVE-2025-37799 https://www.cve.org/CVERecord?id=CVE-2025-37799 Référence CVE CVE-2025-37860 https://www.cve.org/CVERecord?id=

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

Linux の Linux Kernel には、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: < 2.6.31, 5.10.260 ≤ 5.10.*, 5.15.211 ≤ 5.15.*, 6.1.177 ≤ 6.1.*, 6.6.144 ≤ 6.6.*, 6.12.95 ≤ 6.12.*, 6.14.2 ≤ 6.14.*, 6.15 ≤ *
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 16 Apr 2025 · Last source change 4 Jul 2026, 11:50 UTC · CWE-476 · NULL Pointer Dereference

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
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-11172
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

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