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

hwpoison, memory_hotplug: lock folio before unmap hwpoisoned folio

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 21 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 23 May 2026

Evidence used

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

Compensating controls

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

Verification

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

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 21 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

25 package states
Package result overrides the generic status

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

Repository candidate not checked

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

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.19-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.140-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.19-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.19-1Debian Security Tracker ↗Source updated 6 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-intelAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 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-21931 · CSAF 2.0 · revision 44 · interimSUSE Product Security TeamCVE-2025-21931
352 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-extra as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
Summary
In the Linux kernel, the following vulnerability has been resolved: hwpoison, memory_hotplug: lock folio before unmap hwpoisoned folio Commit b15c87263a69 ("hwpoison, memory_hotplug: allow hwpoisoned pages to be offlined) add page poison checks in do_migrate_range in order to make offline hwpoisoned page possible by introducing isolate_lru_page and try_to_unmap for hwpoisoned page. However folio lock must be held before calling try_to_unmap. Add it to fix this problem. Warning will be produced if folio is not locked during unmap: ------------[ cut here ]------------ kernel BUG at ./include/linux/swapops.h:400! Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP Modules linked in: CPU: 4 UID: 0 PID: 411 Comm: bash Tainted: G W 6.13.0-rc1-00016-g3c434c7ee82a-dirty #41 Tainted: [W]=WARN Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015 pstate: 40400005 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : try_to_unmap_one+0xb08/0xd3c lr : try_to_unmap_one+0x3dc/0xd3c Call trace: try_to_unmap_one+0xb08/0xd3c (P) try_to_unmap_one+0x3dc/0xd3c (L) rmap_walk_anon+0xdc/0x1f8 rmap_walk+0x3c/0x58 try_to_unmap+0x88/0x90 unmap_poisoned_folio+0x30/0xa8 do_migrate_range+0x4a0/0x568 offline_pages+0x5a4/0x670 memory_block_action+0x17c/0x374 memory_subsys_offline+0x3c/0x78 device_offline+0xa4/0xd0 state_store+0x8c/0xf0 dev_attr_store+0x18/0x2c sysfs_kf_write+0x44/0x54 kernfs_fop_write_iter+0x118/0x1a8 vfs_write+0x3a8/0x4bc ksys_write+0x6c/0xf8 __arm64_sys_write+0x1c/0x28 invoke_syscall+0x44/0x100 el0_svc_common.constprop.0+0x40/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x30/0xd0 el0t_64_sync_handler+0xc8/0xcc el0t_64_sync+0x198/0x19c Code: f9407be0 b5fff320 d4210000 17ffff97 (d4210000) ---[ end trace 0000000000000000 ]---
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-9390

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 21 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: hwpoison, memory_hotplug: lock folio before unmap hwpoisoned folio Commit b15c87263a69 ("hwpoison, memory_hotplug: allow hwpoisoned pages to be offlined) add page poison checks in do_migrate_range in order to make offline hwpoisoned page possible by introducing isolate_lru_page and try_to_unmap for hwpoisoned page. However folio lock must be held before calling try_to_unmap. Add it to fix this problem. Warning will be produced if folio is not locked during unmap: ------------[ cut here ]------------ kernel BUG at ./include/linux/swapops.h:400! Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP Modules linked in: CPU: 4 UID: 0 PID: 411 Comm: bash Tainted: G W 6.13.0-rc1-00016-g3c434c7ee82a-dirty #41 Tainted: [W]=WARN Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015 pstate: 40400005 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : try_to_unmap_one+0xb08/0xd3c lr : try_to_unmap_one+0x3dc/0xd3c Call trace: try_to_unmap_one+0xb08/0xd3c (P) try_to_unmap_one+0x3dc/0xd3c (L) rmap_walk_anon+0xdc/0x1f8 rmap_walk+0x3c/0x58 try_to_unmap+0x88/0x90 unmap_poisoned_folio+0x30/0xa8 do_migrate_range+0x4a0/0x568 offline_pages+0x5a4/0x670 memory_block_action+0x17c/0x374 memory_subsys_offline+0x3c/0x78 device_offline+0xa4/0xd0 state_store+0x8c/0xf0 dev_attr_store+0x18/0x2c sysfs_kf_write+0x44/0x54 kernfs_fop_write_iter+0x118/0x1a8 vfs_write+0x3a8/0x4bc ksys_write+0x6c/0xf8 __arm64_sys_write+0x1c/0x28 invoke_syscall+0x44/0x100 el0_svc_common.constprop.0+0x40/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x30/0xd0 el0t_64_sync_handler+0xc8/0xcc el0t_64_sync+0x198/0x19c Code: f9407be0 b5fff320 d4210000 17ffff97 (d4210000) ---[ end trace 0000000000000000 ]---

What

In the Linux kernel, the following vulnerability has been resolved: hwpoison, memory_hotplug: lock folio before unmap hwpoisoned folio Commit b15c87263a69 ("hwpoison, memory_hotplug: allow hwpoisoned pages to be offlined) add page poison checks in do_migrate_range in order to make offline hwpoisoned page possible by introducing isolate_lru_page and try_to_unmap for hwpoisoned page. However folio lock must be held before calling try_to_unmap. Add it to fix this problem. Warning will be produced if folio is not locked during unmap: ------------[ cut here ]------------ kernel BUG at ./include/linux/swapops.h:400! Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP Modules linked in: CPU: 4 UID: 0 PID: 411 Comm: bash Tainted: G W 6.13.0-rc1-00016-g3c434c7ee82a-dirty #41 Tainted: [W]=WARN Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015 pstate: 40400005 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : try_to_unmap_one+0xb08/0xd3c lr : try_to_unmap_one+0x3dc/0xd3c Call trace: try_to_unmap_one+0xb08/0xd3c (P) try_to_unmap_one+0x3dc/0xd3c (L) rmap_walk_anon+0xdc/0x1f8 rmap_walk+0x3c/0x58 try_to_unmap+0x88/0x90 unmap_poisoned_folio+0x30/0xa8 do_migrate_range+0x4a0/0x568 offline_pages+0x5a4/0x670 memory_block_action+0x17c/0x374 memory_subsys_offline+0x3c/0x78 device_offline+0xa4/0xd0 state_store+0x8c/0xf0 dev_attr_store+0x18/0x2c sysfs_kf_write+0x44/0x54 kernfs_fop_write_iter+0x118/0x1a8 vfs_write+0x3a8/0x4bc ksys_write+0x6c/0xf8 __arm64_sys_write+0x1c/0x28 invoke_syscall+0x44/0x100 el0_svc_common.constprop.0+0x40/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x30/0xd0 el0t_64_sync_handler+0xc8/0xcc el0t_64_sync+0x198/0x19c Code: f9407be0 b5fff320 d4210000 17ffff97 (d4210000) ---[ end trace 0000000000000000 ]---

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

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: hwpoison, memory_hotplug: lock folio before unmap hwpoisoned folio Commit b15c87263a69 ("hwpoison, memory_hotplug: allow hwpoisoned pages to be offlined) add page poison checks in do_migrate_range in order to make offline hwpoisoned page possible by introducing isolate_lru_page and try_to_unmap for hwpoisoned page. However folio lock must be held before calling try_to_unmap. Add it to fix this problem. Warning will be produced if folio is not locked during unmap: ------------[ cut here ]------------ kernel BUG at ./include/linux/swapops.h:400! Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP Modules linked in: CPU: 4 UID: 0 PID: 411 Comm: bash Tainted: G W 6.13.0-rc1-00016-g3c434c7ee82a-dirty #41 Tainted: [W]=WARN Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015 pstate: 40400005 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : try_to_unmap_one+0xb08/0xd3c lr : try_to_unmap_one+0x3dc/0xd3c Call trace: try_to_unmap_one+0xb08/0xd3c (P) try_to_unmap_one+0x3dc/0xd3c (L) rmap_walk_anon+0xdc/0x1f8 rmap_walk+0x3c/0x58 try_to_unmap+0x88/0x90 unmap_poisoned_folio+0x30/0xa8 do_migrate_range+0x4a0/0x568 offline_pages+0x5a4/0x670 memory_block_action+0x17c/0x374 memory_subsys_offline+0x3c/0x78 device_offline+0xa4/0xd0 state_store+0x8c/0xf0 dev_attr_store+0x18/0x2c sysfs_kf_write+0x44/0x54 kernfs_fop_write_iter+0x118/0x1a8 vfs_write+0x3a8/0x4bc ksys_write+0x6c/0xf8 __arm64_sys_write+0x1c/0x28 invoke_syscall+0x44/0x100 el0_svc_common.constprop.0+0x40/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x30/0xd0 el0t_64_sync_handler+0xc8/0xcc el0t_64_sync+0x198/0x19c Code: f9407be0 b5fff320 d4210000 17ffff97 (d4210000) ---[ end trace 0000000000000000 ]---

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

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 → Improper Locking → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-667 ↗

CWE-667: Improper Locking. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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

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

Official authority intelligence

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

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

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial-of-Service auszulösen und um nicht näher spezifizierte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250402Security Bulletin 02 Apr 2025 [1.46 MB]

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 02 Apr 2025 [1.46 MB], published on 2 April 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2025-21881 Référence CVE CVE-2025-21885 https://www.cve.org/CVERecord?id=CVE-2025-21885 Référence CVE CVE-2025-21891 https://www.cve.org/CVERecord?id=CVE-2025-21891 Référence CVE CVE-2025-21894 https://www.cve.org/CVERecord?id=CVE-2025-21894 Référence CVE CVE-2025-21899 https://www.cve.org/CVERecord?id=CVE-2025-21899 Référence CVE CVE-2025-21908 https://www.cve.org/CVERecord?id=CVE-2025-21908 Référence CVE CVE-2025-21915 https://www.cve.org/CVERecord?id=CVE-2025-21915 Référence CVE CVE-2025-21918 https://www.cve.org/CVERecord?id=CVE-2025-21918 Référence CVE CVE-2025-21927 https://www.cve.org/CVERecord?id=CVE-2025-21927 Référence CVE CVE-2025-21931 https://www.cve.org/CVERecord?id=CVE-2025-21931 Référence CVE CVE-2025-21944 https://www.cve.org/CVERecord?id=CVE-2025-21944 Référence CVE CVE-2025-21945 https://www.cve.org/CVERecord?id=CVE-2025-21945 Référence CVE CVE-2025-21946 https://www.cve.org/CVERecord?id=CVE-2025-21946 Référence CVE CVE-2025-21947 https://www.cve.org/CVERecord?id=CVE-2025-21947 Référence CVE CVE-2025-21955 https://www.cve.org/CVERecord?id=CVE-2025-21955 Référence CVE CVE-2025-21967 https://www.cve.org/CVERecord?id=CVE-2025-21967 Référence CVE CVE-2025-21972 https://www.cve.org/CVERecord?id=CVE-2025-21972 Référence CVE CVE-2025-21976 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-21881 Référence CVE CVE-2025-21885 https://www.cve.org/CVERecord?id=CVE-2025-21885 Référence CVE CVE-2025-21891 https://www.cve.org/CVERecord?id=CVE-2025-21891 Référence CVE CVE-2025-21894 https://www.cve.org/CVERecord?id=CVE-2025-21894 Référence CVE CVE-2025-21899 https://www.cve.org/CVERecord?id=CVE-2025-21899 Référence CVE CVE-2025-21908 https://www.cve.org/CVERecord?id=CVE-2025-21908 Référence CVE CVE-2025-21915 https://www.cve.org/CVERecord?id=CVE-2025-21915 Référence CVE CVE-2025-21918 https://www.cve.org/CVERecord?id=CVE-2025-21918 Référence CVE CVE-2025-21927 https://www.cve.org/CVERecord?id=CVE-2025-21927 Référence CVE CVE-2025-21931 https://www.cve.org/CVERecord?id=CVE-2025-21931 Référence CVE CVE-2025-21944 https://www.cve.org/CVERecord?id=CVE-2025-21944 Référence CVE CVE-2025-21945 https://www.cve.org/CVERecord?id=CVE-2025-21945 Référence CVE CVE-2025-21946 https://www.cve.org/CVERecord?id=CVE-2025-21946 Référence CVE CVE-2025-21947 https://www.cve.org/CVERecord?id=CVE-2025-21947 Référence CVE CVE-2025-21955 https://www.cve.org/CVERecord?id=CVE-2025-21955 Référence CVE CVE-2025-21967 https://www.cve.org/CVERecord?id=CVE-2025-21967 Référence CVE CVE-2025-21972 https://www.cve.org/CVERecord?id=CVE-2025-21972 Référence CVE CVE-2025-21976 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47659 Référence CVE CVE-2024-49927 https://www.cve.org/CVERecord?id=CVE-2024-49927 Référence CVE CVE-2024-50047 https://www.cve.org/CVERecord?id=CVE-2024-50047 Référence CVE CVE-2024-56548 https://www.cve.org/CVERecord?id=CVE-2024-56548 Référence CVE CVE-2024-56593 https://www.cve.org/CVERecord?id=CVE-2024-56593 Référence CVE CVE-2025-21704 https://www.cve.org/CVERecord?id=CVE-2025-21704 Référence CVE CVE-2025-21726 https://www.cve.org/CVERecord?id=CVE-2025-21726 Référence CVE CVE-2025-21780 https://www.cve.org/CVERecord?id=CVE-2025-21780 Référence CVE CVE-2025-21884 https://www.cve.org/CVERecord?id=CVE-2025-21884 Référence CVE CVE-2025-21931 https://www.cve.org/CVERecord?id=CVE-2025-21931 Référence CVE CVE-2025-22026 https://www.cve.org/CVERecord?id=CVE-2025-22026 Référence CVE CVE-2025-22036 https://www.cve.org/CVERecord?id=CVE-2025-22036 Référence CVE CVE-2025-22037 https://www.cve.org/CVERecord?id=CVE-2025-22037 Référence CVE CVE-2025-22101 https://www.cve.org/CVERecord?id=CVE-2025-22101 Référence CVE CVE-2025-22102 https://www.cve.org/CVERecord?id=CVE-2025-22102 Référence CVE CVE-2025-22115 https://www.cve.org/CVERecord?id=CVE-2025-22115 Référence CVE CVE-2025-22120 https://www.cve.org/CVERecord?id=CVE-2025-22120 Référence CVE CVE-2025-22126 https://www.cve.org/CVERecord?id=

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

/notices/USN-8059-6 Référence CVE CVE-2022-49267 https://www.cve.org/CVERecord?id=CVE-2022-49267 Référence CVE CVE-2024-36331 https://www.cve.org/CVERecord?id=CVE-2024-36331 Référence CVE CVE-2024-36350 https://www.cve.org/CVERecord?id=CVE-2024-36350 Référence CVE CVE-2024-36357 https://www.cve.org/CVERecord?id=CVE-2024-36357 Référence CVE CVE-2024-50299 https://www.cve.org/CVERecord?id=CVE-2024-50299 Référence CVE CVE-2024-53217 https://www.cve.org/CVERecord?id=CVE-2024-53217 Référence CVE CVE-2025-21780 https://www.cve.org/CVERecord?id=CVE-2025-21780 Référence CVE CVE-2025-21884 https://www.cve.org/CVERecord?id=CVE-2025-21884 Référence CVE CVE-2025-21931 https://www.cve.org/CVERecord?id=CVE-2025-21931 Référence CVE CVE-2025-22026 https://www.cve.org/CVERecord?id=CVE-2025-22026 Référence CVE CVE-2025-22037 https://www.cve.org/CVERecord?id=CVE-2025-22037 Référence CVE CVE-2025-22101 https://www.cve.org/CVERecord?id=CVE-2025-22101 Référence CVE CVE-2025-22102 https://www.cve.org/CVERecord?id=CVE-2025-22102 Référence CVE CVE-2025-22115 https://www.cve.org/CVERecord?id=CVE-2025-22115 Référence CVE CVE-2025-22120 https://www.cve.org/CVERecord?id=CVE-2025-22120 Référence CVE CVE-2025-22126 https://www.cve.org/CVERecord?id=CVE-2025-22126 Référence CVE CVE-2025-22128 https://www.cve.org/CVERecord?id=

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

ecord?id=CVE-2025-15366 Référence CVE CVE-2025-15367 https://www.cve.org/CVERecord?id=CVE-2025-15367 Référence CVE CVE-2025-15467 https://www.cve.org/CVERecord?id=CVE-2025-15467 Référence CVE CVE-2025-1632 https://www.cve.org/CVERecord?id=CVE-2025-1632 Référence CVE CVE-2025-1795 https://www.cve.org/CVERecord?id=CVE-2025-1795 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-21883 https://www.cve.org/CVERecord?id=CVE-2025-21883 Référence CVE CVE-2025-21884 https://www.cve.org/CVERecord?id=CVE-2025-21884 Référence CVE CVE-2025-21919 https://www.cve.org/CVERecord?id=CVE-2025-21919 Référence CVE CVE-2025-21931 https://www.cve.org/CVERecord?id=CVE-2025-21931 Référence CVE CVE-2025-22013 https://www.cve.org/CVERecord?id=CVE-2025-22013 Référence CVE CVE-2025-22026 https://www.cve.org/CVERecord?id=CVE-2025-22026 Référence CVE CVE-2025-22058 https://www.cve.org/CVERecord?id=CVE-2025-22058 Référence CVE CVE-2025-22101 https://www.cve.org/CVERecord?id=CVE-2025-22101 Référence CVE CVE-2025-22102 https://www.cve.org/CVERecord?id=CVE-2025-22102 Référence CVE CVE-2025-22104 https://www.cve.org/CVERecord?id=CVE-2025-22104 Référence CVE CVE-2025-22115 https://www.cve.org/CVERecord?id=CVE-2025-22115 Référence CVE CVE-2025-22120 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-36331 Référence CVE CVE-2024-36350 https://www.cve.org/CVERecord?id=CVE-2024-36350 Référence CVE CVE-2024-36357 https://www.cve.org/CVERecord?id=CVE-2024-36357 Référence CVE CVE-2024-53114 https://www.cve.org/CVERecord?id=CVE-2024-53114 Référence CVE CVE-2024-56538 https://www.cve.org/CVERecord?id=CVE-2024-56538 Référence CVE CVE-2024-58011 https://www.cve.org/CVERecord?id=CVE-2024-58011 Référence CVE CVE-2025-21726 https://www.cve.org/CVERecord?id=CVE-2025-21726 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-21884 https://www.cve.org/CVERecord?id=CVE-2025-21884 Référence CVE CVE-2025-21931 https://www.cve.org/CVERecord?id=CVE-2025-21931 Référence CVE CVE-2025-22026 https://www.cve.org/CVERecord?id=CVE-2025-22026 Référence CVE CVE-2025-22058 https://www.cve.org/CVERecord?id=CVE-2025-22058 Référence CVE CVE-2025-22101 https://www.cve.org/CVERecord?id=CVE-2025-22101 Référence CVE CVE-2025-22102 https://www.cve.org/CVERecord?id=CVE-2025-22102 Référence CVE CVE-2025-22115 https://www.cve.org/CVERecord?id=CVE-2025-22115 Référence CVE CVE-2025-22120 https://www.cve.org/CVERecord?id=CVE-2025-22120 Référence CVE CVE-2025-22126 https://www.cve.org/CVERecord?id=CVE-2025-22126 Référence CVE CVE-2025-22128 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-50195 Référence CVE CVE-2024-53114 https://www.cve.org/CVERecord?id=CVE-2024-53114 Référence CVE CVE-2024-56538 https://www.cve.org/CVERecord?id=CVE-2024-56538 Référence CVE CVE-2024-56606 https://www.cve.org/CVERecord?id=CVE-2024-56606 Référence CVE CVE-2024-56756 https://www.cve.org/CVERecord?id=CVE-2024-56756 Référence CVE CVE-2024-58011 https://www.cve.org/CVERecord?id=CVE-2024-58011 Référence CVE CVE-2025-21726 https://www.cve.org/CVERecord?id=CVE-2025-21726 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-21884 https://www.cve.org/CVERecord?id=CVE-2025-21884 Référence CVE CVE-2025-21931 https://www.cve.org/CVERecord?id=CVE-2025-21931 Référence CVE CVE-2025-22026 https://www.cve.org/CVERecord?id=CVE-2025-22026 Référence CVE CVE-2025-22058 https://www.cve.org/CVERecord?id=CVE-2025-22058 Référence CVE CVE-2025-22101 https://www.cve.org/CVERecord?id=CVE-2025-22101 Référence CVE CVE-2025-22102 https://www.cve.org/CVERecord?id=CVE-2025-22102 Référence CVE CVE-2025-22115 https://www.cve.org/CVERecord?id=CVE-2025-22115 Référence CVE CVE-2025-22120 https://www.cve.org/CVERecord?id=CVE-2025-22120 Référence CVE CVE-2025-22126 https://www.cve.org/CVERecord?id=CVE-2025-22126 Référence CVE CVE-2025-22128 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-36903 Référence CVE CVE-2024-36927 https://www.cve.org/CVERecord?id=CVE-2024-36927 Référence CVE CVE-2024-43840 https://www.cve.org/CVERecord?id=CVE-2024-43840 Référence CVE CVE-2024-46751 https://www.cve.org/CVERecord?id=CVE-2024-46751 Référence CVE CVE-2024-53203 https://www.cve.org/CVERecord?id=CVE-2024-53203 Référence CVE CVE-2024-53209 https://www.cve.org/CVERecord?id=CVE-2024-53209 Référence CVE CVE-2024-57945 https://www.cve.org/CVERecord?id=CVE-2024-57945 Référence CVE CVE-2025-21645 https://www.cve.org/CVERecord?id=CVE-2025-21645 Référence CVE CVE-2025-21839 https://www.cve.org/CVERecord?id=CVE-2025-21839 Référence CVE CVE-2025-21931 https://www.cve.org/CVERecord?id=CVE-2025-21931 Référence CVE CVE-2025-22062 https://www.cve.org/CVERecord?id=CVE-2025-22062 Référence CVE CVE-2025-37819 https://www.cve.org/CVERecord?id=CVE-2025-37819 Référence CVE CVE-2025-37890 https://www.cve.org/CVERecord?id=CVE-2025-37890 Référence CVE CVE-2025-37897 https://www.cve.org/CVERecord?id=CVE-2025-37897 Référence CVE CVE-2025-37901 https://www.cve.org/CVERecord?id=CVE-2025-37901 Référence CVE CVE-2025-37903 https://www.cve.org/CVERecord?id=CVE-2025-37903 Référence CVE CVE-2025-37905 https://www.cve.org/CVERecord?id=CVE-2025-37905 Référence CVE CVE-2025-37909 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21922 Référence CVE CVE-2025-21923 https://www.cve.org/CVERecord?id=CVE-2025-21923 Référence CVE CVE-2025-21924 https://www.cve.org/CVERecord?id=CVE-2025-21924 Référence CVE CVE-2025-21925 https://www.cve.org/CVERecord?id=CVE-2025-21925 Référence CVE CVE-2025-21926 https://www.cve.org/CVERecord?id=CVE-2025-21926 Référence CVE CVE-2025-21927 https://www.cve.org/CVERecord?id=CVE-2025-21927 Référence CVE CVE-2025-21928 https://www.cve.org/CVERecord?id=CVE-2025-21928 Référence CVE CVE-2025-21929 https://www.cve.org/CVERecord?id=CVE-2025-21929 Référence CVE CVE-2025-21930 https://www.cve.org/CVERecord?id=CVE-2025-21930 Référence CVE CVE-2025-21931 https://www.cve.org/CVERecord?id=CVE-2025-21931 Référence CVE CVE-2025-21934 https://www.cve.org/CVERecord?id=CVE-2025-21934 Référence CVE CVE-2025-21935 https://www.cve.org/CVERecord?id=CVE-2025-21935 Référence CVE CVE-2025-21936 https://www.cve.org/CVERecord?id=CVE-2025-21936 Référence CVE CVE-2025-21937 https://www.cve.org/CVERecord?id=CVE-2025-21937 Référence CVE CVE-2025-21938 https://www.cve.org/CVERecord?id=CVE-2025-21938 Référence CVE CVE-2025-21941 https://www.cve.org/CVERecord?id=CVE-2025-21941 Référence CVE CVE-2025-21943 https://www.cve.org/CVERecord?id=CVE-2025-21943 Référence CVE CVE-2025-21948 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21919 Référence CVE CVE-2025-21922 https://www.cve.org/CVERecord?id=CVE-2025-21922 Référence CVE CVE-2025-21923 https://www.cve.org/CVERecord?id=CVE-2025-21923 Référence CVE CVE-2025-21924 https://www.cve.org/CVERecord?id=CVE-2025-21924 Référence CVE CVE-2025-21925 https://www.cve.org/CVERecord?id=CVE-2025-21925 Référence CVE CVE-2025-21926 https://www.cve.org/CVERecord?id=CVE-2025-21926 Référence CVE CVE-2025-21927 https://www.cve.org/CVERecord?id=CVE-2025-21927 Référence CVE CVE-2025-21928 https://www.cve.org/CVERecord?id=CVE-2025-21928 Référence CVE CVE-2025-21930 https://www.cve.org/CVERecord?id=CVE-2025-21930 Référence CVE CVE-2025-21931 https://www.cve.org/CVERecord?id=CVE-2025-21931 Référence CVE CVE-2025-21934 https://www.cve.org/CVERecord?id=CVE-2025-21934 Référence CVE CVE-2025-21935 https://www.cve.org/CVERecord?id=CVE-2025-21935 Référence CVE CVE-2025-21936 https://www.cve.org/CVERecord?id=CVE-2025-21936 Référence CVE CVE-2025-21937 https://www.cve.org/CVERecord?id=CVE-2025-21937 Référence CVE CVE-2025-21941 https://www.cve.org/CVERecord?id=CVE-2025-21941 Référence CVE CVE-2025-21943 https://www.cve.org/CVERecord?id=CVE-2025-21943 Référence CVE CVE-2025-21948 https://www.cve.org/CVERecord?id=CVE-2025-21948 Référence CVE CVE-2025-21950 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21812 Référence CVE CVE-2025-21833 https://www.cve.org/CVERecord?id=CVE-2025-21833 Référence CVE CVE-2025-21852 https://www.cve.org/CVERecord?id=CVE-2025-21852 Référence CVE CVE-2025-21853 https://www.cve.org/CVERecord?id=CVE-2025-21853 Référence CVE CVE-2025-21854 https://www.cve.org/CVERecord?id=CVE-2025-21854 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=CVE-2025-21867 Référence CVE CVE-2025-21904 https://www.cve.org/CVERecord?id=CVE-2025-21904 Référence CVE CVE-2025-21925 https://www.cve.org/CVERecord?id=CVE-2025-21925 Référence CVE CVE-2025-21926 https://www.cve.org/CVERecord?id=CVE-2025-21926 Référence CVE CVE-2025-21931 https://www.cve.org/CVERecord?id=CVE-2025-21931 Référence CVE CVE-2025-21962 https://www.cve.org/CVERecord?id=CVE-2025-21962 Référence CVE CVE-2025-21963 https://www.cve.org/CVERecord?id=CVE-2025-21963 Référence CVE CVE-2025-21964 https://www.cve.org/CVERecord?id=CVE-2025-21964 Référence CVE CVE-2025-21980 https://www.cve.org/CVERecord?id=CVE-2025-21980 Référence CVE CVE-2025-21985 https://www.cve.org/CVERecord?id=CVE-2025-21985 Référence CVE CVE-2025-21999 https://www.cve.org/CVERecord?id=CVE-2025-21999 Référence CVE CVE-2025-22004 https://www.cve.org/CVERecord?id=CVE-2025-22004 Référence CVE CVE-2025-22015 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-36903 Référence CVE CVE-2024-36927 https://www.cve.org/CVERecord?id=CVE-2024-36927 Référence CVE CVE-2024-43840 https://www.cve.org/CVERecord?id=CVE-2024-43840 Référence CVE CVE-2024-46751 https://www.cve.org/CVERecord?id=CVE-2024-46751 Référence CVE CVE-2024-53203 https://www.cve.org/CVERecord?id=CVE-2024-53203 Référence CVE CVE-2024-53209 https://www.cve.org/CVERecord?id=CVE-2024-53209 Référence CVE CVE-2024-57945 https://www.cve.org/CVERecord?id=CVE-2024-57945 Référence CVE CVE-2025-21645 https://www.cve.org/CVERecord?id=CVE-2025-21645 Référence CVE CVE-2025-21839 https://www.cve.org/CVERecord?id=CVE-2025-21839 Référence CVE CVE-2025-21931 https://www.cve.org/CVERecord?id=CVE-2025-21931 Référence CVE CVE-2025-22062 https://www.cve.org/CVERecord?id=CVE-2025-22062 Référence CVE CVE-2025-37819 https://www.cve.org/CVERecord?id=CVE-2025-37819 Référence CVE CVE-2025-37890 https://www.cve.org/CVERecord?id=CVE-2025-37890 Référence CVE CVE-2025-37897 https://www.cve.org/CVERecord?id=CVE-2025-37897 Référence CVE CVE-2025-37901 https://www.cve.org/CVERecord?id=CVE-2025-37901 Référence CVE CVE-2025-37902 https://www.cve.org/CVERecord?id=CVE-2025-37902 Référence CVE CVE-2025-37903 https://www.cve.org/CVERecord?id=CVE-2025-37903 Référence CVE CVE-2025-37905 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21918 Référence CVE CVE-2025-21922 https://www.cve.org/CVERecord?id=CVE-2025-21922 Référence CVE CVE-2025-21923 https://www.cve.org/CVERecord?id=CVE-2025-21923 Référence CVE CVE-2025-21924 https://www.cve.org/CVERecord?id=CVE-2025-21924 Référence CVE CVE-2025-21925 https://www.cve.org/CVERecord?id=CVE-2025-21925 Référence CVE CVE-2025-21926 https://www.cve.org/CVERecord?id=CVE-2025-21926 Référence CVE CVE-2025-21927 https://www.cve.org/CVERecord?id=CVE-2025-21927 Référence CVE CVE-2025-21928 https://www.cve.org/CVERecord?id=CVE-2025-21928 Référence CVE CVE-2025-21930 https://www.cve.org/CVERecord?id=CVE-2025-21930 Référence CVE CVE-2025-21931 https://www.cve.org/CVERecord?id=CVE-2025-21931 Référence CVE CVE-2025-21934 https://www.cve.org/CVERecord?id=CVE-2025-21934 Référence CVE CVE-2025-21935 https://www.cve.org/CVERecord?id=CVE-2025-21935 Référence CVE CVE-2025-21936 https://www.cve.org/CVERecord?id=CVE-2025-21936 Référence CVE CVE-2025-21937 https://www.cve.org/CVERecord?id=CVE-2025-21937 Référence CVE CVE-2025-21941 https://www.cve.org/CVERecord?id=CVE-2025-21941 Référence CVE CVE-2025-21943 https://www.cve.org/CVERecord?id=CVE-2025-21943 Référence CVE CVE-2025-21948 https://www.cve.org/CVERecord?id=CVE-2025-21948 Référence CVE CVE-2025-21950 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21918 Référence CVE CVE-2025-21922 https://www.cve.org/CVERecord?id=CVE-2025-21922 Référence CVE CVE-2025-21923 https://www.cve.org/CVERecord?id=CVE-2025-21923 Référence CVE CVE-2025-21924 https://www.cve.org/CVERecord?id=CVE-2025-21924 Référence CVE CVE-2025-21925 https://www.cve.org/CVERecord?id=CVE-2025-21925 Référence CVE CVE-2025-21926 https://www.cve.org/CVERecord?id=CVE-2025-21926 Référence CVE CVE-2025-21927 https://www.cve.org/CVERecord?id=CVE-2025-21927 Référence CVE CVE-2025-21928 https://www.cve.org/CVERecord?id=CVE-2025-21928 Référence CVE CVE-2025-21930 https://www.cve.org/CVERecord?id=CVE-2025-21930 Référence CVE CVE-2025-21931 https://www.cve.org/CVERecord?id=CVE-2025-21931 Référence CVE CVE-2025-21934 https://www.cve.org/CVERecord?id=CVE-2025-21934 Référence CVE CVE-2025-21935 https://www.cve.org/CVERecord?id=CVE-2025-21935 Référence CVE CVE-2025-21936 https://www.cve.org/CVERecord?id=CVE-2025-21936 Référence CVE CVE-2025-21937 https://www.cve.org/CVERecord?id=CVE-2025-21937 Référence CVE CVE-2025-21941 https://www.cve.org/CVERecord?id=CVE-2025-21941 Référence CVE CVE-2025-21943 https://www.cve.org/CVERecord?id=CVE-2025-21943 Référence CVE CVE-2025-21948 https://www.cve.org/CVERecord?id=CVE-2025-21948 Référence CVE CVE-2025-21950 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-018015Linux の Linux Kernel におけるリソースのロックに関する脆弱性

Linux の Linux Kernel には、リソースのロックに関する脆弱性が存在します。

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: < 5.0, 6.1.140 ≤ 6.1.*, 6.6.92 ≤ 6.6.*, 6.12.19 ≤ 6.12.*, 6.13.7 ≤ 6.13.*, 6.14 ≤ *
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 1 Apr 2025 · Last source change 23 May 2026, 15:57 UTC · CWE-667 · Improper Locking

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

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

Material change intelligence

What changed after publication

View recent updates ↗

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

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
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-21931 · cve.blacktree.nl