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

Input: alps - fix use-after-free bugs caused by dev3_register_work

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 253 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 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.14% 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 253 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
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-2025-68822 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: Input: alps - fix use-after-free bugs caused by dev3_register_work
232 known affected

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

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A use-after-free flaw was found in the Linux kernel's ALPS touchpad driver. A race condition exists between device disconnection and the dev3_register_work delayed work item. During disconnect, the alps_data structure can be freed while the delayed work is still executing, causing the work function to access freed memory.
Remediation
Fix deferred
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-2280

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 253 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: Input: alps - fix use-after-free bugs caused by dev3_register_work The dev3_register_work delayed work item is initialized within alps_reconnect() and scheduled upon receipt of the first bare PS/2 packet from an external PS/2 device connected to the ALPS touchpad. During device detachment, the original implementation calls flush_workqueue() in psmouse_disconnect() to ensure completion of dev3_register_work. However, the flush_workqueue() in psmouse_disconnect() only blocks and waits for work items that were already queued to the workqueue prior to its invocation. Any work items submitted after flush_workqueue() is called are not included in the set of tasks that the flush operation awaits. This means that after flush_workqueue() has finished executing, the dev3_register_work could still be scheduled. Although the psmouse state is set to PSMOUSE_CMD_MODE in psmouse_disconnect(), the scheduling of dev3_register_work remains unaffected. The race condition can occur as follows: CPU 0 (cleanup path) | CPU 1 (delayed work) psmouse_disconnect() | psmouse_set_state() | flush_workqueue() | alps_report_bare_ps2_packet() alps_disconnect() | psmouse_queue_work() kfree(priv); // FREE | alps_register_bare_ps2_mouse() | priv = container_of(work...); // USE | priv->dev3 // USE Add disable_delayed_work_sync() in alps_disconnect() to ensure that dev3_register_work is properly canceled and prevented from executing after the alps_data structure has been deallocated. This bug is identified by static analysis.

What

In the Linux kernel, the following vulnerability has been resolved: Input: alps - fix use-after-free bugs caused by dev3_register_work The dev3_register_work delayed work item is initialized within alps_reconnect() and scheduled upon receipt of the first bare PS/2 packet from an external PS/2 device connected to the ALPS touchpad. During device detachment, the original implementation calls flush_workqueue() in psmouse_disconnect() to ensure completion of dev3_register_work. However, the flush_workqueue() in psmouse_disconnect() only blocks and waits for work items that were already queued to the workqueue prior to its invocation. Any work items submitted after flush_workqueue() is called are not included in the set of tasks that the flush operation awaits. This means that after flush_workqueue() has finished executing, the dev3_register_work could still be scheduled. Although the psmouse state is set to PSMOUSE_CMD_MODE in psmouse_disconnect(), the scheduling of dev3_register_work remains unaffected. The race condition can occur as follows: CPU 0 (cleanup path) | CPU 1 (delayed work) psmouse_disconnect() | psmouse_set_state() | flush_workqueue() | alps_report_bare_ps2_packet() alps_disconnect() | psmouse_queue_work() kfree(priv); // FREE | alps_register_bare_ps2_mouse() | priv = container_of(work...); // USE | priv->dev3 // USE Add disable_delayed_work_sync() in alps_disconnect() to ensure that dev3_register_work is properly canceled and prevented from executing after the alps_data structure has been deallocated. This bug is identified by 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 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: Input: alps - fix use-after-free bugs caused by dev3_register_work The dev3_register_work delayed work item is initialized within alps_reconnect() and scheduled upon receipt of the first bare PS/2 packet from an external PS/2 device connected to the ALPS touchpad. During device detachment, the original implementation calls flush_workqueue() in psmouse_disconnect() to ensure completion of dev3_register_work. However, the flush_workqueue() in psmouse_disconnect() only blocks and waits for work items that were already queued to the workqueue prior to its invocation. Any work items submitted after flush_workqueue() is called are not included in the set of tasks that the flush operation awaits. This means that after flush_workqueue() has finished executing, the dev3_register_work could still be scheduled. Although the psmouse state is set to PSMOUSE_CMD_MODE in psmouse_disconnect(), the scheduling of dev3_register_work remains unaffected. The race condition can occur as follows: CPU 0 (cleanup path) | CPU 1 (delayed work) psmouse_disconnect() | psmouse_set_state() | flush_workqueue() | alps_report_bare_ps2_packet() alps_disconnect() | psmouse_queue_work() kfree(priv); // FREE | alps_register_bare_ps2_mouse() | priv = container_of(work...); // USE | priv->dev3 // USE Add disable_delayed_work_sync() in alps_disconnect() to ensure that dev3_register_work is properly canceled and prevented from executing after the alps_data structure has been deallocated. This bug is identified by 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 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.

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-1203Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-40170 Référence CVE CVE-2025-40203 https://www.cve.org/CVERecord?id=CVE-2025-40203 Référence CVE CVE-2025-40274 https://www.cve.org/CVERecord?id=CVE-2025-40274 Référence CVE CVE-2025-40344 https://www.cve.org/CVERecord?id=CVE-2025-40344 Référence CVE CVE-2025-40354 https://www.cve.org/CVERecord?id=CVE-2025-40354 Référence CVE CVE-2025-68174 https://www.cve.org/CVERecord?id=CVE-2025-68174 Référence CVE CVE-2025-68304 https://www.cve.org/CVERecord?id=CVE-2025-68304 Référence CVE CVE-2025-68360 https://www.cve.org/CVERecord?id=CVE-2025-68360 Référence CVE CVE-2025-68745 https://www.cve.org/CVERecord?id=CVE-2025-68745 Référence CVE CVE-2025-68822 https://www.cve.org/CVERecord?id=CVE-2025-68822 Référence CVE CVE-2025-71073 https://www.cve.org/CVERecord?id=CVE-2025-71073 Référence CVE CVE-2025-71074 https://www.cve.org/CVERecord?id=CVE-2025-71074 Référence CVE CVE-2025-71202 https://www.cve.org/CVERecord?id=CVE-2025-71202 Référence CVE CVE-2025-71289 https://www.cve.org/CVERecord?id=CVE-2025-71289 Référence CVE CVE-2026-23208 https://www.cve.org/CVERecord?id=CVE-2026-23208 Référence CVE CVE-2026-23239 https://www.cve.org/CVERecord?id=CVE-2026-23239 Référence CVE CVE-2026-23240 https://www.cve.org/CVERecord?id=CVE-2026-23240 Référence CVE CVE-2026-23327 https://www.cve.org/CVERecord?id=

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

nnouncement/2026/suse-su-20262799-1 Bulletin de sécurité SUSE SUSE-SU-2026:2800-1 du 08 juillet 2026 https://www.suse.com/support/update/announcement/2026/suse-su-20262800-1 Référence CVE CVE-2025-10263 https://www.cve.org/CVERecord?id=CVE-2025-10263 Référence CVE CVE-2025-38549 https://www.cve.org/CVERecord?id=CVE-2025-38549 Référence CVE CVE-2025-40216 https://www.cve.org/CVERecord?id=CVE-2025-40216 Référence CVE CVE-2025-40341 https://www.cve.org/CVERecord?id=CVE-2025-40341 Référence CVE CVE-2025-54518 https://www.cve.org/CVERecord?id=CVE-2025-54518 Référence CVE CVE-2025-68324 https://www.cve.org/CVERecord?id=CVE-2025-68324 Référence CVE CVE-2025-68822 https://www.cve.org/CVERecord?id=CVE-2025-68822 Référence CVE CVE-2025-71294 https://www.cve.org/CVERecord?id=CVE-2025-71294 Référence CVE CVE-2026-23278 https://www.cve.org/CVERecord?id=CVE-2026-23278 Référence CVE CVE-2026-23303 https://www.cve.org/CVERecord?id=CVE-2026-23303 Référence CVE CVE-2026-23327 https://www.cve.org/CVERecord?id=CVE-2026-23327 Référence CVE CVE-2026-23359 https://www.cve.org/CVERecord?id=CVE-2026-23359 Référence CVE CVE-2026-23438 https://www.cve.org/CVERecord?id=CVE-2026-23438 Référence CVE CVE-2026-23444 https://www.cve.org/CVERecord?id=CVE-2026-23444 Référence CVE CVE-2026-23451 https://www.cve.org/CVERecord?id=

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

support/update/announcement/2026/suse-su-202622433-1 Bulletin de sécurité SUSE SUSE-SU-2026:22436-1 du 30 juin 2026 https://www.suse.com/support/update/announcement/2026/suse-su-202622436-1 Bulletin de sécurité SUSE SUSE-SU-2026:2722-1 du 01 juillet 2026 https://www.suse.com/support/update/announcement/2026/suse-su-20262722-1 Référence CVE CVE-2025-10263 https://www.cve.org/CVERecord?id=CVE-2025-10263 Référence CVE CVE-2025-38549 https://www.cve.org/CVERecord?id=CVE-2025-38549 Référence CVE CVE-2025-54518 https://www.cve.org/CVERecord?id=CVE-2025-54518 Référence CVE CVE-2025-68324 https://www.cve.org/CVERecord?id=CVE-2025-68324 Référence CVE CVE-2025-68822 https://www.cve.org/CVERecord?id=CVE-2025-68822 Référence CVE CVE-2026-23278 https://www.cve.org/CVERecord?id=CVE-2026-23278 Référence CVE CVE-2026-23303 https://www.cve.org/CVERecord?id=CVE-2026-23303 Référence CVE CVE-2026-23327 https://www.cve.org/CVERecord?id=CVE-2026-23327 Référence CVE CVE-2026-23359 https://www.cve.org/CVERecord?id=CVE-2026-23359 Référence CVE CVE-2026-23392 https://www.cve.org/CVERecord?id=CVE-2026-23392 Référence CVE CVE-2026-23438 https://www.cve.org/CVERecord?id=CVE-2026-23438 Référence CVE CVE-2026-23444 https://www.cve.org/CVERecord?id=CVE-2026-23444 Référence CVE CVE-2026-31396 https://www.cve.org/CVERecord?id=

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

é SUSE SUSE-SU-2026:2421-1 du 16 juin 2026 https://www.suse.com/support/update/announcement/2026/suse-su-20262421-1 Bulletin de sécurité SUSE SUSE-SU-2026:2450-1 du 18 juin 2026 https://www.suse.com/support/update/announcement/2026/suse-su-20262450-1 Référence CVE CVE-2023-20585 https://www.cve.org/CVERecord?id=CVE-2023-20585 Référence CVE CVE-2025-10263 https://www.cve.org/CVERecord?id=CVE-2025-10263 Référence CVE CVE-2025-38549 https://www.cve.org/CVERecord?id=CVE-2025-38549 Référence CVE CVE-2025-40253 https://www.cve.org/CVERecord?id=CVE-2025-40253 Référence CVE CVE-2025-68324 https://www.cve.org/CVERecord?id=CVE-2025-68324 Référence CVE CVE-2025-68822 https://www.cve.org/CVERecord?id=CVE-2025-68822 Référence CVE CVE-2026-23254 https://www.cve.org/CVERecord?id=CVE-2026-23254 Référence CVE CVE-2026-23271 https://www.cve.org/CVERecord?id=CVE-2026-23271 Référence CVE CVE-2026-23279 https://www.cve.org/CVERecord?id=CVE-2026-23279 Référence CVE CVE-2026-23303 https://www.cve.org/CVERecord?id=CVE-2026-23303 Référence CVE CVE-2026-23327 https://www.cve.org/CVERecord?id=CVE-2026-23327 Référence CVE CVE-2026-23359 https://www.cve.org/CVERecord?id=CVE-2026-23359 Référence CVE CVE-2026-23367 https://www.cve.org/CVERecord?id=CVE-2026-23367 Référence CVE CVE-2026-23380 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68813 Référence CVE CVE-2025-68814 https://www.cve.org/CVERecord?id=CVE-2025-68814 Référence CVE CVE-2025-68815 https://www.cve.org/CVERecord?id=CVE-2025-68815 Référence CVE CVE-2025-68816 https://www.cve.org/CVERecord?id=CVE-2025-68816 Référence CVE CVE-2025-68817 https://www.cve.org/CVERecord?id=CVE-2025-68817 Référence CVE CVE-2025-68818 https://www.cve.org/CVERecord?id=CVE-2025-68818 Référence CVE CVE-2025-68819 https://www.cve.org/CVERecord?id=CVE-2025-68819 Référence CVE CVE-2025-68820 https://www.cve.org/CVERecord?id=CVE-2025-68820 Référence CVE CVE-2025-68821 https://www.cve.org/CVERecord?id=CVE-2025-68821 Référence CVE CVE-2025-68822 https://www.cve.org/CVERecord?id=CVE-2025-68822 Référence CVE CVE-2025-68823 https://www.cve.org/CVERecord?id=CVE-2025-68823 Référence CVE CVE-2025-71064 https://www.cve.org/CVERecord?id=CVE-2025-71064 Référence CVE CVE-2025-71065 https://www.cve.org/CVERecord?id=CVE-2025-71065 Référence CVE CVE-2025-71066 https://www.cve.org/CVERecord?id=CVE-2025-71066 Référence CVE CVE-2025-71067 https://www.cve.org/CVERecord?id=CVE-2025-71067 Référence CVE CVE-2025-71068 https://www.cve.org/CVERecord?id=CVE-2025-71068 Référence CVE CVE-2025-71069 https://www.cve.org/CVERecord?id=CVE-2025-71069 Référence CVE CVE-2025-71070 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-68813 Référence CVE CVE-2025-68814 https://www.cve.org/CVERecord?id=CVE-2025-68814 Référence CVE CVE-2025-68815 https://www.cve.org/CVERecord?id=CVE-2025-68815 Référence CVE CVE-2025-68816 https://www.cve.org/CVERecord?id=CVE-2025-68816 Référence CVE CVE-2025-68817 https://www.cve.org/CVERecord?id=CVE-2025-68817 Référence CVE CVE-2025-68818 https://www.cve.org/CVERecord?id=CVE-2025-68818 Référence CVE CVE-2025-68819 https://www.cve.org/CVERecord?id=CVE-2025-68819 Référence CVE CVE-2025-68820 https://www.cve.org/CVERecord?id=CVE-2025-68820 Référence CVE CVE-2025-68821 https://www.cve.org/CVERecord?id=CVE-2025-68821 Référence CVE CVE-2025-68822 https://www.cve.org/CVERecord?id=CVE-2025-68822 Référence CVE CVE-2025-68823 https://www.cve.org/CVERecord?id=CVE-2025-68823 Référence CVE CVE-2025-71064 https://www.cve.org/CVERecord?id=CVE-2025-71064 Référence CVE CVE-2025-71065 https://www.cve.org/CVERecord?id=CVE-2025-71065 Référence CVE CVE-2025-71066 https://www.cve.org/CVERecord?id=CVE-2025-71066 Référence CVE CVE-2025-71067 https://www.cve.org/CVERecord?id=CVE-2025-71067 Référence CVE CVE-2025-71068 https://www.cve.org/CVERecord?id=CVE-2025-71068 Référence CVE CVE-2025-71069 https://www.cve.org/CVERecord?id=CVE-2025-71069 Référence CVE CVE-2025-71070 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-68813 Référence CVE CVE-2025-68814 https://www.cve.org/CVERecord?id=CVE-2025-68814 Référence CVE CVE-2025-68815 https://www.cve.org/CVERecord?id=CVE-2025-68815 Référence CVE CVE-2025-68816 https://www.cve.org/CVERecord?id=CVE-2025-68816 Référence CVE CVE-2025-68817 https://www.cve.org/CVERecord?id=CVE-2025-68817 Référence CVE CVE-2025-68818 https://www.cve.org/CVERecord?id=CVE-2025-68818 Référence CVE CVE-2025-68819 https://www.cve.org/CVERecord?id=CVE-2025-68819 Référence CVE CVE-2025-68820 https://www.cve.org/CVERecord?id=CVE-2025-68820 Référence CVE CVE-2025-68821 https://www.cve.org/CVERecord?id=CVE-2025-68821 Référence CVE CVE-2025-68822 https://www.cve.org/CVERecord?id=CVE-2025-68822 Référence CVE CVE-2025-68972 https://www.cve.org/CVERecord?id=CVE-2025-68972 Référence CVE CVE-2025-69418 https://www.cve.org/CVERecord?id=CVE-2025-69418 Référence CVE CVE-2025-69419 https://www.cve.org/CVERecord?id=CVE-2025-69419 Référence CVE CVE-2025-69420 https://www.cve.org/CVERecord?id=CVE-2025-69420 Référence CVE CVE-2025-69421 https://www.cve.org/CVERecord?id=CVE-2025-69421 Référence CVE CVE-2025-69534 https://www.cve.org/CVERecord?id=CVE-2025-69534 Référence CVE CVE-2025-69644 https://www.cve.org/CVERecord?id=CVE-2025-69644 Référence CVE CVE-2025-69645 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-68813 Référence CVE CVE-2025-68814 https://www.cve.org/CVERecord?id=CVE-2025-68814 Référence CVE CVE-2025-68815 https://www.cve.org/CVERecord?id=CVE-2025-68815 Référence CVE CVE-2025-68816 https://www.cve.org/CVERecord?id=CVE-2025-68816 Référence CVE CVE-2025-68817 https://www.cve.org/CVERecord?id=CVE-2025-68817 Référence CVE CVE-2025-68818 https://www.cve.org/CVERecord?id=CVE-2025-68818 Référence CVE CVE-2025-68819 https://www.cve.org/CVERecord?id=CVE-2025-68819 Référence CVE CVE-2025-68820 https://www.cve.org/CVERecord?id=CVE-2025-68820 Référence CVE CVE-2025-68821 https://www.cve.org/CVERecord?id=CVE-2025-68821 Référence CVE CVE-2025-68822 https://www.cve.org/CVERecord?id=CVE-2025-68822 Référence CVE CVE-2025-68972 https://www.cve.org/CVERecord?id=CVE-2025-68972 Référence CVE CVE-2025-69418 https://www.cve.org/CVERecord?id=CVE-2025-69418 Référence CVE CVE-2025-69419 https://www.cve.org/CVERecord?id=CVE-2025-69419 Référence CVE CVE-2025-69420 https://www.cve.org/CVERecord?id=CVE-2025-69420 Référence CVE CVE-2025-69421 https://www.cve.org/CVERecord?id=CVE-2025-69421 Référence CVE CVE-2025-69534 https://www.cve.org/CVERecord?id=CVE-2025-69534 Référence CVE CVE-2025-69644 https://www.cve.org/CVERecord?id=CVE-2025-69644 Référence CVE CVE-2025-69645 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68808 Référence CVE CVE-2025-68811 https://www.cve.org/CVERecord?id=CVE-2025-68811 Référence CVE CVE-2025-68813 https://www.cve.org/CVERecord?id=CVE-2025-68813 Référence CVE CVE-2025-68814 https://www.cve.org/CVERecord?id=CVE-2025-68814 Référence CVE CVE-2025-68815 https://www.cve.org/CVERecord?id=CVE-2025-68815 Référence CVE CVE-2025-68816 https://www.cve.org/CVERecord?id=CVE-2025-68816 Référence CVE CVE-2025-68819 https://www.cve.org/CVERecord?id=CVE-2025-68819 Référence CVE CVE-2025-68820 https://www.cve.org/CVERecord?id=CVE-2025-68820 Référence CVE CVE-2025-68821 https://www.cve.org/CVERecord?id=CVE-2025-68821 Référence CVE CVE-2025-68822 https://www.cve.org/CVERecord?id=CVE-2025-68822 Référence CVE CVE-2025-71064 https://www.cve.org/CVERecord?id=CVE-2025-71064 Référence CVE CVE-2025-71066 https://www.cve.org/CVERecord?id=CVE-2025-71066 Référence CVE CVE-2025-71073 https://www.cve.org/CVERecord?id=CVE-2025-71073 Référence CVE CVE-2025-71076 https://www.cve.org/CVERecord?id=CVE-2025-71076 Référence CVE CVE-2025-71077 https://www.cve.org/CVERecord?id=CVE-2025-71077 Référence CVE CVE-2025-71078 https://www.cve.org/CVERecord?id=CVE-2025-71078 Référence CVE CVE-2025-71079 https://www.cve.org/CVERecord?id=CVE-2025-71079 Référence CVE CVE-2025-71080 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-68813 Référence CVE CVE-2025-68814 https://www.cve.org/CVERecord?id=CVE-2025-68814 Référence CVE CVE-2025-68815 https://www.cve.org/CVERecord?id=CVE-2025-68815 Référence CVE CVE-2025-68816 https://www.cve.org/CVERecord?id=CVE-2025-68816 Référence CVE CVE-2025-68817 https://www.cve.org/CVERecord?id=CVE-2025-68817 Référence CVE CVE-2025-68818 https://www.cve.org/CVERecord?id=CVE-2025-68818 Référence CVE CVE-2025-68819 https://www.cve.org/CVERecord?id=CVE-2025-68819 Référence CVE CVE-2025-68820 https://www.cve.org/CVERecord?id=CVE-2025-68820 Référence CVE CVE-2025-68821 https://www.cve.org/CVERecord?id=CVE-2025-68821 Référence CVE CVE-2025-68822 https://www.cve.org/CVERecord?id=CVE-2025-68822 Référence CVE CVE-2025-71064 https://www.cve.org/CVERecord?id=CVE-2025-71064 Référence CVE CVE-2025-71065 https://www.cve.org/CVERecord?id=CVE-2025-71065 Référence CVE CVE-2025-71066 https://www.cve.org/CVERecord?id=CVE-2025-71066 Référence CVE CVE-2025-71067 https://www.cve.org/CVERecord?id=CVE-2025-71067 Référence CVE CVE-2025-71068 https://www.cve.org/CVERecord?id=CVE-2025-71068 Référence CVE CVE-2025-71069 https://www.cve.org/CVERecord?id=CVE-2025-71069 Référence CVE CVE-2025-71071 https://www.cve.org/CVERecord?id=CVE-2025-71071 Référence CVE CVE-2025-71072 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
Fixed
Linux: < 4.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 5 Aug 2026, 12:11 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-2280
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceUnavailable
NVD statusNVD not scheduled

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

Material change intelligence

What changed after publication

View recent updates ↗

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

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-2280↗Vendor CSAF · Red Hat Product Security↗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-68822 · cve.blacktree.nl