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

usb: phy: fsl-usb: Fix use-after-free in delayed work during device removal

Linux · Linux

…UnscoredAssess manually
Recommended action
Patch only the product branches with a verified fix

No CVSS base score is available from the CNA, CISA ADP or NIST. Absence of a score is not evidence of low risk; review the vendor advisory, affected exposure and exploit evidence. Verified remediation exists for at least one product or source, but 21 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 severityUnscoredOperational priority:Needs assessment, manual assessment needed.unscored

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.21% 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: Manual assessmentRemediation target: Manual assessment

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

Distribution package intelligence

Release-specific package status

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

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 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.69-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.18.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.18.3-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
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-2329

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: usb: phy: fsl-usb: Fix use-after-free in delayed work during device removal The delayed work item otg_event is initialized in fsl_otg_conf() and scheduled under two conditions: 1. When a host controller binds to the OTG controller. 2. When the USB ID pin state changes (cable insertion/removal). A race condition occurs when the device is removed via fsl_otg_remove(): the fsl_otg instance may be freed while the delayed work is still pending or executing. This leads to use-after-free when the work function fsl_otg_event() accesses the already freed memory. The problematic scenario: (detach thread) | (delayed work) fsl_otg_remove() | kfree(fsl_otg_dev) //FREE| fsl_otg_event() | og = container_of(...) //USE | og-> //USE Fix this by calling disable_delayed_work_sync() in fsl_otg_remove() before deallocating the fsl_otg structure. This ensures the delayed work is properly canceled and completes execution prior to memory deallocation. This bug was identified through static analysis.

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
0.0
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

No CVSS base score is available from the CNA, CISA ADP or NIST. Absence of a score is not evidence of low risk; review the vendor advisory, affected exposure and exploit evidence. Verified remediation exists for at least one product or source, but 21 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: phy: fsl-usb: Fix use-after-free in delayed work during device removal The delayed work item otg_event is initialized in fsl_otg_conf() and scheduled under two conditions: 1. When a host controller binds to the OTG controller. 2. When the USB ID pin state changes (cable insertion/removal). A race condition occurs when the device is removed via fsl_otg_remove(): the fsl_otg instance may be freed while the delayed work is still pending or executing. This leads to use-after-free when the work function fsl_otg_event() accesses the already freed memory. The problematic scenario: (detach thread) | (delayed work) fsl_otg_remove() | kfree(fsl_otg_dev) //FREE| fsl_otg_event() | og = container_of(...) //USE | og-> //USE Fix this by calling disable_delayed_work_sync() in fsl_otg_remove() before deallocating the fsl_otg structure. This ensures the delayed work is properly canceled and completes execution prior to memory deallocation. This bug was identified through static analysis.

What

In the Linux kernel, the following vulnerability has been resolved: usb: phy: fsl-usb: Fix use-after-free in delayed work during device removal The delayed work item otg_event is initialized in fsl_otg_conf() and scheduled under two conditions: 1. When a host controller binds to the OTG controller. 2. When the USB ID pin state changes (cable insertion/removal). A race condition occurs when the device is removed via fsl_otg_remove(): the fsl_otg instance may be freed while the delayed work is still pending or executing. This leads to use-after-free when the work function fsl_otg_event() accesses the already freed memory. The problematic scenario: (detach thread) | (delayed work) fsl_otg_remove() | kfree(fsl_otg_dev) //FREE| fsl_otg_event() | og = container_of(...) //USE | og-> //USE Fix this by calling disable_delayed_work_sync() in fsl_otg_remove() before deallocating the fsl_otg structure. This ensures the delayed work is properly canceled and completes execution prior to memory deallocation. This bug was identified through static analysis.

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 the affected interface may attempt exploitation when the stated preconditions are met. 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: phy: fsl-usb: Fix use-after-free in delayed work during device removal The delayed work item otg_event is initialized in fsl_otg_conf() and scheduled under two conditions: 1. When a host controller binds to the OTG controller. 2. When the USB ID pin state changes (cable insertion/removal). A race condition occurs when the device is removed via fsl_otg_remove(): the fsl_otg instance may be freed while the delayed work is still pending or executing. This leads to use-after-free when the work function fsl_otg_event() accesses the already freed memory. The problematic scenario: (detach thread) | (delayed work) fsl_otg_remove() | kfree(fsl_otg_dev) //FREE| fsl_otg_event() | og = container_of(...) //USE | og-> //USE Fix this by calling disable_delayed_work_sync() in fsl_otg_remove() before deallocating the fsl_otg structure. This ensures the delayed work is properly canceled and completes execution prior to memory deallocation. This bug was identified through static analysis.

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 the affected interface may attempt exploitation when the stated preconditions are met. 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
the affected interface → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Unspecified
Privileges required
Not stated in the selected CVSS metric
User interaction
Not stated in the selected CVSS metric
Attack complexity
Not stated in the selected CVSS metric
Security boundary
Not stated in the selected CVSS metric
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.
Not available from the selected scoring authority.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-2329Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: usb: phy: fsl-usb: Fix use-after-free in delayed work during device removal The delayed work item otg_event is initialized in fsl_otg_conf() and scheduled under two conditions: 1. When a host controller binds to the OTG controller. 2. When the USB ID pin state changes (cable insertion/removal). A race condition occurs when the device is removed via fsl_otg_remove(): the fsl_otg instance may be freed while the delayed work is still pending or executing. This leads to use-after-free when the work function fsl_otg_event() accesses the already freed memory. The problematic scenario: (detach thread) | (delayed work) fsl_otg_remove() | kfree(fsl_otg_dev) //FREE| fsl_otg_event() | og = container_of(...) //USE | og-> //USE Fix this by calling disable_delayed_work_sync() in fsl_otg_remove() before deallocating the fsl_otg structure. This ensures the delayed work is properly canceled and completes execution prior to memory deallocation. This bug was identified through static analysis.

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

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260114Security Bulletin 14 Jan 2026

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

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

d?id=CVE-2025-68771 Référence CVE CVE-2025-68772 https://www.cve.org/CVERecord?id=CVE-2025-68772 Référence CVE CVE-2025-68773 https://www.cve.org/CVERecord?id=CVE-2025-68773 Référence CVE CVE-2025-68774 https://www.cve.org/CVERecord?id=CVE-2025-68774 Référence CVE CVE-2025-68775 https://www.cve.org/CVERecord?id=CVE-2025-68775 Référence CVE CVE-2025-68776 https://www.cve.org/CVERecord?id=CVE-2025-68776 Référence CVE CVE-2025-68777 https://www.cve.org/CVERecord?id=CVE-2025-68777 Référence CVE CVE-2025-68778 https://www.cve.org/CVERecord?id=CVE-2025-68778 Référence CVE CVE-2025-68780 https://www.cve.org/CVERecord?id=CVE-2025-68780 Référence CVE CVE-2025-68781 https://www.cve.org/CVERecord?id=CVE-2025-68781 Référence CVE CVE-2025-68782 https://www.cve.org/CVERecord?id=CVE-2025-68782 Référence CVE CVE-2025-68783 https://www.cve.org/CVERecord?id=CVE-2025-68783 Référence CVE CVE-2025-68784 https://www.cve.org/CVERecord?id=CVE-2025-68784 Référence CVE CVE-2025-68785 https://www.cve.org/CVERecord?id=CVE-2025-68785 Référence CVE CVE-2025-68786 https://www.cve.org/CVERecord?id=CVE-2025-68786 Référence CVE CVE-2025-68787 https://www.cve.org/CVERecord?id=CVE-2025-68787 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68791 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68771 Référence CVE CVE-2025-68772 https://www.cve.org/CVERecord?id=CVE-2025-68772 Référence CVE CVE-2025-68773 https://www.cve.org/CVERecord?id=CVE-2025-68773 Référence CVE CVE-2025-68774 https://www.cve.org/CVERecord?id=CVE-2025-68774 Référence CVE CVE-2025-68775 https://www.cve.org/CVERecord?id=CVE-2025-68775 Référence CVE CVE-2025-68776 https://www.cve.org/CVERecord?id=CVE-2025-68776 Référence CVE CVE-2025-68777 https://www.cve.org/CVERecord?id=CVE-2025-68777 Référence CVE CVE-2025-68778 https://www.cve.org/CVERecord?id=CVE-2025-68778 Référence CVE CVE-2025-68780 https://www.cve.org/CVERecord?id=CVE-2025-68780 Référence CVE CVE-2025-68781 https://www.cve.org/CVERecord?id=CVE-2025-68781 Référence CVE CVE-2025-68782 https://www.cve.org/CVERecord?id=CVE-2025-68782 Référence CVE CVE-2025-68783 https://www.cve.org/CVERecord?id=CVE-2025-68783 Référence CVE CVE-2025-68784 https://www.cve.org/CVERecord?id=CVE-2025-68784 Référence CVE CVE-2025-68785 https://www.cve.org/CVERecord?id=CVE-2025-68785 Référence CVE CVE-2025-68786 https://www.cve.org/CVERecord?id=CVE-2025-68786 Référence CVE CVE-2025-68787 https://www.cve.org/CVERecord?id=CVE-2025-68787 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68791 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68769 Référence CVE CVE-2025-68771 https://www.cve.org/CVERecord?id=CVE-2025-68771 Référence CVE CVE-2025-68772 https://www.cve.org/CVERecord?id=CVE-2025-68772 Référence CVE CVE-2025-68774 https://www.cve.org/CVERecord?id=CVE-2025-68774 Référence CVE CVE-2025-68776 https://www.cve.org/CVERecord?id=CVE-2025-68776 Référence CVE CVE-2025-68777 https://www.cve.org/CVERecord?id=CVE-2025-68777 Référence CVE CVE-2025-68778 https://www.cve.org/CVERecord?id=CVE-2025-68778 Référence CVE CVE-2025-68779 https://www.cve.org/CVERecord?id=CVE-2025-68779 Référence CVE CVE-2025-68780 https://www.cve.org/CVERecord?id=CVE-2025-68780 Référence CVE CVE-2025-68781 https://www.cve.org/CVERecord?id=CVE-2025-68781 Référence CVE CVE-2025-68782 https://www.cve.org/CVERecord?id=CVE-2025-68782 Référence CVE CVE-2025-68783 https://www.cve.org/CVERecord?id=CVE-2025-68783 Référence CVE CVE-2025-68785 https://www.cve.org/CVERecord?id=CVE-2025-68785 Référence CVE CVE-2025-68786 https://www.cve.org/CVERecord?id=CVE-2025-68786 Référence CVE CVE-2025-68787 https://www.cve.org/CVERecord?id=CVE-2025-68787 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68794 https://www.cve.org/CVERecord?id=CVE-2025-68794 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68769 Référence CVE CVE-2025-68771 https://www.cve.org/CVERecord?id=CVE-2025-68771 Référence CVE CVE-2025-68772 https://www.cve.org/CVERecord?id=CVE-2025-68772 Référence CVE CVE-2025-68774 https://www.cve.org/CVERecord?id=CVE-2025-68774 Référence CVE CVE-2025-68776 https://www.cve.org/CVERecord?id=CVE-2025-68776 Référence CVE CVE-2025-68777 https://www.cve.org/CVERecord?id=CVE-2025-68777 Référence CVE CVE-2025-68778 https://www.cve.org/CVERecord?id=CVE-2025-68778 Référence CVE CVE-2025-68779 https://www.cve.org/CVERecord?id=CVE-2025-68779 Référence CVE CVE-2025-68780 https://www.cve.org/CVERecord?id=CVE-2025-68780 Référence CVE CVE-2025-68781 https://www.cve.org/CVERecord?id=CVE-2025-68781 Référence CVE CVE-2025-68782 https://www.cve.org/CVERecord?id=CVE-2025-68782 Référence CVE CVE-2025-68783 https://www.cve.org/CVERecord?id=CVE-2025-68783 Référence CVE CVE-2025-68785 https://www.cve.org/CVERecord?id=CVE-2025-68785 Référence CVE CVE-2025-68786 https://www.cve.org/CVERecord?id=CVE-2025-68786 Référence CVE CVE-2025-68787 https://www.cve.org/CVERecord?id=CVE-2025-68787 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68794 https://www.cve.org/CVERecord?id=CVE-2025-68794 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68769 Référence CVE CVE-2025-68771 https://www.cve.org/CVERecord?id=CVE-2025-68771 Référence CVE CVE-2025-68772 https://www.cve.org/CVERecord?id=CVE-2025-68772 Référence CVE CVE-2025-68773 https://www.cve.org/CVERecord?id=CVE-2025-68773 Référence CVE CVE-2025-68774 https://www.cve.org/CVERecord?id=CVE-2025-68774 Référence CVE CVE-2025-68776 https://www.cve.org/CVERecord?id=CVE-2025-68776 Référence CVE CVE-2025-68777 https://www.cve.org/CVERecord?id=CVE-2025-68777 Référence CVE CVE-2025-68778 https://www.cve.org/CVERecord?id=CVE-2025-68778 Référence CVE CVE-2025-68780 https://www.cve.org/CVERecord?id=CVE-2025-68780 Référence CVE CVE-2025-68781 https://www.cve.org/CVERecord?id=CVE-2025-68781 Référence CVE CVE-2025-68782 https://www.cve.org/CVERecord?id=CVE-2025-68782 Référence CVE CVE-2025-68783 https://www.cve.org/CVERecord?id=CVE-2025-68783 Référence CVE CVE-2025-68785 https://www.cve.org/CVERecord?id=CVE-2025-68785 Référence CVE CVE-2025-68786 https://www.cve.org/CVERecord?id=CVE-2025-68786 Référence CVE CVE-2025-68787 https://www.cve.org/CVERecord?id=CVE-2025-68787 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68771 Référence CVE CVE-2025-68772 https://www.cve.org/CVERecord?id=CVE-2025-68772 Référence CVE CVE-2025-68773 https://www.cve.org/CVERecord?id=CVE-2025-68773 Référence CVE CVE-2025-68774 https://www.cve.org/CVERecord?id=CVE-2025-68774 Référence CVE CVE-2025-68775 https://www.cve.org/CVERecord?id=CVE-2025-68775 Référence CVE CVE-2025-68776 https://www.cve.org/CVERecord?id=CVE-2025-68776 Référence CVE CVE-2025-68777 https://www.cve.org/CVERecord?id=CVE-2025-68777 Référence CVE CVE-2025-68778 https://www.cve.org/CVERecord?id=CVE-2025-68778 Référence CVE CVE-2025-68780 https://www.cve.org/CVERecord?id=CVE-2025-68780 Référence CVE CVE-2025-68781 https://www.cve.org/CVERecord?id=CVE-2025-68781 Référence CVE CVE-2025-68782 https://www.cve.org/CVERecord?id=CVE-2025-68782 Référence CVE CVE-2025-68783 https://www.cve.org/CVERecord?id=CVE-2025-68783 Référence CVE CVE-2025-68784 https://www.cve.org/CVERecord?id=CVE-2025-68784 Référence CVE CVE-2025-68785 https://www.cve.org/CVERecord?id=CVE-2025-68785 Référence CVE CVE-2025-68786 https://www.cve.org/CVERecord?id=CVE-2025-68786 Référence CVE CVE-2025-68787 https://www.cve.org/CVERecord?id=CVE-2025-68787 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68789 https://www.cve.org/CVERecord?id=

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
Linux: 3.0, patch: 6.18.3, patch: 0, 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 2e7c47e2eb3cfeadf78a1ccbac8492c60d508f23, 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 41ca62e3e21e48c2903b3b45e232cf4f2ff7434f, patch: 6.12.64, 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 69f9a0701abc3d1f8225074c56c27e6c16a37222, patch: 6.19
Fixed
Linux: < 3.0, 6.12.64 ≤ 6.12.*, 6.18.3 ≤ 6.18.*, 6.19 ≤ *
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 13 Jan 2026 · Last source change 2 Sept 2026, 12:49 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceUnavailable
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-2329
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD not scheduled

Missing structured fields: CVSS base score, 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. Affected versionsThe structured affected or fixed version information changed.
    Before
    Linux: 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 4476c73bbbb09b13a962176fca934b32d3954a2e, 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 319f7a85b3c4e34ac2fe083eb146fe129a556317, 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 69f9a0701abc3d1f8225074c56c27e6c16a37222, 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 2e7c47e2eb3cfeadf78a1ccbac8492c60d508f23, 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 41ca62e3e21e48c2903b3b45e232cf4f2ff7434f, 3.0 · Fixed: Linux: < 3.0, 6.1.160 ≤ 6.1.*, 6.6.120 ≤ 6.6.*, 6.12.64 ≤ 6.12.*, 6.18.3 ≤ 6.18.*, 6.19 ≤ *
    After
    Linux: 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 69f9a0701abc3d1f8225074c56c27e6c16a37222, 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 2e7c47e2eb3cfeadf78a1ccbac8492c60d508f23, 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 41ca62e3e21e48c2903b3b45e232cf4f2ff7434f, 3.0 · Fixed: Linux: < 3.0, 6.12.64 ≤ 6.12.*, 6.18.3 ≤ 6.18.*, 6.19 ≤ *
    CNA ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/69f9a0701abc3d1f8225074c56c27e6c16a37222; removed remediation: git.kernel.org/4476c73bbbb09b13a962176fca934b32d3954a2e.
    Before
    remediation: git.kernel.org/4476c73bbbb09b13a962176fca934b32d3954a2e
    After
    remediation: git.kernel.org/69f9a0701abc3d1f8225074c56c27e6c16a37222
    CNA ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 4476c73bbbb09b13a962176fca934b32d3954a2e; 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 319f7a85b3c4e34ac2fe083eb146fe129a556317; 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 69f9a0701abc3d1f8225074c56c27e6c16a37222; 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 2e7c47e2eb3cfeadf78a1ccbac8492c60d508f23; 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 41ca62e3e21e48c2903b3b45e232cf4f2ff7434f; 3.0 · Fixed: < 3.0; 6.1.160 ≤ 6.1.*; 6.6.120 ≤ 6.6.*; 6.12.64 ≤ 6.12.*; 6.18.3 ≤ 6.18.*; 6.19 ≤ *
    After
    0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 69f9a0701abc3d1f8225074c56c27e6c16a37222; 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 2e7c47e2eb3cfeadf78a1ccbac8492c60d508f23; 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 41ca62e3e21e48c2903b3b45e232cf4f2ff7434f; 3.0 · Fixed: < 3.0; 6.12.64 ≤ 6.12.*; 6.18.3 ≤ 6.18.*; 6.19 ≤ *
    CNA ↗
  4. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/4476c73bbbb09b13a962176fca934b32d3954a2e; removed remediation: git.kernel.org/69f9a0701abc3d1f8225074c56c27e6c16a37222.
    Before
    remediation: git.kernel.org/69f9a0701abc3d1f8225074c56c27e6c16a37222
    After
    remediation: git.kernel.org/4476c73bbbb09b13a962176fca934b32d3954a2e
    CNA ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 69f9a0701abc3d1f8225074c56c27e6c16a37222; 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 2e7c47e2eb3cfeadf78a1ccbac8492c60d508f23; 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 41ca62e3e21e48c2903b3b45e232cf4f2ff7434f; 3.0 · Fixed: < 3.0; 6.12.64 ≤ 6.12.*; 6.18.3 ≤ 6.18.*; 6.19 ≤ *
    After
    Linux: 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 4476c73bbbb09b13a962176fca934b32d3954a2e, 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 319f7a85b3c4e34ac2fe083eb146fe129a556317, 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 69f9a0701abc3d1f8225074c56c27e6c16a37222, 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 2e7c47e2eb3cfeadf78a1ccbac8492c60d508f23, 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 < 41ca62e3e21e48c2903b3b45e232cf4f2ff7434f, 3.0 · Fixed: Linux: < 3.0, 6.1.160 ≤ 6.1.*, 6.6.120 ≤ 6.6.*, 6.12.64 ≤ 6.12.*, 6.18.3 ≤ 6.18.*, 6.19 ≤ *
    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-2329↗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-2025-68781 · cve.blacktree.nl