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

usb: gadget: uvc: hold opts->lock across XU walks in uvc_function_bind

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
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 24 Jul 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

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

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

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

24 package states
Package result overrides the generic status

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

Repository candidate not checked

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

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.94-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-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-64233 · CSAF 2.0 · revision 8 · interimSUSE Product Security TeamCVE-2026-64233
98 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
Summary
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: uvc: hold opts->lock across XU walks in uvc_function_bind uvc_function_bind() walks &opts->extension_units twice without holding opts->lock: - directly, for the iExtension string-descriptor fixup loop; - indirectly, four times via uvc_copy_descriptors() (once per speed), where the helper iterates uvc->desc.extension_units (which aliases &opts->extension_units) to size and emit XU descriptors. The configfs side (uvcg_extension_make / uvcg_extension_drop, in drivers/usb/gadget/function/uvc_configfs.c) takes opts->lock around its list_add_tail / list_del operations. A privileged userspace process that holds the configfs subtree open and writes the gadget UDC name to bind the function while concurrently rmdir()'ing an extensions subdir can race uvcg_extension_drop() against the bind-time list walks and dereference a freed struct uvcg_extension. Hold opts->lock from the start of the XU string-descriptor fixup through the last uvc_copy_descriptors() call, releasing on the descriptor-error path via a new error_unlock label that drops the lock before falling through to the existing error label. This matches the locking discipline of the configfs callbacks and removes the only remaining unsynchronised reader of the XU list during bind. Reachability: only privileged processes that can mount configfs and write to gadget UDC files can trigger the race, so this is a correctness fix rather than a security boundary.
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-48642

No EUVD known-exploited evidence

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

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: uvc: hold opts->lock across XU walks in uvc_function_bind uvc_function_bind() walks &opts->extension_units twice without holding opts->lock: - directly, for the iExtension string-descriptor fixup loop; - indirectly, four times via uvc_copy_descriptors() (once per speed), where the helper iterates uvc->desc.extension_units (which aliases &opts->extension_units) to size and emit XU descriptors. The configfs side (uvcg_extension_make / uvcg_extension_drop, in drivers/usb/gadget/function/uvc_configfs.c) takes opts->lock around its list_add_tail / list_del operations. A privileged userspace process that holds the configfs subtree open and writes the gadget UDC name to bind the function while concurrently rmdir()'ing an extensions subdir can race uvcg_extension_drop() against the bind-time list walks and dereference a freed struct uvcg_extension. Hold opts->lock from the start of the XU string-descriptor fixup through the last uvc_copy_descriptors() call, releasing on the descriptor-error path via a new error_unlock label that drops the lock before falling through to the existing error label. This matches the locking discipline of the configfs callbacks and removes the only remaining unsynchronised reader of the XU list during bind. Reachability: only privileged processes that can mount configfs and write to gadget UDC files can trigger the race, so this is a correctness fix rather than a security boundary.

What

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: uvc: hold opts->lock across XU walks in uvc_function_bind uvc_function_bind() walks &opts->extension_units twice without holding opts->lock: - directly, for the iExtension string-descriptor fixup loop; - indirectly, four times via uvc_copy_descriptors() (once per speed), where the helper iterates uvc->desc.extension_units (which aliases &opts->extension_units) to size and emit XU descriptors. The configfs side (uvcg_extension_make / uvcg_extension_drop, in drivers/usb/gadget/function/uvc_configfs.c) takes opts->lock around its list_add_tail / list_del operations. A privileged userspace process that holds the configfs subtree open and writes the gadget UDC name to bind the function while concurrently rmdir()'ing an extensions subdir can race uvcg_extension_drop() against the bind-time list walks and dereference a freed struct uvcg_extension. Hold opts->lock from the start of the XU string-descriptor fixup through the last uvc_copy_descriptors() call, releasing on the descriptor-error path via a new error_unlock label that drops the lock before falling through to the existing error label. This matches the locking discipline of the configfs callbacks and removes the only remaining unsynchronised reader of the XU list during bind. Reachability: only privileged processes that can mount configfs and write to gadget UDC files can trigger the race, so this is a correctness fix rather than a security boundary.

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: usb: gadget: uvc: hold opts->lock across XU walks in uvc_function_bind uvc_function_bind() walks &opts->extension_units twice without holding opts->lock: - directly, for the iExtension string-descriptor fixup loop; - indirectly, four times via uvc_copy_descriptors() (once per speed), where the helper iterates uvc->desc.extension_units (which aliases &opts->extension_units) to size and emit XU descriptors. The configfs side (uvcg_extension_make / uvcg_extension_drop, in drivers/usb/gadget/function/uvc_configfs.c) takes opts->lock around its list_add_tail / list_del operations. A privileged userspace process that holds the configfs subtree open and writes the gadget UDC name to bind the function while concurrently rmdir()'ing an extensions subdir can race uvcg_extension_drop() against the bind-time list walks and dereference a freed struct uvcg_extension. Hold opts->lock from the start of the XU string-descriptor fixup through the last uvc_copy_descriptors() call, releasing on the descriptor-error path via a new error_unlock label that drops the lock before falling through to the existing error label. This matches the locking discipline of the configfs callbacks and removes the only remaining unsynchronised reader of the XU list during bind. Reachability: only privileged processes that can mount configfs and write to gadget UDC files can trigger the race, so this is a correctness fix rather than a security boundary.

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.

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

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.

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

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

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

d?id=CVE-2026-64224 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64226 https://www.cve.org/CVERecord?id=CVE-2026-64226 Référence CVE CVE-2026-64227 https://www.cve.org/CVERecord?id=CVE-2026-64227 Référence CVE CVE-2026-64228 https://www.cve.org/CVERecord?id=CVE-2026-64228 Référence CVE CVE-2026-64229 https://www.cve.org/CVERecord?id=CVE-2026-64229 Référence CVE CVE-2026-64230 https://www.cve.org/CVERecord?id=CVE-2026-64230 Référence CVE CVE-2026-64231 https://www.cve.org/CVERecord?id=CVE-2026-64231 Référence CVE CVE-2026-64232 https://www.cve.org/CVERecord?id=CVE-2026-64232 Référence CVE CVE-2026-64233 https://www.cve.org/CVERecord?id=CVE-2026-64233 Référence CVE CVE-2026-64234 https://www.cve.org/CVERecord?id=CVE-2026-64234 Référence CVE CVE-2026-64235 https://www.cve.org/CVERecord?id=CVE-2026-64235 Référence CVE CVE-2026-64236 https://www.cve.org/CVERecord?id=CVE-2026-64236 Référence CVE CVE-2026-64237 https://www.cve.org/CVERecord?id=CVE-2026-64237 Référence CVE CVE-2026-64238 https://www.cve.org/CVERecord?id=CVE-2026-64238 Référence CVE CVE-2026-64239 https://www.cve.org/CVERecord?id=CVE-2026-64239 Référence CVE CVE-2026-64240 https://www.cve.org/CVERecord?id=CVE-2026-64240 Référence CVE CVE-2026-64241 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64224 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64226 https://www.cve.org/CVERecord?id=CVE-2026-64226 Référence CVE CVE-2026-64227 https://www.cve.org/CVERecord?id=CVE-2026-64227 Référence CVE CVE-2026-64228 https://www.cve.org/CVERecord?id=CVE-2026-64228 Référence CVE CVE-2026-64229 https://www.cve.org/CVERecord?id=CVE-2026-64229 Référence CVE CVE-2026-64230 https://www.cve.org/CVERecord?id=CVE-2026-64230 Référence CVE CVE-2026-64231 https://www.cve.org/CVERecord?id=CVE-2026-64231 Référence CVE CVE-2026-64232 https://www.cve.org/CVERecord?id=CVE-2026-64232 Référence CVE CVE-2026-64233 https://www.cve.org/CVERecord?id=CVE-2026-64233 Référence CVE CVE-2026-64234 https://www.cve.org/CVERecord?id=CVE-2026-64234 Référence CVE CVE-2026-64235 https://www.cve.org/CVERecord?id=CVE-2026-64235 Référence CVE CVE-2026-64236 https://www.cve.org/CVERecord?id=CVE-2026-64236 Référence CVE CVE-2026-64237 https://www.cve.org/CVERecord?id=CVE-2026-64237 Référence CVE CVE-2026-64238 https://www.cve.org/CVERecord?id=CVE-2026-64238 Référence CVE CVE-2026-64239 https://www.cve.org/CVERecord?id=CVE-2026-64239 Référence CVE CVE-2026-64240 https://www.cve.org/CVERecord?id=CVE-2026-64240 Référence CVE CVE-2026-64241 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64224 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64226 https://www.cve.org/CVERecord?id=CVE-2026-64226 Référence CVE CVE-2026-64227 https://www.cve.org/CVERecord?id=CVE-2026-64227 Référence CVE CVE-2026-64228 https://www.cve.org/CVERecord?id=CVE-2026-64228 Référence CVE CVE-2026-64229 https://www.cve.org/CVERecord?id=CVE-2026-64229 Référence CVE CVE-2026-64230 https://www.cve.org/CVERecord?id=CVE-2026-64230 Référence CVE CVE-2026-64231 https://www.cve.org/CVERecord?id=CVE-2026-64231 Référence CVE CVE-2026-64232 https://www.cve.org/CVERecord?id=CVE-2026-64232 Référence CVE CVE-2026-64233 https://www.cve.org/CVERecord?id=CVE-2026-64233 Référence CVE CVE-2026-64234 https://www.cve.org/CVERecord?id=CVE-2026-64234 Référence CVE CVE-2026-64235 https://www.cve.org/CVERecord?id=CVE-2026-64235 Référence CVE CVE-2026-64236 https://www.cve.org/CVERecord?id=CVE-2026-64236 Référence CVE CVE-2026-64237 https://www.cve.org/CVERecord?id=CVE-2026-64237 Référence CVE CVE-2026-64238 https://www.cve.org/CVERecord?id=CVE-2026-64238 Référence CVE CVE-2026-64239 https://www.cve.org/CVERecord?id=CVE-2026-64239 Référence CVE CVE-2026-64240 https://www.cve.org/CVERecord?id=CVE-2026-64240 Référence CVE CVE-2026-64241 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-64224 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64226 https://www.cve.org/CVERecord?id=CVE-2026-64226 Référence CVE CVE-2026-64227 https://www.cve.org/CVERecord?id=CVE-2026-64227 Référence CVE CVE-2026-64228 https://www.cve.org/CVERecord?id=CVE-2026-64228 Référence CVE CVE-2026-64229 https://www.cve.org/CVERecord?id=CVE-2026-64229 Référence CVE CVE-2026-64230 https://www.cve.org/CVERecord?id=CVE-2026-64230 Référence CVE CVE-2026-64231 https://www.cve.org/CVERecord?id=CVE-2026-64231 Référence CVE CVE-2026-64232 https://www.cve.org/CVERecord?id=CVE-2026-64232 Référence CVE CVE-2026-64233 https://www.cve.org/CVERecord?id=CVE-2026-64233 Référence CVE CVE-2026-64234 https://www.cve.org/CVERecord?id=CVE-2026-64234 Référence CVE CVE-2026-64235 https://www.cve.org/CVERecord?id=CVE-2026-64235 Référence CVE CVE-2026-64236 https://www.cve.org/CVERecord?id=CVE-2026-64236 Référence CVE CVE-2026-64237 https://www.cve.org/CVERecord?id=CVE-2026-64237 Référence CVE CVE-2026-64238 https://www.cve.org/CVERecord?id=CVE-2026-64238 Référence CVE CVE-2026-64239 https://www.cve.org/CVERecord?id=CVE-2026-64239 Référence CVE CVE-2026-64240 https://www.cve.org/CVERecord?id=CVE-2026-64240 Référence CVE CVE-2026-64241 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-64183 Référence CVE CVE-2026-64187 https://www.cve.org/CVERecord?id=CVE-2026-64187 Référence CVE CVE-2026-64188 https://www.cve.org/CVERecord?id=CVE-2026-64188 Référence CVE CVE-2026-64189 https://www.cve.org/CVERecord?id=CVE-2026-64189 Référence CVE CVE-2026-64191 https://www.cve.org/CVERecord?id=CVE-2026-64191 Référence CVE CVE-2026-64220 https://www.cve.org/CVERecord?id=CVE-2026-64220 Référence CVE CVE-2026-64221 https://www.cve.org/CVERecord?id=CVE-2026-64221 Référence CVE CVE-2026-64223 https://www.cve.org/CVERecord?id=CVE-2026-64223 Référence CVE CVE-2026-64231 https://www.cve.org/CVERecord?id=CVE-2026-64231 Référence CVE CVE-2026-64233 https://www.cve.org/CVERecord?id=CVE-2026-64233 Référence CVE CVE-2026-64234 https://www.cve.org/CVERecord?id=CVE-2026-64234 Référence CVE CVE-2026-64241 https://www.cve.org/CVERecord?id=CVE-2026-64241 Référence CVE CVE-2026-64242 https://www.cve.org/CVERecord?id=CVE-2026-64242 Référence CVE CVE-2026-64330 https://www.cve.org/CVERecord?id=CVE-2026-64330 Référence CVE CVE-2026-64336 https://www.cve.org/CVERecord?id=CVE-2026-64336 Référence CVE CVE-2026-64345 https://www.cve.org/CVERecord?id=CVE-2026-64345 Référence CVE CVE-2026-64347 https://www.cve.org/CVERecord?id=CVE-2026-64347 Référence CVE CVE-2026-64357 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-64224 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64226 https://www.cve.org/CVERecord?id=CVE-2026-64226 Référence CVE CVE-2026-64227 https://www.cve.org/CVERecord?id=CVE-2026-64227 Référence CVE CVE-2026-64228 https://www.cve.org/CVERecord?id=CVE-2026-64228 Référence CVE CVE-2026-64229 https://www.cve.org/CVERecord?id=CVE-2026-64229 Référence CVE CVE-2026-64230 https://www.cve.org/CVERecord?id=CVE-2026-64230 Référence CVE CVE-2026-64231 https://www.cve.org/CVERecord?id=CVE-2026-64231 Référence CVE CVE-2026-64232 https://www.cve.org/CVERecord?id=CVE-2026-64232 Référence CVE CVE-2026-64233 https://www.cve.org/CVERecord?id=CVE-2026-64233 Référence CVE CVE-2026-64234 https://www.cve.org/CVERecord?id=CVE-2026-64234 Référence CVE CVE-2026-64235 https://www.cve.org/CVERecord?id=CVE-2026-64235 Référence CVE CVE-2026-64236 https://www.cve.org/CVERecord?id=CVE-2026-64236 Référence CVE CVE-2026-64237 https://www.cve.org/CVERecord?id=CVE-2026-64237 Référence CVE CVE-2026-64238 https://www.cve.org/CVERecord?id=CVE-2026-64238 Référence CVE CVE-2026-64239 https://www.cve.org/CVERecord?id=CVE-2026-64239 Référence CVE CVE-2026-64240 https://www.cve.org/CVERecord?id=CVE-2026-64240 Référence CVE CVE-2026-64241 https://www.cve.org/CVERecord?id=

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

Linuxカーネルにおいて、以下の脆弱性が修正されました。usb: gadget: uvcに関して、uvc_function_bind内のXU走査中にopts-＞lockを保持しない問題があります。具体的には、uvc_function_bind()はopts-＞lockを保持せずにopts-＞extension_unitsを2回走査しています。 - 1回目はiExtension文字列ディスクリプタの修正ループで直接的に行い、 - 2回目はuvc_copy_descriptors()を通じて間接的に4回（各スピードごとに1回）行っています。 このヘルパー関数はuvc-＞desc.extension_units（&opts-＞extension_unitsのエイリアス）を走査してXUディスクリプタのサイズ計算と出力を行います。configfs側（drivers/usb/gadget/function/uvc_configfs.cのuvcg_extension_makeおよびuvcg_extension_drop）ではlist_add_tailとlist_del操作時にopts-＞lockを取得しています。特権のあるユーザースペースプロセスがconfigfsのサブツリーをオープンした状態で、関数をバインドするためにgadget UDC名を書き込みつつ、同時にextensionsサブディレクトリをrmdir()する状況では、uvcg_extension_drop()とバインド時のリスト走査が競合し、解放済みのstruct uvcg_extensionをデリファレンスする恐れがあります。そこで、XU文字列ディスクリプタの修正開始から最後のuvc_copy_descriptors()呼び出しまでopts-＞lockを保持し、ディスクリプタエラー時の経路では新たにerror_unlockラベルを設けてロックを解放してから既存のerrorラベルに流すようにしました。これにより、configfsコールバックのロック運用と整合し、バインド時にXUリストを非同期に読み取る唯一の箇所を排除しています。到達可能性については、configfsをマウントしgadget UDCファイルに書き込み可能な特権プロセスのみがこの競合を発生させ得るため、本修正はセキュリティ境界ではなく整合性向上のための修正です。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 6.3, 6.6.143 ≤ 6.6.*, 6.12.93 ≤ 6.12.*, 6.18.35 ≤ 6.18.*, 7.0.12 ≤ 7.0.*, 7.1 ≤ *
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 Jul 2026 · Last source change 24 Jul 2026, 15:27 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-48642
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD enriched

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 ↗

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-48642↗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-64233 · cve.blacktree.nl