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

futex: Clear stale exiting pointer in futex_lock_pi() retry path

Linux · Linux

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 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 severityMediumOperational priority:Low, 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.17% 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 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.85-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.170-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.11-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.11-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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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.

4 current
CVE-2026-31555 · CSAF 2.0 · revision 25 · interimSUSE Product Security TeamCVE-2026-31555
153 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: futex: Clear stale exiting pointer in futex_lock_pi() retry path Fuzzying/stressing futexes triggered: WARNING: kernel/futex/core.c:825 at wait_for_owner_exiting+0x7a/0x80, CPU#11: futex_lock_pi_s/524 When futex_lock_pi_atomic() sees the owner is exiting, it returns -EBUSY and stores a refcounted task pointer in 'exiting'. After wait_for_owner_exiting() consumes that reference, the local pointer is never reset to nil. Upon a retry, if futex_lock_pi_atomic() returns a different error, the bogus pointer is passed to wait_for_owner_exiting(). CPU0 CPU1 CPU2 futex_lock_pi(uaddr) // acquires the PI futex exit() futex_cleanup_begin() futex_state = EXITING; futex_lock_pi(uaddr) futex_lock_pi_atomic() attach_to_pi_owner() // observes EXITING *exiting = owner; // takes ref return -EBUSY wait_for_owner_exiting(-EBUSY, owner) put_task_struct(); // drops ref // exiting still points to owner goto retry; futex_lock_pi_atomic() lock_pi_update_atomic() cmpxchg(uaddr) *uaddr ^= WAITERS // whatever // value changed return -EAGAIN; wait_for_owner_exiting(-EAGAIN, exiting) // stale WARN_ON_ONCE(exiting) Fix this by resetting upon retry, essentially aligning it with requeue_pi.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-31555 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: futex: Clear stale exiting pointer in futex_lock_pi() retry path
174 known affected

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

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the Linux kernel. A local user could exploit a race condition within the `futex_lock_pi()` retry path. This vulnerability occurs because a stale pointer to an exiting process is not cleared, leading to a kernel warning. Successful exploitation of this flaw could result in a system crash, causing a Denial of Service (DoS).
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available.
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: Clear stale exiting pointer in futex_lock_pi() retry path Fuzzying/stressing futexes triggered: WARNING: kernel/futex/core.c:825 at wait_for_owner_exiting+0x7a/0x80, CPU#11: futex_lock_pi_s/524 When futex_lock_pi_atomic() sees the owner is exiting, it returns -EBUSY and stores a refcounted task pointer in 'exiting'. After wait_for_owner_exiting() consumes that reference, the local pointer is never reset to nil. Upon a retry, if futex_lock_pi_atomic() returns a different error, the bogus pointer is passed to wait_for_owner_exiting(). CPU0 CPU1 CPU2 futex_lock_pi(uaddr) // acquires the PI futex exit() futex_cleanup_begin() futex_state = EXITING; futex_lock_pi(uaddr) futex_lock_pi_atomic() attach_to_pi_owner() // observes EXITING *exiting = owner; // takes ref return -EBUSY wait_for_owner_exiting(-EBUSY, owner) put_task_struct(); // drops ref // exiting still points to owner goto retry; futex_lock_pi_atomic() lock_pi_update_atomic() cmpxchg(uaddr) *uaddr ^= WAITERS // whatever // value changed return -EAGAIN; wait_for_owner_exiting(-EAGAIN, exiting) // stale WARN_ON_ONCE(exiting) Fix this by resetting upon retry, essentially aligning it with requeue_pi.
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: Clear stale exiting pointer in futex_lock_pi() retry path Fuzzying/stressing futexes triggered: WARNING: kernel/futex/core.c:825 at wait_for_owner_exiting+0x7a/0x80, CPU#11: futex_lock_pi_s/524 When futex_lock_pi_atomic() sees the owner is exiting, it returns -EBUSY and stores a refcounted task pointer in 'exiting'. After wait_for_owner_exiting() consumes that reference, the local pointer is never reset to nil. Upon a retry, if futex_lock_pi_atomic() returns a different error, the bogus pointer is passed to wait_for_owner_exiting(). CPU0 CPU1 CPU2 futex_lock_pi(uaddr) // acquires the PI futex exit() futex_cleanup_begin() futex_state = EXITING; futex_lock_pi(uaddr) futex_lock_pi_atomic() attach_to_pi_owner() // observes EXITING *exiting = owner; // takes ref return -EBUSY wait_for_owner_exiting(-EBUSY, owner) put_task_struct(); // drops ref // exiting still points to owner goto retry; futex_lock_pi_atomic() lock_pi_update_atomic() cmpxchg(uaddr) *uaddr ^= WAITERS // whatever // value changed return -EAGAIN; wait_for_owner_exiting(-EAGAIN, exiting) // stale WARN_ON_ONCE(exiting) Fix this by resetting upon retry, essentially aligning it with requeue_pi.
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-2026-25448

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: futex: Clear stale exiting pointer in futex_lock_pi() retry path Fuzzying/stressing futexes triggered: WARNING: kernel/futex/core.c:825 at wait_for_owner_exiting+0x7a/0x80, CPU#11: futex_lock_pi_s/524 When futex_lock_pi_atomic() sees the owner is exiting, it returns -EBUSY and stores a refcounted task pointer in 'exiting'. After wait_for_owner_exiting() consumes that reference, the local pointer is never reset to nil. Upon a retry, if futex_lock_pi_atomic() returns a different error, the bogus pointer is passed to wait_for_owner_exiting(). CPU0 CPU1 CPU2 futex_lock_pi(uaddr) // acquires the PI futex exit() futex_cleanup_begin() futex_state = EXITING; futex_lock_pi(uaddr) futex_lock_pi_atomic() attach_to_pi_owner() // observes EXITING *exiting = owner; // takes ref return -EBUSY wait_for_owner_exiting(-EBUSY, owner) put_task_struct(); // drops ref // exiting still points to owner goto retry; futex_lock_pi_atomic() lock_pi_update_atomic() cmpxchg(uaddr) *uaddr ^= WAITERS // whatever // value changed return -EAGAIN; wait_for_owner_exiting(-EAGAIN, exiting) // stale WARN_ON_ONCE(exiting) Fix this by resetting upon retry, essentially aligning it with requeue_pi.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
0.0
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

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 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: Clear stale exiting pointer in futex_lock_pi() retry path Fuzzying/stressing futexes triggered: WARNING: kernel/futex/core.c:825 at wait_for_owner_exiting+0x7a/0x80, CPU#11: futex_lock_pi_s/524 When futex_lock_pi_atomic() sees the owner is exiting, it returns -EBUSY and stores a refcounted task pointer in 'exiting'. After wait_for_owner_exiting() consumes that reference, the local pointer is never reset to nil. Upon a retry, if futex_lock_pi_atomic() returns a different error, the bogus pointer is passed to wait_for_owner_exiting(). CPU0 CPU1 CPU2 futex_lock_pi(uaddr) // acquires the PI futex exit() futex_cleanup_begin() futex_state = EXITING; futex_lock_pi(uaddr) futex_lock_pi_atomic() attach_to_pi_owner() // observes EXITING *exiting = owner; // takes ref return -EBUSY wait_for_owner_exiting(-EBUSY, owner) put_task_struct(); // drops ref // exiting still points to owner goto retry; futex_lock_pi_atomic() lock_pi_update_atomic() cmpxchg(uaddr) *uaddr ^= WAITERS // whatever // value changed return -EAGAIN; wait_for_owner_exiting(-EAGAIN, exiting) // stale WARN_ON_ONCE(exiting) Fix this by resetting upon retry, essentially aligning it with requeue_pi.

What

In the Linux kernel, the following vulnerability has been resolved: futex: Clear stale exiting pointer in futex_lock_pi() retry path Fuzzying/stressing futexes triggered: WARNING: kernel/futex/core.c:825 at wait_for_owner_exiting+0x7a/0x80, CPU#11: futex_lock_pi_s/524 When futex_lock_pi_atomic() sees the owner is exiting, it returns -EBUSY and stores a refcounted task pointer in 'exiting'. After wait_for_owner_exiting() consumes that reference, the local pointer is never reset to nil. Upon a retry, if futex_lock_pi_atomic() returns a different error, the bogus pointer is passed to wait_for_owner_exiting(). CPU0 CPU1 CPU2 futex_lock_pi(uaddr) // acquires the PI futex exit() futex_cleanup_begin() futex_state = EXITING; futex_lock_pi(uaddr) futex_lock_pi_atomic() attach_to_pi_owner() // observes EXITING *exiting = owner; // takes ref return -EBUSY wait_for_owner_exiting(-EBUSY, owner) put_task_struct(); // drops ref // exiting still points to owner goto retry; futex_lock_pi_atomic() lock_pi_update_atomic() cmpxchg(uaddr) *uaddr ^= WAITERS // whatever // value changed return -EAGAIN; wait_for_owner_exiting(-EAGAIN, exiting) // stale WARN_ON_ONCE(exiting) Fix this by resetting upon retry, essentially aligning it with requeue_pi.

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: Clear stale exiting pointer in futex_lock_pi() retry path Fuzzying/stressing futexes triggered: WARNING: kernel/futex/core.c:825 at wait_for_owner_exiting+0x7a/0x80, CPU#11: futex_lock_pi_s/524 When futex_lock_pi_atomic() sees the owner is exiting, it returns -EBUSY and stores a refcounted task pointer in 'exiting'. After wait_for_owner_exiting() consumes that reference, the local pointer is never reset to nil. Upon a retry, if futex_lock_pi_atomic() returns a different error, the bogus pointer is passed to wait_for_owner_exiting(). CPU0 CPU1 CPU2 futex_lock_pi(uaddr) // acquires the PI futex exit() futex_cleanup_begin() futex_state = EXITING; futex_lock_pi(uaddr) futex_lock_pi_atomic() attach_to_pi_owner() // observes EXITING *exiting = owner; // takes ref return -EBUSY wait_for_owner_exiting(-EBUSY, owner) put_task_struct(); // drops ref // exiting still points to owner goto retry; futex_lock_pi_atomic() lock_pi_update_atomic() cmpxchg(uaddr) *uaddr ^= WAITERS // whatever // value changed return -EAGAIN; wait_for_owner_exiting(-EAGAIN, exiting) // stale WARN_ON_ONCE(exiting) Fix this by resetting upon retry, essentially aligning it with requeue_pi.

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:N/I:N/A:H

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

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

Official authority intelligence

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

ENISA EUVD · EUVD-2026-25448Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: futex: Clear stale exiting pointer in futex_lock_pi() retry path Fuzzying/stressing futexes triggered: WARNING: kernel/futex/core.c:825 at wait_for_owner_exiting+0x7a/0x80, CPU#11: futex_lock_pi_s/524 When futex_lock_pi_atomic() sees the owner is exiting, it returns -EBUSY and stores a refcounted task pointer in 'exiting'. After wait_for_owner_exiting() consumes that reference, the local pointer is never reset to nil. Upon a retry, if futex_lock_pi_atomic() returns a different error, the bogus pointer is passed to wait_for_owner_exiting(). CPU0 CPU1 CPU2 futex_lock_pi(uaddr) // acquires the PI futex exit() futex_cleanup_begin() futex_state = EXITING; futex_lock_pi(uaddr) futex_lock_pi_atomic() attach_to_pi_owner() // observes EXITING *exiting = owner; // takes ref return -EBUSY wait_for_owner_exiting(-EBUSY, owner) put_task_struct(); // drops ref // exiting still points to owner goto retry; futex_lock_pi_atomic() lock_pi_update_atomic() cmpxchg(uaddr) *uaddr ^= WAITERS // whatever // value changed return -EAGAIN; wait_for_owner_exiting(-EAGAIN, exiting) // stale WARN_ON_ONCE(exiting) Fix this by resetting upon retry, essentially aligning it with requeue_pi.

Official EUVD record ↗
BSI · German · WID-SEC-2026-1279Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, welche zu einem Denial-of-Service-Zustand, einer Rechteausweitung, der Ausführung von Code oder einer Speicherbeschädigung führen könnten.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260429Security Bulletin 29 Apr 2026

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

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

d?id=CVE-2026-31524 Référence CVE CVE-2026-31532 https://www.cve.org/CVERecord?id=CVE-2026-31532 Référence CVE CVE-2026-31540 https://www.cve.org/CVERecord?id=CVE-2026-31540 Référence CVE CVE-2026-31545 https://www.cve.org/CVERecord?id=CVE-2026-31545 Référence CVE CVE-2026-31546 https://www.cve.org/CVERecord?id=CVE-2026-31546 Référence CVE CVE-2026-31549 https://www.cve.org/CVERecord?id=CVE-2026-31549 Référence CVE CVE-2026-31550 https://www.cve.org/CVERecord?id=CVE-2026-31550 Référence CVE CVE-2026-31551 https://www.cve.org/CVERecord?id=CVE-2026-31551 Référence CVE CVE-2026-31552 https://www.cve.org/CVERecord?id=CVE-2026-31552 Référence CVE CVE-2026-31555 https://www.cve.org/CVERecord?id=CVE-2026-31555 Référence CVE CVE-2026-31560 https://www.cve.org/CVERecord?id=CVE-2026-31560 Référence CVE CVE-2026-31565 https://www.cve.org/CVERecord?id=CVE-2026-31565 Référence CVE CVE-2026-31570 https://www.cve.org/CVERecord?id=CVE-2026-31570 Référence CVE CVE-2026-31576 https://www.cve.org/CVERecord?id=CVE-2026-31576 Référence CVE CVE-2026-31577 https://www.cve.org/CVERecord?id=CVE-2026-31577 Référence CVE CVE-2026-31578 https://www.cve.org/CVERecord?id=CVE-2026-31578 Référence CVE CVE-2026-31580 https://www.cve.org/CVERecord?id=CVE-2026-31580 Référence CVE CVE-2026-31581 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31524 Référence CVE CVE-2026-31532 https://www.cve.org/CVERecord?id=CVE-2026-31532 Référence CVE CVE-2026-31540 https://www.cve.org/CVERecord?id=CVE-2026-31540 Référence CVE CVE-2026-31545 https://www.cve.org/CVERecord?id=CVE-2026-31545 Référence CVE CVE-2026-31546 https://www.cve.org/CVERecord?id=CVE-2026-31546 Référence CVE CVE-2026-31549 https://www.cve.org/CVERecord?id=CVE-2026-31549 Référence CVE CVE-2026-31550 https://www.cve.org/CVERecord?id=CVE-2026-31550 Référence CVE CVE-2026-31551 https://www.cve.org/CVERecord?id=CVE-2026-31551 Référence CVE CVE-2026-31552 https://www.cve.org/CVERecord?id=CVE-2026-31552 Référence CVE CVE-2026-31555 https://www.cve.org/CVERecord?id=CVE-2026-31555 Référence CVE CVE-2026-31565 https://www.cve.org/CVERecord?id=CVE-2026-31565 Référence CVE CVE-2026-31570 https://www.cve.org/CVERecord?id=CVE-2026-31570 Référence CVE CVE-2026-31576 https://www.cve.org/CVERecord?id=CVE-2026-31576 Référence CVE CVE-2026-31577 https://www.cve.org/CVERecord?id=CVE-2026-31577 Référence CVE CVE-2026-31578 https://www.cve.org/CVERecord?id=CVE-2026-31578 Référence CVE CVE-2026-31580 https://www.cve.org/CVERecord?id=CVE-2026-31580 Référence CVE CVE-2026-31581 https://www.cve.org/CVERecord?id=CVE-2026-31581 Référence CVE CVE-2026-31583 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31542 Référence CVE CVE-2026-31545 https://www.cve.org/CVERecord?id=CVE-2026-31545 Référence CVE CVE-2026-31546 https://www.cve.org/CVERecord?id=CVE-2026-31546 Référence CVE CVE-2026-31548 https://www.cve.org/CVERecord?id=CVE-2026-31548 Référence CVE CVE-2026-31549 https://www.cve.org/CVERecord?id=CVE-2026-31549 Référence CVE CVE-2026-31550 https://www.cve.org/CVERecord?id=CVE-2026-31550 Référence CVE CVE-2026-31551 https://www.cve.org/CVERecord?id=CVE-2026-31551 Référence CVE CVE-2026-31552 https://www.cve.org/CVERecord?id=CVE-2026-31552 Référence CVE CVE-2026-31554 https://www.cve.org/CVERecord?id=CVE-2026-31554 Référence CVE CVE-2026-31555 https://www.cve.org/CVERecord?id=CVE-2026-31555 Référence CVE CVE-2026-31556 https://www.cve.org/CVERecord?id=CVE-2026-31556 Référence CVE CVE-2026-31557 https://www.cve.org/CVERecord?id=CVE-2026-31557 Référence CVE CVE-2026-31563 https://www.cve.org/CVERecord?id=CVE-2026-31563 Référence CVE CVE-2026-31565 https://www.cve.org/CVERecord?id=CVE-2026-31565 Référence CVE CVE-2026-31566 https://www.cve.org/CVERecord?id=CVE-2026-31566 Référence CVE CVE-2026-31570 https://www.cve.org/CVERecord?id=CVE-2026-31570 Référence CVE CVE-2026-31575 https://www.cve.org/CVERecord?id=CVE-2026-31575 Référence CVE CVE-2026-31576 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31524 Référence CVE CVE-2026-31532 https://www.cve.org/CVERecord?id=CVE-2026-31532 Référence CVE CVE-2026-31540 https://www.cve.org/CVERecord?id=CVE-2026-31540 Référence CVE CVE-2026-31545 https://www.cve.org/CVERecord?id=CVE-2026-31545 Référence CVE CVE-2026-31546 https://www.cve.org/CVERecord?id=CVE-2026-31546 Référence CVE CVE-2026-31549 https://www.cve.org/CVERecord?id=CVE-2026-31549 Référence CVE CVE-2026-31550 https://www.cve.org/CVERecord?id=CVE-2026-31550 Référence CVE CVE-2026-31551 https://www.cve.org/CVERecord?id=CVE-2026-31551 Référence CVE CVE-2026-31552 https://www.cve.org/CVERecord?id=CVE-2026-31552 Référence CVE CVE-2026-31555 https://www.cve.org/CVERecord?id=CVE-2026-31555 Référence CVE CVE-2026-31565 https://www.cve.org/CVERecord?id=CVE-2026-31565 Référence CVE CVE-2026-31570 https://www.cve.org/CVERecord?id=CVE-2026-31570 Référence CVE CVE-2026-31576 https://www.cve.org/CVERecord?id=CVE-2026-31576 Référence CVE CVE-2026-31577 https://www.cve.org/CVERecord?id=CVE-2026-31577 Référence CVE CVE-2026-31578 https://www.cve.org/CVERecord?id=CVE-2026-31578 Référence CVE CVE-2026-31580 https://www.cve.org/CVERecord?id=CVE-2026-31580 Référence CVE CVE-2026-31581 https://www.cve.org/CVERecord?id=CVE-2026-31581 Référence CVE CVE-2026-31583 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31469 Référence CVE CVE-2026-31479 https://www.cve.org/CVERecord?id=CVE-2026-31479 Référence CVE CVE-2026-31492 https://www.cve.org/CVERecord?id=CVE-2026-31492 Référence CVE CVE-2026-31495 https://www.cve.org/CVERecord?id=CVE-2026-31495 Référence CVE CVE-2026-31499 https://www.cve.org/CVERecord?id=CVE-2026-31499 Référence CVE CVE-2026-31502 https://www.cve.org/CVERecord?id=CVE-2026-31502 Référence CVE CVE-2026-31503 https://www.cve.org/CVERecord?id=CVE-2026-31503 Référence CVE CVE-2026-31505 https://www.cve.org/CVERecord?id=CVE-2026-31505 Référence CVE CVE-2026-31533 https://www.cve.org/CVERecord?id=CVE-2026-31533 Référence CVE CVE-2026-31555 https://www.cve.org/CVERecord?id=CVE-2026-31555 Référence CVE CVE-2026-31560 https://www.cve.org/CVERecord?id=CVE-2026-31560 Référence CVE CVE-2026-31570 https://www.cve.org/CVERecord?id=CVE-2026-31570 Référence CVE CVE-2026-31580 https://www.cve.org/CVERecord?id=CVE-2026-31580 Référence CVE CVE-2026-31586 https://www.cve.org/CVERecord?id=CVE-2026-31586 Référence CVE CVE-2026-31596 https://www.cve.org/CVERecord?id=CVE-2026-31596 Référence CVE CVE-2026-31646 https://www.cve.org/CVERecord?id=CVE-2026-31646 Référence CVE CVE-2026-31647 https://www.cve.org/CVERecord?id=CVE-2026-31647 Référence CVE CVE-2026-31663 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-2026-31542 Référence CVE CVE-2026-31545 https://www.cve.org/CVERecord?id=CVE-2026-31545 Référence CVE CVE-2026-31546 https://www.cve.org/CVERecord?id=CVE-2026-31546 Référence CVE CVE-2026-31548 https://www.cve.org/CVERecord?id=CVE-2026-31548 Référence CVE CVE-2026-31549 https://www.cve.org/CVERecord?id=CVE-2026-31549 Référence CVE CVE-2026-31550 https://www.cve.org/CVERecord?id=CVE-2026-31550 Référence CVE CVE-2026-31551 https://www.cve.org/CVERecord?id=CVE-2026-31551 Référence CVE CVE-2026-31552 https://www.cve.org/CVERecord?id=CVE-2026-31552 Référence CVE CVE-2026-31554 https://www.cve.org/CVERecord?id=CVE-2026-31554 Référence CVE CVE-2026-31555 https://www.cve.org/CVERecord?id=CVE-2026-31555 Référence CVE CVE-2026-31556 https://www.cve.org/CVERecord?id=CVE-2026-31556 Référence CVE CVE-2026-31557 https://www.cve.org/CVERecord?id=CVE-2026-31557 Référence CVE CVE-2026-31563 https://www.cve.org/CVERecord?id=CVE-2026-31563 Référence CVE CVE-2026-31565 https://www.cve.org/CVERecord?id=CVE-2026-31565 Référence CVE CVE-2026-31566 https://www.cve.org/CVERecord?id=CVE-2026-31566 Référence CVE CVE-2026-31570 https://www.cve.org/CVERecord?id=CVE-2026-31570 Référence CVE CVE-2026-31574 https://www.cve.org/CVERecord?id=CVE-2026-31574 Référence CVE CVE-2026-31575 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31524 Référence CVE CVE-2026-31532 https://www.cve.org/CVERecord?id=CVE-2026-31532 Référence CVE CVE-2026-31533 https://www.cve.org/CVERecord?id=CVE-2026-31533 Référence CVE CVE-2026-31540 https://www.cve.org/CVERecord?id=CVE-2026-31540 Référence CVE CVE-2026-31545 https://www.cve.org/CVERecord?id=CVE-2026-31545 Référence CVE CVE-2026-31548 https://www.cve.org/CVERecord?id=CVE-2026-31548 Référence CVE CVE-2026-31549 https://www.cve.org/CVERecord?id=CVE-2026-31549 Référence CVE CVE-2026-31551 https://www.cve.org/CVERecord?id=CVE-2026-31551 Référence CVE CVE-2026-31552 https://www.cve.org/CVERecord?id=CVE-2026-31552 Référence CVE CVE-2026-31555 https://www.cve.org/CVERecord?id=CVE-2026-31555 Référence CVE CVE-2026-31560 https://www.cve.org/CVERecord?id=CVE-2026-31560 Référence CVE CVE-2026-31561 https://www.cve.org/CVERecord?id=CVE-2026-31561 Référence CVE CVE-2026-31566 https://www.cve.org/CVERecord?id=CVE-2026-31566 Référence CVE CVE-2026-31568 https://www.cve.org/CVERecord?id=CVE-2026-31568 Référence CVE CVE-2026-31570 https://www.cve.org/CVERecord?id=CVE-2026-31570 Référence CVE CVE-2026-31576 https://www.cve.org/CVERecord?id=CVE-2026-31576 Référence CVE CVE-2026-31578 https://www.cve.org/CVERecord?id=CVE-2026-31578 Référence CVE CVE-2026-31580 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31542 Référence CVE CVE-2026-31545 https://www.cve.org/CVERecord?id=CVE-2026-31545 Référence CVE CVE-2026-31546 https://www.cve.org/CVERecord?id=CVE-2026-31546 Référence CVE CVE-2026-31548 https://www.cve.org/CVERecord?id=CVE-2026-31548 Référence CVE CVE-2026-31549 https://www.cve.org/CVERecord?id=CVE-2026-31549 Référence CVE CVE-2026-31550 https://www.cve.org/CVERecord?id=CVE-2026-31550 Référence CVE CVE-2026-31551 https://www.cve.org/CVERecord?id=CVE-2026-31551 Référence CVE CVE-2026-31552 https://www.cve.org/CVERecord?id=CVE-2026-31552 Référence CVE CVE-2026-31554 https://www.cve.org/CVERecord?id=CVE-2026-31554 Référence CVE CVE-2026-31555 https://www.cve.org/CVERecord?id=CVE-2026-31555 Référence CVE CVE-2026-31556 https://www.cve.org/CVERecord?id=CVE-2026-31556 Référence CVE CVE-2026-31557 https://www.cve.org/CVERecord?id=CVE-2026-31557 Référence CVE CVE-2026-31563 https://www.cve.org/CVERecord?id=CVE-2026-31563 Référence CVE CVE-2026-31565 https://www.cve.org/CVERecord?id=CVE-2026-31565 Référence CVE CVE-2026-31566 https://www.cve.org/CVERecord?id=CVE-2026-31566 Référence CVE CVE-2026-31570 https://www.cve.org/CVERecord?id=CVE-2026-31570 Référence CVE CVE-2026-31574 https://www.cve.org/CVERecord?id=CVE-2026-31574 Référence CVE CVE-2026-31575 https://www.cve.org/CVERecord?id=

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

26-23475, CVE-2026-27135, CVE-2026-31389, CVE-2026-31391, CVE-2026-31396, CVE-2026-31402, CVE-2026-31403, CVE-2026-31411, CVE-2026-31414, CVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31418, CVE-2026-31421, CVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31427, CVE-2026-31428, CVE-2026-31431, CVE-2026-31441, CVE-2026-31446, CVE-2026-31447, CVE-2026-31448, CVE-2026-31450, CVE-2026-31452, CVE-2026-31466, CVE-2026-31469, CVE-2026-31485, CVE-2026-31494, CVE-2026-31495, CVE-2026-31496, CVE-2026-31503, CVE-2026-31504, CVE-2026-31507, CVE-2026-31508, CVE-2026-31515, CVE-2026-31518, CVE-2026-31521, CVE-2026-31533, CVE-2026-31546, CVE-2026-31555, CVE-2026-31563, CVE-2026-31565, CVE-2026-31628, CVE-2026-31634, CVE-2026-31649, CVE-2026-31651, CVE-2026-31658, CVE-2026-31664, CVE-2026-31665, CVE-2026-31669, CVE-2026-31670, CVE-2026-31671, CVE-2026-31674, CVE-2026-31680, CVE-2026-31682, CVE-2026-31737, CVE-2026-31752, CVE-2026-31761, CVE-2026-31768, CVE-2026-40355, CVE-2026-41989, CVE-2026-43011, CVE-2026-43024, CVE-2026-43025, CVE-2026-43026, CVE-2026-43027, CVE-2026-43028, CVE-2026-43030, CVE-2026-43033, CVE-2026-43035, CVE-2026-43038, CVE-2026-43040, CVE-2026-43057, CVE-2026-43284, CVE-2026-46174, CVE-2026-46300 et CVE-2026-46333. SIMATIC S7-PLCSIM Advanced toutes versions pour la vul

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

ord?id=CVE-2026-31499 Référence CVE CVE-2026-3150 https://www.cve.org/CVERecord?id=CVE-2026-3150 Référence CVE CVE-2026-31500 https://www.cve.org/CVERecord?id=CVE-2026-31500 Référence CVE CVE-2026-31502 https://www.cve.org/CVERecord?id=CVE-2026-31502 Référence CVE CVE-2026-31504 https://www.cve.org/CVERecord?id=CVE-2026-31504 Référence CVE CVE-2026-31516 https://www.cve.org/CVERecord?id=CVE-2026-31516 Référence CVE CVE-2026-31518 https://www.cve.org/CVERecord?id=CVE-2026-31518 Référence CVE CVE-2026-31546 https://www.cve.org/CVERecord?id=CVE-2026-31546 Référence CVE CVE-2026-31554 https://www.cve.org/CVERecord?id=CVE-2026-31554 Référence CVE CVE-2026-31555 https://www.cve.org/CVERecord?id=CVE-2026-31555 Référence CVE CVE-2026-31560 https://www.cve.org/CVERecord?id=CVE-2026-31560 Référence CVE CVE-2026-31590 https://www.cve.org/CVERecord?id=CVE-2026-31590 Référence CVE CVE-2026-31592 https://www.cve.org/CVERecord?id=CVE-2026-31592 Référence CVE CVE-2026-31593 https://www.cve.org/CVERecord?id=CVE-2026-31593 Référence CVE CVE-2026-31596 https://www.cve.org/CVERecord?id=CVE-2026-31596 Référence CVE CVE-2026-31613 https://www.cve.org/CVERecord?id=CVE-2026-31613 Référence CVE CVE-2026-31614 https://www.cve.org/CVERecord?id=CVE-2026-31614 Référence CVE CVE-2026-31629 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2026-31495 Référence CVE CVE-2026-31499 https://www.cve.org/CVERecord?id=CVE-2026-31499 Référence CVE CVE-2026-3150 https://www.cve.org/CVERecord?id=CVE-2026-3150 Référence CVE CVE-2026-31500 https://www.cve.org/CVERecord?id=CVE-2026-31500 Référence CVE CVE-2026-31504 https://www.cve.org/CVERecord?id=CVE-2026-31504 Référence CVE CVE-2026-31516 https://www.cve.org/CVERecord?id=CVE-2026-31516 Référence CVE CVE-2026-31518 https://www.cve.org/CVERecord?id=CVE-2026-31518 Référence CVE CVE-2026-31546 https://www.cve.org/CVERecord?id=CVE-2026-31546 Référence CVE CVE-2026-31554 https://www.cve.org/CVERecord?id=CVE-2026-31554 Référence CVE CVE-2026-31555 https://www.cve.org/CVERecord?id=CVE-2026-31555 Référence CVE CVE-2026-31560 https://www.cve.org/CVERecord?id=CVE-2026-31560 Référence CVE CVE-2026-31590 https://www.cve.org/CVERecord?id=CVE-2026-31590 Référence CVE CVE-2026-31592 https://www.cve.org/CVERecord?id=CVE-2026-31592 Référence CVE CVE-2026-31593 https://www.cve.org/CVERecord?id=CVE-2026-31593 Référence CVE CVE-2026-31596 https://www.cve.org/CVERecord?id=CVE-2026-31596 Référence CVE CVE-2026-31613 https://www.cve.org/CVERecord?id=CVE-2026-31613 Référence CVE CVE-2026-31614 https://www.cve.org/CVERecord?id=CVE-2026-31614 Référence CVE CVE-2026-31629 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31512 Référence CVE CVE-2026-31515 https://www.cve.org/CVERecord?id=CVE-2026-31515 Référence CVE CVE-2026-31518 https://www.cve.org/CVERecord?id=CVE-2026-31518 Référence CVE CVE-2026-31523 https://www.cve.org/CVERecord?id=CVE-2026-31523 Référence CVE CVE-2026-31524 https://www.cve.org/CVERecord?id=CVE-2026-31524 Référence CVE CVE-2026-31545 https://www.cve.org/CVERecord?id=CVE-2026-31545 Référence CVE CVE-2026-31546 https://www.cve.org/CVERecord?id=CVE-2026-31546 Référence CVE CVE-2026-31550 https://www.cve.org/CVERecord?id=CVE-2026-31550 Référence CVE CVE-2026-31552 https://www.cve.org/CVERecord?id=CVE-2026-31552 Référence CVE CVE-2026-31555 https://www.cve.org/CVERecord?id=CVE-2026-31555 Référence CVE CVE-2026-31570 https://www.cve.org/CVERecord?id=CVE-2026-31570 Référence CVE CVE-2026-31628 https://www.cve.org/CVERecord?id=CVE-2026-31628 Référence CVE CVE-2026-31649 https://www.cve.org/CVERecord?id=CVE-2026-31649 Référence CVE CVE-2026-31651 https://www.cve.org/CVERecord?id=CVE-2026-31651 Référence CVE CVE-2026-31658 https://www.cve.org/CVERecord?id=CVE-2026-31658 Référence CVE CVE-2026-31659 https://www.cve.org/CVERecord?id=CVE-2026-31659 Référence CVE CVE-2026-31660 https://www.cve.org/CVERecord?id=CVE-2026-31660 Référence CVE CVE-2026-31661 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31533 Référence CVE CVE-2026-31540 https://www.cve.org/CVERecord?id=CVE-2026-31540 Référence CVE CVE-2026-31545 https://www.cve.org/CVERecord?id=CVE-2026-31545 Référence CVE CVE-2026-31546 https://www.cve.org/CVERecord?id=CVE-2026-31546 Référence CVE CVE-2026-31548 https://www.cve.org/CVERecord?id=CVE-2026-31548 Référence CVE CVE-2026-31549 https://www.cve.org/CVERecord?id=CVE-2026-31549 Référence CVE CVE-2026-31550 https://www.cve.org/CVERecord?id=CVE-2026-31550 Référence CVE CVE-2026-31551 https://www.cve.org/CVERecord?id=CVE-2026-31551 Référence CVE CVE-2026-31552 https://www.cve.org/CVERecord?id=CVE-2026-31552 Référence CVE CVE-2026-31555 https://www.cve.org/CVERecord?id=CVE-2026-31555 Référence CVE CVE-2026-31563 https://www.cve.org/CVERecord?id=CVE-2026-31563 Référence CVE CVE-2026-31565 https://www.cve.org/CVERecord?id=CVE-2026-31565 Référence CVE CVE-2026-31566 https://www.cve.org/CVERecord?id=CVE-2026-31566 Référence CVE CVE-2026-31570 https://www.cve.org/CVERecord?id=CVE-2026-31570 Référence CVE CVE-2026-31628 https://www.cve.org/CVERecord?id=CVE-2026-31628 Référence CVE CVE-2026-31634 https://www.cve.org/CVERecord?id=CVE-2026-31634 Référence CVE CVE-2026-31649 https://www.cve.org/CVERecord?id=CVE-2026-31649 Référence CVE CVE-2026-31651 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31542 Référence CVE CVE-2026-31545 https://www.cve.org/CVERecord?id=CVE-2026-31545 Référence CVE CVE-2026-31546 https://www.cve.org/CVERecord?id=CVE-2026-31546 Référence CVE CVE-2026-31548 https://www.cve.org/CVERecord?id=CVE-2026-31548 Référence CVE CVE-2026-31549 https://www.cve.org/CVERecord?id=CVE-2026-31549 Référence CVE CVE-2026-31550 https://www.cve.org/CVERecord?id=CVE-2026-31550 Référence CVE CVE-2026-31551 https://www.cve.org/CVERecord?id=CVE-2026-31551 Référence CVE CVE-2026-31552 https://www.cve.org/CVERecord?id=CVE-2026-31552 Référence CVE CVE-2026-31554 https://www.cve.org/CVERecord?id=CVE-2026-31554 Référence CVE CVE-2026-31555 https://www.cve.org/CVERecord?id=CVE-2026-31555 Référence CVE CVE-2026-31556 https://www.cve.org/CVERecord?id=CVE-2026-31556 Référence CVE CVE-2026-31557 https://www.cve.org/CVERecord?id=CVE-2026-31557 Référence CVE CVE-2026-31558 https://www.cve.org/CVERecord?id=CVE-2026-31558 Référence CVE CVE-2026-31559 https://www.cve.org/CVERecord?id=CVE-2026-31559 Référence CVE CVE-2026-31561 https://www.cve.org/CVERecord?id=CVE-2026-31561 Référence CVE CVE-2026-31563 https://www.cve.org/CVERecord?id=CVE-2026-31563 Référence CVE CVE-2026-31565 https://www.cve.org/CVERecord?id=CVE-2026-31565 Référence CVE CVE-2026-31566 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0519Multiples vulnérabilités dans Microsoft Azure Linux

sécurité Microsoft CVE-2026-31520 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31521 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31522 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31523 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31524 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31525 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31528 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-41989 du 24 avril 2026 Bulletin de sécurité Microsoft CVE-2026-23360 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-23414 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31555 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31565 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31566 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31570 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31589 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31591 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31593 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31600 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31601 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31608 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31609 du 26 avril 2026 Bu

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

Linuxカーネルにおいて、futex_lock_pi()のリトライパスで古いexitingポインタをクリアしない問題が修正されました。この問題により、futex_lock_pi_atomic()が-EBUSYを返して参照カウントされたタスクポインタを'exiting'に保存した後、wait_for_owner_exiting()がその参照を解放してもローカルポインタがnilにリセットされず、リトライ時に不正なポインタが渡される可能性がありました。この脆弱性はリトライ時にポインタをリセットすることで修正されました。

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.5, 5.10.253 ≤ 5.10.*, 5.15.203 ≤ 5.15.*, 6.1.168 ≤ 6.1.*, 6.6.131 ≤ 6.6.*, 6.12.80 ≤ 6.12.*, 6.18.21 ≤ 6.18.*, 6.19.11 ≤ 6.19.*, 7.0 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 24 Apr 2026 · Last source change 8 Sept 2026, 08:47 UTC · CWE not yet assigned

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-2026-25448
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD modified after enrichment

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
    3ef240eaff36b8119ac9e2ea17cbf41179c930ba < 33095ae3bdde5e5c264d7e88a2f3e7703a26c7aa; 3ef240eaff36b8119ac9e2ea17cbf41179c930ba < e7824ec168d2ac883a213cd1f4d6cc0816002a85; 3ef240eaff36b8119ac9e2ea17cbf41179c930ba < 5e8e06bf8909e79b4acd950cf578cfc2f10bbefa; 3ef240eaff36b8119ac9e2ea17cbf41179c930ba < de7c0c04ad868f2cee6671b11c0a6d20421af1da; 3ef240eaff36b8119ac9e2ea17cbf41179c930ba < 7475dfad10a05a5bfadebf5f2499bd61b19ed293; 3ef240eaff36b8119ac9e2ea17cbf41179c930ba < 92e47ad03e03dbb5515bdf06444bf6b1e147310d; 3ef240eaff36b8119ac9e2ea17cbf41179c930ba < 71112e62807d1925dc3ae6188b11f8cfc85aec23; 3ef240eaff36b8119ac9e2ea17cbf41179c930ba < 210d36d892de5195e6766c45519dfb1e65f3eb83 · Fixed: < 5.5; 5.10.253 ≤ 5.10.*; 5.15.203 ≤ 5.15.*; 6.1.168 ≤ 6.1.*; 6.6.131 ≤ 6.6.*; 6.12.80 ≤ 6.12.*; 6.18.21 ≤ 6.18.*; 6.19.11 ≤ 6.19.*
    After
    Linux: 3ef240eaff36b8119ac9e2ea17cbf41179c930ba < 33095ae3bdde5e5c264d7e88a2f3e7703a26c7aa, 3ef240eaff36b8119ac9e2ea17cbf41179c930ba < e7824ec168d2ac883a213cd1f4d6cc0816002a85, 3ef240eaff36b8119ac9e2ea17cbf41179c930ba < 5e8e06bf8909e79b4acd950cf578cfc2f10bbefa, 3ef240eaff36b8119ac9e2ea17cbf41179c930ba < de7c0c04ad868f2cee6671b11c0a6d20421af1da, 3ef240eaff36b8119ac9e2ea17cbf41179c930ba < 7475dfad10a05a5bfadebf5f2499bd61b19ed293, 3ef240eaff36b8119ac9e2ea17cbf41179c930ba < 92e47ad03e03dbb5515bdf06444bf6b1e147310d, 3ef240eaff36b8119ac9e2ea17cbf41179c930ba < 71112e62807d1925dc3ae6188b11f8cfc85aec23, 3ef240eaff36b8119ac9e2ea17cbf41179c930ba < 210d36d892de5195e6766c45519dfb1e65f3eb83, f2a9957e5c08b1b1caacd18a3dc4c0a1bdb7b463, cf16e42709aa86aa3e37f3acc3d13d5715d90096, 61fa9f167caaa73d0a7c88f498eceeb12c6fa3db, 7874eee0130adf9bee28e8720bb5dd051089def3, fc3b55ef2c840bb2746b2d8121a0788de84f7fac, 4.4.255 < 4.5, 4.9.255 < 4.10, 4.14.158 < 4.15, 4.19.172 < 4.20, 5.4.1 < 5.5, 5.5 · Fixed: Linux: < 5.5, 5.10.253 ≤ 5.10.*, 5.15.203 ≤ 5.15.*, 6.1.168 ≤ 6.1.*, 6.6.131 ≤ 6.6.*, 6.12.80 ≤ 6.12.*, 6.18.21 ≤ 6.18.*, 6.19.11 ≤ 6.19.*, 7.0 ≤ *
    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-2026-25448↗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-2026-31555 · cve.blacktree.nl