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

usb: gadget: udc: bdc: free IRQ and drain func_wake_notify before teardown

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 23 Aug 2026

Evidence used

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

Compensating controls

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

Verification

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

25 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.101-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.187-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.101-1~deb12u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.6-1Debian Security Tracker ↗Source updated 5 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-64583 · CSAF 2.0 · revision 10 · interimSUSE Product Security TeamCVE-2026-64583
17 known affected

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

  • SUSE Linux Micro Extras 6.2:kernel-obs-build
  • SUSE Linux Micro Extras 6.2:kernel-syms
  • SLES 15 SP1 CHOST Images for Amazon EC2
  • SLES 15 SP2 CHOST Images for Amazon EC2
  • SLES 15 SP3 CHOST Images for Amazon EC2
  • SLES 15 SP4 CHOST Images for Amazon EC2
  • SLES 15 SP5 CHOST Images for Amazon EC2
  • SLES 15 SP1 CHOST Images for Google
  • SLES 15 SP2 CHOST Images for Google
  • SLES 15 SP3 CHOST Images for Google
  • SLES 15 SP4 CHOST Images for Google
  • SLES 15 SP5 CHOST Images for Google
Summary
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: udc: bdc: free IRQ and drain func_wake_notify before teardown The Broadcom BDC UDC driver registers its IRQ handler with devm_request_irq() in bdc_udc_init(), so the IRQ is released by devm only after bdc_remove() returns. devm releases resources in reverse LIFO order, but bdc_remove() runs bdc_udc_exit() and bdc_hw_exit() -> bdc_mem_free() manually before returning: bdc_udc_exit() tears down individual endpoint objects via bdc_free_ep(), while bdc_hw_exit() -> bdc_mem_free() frees and NULLs the DMA-coherent status-report ring (bdc->srr.sr_bds) and kfree()s bdc->bdc_ep_array. Both happen while the IRQ handler (bdc_udc_interrupt, requested with IRQF_SHARED) remains deliverable in the window up to the post-remove devm free_irq(). On receipt of a shared interrupt in that window, bdc_udc_interrupt() dereferences bdc->srr.sr_bds[bdc->srr.dqp_index] (NULL or freed DMA) and dispatches sr_handler callbacks that index into bdc_ep_array, causing a NULL-deref or use-after-free. The same window affects the delayed_work bdc->func_wake_notify, which is armed from the IRQ handler via bdc_sr_uspc() -> handle_link_state_change() -> schedule_delayed_work() and may self-rearm from its own callback bdc_func_wake_timer(). No cancel exists anywhere in the driver, so a queued work item that fires after bdc_remove() returns and the bdc structure is devm-freed dereferences freed memory. Replace devm_request_irq() with request_irq() and add an explicit free_irq(bdc->irq, bdc) in bdc_remove(). Clear BDC_GIE before free_irq() to stop the device from asserting interrupts, then free_irq() drains any in-flight handler, then cancel_delayed_work_sync() drains the func_wake_notify delayed work. This ordering ensures the IRQ handler and delayed work cannot interfere with the subsequent endpoint and DMA teardown in bdc_udc_exit() and bdc_hw_exit(). Wire the matching free_irq() into the bdc_udc_init() error path so the IRQ is released on probe failure, and route the bdc_init_ep() failure through err0 instead of returning directly. This issue was found by an in-house static analysis tool.
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-53770

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: udc: bdc: free IRQ and drain func_wake_notify before teardown The Broadcom BDC UDC driver registers its IRQ handler with devm_request_irq() in bdc_udc_init(), so the IRQ is released by devm only after bdc_remove() returns. devm releases resources in reverse LIFO order, but bdc_remove() runs bdc_udc_exit() and bdc_hw_exit() -> bdc_mem_free() manually before returning: bdc_udc_exit() tears down individual endpoint objects via bdc_free_ep(), while bdc_hw_exit() -> bdc_mem_free() frees and NULLs the DMA-coherent status-report ring (bdc->srr.sr_bds) and kfree()s bdc->bdc_ep_array. Both happen while the IRQ handler (bdc_udc_interrupt, requested with IRQF_SHARED) remains deliverable in the window up to the post-remove devm free_irq(). On receipt of a shared interrupt in that window, bdc_udc_interrupt() dereferences bdc->srr.sr_bds[bdc->srr.dqp_index] (NULL or freed DMA) and dispatches sr_handler callbacks that index into bdc_ep_array, causing a NULL-deref or use-after-free. The same window affects the delayed_work bdc->func_wake_notify, which is armed from the IRQ handler via bdc_sr_uspc() -> handle_link_state_change() -> schedule_delayed_work() and may self-rearm from its own callback bdc_func_wake_timer(). No cancel exists anywhere in the driver, so a queued work item that fires after bdc_remove() returns and the bdc structure is devm-freed dereferences freed memory. Replace devm_request_irq() with request_irq() and add an explicit free_irq(bdc->irq, bdc) in bdc_remove(). Clear BDC_GIE before free_irq() to stop the device from asserting interrupts, then free_irq() drains any in-flight handler, then cancel_delayed_work_sync() drains the func_wake_notify delayed work. This ordering ensures the IRQ handler and delayed work cannot interfere with the subsequent endpoint and DMA teardown in bdc_udc_exit() and bdc_hw_exit(). Wire the matching free_irq() into the bdc_udc_init() error path so the IRQ is released on probe failure, and route the bdc_init_ep() failure through err0 instead of returning directly. This issue was found by an in-house static analysis tool.

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 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: udc: bdc: free IRQ and drain func_wake_notify before teardown The Broadcom BDC UDC driver registers its IRQ handler with devm_request_irq() in bdc_udc_init(), so the IRQ is released by devm only after bdc_remove() returns. devm releases resources in reverse LIFO order, but bdc_remove() runs bdc_udc_exit() and bdc_hw_exit() -> bdc_mem_free() manually before returning: bdc_udc_exit() tears down individual endpoint objects via bdc_free_ep(), while bdc_hw_exit() -> bdc_mem_free() frees and NULLs the DMA-coherent status-report ring (bdc->srr.sr_bds) and kfree()s bdc->bdc_ep_array. Both happen while the IRQ handler (bdc_udc_interrupt, requested with IRQF_SHARED) remains deliverable in the window up to the post-remove devm free_irq(). On receipt of a shared interrupt in that window, bdc_udc_interrupt() dereferences bdc->srr.sr_bds[bdc->srr.dqp_index] (NULL or freed DMA) and dispatches sr_handler callbacks that index into bdc_ep_array, causing a NULL-deref or use-after-free. The same window affects the delayed_work bdc->func_wake_notify, which is armed from the IRQ handler via bdc_sr_uspc() -> handle_link_state_change() -> schedule_delayed_work() and may self-rearm from its own callback bdc_func_wake_timer(). No cancel exists anywhere in the driver, so a queued work item that fires after bdc_remove() returns and the bdc structure is devm-freed dereferences freed memory. Replace devm_request_irq() with request_irq() and add an explicit free_irq(bdc->irq, bdc) in bdc_remove(). Clear BDC_GIE before free_irq() to stop the device from asserting interrupts, then free_irq() drains any in-flight handler, then cancel_delayed_work_sync() drains the func_wake_notify delayed work. This ordering ensures the IRQ handler and delayed work cannot interfere with the subsequent endpoint and DMA teardown in bdc_udc_exit() and bdc_hw_exit(). Wire the matching free_irq() into the bdc_udc_init() error path so the IRQ is released on probe failure, and route the bdc_init_ep() failure through err0 instead of returning directly. This issue was found by an in-house static analysis tool.

What

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: udc: bdc: free IRQ and drain func_wake_notify before teardown The Broadcom BDC UDC driver registers its IRQ handler with devm_request_irq() in bdc_udc_init(), so the IRQ is released by devm only after bdc_remove() returns. devm releases resources in reverse LIFO order, but bdc_remove() runs bdc_udc_exit() and bdc_hw_exit() -> bdc_mem_free() manually before returning: bdc_udc_exit() tears down individual endpoint objects via bdc_free_ep(), while bdc_hw_exit() -> bdc_mem_free() frees and NULLs the DMA-coherent status-report ring (bdc->srr.sr_bds) and kfree()s bdc->bdc_ep_array. Both happen while the IRQ handler (bdc_udc_interrupt, requested with IRQF_SHARED) remains deliverable in the window up to the post-remove devm free_irq(). On receipt of a shared interrupt in that window, bdc_udc_interrupt() dereferences bdc->srr.sr_bds[bdc->srr.dqp_index] (NULL or freed DMA) and dispatches sr_handler callbacks that index into bdc_ep_array, causing a NULL-deref or use-after-free. The same window affects the delayed_work bdc->func_wake_notify, which is armed from the IRQ handler via bdc_sr_uspc() -> handle_link_state_change() -> schedule_delayed_work() and may self-rearm from its own callback bdc_func_wake_timer(). No cancel exists anywhere in the driver, so a queued work item that fires after bdc_remove() returns and the bdc structure is devm-freed dereferences freed memory. Replace devm_request_irq() with request_irq() and add an explicit free_irq(bdc->irq, bdc) in bdc_remove(). Clear BDC_GIE before free_irq() to stop the device from asserting interrupts, then free_irq() drains any in-flight handler, then cancel_delayed_work_sync() drains the func_wake_notify delayed work. This ordering ensures the IRQ handler and delayed work cannot interfere with the subsequent endpoint and DMA teardown in bdc_udc_exit() and bdc_hw_exit(). Wire the matching free_irq() into the bdc_udc_init() error path so the IRQ is released on probe failure, and route the bdc_init_ep() failure through err0 instead of returning directly. This issue was found by an in-house static analysis tool.

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: udc: bdc: free IRQ and drain func_wake_notify before teardown The Broadcom BDC UDC driver registers its IRQ handler with devm_request_irq() in bdc_udc_init(), so the IRQ is released by devm only after bdc_remove() returns. devm releases resources in reverse LIFO order, but bdc_remove() runs bdc_udc_exit() and bdc_hw_exit() -> bdc_mem_free() manually before returning: bdc_udc_exit() tears down individual endpoint objects via bdc_free_ep(), while bdc_hw_exit() -> bdc_mem_free() frees and NULLs the DMA-coherent status-report ring (bdc->srr.sr_bds) and kfree()s bdc->bdc_ep_array. Both happen while the IRQ handler (bdc_udc_interrupt, requested with IRQF_SHARED) remains deliverable in the window up to the post-remove devm free_irq(). On receipt of a shared interrupt in that window, bdc_udc_interrupt() dereferences bdc->srr.sr_bds[bdc->srr.dqp_index] (NULL or freed DMA) and dispatches sr_handler callbacks that index into bdc_ep_array, causing a NULL-deref or use-after-free. The same window affects the delayed_work bdc->func_wake_notify, which is armed from the IRQ handler via bdc_sr_uspc() -> handle_link_state_change() -> schedule_delayed_work() and may self-rearm from its own callback bdc_func_wake_timer(). No cancel exists anywhere in the driver, so a queued work item that fires after bdc_remove() returns and the bdc structure is devm-freed dereferences freed memory. Replace devm_request_irq() with request_irq() and add an explicit free_irq(bdc->irq, bdc) in bdc_remove(). Clear BDC_GIE before free_irq() to stop the device from asserting interrupts, then free_irq() drains any in-flight handler, then cancel_delayed_work_sync() drains the func_wake_notify delayed work. This ordering ensures the IRQ handler and delayed work cannot interfere with the subsequent endpoint and DMA teardown in bdc_udc_exit() and bdc_hw_exit(). Wire the matching free_irq() into the bdc_udc_init() error path so the IRQ is released on probe failure, and route the bdc_init_ep() failure through err0 instead of returning directly. This issue was found by an in-house static analysis tool.

Why

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

How

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

02

Exploit reality and attack path

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

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

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

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

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

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

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

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

Official authority intelligence

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

ENISA EUVD · EUVD-2026-53770Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: udc: bdc: free IRQ and drain func_wake_notify before teardown The Broadcom BDC UDC driver registers its IRQ handler with devm_request_irq() in bdc_udc_init(), so the IRQ is released by devm only after bdc_remove() returns. devm releases resources in reverse LIFO order, but bdc_remove() runs bdc_udc_exit() and bdc_hw_exit() -> bdc_mem_free() manually before returning: bdc_udc_exit() tears down individual endpoint objects via bdc_free_ep(), while bdc_hw_exit() -> bdc_mem_free() frees and NULLs the DMA-coherent status-report ring (bdc->srr.sr_bds) and kfree()s bdc->bdc_ep_array. Both happen while the IRQ handler (bdc_udc_interrupt, requested with IRQF_SHARED) remains deliverable in the window up to the post-remove devm free_irq(). On receipt of a shared interrupt in that window, bdc_udc_interrupt() dereferences bdc->srr.sr_bds[bdc->srr.dqp_index] (NULL or freed DMA) and dispatches sr_handler callbacks that index into bdc_ep_array, causing a NULL-deref or use-after-free. The same window affects the delayed_work bdc->func_wake_notify, which is armed from the IRQ handler via bdc_sr_uspc() -> handle_link_state_change() -> schedule_delayed_work() and may self-rearm from its own callback bdc_func_wake_timer(). No cancel exists anywhere in the driver, so a queued work item that fires after bdc_remove() returns and the bdc structure is devm-freed dereferences freed memory. Replace devm_request_irq() with request_irq() and add an explicit free_irq(bdc->irq, bdc) in bdc_remove(). Clear BDC_GIE before free_irq() to stop the device from asserting interrupts, then free_irq() drains any in-flight handler, then cancel_delayed_work_sync() drains the func_wake_notify delayed work. This ordering ensures the IRQ handler and delayed work cannot interfere with the subsequent endpoint and DMA teardown in bdc_udc_exit() and bdc_hw_exit(). Wire the matching free_irq() into the bdc_udc_init() error path so the IRQ is released on probe failure, and route the bdc_init_ep() failure through err0 instead of returning directly. This issue was found by an in-house static analysis tool.

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

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise das Auslösen eines Denial-of-Service-Zustands, die Umgehung von Sicherheitsmaßnahmen oder das Verursachen von Speicherbeschädigungen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260812Security Bulletin 12 Aug 2026

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

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

d?id=CVE-2026-64571 Référence CVE CVE-2026-64572 https://www.cve.org/CVERecord?id=CVE-2026-64572 Référence CVE CVE-2026-64573 https://www.cve.org/CVERecord?id=CVE-2026-64573 Référence CVE CVE-2026-64574 https://www.cve.org/CVERecord?id=CVE-2026-64574 Référence CVE CVE-2026-64576 https://www.cve.org/CVERecord?id=CVE-2026-64576 Référence CVE CVE-2026-64577 https://www.cve.org/CVERecord?id=CVE-2026-64577 Référence CVE CVE-2026-64579 https://www.cve.org/CVERecord?id=CVE-2026-64579 Référence CVE CVE-2026-64581 https://www.cve.org/CVERecord?id=CVE-2026-64581 Référence CVE CVE-2026-64582 https://www.cve.org/CVERecord?id=CVE-2026-64582 Référence CVE CVE-2026-64583 https://www.cve.org/CVERecord?id=CVE-2026-64583 Référence CVE CVE-2026-64584 https://www.cve.org/CVERecord?id=CVE-2026-64584 Référence CVE CVE-2026-64585 https://www.cve.org/CVERecord?id=CVE-2026-64585 Référence CVE CVE-2026-64586 https://www.cve.org/CVERecord?id=CVE-2026-64586 Référence CVE CVE-2026-64589 https://www.cve.org/CVERecord?id=CVE-2026-64589 Référence CVE CVE-2026-64593 https://www.cve.org/CVERecord?id=CVE-2026-64593 Référence CVE CVE-2026-64599 https://www.cve.org/CVERecord?id=CVE-2026-64599 Référence CVE CVE-2026-64602 https://www.cve.org/CVERecord?id=CVE-2026-64602 Référence CVE CVE-2026-64603 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64570 Référence CVE CVE-2026-64571 https://www.cve.org/CVERecord?id=CVE-2026-64571 Référence CVE CVE-2026-64572 https://www.cve.org/CVERecord?id=CVE-2026-64572 Référence CVE CVE-2026-64573 https://www.cve.org/CVERecord?id=CVE-2026-64573 Référence CVE CVE-2026-64574 https://www.cve.org/CVERecord?id=CVE-2026-64574 Référence CVE CVE-2026-64576 https://www.cve.org/CVERecord?id=CVE-2026-64576 Référence CVE CVE-2026-64577 https://www.cve.org/CVERecord?id=CVE-2026-64577 Référence CVE CVE-2026-64581 https://www.cve.org/CVERecord?id=CVE-2026-64581 Référence CVE CVE-2026-64582 https://www.cve.org/CVERecord?id=CVE-2026-64582 Référence CVE CVE-2026-64583 https://www.cve.org/CVERecord?id=CVE-2026-64583 Référence CVE CVE-2026-64584 https://www.cve.org/CVERecord?id=CVE-2026-64584 Référence CVE CVE-2026-64585 https://www.cve.org/CVERecord?id=CVE-2026-64585 Référence CVE CVE-2026-64593 https://www.cve.org/CVERecord?id=CVE-2026-64593 Référence CVE CVE-2026-64597 https://www.cve.org/CVERecord?id=CVE-2026-64597 Référence CVE CVE-2026-64598 https://www.cve.org/CVERecord?id=CVE-2026-64598 Référence CVE CVE-2026-64599 https://www.cve.org/CVERecord?id=CVE-2026-64599 Référence CVE CVE-2026-64600 https://www.cve.org/CVERecord?id=CVE-2026-64600 Référence CVE CVE-2026-64602 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64572 Référence CVE CVE-2026-64573 https://www.cve.org/CVERecord?id=CVE-2026-64573 Référence CVE CVE-2026-64576 https://www.cve.org/CVERecord?id=CVE-2026-64576 Référence CVE CVE-2026-64577 https://www.cve.org/CVERecord?id=CVE-2026-64577 Référence CVE CVE-2026-64578 https://www.cve.org/CVERecord?id=CVE-2026-64578 Référence CVE CVE-2026-64579 https://www.cve.org/CVERecord?id=CVE-2026-64579 Référence CVE CVE-2026-64580 https://www.cve.org/CVERecord?id=CVE-2026-64580 Référence CVE CVE-2026-64581 https://www.cve.org/CVERecord?id=CVE-2026-64581 Référence CVE CVE-2026-64582 https://www.cve.org/CVERecord?id=CVE-2026-64582 Référence CVE CVE-2026-64583 https://www.cve.org/CVERecord?id=CVE-2026-64583 Référence CVE CVE-2026-64584 https://www.cve.org/CVERecord?id=CVE-2026-64584 Référence CVE CVE-2026-64586 https://www.cve.org/CVERecord?id=CVE-2026-64586 Référence CVE CVE-2026-64590 https://www.cve.org/CVERecord?id=CVE-2026-64590 Référence CVE CVE-2026-68082 https://www.cve.org/CVERecord?id=CVE-2026-68082 Référence CVE CVE-2026-68093 https://www.cve.org/CVERecord?id=CVE-2026-68093 Référence CVE CVE-2026-68096 https://www.cve.org/CVERecord?id=CVE-2026-68096 Référence CVE CVE-2026-68099 https://www.cve.org/CVERecord?id=CVE-2026-68099 Référence CVE CVE-2026-68100 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64570 Référence CVE CVE-2026-64571 https://www.cve.org/CVERecord?id=CVE-2026-64571 Référence CVE CVE-2026-64572 https://www.cve.org/CVERecord?id=CVE-2026-64572 Référence CVE CVE-2026-64573 https://www.cve.org/CVERecord?id=CVE-2026-64573 Référence CVE CVE-2026-64574 https://www.cve.org/CVERecord?id=CVE-2026-64574 Référence CVE CVE-2026-64576 https://www.cve.org/CVERecord?id=CVE-2026-64576 Référence CVE CVE-2026-64577 https://www.cve.org/CVERecord?id=CVE-2026-64577 Référence CVE CVE-2026-64581 https://www.cve.org/CVERecord?id=CVE-2026-64581 Référence CVE CVE-2026-64582 https://www.cve.org/CVERecord?id=CVE-2026-64582 Référence CVE CVE-2026-64583 https://www.cve.org/CVERecord?id=CVE-2026-64583 Référence CVE CVE-2026-64584 https://www.cve.org/CVERecord?id=CVE-2026-64584 Référence CVE CVE-2026-64585 https://www.cve.org/CVERecord?id=CVE-2026-64585 Référence CVE CVE-2026-64593 https://www.cve.org/CVERecord?id=CVE-2026-64593 Référence CVE CVE-2026-64597 https://www.cve.org/CVERecord?id=CVE-2026-64597 Référence CVE CVE-2026-64598 https://www.cve.org/CVERecord?id=CVE-2026-64598 Référence CVE CVE-2026-64599 https://www.cve.org/CVERecord?id=CVE-2026-64599 Référence CVE CVE-2026-64600 https://www.cve.org/CVERecord?id=CVE-2026-64600 Référence CVE CVE-2026-64602 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64571 Référence CVE CVE-2026-64572 https://www.cve.org/CVERecord?id=CVE-2026-64572 Référence CVE CVE-2026-64573 https://www.cve.org/CVERecord?id=CVE-2026-64573 Référence CVE CVE-2026-64574 https://www.cve.org/CVERecord?id=CVE-2026-64574 Référence CVE CVE-2026-64576 https://www.cve.org/CVERecord?id=CVE-2026-64576 Référence CVE CVE-2026-64577 https://www.cve.org/CVERecord?id=CVE-2026-64577 Référence CVE CVE-2026-64578 https://www.cve.org/CVERecord?id=CVE-2026-64578 Référence CVE CVE-2026-64579 https://www.cve.org/CVERecord?id=CVE-2026-64579 Référence CVE CVE-2026-64580 https://www.cve.org/CVERecord?id=CVE-2026-64580 Référence CVE CVE-2026-64583 https://www.cve.org/CVERecord?id=CVE-2026-64583 Référence CVE CVE-2026-64584 https://www.cve.org/CVERecord?id=CVE-2026-64584 Référence CVE CVE-2026-68093 https://www.cve.org/CVERecord?id=CVE-2026-68093 Référence CVE CVE-2026-68096 https://www.cve.org/CVERecord?id=CVE-2026-68096 Référence CVE CVE-2026-68097 https://www.cve.org/CVERecord?id=CVE-2026-68097 Référence CVE CVE-2026-68098 https://www.cve.org/CVERecord?id=CVE-2026-68098 Référence CVE CVE-2026-68099 https://www.cve.org/CVERecord?id=CVE-2026-68099 Référence CVE CVE-2026-68100 https://www.cve.org/CVERecord?id=CVE-2026-68100 Référence CVE CVE-2026-68102 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64571 Référence CVE CVE-2026-64572 https://www.cve.org/CVERecord?id=CVE-2026-64572 Référence CVE CVE-2026-64573 https://www.cve.org/CVERecord?id=CVE-2026-64573 Référence CVE CVE-2026-64574 https://www.cve.org/CVERecord?id=CVE-2026-64574 Référence CVE CVE-2026-64576 https://www.cve.org/CVERecord?id=CVE-2026-64576 Référence CVE CVE-2026-64577 https://www.cve.org/CVERecord?id=CVE-2026-64577 Référence CVE CVE-2026-64578 https://www.cve.org/CVERecord?id=CVE-2026-64578 Référence CVE CVE-2026-64579 https://www.cve.org/CVERecord?id=CVE-2026-64579 Référence CVE CVE-2026-64580 https://www.cve.org/CVERecord?id=CVE-2026-64580 Référence CVE CVE-2026-64583 https://www.cve.org/CVERecord?id=CVE-2026-64583 Référence CVE CVE-2026-64584 https://www.cve.org/CVERecord?id=CVE-2026-64584 Gestion détaillée du document le 14 août 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

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: < 3.19, 5.10.266 ≤ 5.10.*, 5.15.216 ≤ 5.15.*, 6.1.183 ≤ 6.1.*, 6.6.148 ≤ 6.6.*, 6.12.101 ≤ 6.12.*, 6.18.42 ≤ 6.18.*, 7.1.6 ≤ 7.1.*, 7.2 ≤ *
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 6 Aug 2026 · Last source change 23 Aug 2026, 12:45 UTC · CWE not yet assigned

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

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/eac1107e54679db2df2c36d8bba3b66d3ab6cbcd; removed remediation: git.kernel.org/0b0b76e31b3991a899ae724eb97d359de0c0f1b1.
    Before
    remediation: git.kernel.org/0b0b76e31b3991a899ae724eb97d359de0c0f1b1
    After
    remediation: git.kernel.org/eac1107e54679db2df2c36d8bba3b66d3ab6cbcd
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    efed421a94e62a7ddbc76acba4312b70e4be958f < 0b0b76e31b3991a899ae724eb97d359de0c0f1b1; efed421a94e62a7ddbc76acba4312b70e4be958f < 3fe181952b8a1aeb167d4503c794c0f5050f08ed; efed421a94e62a7ddbc76acba4312b70e4be958f < 1a1d7158420df6b8fa1efc0cdd6ab704801a4fc8; efed421a94e62a7ddbc76acba4312b70e4be958f < f6fc21ec7ccd83726ba766d73d0b8cc03e726475; efed421a94e62a7ddbc76acba4312b70e4be958f < dcf3e2f164435b5844706cb8eefef29ebee0eedb; efed421a94e62a7ddbc76acba4312b70e4be958f < d4964a74717107697999f48bcb4e80a9c0679a27; efed421a94e62a7ddbc76acba4312b70e4be958f < 0583f2fbf8f86ae3a0ce054f96783dd83e65d9bb; 3.19 · Fixed: < 3.19; 5.15.216 ≤ 5.15.*; 6.1.183 ≤ 6.1.*; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2 ≤ *
    After
    efed421a94e62a7ddbc76acba4312b70e4be958f < eac1107e54679db2df2c36d8bba3b66d3ab6cbcd; efed421a94e62a7ddbc76acba4312b70e4be958f < 0b0b76e31b3991a899ae724eb97d359de0c0f1b1; efed421a94e62a7ddbc76acba4312b70e4be958f < 3fe181952b8a1aeb167d4503c794c0f5050f08ed; efed421a94e62a7ddbc76acba4312b70e4be958f < 1a1d7158420df6b8fa1efc0cdd6ab704801a4fc8; efed421a94e62a7ddbc76acba4312b70e4be958f < f6fc21ec7ccd83726ba766d73d0b8cc03e726475; efed421a94e62a7ddbc76acba4312b70e4be958f < dcf3e2f164435b5844706cb8eefef29ebee0eedb; efed421a94e62a7ddbc76acba4312b70e4be958f < d4964a74717107697999f48bcb4e80a9c0679a27; efed421a94e62a7ddbc76acba4312b70e4be958f < 0583f2fbf8f86ae3a0ce054f96783dd83e65d9bb · Fixed: < 3.19; 5.10.266 ≤ 5.10.*; 5.15.216 ≤ 5.15.*; 6.1.183 ≤ 6.1.*; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*
    CNA ↗
  3. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/0b0b76e31b3991a899ae724eb97d359de0c0f1b1; removed remediation: git.kernel.org/1a1d7158420df6b8fa1efc0cdd6ab704801a4fc8.
    Before
    remediation: git.kernel.org/1a1d7158420df6b8fa1efc0cdd6ab704801a4fc8
    After
    remediation: git.kernel.org/0b0b76e31b3991a899ae724eb97d359de0c0f1b1
    CNA ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    efed421a94e62a7ddbc76acba4312b70e4be958f < 1a1d7158420df6b8fa1efc0cdd6ab704801a4fc8; efed421a94e62a7ddbc76acba4312b70e4be958f < f6fc21ec7ccd83726ba766d73d0b8cc03e726475; efed421a94e62a7ddbc76acba4312b70e4be958f < dcf3e2f164435b5844706cb8eefef29ebee0eedb; efed421a94e62a7ddbc76acba4312b70e4be958f < d4964a74717107697999f48bcb4e80a9c0679a27; efed421a94e62a7ddbc76acba4312b70e4be958f < 0583f2fbf8f86ae3a0ce054f96783dd83e65d9bb; 3.19 · Fixed: < 3.19; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2 ≤ *
    After
    efed421a94e62a7ddbc76acba4312b70e4be958f < 0b0b76e31b3991a899ae724eb97d359de0c0f1b1; efed421a94e62a7ddbc76acba4312b70e4be958f < 3fe181952b8a1aeb167d4503c794c0f5050f08ed; efed421a94e62a7ddbc76acba4312b70e4be958f < 1a1d7158420df6b8fa1efc0cdd6ab704801a4fc8; efed421a94e62a7ddbc76acba4312b70e4be958f < f6fc21ec7ccd83726ba766d73d0b8cc03e726475; efed421a94e62a7ddbc76acba4312b70e4be958f < dcf3e2f164435b5844706cb8eefef29ebee0eedb; efed421a94e62a7ddbc76acba4312b70e4be958f < d4964a74717107697999f48bcb4e80a9c0679a27; efed421a94e62a7ddbc76acba4312b70e4be958f < 0583f2fbf8f86ae3a0ce054f96783dd83e65d9bb; 3.19 · Fixed: < 3.19; 5.15.216 ≤ 5.15.*; 6.1.183 ≤ 6.1.*; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    efed421a94e62a7ddbc76acba4312b70e4be958f < 1a1d7158420df6b8fa1efc0cdd6ab704801a4fc8; efed421a94e62a7ddbc76acba4312b70e4be958f < f6fc21ec7ccd83726ba766d73d0b8cc03e726475; efed421a94e62a7ddbc76acba4312b70e4be958f < dcf3e2f164435b5844706cb8eefef29ebee0eedb; efed421a94e62a7ddbc76acba4312b70e4be958f < d4964a74717107697999f48bcb4e80a9c0679a27; efed421a94e62a7ddbc76acba4312b70e4be958f < 0583f2fbf8f86ae3a0ce054f96783dd83e65d9bb; 3.19 · Fixed: < 3.19; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2-rc5 ≤ *
    After
    efed421a94e62a7ddbc76acba4312b70e4be958f < 1a1d7158420df6b8fa1efc0cdd6ab704801a4fc8; efed421a94e62a7ddbc76acba4312b70e4be958f < f6fc21ec7ccd83726ba766d73d0b8cc03e726475; efed421a94e62a7ddbc76acba4312b70e4be958f < dcf3e2f164435b5844706cb8eefef29ebee0eedb; efed421a94e62a7ddbc76acba4312b70e4be958f < d4964a74717107697999f48bcb4e80a9c0679a27; efed421a94e62a7ddbc76acba4312b70e4be958f < 0583f2fbf8f86ae3a0ce054f96783dd83e65d9bb; 3.19 · Fixed: < 3.19; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-53770↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-64583 · cve.blacktree.nl