BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-39801High confidence

usb: dwc3: Remove WARN_ON for device endpoint command timeouts

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 22 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 12 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.15% 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 22 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 21 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.48-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.153-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.16.5-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.16.5-1Debian Security Tracker ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-intelAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

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

2 current
CVE-2025-39801 · CSAF 2.0 · revision 49 · interimSUSE Product Security TeamCVE-2025-39801
339 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP5
Summary
In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: Remove WARN_ON for device endpoint command timeouts This commit addresses a rarely observed endpoint command timeout which causes kernel panic due to warn when 'panic_on_warn' is enabled and unnecessary call trace prints when 'panic_on_warn' is disabled. It is seen during fast software-controlled connect/disconnect testcases. The following is one such endpoint command timeout that we observed: 1. Connect ======= ->dwc3_thread_interrupt ->dwc3_ep0_interrupt ->configfs_composite_setup ->composite_setup ->usb_ep_queue ->dwc3_gadget_ep0_queue ->__dwc3_gadget_ep0_queue ->__dwc3_ep0_do_control_data ->dwc3_send_gadget_ep_cmd 2. Disconnect ========== ->dwc3_thread_interrupt ->dwc3_gadget_disconnect_interrupt ->dwc3_ep0_reset_state ->dwc3_ep0_end_control_data ->dwc3_send_gadget_ep_cmd In the issue scenario, in Exynos platforms, we observed that control transfers for the previous connect have not yet been completed and end transfer command sent as a part of the disconnect sequence and processing of USB_ENDPOINT_HALT feature request from the host timeout. This maybe an expected scenario since the controller is processing EP commands sent as a part of the previous connect. It maybe better to remove WARN_ON in all places where device endpoint commands are sent to avoid unnecessary kernel panic due to warn.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
SSA-032379 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-032379: Multiple Vulnerabilities in SIMATIC CN 4100 Before V5.0
1 known affected

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

  • SIMATIC CN 4100
Summary
In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: Remove WARN_ON for device endpoint command timeouts This commit addresses a rarely observed endpoint command timeout which causes kernel panic due to warn when 'panic_on_warn' is enabled and unnecessary call trace prints when 'panic_on_warn' is disabled. It is seen during fast software-controlled connect/disconnect testcases. The following is one such endpoint command timeout that we observed: 1. Connect ======= ->dwc3_thread_interrupt ->dwc3_ep0_interrupt ->configfs_composite_setup ->composite_setup ->usb_ep_queue ->dwc3_gadget_ep0_queue ->__dwc3_gadget_ep0_queue ->__dwc3_ep0_do_control_data ->dwc3_send_gadget_ep_cmd 2. Disconnect ========== ->dwc3_thread_interrupt ->dwc3_gadget_disconnect_interrupt ->dwc3_ep0_reset_state ->dwc3_ep0_end_control_data ->dwc3_send_gadget_ep_cmd In the issue scenario, in Exynos platforms, we observed that control transfers for the previous connect have not yet been completed and end transfer command sent as a part of the disconnect sequence and processing of USB_ENDPOINT_HALT feature request from the host timeout. This maybe an expected scenario since the controller is processing EP commands sent as a part of the previous connect. It maybe better to remove WARN_ON in all places where device endpoint commands are sent to avoid unnecessary kernel panic due to warn.
Remediation
Update to V5.0 or later version
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-2025-29185

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 22 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: dwc3: Remove WARN_ON for device endpoint command timeouts This commit addresses a rarely observed endpoint command timeout which causes kernel panic due to warn when 'panic_on_warn' is enabled and unnecessary call trace prints when 'panic_on_warn' is disabled. It is seen during fast software-controlled connect/disconnect testcases. The following is one such endpoint command timeout that we observed: 1. Connect ======= ->dwc3_thread_interrupt ->dwc3_ep0_interrupt ->configfs_composite_setup ->composite_setup ->usb_ep_queue ->dwc3_gadget_ep0_queue ->__dwc3_gadget_ep0_queue ->__dwc3_ep0_do_control_data ->dwc3_send_gadget_ep_cmd 2. Disconnect ========== ->dwc3_thread_interrupt ->dwc3_gadget_disconnect_interrupt ->dwc3_ep0_reset_state ->dwc3_ep0_end_control_data ->dwc3_send_gadget_ep_cmd In the issue scenario, in Exynos platforms, we observed that control transfers for the previous connect have not yet been completed and end transfer command sent as a part of the disconnect sequence and processing of USB_ENDPOINT_HALT feature request from the host timeout. This maybe an expected scenario since the controller is processing EP commands sent as a part of the previous connect. It maybe better to remove WARN_ON in all places where device endpoint commands are sent to avoid unnecessary kernel panic due to warn.

What

In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: Remove WARN_ON for device endpoint command timeouts This commit addresses a rarely observed endpoint command timeout which causes kernel panic due to warn when 'panic_on_warn' is enabled and unnecessary call trace prints when 'panic_on_warn' is disabled. It is seen during fast software-controlled connect/disconnect testcases. The following is one such endpoint command timeout that we observed: 1. Connect ======= ->dwc3_thread_interrupt ->dwc3_ep0_interrupt ->configfs_composite_setup ->composite_setup ->usb_ep_queue ->dwc3_gadget_ep0_queue ->__dwc3_gadget_ep0_queue ->__dwc3_ep0_do_control_data ->dwc3_send_gadget_ep_cmd 2. Disconnect ========== ->dwc3_thread_interrupt ->dwc3_gadget_disconnect_interrupt ->dwc3_ep0_reset_state ->dwc3_ep0_end_control_data ->dwc3_send_gadget_ep_cmd In the issue scenario, in Exynos platforms, we observed that control transfers for the previous connect have not yet been completed and end transfer command sent as a part of the disconnect sequence and processing of USB_ENDPOINT_HALT feature request from the host timeout. This maybe an expected scenario since the controller is processing EP commands sent as a part of the previous connect. It maybe better to remove WARN_ON in all places where device endpoint commands are sent to avoid unnecessary kernel panic due to warn.

Why

The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

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: dwc3: Remove WARN_ON for device endpoint command timeouts This commit addresses a rarely observed endpoint command timeout which causes kernel panic due to warn when 'panic_on_warn' is enabled and unnecessary call trace prints when 'panic_on_warn' is disabled. It is seen during fast software-controlled connect/disconnect testcases. The following is one such endpoint command timeout that we observed: 1. Connect ======= ->dwc3_thread_interrupt ->dwc3_ep0_interrupt ->configfs_composite_setup ->composite_setup ->usb_ep_queue ->dwc3_gadget_ep0_queue ->__dwc3_gadget_ep0_queue ->__dwc3_ep0_do_control_data ->dwc3_send_gadget_ep_cmd 2. Disconnect ========== ->dwc3_thread_interrupt ->dwc3_gadget_disconnect_interrupt ->dwc3_ep0_reset_state ->dwc3_ep0_end_control_data ->dwc3_send_gadget_ep_cmd In the issue scenario, in Exynos platforms, we observed that control transfers for the previous connect have not yet been completed and end transfer command sent as a part of the disconnect sequence and processing of USB_ENDPOINT_HALT feature request from the host timeout. This maybe an expected scenario since the controller is processing EP commands sent as a part of the previous connect. It maybe better to remove WARN_ON in all places where device endpoint commands are sent to avoid unnecessary kernel panic due to warn.

Why

The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

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 → Reachable Assertion → 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-617 ↗

CWE-617: Reachable Assertion. The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

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

Official authority intelligence

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

BSI · German · WID-SEC-2025-2053Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250917SECURITY BULLETIN 17 SEPT 2025

The Cyber Security Agency of Singapore included this CVE in its official SECURITY BULLETIN 17 SEPT 2025, published on 17 September 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2025-39782 Référence CVE CVE-2025-39783 https://www.cve.org/CVERecord?id=CVE-2025-39783 Référence CVE CVE-2025-39787 https://www.cve.org/CVERecord?id=CVE-2025-39787 Référence CVE CVE-2025-39788 https://www.cve.org/CVERecord?id=CVE-2025-39788 Référence CVE CVE-2025-39790 https://www.cve.org/CVERecord?id=CVE-2025-39790 Référence CVE CVE-2025-39794 https://www.cve.org/CVERecord?id=CVE-2025-39794 Référence CVE CVE-2025-39795 https://www.cve.org/CVERecord?id=CVE-2025-39795 Référence CVE CVE-2025-39798 https://www.cve.org/CVERecord?id=CVE-2025-39798 Référence CVE CVE-2025-39800 https://www.cve.org/CVERecord?id=CVE-2025-39800 Référence CVE CVE-2025-39801 https://www.cve.org/CVERecord?id=CVE-2025-39801 Référence CVE CVE-2025-39806 https://www.cve.org/CVERecord?id=CVE-2025-39806 Référence CVE CVE-2025-39808 https://www.cve.org/CVERecord?id=CVE-2025-39808 Référence CVE CVE-2025-39812 https://www.cve.org/CVERecord?id=CVE-2025-39812 Référence CVE CVE-2025-39813 https://www.cve.org/CVERecord?id=CVE-2025-39813 Référence CVE CVE-2025-39817 https://www.cve.org/CVERecord?id=CVE-2025-39817 Référence CVE CVE-2025-39819 https://www.cve.org/CVERecord?id=CVE-2025-39819 Référence CVE CVE-2025-39823 https://www.cve.org/CVERecord?id=CVE-2025-39823 Référence CVE CVE-2025-39824 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39783 Référence CVE CVE-2025-39787 https://www.cve.org/CVERecord?id=CVE-2025-39787 Référence CVE CVE-2025-39788 https://www.cve.org/CVERecord?id=CVE-2025-39788 Référence CVE CVE-2025-39790 https://www.cve.org/CVERecord?id=CVE-2025-39790 Référence CVE CVE-2025-39794 https://www.cve.org/CVERecord?id=CVE-2025-39794 Référence CVE CVE-2025-39795 https://www.cve.org/CVERecord?id=CVE-2025-39795 Référence CVE CVE-2025-39797 https://www.cve.org/CVERecord?id=CVE-2025-39797 Référence CVE CVE-2025-39798 https://www.cve.org/CVERecord?id=CVE-2025-39798 Référence CVE CVE-2025-39800 https://www.cve.org/CVERecord?id=CVE-2025-39800 Référence CVE CVE-2025-39801 https://www.cve.org/CVERecord?id=CVE-2025-39801 Référence CVE CVE-2025-39889 https://www.cve.org/CVERecord?id=CVE-2025-39889 Référence CVE CVE-2025-39890 https://www.cve.org/CVERecord?id=CVE-2025-39890 Référence CVE CVE-2025-39946 https://www.cve.org/CVERecord?id=CVE-2025-39946 Référence CVE CVE-2025-39989 https://www.cve.org/CVERecord?id=CVE-2025-39989 Référence CVE CVE-2025-40019 https://www.cve.org/CVERecord?id=CVE-2025-40019 Référence CVE CVE-2025-40214 https://www.cve.org/CVERecord?id=CVE-2025-40214 Référence CVE CVE-2025-40215 https://www.cve.org/CVERecord?id=CVE-2025-40215 Référence CVE CVE-2025-40297 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39783 Référence CVE CVE-2025-39787 https://www.cve.org/CVERecord?id=CVE-2025-39787 Référence CVE CVE-2025-39788 https://www.cve.org/CVERecord?id=CVE-2025-39788 Référence CVE CVE-2025-39790 https://www.cve.org/CVERecord?id=CVE-2025-39790 Référence CVE CVE-2025-39794 https://www.cve.org/CVERecord?id=CVE-2025-39794 Référence CVE CVE-2025-39795 https://www.cve.org/CVERecord?id=CVE-2025-39795 Référence CVE CVE-2025-39797 https://www.cve.org/CVERecord?id=CVE-2025-39797 Référence CVE CVE-2025-39798 https://www.cve.org/CVERecord?id=CVE-2025-39798 Référence CVE CVE-2025-39800 https://www.cve.org/CVERecord?id=CVE-2025-39800 Référence CVE CVE-2025-39801 https://www.cve.org/CVERecord?id=CVE-2025-39801 Référence CVE CVE-2025-39889 https://www.cve.org/CVERecord?id=CVE-2025-39889 Référence CVE CVE-2025-39890 https://www.cve.org/CVERecord?id=CVE-2025-39890 Référence CVE CVE-2025-39946 https://www.cve.org/CVERecord?id=CVE-2025-39946 Référence CVE CVE-2025-39989 https://www.cve.org/CVERecord?id=CVE-2025-39989 Référence CVE CVE-2025-40001 https://www.cve.org/CVERecord?id=CVE-2025-40001 Référence CVE CVE-2025-40002 https://www.cve.org/CVERecord?id=CVE-2025-40002 Référence CVE CVE-2025-40003 https://www.cve.org/CVERecord?id=CVE-2025-40003 Référence CVE CVE-2025-40004 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39783 Référence CVE CVE-2025-39787 https://www.cve.org/CVERecord?id=CVE-2025-39787 Référence CVE CVE-2025-39788 https://www.cve.org/CVERecord?id=CVE-2025-39788 Référence CVE CVE-2025-39790 https://www.cve.org/CVERecord?id=CVE-2025-39790 Référence CVE CVE-2025-39794 https://www.cve.org/CVERecord?id=CVE-2025-39794 Référence CVE CVE-2025-39795 https://www.cve.org/CVERecord?id=CVE-2025-39795 Référence CVE CVE-2025-39797 https://www.cve.org/CVERecord?id=CVE-2025-39797 Référence CVE CVE-2025-39798 https://www.cve.org/CVERecord?id=CVE-2025-39798 Référence CVE CVE-2025-39800 https://www.cve.org/CVERecord?id=CVE-2025-39800 Référence CVE CVE-2025-39801 https://www.cve.org/CVERecord?id=CVE-2025-39801 Référence CVE CVE-2025-39869 https://www.cve.org/CVERecord?id=CVE-2025-39869 Référence CVE CVE-2025-39873 https://www.cve.org/CVERecord?id=CVE-2025-39873 Référence CVE CVE-2025-39876 https://www.cve.org/CVERecord?id=CVE-2025-39876 Référence CVE CVE-2025-39880 https://www.cve.org/CVERecord?id=CVE-2025-39880 Référence CVE CVE-2025-39883 https://www.cve.org/CVERecord?id=CVE-2025-39883 Référence CVE CVE-2025-39885 https://www.cve.org/CVERecord?id=CVE-2025-39885 Référence CVE CVE-2025-39889 https://www.cve.org/CVERecord?id=CVE-2025-39889 Référence CVE CVE-2025-39890 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39783 Référence CVE CVE-2025-39787 https://www.cve.org/CVERecord?id=CVE-2025-39787 Référence CVE CVE-2025-39788 https://www.cve.org/CVERecord?id=CVE-2025-39788 Référence CVE CVE-2025-39790 https://www.cve.org/CVERecord?id=CVE-2025-39790 Référence CVE CVE-2025-39794 https://www.cve.org/CVERecord?id=CVE-2025-39794 Référence CVE CVE-2025-39795 https://www.cve.org/CVERecord?id=CVE-2025-39795 Référence CVE CVE-2025-39797 https://www.cve.org/CVERecord?id=CVE-2025-39797 Référence CVE CVE-2025-39798 https://www.cve.org/CVERecord?id=CVE-2025-39798 Référence CVE CVE-2025-39800 https://www.cve.org/CVERecord?id=CVE-2025-39800 Référence CVE CVE-2025-39801 https://www.cve.org/CVERecord?id=CVE-2025-39801 Référence CVE CVE-2025-39869 https://www.cve.org/CVERecord?id=CVE-2025-39869 Référence CVE CVE-2025-39873 https://www.cve.org/CVERecord?id=CVE-2025-39873 Référence CVE CVE-2025-39876 https://www.cve.org/CVERecord?id=CVE-2025-39876 Référence CVE CVE-2025-39880 https://www.cve.org/CVERecord?id=CVE-2025-39880 Référence CVE CVE-2025-39883 https://www.cve.org/CVERecord?id=CVE-2025-39883 Référence CVE CVE-2025-39885 https://www.cve.org/CVERecord?id=CVE-2025-39885 Référence CVE CVE-2025-39889 https://www.cve.org/CVERecord?id=CVE-2025-39889 Référence CVE CVE-2025-39890 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39783 Référence CVE CVE-2025-39787 https://www.cve.org/CVERecord?id=CVE-2025-39787 Référence CVE CVE-2025-39788 https://www.cve.org/CVERecord?id=CVE-2025-39788 Référence CVE CVE-2025-39790 https://www.cve.org/CVERecord?id=CVE-2025-39790 Référence CVE CVE-2025-39794 https://www.cve.org/CVERecord?id=CVE-2025-39794 Référence CVE CVE-2025-39795 https://www.cve.org/CVERecord?id=CVE-2025-39795 Référence CVE CVE-2025-39797 https://www.cve.org/CVERecord?id=CVE-2025-39797 Référence CVE CVE-2025-39798 https://www.cve.org/CVERecord?id=CVE-2025-39798 Référence CVE CVE-2025-39800 https://www.cve.org/CVERecord?id=CVE-2025-39800 Référence CVE CVE-2025-39801 https://www.cve.org/CVERecord?id=CVE-2025-39801 Référence CVE CVE-2025-39869 https://www.cve.org/CVERecord?id=CVE-2025-39869 Référence CVE CVE-2025-39873 https://www.cve.org/CVERecord?id=CVE-2025-39873 Référence CVE CVE-2025-39876 https://www.cve.org/CVERecord?id=CVE-2025-39876 Référence CVE CVE-2025-39880 https://www.cve.org/CVERecord?id=CVE-2025-39880 Référence CVE CVE-2025-39883 https://www.cve.org/CVERecord?id=CVE-2025-39883 Référence CVE CVE-2025-39885 https://www.cve.org/CVERecord?id=CVE-2025-39885 Référence CVE CVE-2025-39889 https://www.cve.org/CVERecord?id=CVE-2025-39889 Référence CVE CVE-2025-39890 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39776 Référence CVE CVE-2025-39782 https://www.cve.org/CVERecord?id=CVE-2025-39782 Référence CVE CVE-2025-39783 https://www.cve.org/CVERecord?id=CVE-2025-39783 Référence CVE CVE-2025-39787 https://www.cve.org/CVERecord?id=CVE-2025-39787 Référence CVE CVE-2025-39788 https://www.cve.org/CVERecord?id=CVE-2025-39788 Référence CVE CVE-2025-39790 https://www.cve.org/CVERecord?id=CVE-2025-39790 Référence CVE CVE-2025-39794 https://www.cve.org/CVERecord?id=CVE-2025-39794 Référence CVE CVE-2025-39795 https://www.cve.org/CVERecord?id=CVE-2025-39795 Référence CVE CVE-2025-39798 https://www.cve.org/CVERecord?id=CVE-2025-39798 Référence CVE CVE-2025-39801 https://www.cve.org/CVERecord?id=CVE-2025-39801 Référence CVE CVE-2025-39806 https://www.cve.org/CVERecord?id=CVE-2025-39806 Référence CVE CVE-2025-39808 https://www.cve.org/CVERecord?id=CVE-2025-39808 Référence CVE CVE-2025-39809 https://www.cve.org/CVERecord?id=CVE-2025-39809 Référence CVE CVE-2025-39812 https://www.cve.org/CVERecord?id=CVE-2025-39812 Référence CVE CVE-2025-39813 https://www.cve.org/CVERecord?id=CVE-2025-39813 Référence CVE CVE-2025-39817 https://www.cve.org/CVERecord?id=CVE-2025-39817 Référence CVE CVE-2025-39818 https://www.cve.org/CVERecord?id=CVE-2025-39818 Référence CVE CVE-2025-39823 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39787 Référence CVE CVE-2025-39788 https://www.cve.org/CVERecord?id=CVE-2025-39788 Référence CVE CVE-2025-39790 https://www.cve.org/CVERecord?id=CVE-2025-39790 Référence CVE CVE-2025-39791 https://www.cve.org/CVERecord?id=CVE-2025-39791 Référence CVE CVE-2025-39792 https://www.cve.org/CVERecord?id=CVE-2025-39792 Référence CVE CVE-2025-39794 https://www.cve.org/CVERecord?id=CVE-2025-39794 Référence CVE CVE-2025-39797 https://www.cve.org/CVERecord?id=CVE-2025-39797 Référence CVE CVE-2025-39798 https://www.cve.org/CVERecord?id=CVE-2025-39798 Référence CVE CVE-2025-39800 https://www.cve.org/CVERecord?id=CVE-2025-39800 Référence CVE CVE-2025-39801 https://www.cve.org/CVERecord?id=CVE-2025-39801 Référence CVE CVE-2025-39806 https://www.cve.org/CVERecord?id=CVE-2025-39806 Référence CVE CVE-2025-39807 https://www.cve.org/CVERecord?id=CVE-2025-39807 Référence CVE CVE-2025-39808 https://www.cve.org/CVERecord?id=CVE-2025-39808 Référence CVE CVE-2025-39810 https://www.cve.org/CVERecord?id=CVE-2025-39810 Référence CVE CVE-2025-39811 https://www.cve.org/CVERecord?id=CVE-2025-39811 Référence CVE CVE-2025-39812 https://www.cve.org/CVERecord?id=CVE-2025-39812 Référence CVE CVE-2025-39813 https://www.cve.org/CVERecord?id=CVE-2025-39813 Référence CVE CVE-2025-39816 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39776 Référence CVE CVE-2025-39782 https://www.cve.org/CVERecord?id=CVE-2025-39782 Référence CVE CVE-2025-39783 https://www.cve.org/CVERecord?id=CVE-2025-39783 Référence CVE CVE-2025-39787 https://www.cve.org/CVERecord?id=CVE-2025-39787 Référence CVE CVE-2025-39788 https://www.cve.org/CVERecord?id=CVE-2025-39788 Référence CVE CVE-2025-39790 https://www.cve.org/CVERecord?id=CVE-2025-39790 Référence CVE CVE-2025-39794 https://www.cve.org/CVERecord?id=CVE-2025-39794 Référence CVE CVE-2025-39795 https://www.cve.org/CVERecord?id=CVE-2025-39795 Référence CVE CVE-2025-39798 https://www.cve.org/CVERecord?id=CVE-2025-39798 Référence CVE CVE-2025-39801 https://www.cve.org/CVERecord?id=CVE-2025-39801 Référence CVE CVE-2025-39806 https://www.cve.org/CVERecord?id=CVE-2025-39806 Référence CVE CVE-2025-39808 https://www.cve.org/CVERecord?id=CVE-2025-39808 Référence CVE CVE-2025-39809 https://www.cve.org/CVERecord?id=CVE-2025-39809 Référence CVE CVE-2025-39812 https://www.cve.org/CVERecord?id=CVE-2025-39812 Référence CVE CVE-2025-39813 https://www.cve.org/CVERecord?id=CVE-2025-39813 Référence CVE CVE-2025-39817 https://www.cve.org/CVERecord?id=CVE-2025-39817 Référence CVE CVE-2025-39818 https://www.cve.org/CVERecord?id=CVE-2025-39818 Référence CVE CVE-2025-39823 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39761 Référence CVE CVE-2025-39763 https://www.cve.org/CVERecord?id=CVE-2025-39763 Référence CVE CVE-2025-39772 https://www.cve.org/CVERecord?id=CVE-2025-39772 Référence CVE CVE-2025-39783 https://www.cve.org/CVERecord?id=CVE-2025-39783 Référence CVE CVE-2025-39790 https://www.cve.org/CVERecord?id=CVE-2025-39790 Référence CVE CVE-2025-39794 https://www.cve.org/CVERecord?id=CVE-2025-39794 Référence CVE CVE-2025-39797 https://www.cve.org/CVERecord?id=CVE-2025-39797 Référence CVE CVE-2025-39798 https://www.cve.org/CVERecord?id=CVE-2025-39798 Référence CVE CVE-2025-39800 https://www.cve.org/CVERecord?id=CVE-2025-39800 Référence CVE CVE-2025-39801 https://www.cve.org/CVERecord?id=CVE-2025-39801 Référence CVE CVE-2025-39806 https://www.cve.org/CVERecord?id=CVE-2025-39806 Référence CVE CVE-2025-39808 https://www.cve.org/CVERecord?id=CVE-2025-39808 Référence CVE CVE-2025-39810 https://www.cve.org/CVERecord?id=CVE-2025-39810 Référence CVE CVE-2025-39812 https://www.cve.org/CVERecord?id=CVE-2025-39812 Référence CVE CVE-2025-39813 https://www.cve.org/CVERecord?id=CVE-2025-39813 Référence CVE CVE-2025-39824 https://www.cve.org/CVERecord?id=CVE-2025-39824 Référence CVE CVE-2025-39826 https://www.cve.org/CVERecord?id=CVE-2025-39826 Référence CVE CVE-2025-39827 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39761 Référence CVE CVE-2025-39763 https://www.cve.org/CVERecord?id=CVE-2025-39763 Référence CVE CVE-2025-39772 https://www.cve.org/CVERecord?id=CVE-2025-39772 Référence CVE CVE-2025-39783 https://www.cve.org/CVERecord?id=CVE-2025-39783 Référence CVE CVE-2025-39790 https://www.cve.org/CVERecord?id=CVE-2025-39790 Référence CVE CVE-2025-39794 https://www.cve.org/CVERecord?id=CVE-2025-39794 Référence CVE CVE-2025-39797 https://www.cve.org/CVERecord?id=CVE-2025-39797 Référence CVE CVE-2025-39798 https://www.cve.org/CVERecord?id=CVE-2025-39798 Référence CVE CVE-2025-39800 https://www.cve.org/CVERecord?id=CVE-2025-39800 Référence CVE CVE-2025-39801 https://www.cve.org/CVERecord?id=CVE-2025-39801 Référence CVE CVE-2025-39806 https://www.cve.org/CVERecord?id=CVE-2025-39806 Référence CVE CVE-2025-39808 https://www.cve.org/CVERecord?id=CVE-2025-39808 Référence CVE CVE-2025-39810 https://www.cve.org/CVERecord?id=CVE-2025-39810 Référence CVE CVE-2025-39812 https://www.cve.org/CVERecord?id=CVE-2025-39812 Référence CVE CVE-2025-39813 https://www.cve.org/CVERecord?id=CVE-2025-39813 Référence CVE CVE-2025-39824 https://www.cve.org/CVERecord?id=CVE-2025-39824 Référence CVE CVE-2025-39826 https://www.cve.org/CVERecord?id=CVE-2025-39826 Référence CVE CVE-2025-39827 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39772 Référence CVE CVE-2025-39773 https://www.cve.org/CVERecord?id=CVE-2025-39773 Référence CVE CVE-2025-39782 https://www.cve.org/CVERecord?id=CVE-2025-39782 Référence CVE CVE-2025-39783 https://www.cve.org/CVERecord?id=CVE-2025-39783 Référence CVE CVE-2025-39787 https://www.cve.org/CVERecord?id=CVE-2025-39787 Référence CVE CVE-2025-39790 https://www.cve.org/CVERecord?id=CVE-2025-39790 Référence CVE CVE-2025-39797 https://www.cve.org/CVERecord?id=CVE-2025-39797 Référence CVE CVE-2025-39798 https://www.cve.org/CVERecord?id=CVE-2025-39798 Référence CVE CVE-2025-39800 https://www.cve.org/CVERecord?id=CVE-2025-39800 Référence CVE CVE-2025-39801 https://www.cve.org/CVERecord?id=CVE-2025-39801 Référence CVE CVE-2025-39806 https://www.cve.org/CVERecord?id=CVE-2025-39806 Référence CVE CVE-2025-39807 https://www.cve.org/CVERecord?id=CVE-2025-39807 Référence CVE CVE-2025-39808 https://www.cve.org/CVERecord?id=CVE-2025-39808 Référence CVE CVE-2025-39810 https://www.cve.org/CVERecord?id=CVE-2025-39810 Référence CVE CVE-2025-39811 https://www.cve.org/CVERecord?id=CVE-2025-39811 Référence CVE CVE-2025-39816 https://www.cve.org/CVERecord?id=CVE-2025-39816 Référence CVE CVE-2025-39823 https://www.cve.org/CVERecord?id=CVE-2025-39823 Référence CVE CVE-2025-39824 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39772 Référence CVE CVE-2025-39773 https://www.cve.org/CVERecord?id=CVE-2025-39773 Référence CVE CVE-2025-39782 https://www.cve.org/CVERecord?id=CVE-2025-39782 Référence CVE CVE-2025-39783 https://www.cve.org/CVERecord?id=CVE-2025-39783 Référence CVE CVE-2025-39787 https://www.cve.org/CVERecord?id=CVE-2025-39787 Référence CVE CVE-2025-39790 https://www.cve.org/CVERecord?id=CVE-2025-39790 Référence CVE CVE-2025-39797 https://www.cve.org/CVERecord?id=CVE-2025-39797 Référence CVE CVE-2025-39798 https://www.cve.org/CVERecord?id=CVE-2025-39798 Référence CVE CVE-2025-39800 https://www.cve.org/CVERecord?id=CVE-2025-39800 Référence CVE CVE-2025-39801 https://www.cve.org/CVERecord?id=CVE-2025-39801 Référence CVE CVE-2025-39806 https://www.cve.org/CVERecord?id=CVE-2025-39806 Référence CVE CVE-2025-39807 https://www.cve.org/CVERecord?id=CVE-2025-39807 Référence CVE CVE-2025-39808 https://www.cve.org/CVERecord?id=CVE-2025-39808 Référence CVE CVE-2025-39810 https://www.cve.org/CVERecord?id=CVE-2025-39810 Référence CVE CVE-2025-39811 https://www.cve.org/CVERecord?id=CVE-2025-39811 Référence CVE CVE-2025-39816 https://www.cve.org/CVERecord?id=CVE-2025-39816 Référence CVE CVE-2025-39823 https://www.cve.org/CVERecord?id=CVE-2025-39823 Référence CVE CVE-2025-39824 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39782 Référence CVE CVE-2025-39783 https://www.cve.org/CVERecord?id=CVE-2025-39783 Référence CVE CVE-2025-39787 https://www.cve.org/CVERecord?id=CVE-2025-39787 Référence CVE CVE-2025-39788 https://www.cve.org/CVERecord?id=CVE-2025-39788 Référence CVE CVE-2025-39790 https://www.cve.org/CVERecord?id=CVE-2025-39790 Référence CVE CVE-2025-39794 https://www.cve.org/CVERecord?id=CVE-2025-39794 Référence CVE CVE-2025-39795 https://www.cve.org/CVERecord?id=CVE-2025-39795 Référence CVE CVE-2025-39798 https://www.cve.org/CVERecord?id=CVE-2025-39798 Référence CVE CVE-2025-39800 https://www.cve.org/CVERecord?id=CVE-2025-39800 Référence CVE CVE-2025-39801 https://www.cve.org/CVERecord?id=CVE-2025-39801 Référence CVE CVE-2025-39806 https://www.cve.org/CVERecord?id=CVE-2025-39806 Référence CVE CVE-2025-39808 https://www.cve.org/CVERecord?id=CVE-2025-39808 Référence CVE CVE-2025-39812 https://www.cve.org/CVERecord?id=CVE-2025-39812 Référence CVE CVE-2025-39813 https://www.cve.org/CVERecord?id=CVE-2025-39813 Référence CVE CVE-2025-39817 https://www.cve.org/CVERecord?id=CVE-2025-39817 Référence CVE CVE-2025-39819 https://www.cve.org/CVERecord?id=CVE-2025-39819 Référence CVE CVE-2025-39823 https://www.cve.org/CVERecord?id=CVE-2025-39823 Référence CVE CVE-2025-39824 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39783 Référence CVE CVE-2025-39787 https://www.cve.org/CVERecord?id=CVE-2025-39787 Référence CVE CVE-2025-39788 https://www.cve.org/CVERecord?id=CVE-2025-39788 Référence CVE CVE-2025-39790 https://www.cve.org/CVERecord?id=CVE-2025-39790 Référence CVE CVE-2025-39791 https://www.cve.org/CVERecord?id=CVE-2025-39791 Référence CVE CVE-2025-39794 https://www.cve.org/CVERecord?id=CVE-2025-39794 Référence CVE CVE-2025-39795 https://www.cve.org/CVERecord?id=CVE-2025-39795 Référence CVE CVE-2025-39798 https://www.cve.org/CVERecord?id=CVE-2025-39798 Référence CVE CVE-2025-39800 https://www.cve.org/CVERecord?id=CVE-2025-39800 Référence CVE CVE-2025-39801 https://www.cve.org/CVERecord?id=CVE-2025-39801 Référence CVE CVE-2025-39805 https://www.cve.org/CVERecord?id=CVE-2025-39805 Référence CVE CVE-2025-39806 https://www.cve.org/CVERecord?id=CVE-2025-39806 Référence CVE CVE-2025-39807 https://www.cve.org/CVERecord?id=CVE-2025-39807 Référence CVE CVE-2025-39808 https://www.cve.org/CVERecord?id=CVE-2025-39808 Référence CVE CVE-2025-39810 https://www.cve.org/CVERecord?id=CVE-2025-39810 Référence CVE CVE-2025-39811 https://www.cve.org/CVERecord?id=CVE-2025-39811 Référence CVE CVE-2025-39812 https://www.cve.org/CVERecord?id=CVE-2025-39812 Référence CVE CVE-2025-39813 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-025309Debian等の複数ベンダの製品における到達可能なアサーションに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました：usb: dwc3のデバイスエンドポイントコマンドのタイムアウトに対するWARN_ONを削除しました。このコミットは、まれに発生するエンドポイントコマンドのタイムアウトに対処しています。これにより、'panic_on_warn'が有効な場合にカーネルパニックを引き起こし、無効な場合には不要なコールトレースが出力されていました。この問題は、ソフトウェア制御の高速な接続／切断テストケース中に確認されています。以下は観測されたエンドポイントコマンドのタイムアウトの一例です。1. 接続時の呼び出しシーケンス：dwc3_thread_interruptからdwc3_ep0_interrupt、configfs_composite_setup、composite_setup、usb_ep_queue、dwc3_gadget_ep0_queue、__dwc3_gadget_ep0_queue、__dwc3_ep0_do_control_data、そしてdwc3_send_gadget_ep_cmdまで。2. 切断時の呼び出しシーケンス：dwc3_thread_interruptからdwc3_gadget_disconnect_interrupt、dwc3_ep0_reset_state、dwc3_ep0_end_control_data、そしてdwc3_send_gadget_ep_cmdまで。問題のシナリオでは、Exynosプラットフォーム上で前回の接続のコントロール転送がまだ完了しておらず、切断シーケンスの一部として送信された終了転送コマンドおよびホストからのUSB_ENDPOINT_HALT機能要求の処理でタイムアウトが発生しました。これはコントローラーが前回の接続の一部として送信されたEPコマンドを処理しているため、予期される状況であるかもしれません。デバイスエンドポイントコマンドを送信するすべての場所でWARN_ONを削除し、警告による不要なカーネルパニックを回避することが適切だと考えられます。

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0147Kwetsbaarheden verholpen in Siemens-producten

Multiple security vulnerabilities affecting AMD processors and various Linux kernel subsystems, including USB, networking, filesystems, and drivers, were identified and fixed across SUSE Linux Enterprise and Micro kernels, alongside a VMSCAPE flaw impacting branch predictor isolation.

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.2, 5.15.190 ≤ 5.15.*, 6.1.149 ≤ 6.1.*, 6.6.103 ≤ 6.6.*, 6.12.44 ≤ 6.12.*, 6.16.4 ≤ 6.16.*, 6.17 ≤ *
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 15 Sept 2025 · Last source change 12 May 2026, 12:07 UTC · CWE-617 · Reachable Assertion

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-2025-29185
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

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

Material change intelligence

What changed after publication

View recent updates ↗

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

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