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

macintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityUnscoredOperational priority:Needs assessment, manual assessment needed.unscored

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.20% 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 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

24 package states
Package result overrides the generic status

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

Repository candidate not checked

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

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.63-1Debian Security Tracker ↗Source updated 23 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.162-1Debian Security Tracker ↗Source updated 23 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.17.13-1Debian Security Tracker ↗Source updated 23 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.17.13-1Debian Security Tracker ↗Source updated 23 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 23 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 23 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 23 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 23 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 23 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 23 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 23 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 23 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 23 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 23 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 23 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 23 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 23 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 23 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 23 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 23 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 23 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 23 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 23 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 23 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-68367 · CSAF 2.0 · revision 36 · interimSUSE Product Security TeamCVE-2025-68367
437 known affected

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

  • kernel-default as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-source as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
Summary
In the Linux kernel, the following vulnerability has been resolved: macintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse The following warning appears when running syzkaller, and this issue also exists in the mainline code. ------------[ cut here ]------------ list_add double add: new=ffffffffa57eee28, prev=ffffffffa57eee28, next=ffffffffa5e63100. WARNING: CPU: 0 PID: 1491 at lib/list_debug.c:35 __list_add_valid_or_report+0xf7/0x130 Modules linked in: CPU: 0 PID: 1491 Comm: syz.1.28 Not tainted 6.6.0+ #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 RIP: 0010:__list_add_valid_or_report+0xf7/0x130 RSP: 0018:ff1100010dfb7b78 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffffffffa57eee18 RCX: ffffffff97fc9817 RDX: 0000000000040000 RSI: ffa0000002383000 RDI: 0000000000000001 RBP: ffffffffa57eee28 R08: 0000000000000001 R09: ffe21c0021bf6f2c R10: 0000000000000001 R11: 6464615f7473696c R12: ffffffffa5e63100 R13: ffffffffa57eee28 R14: ffffffffa57eee28 R15: ff1100010dfb7d48 FS: 00007fb14398b640(0000) GS:ff11000119600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 000000010d096005 CR4: 0000000000773ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 80000000 Call Trace: input_register_handler+0xb3/0x210 mac_hid_start_emulation+0x1c5/0x290 mac_hid_toggle_emumouse+0x20a/0x240 proc_sys_call_handler+0x4c2/0x6e0 new_sync_write+0x1b1/0x2d0 vfs_write+0x709/0x950 ksys_write+0x12a/0x250 do_syscall_64+0x5a/0x110 entry_SYSCALL_64_after_hwframe+0x78/0xe2 The WARNING occurs when two processes concurrently write to the mac-hid emulation sysctl, causing a race condition in mac_hid_toggle_emumouse(). Both processes read old_val=0, then both try to register the input handler, leading to a double list_add of the same handler. CPU0 CPU1 ------------------------- ------------------------- vfs_write() //write 1 vfs_write() //write 1 proc_sys_write() proc_sys_write() mac_hid_toggle_emumouse() mac_hid_toggle_emumouse() old_val = *valp // old_val=0 old_val = *valp // old_val=0 mutex_lock_killable() proc_dointvec() // *valp=1 mac_hid_start_emulation() input_register_handler() mutex_unlock() mutex_lock_killable() proc_dointvec() mac_hid_start_emulation() input_register_handler() //Trigger Warning mutex_unlock() Fix this by moving the old_val read inside the mutex lock region.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-205087

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

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

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: macintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse The following warning appears when running syzkaller, and this issue also exists in the mainline code. ------------[ cut here ]------------ list_add double add: new=ffffffffa57eee28, prev=ffffffffa57eee28, next=ffffffffa5e63100. WARNING: CPU: 0 PID: 1491 at lib/list_debug.c:35 __list_add_valid_or_report+0xf7/0x130 Modules linked in: CPU: 0 PID: 1491 Comm: syz.1.28 Not tainted 6.6.0+ #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 RIP: 0010:__list_add_valid_or_report+0xf7/0x130 RSP: 0018:ff1100010dfb7b78 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffffffffa57eee18 RCX: ffffffff97fc9817 RDX: 0000000000040000 RSI: ffa0000002383000 RDI: 0000000000000001 RBP: ffffffffa57eee28 R08: 0000000000000001 R09: ffe21c0021bf6f2c R10: 0000000000000001 R11: 6464615f7473696c R12: ffffffffa5e63100 R13: ffffffffa57eee28 R14: ffffffffa57eee28 R15: ff1100010dfb7d48 FS: 00007fb14398b640(0000) GS:ff11000119600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 000000010d096005 CR4: 0000000000773ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 80000000 Call Trace: <TASK> input_register_handler+0xb3/0x210 mac_hid_start_emulation+0x1c5/0x290 mac_hid_toggle_emumouse+0x20a/0x240 proc_sys_call_handler+0x4c2/0x6e0 new_sync_write+0x1b1/0x2d0 vfs_write+0x709/0x950 ksys_write+0x12a/0x250 do_syscall_64+0x5a/0x110 entry_SYSCALL_64_after_hwframe+0x78/0xe2 The WARNING occurs when two processes concurrently write to the mac-hid emulation sysctl, causing a race condition in mac_hid_toggle_emumouse(). Both processes read old_val=0, then both try to register the input handler, leading to a double list_add of the same handler. CPU0 CPU1 ------------------------- ------------------------- vfs_write() //write 1 vfs_write() //write 1 proc_sys_write() proc_sys_write() mac_hid_toggle_emumouse() mac_hid_toggle_emumouse() old_val = *valp // old_val=0 old_val = *valp // old_val=0 mutex_lock_killable() proc_dointvec() // *valp=1 mac_hid_start_emulation() input_register_handler() mutex_unlock() mutex_lock_killable() proc_dointvec() mac_hid_start_emulation() input_register_handler() //Trigger Warning mutex_unlock() Fix this by moving the old_val read inside the mutex lock region.

What

In the Linux kernel, the following vulnerability has been resolved: macintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse The following warning appears when running syzkaller, and this issue also exists in the mainline code. ------------[ cut here ]------------ list_add double add: new=ffffffffa57eee28, prev=ffffffffa57eee28, next=ffffffffa5e63100. WARNING: CPU: 0 PID: 1491 at lib/list_debug.c:35 __list_add_valid_or_report+0xf7/0x130 Modules linked in: CPU: 0 PID: 1491 Comm: syz.1.28 Not tainted 6.6.0+ #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 RIP: 0010:__list_add_valid_or_report+0xf7/0x130 RSP: 0018:ff1100010dfb7b78 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffffffffa57eee18 RCX: ffffffff97fc9817 RDX: 0000000000040000 RSI: ffa0000002383000 RDI: 0000000000000001 RBP: ffffffffa57eee28 R08: 0000000000000001 R09: ffe21c0021bf6f2c R10: 0000000000000001 R11: 6464615f7473696c R12: ffffffffa5e63100 R13: ffffffffa57eee28 R14: ffffffffa57eee28 R15: ff1100010dfb7d48 FS: 00007fb14398b640(0000) GS:ff11000119600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 000000010d096005 CR4: 0000000000773ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 80000000 Call Trace: <TASK> input_register_handler+0xb3/0x210 mac_hid_start_emulation+0x1c5/0x290 mac_hid_toggle_emumouse+0x20a/0x240 proc_sys_call_handler+0x4c2/0x6e0 new_sync_write+0x1b1/0x2d0 vfs_write+0x709/0x950 ksys_write+0x12a/0x250 do_syscall_64+0x5a/0x110 entry_SYSCALL_64_after_hwframe+0x78/0xe2 The WARNING occurs when two processes concurrently write to the mac-hid emulation sysctl, causing a race condition in mac_hid_toggle_emumouse(). Both processes read old_val=0, then both try to register the input handler, leading to a double list_add of the same handler. CPU0 CPU1 ------------------------- ------------------------- vfs_write() //write 1 vfs_write() //write 1 proc_sys_write() proc_sys_write() mac_hid_toggle_emumouse() mac_hid_toggle_emumouse() old_val = *valp // old_val=0 old_val = *valp // old_val=0 mutex_lock_killable() proc_dointvec() // *valp=1 mac_hid_start_emulation() input_register_handler() mutex_unlock() mutex_lock_killable() proc_dointvec() mac_hid_start_emulation() input_register_handler() //Trigger Warning mutex_unlock() Fix this by moving the old_val read inside the mutex lock region.

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: macintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse The following warning appears when running syzkaller, and this issue also exists in the mainline code. ------------[ cut here ]------------ list_add double add: new=ffffffffa57eee28, prev=ffffffffa57eee28, next=ffffffffa5e63100. WARNING: CPU: 0 PID: 1491 at lib/list_debug.c:35 __list_add_valid_or_report+0xf7/0x130 Modules linked in: CPU: 0 PID: 1491 Comm: syz.1.28 Not tainted 6.6.0+ #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 RIP: 0010:__list_add_valid_or_report+0xf7/0x130 RSP: 0018:ff1100010dfb7b78 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffffffffa57eee18 RCX: ffffffff97fc9817 RDX: 0000000000040000 RSI: ffa0000002383000 RDI: 0000000000000001 RBP: ffffffffa57eee28 R08: 0000000000000001 R09: ffe21c0021bf6f2c R10: 0000000000000001 R11: 6464615f7473696c R12: ffffffffa5e63100 R13: ffffffffa57eee28 R14: ffffffffa57eee28 R15: ff1100010dfb7d48 FS: 00007fb14398b640(0000) GS:ff11000119600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 000000010d096005 CR4: 0000000000773ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 80000000 Call Trace: <TASK> input_register_handler+0xb3/0x210 mac_hid_start_emulation+0x1c5/0x290 mac_hid_toggle_emumouse+0x20a/0x240 proc_sys_call_handler+0x4c2/0x6e0 new_sync_write+0x1b1/0x2d0 vfs_write+0x709/0x950 ksys_write+0x12a/0x250 do_syscall_64+0x5a/0x110 entry_SYSCALL_64_after_hwframe+0x78/0xe2 The WARNING occurs when two processes concurrently write to the mac-hid emulation sysctl, causing a race condition in mac_hid_toggle_emumouse(). Both processes read old_val=0, then both try to register the input handler, leading to a double list_add of the same handler. CPU0 CPU1 ------------------------- ------------------------- vfs_write() //write 1 vfs_write() //write 1 proc_sys_write() proc_sys_write() mac_hid_toggle_emumouse() mac_hid_toggle_emumouse() old_val = *valp // old_val=0 old_val = *valp // old_val=0 mutex_lock_killable() proc_dointvec() // *valp=1 mac_hid_start_emulation() input_register_handler() mutex_unlock() mutex_lock_killable() proc_dointvec() mac_hid_start_emulation() input_register_handler() //Trigger Warning mutex_unlock() Fix this by moving the old_val read inside the mutex lock region.

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.

BSI · German · WID-SEC-2025-2920Linux 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-20251231Security Bulletin 31 Dec 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 31 Dec 2025, published on 31 December 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2025-68349 Référence CVE CVE-2025-68351 https://www.cve.org/CVERecord?id=CVE-2025-68351 Référence CVE CVE-2025-68354 https://www.cve.org/CVERecord?id=CVE-2025-68354 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68364 https://www.cve.org/CVERecord?id=CVE-2025-68364 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68367 https://www.cve.org/CVERecord?id=CVE-2025-68367 Référence CVE CVE-2025-68369 https://www.cve.org/CVERecord?id=CVE-2025-68369 Référence CVE CVE-2025-68371 https://www.cve.org/CVERecord?id=CVE-2025-68371 Référence CVE CVE-2025-68372 https://www.cve.org/CVERecord?id=CVE-2025-68372 Référence CVE CVE-2025-68374 https://www.cve.org/CVERecord?id=CVE-2025-68374 Référence CVE CVE-2025-68378 https://www.cve.org/CVERecord?id=CVE-2025-68378 Référence CVE CVE-2025-68379 https://www.cve.org/CVERecord?id=CVE-2025-68379 Référence CVE CVE-2025-68380 https://www.cve.org/CVERecord?id=CVE-2025-68380 Référence CVE CVE-2025-68724 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68346 Référence CVE CVE-2025-68347 https://www.cve.org/CVERecord?id=CVE-2025-68347 Référence CVE CVE-2025-68349 https://www.cve.org/CVERecord?id=CVE-2025-68349 Référence CVE CVE-2025-68354 https://www.cve.org/CVERecord?id=CVE-2025-68354 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68364 https://www.cve.org/CVERecord?id=CVE-2025-68364 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68367 https://www.cve.org/CVERecord?id=CVE-2025-68367 Référence CVE CVE-2025-68369 https://www.cve.org/CVERecord?id=CVE-2025-68369 Référence CVE CVE-2025-68371 https://www.cve.org/CVERecord?id=CVE-2025-68371 Référence CVE CVE-2025-68372 https://www.cve.org/CVERecord?id=CVE-2025-68372 Référence CVE CVE-2025-68374 https://www.cve.org/CVERecord?id=CVE-2025-68374 Référence CVE CVE-2025-68378 https://www.cve.org/CVERecord?id=CVE-2025-68378 Référence CVE CVE-2025-68379 https://www.cve.org/CVERecord?id=CVE-2025-68379 Référence CVE CVE-2025-68380 https://www.cve.org/CVERecord?id=CVE-2025-68380 Référence CVE CVE-2025-68724 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68346 Référence CVE CVE-2025-68347 https://www.cve.org/CVERecord?id=CVE-2025-68347 Référence CVE CVE-2025-68349 https://www.cve.org/CVERecord?id=CVE-2025-68349 Référence CVE CVE-2025-68354 https://www.cve.org/CVERecord?id=CVE-2025-68354 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68364 https://www.cve.org/CVERecord?id=CVE-2025-68364 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68367 https://www.cve.org/CVERecord?id=CVE-2025-68367 Référence CVE CVE-2025-68369 https://www.cve.org/CVERecord?id=CVE-2025-68369 Référence CVE CVE-2025-68371 https://www.cve.org/CVERecord?id=CVE-2025-68371 Référence CVE CVE-2025-68372 https://www.cve.org/CVERecord?id=CVE-2025-68372 Référence CVE CVE-2025-68374 https://www.cve.org/CVERecord?id=CVE-2025-68374 Référence CVE CVE-2025-68378 https://www.cve.org/CVERecord?id=CVE-2025-68378 Référence CVE CVE-2025-68379 https://www.cve.org/CVERecord?id=CVE-2025-68379 Référence CVE CVE-2025-68380 https://www.cve.org/CVERecord?id=CVE-2025-68380 Référence CVE CVE-2025-68724 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68345 Référence CVE CVE-2025-68346 https://www.cve.org/CVERecord?id=CVE-2025-68346 Référence CVE CVE-2025-68347 https://www.cve.org/CVERecord?id=CVE-2025-68347 Référence CVE CVE-2025-68349 https://www.cve.org/CVERecord?id=CVE-2025-68349 Référence CVE CVE-2025-68354 https://www.cve.org/CVERecord?id=CVE-2025-68354 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68364 https://www.cve.org/CVERecord?id=CVE-2025-68364 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68367 https://www.cve.org/CVERecord?id=CVE-2025-68367 Référence CVE CVE-2025-68369 https://www.cve.org/CVERecord?id=CVE-2025-68369 Référence CVE CVE-2025-68371 https://www.cve.org/CVERecord?id=CVE-2025-68371 Référence CVE CVE-2025-68372 https://www.cve.org/CVERecord?id=CVE-2025-68372 Référence CVE CVE-2025-68374 https://www.cve.org/CVERecord?id=CVE-2025-68374 Référence CVE CVE-2025-68378 https://www.cve.org/CVERecord?id=CVE-2025-68378 Référence CVE CVE-2025-68379 https://www.cve.org/CVERecord?id=CVE-2025-68379 Référence CVE CVE-2025-68380 https://www.cve.org/CVERecord?id=CVE-2025-68380 Référence CVE CVE-2025-68724 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-68349 Référence CVE CVE-2025-68351 https://www.cve.org/CVERecord?id=CVE-2025-68351 Référence CVE CVE-2025-68353 https://www.cve.org/CVERecord?id=CVE-2025-68353 Référence CVE CVE-2025-68354 https://www.cve.org/CVERecord?id=CVE-2025-68354 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68364 https://www.cve.org/CVERecord?id=CVE-2025-68364 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68367 https://www.cve.org/CVERecord?id=CVE-2025-68367 Référence CVE CVE-2025-68368 https://www.cve.org/CVERecord?id=CVE-2025-68368 Référence CVE CVE-2025-68369 https://www.cve.org/CVERecord?id=CVE-2025-68369 Référence CVE CVE-2025-68371 https://www.cve.org/CVERecord?id=CVE-2025-68371 Référence CVE CVE-2025-68372 https://www.cve.org/CVERecord?id=CVE-2025-68372 Référence CVE CVE-2025-68374 https://www.cve.org/CVERecord?id=CVE-2025-68374 Référence CVE CVE-2025-68378 https://www.cve.org/CVERecord?id=CVE-2025-68378 Référence CVE CVE-2025-68379 https://www.cve.org/CVERecord?id=CVE-2025-68379 Référence CVE CVE-2025-68380 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-68349 Référence CVE CVE-2025-68351 https://www.cve.org/CVERecord?id=CVE-2025-68351 Référence CVE CVE-2025-68353 https://www.cve.org/CVERecord?id=CVE-2025-68353 Référence CVE CVE-2025-68354 https://www.cve.org/CVERecord?id=CVE-2025-68354 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68364 https://www.cve.org/CVERecord?id=CVE-2025-68364 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68367 https://www.cve.org/CVERecord?id=CVE-2025-68367 Référence CVE CVE-2025-68368 https://www.cve.org/CVERecord?id=CVE-2025-68368 Référence CVE CVE-2025-68369 https://www.cve.org/CVERecord?id=CVE-2025-68369 Référence CVE CVE-2025-68371 https://www.cve.org/CVERecord?id=CVE-2025-68371 Référence CVE CVE-2025-68372 https://www.cve.org/CVERecord?id=CVE-2025-68372 Référence CVE CVE-2025-68374 https://www.cve.org/CVERecord?id=CVE-2025-68374 Référence CVE CVE-2025-68378 https://www.cve.org/CVERecord?id=CVE-2025-68378 Référence CVE CVE-2025-68379 https://www.cve.org/CVERecord?id=CVE-2025-68379 Référence CVE CVE-2025-68380 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68358 Référence CVE CVE-2025-68359 https://www.cve.org/CVERecord?id=CVE-2025-68359 Référence CVE CVE-2025-68360 https://www.cve.org/CVERecord?id=CVE-2025-68360 Référence CVE CVE-2025-68361 https://www.cve.org/CVERecord?id=CVE-2025-68361 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68364 https://www.cve.org/CVERecord?id=CVE-2025-68364 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68367 https://www.cve.org/CVERecord?id=CVE-2025-68367 Référence CVE CVE-2025-68369 https://www.cve.org/CVERecord?id=CVE-2025-68369 Référence CVE CVE-2025-68370 https://www.cve.org/CVERecord?id=CVE-2025-68370 Référence CVE CVE-2025-68371 https://www.cve.org/CVERecord?id=CVE-2025-68371 Référence CVE CVE-2025-68372 https://www.cve.org/CVERecord?id=CVE-2025-68372 Référence CVE CVE-2025-68373 https://www.cve.org/CVERecord?id=CVE-2025-68373 Référence CVE CVE-2025-68374 https://www.cve.org/CVERecord?id=CVE-2025-68374 Référence CVE CVE-2025-68375 https://www.cve.org/CVERecord?id=CVE-2025-68375 Référence CVE CVE-2025-68376 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68356 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68359 https://www.cve.org/CVERecord?id=CVE-2025-68359 Référence CVE CVE-2025-68360 https://www.cve.org/CVERecord?id=CVE-2025-68360 Référence CVE CVE-2025-68361 https://www.cve.org/CVERecord?id=CVE-2025-68361 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68364 https://www.cve.org/CVERecord?id=CVE-2025-68364 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68367 https://www.cve.org/CVERecord?id=CVE-2025-68367 Référence CVE CVE-2025-68369 https://www.cve.org/CVERecord?id=CVE-2025-68369 Référence CVE CVE-2025-68370 https://www.cve.org/CVERecord?id=CVE-2025-68370 Référence CVE CVE-2025-68371 https://www.cve.org/CVERecord?id=CVE-2025-68371 Référence CVE CVE-2025-68372 https://www.cve.org/CVERecord?id=CVE-2025-68372 Référence CVE CVE-2025-68373 https://www.cve.org/CVERecord?id=CVE-2025-68373 Référence CVE CVE-2025-68374 https://www.cve.org/CVERecord?id=CVE-2025-68374 Référence CVE CVE-2025-68375 https://www.cve.org/CVERecord?id=CVE-2025-68375 Référence CVE CVE-2025-68376 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68356 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68359 https://www.cve.org/CVERecord?id=CVE-2025-68359 Référence CVE CVE-2025-68360 https://www.cve.org/CVERecord?id=CVE-2025-68360 Référence CVE CVE-2025-68361 https://www.cve.org/CVERecord?id=CVE-2025-68361 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68364 https://www.cve.org/CVERecord?id=CVE-2025-68364 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68367 https://www.cve.org/CVERecord?id=CVE-2025-68367 Référence CVE CVE-2025-68369 https://www.cve.org/CVERecord?id=CVE-2025-68369 Référence CVE CVE-2025-68370 https://www.cve.org/CVERecord?id=CVE-2025-68370 Référence CVE CVE-2025-68371 https://www.cve.org/CVERecord?id=CVE-2025-68371 Référence CVE CVE-2025-68372 https://www.cve.org/CVERecord?id=CVE-2025-68372 Référence CVE CVE-2025-68373 https://www.cve.org/CVERecord?id=CVE-2025-68373 Référence CVE CVE-2025-68374 https://www.cve.org/CVERecord?id=CVE-2025-68374 Référence CVE CVE-2025-68375 https://www.cve.org/CVERecord?id=CVE-2025-68375 Référence CVE CVE-2025-68376 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68346 Référence CVE CVE-2025-68347 https://www.cve.org/CVERecord?id=CVE-2025-68347 Référence CVE CVE-2025-68349 https://www.cve.org/CVERecord?id=CVE-2025-68349 Référence CVE CVE-2025-68351 https://www.cve.org/CVERecord?id=CVE-2025-68351 Référence CVE CVE-2025-68354 https://www.cve.org/CVERecord?id=CVE-2025-68354 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68367 https://www.cve.org/CVERecord?id=CVE-2025-68367 Référence CVE CVE-2025-68372 https://www.cve.org/CVERecord?id=CVE-2025-68372 Référence CVE CVE-2025-68374 https://www.cve.org/CVERecord?id=CVE-2025-68374 Référence CVE CVE-2025-68378 https://www.cve.org/CVERecord?id=CVE-2025-68378 Référence CVE CVE-2025-68379 https://www.cve.org/CVERecord?id=CVE-2025-68379 Référence CVE CVE-2025-68380 https://www.cve.org/CVERecord?id=CVE-2025-68380 Référence CVE CVE-2025-68724 https://www.cve.org/CVERecord?id=CVE-2025-68724 Référence CVE CVE-2025-68725 https://www.cve.org/CVERecord?id=CVE-2025-68725 Référence CVE CVE-2025-68727 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68356 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68359 https://www.cve.org/CVERecord?id=CVE-2025-68359 Référence CVE CVE-2025-68360 https://www.cve.org/CVERecord?id=CVE-2025-68360 Référence CVE CVE-2025-68361 https://www.cve.org/CVERecord?id=CVE-2025-68361 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68364 https://www.cve.org/CVERecord?id=CVE-2025-68364 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68367 https://www.cve.org/CVERecord?id=CVE-2025-68367 Référence CVE CVE-2025-68369 https://www.cve.org/CVERecord?id=CVE-2025-68369 Référence CVE CVE-2025-68370 https://www.cve.org/CVERecord?id=CVE-2025-68370 Référence CVE CVE-2025-68371 https://www.cve.org/CVERecord?id=CVE-2025-68371 Référence CVE CVE-2025-68372 https://www.cve.org/CVERecord?id=CVE-2025-68372 Référence CVE CVE-2025-68373 https://www.cve.org/CVERecord?id=CVE-2025-68373 Référence CVE CVE-2025-68374 https://www.cve.org/CVERecord?id=CVE-2025-68374 Référence CVE CVE-2025-68375 https://www.cve.org/CVERecord?id=CVE-2025-68375 Référence CVE CVE-2025-68376 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-68346 Référence CVE CVE-2025-68349 https://www.cve.org/CVERecord?id=CVE-2025-68349 Référence CVE CVE-2025-68354 https://www.cve.org/CVERecord?id=CVE-2025-68354 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68364 https://www.cve.org/CVERecord?id=CVE-2025-68364 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68367 https://www.cve.org/CVERecord?id=CVE-2025-68367 Référence CVE CVE-2025-68371 https://www.cve.org/CVERecord?id=CVE-2025-68371 Référence CVE CVE-2025-68372 https://www.cve.org/CVERecord?id=CVE-2025-68372 Référence CVE CVE-2025-68378 https://www.cve.org/CVERecord?id=CVE-2025-68378 Référence CVE CVE-2025-68379 https://www.cve.org/CVERecord?id=CVE-2025-68379 Référence CVE CVE-2025-68724 https://www.cve.org/CVERecord?id=CVE-2025-68724 Référence CVE CVE-2025-68725 https://www.cve.org/CVERecord?id=CVE-2025-68725 Référence CVE CVE-2025-68727 https://www.cve.org/CVERecord?id=CVE-2025-68727 Référence CVE CVE-2025-68728 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-68346 Référence CVE CVE-2025-68349 https://www.cve.org/CVERecord?id=CVE-2025-68349 Référence CVE CVE-2025-68354 https://www.cve.org/CVERecord?id=CVE-2025-68354 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68364 https://www.cve.org/CVERecord?id=CVE-2025-68364 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68367 https://www.cve.org/CVERecord?id=CVE-2025-68367 Référence CVE CVE-2025-68371 https://www.cve.org/CVERecord?id=CVE-2025-68371 Référence CVE CVE-2025-68372 https://www.cve.org/CVERecord?id=CVE-2025-68372 Référence CVE CVE-2025-68378 https://www.cve.org/CVERecord?id=CVE-2025-68378 Référence CVE CVE-2025-68379 https://www.cve.org/CVERecord?id=CVE-2025-68379 Référence CVE CVE-2025-68724 https://www.cve.org/CVERecord?id=CVE-2025-68724 Référence CVE CVE-2025-68725 https://www.cve.org/CVERecord?id=CVE-2025-68725 Référence CVE CVE-2025-68727 https://www.cve.org/CVERecord?id=CVE-2025-68727 Référence CVE CVE-2025-68728 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-68354 Référence CVE CVE-2025-68356 https://www.cve.org/CVERecord?id=CVE-2025-68356 Référence CVE CVE-2025-68359 https://www.cve.org/CVERecord?id=CVE-2025-68359 Référence CVE CVE-2025-68360 https://www.cve.org/CVERecord?id=CVE-2025-68360 Référence CVE CVE-2025-68361 https://www.cve.org/CVERecord?id=CVE-2025-68361 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68367 https://www.cve.org/CVERecord?id=CVE-2025-68367 Référence CVE CVE-2025-68368 https://www.cve.org/CVERecord?id=CVE-2025-68368 Référence CVE CVE-2025-68372 https://www.cve.org/CVERecord?id=CVE-2025-68372 Référence CVE CVE-2025-68374 https://www.cve.org/CVERecord?id=CVE-2025-68374 Référence CVE CVE-2025-68376 https://www.cve.org/CVERecord?id=CVE-2025-68376 Référence CVE CVE-2025-68378 https://www.cve.org/CVERecord?id=CVE-2025-68378 Référence CVE CVE-2025-68379 https://www.cve.org/CVERecord?id=CVE-2025-68379 Référence CVE CVE-2025-68380 https://www.cve.org/CVERecord?id=CVE-2025-68380 Référence CVE CVE-2025-68724 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68346 Référence CVE CVE-2025-68347 https://www.cve.org/CVERecord?id=CVE-2025-68347 Référence CVE CVE-2025-68349 https://www.cve.org/CVERecord?id=CVE-2025-68349 Référence CVE CVE-2025-68351 https://www.cve.org/CVERecord?id=CVE-2025-68351 Référence CVE CVE-2025-68354 https://www.cve.org/CVERecord?id=CVE-2025-68354 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68367 https://www.cve.org/CVERecord?id=CVE-2025-68367 Référence CVE CVE-2025-68372 https://www.cve.org/CVERecord?id=CVE-2025-68372 Référence CVE CVE-2025-68378 https://www.cve.org/CVERecord?id=CVE-2025-68378 Référence CVE CVE-2025-68379 https://www.cve.org/CVERecord?id=CVE-2025-68379 Référence CVE CVE-2025-68380 https://www.cve.org/CVERecord?id=CVE-2025-68380 Référence CVE CVE-2025-68724 https://www.cve.org/CVERecord?id=CVE-2025-68724 Référence CVE CVE-2025-68725 https://www.cve.org/CVERecord?id=CVE-2025-68725 Référence CVE CVE-2025-68727 https://www.cve.org/CVERecord?id=CVE-2025-68727 Référence CVE CVE-2025-68728 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68325 Référence CVE CVE-2025-68327 https://www.cve.org/CVERecord?id=CVE-2025-68327 Référence CVE CVE-2025-68337 https://www.cve.org/CVERecord?id=CVE-2025-68337 Référence CVE CVE-2025-68349 https://www.cve.org/CVERecord?id=CVE-2025-68349 Référence CVE CVE-2025-68354 https://www.cve.org/CVERecord?id=CVE-2025-68354 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68367 https://www.cve.org/CVERecord?id=CVE-2025-68367 Référence CVE CVE-2025-68372 https://www.cve.org/CVERecord?id=CVE-2025-68372 Référence CVE CVE-2025-68379 https://www.cve.org/CVERecord?id=CVE-2025-68379 Référence CVE CVE-2025-68725 https://www.cve.org/CVERecord?id=CVE-2025-68725 Référence CVE CVE-2025-68727 https://www.cve.org/CVERecord?id=CVE-2025-68727 Référence CVE CVE-2025-68728 https://www.cve.org/CVERecord?id=CVE-2025-68728 Référence CVE CVE-2025-68732 https://www.cve.org/CVERecord?id=CVE-2025-68732 Référence CVE CVE-2025-68733 https://www.cve.org/CVERecord?id=CVE-2025-68733 Référence CVE CVE-2025-68740 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-68346 Référence CVE CVE-2025-68347 https://www.cve.org/CVERecord?id=CVE-2025-68347 Référence CVE CVE-2025-68349 https://www.cve.org/CVERecord?id=CVE-2025-68349 Référence CVE CVE-2025-68354 https://www.cve.org/CVERecord?id=CVE-2025-68354 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68364 https://www.cve.org/CVERecord?id=CVE-2025-68364 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68367 https://www.cve.org/CVERecord?id=CVE-2025-68367 Référence CVE CVE-2025-68369 https://www.cve.org/CVERecord?id=CVE-2025-68369 Référence CVE CVE-2025-68371 https://www.cve.org/CVERecord?id=CVE-2025-68371 Référence CVE CVE-2025-68372 https://www.cve.org/CVERecord?id=CVE-2025-68372 Référence CVE CVE-2025-68380 https://www.cve.org/CVERecord?id=CVE-2025-68380 Référence CVE CVE-2025-68724 https://www.cve.org/CVERecord?id=CVE-2025-68724 Référence CVE CVE-2025-68725 https://www.cve.org/CVERecord?id=CVE-2025-68725 Référence CVE CVE-2025-68727 https://www.cve.org/CVERecord?id=CVE-2025-68727 Référence CVE CVE-2025-68728 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-68351 Référence CVE CVE-2025-68354 https://www.cve.org/CVERecord?id=CVE-2025-68354 Référence CVE CVE-2025-68357 https://www.cve.org/CVERecord?id=CVE-2025-68357 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=CVE-2025-68362 Référence CVE CVE-2025-68363 https://www.cve.org/CVERecord?id=CVE-2025-68363 Référence CVE CVE-2025-68364 https://www.cve.org/CVERecord?id=CVE-2025-68364 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68367 https://www.cve.org/CVERecord?id=CVE-2025-68367 Référence CVE CVE-2025-68369 https://www.cve.org/CVERecord?id=CVE-2025-68369 Référence CVE CVE-2025-68371 https://www.cve.org/CVERecord?id=CVE-2025-68371 Référence CVE CVE-2025-68372 https://www.cve.org/CVERecord?id=CVE-2025-68372 Référence CVE CVE-2025-68380 https://www.cve.org/CVERecord?id=CVE-2025-68380 Référence CVE CVE-2025-68724 https://www.cve.org/CVERecord?id=CVE-2025-68724 Référence CVE CVE-2025-68725 https://www.cve.org/CVERecord?id=CVE-2025-68725 Référence CVE CVE-2025-68727 https://www.cve.org/CVERecord?id=CVE-2025-68727 Référence CVE CVE-2025-68728 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: < 2.6.34, 5.10.248 ≤ 5.10.*, 5.15.198 ≤ 5.15.*, 6.1.160 ≤ 6.1.*, 6.6.120 ≤ 6.6.*, 6.12.63 ≤ 6.12.*, 6.17.13 ≤ 6.17.*, 6.18.2 ≤ 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 24 Dec 2025 · Last source change 11 May 2026, 21:51 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-2025-205087
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
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
    kernel-default as component of SLES-LTSS-TERADATA 15 SP2; kernel-source as component of SLES-LTSS-TERADATA 15 SP2; kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6; cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP3; ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP6; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP6; kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP2; 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; and 410 more
    After
    kernel-default as component of SLES-LTSS-TERADATA 15 SP2; kernel-source as component of SLES-LTSS-TERADATA 15 SP2; kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP6; kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6; cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP3; ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3; kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP6; kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP6; kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP2; kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP2; 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; and 407 more
    SUSE Product Security Team ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    99b089c3c38a83ebaeb1cc4584ddcde841626467 < d5f1d40fd342b589420de7508b4c748fcf28122e; 99b089c3c38a83ebaeb1cc4584ddcde841626467 < 14c209835e47a87e6da94bb9401e570dcc14f31f; 99b089c3c38a83ebaeb1cc4584ddcde841626467 < 583d36523f56d8e9ddfa0bec20743a6faefc9b74; 99b089c3c38a83ebaeb1cc4584ddcde841626467 < 61abf8c3162d155b4fd0fb251f08557093363a0a; 99b089c3c38a83ebaeb1cc4584ddcde841626467 < 230621ffdb361d15cd3ef92d8b4fa8d314f4fad4; 99b089c3c38a83ebaeb1cc4584ddcde841626467 < 388391dd1cc567fcf0b372b63d414c119d23e911; 99b089c3c38a83ebaeb1cc4584ddcde841626467 < 48a7d427eb65922b3f17fbe00e2bbc7cb9eac381; 99b089c3c38a83ebaeb1cc4584ddcde841626467 < 1e4b207ffe54cf33a4b7a2912c4110f89c73bf3f · Fixed: < 2.6.34; 5.10.248 ≤ 5.10.*; 5.15.198 ≤ 5.15.*; 6.1.160 ≤ 6.1.*; 6.6.120 ≤ 6.6.*; 6.12.63 ≤ 6.12.*; 6.17.13 ≤ 6.17.*; 6.18.2 ≤ 6.18.*
    After
    Linux: 99b089c3c38a83ebaeb1cc4584ddcde841626467 < d5f1d40fd342b589420de7508b4c748fcf28122e, 99b089c3c38a83ebaeb1cc4584ddcde841626467 < 14c209835e47a87e6da94bb9401e570dcc14f31f, 99b089c3c38a83ebaeb1cc4584ddcde841626467 < 583d36523f56d8e9ddfa0bec20743a6faefc9b74, 99b089c3c38a83ebaeb1cc4584ddcde841626467 < 61abf8c3162d155b4fd0fb251f08557093363a0a, 99b089c3c38a83ebaeb1cc4584ddcde841626467 < 230621ffdb361d15cd3ef92d8b4fa8d314f4fad4, 99b089c3c38a83ebaeb1cc4584ddcde841626467 < 388391dd1cc567fcf0b372b63d414c119d23e911, 99b089c3c38a83ebaeb1cc4584ddcde841626467 < 48a7d427eb65922b3f17fbe00e2bbc7cb9eac381, 99b089c3c38a83ebaeb1cc4584ddcde841626467 < 1e4b207ffe54cf33a4b7a2912c4110f89c73bf3f, 2.6.34 · Fixed: Linux: < 2.6.34, 5.10.248 ≤ 5.10.*, 5.15.198 ≤ 5.15.*, 6.1.160 ≤ 6.1.*, 6.6.120 ≤ 6.6.*, 6.12.63 ≤ 6.12.*, 6.17.13 ≤ 6.17.*, 6.18.2 ≤ 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-2025-205087↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-68367 · cve.blacktree.nl