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

timers: Fix NULL function pointer race in timer_shutdown_sync()

Linux · Linux

4.7MediumCVSS 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 20 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 23 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.13% 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 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.63-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.159-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.17.10-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.17.10-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-2025-68214 · CSAF 2.0 · revision 27 · interimSUSE Product Security TeamCVE-2025-68214
357 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 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 Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
Summary
In the Linux kernel, the following vulnerability has been resolved: timers: Fix NULL function pointer race in timer_shutdown_sync() There is a race condition between timer_shutdown_sync() and timer expiration that can lead to hitting a WARN_ON in expire_timers(). The issue occurs when timer_shutdown_sync() clears the timer function to NULL while the timer is still running on another CPU. The race scenario looks like this: CPU0 CPU1 lock_timer_base() expire_timers() base->running_timer = timer; unlock_timer_base() [call_timer_fn enter] mod_timer() ... timer_shutdown_sync() lock_timer_base() // For now, will not detach the timer but only clear its function to NULL if (base->running_timer != timer) ret = detach_if_pending(timer, base, true); if (shutdown) timer->function = NULL; unlock_timer_base() [call_timer_fn exit] lock_timer_base() base->running_timer = NULL; unlock_timer_base() ... // Now timer is pending while its function set to NULL. // next timer trigger expire_timers() WARN_ON_ONCE(!fn) // hit ... lock_timer_base() // Now timer will detach if (base->running_timer != timer) ret = detach_if_pending(timer, base, true); if (shutdown) timer->function = NULL; unlock_timer_base() The problem is that timer_shutdown_sync() clears the timer function regardless of whether the timer is currently running. This can leave a pending timer with a NULL function pointer, which triggers the WARN_ON_ONCE(!fn) check in expire_timers(). Fix this by only clearing the timer function when actually detaching the timer. If the timer is running, leave the function pointer intact, which is safe because the timer will be properly detached when it finishes running.
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-203682

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 20 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: timers: Fix NULL function pointer race in timer_shutdown_sync() There is a race condition between timer_shutdown_sync() and timer expiration that can lead to hitting a WARN_ON in expire_timers(). The issue occurs when timer_shutdown_sync() clears the timer function to NULL while the timer is still running on another CPU. The race scenario looks like this: CPU0 CPU1 <SOFTIRQ> lock_timer_base() expire_timers() base->running_timer = timer; unlock_timer_base() [call_timer_fn enter] mod_timer() ... timer_shutdown_sync() lock_timer_base() // For now, will not detach the timer but only clear its function to NULL if (base->running_timer != timer) ret = detach_if_pending(timer, base, true); if (shutdown) timer->function = NULL; unlock_timer_base() [call_timer_fn exit] lock_timer_base() base->running_timer = NULL; unlock_timer_base() ... // Now timer is pending while its function set to NULL. // next timer trigger <SOFTIRQ> expire_timers() WARN_ON_ONCE(!fn) // hit ... lock_timer_base() // Now timer will detach if (base->running_timer != timer) ret = detach_if_pending(timer, base, true); if (shutdown) timer->function = NULL; unlock_timer_base() The problem is that timer_shutdown_sync() clears the timer function regardless of whether the timer is currently running. This can leave a pending timer with a NULL function pointer, which triggers the WARN_ON_ONCE(!fn) check in expire_timers(). Fix this by only clearing the timer function when actually detaching the timer. If the timer is running, leave the function pointer intact, which is safe because the timer will be properly detached when it finishes running.

What

In the Linux kernel, the following vulnerability has been resolved: timers: Fix NULL function pointer race in timer_shutdown_sync() There is a race condition between timer_shutdown_sync() and timer expiration that can lead to hitting a WARN_ON in expire_timers(). The issue occurs when timer_shutdown_sync() clears the timer function to NULL while the timer is still running on another CPU. The race scenario looks like this: CPU0 CPU1 <SOFTIRQ> lock_timer_base() expire_timers() base->running_timer = timer; unlock_timer_base() [call_timer_fn enter] mod_timer() ... timer_shutdown_sync() lock_timer_base() // For now, will not detach the timer but only clear its function to NULL if (base->running_timer != timer) ret = detach_if_pending(timer, base, true); if (shutdown) timer->function = NULL; unlock_timer_base() [call_timer_fn exit] lock_timer_base() base->running_timer = NULL; unlock_timer_base() ... // Now timer is pending while its function set to NULL. // next timer trigger <SOFTIRQ> expire_timers() WARN_ON_ONCE(!fn) // hit ... lock_timer_base() // Now timer will detach if (base->running_timer != timer) ret = detach_if_pending(timer, base, true); if (shutdown) timer->function = NULL; unlock_timer_base() The problem is that timer_shutdown_sync() clears the timer function regardless of whether the timer is currently running. This can leave a pending timer with a NULL function pointer, which triggers the WARN_ON_ONCE(!fn) check in expire_timers(). Fix this by only clearing the timer function when actually detaching the timer. If the timer is running, leave the function pointer intact, which is safe because the timer will be properly detached when it finishes running.

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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: timers: Fix NULL function pointer race in timer_shutdown_sync() There is a race condition between timer_shutdown_sync() and timer expiration that can lead to hitting a WARN_ON in expire_timers(). The issue occurs when timer_shutdown_sync() clears the timer function to NULL while the timer is still running on another CPU. The race scenario looks like this: CPU0 CPU1 <SOFTIRQ> lock_timer_base() expire_timers() base->running_timer = timer; unlock_timer_base() [call_timer_fn enter] mod_timer() ... timer_shutdown_sync() lock_timer_base() // For now, will not detach the timer but only clear its function to NULL if (base->running_timer != timer) ret = detach_if_pending(timer, base, true); if (shutdown) timer->function = NULL; unlock_timer_base() [call_timer_fn exit] lock_timer_base() base->running_timer = NULL; unlock_timer_base() ... // Now timer is pending while its function set to NULL. // next timer trigger <SOFTIRQ> expire_timers() WARN_ON_ONCE(!fn) // hit ... lock_timer_base() // Now timer will detach if (base->running_timer != timer) ret = detach_if_pending(timer, base, true); if (shutdown) timer->function = NULL; unlock_timer_base() The problem is that timer_shutdown_sync() clears the timer function regardless of whether the timer is currently running. This can leave a pending timer with a NULL function pointer, which triggers the WARN_ON_ONCE(!fn) check in expire_timers(). Fix this by only clearing the timer function when actually detaching the timer. If the timer is running, leave the function pointer intact, which is safe because the timer will be properly detached when it finishes running.

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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 → Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') → 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
High: exploitation depends on specific conditions
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-362 ↗

CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'). The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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:H/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.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.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-362
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-3623IBM DataPower Gateway: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM DataPower Gateway ausnutzen, um beliebigen Programmcode auszuführen, erweiterte Berechtigungen zu erlangen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen, einen Denial-of-Service-Zustand auszulösen oder Cross-Site-Scripting-Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2025-2868Linux 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- Bedingung führen oder eine Speicherbeschädigung verursachen können.

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

//www.suse.com/support/update/announcement/2026/suse-su-202623964-1 Bulletin de sécurité SUSE SUSE-SU-2026:23965-1 du 29 septembre 2026 https://www.suse.com/support/update/announcement/2026/suse-su-202623965-1 Bulletin de sécurité SUSE SUSE-SU-2026:23966-1 du 29 septembre 2026 https://www.suse.com/support/update/announcement/2026/suse-su-202623966-1 Bulletin de sécurité SUSE SUSE-SU-2026:23967-1 du 29 septembre 2026 https://www.suse.com/support/update/announcement/2026/suse-su-202623967-1 Bulletin de sécurité SUSE SUSE-SU-2026:23968-1 du 29 septembre 2026 https://www.suse.com/support/update/announcement/2026/suse-su-202623968-1 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68780 https://www.cve.org/CVERecord?id=CVE-2025-68780 Référence CVE CVE-2025-71075 https://www.cve.org/CVERecord?id=CVE-2025-71075 Référence CVE CVE-2026-23113 https://www.cve.org/CVERecord?id=CVE-2026-23113 Référence CVE CVE-2026-23306 https://www.cve.org/CVERecord?id=CVE-2026-23306 Référence CVE CVE-2026-23348 https://www.cve.org/CVERecord?id=CVE-2026-23348 Référence CVE CVE-2026-31418 https://www.cve.org/CVERecord?id=CVE-2026-31418 Référence CVE CVE-2026-31530 https://www.cve.org/CVERecord?id=

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

ouncement/2026/suse-su-20264344-1 Bulletin de sécurité SUSE SUSE-SU-2026:4347-1 du 24 septembre 2026 https://www.suse.com/support/update/announcement/2026/suse-su-20264347-1 Référence CVE CVE-2023-53109 https://www.cve.org/CVERecord?id=CVE-2023-53109 Référence CVE CVE-2024-35973 https://www.cve.org/CVERecord?id=CVE-2024-35973 Référence CVE CVE-2024-57841 https://www.cve.org/CVERecord?id=CVE-2024-57841 Référence CVE CVE-2025-39964 https://www.cve.org/CVERecord?id=CVE-2025-39964 Référence CVE CVE-2025-40022 https://www.cve.org/CVERecord?id=CVE-2025-40022 Référence CVE CVE-2025-40277 https://www.cve.org/CVERecord?id=CVE-2025-40277 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2026-23003 https://www.cve.org/CVERecord?id=CVE-2026-23003 Référence CVE CVE-2026-23443 https://www.cve.org/CVERecord?id=CVE-2026-23443 Référence CVE CVE-2026-23451 https://www.cve.org/CVERecord?id=CVE-2026-23451 Référence CVE CVE-2026-31483 https://www.cve.org/CVERecord?id=CVE-2026-31483 Référence CVE CVE-2026-31502 https://www.cve.org/CVERecord?id=CVE-2026-31502 Référence CVE CVE-2026-43116 https://www.cve.org/CVERecord?id=CVE-2026-43116 Référence CVE CVE-2026-43125 https://www.cve.org/CVERecord?id=CVE-2026-43125 Référence CVE CVE-2026-43134 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-57841 Référence CVE CVE-2025-23137 https://www.cve.org/CVERecord?id=CVE-2025-23137 Référence CVE CVE-2025-38469 https://www.cve.org/CVERecord?id=CVE-2025-38469 Référence CVE CVE-2025-39939 https://www.cve.org/CVERecord?id=CVE-2025-39939 Référence CVE CVE-2025-39964 https://www.cve.org/CVERecord?id=CVE-2025-39964 Référence CVE CVE-2025-40022 https://www.cve.org/CVERecord?id=CVE-2025-40022 Référence CVE CVE-2025-40199 https://www.cve.org/CVERecord?id=CVE-2025-40199 Référence CVE CVE-2025-40204 https://www.cve.org/CVERecord?id=CVE-2025-40204 Référence CVE CVE-2025-68179 https://www.cve.org/CVERecord?id=CVE-2025-68179 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2025-71075 https://www.cve.org/CVERecord?id=CVE-2025-71075 Référence CVE CVE-2025-71104 https://www.cve.org/CVERecord?id=CVE-2025-71104 Référence CVE CVE-2026-23210 https://www.cve.org/CVERecord?id=CVE-2026-23210 Référence CVE CVE-2026-23227 https://www.cve.org/CVERecord?id=CVE-2026-23227 Référence CVE CVE-2026-23230 https://www.cve.org/CVERecord?id=CVE-2026-23230 Référence CVE CVE-2026-23240 https://www.cve.org/CVERecord?id=CVE-2026-23240 Référence CVE CVE-2026-23449 https://www.cve.org/CVERecord?id=CVE-2026-23449 Référence CVE CVE-2026-23454 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-57841 Référence CVE CVE-2025-23137 https://www.cve.org/CVERecord?id=CVE-2025-23137 Référence CVE CVE-2025-38469 https://www.cve.org/CVERecord?id=CVE-2025-38469 Référence CVE CVE-2025-39939 https://www.cve.org/CVERecord?id=CVE-2025-39939 Référence CVE CVE-2025-39964 https://www.cve.org/CVERecord?id=CVE-2025-39964 Référence CVE CVE-2025-40022 https://www.cve.org/CVERecord?id=CVE-2025-40022 Référence CVE CVE-2025-40199 https://www.cve.org/CVERecord?id=CVE-2025-40199 Référence CVE CVE-2025-40204 https://www.cve.org/CVERecord?id=CVE-2025-40204 Référence CVE CVE-2025-68179 https://www.cve.org/CVERecord?id=CVE-2025-68179 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2025-71075 https://www.cve.org/CVERecord?id=CVE-2025-71075 Référence CVE CVE-2025-71104 https://www.cve.org/CVERecord?id=CVE-2025-71104 Référence CVE CVE-2026-23210 https://www.cve.org/CVERecord?id=CVE-2026-23210 Référence CVE CVE-2026-23227 https://www.cve.org/CVERecord?id=CVE-2026-23227 Référence CVE CVE-2026-23230 https://www.cve.org/CVERecord?id=CVE-2026-23230 Référence CVE CVE-2026-23240 https://www.cve.org/CVERecord?id=CVE-2026-23240 Référence CVE CVE-2026-23449 https://www.cve.org/CVERecord?id=CVE-2026-23449 Référence CVE CVE-2026-23454 https://www.cve.org/CVERecord?id=

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

lletin de sécurité Red Hat RHSA-2026:51295 du 06 août 2026 https://access.redhat.com/errata/RHSA-2026:51295 Bulletin de sécurité Red Hat RHSA-2026:51603 du 07 août 2026 https://access.redhat.com/errata/RHSA-2026:51603 Bulletin de sécurité Red Hat RHSA-2026:51604 du 07 août 2026 https://access.redhat.com/errata/RHSA-2026:51604 Référence CVE CVE-2025-10263 https://www.cve.org/CVERecord?id=CVE-2025-10263 Référence CVE CVE-2025-40026 https://www.cve.org/CVERecord?id=CVE-2025-40026 Référence CVE CVE-2025-54518 https://www.cve.org/CVERecord?id=CVE-2025-54518 Référence CVE CVE-2025-68211 https://www.cve.org/CVERecord?id=CVE-2025-68211 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2026-23199 https://www.cve.org/CVERecord?id=CVE-2026-23199 Référence CVE CVE-2026-23415 https://www.cve.org/CVERecord?id=CVE-2026-23415 Référence CVE CVE-2026-31692 https://www.cve.org/CVERecord?id=CVE-2026-31692 Référence CVE CVE-2026-31787 https://www.cve.org/CVERecord?id=CVE-2026-31787 Référence CVE CVE-2026-43116 https://www.cve.org/CVERecord?id=CVE-2026-43116 Référence CVE CVE-2026-43186 https://www.cve.org/CVERecord?id=CVE-2026-43186 Référence CVE CVE-2026-43450 https://www.cve.org/CVERecord?id=CVE-2026-43450 Référence CVE CVE-2026-45984 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40103 Référence CVE CVE-2025-40135 https://www.cve.org/CVERecord?id=CVE-2025-40135 Référence CVE CVE-2025-40150 https://www.cve.org/CVERecord?id=CVE-2025-40150 Référence CVE CVE-2025-40323 https://www.cve.org/CVERecord?id=CVE-2025-40323 Référence CVE CVE-2025-54505 https://www.cve.org/CVERecord?id=CVE-2025-54505 Référence CVE CVE-2025-54518 https://www.cve.org/CVERecord?id=CVE-2025-54518 Référence CVE CVE-2025-62626 https://www.cve.org/CVERecord?id=CVE-2025-62626 Référence CVE CVE-2025-68175 https://www.cve.org/CVERecord?id=CVE-2025-68175 Référence CVE CVE-2025-68206 https://www.cve.org/CVERecord?id=CVE-2025-68206 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2025-68239 https://www.cve.org/CVERecord?id=CVE-2025-68239 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68263 https://www.cve.org/CVERecord?id=CVE-2025-68263 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68334 https://www.cve.org/CVERecord?id=CVE-2025-68334 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68736 https://www.cve.org/CVERecord?id=CVE-2025-68736 Référence CVE CVE-2025-71089 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-48816 Référence CVE CVE-2023-52646 https://www.cve.org/CVERecord?id=CVE-2023-52646 Référence CVE CVE-2023-53673 https://www.cve.org/CVERecord?id=CVE-2023-53673 Référence CVE CVE-2024-56643 https://www.cve.org/CVERecord?id=CVE-2024-56643 Référence CVE CVE-2025-37778 https://www.cve.org/CVERecord?id=CVE-2025-37778 Référence CVE CVE-2025-37822 https://www.cve.org/CVERecord?id=CVE-2025-37822 Référence CVE CVE-2025-37924 https://www.cve.org/CVERecord?id=CVE-2025-37924 Référence CVE CVE-2025-38201 https://www.cve.org/CVERecord?id=CVE-2025-38201 Référence CVE CVE-2025-40082 https://www.cve.org/CVERecord?id=CVE-2025-40082 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2025-68263 https://www.cve.org/CVERecord?id=CVE-2025-68263 Référence CVE CVE-2025-71089 https://www.cve.org/CVERecord?id=CVE-2025-71089 Référence CVE CVE-2025-71220 https://www.cve.org/CVERecord?id=CVE-2025-71220 Référence CVE CVE-2025-71222 https://www.cve.org/CVERecord?id=CVE-2025-71222 Référence CVE CVE-2025-71224 https://www.cve.org/CVERecord?id=CVE-2025-71224 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-23176 https://www.cve.org/CVERecord?id=CVE-2026-23176 Référence CVE CVE-2026-23180 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-50060 Référence CVE CVE-2024-56643 https://www.cve.org/CVERecord?id=CVE-2024-56643 Référence CVE CVE-2025-37778 https://www.cve.org/CVERecord?id=CVE-2025-37778 Référence CVE CVE-2025-37822 https://www.cve.org/CVERecord?id=CVE-2025-37822 Référence CVE CVE-2025-37924 https://www.cve.org/CVERecord?id=CVE-2025-37924 Référence CVE CVE-2025-38201 https://www.cve.org/CVERecord?id=CVE-2025-38201 Référence CVE CVE-2025-40005 https://www.cve.org/CVERecord?id=CVE-2025-40005 Référence CVE CVE-2025-40082 https://www.cve.org/CVERecord?id=CVE-2025-40082 Référence CVE CVE-2025-54505 https://www.cve.org/CVERecord?id=CVE-2025-54505 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2025-68263 https://www.cve.org/CVERecord?id=CVE-2025-68263 Référence CVE CVE-2025-71088 https://www.cve.org/CVERecord?id=CVE-2025-71088 Référence CVE CVE-2025-71089 https://www.cve.org/CVERecord?id=CVE-2025-71089 Référence CVE CVE-2025-71090 https://www.cve.org/CVERecord?id=CVE-2025-71090 Référence CVE CVE-2025-71127 https://www.cve.org/CVERecord?id=CVE-2025-71127 Référence CVE CVE-2025-71134 https://www.cve.org/CVERecord?id=CVE-2025-71134 Référence CVE CVE-2025-71141 https://www.cve.org/CVERecord?id=CVE-2025-71141 Référence CVE CVE-2025-71142 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-37924 Référence CVE CVE-2025-37926 https://www.cve.org/CVERecord?id=CVE-2025-37926 Référence CVE CVE-2025-38201 https://www.cve.org/CVERecord?id=CVE-2025-38201 Référence CVE CVE-2025-38591 https://www.cve.org/CVERecord?id=CVE-2025-38591 Référence CVE CVE-2025-40005 https://www.cve.org/CVERecord?id=CVE-2025-40005 Référence CVE CVE-2025-40039 https://www.cve.org/CVERecord?id=CVE-2025-40039 Référence CVE CVE-2025-40082 https://www.cve.org/CVERecord?id=CVE-2025-40082 Référence CVE CVE-2025-40149 https://www.cve.org/CVERecord?id=CVE-2025-40149 Référence CVE CVE-2025-54505 https://www.cve.org/CVERecord?id=CVE-2025-54505 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2025-68263 https://www.cve.org/CVERecord?id=CVE-2025-68263 Référence CVE CVE-2025-68351 https://www.cve.org/CVERecord?id=CVE-2025-68351 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68725 https://www.cve.org/CVERecord?id=CVE-2025-68725 Référence CVE CVE-2025-68749 https://www.cve.org/CVERecord?id=CVE-2025-68749 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68823 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68194 Référence CVE CVE-2025-68198 https://www.cve.org/CVERecord?id=CVE-2025-68198 Référence CVE CVE-2025-68200 https://www.cve.org/CVERecord?id=CVE-2025-68200 Référence CVE CVE-2025-68201 https://www.cve.org/CVERecord?id=CVE-2025-68201 Référence CVE CVE-2025-68204 https://www.cve.org/CVERecord?id=CVE-2025-68204 Référence CVE CVE-2025-68206 https://www.cve.org/CVERecord?id=CVE-2025-68206 Référence CVE CVE-2025-68208 https://www.cve.org/CVERecord?id=CVE-2025-68208 Référence CVE CVE-2025-68211 https://www.cve.org/CVERecord?id=CVE-2025-68211 Référence CVE CVE-2025-68213 https://www.cve.org/CVERecord?id=CVE-2025-68213 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2025-68217 https://www.cve.org/CVERecord?id=CVE-2025-68217 Référence CVE CVE-2025-68218 https://www.cve.org/CVERecord?id=CVE-2025-68218 Référence CVE CVE-2025-68219 https://www.cve.org/CVERecord?id=CVE-2025-68219 Référence CVE CVE-2025-68220 https://www.cve.org/CVERecord?id=CVE-2025-68220 Référence CVE CVE-2025-68222 https://www.cve.org/CVERecord?id=CVE-2025-68222 Référence CVE CVE-2025-68223 https://www.cve.org/CVERecord?id=CVE-2025-68223 Référence CVE CVE-2025-68227 https://www.cve.org/CVERecord?id=CVE-2025-68227 Référence CVE CVE-2025-68229 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68194 Référence CVE CVE-2025-68198 https://www.cve.org/CVERecord?id=CVE-2025-68198 Référence CVE CVE-2025-68200 https://www.cve.org/CVERecord?id=CVE-2025-68200 Référence CVE CVE-2025-68201 https://www.cve.org/CVERecord?id=CVE-2025-68201 Référence CVE CVE-2025-68204 https://www.cve.org/CVERecord?id=CVE-2025-68204 Référence CVE CVE-2025-68208 https://www.cve.org/CVERecord?id=CVE-2025-68208 Référence CVE CVE-2025-68211 https://www.cve.org/CVERecord?id=CVE-2025-68211 Référence CVE CVE-2025-68212 https://www.cve.org/CVERecord?id=CVE-2025-68212 Référence CVE CVE-2025-68213 https://www.cve.org/CVERecord?id=CVE-2025-68213 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2025-68215 https://www.cve.org/CVERecord?id=CVE-2025-68215 Référence CVE CVE-2025-68217 https://www.cve.org/CVERecord?id=CVE-2025-68217 Référence CVE CVE-2025-68218 https://www.cve.org/CVERecord?id=CVE-2025-68218 Référence CVE CVE-2025-68219 https://www.cve.org/CVERecord?id=CVE-2025-68219 Référence CVE CVE-2025-68220 https://www.cve.org/CVERecord?id=CVE-2025-68220 Référence CVE CVE-2025-68221 https://www.cve.org/CVERecord?id=CVE-2025-68221 Référence CVE CVE-2025-68222 https://www.cve.org/CVERecord?id=CVE-2025-68222 Référence CVE CVE-2025-68223 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68192 Référence CVE CVE-2025-68194 https://www.cve.org/CVERecord?id=CVE-2025-68194 Référence CVE CVE-2025-68198 https://www.cve.org/CVERecord?id=CVE-2025-68198 Référence CVE CVE-2025-68200 https://www.cve.org/CVERecord?id=CVE-2025-68200 Référence CVE CVE-2025-68201 https://www.cve.org/CVERecord?id=CVE-2025-68201 Référence CVE CVE-2025-68204 https://www.cve.org/CVERecord?id=CVE-2025-68204 Référence CVE CVE-2025-68208 https://www.cve.org/CVERecord?id=CVE-2025-68208 Référence CVE CVE-2025-68212 https://www.cve.org/CVERecord?id=CVE-2025-68212 Référence CVE CVE-2025-68213 https://www.cve.org/CVERecord?id=CVE-2025-68213 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2025-68215 https://www.cve.org/CVERecord?id=CVE-2025-68215 Référence CVE CVE-2025-68217 https://www.cve.org/CVERecord?id=CVE-2025-68217 Référence CVE CVE-2025-68218 https://www.cve.org/CVERecord?id=CVE-2025-68218 Référence CVE CVE-2025-68219 https://www.cve.org/CVERecord?id=CVE-2025-68219 Référence CVE CVE-2025-68220 https://www.cve.org/CVERecord?id=CVE-2025-68220 Référence CVE CVE-2025-68221 https://www.cve.org/CVERecord?id=CVE-2025-68221 Référence CVE CVE-2025-68222 https://www.cve.org/CVERecord?id=CVE-2025-68222 Référence CVE CVE-2025-68223 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68192 Référence CVE CVE-2025-68194 https://www.cve.org/CVERecord?id=CVE-2025-68194 Référence CVE CVE-2025-68198 https://www.cve.org/CVERecord?id=CVE-2025-68198 Référence CVE CVE-2025-68200 https://www.cve.org/CVERecord?id=CVE-2025-68200 Référence CVE CVE-2025-68201 https://www.cve.org/CVERecord?id=CVE-2025-68201 Référence CVE CVE-2025-68204 https://www.cve.org/CVERecord?id=CVE-2025-68204 Référence CVE CVE-2025-68208 https://www.cve.org/CVERecord?id=CVE-2025-68208 Référence CVE CVE-2025-68212 https://www.cve.org/CVERecord?id=CVE-2025-68212 Référence CVE CVE-2025-68213 https://www.cve.org/CVERecord?id=CVE-2025-68213 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2025-68215 https://www.cve.org/CVERecord?id=CVE-2025-68215 Référence CVE CVE-2025-68217 https://www.cve.org/CVERecord?id=CVE-2025-68217 Référence CVE CVE-2025-68218 https://www.cve.org/CVERecord?id=CVE-2025-68218 Référence CVE CVE-2025-68219 https://www.cve.org/CVERecord?id=CVE-2025-68219 Référence CVE CVE-2025-68220 https://www.cve.org/CVERecord?id=CVE-2025-68220 Référence CVE CVE-2025-68221 https://www.cve.org/CVERecord?id=CVE-2025-68221 Référence CVE CVE-2025-68222 https://www.cve.org/CVERecord?id=CVE-2025-68222 Référence CVE CVE-2025-68223 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68192 Référence CVE CVE-2025-68194 https://www.cve.org/CVERecord?id=CVE-2025-68194 Référence CVE CVE-2025-68198 https://www.cve.org/CVERecord?id=CVE-2025-68198 Référence CVE CVE-2025-68200 https://www.cve.org/CVERecord?id=CVE-2025-68200 Référence CVE CVE-2025-68201 https://www.cve.org/CVERecord?id=CVE-2025-68201 Référence CVE CVE-2025-68204 https://www.cve.org/CVERecord?id=CVE-2025-68204 Référence CVE CVE-2025-68208 https://www.cve.org/CVERecord?id=CVE-2025-68208 Référence CVE CVE-2025-68212 https://www.cve.org/CVERecord?id=CVE-2025-68212 Référence CVE CVE-2025-68213 https://www.cve.org/CVERecord?id=CVE-2025-68213 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2025-68215 https://www.cve.org/CVERecord?id=CVE-2025-68215 Référence CVE CVE-2025-68217 https://www.cve.org/CVERecord?id=CVE-2025-68217 Référence CVE CVE-2025-68218 https://www.cve.org/CVERecord?id=CVE-2025-68218 Référence CVE CVE-2025-68219 https://www.cve.org/CVERecord?id=CVE-2025-68219 Référence CVE CVE-2025-68220 https://www.cve.org/CVERecord?id=CVE-2025-68220 Référence CVE CVE-2025-68221 https://www.cve.org/CVERecord?id=CVE-2025-68221 Référence CVE CVE-2025-68222 https://www.cve.org/CVERecord?id=CVE-2025-68222 Référence CVE CVE-2025-68223 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-68192 Référence CVE CVE-2025-68193 https://www.cve.org/CVERecord?id=CVE-2025-68193 Référence CVE CVE-2025-68194 https://www.cve.org/CVERecord?id=CVE-2025-68194 Référence CVE CVE-2025-68196 https://www.cve.org/CVERecord?id=CVE-2025-68196 Référence CVE CVE-2025-68200 https://www.cve.org/CVERecord?id=CVE-2025-68200 Référence CVE CVE-2025-68201 https://www.cve.org/CVERecord?id=CVE-2025-68201 Référence CVE CVE-2025-68204 https://www.cve.org/CVERecord?id=CVE-2025-68204 Référence CVE CVE-2025-68206 https://www.cve.org/CVERecord?id=CVE-2025-68206 Référence CVE CVE-2025-68211 https://www.cve.org/CVERecord?id=CVE-2025-68211 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2025-68217 https://www.cve.org/CVERecord?id=CVE-2025-68217 Référence CVE CVE-2025-68219 https://www.cve.org/CVERecord?id=CVE-2025-68219 Référence CVE CVE-2025-68220 https://www.cve.org/CVERecord?id=CVE-2025-68220 Référence CVE CVE-2025-68223 https://www.cve.org/CVERecord?id=CVE-2025-68223 Référence CVE CVE-2025-68227 https://www.cve.org/CVERecord?id=CVE-2025-68227 Référence CVE CVE-2025-68229 https://www.cve.org/CVERecord?id=CVE-2025-68229 Référence CVE CVE-2025-68230 https://www.cve.org/CVERecord?id=CVE-2025-68230 Référence CVE CVE-2025-68231 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-68192 Référence CVE CVE-2025-68193 https://www.cve.org/CVERecord?id=CVE-2025-68193 Référence CVE CVE-2025-68194 https://www.cve.org/CVERecord?id=CVE-2025-68194 Référence CVE CVE-2025-68196 https://www.cve.org/CVERecord?id=CVE-2025-68196 Référence CVE CVE-2025-68200 https://www.cve.org/CVERecord?id=CVE-2025-68200 Référence CVE CVE-2025-68201 https://www.cve.org/CVERecord?id=CVE-2025-68201 Référence CVE CVE-2025-68204 https://www.cve.org/CVERecord?id=CVE-2025-68204 Référence CVE CVE-2025-68206 https://www.cve.org/CVERecord?id=CVE-2025-68206 Référence CVE CVE-2025-68211 https://www.cve.org/CVERecord?id=CVE-2025-68211 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2025-68217 https://www.cve.org/CVERecord?id=CVE-2025-68217 Référence CVE CVE-2025-68219 https://www.cve.org/CVERecord?id=CVE-2025-68219 Référence CVE CVE-2025-68220 https://www.cve.org/CVERecord?id=CVE-2025-68220 Référence CVE CVE-2025-68223 https://www.cve.org/CVERecord?id=CVE-2025-68223 Référence CVE CVE-2025-68227 https://www.cve.org/CVERecord?id=CVE-2025-68227 Référence CVE CVE-2025-68229 https://www.cve.org/CVERecord?id=CVE-2025-68229 Référence CVE CVE-2025-68230 https://www.cve.org/CVERecord?id=CVE-2025-68230 Référence CVE CVE-2025-68231 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68173 Référence CVE CVE-2025-68176 https://www.cve.org/CVERecord?id=CVE-2025-68176 Référence CVE CVE-2025-68177 https://www.cve.org/CVERecord?id=CVE-2025-68177 Référence CVE CVE-2025-68185 https://www.cve.org/CVERecord?id=CVE-2025-68185 Référence CVE CVE-2025-68191 https://www.cve.org/CVERecord?id=CVE-2025-68191 Référence CVE CVE-2025-68192 https://www.cve.org/CVERecord?id=CVE-2025-68192 Référence CVE CVE-2025-68194 https://www.cve.org/CVERecord?id=CVE-2025-68194 Référence CVE CVE-2025-68200 https://www.cve.org/CVERecord?id=CVE-2025-68200 Référence CVE CVE-2025-68204 https://www.cve.org/CVERecord?id=CVE-2025-68204 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2025-68217 https://www.cve.org/CVERecord?id=CVE-2025-68217 Référence CVE CVE-2025-68218 https://www.cve.org/CVERecord?id=CVE-2025-68218 Référence CVE CVE-2025-68220 https://www.cve.org/CVERecord?id=CVE-2025-68220 Référence CVE CVE-2025-68227 https://www.cve.org/CVERecord?id=CVE-2025-68227 Référence CVE CVE-2025-68229 https://www.cve.org/CVERecord?id=CVE-2025-68229 Référence CVE CVE-2025-68231 https://www.cve.org/CVERecord?id=CVE-2025-68231 Référence CVE CVE-2025-68233 https://www.cve.org/CVERecord?id=CVE-2025-68233 Référence CVE CVE-2025-68237 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-026160LinuxのLinux Kernelにおける競合状態に関する脆弱性

Linuxカーネルにおいて、timer_shutdown_sync()関数の競合状態によりNULL関数ポインタが設定され、expire_timers()でエラーが発生する脆弱性が修正されました。timer_shutdown_sync()はタイマーが実行中であっても関数をNULLにクリアしていましたが、これにより有効なタイマー関数を失い、WARN_ONが発生していました。修正では、タイマーを分離する必要がある場合にのみ関数をNULLに設定し、実行中のタイマー関数を維持するように改善しました。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 6.2, 6.1.159 ≤ 6.1.*, 6.6.118 ≤ 6.6.*, 6.12.60 ≤ 6.12.*, 6.17.10 ≤ 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 16 Dec 2025 · Last source change 23 May 2026, 16:02 UTC · CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

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

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    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 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 Desktop 15 SP7; kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7; cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP3; ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP6; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP6; cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7; ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0; kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0; 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; and 360 more · Fixed: cluster-md-kmp-default-6.4.0-150600.23.135.1 as component of SUSE Linux Enterprise Server 15 SP6-LTSS; dlm-kmp-default-6.4.0-150600.23.135.1 as component of SUSE Linux Enterprise Server 15 SP6-LTSS; gfs2-kmp-default-6.4.0-150600.23.135.1 as component of SUSE Linux Enterprise Server 15 SP6-LTSS; kernel-64kb-6.4.0-150600.23.135.1 as component of SUSE Linux Enterprise Server 15 SP6-LTSS; kernel-64kb-devel-6.4.0-150600.23.135.1 as component of SUSE Linux Enterprise Server 15 SP6-LTSS; kernel-default-6.4.0-150600.23.135.1 as component of SUSE Linux Enterprise Server 15 SP6-LTSS; kernel-default-base-6.4.0-150600.23.135.1.150600.12.62.4 as component of SUSE Linux Enterprise Server 15 SP6-LTSS; kernel-default-devel-6.4.0-150600.23.135.1 as component of SUSE Linux Enterprise Server 15 SP6-LTSS; kernel-devel-6.4.0-150600.23.135.1 as component of SUSE Linux Enterprise Server 15 SP6-LTSS; kernel-docs-6.4.0-150600.23.135.1 as component of SUSE Linux Enterprise Server 15 SP6-LTSS; kernel-macros-6.4.0-150600.23.135.1 as component of SUSE Linux Enterprise Server 15 SP6-LTSS; kernel-obs-build-6.4.0-150600.23.135.1 as component of SUSE Linux Enterprise Server 15 SP6-LTSS; kernel-source-6.4.0-150600.23.135.1 as component of SUSE Linux Enterprise Server 15 SP6-LTSS; kernel-syms-6.4.0-150600.23.135.1 as component of SUSE Linux Enterprise Server 15 SP6-LTSS; kernel-zfcpdump-6.4.0-150600.23.135.1 as component of SUSE Linux Enterprise Server 15 SP6-LTSS; ocfs2-kmp-default-6.4.0-150600.23.135.1 as component of SUSE Linux Enterprise Server 15 SP6-LTSS; reiserfs-kmp-default-6.4.0-150600.23.135.1 as component of SUSE Linux Enterprise Server 15 SP6-LTSS; kernel-64kb-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-64kb-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-64kb-extra-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-azure-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-azure-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-azure-extra-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-azure-vdso-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-default-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-default-base-6.12.0-160000.38.1.160000.2.24 as component of SUSE Linux Enterprise Server 16.0; kernel-default-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-default-extra-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-default-livepatch-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-default-vdso-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; and 69 more
    After
    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 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 Desktop 15 SP7; kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7; kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7; cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP3; ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP6; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP6; cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7; ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7; kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0; kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0; 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; and 327 more
    SUSE Product Security Team ↗
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-203682↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update 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-68214 · cve.blacktree.nl