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

futex: Prevent use-after-free during requeue-PI

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 30 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 8 Sep 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.15% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 30 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.57-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.158-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.16.10-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.16.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.

3 current
CVE-2025-39977 · CSAF 2.0 · revision 57 · interimSUSE Product Security TeamCVE-2025-39977
62 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default as component of SUSE Linux Enterprise Module for Basesystem 15 SP6
  • kernel-default-devel as component of SUSE Linux Enterprise Module for Basesystem 15 SP6
  • kernel-devel as component of SUSE Linux Enterprise Module for Basesystem 15 SP6
  • kernel-macros as component of SUSE Linux Enterprise Module for Basesystem 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Module for Basesystem 15 SP6
  • kernel-default as component of SUSE Linux Enterprise Module for Development Tools 15 SP6
Summary
In the Linux kernel, the following vulnerability has been resolved: futex: Prevent use-after-free during requeue-PI syzbot managed to trigger the following race: T1 T2 futex_wait_requeue_pi() futex_do_wait() schedule() futex_requeue() futex_proxy_trylock_atomic() futex_requeue_pi_prepare() requeue_pi_wake_futex() futex_requeue_pi_complete() /* preempt */ * timeout/ signal wakes T1 * futex_requeue_pi_wakeup_sync() // Q_REQUEUE_PI_LOCKED futex_hash_put() // back to userland, on stack futex_q is garbage /* back */ wake_up_state(q->task, TASK_NORMAL); In this scenario futex_wait_requeue_pi() is able to leave without using futex_q::lock_ptr for synchronization. This can be prevented by reading futex_q::task before updating the futex_q::requeue_state. A reference on the task_struct is not needed because requeue_pi_wake_futex() is invoked with a spinlock_t held which implies a RCU read section. Even if T1 terminates immediately after, the task_struct will remain valid during T2's wake_up_state(). A READ_ONCE on futex_q::task before futex_requeue_pi_complete() is enough because it ensures that the variable is read before the state is updated. Read futex_q::task before updating the requeue state, use it for the following wakeup.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
SSA-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
In the Linux kernel, the following vulnerability has been resolved: futex: Prevent use-after-free during requeue-PI syzbot managed to trigger the following race: T1 T2 futex_wait_requeue_pi() futex_do_wait() schedule() futex_requeue() futex_proxy_trylock_atomic() futex_requeue_pi_prepare() requeue_pi_wake_futex() futex_requeue_pi_complete() /* preempt */ * timeout/ signal wakes T1 * futex_requeue_pi_wakeup_sync() // Q_REQUEUE_PI_LOCKED futex_hash_put() // back to userland, on stack futex_q is garbage /* back */ wake_up_state(q->task, TASK_NORMAL); In this scenario futex_wait_requeue_pi() is able to leave without using futex_q::lock_ptr for synchronization. This can be prevented by reading futex_q::task before updating the futex_q::requeue_state. A reference on the task_struct is not needed because requeue_pi_wake_futex() is invoked with a spinlock_t held which implies a RCU read section. Even if T1 terminates immediately after, the task_struct will remain valid during T2's wake_up_state(). A READ_ONCE on futex_q::task before futex_requeue_pi_complete() is enough because it ensures that the variable is read before the state is updated. Read futex_q::task before updating the requeue state, use it for the following wakeup.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
SSA-082556 · CSAF 2.0 · revision 7 · interimSiemens ProductCERTSSA-082556: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.5
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.5
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.5
Summary
In the Linux kernel, the following vulnerability has been resolved: futex: Prevent use-after-free during requeue-PI syzbot managed to trigger the following race: T1 T2 futex_wait_requeue_pi() futex_do_wait() schedule() futex_requeue() futex_proxy_trylock_atomic() futex_requeue_pi_prepare() requeue_pi_wake_futex() futex_requeue_pi_complete() /* preempt */ * timeout/ signal wakes T1 * futex_requeue_pi_wakeup_sync() // Q_REQUEUE_PI_LOCKED futex_hash_put() // back to userland, on stack futex_q is garbage /* back */ wake_up_state(q->task, TASK_NORMAL); In this scenario futex_wait_requeue_pi() is able to leave without using futex_q::lock_ptr for synchronization. This can be prevented by reading futex_q::task before updating the futex_q::requeue_state. A reference on the task_struct is not needed because requeue_pi_wake_futex() is invoked with a spinlock_t held which implies a RCU read section. Even if T1 terminates immediately after, the task_struct will remain valid during T2's wake_up_state(). A READ_ONCE on futex_q::task before futex_requeue_pi_complete() is enough because it ensures that the variable is read before the state is updated. Read futex_q::task before updating the requeue state, use it for the following wakeup.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
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-34595

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: futex: Prevent use-after-free during requeue-PI syzbot managed to trigger the following race: T1 T2 futex_wait_requeue_pi() futex_do_wait() schedule() futex_requeue() futex_proxy_trylock_atomic() futex_requeue_pi_prepare() requeue_pi_wake_futex() futex_requeue_pi_complete() /* preempt */ * timeout/ signal wakes T1 * futex_requeue_pi_wakeup_sync() // Q_REQUEUE_PI_LOCKED futex_hash_put() // back to userland, on stack futex_q is garbage /* back */ wake_up_state(q->task, TASK_NORMAL); In this scenario futex_wait_requeue_pi() is able to leave without using futex_q::lock_ptr for synchronization. This can be prevented by reading futex_q::task before updating the futex_q::requeue_state. A reference on the task_struct is not needed because requeue_pi_wake_futex() is invoked with a spinlock_t held which implies a RCU read section. Even if T1 terminates immediately after, the task_struct will remain valid during T2's wake_up_state(). A READ_ONCE on futex_q::task before futex_requeue_pi_complete() is enough because it ensures that the variable is read before the state is updated. Read futex_q::task before updating the requeue state, use it for the following wakeup.

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 30 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: futex: Prevent use-after-free during requeue-PI syzbot managed to trigger the following race: T1 T2 futex_wait_requeue_pi() futex_do_wait() schedule() futex_requeue() futex_proxy_trylock_atomic() futex_requeue_pi_prepare() requeue_pi_wake_futex() futex_requeue_pi_complete() /* preempt */ * timeout/ signal wakes T1 * futex_requeue_pi_wakeup_sync() // Q_REQUEUE_PI_LOCKED futex_hash_put() // back to userland, on stack futex_q is garbage /* back */ wake_up_state(q->task, TASK_NORMAL); In this scenario futex_wait_requeue_pi() is able to leave without using futex_q::lock_ptr for synchronization. This can be prevented by reading futex_q::task before updating the futex_q::requeue_state. A reference on the task_struct is not needed because requeue_pi_wake_futex() is invoked with a spinlock_t held which implies a RCU read section. Even if T1 terminates immediately after, the task_struct will remain valid during T2's wake_up_state(). A READ_ONCE on futex_q::task before futex_requeue_pi_complete() is enough because it ensures that the variable is read before the state is updated. Read futex_q::task before updating the requeue state, use it for the following wakeup.

What

In the Linux kernel, the following vulnerability has been resolved: futex: Prevent use-after-free during requeue-PI syzbot managed to trigger the following race: T1 T2 futex_wait_requeue_pi() futex_do_wait() schedule() futex_requeue() futex_proxy_trylock_atomic() futex_requeue_pi_prepare() requeue_pi_wake_futex() futex_requeue_pi_complete() /* preempt */ * timeout/ signal wakes T1 * futex_requeue_pi_wakeup_sync() // Q_REQUEUE_PI_LOCKED futex_hash_put() // back to userland, on stack futex_q is garbage /* back */ wake_up_state(q->task, TASK_NORMAL); In this scenario futex_wait_requeue_pi() is able to leave without using futex_q::lock_ptr for synchronization. This can be prevented by reading futex_q::task before updating the futex_q::requeue_state. A reference on the task_struct is not needed because requeue_pi_wake_futex() is invoked with a spinlock_t held which implies a RCU read section. Even if T1 terminates immediately after, the task_struct will remain valid during T2's wake_up_state(). A READ_ONCE on futex_q::task before futex_requeue_pi_complete() is enough because it ensures that the variable is read before the state is updated. Read futex_q::task before updating the requeue state, use it for the following wakeup.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

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

What

In the Linux kernel, the following vulnerability has been resolved: futex: Prevent use-after-free during requeue-PI syzbot managed to trigger the following race: T1 T2 futex_wait_requeue_pi() futex_do_wait() schedule() futex_requeue() futex_proxy_trylock_atomic() futex_requeue_pi_prepare() requeue_pi_wake_futex() futex_requeue_pi_complete() /* preempt */ * timeout/ signal wakes T1 * futex_requeue_pi_wakeup_sync() // Q_REQUEUE_PI_LOCKED futex_hash_put() // back to userland, on stack futex_q is garbage /* back */ wake_up_state(q->task, TASK_NORMAL); In this scenario futex_wait_requeue_pi() is able to leave without using futex_q::lock_ptr for synchronization. This can be prevented by reading futex_q::task before updating the futex_q::requeue_state. A reference on the task_struct is not needed because requeue_pi_wake_futex() is invoked with a spinlock_t held which implies a RCU read section. Even if T1 terminates immediately after, the task_struct will remain valid during T2's wake_up_state(). A READ_ONCE on futex_q::task before futex_requeue_pi_complete() is enough because it ensures that the variable is read before the state is updated. Read futex_q::task before updating the requeue state, use it for the following wakeup.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

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

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

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

ENISA EUVD · EUVD-2025-34595Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: futex: Prevent use-after-free during requeue-PI syzbot managed to trigger the following race: T1 T2 futex_wait_requeue_pi() futex_do_wait() schedule() futex_requeue() futex_proxy_trylock_atomic() futex_requeue_pi_prepare() requeue_pi_wake_futex() futex_requeue_pi_complete() /* preempt */ * timeout/ signal wakes T1 * futex_requeue_pi_wakeup_sync() // Q_REQUEUE_PI_LOCKED futex_hash_put() // back to userland, on stack futex_q is garbage /* back */ wake_up_state(q->task, TASK_NORMAL); In this scenario futex_wait_requeue_pi() is able to leave without using futex_q::lock_ptr for synchronization. This can be prevented by reading futex_q::task before updating the futex_q::requeue_state. A reference on the task_struct is not needed because requeue_pi_wake_futex() is invoked with a spinlock_t held which implies a RCU read section. Even if T1 terminates immediately after, the task_struct will remain valid during T2's wake_up_state(). A READ_ONCE on futex_q::task before futex_requeue_pi_complete() is enough because it ensures that the variable is read before the state is updated. Read futex_q::task before updating the requeue state, use it for the following wakeup.

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

Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen, Daten zu manipulieren und andere, nicht näher spezifizierte Angriffe durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20251022Security Bulletin 22 Oct 2025

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

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

25-37909, CVE-2025-37917, CVE-2025-37945, CVE-2025-37959, CVE-2025-37964, CVE-2025-37972, CVE-2025-37980, CVE-2025-38125, CVE-2025-38162, CVE-2025-38192, CVE-2025-38201, CVE-2025-38232, CVE-2025-38322, CVE-2025-38591, CVE-2025-38614, CVE-2025-38681, CVE-2025-38704, CVE-2025-38721, CVE-2025-38725, CVE-2025-38727, CVE-2025-38732, CVE-2025-38736, CVE-2025-39681, CVE-2025-39691, CVE-2025-39721, CVE-2025-39748, CVE-2025-39756, CVE-2025-39764, CVE-2025-39770, CVE-2025-39773, CVE-2025-39782, CVE-2025-39795, CVE-2025-39826, CVE-2025-39827, CVE-2025-39845, CVE-2025-39866, CVE-2025-39871, CVE-2025-39931, CVE-2025-39953, CVE-2025-39955, CVE-2025-39964, CVE-2025-39977, CVE-2025-39978, CVE-2025-39980, CVE-2025-40022, CVE-2025-40070, CVE-2025-40078, CVE-2025-40080, CVE-2025-40105, CVE-2025-40135, CVE-2025-40149, CVE-2025-40219, CVE-2025-40261, CVE-2025-40300, CVE-2025-61984, CVE-2025-61985, CVE-2025-68206, CVE-2025-68261, CVE-2025-68264, CVE-2025-68265, CVE-2025-68266, CVE-2025-68291, CVE-2025-68337, CVE-2025-68349, CVE-2025-68363, CVE-2025-68371, CVE-2025-68724, CVE-2025-68725, CVE-2025-68742, CVE-2025-68764, CVE-2025-68773, CVE-2025-68776, CVE-2025-68782, CVE-2025-68787, CVE-2025-68788, CVE-2025-68798, CVE-2025-68803, CVE-2025-68814, CVE-2025-68816, CVE-2025-68818, CVE-2025-68820, CVE-2025-71064, CVE-2025

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Elles permettent à un attaquant de provoquer un déni de service et un problème de sécurité non spécifié par l'éditeur.

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

d?id=CVE-2025-39961 Référence CVE CVE-2025-39965 https://www.cve.org/CVERecord?id=CVE-2025-39965 Référence CVE CVE-2025-39967 https://www.cve.org/CVERecord?id=CVE-2025-39967 Référence CVE CVE-2025-39968 https://www.cve.org/CVERecord?id=CVE-2025-39968 Référence CVE CVE-2025-39969 https://www.cve.org/CVERecord?id=CVE-2025-39969 Référence CVE CVE-2025-39970 https://www.cve.org/CVERecord?id=CVE-2025-39970 Référence CVE CVE-2025-39971 https://www.cve.org/CVERecord?id=CVE-2025-39971 Référence CVE CVE-2025-39972 https://www.cve.org/CVERecord?id=CVE-2025-39972 Référence CVE CVE-2025-39973 https://www.cve.org/CVERecord?id=CVE-2025-39973 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=CVE-2025-39977 Référence CVE CVE-2025-39978 https://www.cve.org/CVERecord?id=CVE-2025-39978 Référence CVE CVE-2025-39980 https://www.cve.org/CVERecord?id=CVE-2025-39980 Référence CVE CVE-2025-39981 https://www.cve.org/CVERecord?id=CVE-2025-39981 Référence CVE CVE-2025-39982 https://www.cve.org/CVERecord?id=CVE-2025-39982 Référence CVE CVE-2025-39985 https://www.cve.org/CVERecord?id=CVE-2025-39985 Référence CVE CVE-2025-39986 https://www.cve.org/CVERecord?id=CVE-2025-39986 Référence CVE CVE-2025-39987 https://www.cve.org/CVERecord?id=CVE-2025-39987 Référence CVE CVE-2025-39988 https://www.cve.org/CVERecord?id=

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

use.com/support/update/announcement/2026/suse-su-20261724-1 Bulletin de sécurité SUSE SUSE-SU-2026:1725-1 du 06 mai 2026 https://www.suse.com/support/update/announcement/2026/suse-su-20261725-1 Bulletin de sécurité SUSE SUSE-SU-2026:1726-1 du 06 mai 2026 https://www.suse.com/support/update/announcement/2026/suse-su-20261726-1 Référence CVE CVE-2024-26584 https://www.cve.org/CVERecord?id=CVE-2024-26584 Référence CVE CVE-2025-38234 https://www.cve.org/CVERecord?id=CVE-2025-38234 Référence CVE CVE-2025-38375 https://www.cve.org/CVERecord?id=CVE-2025-38375 Référence CVE CVE-2025-39759 https://www.cve.org/CVERecord?id=CVE-2025-39759 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=CVE-2025-39977 Référence CVE CVE-2025-39998 https://www.cve.org/CVERecord?id=CVE-2025-39998 Référence CVE CVE-2025-40309 https://www.cve.org/CVERecord?id=CVE-2025-40309 Référence CVE CVE-2025-68794 https://www.cve.org/CVERecord?id=CVE-2025-68794 Référence CVE CVE-2025-71066 https://www.cve.org/CVERecord?id=CVE-2025-71066 Référence CVE CVE-2025-71268 https://www.cve.org/CVERecord?id=CVE-2025-71268 Référence CVE CVE-2025-71269 https://www.cve.org/CVERecord?id=CVE-2025-71269 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-23004 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-39961 Référence CVE CVE-2025-39965 https://www.cve.org/CVERecord?id=CVE-2025-39965 Référence CVE CVE-2025-39967 https://www.cve.org/CVERecord?id=CVE-2025-39967 Référence CVE CVE-2025-39968 https://www.cve.org/CVERecord?id=CVE-2025-39968 Référence CVE CVE-2025-39969 https://www.cve.org/CVERecord?id=CVE-2025-39969 Référence CVE CVE-2025-39970 https://www.cve.org/CVERecord?id=CVE-2025-39970 Référence CVE CVE-2025-39971 https://www.cve.org/CVERecord?id=CVE-2025-39971 Référence CVE CVE-2025-39972 https://www.cve.org/CVERecord?id=CVE-2025-39972 Référence CVE CVE-2025-39973 https://www.cve.org/CVERecord?id=CVE-2025-39973 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=CVE-2025-39977 Référence CVE CVE-2025-39978 https://www.cve.org/CVERecord?id=CVE-2025-39978 Référence CVE CVE-2025-39980 https://www.cve.org/CVERecord?id=CVE-2025-39980 Référence CVE CVE-2025-39981 https://www.cve.org/CVERecord?id=CVE-2025-39981 Référence CVE CVE-2025-39982 https://www.cve.org/CVERecord?id=CVE-2025-39982 Référence CVE CVE-2025-39985 https://www.cve.org/CVERecord?id=CVE-2025-39985 Référence CVE CVE-2025-39986 https://www.cve.org/CVERecord?id=CVE-2025-39986 Référence CVE CVE-2025-39987 https://www.cve.org/CVERecord?id=CVE-2025-39987 Référence CVE CVE-2025-39988 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-39961 Référence CVE CVE-2025-39965 https://www.cve.org/CVERecord?id=CVE-2025-39965 Référence CVE CVE-2025-39967 https://www.cve.org/CVERecord?id=CVE-2025-39967 Référence CVE CVE-2025-39968 https://www.cve.org/CVERecord?id=CVE-2025-39968 Référence CVE CVE-2025-39969 https://www.cve.org/CVERecord?id=CVE-2025-39969 Référence CVE CVE-2025-39970 https://www.cve.org/CVERecord?id=CVE-2025-39970 Référence CVE CVE-2025-39971 https://www.cve.org/CVERecord?id=CVE-2025-39971 Référence CVE CVE-2025-39972 https://www.cve.org/CVERecord?id=CVE-2025-39972 Référence CVE CVE-2025-39973 https://www.cve.org/CVERecord?id=CVE-2025-39973 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=CVE-2025-39977 Référence CVE CVE-2025-39978 https://www.cve.org/CVERecord?id=CVE-2025-39978 Référence CVE CVE-2025-39980 https://www.cve.org/CVERecord?id=CVE-2025-39980 Référence CVE CVE-2025-39981 https://www.cve.org/CVERecord?id=CVE-2025-39981 Référence CVE CVE-2025-39982 https://www.cve.org/CVERecord?id=CVE-2025-39982 Référence CVE CVE-2025-39985 https://www.cve.org/CVERecord?id=CVE-2025-39985 Référence CVE CVE-2025-39986 https://www.cve.org/CVERecord?id=CVE-2025-39986 Référence CVE CVE-2025-39987 https://www.cve.org/CVERecord?id=CVE-2025-39987 Référence CVE CVE-2025-39988 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-39961 Référence CVE CVE-2025-39965 https://www.cve.org/CVERecord?id=CVE-2025-39965 Référence CVE CVE-2025-39967 https://www.cve.org/CVERecord?id=CVE-2025-39967 Référence CVE CVE-2025-39968 https://www.cve.org/CVERecord?id=CVE-2025-39968 Référence CVE CVE-2025-39969 https://www.cve.org/CVERecord?id=CVE-2025-39969 Référence CVE CVE-2025-39970 https://www.cve.org/CVERecord?id=CVE-2025-39970 Référence CVE CVE-2025-39971 https://www.cve.org/CVERecord?id=CVE-2025-39971 Référence CVE CVE-2025-39972 https://www.cve.org/CVERecord?id=CVE-2025-39972 Référence CVE CVE-2025-39973 https://www.cve.org/CVERecord?id=CVE-2025-39973 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=CVE-2025-39977 Référence CVE CVE-2025-39978 https://www.cve.org/CVERecord?id=CVE-2025-39978 Référence CVE CVE-2025-39980 https://www.cve.org/CVERecord?id=CVE-2025-39980 Référence CVE CVE-2025-39981 https://www.cve.org/CVERecord?id=CVE-2025-39981 Référence CVE CVE-2025-39982 https://www.cve.org/CVERecord?id=CVE-2025-39982 Référence CVE CVE-2025-39985 https://www.cve.org/CVERecord?id=CVE-2025-39985 Référence CVE CVE-2025-39986 https://www.cve.org/CVERecord?id=CVE-2025-39986 Référence CVE CVE-2025-39987 https://www.cve.org/CVERecord?id=CVE-2025-39987 Référence CVE CVE-2025-39988 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39689 Référence CVE CVE-2025-39748 https://www.cve.org/CVERecord?id=CVE-2025-39748 Référence CVE CVE-2025-39813 https://www.cve.org/CVERecord?id=CVE-2025-39813 Référence CVE CVE-2025-39817 https://www.cve.org/CVERecord?id=CVE-2025-39817 Référence CVE CVE-2025-39829 https://www.cve.org/CVERecord?id=CVE-2025-39829 Référence CVE CVE-2025-39880 https://www.cve.org/CVERecord?id=CVE-2025-39880 Référence CVE CVE-2025-39890 https://www.cve.org/CVERecord?id=CVE-2025-39890 Référence CVE CVE-2025-39913 https://www.cve.org/CVERecord?id=CVE-2025-39913 Référence CVE CVE-2025-39964 https://www.cve.org/CVERecord?id=CVE-2025-39964 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=CVE-2025-39977 Référence CVE CVE-2025-39998 https://www.cve.org/CVERecord?id=CVE-2025-39998 Référence CVE CVE-2025-40006 https://www.cve.org/CVERecord?id=CVE-2025-40006 Référence CVE CVE-2025-40024 https://www.cve.org/CVERecord?id=CVE-2025-40024 Référence CVE CVE-2025-40033 https://www.cve.org/CVERecord?id=CVE-2025-40033 Référence CVE CVE-2025-40042 https://www.cve.org/CVERecord?id=CVE-2025-40042 Référence CVE CVE-2025-40053 https://www.cve.org/CVERecord?id=CVE-2025-40053 Référence CVE CVE-2025-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40097 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39961 Référence CVE CVE-2025-39965 https://www.cve.org/CVERecord?id=CVE-2025-39965 Référence CVE CVE-2025-39967 https://www.cve.org/CVERecord?id=CVE-2025-39967 Référence CVE CVE-2025-39968 https://www.cve.org/CVERecord?id=CVE-2025-39968 Référence CVE CVE-2025-39969 https://www.cve.org/CVERecord?id=CVE-2025-39969 Référence CVE CVE-2025-39970 https://www.cve.org/CVERecord?id=CVE-2025-39970 Référence CVE CVE-2025-39971 https://www.cve.org/CVERecord?id=CVE-2025-39971 Référence CVE CVE-2025-39972 https://www.cve.org/CVERecord?id=CVE-2025-39972 Référence CVE CVE-2025-39973 https://www.cve.org/CVERecord?id=CVE-2025-39973 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=CVE-2025-39977 Référence CVE CVE-2025-39978 https://www.cve.org/CVERecord?id=CVE-2025-39978 Référence CVE CVE-2025-39980 https://www.cve.org/CVERecord?id=CVE-2025-39980 Référence CVE CVE-2025-39981 https://www.cve.org/CVERecord?id=CVE-2025-39981 Référence CVE CVE-2025-39982 https://www.cve.org/CVERecord?id=CVE-2025-39982 Référence CVE CVE-2025-39985 https://www.cve.org/CVERecord?id=CVE-2025-39985 Référence CVE CVE-2025-39986 https://www.cve.org/CVERecord?id=CVE-2025-39986 Référence CVE CVE-2025-39987 https://www.cve.org/CVERecord?id=CVE-2025-39987 Référence CVE CVE-2025-39988 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-39932 Référence CVE CVE-2025-39933 https://www.cve.org/CVERecord?id=CVE-2025-39933 Référence CVE CVE-2025-39940 https://www.cve.org/CVERecord?id=CVE-2025-39940 Référence CVE CVE-2025-39942 https://www.cve.org/CVERecord?id=CVE-2025-39942 Référence CVE CVE-2025-39947 https://www.cve.org/CVERecord?id=CVE-2025-39947 Référence CVE CVE-2025-39952 https://www.cve.org/CVERecord?id=CVE-2025-39952 Référence CVE CVE-2025-39957 https://www.cve.org/CVERecord?id=CVE-2025-39957 Référence CVE CVE-2025-39958 https://www.cve.org/CVERecord?id=CVE-2025-39958 Référence CVE CVE-2025-39961 https://www.cve.org/CVERecord?id=CVE-2025-39961 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=CVE-2025-39977 Référence CVE CVE-2025-39978 https://www.cve.org/CVERecord?id=CVE-2025-39978 Référence CVE CVE-2025-39989 https://www.cve.org/CVERecord?id=CVE-2025-39989 Référence CVE CVE-2025-39990 https://www.cve.org/CVERecord?id=CVE-2025-39990 Référence CVE CVE-2025-39992 https://www.cve.org/CVERecord?id=CVE-2025-39992 Référence CVE CVE-2025-40003 https://www.cve.org/CVERecord?id=CVE-2025-40003 Référence CVE CVE-2025-40005 https://www.cve.org/CVERecord?id=CVE-2025-40005 Référence CVE CVE-2025-40012 https://www.cve.org/CVERecord?id=CVE-2025-40012 Référence CVE CVE-2025-40016 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-39932 Référence CVE CVE-2025-39933 https://www.cve.org/CVERecord?id=CVE-2025-39933 Référence CVE CVE-2025-39940 https://www.cve.org/CVERecord?id=CVE-2025-39940 Référence CVE CVE-2025-39942 https://www.cve.org/CVERecord?id=CVE-2025-39942 Référence CVE CVE-2025-39947 https://www.cve.org/CVERecord?id=CVE-2025-39947 Référence CVE CVE-2025-39952 https://www.cve.org/CVERecord?id=CVE-2025-39952 Référence CVE CVE-2025-39957 https://www.cve.org/CVERecord?id=CVE-2025-39957 Référence CVE CVE-2025-39958 https://www.cve.org/CVERecord?id=CVE-2025-39958 Référence CVE CVE-2025-39961 https://www.cve.org/CVERecord?id=CVE-2025-39961 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=CVE-2025-39977 Référence CVE CVE-2025-39978 https://www.cve.org/CVERecord?id=CVE-2025-39978 Référence CVE CVE-2025-39989 https://www.cve.org/CVERecord?id=CVE-2025-39989 Référence CVE CVE-2025-39990 https://www.cve.org/CVERecord?id=CVE-2025-39990 Référence CVE CVE-2025-39992 https://www.cve.org/CVERecord?id=CVE-2025-39992 Référence CVE CVE-2025-40003 https://www.cve.org/CVERecord?id=CVE-2025-40003 Référence CVE CVE-2025-40005 https://www.cve.org/CVERecord?id=CVE-2025-40005 Référence CVE CVE-2025-40012 https://www.cve.org/CVERecord?id=CVE-2025-40012 Référence CVE CVE-2025-40016 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39817 Référence CVE CVE-2025-39819 https://www.cve.org/CVERecord?id=CVE-2025-39819 Référence CVE CVE-2025-39829 https://www.cve.org/CVERecord?id=CVE-2025-39829 Référence CVE CVE-2025-39859 https://www.cve.org/CVERecord?id=CVE-2025-39859 Référence CVE CVE-2025-39880 https://www.cve.org/CVERecord?id=CVE-2025-39880 Référence CVE CVE-2025-39890 https://www.cve.org/CVERecord?id=CVE-2025-39890 Référence CVE CVE-2025-39913 https://www.cve.org/CVERecord?id=CVE-2025-39913 Référence CVE CVE-2025-39927 https://www.cve.org/CVERecord?id=CVE-2025-39927 Référence CVE CVE-2025-39944 https://www.cve.org/CVERecord?id=CVE-2025-39944 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=CVE-2025-39977 Référence CVE CVE-2025-39980 https://www.cve.org/CVERecord?id=CVE-2025-39980 Référence CVE CVE-2025-40001 https://www.cve.org/CVERecord?id=CVE-2025-40001 Référence CVE CVE-2025-40006 https://www.cve.org/CVERecord?id=CVE-2025-40006 Référence CVE CVE-2025-40021 https://www.cve.org/CVERecord?id=CVE-2025-40021 Référence CVE CVE-2025-40024 https://www.cve.org/CVERecord?id=CVE-2025-40024 Référence CVE CVE-2025-40027 https://www.cve.org/CVERecord?id=CVE-2025-40027 Référence CVE CVE-2025-40030 https://www.cve.org/CVERecord?id=CVE-2025-40030 Référence CVE CVE-2025-40033 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39813 Référence CVE CVE-2025-39819 https://www.cve.org/CVERecord?id=CVE-2025-39819 Référence CVE CVE-2025-39829 https://www.cve.org/CVERecord?id=CVE-2025-39829 Référence CVE CVE-2025-39836 https://www.cve.org/CVERecord?id=CVE-2025-39836 Référence CVE CVE-2025-39859 https://www.cve.org/CVERecord?id=CVE-2025-39859 Référence CVE CVE-2025-39880 https://www.cve.org/CVERecord?id=CVE-2025-39880 Référence CVE CVE-2025-39890 https://www.cve.org/CVERecord?id=CVE-2025-39890 Référence CVE CVE-2025-39913 https://www.cve.org/CVERecord?id=CVE-2025-39913 Référence CVE CVE-2025-39944 https://www.cve.org/CVERecord?id=CVE-2025-39944 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=CVE-2025-39977 Référence CVE CVE-2025-39980 https://www.cve.org/CVERecord?id=CVE-2025-39980 Référence CVE CVE-2025-40001 https://www.cve.org/CVERecord?id=CVE-2025-40001 Référence CVE CVE-2025-40006 https://www.cve.org/CVERecord?id=CVE-2025-40006 Référence CVE CVE-2025-40019 https://www.cve.org/CVERecord?id=CVE-2025-40019 Référence CVE CVE-2025-40021 https://www.cve.org/CVERecord?id=CVE-2025-40021 Référence CVE CVE-2025-40024 https://www.cve.org/CVERecord?id=CVE-2025-40024 Référence CVE CVE-2025-40027 https://www.cve.org/CVERecord?id=CVE-2025-40027 Référence CVE CVE-2025-40030 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38602 Référence CVE CVE-2025-38656 https://www.cve.org/CVERecord?id=CVE-2025-38656 Référence CVE CVE-2025-38684 https://www.cve.org/CVERecord?id=CVE-2025-38684 Référence CVE CVE-2025-39689 https://www.cve.org/CVERecord?id=CVE-2025-39689 Référence CVE CVE-2025-39813 https://www.cve.org/CVERecord?id=CVE-2025-39813 Référence CVE CVE-2025-39829 https://www.cve.org/CVERecord?id=CVE-2025-39829 Référence CVE CVE-2025-39836 https://www.cve.org/CVERecord?id=CVE-2025-39836 Référence CVE CVE-2025-39880 https://www.cve.org/CVERecord?id=CVE-2025-39880 Référence CVE CVE-2025-39913 https://www.cve.org/CVERecord?id=CVE-2025-39913 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=CVE-2025-39977 Référence CVE CVE-2025-40019 https://www.cve.org/CVERecord?id=CVE-2025-40019 Référence CVE CVE-2025-40044 https://www.cve.org/CVERecord?id=CVE-2025-40044 Référence CVE CVE-2025-40087 https://www.cve.org/CVERecord?id=CVE-2025-40087 Référence CVE CVE-2025-40088 https://www.cve.org/CVERecord?id=CVE-2025-40088 Référence CVE CVE-2025-40097 https://www.cve.org/CVERecord?id=CVE-2025-40097 Référence CVE CVE-2025-40106 https://www.cve.org/CVERecord?id=CVE-2025-40106 Référence CVE CVE-2025-40115 https://www.cve.org/CVERecord?id=CVE-2025-40115 Référence CVE CVE-2025-40132 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56658 Référence CVE CVE-2024-57996 https://www.cve.org/CVERecord?id=CVE-2024-57996 Référence CVE CVE-2025-21718 https://www.cve.org/CVERecord?id=CVE-2025-21718 Référence CVE CVE-2025-21772 https://www.cve.org/CVERecord?id=CVE-2025-21772 Référence CVE CVE-2025-38068 https://www.cve.org/CVERecord?id=CVE-2025-38068 Référence CVE CVE-2025-38159 https://www.cve.org/CVERecord?id=CVE-2025-38159 Référence CVE CVE-2025-38704 https://www.cve.org/CVERecord?id=CVE-2025-38704 Référence CVE CVE-2025-39880 https://www.cve.org/CVERecord?id=CVE-2025-39880 Référence CVE CVE-2025-39963 https://www.cve.org/CVERecord?id=CVE-2025-39963 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=CVE-2025-39977 Référence CVE CVE-2025-40018 https://www.cve.org/CVERecord?id=CVE-2025-40018 Référence CVE CVE-2025-40019 https://www.cve.org/CVERecord?id=CVE-2025-40019 Référence CVE CVE-2025-40042 https://www.cve.org/CVERecord?id=CVE-2025-40042 Référence CVE CVE-2025-40123 https://www.cve.org/CVERecord?id=CVE-2025-40123 Référence CVE CVE-2025-40130 https://www.cve.org/CVERecord?id=CVE-2025-40130 Référence CVE CVE-2025-40160 https://www.cve.org/CVERecord?id=CVE-2025-40160 Référence CVE CVE-2025-40167 https://www.cve.org/CVERecord?id=CVE-2025-40167 Référence CVE CVE-2025-40170 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38608 Référence CVE CVE-2025-38616 https://www.cve.org/CVERecord?id=CVE-2025-38616 Référence CVE CVE-2025-38617 https://www.cve.org/CVERecord?id=CVE-2025-38617 Référence CVE CVE-2025-38618 https://www.cve.org/CVERecord?id=CVE-2025-38618 Référence CVE CVE-2025-38664 https://www.cve.org/CVERecord?id=CVE-2025-38664 Référence CVE CVE-2025-38728 https://www.cve.org/CVERecord?id=CVE-2025-38728 Référence CVE CVE-2025-39682 https://www.cve.org/CVERecord?id=CVE-2025-39682 Référence CVE CVE-2025-39890 https://www.cve.org/CVERecord?id=CVE-2025-39890 Référence CVE CVE-2025-39963 https://www.cve.org/CVERecord?id=CVE-2025-39963 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=CVE-2025-39977 Référence CVE CVE-2025-40006 https://www.cve.org/CVERecord?id=CVE-2025-40006 Référence CVE CVE-2025-40019 https://www.cve.org/CVERecord?id=CVE-2025-40019 Référence CVE CVE-2025-40024 https://www.cve.org/CVERecord?id=CVE-2025-40024 Référence CVE CVE-2025-40033 https://www.cve.org/CVERecord?id=CVE-2025-40033 Référence CVE CVE-2025-40035 https://www.cve.org/CVERecord?id=CVE-2025-40035 Référence CVE CVE-2025-40042 https://www.cve.org/CVERecord?id=CVE-2025-40042 Référence CVE CVE-2025-40053 https://www.cve.org/CVERecord?id=CVE-2025-40053 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39957 Référence CVE CVE-2025-39964 https://www.cve.org/CVERecord?id=CVE-2025-39964 Référence CVE CVE-2025-39967 https://www.cve.org/CVERecord?id=CVE-2025-39967 Référence CVE CVE-2025-39968 https://www.cve.org/CVERecord?id=CVE-2025-39968 Référence CVE CVE-2025-39969 https://www.cve.org/CVERecord?id=CVE-2025-39969 Référence CVE CVE-2025-39970 https://www.cve.org/CVERecord?id=CVE-2025-39970 Référence CVE CVE-2025-39971 https://www.cve.org/CVERecord?id=CVE-2025-39971 Référence CVE CVE-2025-39972 https://www.cve.org/CVERecord?id=CVE-2025-39972 Référence CVE CVE-2025-39973 https://www.cve.org/CVERecord?id=CVE-2025-39973 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=CVE-2025-39977 Référence CVE CVE-2025-39978 https://www.cve.org/CVERecord?id=CVE-2025-39978 Référence CVE CVE-2025-39980 https://www.cve.org/CVERecord?id=CVE-2025-39980 Référence CVE CVE-2025-39982 https://www.cve.org/CVERecord?id=CVE-2025-39982 Référence CVE CVE-2025-39985 https://www.cve.org/CVERecord?id=CVE-2025-39985 Référence CVE CVE-2025-39986 https://www.cve.org/CVERecord?id=CVE-2025-39986 Référence CVE CVE-2025-39987 https://www.cve.org/CVERecord?id=CVE-2025-39987 Référence CVE CVE-2025-39988 https://www.cve.org/CVERecord?id=CVE-2025-39988 Référence CVE CVE-2025-39993 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39957 Référence CVE CVE-2025-39964 https://www.cve.org/CVERecord?id=CVE-2025-39964 Référence CVE CVE-2025-39967 https://www.cve.org/CVERecord?id=CVE-2025-39967 Référence CVE CVE-2025-39968 https://www.cve.org/CVERecord?id=CVE-2025-39968 Référence CVE CVE-2025-39969 https://www.cve.org/CVERecord?id=CVE-2025-39969 Référence CVE CVE-2025-39970 https://www.cve.org/CVERecord?id=CVE-2025-39970 Référence CVE CVE-2025-39971 https://www.cve.org/CVERecord?id=CVE-2025-39971 Référence CVE CVE-2025-39972 https://www.cve.org/CVERecord?id=CVE-2025-39972 Référence CVE CVE-2025-39973 https://www.cve.org/CVERecord?id=CVE-2025-39973 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=CVE-2025-39977 Référence CVE CVE-2025-39978 https://www.cve.org/CVERecord?id=CVE-2025-39978 Référence CVE CVE-2025-39980 https://www.cve.org/CVERecord?id=CVE-2025-39980 Référence CVE CVE-2025-39982 https://www.cve.org/CVERecord?id=CVE-2025-39982 Référence CVE CVE-2025-39985 https://www.cve.org/CVERecord?id=CVE-2025-39985 Référence CVE CVE-2025-39986 https://www.cve.org/CVERecord?id=CVE-2025-39986 Référence CVE CVE-2025-39987 https://www.cve.org/CVERecord?id=CVE-2025-39987 Référence CVE CVE-2025-39988 https://www.cve.org/CVERecord?id=CVE-2025-39988 Référence CVE CVE-2025-39993 https://www.cve.org/CVERecord?id=

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

CVE-2025-39964 du 15 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39965 du 15 octobre 2025 Bulletin de sécurité Microsoft CVE-2022-49069 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39967 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39968 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39969 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39970 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39971 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39972 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39973 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39977 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39980 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39981 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39982 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39985 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39987 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39990 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39994 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39998 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2022-49124 du 17 octobre 2025 Bulletin de sécurité Microsoft CVE-2022-49133

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 5.15, 6.1.155 ≤ 6.1.*, 6.6.109 ≤ 6.6.*, 6.12.50 ≤ 6.12.*, 6.16.10 ≤ 6.16.*, 6.17 ≤ *
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 15 Oct 2025 · Last source change 8 Sept 2026, 08:42 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-34595
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD not scheduled

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    07d91ef510fb16a2e0ca7453222105835b7ba3b8 < cb5d19a61274b51b49601214a87af573b43d60fa; 07d91ef510fb16a2e0ca7453222105835b7ba3b8 < 348736955ed6ca6e99ca24b93b1d3fbfe352c181; 07d91ef510fb16a2e0ca7453222105835b7ba3b8 < a170b9c0dde83312b8b58ccc91509c7c15711641; 07d91ef510fb16a2e0ca7453222105835b7ba3b8 < d824b2dbdcfe3c390278dd9652ea526168ef6850; 07d91ef510fb16a2e0ca7453222105835b7ba3b8 < b549113738e8c751b613118032a724b772aa83f2; 5.15 · Fixed: < 5.15; 6.1.155 ≤ 6.1.*; 6.6.109 ≤ 6.6.*; 6.12.50 ≤ 6.12.*; 6.16.10 ≤ 6.16.*; 6.17 ≤ *
    After
    Linux: 07d91ef510fb16a2e0ca7453222105835b7ba3b8 < cb5d19a61274b51b49601214a87af573b43d60fa, 07d91ef510fb16a2e0ca7453222105835b7ba3b8 < 348736955ed6ca6e99ca24b93b1d3fbfe352c181, 07d91ef510fb16a2e0ca7453222105835b7ba3b8 < a170b9c0dde83312b8b58ccc91509c7c15711641, 07d91ef510fb16a2e0ca7453222105835b7ba3b8 < d824b2dbdcfe3c390278dd9652ea526168ef6850, 07d91ef510fb16a2e0ca7453222105835b7ba3b8 < b549113738e8c751b613118032a724b772aa83f2, 5.15 · Fixed: Linux: < 5.15, 6.1.155 ≤ 6.1.*, 6.6.109 ≤ 6.6.*, 6.12.50 ≤ 6.12.*, 6.16.10 ≤ 6.16.*, 6.17 ≤ *
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2025-34595↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-39977 · cve.blacktree.nl