Full vulnerability report · 2026

CVE-2026-31726High confidence

usb: gadget: uvc: fix NULL pointer dereference during unbind race

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 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

Operational reassessment

Published severity in operational context

Open reassessment dashboard →

Published severityMediumOperational priority:Low, lowered one band.downgradedsince 23 May 2026

Evidence used

No CISA KEV confirmation is currently recorded.
Exploitation requires an existing local or physical foothold with privileges.
EPSS is 0.16% 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

Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
Verify the installed build against the product-specific fixed version after deployment.
Validate exposure, authentication requirements and compensating controls in the actual environment.
Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.

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.

Canonical Ubuntu Security: 20 affected package states with no published fix

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 release	Source package	Vendor state	Fixed version	Evidence
Debian trixietrixie · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.12.85-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.1.170-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.19.12-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.19.12-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-aws`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-fde`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-nvidia`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gcp`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gke`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gkeop`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-ibm`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-lowlatency`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-lowlatency`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-tegra`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oem-6.11`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oracle`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi-realtime`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-realtime`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-riscv`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-xilinx`	Affected, 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 feed`	Canonical 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-31726 · CSAF 2.0 · revision 8 · interimSUSE Product Security TeamCVE-2026-31726

151 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: usb: gadget: uvc: fix NULL pointer dereference during unbind race Commit b81ac4395bbe ("usb: gadget: uvc: allow for application to cleanly shutdown") introduced two stages of synchronization waits totaling 1500ms in uvc_function_unbind() to prevent several types of kernel panics. However, this timing-based approach is insufficient during power management (PM) transitions. When the PM subsystem starts freezing user space processes, the wait_event_interruptible_timeout() is aborted early, which allows the unbind thread to proceed and nullify the gadget pointer (cdev->gadget = NULL): [ 814.123447][ T947] configfs-gadget.g1 gadget.0: uvc: uvc_function_unbind() [ 814.178583][ T3173] PM: suspend entry (deep) [ 814.192487][ T3173] Freezing user space processes [ 814.197668][ T947] configfs-gadget.g1 gadget.0: uvc: uvc_function_unbind no clean disconnect, wait for release When the PM subsystem resumes or aborts the suspend and tasks are restarted, the V4L2 release path is executed and attempts to access the already nullified gadget pointer, triggering a kernel panic: [ 814.292597][ C0] PM: pm_system_irq_wakeup: 479 triggered dhdpcie_host_wake [ 814.386727][ T3173] Restarting tasks ... [ 814.403522][ T4558] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000030 [ 814.404021][ T4558] pc : usb_gadget_deactivate+0x14/0xf4 [ 814.404031][ T4558] lr : usb_function_deactivate+0x54/0x94 [ 814.404078][ T4558] Call trace: [ 814.404080][ T4558] usb_gadget_deactivate+0x14/0xf4 [ 814.404083][ T4558] usb_function_deactivate+0x54/0x94 [ 814.404087][ T4558] uvc_function_disconnect+0x1c/0x5c [ 814.404092][ T4558] uvc_v4l2_release+0x44/0xac [ 814.404095][ T4558] v4l2_release+0xcc/0x130 Address the race condition and NULL pointer dereference by: 1. State Synchronization (flag + mutex) Introduce a 'func_unbound' flag in struct uvc_device. This allows uvc_function_disconnect() to safely skip accessing the nullified cdev->gadget pointer. As suggested by Alan Stern, this flag is protected by a new mutex (uvc->lock) to ensure proper memory ordering and prevent instruction reordering or speculative loads. This mutex is also used to protect 'func_connected' for consistent state management. 2. Explicit Synchronization (completion) Use a completion to synchronize uvc_function_unbind() with the uvc_vdev_release() callback. This prevents Use-After-Free (UAF) by ensuring struct uvc_device is freed after all video device resources are released.
Remediation: To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".

Recommended actionPatch only the product branches with a verified fix

Fix availability varies by product

What, why and how

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: uvc: fix NULL pointer dereference during unbind race Commit b81ac4395bbe ("usb: gadget: uvc: allow for application to cleanly shutdown") introduced two stages of synchronization waits totaling 1500ms in uvc_function_unbind() to prevent several types of kernel panics. However, this timing-based approach is insufficient during power management (PM) transitions. When the PM subsystem starts freezing user space processes, the wait_event_interruptible_timeout() is aborted early, which allows the unbind thread to proceed and nullify the gadget pointer (cdev->gadget = NULL): [ 814.123447][ T947] configfs-gadget.g1 gadget.0: uvc: uvc_function_unbind() [ 814.178583][ T3173] PM: suspend entry (deep) [ 814.192487][ T3173] Freezing user space processes [ 814.197668][ T947] configfs-gadget.g1 gadget.0: uvc: uvc_function_unbind no clean disconnect, wait for release When the PM subsystem resumes or aborts the suspend and tasks are restarted, the V4L2 release path is executed and attempts to access the already nullified gadget pointer, triggering a kernel panic: [ 814.292597][ C0] PM: pm_system_irq_wakeup: 479 triggered dhdpcie_host_wake [ 814.386727][ T3173] Restarting tasks ... [ 814.403522][ T4558] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000030 [ 814.404021][ T4558] pc : usb_gadget_deactivate+0x14/0xf4 [ 814.404031][ T4558] lr : usb_function_deactivate+0x54/0x94 [ 814.404078][ T4558] Call trace: [ 814.404080][ T4558] usb_gadget_deactivate+0x14/0xf4 [ 814.404083][ T4558] usb_function_deactivate+0x54/0x94 [ 814.404087][ T4558] uvc_function_disconnect+0x1c/0x5c [ 814.404092][ T4558] uvc_v4l2_release+0x44/0xac [ 814.404095][ T4558] v4l2_release+0xcc/0x130 Address the race condition and NULL pointer dereference by: 1. State Synchronization (flag + mutex) Introduce a 'func_unbound' flag in struct uvc_device. This allows uvc_function_disconnect() to safely skip accessing the nullified cdev->gadget pointer. As suggested by Alan Stern, this flag is protected by a new mutex (uvc->lock) to ensure proper memory ordering and prevent instruction reordering or speculative loads. This mutex is also used to protect 'func_connected' for consistent state management. 2. Explicit Synchronization (completion) Use a completion to synchronize uvc_function_unbind() with the uvc_vdev_release() callback. This prevents Use-After-Free (UAF) by ensuring struct uvc_device is freed after all video device resources are released.

What

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

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

What

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

Exploit reality and attack path

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

Observed exploitation

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

No confirmed evidence

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

Public PoC / exploit material

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

None recorded

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

Likely attack path: local access → NULL Pointer Dereference → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface: Local
Privileges required: Low: a basic authenticated account is required
User interaction: None
Attack complexity: Low: no specialised conditions are recorded
Security boundary: Unchanged: impact remains within the vulnerable component's security authority
Weakness ? CWE means Common Weakness Enumeration: a standard category for the underlying weakness.: CWE-476 ↗
CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land: The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.

CWE-476

Official authority intelligence

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

ENISA EUVD · EUVD-2026-26539Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

BSI · German · WID-SEC-2026-1346Linux Kernel: Mehrere Schwachstellen

Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Root-Rechte zu erlangen, um Sicherheitsmechanismen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder Auswirkungen unbestimmter Art zu erzielen.

Official advisory ↗

Cyber Security Agency of Singapore · English · CSA-SB-20260506Security Bulletin 06 May 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 06 May 2026, published on 6 May 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-31696 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-31705 https://www.cve.org/CVERecord?id=CVE-2026-31705 Référence CVE CVE-2026-31716 https://www.cve.org/CVERecord?id=CVE-2026-31716 Référence CVE CVE-2026-31720 https://www.cve.org/CVERecord?id=CVE-2026-31720 Référence CVE CVE-2026-31721 https://www.cve.org/CVERecord?id=CVE-2026-31721 Référence CVE CVE-2026-31726 https://www.cve.org/CVERecord?id=CVE-2026-31726 Référence CVE CVE-2026-31728 https://www.cve.org/CVERecord?id=CVE-2026-31728 Référence CVE CVE-2026-31737 https://www.cve.org/CVERecord?id=CVE-2026-31737 Référence CVE CVE-2026-31738 https://www.cve.org/CVERecord?id=CVE-2026-31738 Référence CVE CVE-2026-31747 https://www.cve.org/CVERecord?id=CVE-2026-31747 Référence CVE CVE-2026-31748 https://www.cve.org/CVERecord?id=CVE-2026-31748 Référence CVE CVE-2026-31749 https://www.cve.org/CVERecord?id=CVE-2026-31749 Référence CVE CVE-2026-31751 https://www.cve.org/CVERecord?id=CVE-2026-31751 Référence CVE CVE-2026-31752 https://www.cve.org/CVERecord?id=

Official advisory ↗

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

Official advisory ↗

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

d?id=CVE-2026-31714 Référence CVE CVE-2026-31715 https://www.cve.org/CVERecord?id=CVE-2026-31715 Référence CVE CVE-2026-31716 https://www.cve.org/CVERecord?id=CVE-2026-31716 Référence CVE CVE-2026-31720 https://www.cve.org/CVERecord?id=CVE-2026-31720 Référence CVE CVE-2026-31721 https://www.cve.org/CVERecord?id=CVE-2026-31721 Référence CVE CVE-2026-31722 https://www.cve.org/CVERecord?id=CVE-2026-31722 Référence CVE CVE-2026-31723 https://www.cve.org/CVERecord?id=CVE-2026-31723 Référence CVE CVE-2026-31724 https://www.cve.org/CVERecord?id=CVE-2026-31724 Référence CVE CVE-2026-31725 https://www.cve.org/CVERecord?id=CVE-2026-31725 Référence CVE CVE-2026-31726 https://www.cve.org/CVERecord?id=CVE-2026-31726 Référence CVE CVE-2026-31728 https://www.cve.org/CVERecord?id=CVE-2026-31728 Référence CVE CVE-2026-31729 https://www.cve.org/CVERecord?id=CVE-2026-31729 Référence CVE CVE-2026-31730 https://www.cve.org/CVERecord?id=CVE-2026-31730 Référence CVE CVE-2026-31731 https://www.cve.org/CVERecord?id=CVE-2026-31731 Référence CVE CVE-2026-31737 https://www.cve.org/CVERecord?id=CVE-2026-31737 Référence CVE CVE-2026-31738 https://www.cve.org/CVERecord?id=CVE-2026-31738 Référence CVE CVE-2026-31740 https://www.cve.org/CVERecord?id=CVE-2026-31740 Référence CVE CVE-2026-31741 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-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=CVE-2026-31720 Référence CVE CVE-2026-31721 https://www.cve.org/CVERecord?id=CVE-2026-31721 Référence CVE CVE-2026-31726 https://www.cve.org/CVERecord?id=CVE-2026-31726 Référence CVE CVE-2026-31727 https://www.cve.org/CVERecord?id=CVE-2026-31727 Référence CVE CVE-2026-31728 https://www.cve.org/CVERecord?id=CVE-2026-31728 Référence CVE CVE-2026-31730 https://www.cve.org/CVERecord?id=CVE-2026-31730 Référence CVE CVE-2026-31738 https://www.cve.org/CVERecord?id=CVE-2026-31738 Référence CVE CVE-2026-31739 https://www.cve.org/CVERecord?id=CVE-2026-31739 Référence CVE CVE-2026-31740 https://www.cve.org/CVERecord?id=CVE-2026-31740 Référence CVE CVE-2026-31741 https://www.cve.org/CVERecord?id=CVE-2026-31741 Référence CVE CVE-2026-31747 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-31695 Référence CVE CVE-2026-31696 https://www.cve.org/CVERecord?id=CVE-2026-31696 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-31716 https://www.cve.org/CVERecord?id=CVE-2026-31716 Référence CVE CVE-2026-31720 https://www.cve.org/CVERecord?id=CVE-2026-31720 Référence CVE CVE-2026-31721 https://www.cve.org/CVERecord?id=CVE-2026-31721 Référence CVE CVE-2026-31726 https://www.cve.org/CVERecord?id=CVE-2026-31726 Référence CVE CVE-2026-31728 https://www.cve.org/CVERecord?id=CVE-2026-31728 Référence CVE CVE-2026-31737 https://www.cve.org/CVERecord?id=CVE-2026-31737 Référence CVE CVE-2026-31738 https://www.cve.org/CVERecord?id=CVE-2026-31738 Référence CVE CVE-2026-31747 https://www.cve.org/CVERecord?id=CVE-2026-31747 Référence CVE CVE-2026-31748 https://www.cve.org/CVERecord?id=CVE-2026-31748 Référence CVE CVE-2026-31749 https://www.cve.org/CVERecord?id=CVE-2026-31749 Référence CVE CVE-2026-31751 https://www.cve.org/CVERecord?id=CVE-2026-31751 Référence CVE CVE-2026-31752 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-31717 Référence CVE CVE-2026-31718 https://www.cve.org/CVERecord?id=CVE-2026-31718 Référence CVE CVE-2026-31719 https://www.cve.org/CVERecord?id=CVE-2026-31719 Référence CVE CVE-2026-31720 https://www.cve.org/CVERecord?id=CVE-2026-31720 Référence CVE CVE-2026-31721 https://www.cve.org/CVERecord?id=CVE-2026-31721 Référence CVE CVE-2026-31722 https://www.cve.org/CVERecord?id=CVE-2026-31722 Référence CVE CVE-2026-31723 https://www.cve.org/CVERecord?id=CVE-2026-31723 Référence CVE CVE-2026-31724 https://www.cve.org/CVERecord?id=CVE-2026-31724 Référence CVE CVE-2026-31725 https://www.cve.org/CVERecord?id=CVE-2026-31725 Référence CVE CVE-2026-31726 https://www.cve.org/CVERecord?id=CVE-2026-31726 Référence CVE CVE-2026-31728 https://www.cve.org/CVERecord?id=CVE-2026-31728 Référence CVE CVE-2026-31729 https://www.cve.org/CVERecord?id=CVE-2026-31729 Référence CVE CVE-2026-31730 https://www.cve.org/CVERecord?id=CVE-2026-31730 Référence CVE CVE-2026-31731 https://www.cve.org/CVERecord?id=CVE-2026-31731 Référence CVE CVE-2026-31737 https://www.cve.org/CVERecord?id=CVE-2026-31737 Référence CVE CVE-2026-31738 https://www.cve.org/CVERecord?id=CVE-2026-31738 Référence CVE CVE-2026-31740 https://www.cve.org/CVERecord?id=CVE-2026-31740 Référence CVE CVE-2026-31741 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-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=CVE-2026-31687 Référence CVE CVE-2026-31693 https://www.cve.org/CVERecord?id=CVE-2026-31693 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=CVE-2026-31720 Référence CVE CVE-2026-31726 https://www.cve.org/CVERecord?id=CVE-2026-31726 Référence CVE CVE-2026-31727 https://www.cve.org/CVERecord?id=CVE-2026-31727 Référence CVE CVE-2026-31728 https://www.cve.org/CVERecord?id=CVE-2026-31728 Référence CVE CVE-2026-31730 https://www.cve.org/CVERecord?id=CVE-2026-31730 Référence CVE CVE-2026-31743 https://www.cve.org/CVERecord?id=CVE-2026-31743 Référence CVE CVE-2026-31747 https://www.cve.org/CVERecord?id=CVE-2026-31747 Référence CVE CVE-2026-31748 https://www.cve.org/CVERecord?id=CVE-2026-31748 Référence CVE CVE-2026-31749 https://www.cve.org/CVERecord?id=CVE-2026-31749 Référence CVE CVE-2026-31751 https://www.cve.org/CVERecord?id=

Official advisory ↗

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

Official advisory ↗

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

d?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=CVE-2026-31682 Référence CVE CVE-2026-31683 https://www.cve.org/CVERecord?id=CVE-2026-31683 Référence CVE CVE-2026-31720 https://www.cve.org/CVERecord?id=CVE-2026-31720 Référence CVE CVE-2026-31721 https://www.cve.org/CVERecord?id=CVE-2026-31721 Référence CVE CVE-2026-31726 https://www.cve.org/CVERecord?id=CVE-2026-31726 Référence CVE CVE-2026-31728 https://www.cve.org/CVERecord?id=CVE-2026-31728 Référence CVE CVE-2026-31737 https://www.cve.org/CVERecord?id=CVE-2026-31737 Référence CVE CVE-2026-31738 https://www.cve.org/CVERecord?id=CVE-2026-31738 Référence CVE CVE-2026-31747 https://www.cve.org/CVERecord?id=CVE-2026-31747 Référence CVE CVE-2026-31748 https://www.cve.org/CVERecord?id=CVE-2026-31748 Référence CVE CVE-2026-31749 https://www.cve.org/CVERecord?id=CVE-2026-31749 Référence CVE CVE-2026-31751 https://www.cve.org/CVERecord?id=CVE-2026-31751 Référence CVE CVE-2026-31752 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-31678 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=CVE-2026-31682 Référence CVE CVE-2026-31683 https://www.cve.org/CVERecord?id=CVE-2026-31683 Référence CVE CVE-2026-31689 https://www.cve.org/CVERecord?id=CVE-2026-31689 Référence CVE CVE-2026-31695 https://www.cve.org/CVERecord?id=CVE-2026-31695 Référence CVE CVE-2026-31720 https://www.cve.org/CVERecord?id=CVE-2026-31720 Référence CVE CVE-2026-31721 https://www.cve.org/CVERecord?id=CVE-2026-31721 Référence CVE CVE-2026-31726 https://www.cve.org/CVERecord?id=CVE-2026-31726 Référence CVE CVE-2026-31728 https://www.cve.org/CVERecord?id=CVE-2026-31728 Référence CVE CVE-2026-31737 https://www.cve.org/CVERecord?id=CVE-2026-31737 Référence CVE CVE-2026-31738 https://www.cve.org/CVERecord?id=CVE-2026-31738 Référence CVE CVE-2026-31747 https://www.cve.org/CVERecord?id=CVE-2026-31747 Référence CVE CVE-2026-31748 https://www.cve.org/CVERecord?id=CVE-2026-31748 Référence CVE CVE-2026-31749 https://www.cve.org/CVERecord?id=CVE-2026-31749 Référence CVE CVE-2026-31751 https://www.cve.org/CVERecord?id=CVE-2026-31751 Référence CVE CVE-2026-31752 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-31683 Référence CVE CVE-2026-31684 https://www.cve.org/CVERecord?id=CVE-2026-31684 Référence CVE CVE-2026-31685 https://www.cve.org/CVERecord?id=CVE-2026-31685 Référence CVE CVE-2026-31686 https://www.cve.org/CVERecord?id=CVE-2026-31686 Référence CVE CVE-2026-31689 https://www.cve.org/CVERecord?id=CVE-2026-31689 Référence CVE CVE-2026-31693 https://www.cve.org/CVERecord?id=CVE-2026-31693 Référence CVE CVE-2026-31695 https://www.cve.org/CVERecord?id=CVE-2026-31695 Référence CVE CVE-2026-31720 https://www.cve.org/CVERecord?id=CVE-2026-31720 Référence CVE CVE-2026-31721 https://www.cve.org/CVERecord?id=CVE-2026-31721 Référence CVE CVE-2026-31726 https://www.cve.org/CVERecord?id=CVE-2026-31726 Référence CVE CVE-2026-31728 https://www.cve.org/CVERecord?id=CVE-2026-31728 Référence CVE CVE-2026-31737 https://www.cve.org/CVERecord?id=CVE-2026-31737 Référence CVE CVE-2026-31738 https://www.cve.org/CVERecord?id=CVE-2026-31738 Référence CVE CVE-2026-31747 https://www.cve.org/CVERecord?id=CVE-2026-31747 Référence CVE CVE-2026-31748 https://www.cve.org/CVERecord?id=CVE-2026-31748 Référence CVE CVE-2026-31749 https://www.cve.org/CVERecord?id=CVE-2026-31749 Référence CVE CVE-2026-31751 https://www.cve.org/CVERecord?id=CVE-2026-31751 Référence CVE CVE-2026-31752 https://www.cve.org/CVERecord?id=

Official advisory ↗

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

Linuxカーネルにおいて、以下の脆弱性が修正されました。usb: gadget: uvcのunbindレース時に発生するNULLポインタ参照についての修正です。コミットb81ac4395bbe（"usb: gadget: uvc: allow for application to cleanly shutdown"）により、カーネルパニックを防止するためにuvc_function_unbind()で合計1500msの2段階同期待機が導入されました。しかし、このタイミングベースの方法は電源管理（PM）遷移時には不十分です。PMサブシステムがユーザースペースプロセスをフリーズし始めると、wait_event_interruptible_timeout()が早期に中断され、unbindスレッドが進行してgadgetポインタ(cdev-gadget = NULL)をNULL化します。PMサブシステムの再開や中断時にタスクが再開されると、V4L2のリリース経路が既にNULL化されたgadgetポインタにアクセスしようとしてカーネルパニックを引き起こします。このレースコンディションとNULLポインタ参照に対処するために、まず1. 状態同期としてフラグとミューテックスを用い、struct uvc_deviceに'func_unbound'フラグを導入しました。これにより、uvc_function_disconnect()はNULL化されたcdev-gadgetポインタへのアクセスを安全にスキップできます。Alan Sternの提案に従い、このフラグは新しいミューテックス（uvc-lock）で保護され、適切なメモリ順序と命令の再配置および投機的読み込みを防止します。このミューテックスは一貫した状態管理のために'func_connected'の保護にも使用されます。次に2. 明示的同期として、uvc_function_unbind()とuvc_vdev_release()コールバックの同期にcompletionを使用し、すべてのビデオデバイスリソースを解放した後にstruct uvc_deviceが解放されることを保証してUse-After-Free（UAF）を防止します。

Official advisory ↗

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: 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
cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
ocfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5
dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5
gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5
kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP5
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP5
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP5
kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP5
ocfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5
and 121 more
Fixed: Linux: < 5.18, 5.10.253 ≤ 5.10.*, 5.15.203 ≤ 5.15.*, 6.1.168 ≤ 6.1.*, 6.6.134 ≤ 6.6.*, 6.12.81 ≤ 6.12.*, 6.18.22 ≤ 6.18.*, 6.19.12 ≤ 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.

Evidence and provenance

Published 1 May 2026 · Last source change 23 May 2026, 16:05 UTC · CWE-476 · NULL Pointer Dereference

CVE recordCVE.org · 5.2

CVSS sourceNIST NVD

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-08-14

European sourceENISA EUVD · EUVD-2026-26539

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.

2026-05-01CVE published

2026-05-23Fixed release or patch reference recorded

ENISA EUVD · EUVD-2026-26539↗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.

usb: gadget: uvc: fix NULL pointer dereference during unbind race

Published severity in operational context

Evidence used

Compensating controls

Verification

Remediation availability differs by product scope

Release-specific package status

Authoritative vendor CSAF and VEX advisories

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

ENISA European Vulnerability Database

EUVD-2026-26539

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication