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

Input: uinput - fix circular locking dependency with ff-core

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 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

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

Evidence used

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

Distribution package intelligence

Release-specific package status

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

24 package states
Package result overrides the generic status

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

Repository candidate not checked

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

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.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.13-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.13-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-31667 · CSAF 2.0 · revision 12 · interimSUSE Product Security TeamCVE-2026-31667
288 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
Summary
In the Linux kernel, the following vulnerability has been resolved: Input: uinput - fix circular locking dependency with ff-core A lockdep circular locking dependency warning can be triggered reproducibly when using a force-feedback gamepad with uinput (for example, playing ELDEN RING under Wine with a Flydigi Vader 5 controller): ff->mutex -> udev->mutex -> input_mutex -> dev->mutex -> ff->mutex The cycle is caused by four lock acquisition paths: 1. ff upload: input_ff_upload() holds ff->mutex and calls uinput_dev_upload_effect() -> uinput_request_submit() -> uinput_request_send(), which acquires udev->mutex. 2. device create: uinput_ioctl_handler() holds udev->mutex and calls uinput_create_device() -> input_register_device(), which acquires input_mutex. 3. device register: input_register_device() holds input_mutex and calls kbd_connect() -> input_register_handle(), which acquires dev->mutex. 4. evdev release: evdev_release() calls input_flush_device() under dev->mutex, which calls input_ff_flush() acquiring ff->mutex. Fix this by introducing a new state_lock spinlock to protect udev->state and udev->dev access in uinput_request_send() instead of acquiring udev->mutex. The function only needs to atomically check device state and queue an input event into the ring buffer via uinput_dev_event() -- both operations are safe under a spinlock (ktime_get_ts64() and wake_up_interruptible() do not sleep). This breaks the ff->mutex -> udev->mutex link since a spinlock is a leaf in the lock ordering and cannot form cycles with mutexes. To keep state transitions visible to uinput_request_send(), protect writes to udev->state in uinput_create_device() and uinput_destroy_device() with the same state_lock spinlock. Additionally, move init_completion(&request->done) from uinput_request_send() to uinput_request_submit() before uinput_request_reserve_slot(). Once the slot is allocated, uinput_flush_requests() may call complete() on it at any time from the destroy path, so the completion must be initialised before the request becomes visible. Lock ordering after the fix: ff->mutex -> state_lock (spinlock, leaf) udev->mutex -> state_lock (spinlock, leaf) udev->mutex -> input_mutex -> dev->mutex -> ff->mutex (no back-edge)
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-25560

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

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

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

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: Input: uinput - fix circular locking dependency with ff-core A lockdep circular locking dependency warning can be triggered reproducibly when using a force-feedback gamepad with uinput (for example, playing ELDEN RING under Wine with a Flydigi Vader 5 controller): ff->mutex -> udev->mutex -> input_mutex -> dev->mutex -> ff->mutex The cycle is caused by four lock acquisition paths: 1. ff upload: input_ff_upload() holds ff->mutex and calls uinput_dev_upload_effect() -> uinput_request_submit() -> uinput_request_send(), which acquires udev->mutex. 2. device create: uinput_ioctl_handler() holds udev->mutex and calls uinput_create_device() -> input_register_device(), which acquires input_mutex. 3. device register: input_register_device() holds input_mutex and calls kbd_connect() -> input_register_handle(), which acquires dev->mutex. 4. evdev release: evdev_release() calls input_flush_device() under dev->mutex, which calls input_ff_flush() acquiring ff->mutex. Fix this by introducing a new state_lock spinlock to protect udev->state and udev->dev access in uinput_request_send() instead of acquiring udev->mutex. The function only needs to atomically check device state and queue an input event into the ring buffer via uinput_dev_event() -- both operations are safe under a spinlock (ktime_get_ts64() and wake_up_interruptible() do not sleep). This breaks the ff->mutex -> udev->mutex link since a spinlock is a leaf in the lock ordering and cannot form cycles with mutexes. To keep state transitions visible to uinput_request_send(), protect writes to udev->state in uinput_create_device() and uinput_destroy_device() with the same state_lock spinlock. Additionally, move init_completion(&request->done) from uinput_request_send() to uinput_request_submit() before uinput_request_reserve_slot(). Once the slot is allocated, uinput_flush_requests() may call complete() on it at any time from the destroy path, so the completion must be initialised before the request becomes visible. Lock ordering after the fix: ff->mutex -> state_lock (spinlock, leaf) udev->mutex -> state_lock (spinlock, leaf) udev->mutex -> input_mutex -> dev->mutex -> ff->mutex (no back-edge)

What

In the Linux kernel, the following vulnerability has been resolved: Input: uinput - fix circular locking dependency with ff-core A lockdep circular locking dependency warning can be triggered reproducibly when using a force-feedback gamepad with uinput (for example, playing ELDEN RING under Wine with a Flydigi Vader 5 controller): ff->mutex -> udev->mutex -> input_mutex -> dev->mutex -> ff->mutex The cycle is caused by four lock acquisition paths: 1. ff upload: input_ff_upload() holds ff->mutex and calls uinput_dev_upload_effect() -> uinput_request_submit() -> uinput_request_send(), which acquires udev->mutex. 2. device create: uinput_ioctl_handler() holds udev->mutex and calls uinput_create_device() -> input_register_device(), which acquires input_mutex. 3. device register: input_register_device() holds input_mutex and calls kbd_connect() -> input_register_handle(), which acquires dev->mutex. 4. evdev release: evdev_release() calls input_flush_device() under dev->mutex, which calls input_ff_flush() acquiring ff->mutex. Fix this by introducing a new state_lock spinlock to protect udev->state and udev->dev access in uinput_request_send() instead of acquiring udev->mutex. The function only needs to atomically check device state and queue an input event into the ring buffer via uinput_dev_event() -- both operations are safe under a spinlock (ktime_get_ts64() and wake_up_interruptible() do not sleep). This breaks the ff->mutex -> udev->mutex link since a spinlock is a leaf in the lock ordering and cannot form cycles with mutexes. To keep state transitions visible to uinput_request_send(), protect writes to udev->state in uinput_create_device() and uinput_destroy_device() with the same state_lock spinlock. Additionally, move init_completion(&request->done) from uinput_request_send() to uinput_request_submit() before uinput_request_reserve_slot(). Once the slot is allocated, uinput_flush_requests() may call complete() on it at any time from the destroy path, so the completion must be initialised before the request becomes visible. Lock ordering after the fix: ff->mutex -> state_lock (spinlock, leaf) udev->mutex -> state_lock (spinlock, leaf) udev->mutex -> input_mutex -> dev->mutex -> ff->mutex (no back-edge)

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

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: Input: uinput - fix circular locking dependency with ff-core A lockdep circular locking dependency warning can be triggered reproducibly when using a force-feedback gamepad with uinput (for example, playing ELDEN RING under Wine with a Flydigi Vader 5 controller): ff->mutex -> udev->mutex -> input_mutex -> dev->mutex -> ff->mutex The cycle is caused by four lock acquisition paths: 1. ff upload: input_ff_upload() holds ff->mutex and calls uinput_dev_upload_effect() -> uinput_request_submit() -> uinput_request_send(), which acquires udev->mutex. 2. device create: uinput_ioctl_handler() holds udev->mutex and calls uinput_create_device() -> input_register_device(), which acquires input_mutex. 3. device register: input_register_device() holds input_mutex and calls kbd_connect() -> input_register_handle(), which acquires dev->mutex. 4. evdev release: evdev_release() calls input_flush_device() under dev->mutex, which calls input_ff_flush() acquiring ff->mutex. Fix this by introducing a new state_lock spinlock to protect udev->state and udev->dev access in uinput_request_send() instead of acquiring udev->mutex. The function only needs to atomically check device state and queue an input event into the ring buffer via uinput_dev_event() -- both operations are safe under a spinlock (ktime_get_ts64() and wake_up_interruptible() do not sleep). This breaks the ff->mutex -> udev->mutex link since a spinlock is a leaf in the lock ordering and cannot form cycles with mutexes. To keep state transitions visible to uinput_request_send(), protect writes to udev->state in uinput_create_device() and uinput_destroy_device() with the same state_lock spinlock. Additionally, move init_completion(&request->done) from uinput_request_send() to uinput_request_submit() before uinput_request_reserve_slot(). Once the slot is allocated, uinput_flush_requests() may call complete() on it at any time from the destroy path, so the completion must be initialised before the request becomes visible. Lock ordering after the fix: ff->mutex -> state_lock (spinlock, leaf) udev->mutex -> state_lock (spinlock, leaf) udev->mutex -> input_mutex -> dev->mutex -> ff->mutex (no back-edge)

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

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 → Improper Locking → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-667 ↗

CWE-667: Improper Locking. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

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.
CWE-667
A

Official authority intelligence

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

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-31642 Référence CVE CVE-2026-31651 https://www.cve.org/CVERecord?id=CVE-2026-31651 Référence CVE CVE-2026-31656 https://www.cve.org/CVERecord?id=CVE-2026-31656 Référence CVE CVE-2026-31658 https://www.cve.org/CVERecord?id=CVE-2026-31658 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=CVE-2026-31661 Référence CVE CVE-2026-31662 https://www.cve.org/CVERecord?id=CVE-2026-31662 Référence CVE CVE-2026-31664 https://www.cve.org/CVERecord?id=CVE-2026-31664 Référence CVE CVE-2026-31665 https://www.cve.org/CVERecord?id=CVE-2026-31665 Référence CVE CVE-2026-31667 https://www.cve.org/CVERecord?id=CVE-2026-31667 Référence CVE CVE-2026-31670 https://www.cve.org/CVERecord?id=CVE-2026-31670 Référence CVE CVE-2026-31671 https://www.cve.org/CVERecord?id=CVE-2026-31671 Référence CVE CVE-2026-31672 https://www.cve.org/CVERecord?id=CVE-2026-31672 Référence CVE CVE-2026-31673 https://www.cve.org/CVERecord?id=CVE-2026-31673 Référence CVE CVE-2026-31674 https://www.cve.org/CVERecord?id=CVE-2026-31674 Référence CVE CVE-2026-31676 https://www.cve.org/CVERecord?id=CVE-2026-31676 Référence CVE CVE-2026-31679 https://www.cve.org/CVERecord?id=CVE-2026-31679 Référence CVE CVE-2026-31680 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-31656 Référence CVE CVE-2026-31657 https://www.cve.org/CVERecord?id=CVE-2026-31657 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=CVE-2026-31661 Référence CVE CVE-2026-31662 https://www.cve.org/CVERecord?id=CVE-2026-31662 Référence CVE CVE-2026-31664 https://www.cve.org/CVERecord?id=CVE-2026-31664 Référence CVE CVE-2026-31665 https://www.cve.org/CVERecord?id=CVE-2026-31665 Référence CVE CVE-2026-31667 https://www.cve.org/CVERecord?id=CVE-2026-31667 Référence CVE CVE-2026-31668 https://www.cve.org/CVERecord?id=CVE-2026-31668 Référence CVE CVE-2026-31670 https://www.cve.org/CVERecord?id=CVE-2026-31670 Référence CVE CVE-2026-31671 https://www.cve.org/CVERecord?id=CVE-2026-31671 Référence CVE CVE-2026-31672 https://www.cve.org/CVERecord?id=CVE-2026-31672 Référence CVE CVE-2026-31673 https://www.cve.org/CVERecord?id=CVE-2026-31673 Référence CVE CVE-2026-31674 https://www.cve.org/CVERecord?id=CVE-2026-31674 Référence CVE CVE-2026-31676 https://www.cve.org/CVERecord?id=CVE-2026-31676 Référence CVE CVE-2026-31679 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-31655 Référence CVE CVE-2026-31656 https://www.cve.org/CVERecord?id=CVE-2026-31656 Référence CVE CVE-2026-31657 https://www.cve.org/CVERecord?id=CVE-2026-31657 Référence CVE CVE-2026-31658 https://www.cve.org/CVERecord?id=CVE-2026-31658 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=CVE-2026-31661 Référence CVE CVE-2026-31662 https://www.cve.org/CVERecord?id=CVE-2026-31662 Référence CVE CVE-2026-31664 https://www.cve.org/CVERecord?id=CVE-2026-31664 Référence CVE CVE-2026-31665 https://www.cve.org/CVERecord?id=CVE-2026-31665 Référence CVE CVE-2026-31667 https://www.cve.org/CVERecord?id=CVE-2026-31667 Référence CVE CVE-2026-31668 https://www.cve.org/CVERecord?id=CVE-2026-31668 Référence CVE CVE-2026-31670 https://www.cve.org/CVERecord?id=CVE-2026-31670 Référence CVE CVE-2026-31671 https://www.cve.org/CVERecord?id=CVE-2026-31671 Référence CVE CVE-2026-31672 https://www.cve.org/CVERecord?id=CVE-2026-31672 Référence CVE CVE-2026-31673 https://www.cve.org/CVERecord?id=CVE-2026-31673 Référence CVE CVE-2026-31674 https://www.cve.org/CVERecord?id=CVE-2026-31674 Référence CVE CVE-2026-31675 https://www.cve.org/CVERecord?id=CVE-2026-31675 Référence CVE CVE-2026-31677 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31627 Référence CVE CVE-2026-31628 https://www.cve.org/CVERecord?id=CVE-2026-31628 Référence CVE CVE-2026-31629 https://www.cve.org/CVERecord?id=CVE-2026-31629 Référence CVE CVE-2026-31651 https://www.cve.org/CVERecord?id=CVE-2026-31651 Référence CVE CVE-2026-31656 https://www.cve.org/CVERecord?id=CVE-2026-31656 Référence CVE CVE-2026-31657 https://www.cve.org/CVERecord?id=CVE-2026-31657 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=CVE-2026-31661 Référence CVE CVE-2026-31667 https://www.cve.org/CVERecord?id=CVE-2026-31667 Référence CVE CVE-2026-31672 https://www.cve.org/CVERecord?id=CVE-2026-31672 Référence CVE CVE-2026-31677 https://www.cve.org/CVERecord?id=CVE-2026-31677 Référence CVE CVE-2026-31687 https://www.cve.org/CVERecord?id=CVE-2026-31687 Référence CVE CVE-2026-31697 https://www.cve.org/CVERecord?id=CVE-2026-31697 Référence CVE CVE-2026-31698 https://www.cve.org/CVERecord?id=CVE-2026-31698 Référence CVE CVE-2026-31699 https://www.cve.org/CVERecord?id=CVE-2026-31699 Référence CVE CVE-2026-31701 https://www.cve.org/CVERecord?id=CVE-2026-31701 Référence CVE CVE-2026-31720 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-31642 Référence CVE CVE-2026-31651 https://www.cve.org/CVERecord?id=CVE-2026-31651 Référence CVE CVE-2026-31656 https://www.cve.org/CVERecord?id=CVE-2026-31656 Référence CVE CVE-2026-31658 https://www.cve.org/CVERecord?id=CVE-2026-31658 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=CVE-2026-31661 Référence CVE CVE-2026-31662 https://www.cve.org/CVERecord?id=CVE-2026-31662 Référence CVE CVE-2026-31664 https://www.cve.org/CVERecord?id=CVE-2026-31664 Référence CVE CVE-2026-31665 https://www.cve.org/CVERecord?id=CVE-2026-31665 Référence CVE CVE-2026-31667 https://www.cve.org/CVERecord?id=CVE-2026-31667 Référence CVE CVE-2026-31670 https://www.cve.org/CVERecord?id=CVE-2026-31670 Référence CVE CVE-2026-31671 https://www.cve.org/CVERecord?id=CVE-2026-31671 Référence CVE CVE-2026-31672 https://www.cve.org/CVERecord?id=CVE-2026-31672 Référence CVE CVE-2026-31673 https://www.cve.org/CVERecord?id=CVE-2026-31673 Référence CVE CVE-2026-31674 https://www.cve.org/CVERecord?id=CVE-2026-31674 Référence CVE CVE-2026-31676 https://www.cve.org/CVERecord?id=CVE-2026-31676 Référence CVE CVE-2026-31679 https://www.cve.org/CVERecord?id=CVE-2026-31679 Référence CVE CVE-2026-31680 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-31656 Référence CVE CVE-2026-31657 https://www.cve.org/CVERecord?id=CVE-2026-31657 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=CVE-2026-31661 Référence CVE CVE-2026-31662 https://www.cve.org/CVERecord?id=CVE-2026-31662 Référence CVE CVE-2026-31664 https://www.cve.org/CVERecord?id=CVE-2026-31664 Référence CVE CVE-2026-31665 https://www.cve.org/CVERecord?id=CVE-2026-31665 Référence CVE CVE-2026-31667 https://www.cve.org/CVERecord?id=CVE-2026-31667 Référence CVE CVE-2026-31668 https://www.cve.org/CVERecord?id=CVE-2026-31668 Référence CVE CVE-2026-31669 https://www.cve.org/CVERecord?id=CVE-2026-31669 Référence CVE CVE-2026-31670 https://www.cve.org/CVERecord?id=CVE-2026-31670 Référence CVE CVE-2026-31671 https://www.cve.org/CVERecord?id=CVE-2026-31671 Référence CVE CVE-2026-31672 https://www.cve.org/CVERecord?id=CVE-2026-31672 Référence CVE CVE-2026-31673 https://www.cve.org/CVERecord?id=CVE-2026-31673 Référence CVE CVE-2026-31674 https://www.cve.org/CVERecord?id=CVE-2026-31674 Référence CVE CVE-2026-31675 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-31647 Référence CVE CVE-2026-31651 https://www.cve.org/CVERecord?id=CVE-2026-31651 Référence CVE CVE-2026-31657 https://www.cve.org/CVERecord?id=CVE-2026-31657 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=CVE-2026-31661 Référence CVE CVE-2026-31663 https://www.cve.org/CVERecord?id=CVE-2026-31663 Référence CVE CVE-2026-31664 https://www.cve.org/CVERecord?id=CVE-2026-31664 Référence CVE CVE-2026-31665 https://www.cve.org/CVERecord?id=CVE-2026-31665 Référence CVE CVE-2026-31667 https://www.cve.org/CVERecord?id=CVE-2026-31667 Référence CVE CVE-2026-31670 https://www.cve.org/CVERecord?id=CVE-2026-31670 Référence CVE CVE-2026-31672 https://www.cve.org/CVERecord?id=CVE-2026-31672 Référence CVE CVE-2026-31673 https://www.cve.org/CVERecord?id=CVE-2026-31673 Référence CVE CVE-2026-31674 https://www.cve.org/CVERecord?id=CVE-2026-31674 Référence CVE CVE-2026-31678 https://www.cve.org/CVERecord?id=CVE-2026-31678 Référence CVE CVE-2026-31680 https://www.cve.org/CVERecord?id=CVE-2026-31680 Référence CVE CVE-2026-31685 https://www.cve.org/CVERecord?id=CVE-2026-31685 Référence CVE CVE-2026-31687 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-31656 Référence CVE CVE-2026-31657 https://www.cve.org/CVERecord?id=CVE-2026-31657 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=CVE-2026-31661 Référence CVE CVE-2026-31662 https://www.cve.org/CVERecord?id=CVE-2026-31662 Référence CVE CVE-2026-31664 https://www.cve.org/CVERecord?id=CVE-2026-31664 Référence CVE CVE-2026-31665 https://www.cve.org/CVERecord?id=CVE-2026-31665 Référence CVE CVE-2026-31667 https://www.cve.org/CVERecord?id=CVE-2026-31667 Référence CVE CVE-2026-31668 https://www.cve.org/CVERecord?id=CVE-2026-31668 Référence CVE CVE-2026-31669 https://www.cve.org/CVERecord?id=CVE-2026-31669 Référence CVE CVE-2026-31670 https://www.cve.org/CVERecord?id=CVE-2026-31670 Référence CVE CVE-2026-31671 https://www.cve.org/CVERecord?id=CVE-2026-31671 Référence CVE CVE-2026-31672 https://www.cve.org/CVERecord?id=CVE-2026-31672 Référence CVE CVE-2026-31673 https://www.cve.org/CVERecord?id=CVE-2026-31673 Référence CVE CVE-2026-31674 https://www.cve.org/CVERecord?id=CVE-2026-31674 Référence CVE CVE-2026-31675 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-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=CVE-2026-31661 Référence CVE CVE-2026-31662 https://www.cve.org/CVERecord?id=CVE-2026-31662 Référence CVE CVE-2026-31665 https://www.cve.org/CVERecord?id=CVE-2026-31665 Référence CVE CVE-2026-31667 https://www.cve.org/CVERecord?id=CVE-2026-31667 Référence CVE CVE-2026-31668 https://www.cve.org/CVERecord?id=CVE-2026-31668 Référence CVE CVE-2026-31670 https://www.cve.org/CVERecord?id=CVE-2026-31670 Référence CVE CVE-2026-31671 https://www.cve.org/CVERecord?id=CVE-2026-31671 Référence CVE CVE-2026-31672 https://www.cve.org/CVERecord?id=CVE-2026-31672 Référence CVE CVE-2026-31674 https://www.cve.org/CVERecord?id=CVE-2026-31674 Référence CVE CVE-2026-31679 https://www.cve.org/CVERecord?id=CVE-2026-31679 Référence CVE CVE-2026-31680 https://www.cve.org/CVERecord?id=CVE-2026-31680 Référence CVE CVE-2026-31682 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31428 Référence CVE CVE-2026-31496 https://www.cve.org/CVERecord?id=CVE-2026-31496 Référence CVE CVE-2026-31504 https://www.cve.org/CVERecord?id=CVE-2026-31504 Référence CVE CVE-2026-31507 https://www.cve.org/CVERecord?id=CVE-2026-31507 Référence CVE CVE-2026-31512 https://www.cve.org/CVERecord?id=CVE-2026-31512 Référence CVE CVE-2026-31524 https://www.cve.org/CVERecord?id=CVE-2026-31524 Référence CVE CVE-2026-31602 https://www.cve.org/CVERecord?id=CVE-2026-31602 Référence CVE CVE-2026-31607 https://www.cve.org/CVERecord?id=CVE-2026-31607 Référence CVE CVE-2026-31649 https://www.cve.org/CVERecord?id=CVE-2026-31649 Référence CVE CVE-2026-31667 https://www.cve.org/CVERecord?id=CVE-2026-31667 Référence CVE CVE-2026-31675 https://www.cve.org/CVERecord?id=CVE-2026-31675 Référence CVE CVE-2026-31681 https://www.cve.org/CVERecord?id=CVE-2026-31681 Référence CVE CVE-2026-31685 https://www.cve.org/CVERecord?id=CVE-2026-31685 Référence CVE CVE-2026-31700 https://www.cve.org/CVERecord?id=CVE-2026-31700 Référence CVE CVE-2026-31738 https://www.cve.org/CVERecord?id=CVE-2026-31738 Référence CVE CVE-2026-31787 https://www.cve.org/CVERecord?id=CVE-2026-31787 Référence CVE CVE-2026-43025 https://www.cve.org/CVERecord?id=CVE-2026-43025 Référence CVE CVE-2026-43088 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-31656 Référence CVE CVE-2026-31657 https://www.cve.org/CVERecord?id=CVE-2026-31657 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=CVE-2026-31661 Référence CVE CVE-2026-31662 https://www.cve.org/CVERecord?id=CVE-2026-31662 Référence CVE CVE-2026-31664 https://www.cve.org/CVERecord?id=CVE-2026-31664 Référence CVE CVE-2026-31665 https://www.cve.org/CVERecord?id=CVE-2026-31665 Référence CVE CVE-2026-31667 https://www.cve.org/CVERecord?id=CVE-2026-31667 Référence CVE CVE-2026-31668 https://www.cve.org/CVERecord?id=CVE-2026-31668 Référence CVE CVE-2026-31669 https://www.cve.org/CVERecord?id=CVE-2026-31669 Référence CVE CVE-2026-31670 https://www.cve.org/CVERecord?id=CVE-2026-31670 Référence CVE CVE-2026-31671 https://www.cve.org/CVERecord?id=CVE-2026-31671 Référence CVE CVE-2026-31672 https://www.cve.org/CVERecord?id=CVE-2026-31672 Référence CVE CVE-2026-31674 https://www.cve.org/CVERecord?id=CVE-2026-31674 Référence CVE CVE-2026-31678 https://www.cve.org/CVERecord?id=CVE-2026-31678 Référence CVE CVE-2026-31679 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-31657 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=CVE-2026-31661 Référence CVE CVE-2026-31662 https://www.cve.org/CVERecord?id=CVE-2026-31662 Référence CVE CVE-2026-31664 https://www.cve.org/CVERecord?id=CVE-2026-31664 Référence CVE CVE-2026-31665 https://www.cve.org/CVERecord?id=CVE-2026-31665 Référence CVE CVE-2026-31666 https://www.cve.org/CVERecord?id=CVE-2026-31666 Référence CVE CVE-2026-31667 https://www.cve.org/CVERecord?id=CVE-2026-31667 Référence CVE CVE-2026-31668 https://www.cve.org/CVERecord?id=CVE-2026-31668 Référence CVE CVE-2026-31669 https://www.cve.org/CVERecord?id=CVE-2026-31669 Référence CVE CVE-2026-31670 https://www.cve.org/CVERecord?id=CVE-2026-31670 Référence CVE CVE-2026-31671 https://www.cve.org/CVERecord?id=CVE-2026-31671 Référence CVE CVE-2026-31672 https://www.cve.org/CVERecord?id=CVE-2026-31672 Référence CVE CVE-2026-31673 https://www.cve.org/CVERecord?id=CVE-2026-31673 Référence CVE CVE-2026-31674 https://www.cve.org/CVERecord?id=CVE-2026-31674 Référence CVE CVE-2026-31675 https://www.cve.org/CVERecord?id=

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

sécurité Microsoft CVE-2026-31651 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31655 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31656 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31657 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31658 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31659 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31660 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31662 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31664 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31665 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31667 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31668 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31669 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31670 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31671 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31672 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31673 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31676 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31681 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31684 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31685 du 26 avril 2026 Bu

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-013620LinuxのLinux Kernelにおけるリソースのロックに関する脆弱性

Linuxカーネルにおいて、uinputのforce-feedback対応ゲームパッド使用時に発生していたff-coreとの循環ロック依存関係の問題が修正されました。lockdepによる循環ロック依存関係の警告は、ff-mutex、udev-mutex、input_mutex、dev-mutex間で循環が発生していたことが原因でした。修正では、新たにstate_lockスピンロックを導入し、udev-stateおよびudev-devへのアクセスを保護することで循環ロックの問題を解消しています。また、リクエスト構造体の初期化順序を変更してロック順序の整合性を確保し、ゲームパッド使用時のロック依存関係に起因する問題を防止しています。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 2.6.19, 5.10.253 ≤ 5.10.*, 5.15.203 ≤ 5.15.*, 6.1.169 ≤ 6.1.*, 6.6.135 ≤ 6.6.*, 6.12.82 ≤ 6.12.*, 6.18.23 ≤ 6.18.*, 6.19.13 ≤ 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 5 Aug 2026, 12:24 UTC · CWE-667 · Improper Locking

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

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

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-25560↗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-31667 · cve.blacktree.nl