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

mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize()

Linux · Linux

Official source article: Siemens SSA-019113 ↗. Check the applicable product and release in the original source.

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 25 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 8 Sep 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.23% 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 25 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.17-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.158-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.17-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.17-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-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
SSA-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
In the Linux kernel, the following vulnerability has been resolved: mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize() If migration succeeded, we called folio_migrate_flags()->mem_cgroup_migrate() to migrate the memcg from the old to the new folio. This will set memcg_data of the old folio to 0. Similarly, if migration failed, memcg_data of the dst folio is left unset. If we call folio_putback_lru() on such folios (memcg_data == 0), we will add the folio to be freed to the LRU, making memcg code unhappy. Running the hmm selftests: # ./hmm-tests ... # RUN hmm.hmm_device_private.migrate ... [ 102.078007][T14893] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x7ff27d200 pfn:0x13cc00 [ 102.079974][T14893] anon flags: 0x17ff00000020018(uptodate|dirty|swapbacked|node=0|zone=2|lastcpupid=0x7ff) [ 102.082037][T14893] raw: 017ff00000020018 dead000000000100 dead000000000122 ffff8881353896c9 [ 102.083687][T14893] raw: 00000007ff27d200 0000000000000000 00000001ffffffff 0000000000000000 [ 102.085331][T14893] page dumped because: VM_WARN_ON_ONCE_FOLIO(!memcg && !mem_cgroup_disabled()) [ 102.087230][T14893] ------------[ cut here ]------------ [ 102.088279][T14893] WARNING: CPU: 0 PID: 14893 at ./include/linux/memcontrol.h:726 folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.090478][T14893] Modules linked in: [ 102.091244][T14893] CPU: 0 UID: 0 PID: 14893 Comm: hmm-tests Not tainted 6.13.0-09623-g6c216bc522fd #151 [ 102.093089][T14893] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014 [ 102.094848][T14893] RIP: 0010:folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.096104][T14893] Code: ... [ 102.099908][T14893] RSP: 0018:ffffc900236c37b0 EFLAGS: 00010293 [ 102.101152][T14893] RAX: 0000000000000000 RBX: ffffea0004f30000 RCX: ffffffff8183f426 [ 102.102684][T14893] RDX: ffff8881063cb880 RSI: ffffffff81b8117f RDI: ffff8881063cb880 [ 102.104227][T14893] RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000000 [ 102.105757][T14893] R10: 0000000000000001 R11: 0000000000000002 R12: ffffc900236c37d8 [ 102.107296][T14893] R13: ffff888277a2bcb0 R14: 000000000000001f R15: 0000000000000000 [ 102.108830][T14893] FS: 00007ff27dbdd740(0000) GS:ffff888277a00000(0000) knlGS:0000000000000000 [ 102.110643][T14893] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 102.111924][T14893] CR2: 00007ff27d400000 CR3: 000000010866e000 CR4: 0000000000750ef0 [ 102.113478][T14893] PKRU: 55555554 [ 102.114172][T14893] Call Trace: [ 102.114805][T14893] [ 102.115397][T14893] ? folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.116547][T14893] ? __warn.cold+0x110/0x210 [ 102.117461][T14893] ? folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.118667][T14893] ? report_bug+0x1b9/0x320 [ 102.119571][T14893] ? handle_bug+0x54/0x90 [ 102.120494][T14893] ? exc_invalid_op+0x17/0x50 [ 102.121433][T14893] ? asm_exc_invalid_op+0x1a/0x20 [ 102.122435][T14893] ? __wake_up_klogd.part.0+0x76/0xd0 [ 102.123506][T14893] ? dump_page+0x4f/0x60 [ 102.124352][T14893] ? folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.125500][T14893] folio_batch_move_lru+0xd4/0x200 [ 102.126577][T14893] ? __pfx_lru_add+0x10/0x10 [ 102.127505][T14893] __folio_batch_add_and_move+0x391/0x720 [ 102.128633][T14893] ? __pfx_lru_add+0x10/0x10 [ 102.129550][T14893] folio_putback_lru+0x16/0x80 [ 102.130564][T14893] migrate_device_finalize+0x9b/0x530 [ 102.131640][T14893] dmirror_migrate_to_device.constprop.0+0x7c5/0xad0 [ 102.133047][T14893] dmirror_fops_unlocked_ioctl+0x89b/0xc80 Likely, nothing else goes wrong: putting the last folio reference will remove the folio from the LRU again. So besides memcg complaining, adding the folio to be freed to the LRU is just an unnecessary step. The new flow resembles what we have in migrate_folio_move(): add the dst to the lru, rem ---truncated---
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
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-7599

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize() If migration succeeded, we called folio_migrate_flags()->mem_cgroup_migrate() to migrate the memcg from the old to the new folio. This will set memcg_data of the old folio to 0. Similarly, if migration failed, memcg_data of the dst folio is left unset. If we call folio_putback_lru() on such folios (memcg_data == 0), we will add the folio to be freed to the LRU, making memcg code unhappy. Running the hmm selftests: # ./hmm-tests ... # RUN hmm.hmm_device_private.migrate ... [ 102.078007][T14893] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x7ff27d200 pfn:0x13cc00 [ 102.079974][T14893] anon flags: 0x17ff00000020018(uptodate|dirty|swapbacked|node=0|zone=2|lastcpupid=0x7ff) [ 102.082037][T14893] raw: 017ff00000020018 dead000000000100 dead000000000122 ffff8881353896c9 [ 102.083687][T14893] raw: 00000007ff27d200 0000000000000000 00000001ffffffff 0000000000000000 [ 102.085331][T14893] page dumped because: VM_WARN_ON_ONCE_FOLIO(!memcg && !mem_cgroup_disabled()) [ 102.087230][T14893] ------------[ cut here ]------------ [ 102.088279][T14893] WARNING: CPU: 0 PID: 14893 at ./include/linux/memcontrol.h:726 folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.090478][T14893] Modules linked in: [ 102.091244][T14893] CPU: 0 UID: 0 PID: 14893 Comm: hmm-tests Not tainted 6.13.0-09623-g6c216bc522fd #151 [ 102.093089][T14893] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014 [ 102.094848][T14893] RIP: 0010:folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.096104][T14893] Code: ... [ 102.099908][T14893] RSP: 0018:ffffc900236c37b0 EFLAGS: 00010293 [ 102.101152][T14893] RAX: 0000000000000000 RBX: ffffea0004f30000 RCX: ffffffff8183f426 [ 102.102684][T14893] RDX: ffff8881063cb880 RSI: ffffffff81b8117f RDI: ffff8881063cb880 [ 102.104227][T14893] RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000000 [ 102.105757][T14893] R10: 0000000000000001 R11: 0000000000000002 R12: ffffc900236c37d8 [ 102.107296][T14893] R13: ffff888277a2bcb0 R14: 000000000000001f R15: 0000000000000000 [ 102.108830][T14893] FS: 00007ff27dbdd740(0000) GS:ffff888277a00000(0000) knlGS:0000000000000000 [ 102.110643][T14893] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 102.111924][T14893] CR2: 00007ff27d400000 CR3: 000000010866e000 CR4: 0000000000750ef0 [ 102.113478][T14893] PKRU: 55555554 [ 102.114172][T14893] Call Trace: [ 102.114805][T14893] <TASK> [ 102.115397][T14893] ? folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.116547][T14893] ? __warn.cold+0x110/0x210 [ 102.117461][T14893] ? folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.118667][T14893] ? report_bug+0x1b9/0x320 [ 102.119571][T14893] ? handle_bug+0x54/0x90 [ 102.120494][T14893] ? exc_invalid_op+0x17/0x50 [ 102.121433][T14893] ? asm_exc_invalid_op+0x1a/0x20 [ 102.122435][T14893] ? __wake_up_klogd.part.0+0x76/0xd0 [ 102.123506][T14893] ? dump_page+0x4f/0x60 [ 102.124352][T14893] ? folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.125500][T14893] folio_batch_move_lru+0xd4/0x200 [ 102.126577][T14893] ? __pfx_lru_add+0x10/0x10 [ 102.127505][T14893] __folio_batch_add_and_move+0x391/0x720 [ 102.128633][T14893] ? __pfx_lru_add+0x10/0x10 [ 102.129550][T14893] folio_putback_lru+0x16/0x80 [ 102.130564][T14893] migrate_device_finalize+0x9b/0x530 [ 102.131640][T14893] dmirror_migrate_to_device.constprop.0+0x7c5/0xad0 [ 102.133047][T14893] dmirror_fops_unlocked_ioctl+0x89b/0xc80 Likely, nothing else goes wrong: putting the last folio reference will remove the folio from the LRU again. So besides memcg complaining, adding the folio to be freed to the LRU is just an unnecessary step. The new flow resembles what we have in migrate_folio_move(): add the dst to the lru, rem ---truncated---

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
5.5 · CVSS 3.1
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 25 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: mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize() If migration succeeded, we called folio_migrate_flags()->mem_cgroup_migrate() to migrate the memcg from the old to the new folio. This will set memcg_data of the old folio to 0. Similarly, if migration failed, memcg_data of the dst folio is left unset. If we call folio_putback_lru() on such folios (memcg_data == 0), we will add the folio to be freed to the LRU, making memcg code unhappy. Running the hmm selftests: # ./hmm-tests ... # RUN hmm.hmm_device_private.migrate ... [ 102.078007][T14893] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x7ff27d200 pfn:0x13cc00 [ 102.079974][T14893] anon flags: 0x17ff00000020018(uptodate|dirty|swapbacked|node=0|zone=2|lastcpupid=0x7ff) [ 102.082037][T14893] raw: 017ff00000020018 dead000000000100 dead000000000122 ffff8881353896c9 [ 102.083687][T14893] raw: 00000007ff27d200 0000000000000000 00000001ffffffff 0000000000000000 [ 102.085331][T14893] page dumped because: VM_WARN_ON_ONCE_FOLIO(!memcg && !mem_cgroup_disabled()) [ 102.087230][T14893] ------------[ cut here ]------------ [ 102.088279][T14893] WARNING: CPU: 0 PID: 14893 at ./include/linux/memcontrol.h:726 folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.090478][T14893] Modules linked in: [ 102.091244][T14893] CPU: 0 UID: 0 PID: 14893 Comm: hmm-tests Not tainted 6.13.0-09623-g6c216bc522fd #151 [ 102.093089][T14893] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014 [ 102.094848][T14893] RIP: 0010:folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.096104][T14893] Code: ... [ 102.099908][T14893] RSP: 0018:ffffc900236c37b0 EFLAGS: 00010293 [ 102.101152][T14893] RAX: 0000000000000000 RBX: ffffea0004f30000 RCX: ffffffff8183f426 [ 102.102684][T14893] RDX: ffff8881063cb880 RSI: ffffffff81b8117f RDI: ffff8881063cb880 [ 102.104227][T14893] RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000000 [ 102.105757][T14893] R10: 0000000000000001 R11: 0000000000000002 R12: ffffc900236c37d8 [ 102.107296][T14893] R13: ffff888277a2bcb0 R14: 000000000000001f R15: 0000000000000000 [ 102.108830][T14893] FS: 00007ff27dbdd740(0000) GS:ffff888277a00000(0000) knlGS:0000000000000000 [ 102.110643][T14893] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 102.111924][T14893] CR2: 00007ff27d400000 CR3: 000000010866e000 CR4: 0000000000750ef0 [ 102.113478][T14893] PKRU: 55555554 [ 102.114172][T14893] Call Trace: [ 102.114805][T14893] <TASK> [ 102.115397][T14893] ? folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.116547][T14893] ? __warn.cold+0x110/0x210 [ 102.117461][T14893] ? folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.118667][T14893] ? report_bug+0x1b9/0x320 [ 102.119571][T14893] ? handle_bug+0x54/0x90 [ 102.120494][T14893] ? exc_invalid_op+0x17/0x50 [ 102.121433][T14893] ? asm_exc_invalid_op+0x1a/0x20 [ 102.122435][T14893] ? __wake_up_klogd.part.0+0x76/0xd0 [ 102.123506][T14893] ? dump_page+0x4f/0x60 [ 102.124352][T14893] ? folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.125500][T14893] folio_batch_move_lru+0xd4/0x200 [ 102.126577][T14893] ? __pfx_lru_add+0x10/0x10 [ 102.127505][T14893] __folio_batch_add_and_move+0x391/0x720 [ 102.128633][T14893] ? __pfx_lru_add+0x10/0x10 [ 102.129550][T14893] folio_putback_lru+0x16/0x80 [ 102.130564][T14893] migrate_device_finalize+0x9b/0x530 [ 102.131640][T14893] dmirror_migrate_to_device.constprop.0+0x7c5/0xad0 [ 102.133047][T14893] dmirror_fops_unlocked_ioctl+0x89b/0xc80 Likely, nothing else goes wrong: putting the last folio reference will remove the folio from the LRU again. So besides memcg complaining, adding the folio to be freed to the LRU is just an unnecessary step. The new flow resembles what we have in migrate_folio_move(): add the dst to the lru, rem ---truncated---

What

In the Linux kernel, the following vulnerability has been resolved: mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize() If migration succeeded, we called folio_migrate_flags()->mem_cgroup_migrate() to migrate the memcg from the old to the new folio. This will set memcg_data of the old folio to 0. Similarly, if migration failed, memcg_data of the dst folio is left unset. If we call folio_putback_lru() on such folios (memcg_data == 0), we will add the folio to be freed to the LRU, making memcg code unhappy. Running the hmm selftests: # ./hmm-tests ... # RUN hmm.hmm_device_private.migrate ... [ 102.078007][T14893] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x7ff27d200 pfn:0x13cc00 [ 102.079974][T14893] anon flags: 0x17ff00000020018(uptodate|dirty|swapbacked|node=0|zone=2|lastcpupid=0x7ff) [ 102.082037][T14893] raw: 017ff00000020018 dead000000000100 dead000000000122 ffff8881353896c9 [ 102.083687][T14893] raw: 00000007ff27d200 0000000000000000 00000001ffffffff 0000000000000000 [ 102.085331][T14893] page dumped because: VM_WARN_ON_ONCE_FOLIO(!memcg && !mem_cgroup_disabled()) [ 102.087230][T14893] ------------[ cut here ]------------ [ 102.088279][T14893] WARNING: CPU: 0 PID: 14893 at ./include/linux/memcontrol.h:726 folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.090478][T14893] Modules linked in: [ 102.091244][T14893] CPU: 0 UID: 0 PID: 14893 Comm: hmm-tests Not tainted 6.13.0-09623-g6c216bc522fd #151 [ 102.093089][T14893] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014 [ 102.094848][T14893] RIP: 0010:folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.096104][T14893] Code: ... [ 102.099908][T14893] RSP: 0018:ffffc900236c37b0 EFLAGS: 00010293 [ 102.101152][T14893] RAX: 0000000000000000 RBX: ffffea0004f30000 RCX: ffffffff8183f426 [ 102.102684][T14893] RDX: ffff8881063cb880 RSI: ffffffff81b8117f RDI: ffff8881063cb880 [ 102.104227][T14893] RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000000 [ 102.105757][T14893] R10: 0000000000000001 R11: 0000000000000002 R12: ffffc900236c37d8 [ 102.107296][T14893] R13: ffff888277a2bcb0 R14: 000000000000001f R15: 0000000000000000 [ 102.108830][T14893] FS: 00007ff27dbdd740(0000) GS:ffff888277a00000(0000) knlGS:0000000000000000 [ 102.110643][T14893] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 102.111924][T14893] CR2: 00007ff27d400000 CR3: 000000010866e000 CR4: 0000000000750ef0 [ 102.113478][T14893] PKRU: 55555554 [ 102.114172][T14893] Call Trace: [ 102.114805][T14893] <TASK> [ 102.115397][T14893] ? folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.116547][T14893] ? __warn.cold+0x110/0x210 [ 102.117461][T14893] ? folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.118667][T14893] ? report_bug+0x1b9/0x320 [ 102.119571][T14893] ? handle_bug+0x54/0x90 [ 102.120494][T14893] ? exc_invalid_op+0x17/0x50 [ 102.121433][T14893] ? asm_exc_invalid_op+0x1a/0x20 [ 102.122435][T14893] ? __wake_up_klogd.part.0+0x76/0xd0 [ 102.123506][T14893] ? dump_page+0x4f/0x60 [ 102.124352][T14893] ? folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.125500][T14893] folio_batch_move_lru+0xd4/0x200 [ 102.126577][T14893] ? __pfx_lru_add+0x10/0x10 [ 102.127505][T14893] __folio_batch_add_and_move+0x391/0x720 [ 102.128633][T14893] ? __pfx_lru_add+0x10/0x10 [ 102.129550][T14893] folio_putback_lru+0x16/0x80 [ 102.130564][T14893] migrate_device_finalize+0x9b/0x530 [ 102.131640][T14893] dmirror_migrate_to_device.constprop.0+0x7c5/0xad0 [ 102.133047][T14893] dmirror_fops_unlocked_ioctl+0x89b/0xc80 Likely, nothing else goes wrong: putting the last folio reference will remove the folio from the LRU again. So besides memcg complaining, adding the folio to be freed to the LRU is just an unnecessary step. The new flow resembles what we have in migrate_folio_move(): add the dst to the lru, rem ---truncated---

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

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: mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize() If migration succeeded, we called folio_migrate_flags()->mem_cgroup_migrate() to migrate the memcg from the old to the new folio. This will set memcg_data of the old folio to 0. Similarly, if migration failed, memcg_data of the dst folio is left unset. If we call folio_putback_lru() on such folios (memcg_data == 0), we will add the folio to be freed to the LRU, making memcg code unhappy. Running the hmm selftests: # ./hmm-tests ... # RUN hmm.hmm_device_private.migrate ... [ 102.078007][T14893] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x7ff27d200 pfn:0x13cc00 [ 102.079974][T14893] anon flags: 0x17ff00000020018(uptodate|dirty|swapbacked|node=0|zone=2|lastcpupid=0x7ff) [ 102.082037][T14893] raw: 017ff00000020018 dead000000000100 dead000000000122 ffff8881353896c9 [ 102.083687][T14893] raw: 00000007ff27d200 0000000000000000 00000001ffffffff 0000000000000000 [ 102.085331][T14893] page dumped because: VM_WARN_ON_ONCE_FOLIO(!memcg && !mem_cgroup_disabled()) [ 102.087230][T14893] ------------[ cut here ]------------ [ 102.088279][T14893] WARNING: CPU: 0 PID: 14893 at ./include/linux/memcontrol.h:726 folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.090478][T14893] Modules linked in: [ 102.091244][T14893] CPU: 0 UID: 0 PID: 14893 Comm: hmm-tests Not tainted 6.13.0-09623-g6c216bc522fd #151 [ 102.093089][T14893] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014 [ 102.094848][T14893] RIP: 0010:folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.096104][T14893] Code: ... [ 102.099908][T14893] RSP: 0018:ffffc900236c37b0 EFLAGS: 00010293 [ 102.101152][T14893] RAX: 0000000000000000 RBX: ffffea0004f30000 RCX: ffffffff8183f426 [ 102.102684][T14893] RDX: ffff8881063cb880 RSI: ffffffff81b8117f RDI: ffff8881063cb880 [ 102.104227][T14893] RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000000 [ 102.105757][T14893] R10: 0000000000000001 R11: 0000000000000002 R12: ffffc900236c37d8 [ 102.107296][T14893] R13: ffff888277a2bcb0 R14: 000000000000001f R15: 0000000000000000 [ 102.108830][T14893] FS: 00007ff27dbdd740(0000) GS:ffff888277a00000(0000) knlGS:0000000000000000 [ 102.110643][T14893] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 102.111924][T14893] CR2: 00007ff27d400000 CR3: 000000010866e000 CR4: 0000000000750ef0 [ 102.113478][T14893] PKRU: 55555554 [ 102.114172][T14893] Call Trace: [ 102.114805][T14893] <TASK> [ 102.115397][T14893] ? folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.116547][T14893] ? __warn.cold+0x110/0x210 [ 102.117461][T14893] ? folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.118667][T14893] ? report_bug+0x1b9/0x320 [ 102.119571][T14893] ? handle_bug+0x54/0x90 [ 102.120494][T14893] ? exc_invalid_op+0x17/0x50 [ 102.121433][T14893] ? asm_exc_invalid_op+0x1a/0x20 [ 102.122435][T14893] ? __wake_up_klogd.part.0+0x76/0xd0 [ 102.123506][T14893] ? dump_page+0x4f/0x60 [ 102.124352][T14893] ? folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.125500][T14893] folio_batch_move_lru+0xd4/0x200 [ 102.126577][T14893] ? __pfx_lru_add+0x10/0x10 [ 102.127505][T14893] __folio_batch_add_and_move+0x391/0x720 [ 102.128633][T14893] ? __pfx_lru_add+0x10/0x10 [ 102.129550][T14893] folio_putback_lru+0x16/0x80 [ 102.130564][T14893] migrate_device_finalize+0x9b/0x530 [ 102.131640][T14893] dmirror_migrate_to_device.constprop.0+0x7c5/0xad0 [ 102.133047][T14893] dmirror_fops_unlocked_ioctl+0x89b/0xc80 Likely, nothing else goes wrong: putting the last folio reference will remove the folio from the LRU again. So besides memcg complaining, adding the folio to be freed to the LRU is just an unnecessary step. The new flow resembles what we have in migrate_folio_move(): add the dst to the lru, rem ---truncated---

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

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 → Use After Free → 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-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

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

Official authority intelligence

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

ENISA EUVD · EUVD-2025-7599Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize() If migration succeeded, we called folio_migrate_flags()->mem_cgroup_migrate() to migrate the memcg from the old to the new folio. This will set memcg_data of the old folio to 0. Similarly, if migration failed, memcg_data of the dst folio is left unset. If we call folio_putback_lru() on such folios (memcg_data == 0), we will add the folio to be freed to the LRU, making memcg code unhappy. Running the hmm selftests: # ./hmm-tests ... # RUN hmm.hmm_device_private.migrate ... [ 102.078007][T14893] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x7ff27d200 pfn:0x13cc00 [ 102.079974][T14893] anon flags: 0x17ff00000020018(uptodate|dirty|swapbacked|node=0|zone=2|lastcpupid=0x7ff) [ 102.082037][T14893] raw: 017ff00000020018 dead000000000100 dead000000000122 ffff8881353896c9 [ 102.083687][T14893] raw: 00000007ff27d200 0000000000000000 00000001ffffffff 0000000000000000 [ 102.085331][T14893] page dumped because: VM_WARN_ON_ONCE_FOLIO(!memcg && !mem_cgroup_disabled()) [ 102.087230][T14893] ------------[ cut here ]------------ [ 102.088279][T14893] WARNING: CPU: 0 PID: 14893 at ./include/linux/memcontrol.h:726 folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.090478][T14893] Modules linked in: [ 102.091244][T14893] CPU: 0 UID: 0 PID: 14893 Comm: hmm-tests Not tainted 6.13.0-09623-g6c216bc522fd #151 [ 102.093089][T14893] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014 [ 102.094848][T14893] RIP: 0010:folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.096104][T14893] Code: ... [ 102.099908][T14893] RSP: 0018:ffffc900236c37b0 EFLAGS: 00010293 [ 102.101152][T14893] RAX: 0000000000000000 RBX: ffffea0004f30000 RCX: ffffffff8183f426 [ 102.102684][T14893] RDX: ffff8881063cb880 RSI: ffffffff81b8117f RDI: ffff8881063cb880 [ 102.104227][T14893] RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000000 [ 102.105757][T14893] R10: 0000000000000001 R11: 0000000000000002 R12: ffffc900236c37d8 [ 102.107296][T14893] R13: ffff888277a2bcb0 R14: 000000000000001f R15: 0000000000000000 [ 102.108830][T14893] FS: 00007ff27dbdd740(0000) GS:ffff888277a00000(0000) knlGS:0000000000000000 [ 102.110643][T14893] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 102.111924][T14893] CR2: 00007ff27d400000 CR3: 000000010866e000 CR4: 0000000000750ef0 [ 102.113478][T14893] PKRU: 55555554 [ 102.114172][T14893] Call Trace: [ 102.114805][T14893] <TASK> [ 102.115397][T14893] ? folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.116547][T14893] ? __warn.cold+0x110/0x210 [ 102.117461][T14893] ? folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.118667][T14893] ? report_bug+0x1b9/0x320 [ 102.119571][T14893] ? handle_bug+0x54/0x90 [ 102.120494][T14893] ? exc_invalid_op+0x17/0x50 [ 102.121433][T14893] ? asm_exc_invalid_op+0x1a/0x20 [ 102.122435][T14893] ? __wake_up_klogd.part.0+0x76/0xd0 [ 102.123506][T14893] ? dump_page+0x4f/0x60 [ 102.124352][T14893] ? folio_lruvec_lock_irqsave+0x10e/0x170 [ 102.125500][T14893] folio_batch_move_lru+0xd4/0x200 [ 102.126577][T14893] ? __pfx_lru_add+0x10/0x10 [ 102.127505][T14893] __folio_batch_add_and_move+0x391/0x720 [ 102.128633][T14893] ? __pfx_lru_add+0x10/0x10 [ 102.129550][T14893] folio_putback_lru+0x16/0x80 [ 102.130564][T14893] migrate_device_finalize+0x9b/0x530 [ 102.131640][T14893] dmirror_migrate_to_device.constprop.0+0x7c5/0xad0 [ 102.133047][T14893] dmirror_fops_unlocked_ioctl+0x89b/0xc80 Likely, nothing else goes wrong: putting the last folio reference will remove the folio from the LRU again. So besides memcg complaining, adding the folio to be freed to the LRU is just an unnecessary step. The new flow resembles what we have in migrate_folio_move(): add the dst to the lru, rem ---truncated---

Official EUVD record ↗
BSI · German · WID-SEC-2026-2253IBM Security Verify Access: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM Security Verify Access ausnutzen, um erweiterte Berechtigungen zu erlangen, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, sensible Informationen offenzulegen und andere, nicht näher bezeichnete Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2025-0545Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen und um nicht näher beschriebene Auswirkungen zu verursachen.

Official advisory ↗
BSI · German · WID-SEC-2025-1439Dell Secure Connect Gateway: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen in Dell Secure Connect Gateway ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

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

24-53124, CVE-2024-53170, CVE-2024-54458, CVE-2024-56631, CVE-2024-56703, CVE-2024-56719, CVE-2024-57917, CVE-2024-57924, CVE-2024-57973, CVE-2024-57977, CVE-2024-57979, CVE-2024-58011, CVE-2024-58016, CVE-2024-58020, CVE-2024-58056, CVE-2024-58058, CVE-2024-58061, CVE-2024-58086, CVE-2025-21645, CVE-2025-21648, CVE-2025-21655, CVE-2025-21676, CVE-2025-21682, CVE-2025-21702, CVE-2025-21705, CVE-2025-21706, CVE-2025-21707, CVE-2025-21718, CVE-2025-21731, CVE-2025-21745, CVE-2025-21758, CVE-2025-21760, CVE-2025-21764, CVE-2025-21765, CVE-2025-21780, CVE-2025-21795, CVE-2025-21796, CVE-2025-21802, CVE-2025-21814, CVE-2025-21846, CVE-2025-21853, CVE-2025-21861, CVE-2025-21864, CVE-2025-21867, CVE-2025-21875, CVE-2025-21887, CVE-2025-21913, CVE-2025-21919, CVE-2025-21925, CVE-2025-21926, CVE-2025-21938, CVE-2025-21959, CVE-2025-21999, CVE-2025-22005, CVE-2025-22015, CVE-2025-22055, CVE-2025-22056, CVE-2025-22060, CVE-2025-22083, CVE-2025-22090, CVE-2025-22095, CVE-2025-22107, CVE-2025-22111, CVE-2025-22121, CVE-2025-23136, CVE-2025-23143, CVE-2025-37785, CVE-2025-37909, CVE-2025-37917, CVE-2025-37945, CVE-2025-37959, CVE-2025-37964, CVE-2025-37972, CVE-2025-37980, CVE-2025-38125, CVE-2025-38162, CVE-2025-38192, CVE-2025-38201, CVE-2025-38232, CVE-2025-38322, CVE-2025-38591, CVE-2025-38614, CVE-2025

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

d?id=CVE-2024-41014 Référence CVE CVE-2024-46830 https://www.cve.org/CVERecord?id=CVE-2024-46830 Référence CVE CVE-2024-47666 https://www.cve.org/CVERecord?id=CVE-2024-47666 Référence CVE CVE-2024-49968 https://www.cve.org/CVERecord?id=CVE-2024-49968 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-57795 https://www.cve.org/CVERecord?id=CVE-2024-57795 Référence CVE CVE-2024-58011 https://www.cve.org/CVERecord?id=CVE-2024-58011 Référence CVE CVE-2025-21780 https://www.cve.org/CVERecord?id=CVE-2025-21780 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-22022 https://www.cve.org/CVERecord?id=CVE-2025-22022 Référence CVE CVE-2025-22058 https://www.cve.org/CVERecord?id=CVE-2025-22058 Référence CVE CVE-2025-22111 https://www.cve.org/CVERecord?id=CVE-2025-22111 Référence CVE CVE-2025-22121 https://www.cve.org/CVERecord?id=CVE-2025-22121 Référence CVE CVE-2025-23143 https://www.cve.org/CVERecord?id=CVE-2025-23143 Référence CVE CVE-2025-37849 https://www.cve.org/CVERecord?id=CVE-2025-37849 Référence CVE CVE-2025-38022 https://www.cve.org/CVERecord?id=CVE-2025-38022 Référence CVE CVE-2025-38057 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-2024-56538 Référence CVE CVE-2024-56581 https://www.cve.org/CVERecord?id=CVE-2024-56581 Référence CVE CVE-2024-56593 https://www.cve.org/CVERecord?id=CVE-2024-56593 Référence CVE CVE-2024-56640 https://www.cve.org/CVERecord?id=CVE-2024-56640 Référence CVE CVE-2024-57795 https://www.cve.org/CVERecord?id=CVE-2024-57795 Référence CVE CVE-2024-58011 https://www.cve.org/CVERecord?id=CVE-2024-58011 Référence CVE CVE-2025-21704 https://www.cve.org/CVERecord?id=CVE-2025-21704 Référence CVE CVE-2025-21735 https://www.cve.org/CVERecord?id=CVE-2025-21735 Référence CVE CVE-2025-21780 https://www.cve.org/CVERecord?id=CVE-2025-21780 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-22022 https://www.cve.org/CVERecord?id=CVE-2025-22022 Référence CVE CVE-2025-22058 https://www.cve.org/CVERecord?id=CVE-2025-22058 Référence CVE CVE-2025-22111 https://www.cve.org/CVERecord?id=CVE-2025-22111 Référence CVE CVE-2025-22121 https://www.cve.org/CVERecord?id=CVE-2025-22121 Référence CVE CVE-2025-23143 https://www.cve.org/CVERecord?id=CVE-2025-23143 Référence CVE CVE-2025-37849 https://www.cve.org/CVERecord?id=CVE-2025-37849 Référence CVE CVE-2025-38022 https://www.cve.org/CVERecord?id=CVE-2025-38022 Référence CVE CVE-2025-38057 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-2024-46830 Référence CVE CVE-2024-47666 https://www.cve.org/CVERecord?id=CVE-2024-47666 Référence CVE CVE-2024-49968 https://www.cve.org/CVERecord?id=CVE-2024-49968 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-21735 https://www.cve.org/CVERecord?id=CVE-2025-21735 Référence CVE CVE-2025-21780 https://www.cve.org/CVERecord?id=CVE-2025-21780 Référence CVE CVE-2025-21833 https://www.cve.org/CVERecord?id=CVE-2025-21833 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-22022 https://www.cve.org/CVERecord?id=CVE-2025-22022 Référence CVE CVE-2025-22058 https://www.cve.org/CVERecord?id=CVE-2025-22058 Référence CVE CVE-2025-22103 https://www.cve.org/CVERecord?id=CVE-2025-22103 Référence CVE CVE-2025-22105 https://www.cve.org/CVERecord?id=CVE-2025-22105 Référence CVE CVE-2025-22106 https://www.cve.org/CVERecord?id=CVE-2025-22106 Référence CVE CVE-2025-22107 https://www.cve.org/CVERecord?id=CVE-2025-22107 Référence CVE CVE-2025-22111 https://www.cve.org/CVERecord?id=CVE-2025-22111 Référence CVE CVE-2025-22113 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-2024-46830 Référence CVE CVE-2024-47666 https://www.cve.org/CVERecord?id=CVE-2024-47666 Référence CVE CVE-2024-49968 https://www.cve.org/CVERecord?id=CVE-2024-49968 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-21735 https://www.cve.org/CVERecord?id=CVE-2025-21735 Référence CVE CVE-2025-21780 https://www.cve.org/CVERecord?id=CVE-2025-21780 Référence CVE CVE-2025-21833 https://www.cve.org/CVERecord?id=CVE-2025-21833 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-22022 https://www.cve.org/CVERecord?id=CVE-2025-22022 Référence CVE CVE-2025-22058 https://www.cve.org/CVERecord?id=CVE-2025-22058 Référence CVE CVE-2025-22103 https://www.cve.org/CVERecord?id=CVE-2025-22103 Référence CVE CVE-2025-22105 https://www.cve.org/CVERecord?id=CVE-2025-22105 Référence CVE CVE-2025-22106 https://www.cve.org/CVERecord?id=CVE-2025-22106 Référence CVE CVE-2025-22107 https://www.cve.org/CVERecord?id=CVE-2025-22107 Référence CVE CVE-2025-22111 https://www.cve.org/CVERecord?id=CVE-2025-22111 Référence CVE CVE-2025-22113 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-15079 Référence CVE CVE-2025-15224 https://www.cve.org/CVERecord?id=CVE-2025-15224 Référence CVE CVE-2025-15281 https://www.cve.org/CVERecord?id=CVE-2025-15281 Référence CVE CVE-2025-15282 https://www.cve.org/CVERecord?id=CVE-2025-15282 Référence CVE CVE-2025-15366 https://www.cve.org/CVERecord?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=

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

d?id=CVE-2025-14512 Référence CVE CVE-2025-14831 https://www.cve.org/CVERecord?id=CVE-2025-14831 Référence CVE CVE-2025-15281 https://www.cve.org/CVERecord?id=CVE-2025-15281 Référence CVE CVE-2025-15282 https://www.cve.org/CVERecord?id=CVE-2025-15282 Référence CVE CVE-2025-15366 https://www.cve.org/CVERecord?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-15468 https://www.cve.org/CVERecord?id=CVE-2025-15468 Référence CVE CVE-2025-15469 https://www.cve.org/CVERecord?id=CVE-2025-15469 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-22058 https://www.cve.org/CVERecord?id=CVE-2025-22058 Référence CVE CVE-2025-22868 https://www.cve.org/CVERecord?id=CVE-2025-22868 Référence CVE CVE-2025-22873 https://www.cve.org/CVERecord?id=CVE-2025-22873 Référence CVE CVE-2025-22874 https://www.cve.org/CVERecord?id=CVE-2025-22874 Référence CVE CVE-2025-23143 https://www.cve.org/CVERecord?id=CVE-2025-23143 Référence CVE CVE-2025-27144 https://www.cve.org/CVERecord?id=CVE-2025-27144 Référence CVE CVE-2025-30204 https://www.cve.org/CVERecord?id=CVE-2025-30204 Référence CVE CVE-2025-31133 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-15281 Référence CVE CVE-2025-15282 https://www.cve.org/CVERecord?id=CVE-2025-15282 Référence CVE CVE-2025-15366 https://www.cve.org/CVERecord?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-15468 https://www.cve.org/CVERecord?id=CVE-2025-15468 Référence CVE CVE-2025-15469 https://www.cve.org/CVERecord?id=CVE-2025-15469 Référence CVE CVE-2025-21502 https://www.cve.org/CVERecord?id=CVE-2025-21502 Référence CVE CVE-2025-21587 https://www.cve.org/CVERecord?id=CVE-2025-21587 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-22058 https://www.cve.org/CVERecord?id=CVE-2025-22058 Référence CVE CVE-2025-22866 https://www.cve.org/CVERecord?id=CVE-2025-22866 Référence CVE CVE-2025-22868 https://www.cve.org/CVERecord?id=CVE-2025-22868 Référence CVE CVE-2025-22869 https://www.cve.org/CVERecord?id=CVE-2025-22869 Référence CVE CVE-2025-22870 https://www.cve.org/CVERecord?id=CVE-2025-22870 Référence CVE CVE-2025-22871 https://www.cve.org/CVERecord?id=CVE-2025-22871 Référence CVE CVE-2025-22872 https://www.cve.org/CVERecord?id=CVE-2025-22872 Référence CVE CVE-2025-22873 https://www.cve.org/CVERecord?id=

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

/notices/USN-7990-5 Référence CVE CVE-2022-49698 https://www.cve.org/CVERecord?id=CVE-2022-49698 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-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=

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

d?id=CVE-2024-36357 Référence CVE CVE-2024-49959 https://www.cve.org/CVERecord?id=CVE-2024-49959 Référence CVE CVE-2024-50195 https://www.cve.org/CVERecord?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=

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

entialité des données et une atteinte à l'intégrité des données. Solutions Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Debian LTS DLA-4404-1 du 12 décembre 2025 https://lists.debian.org/debian-lts-announce/2025/12/msg00015.html Référence CVE CVE-2023-53498 https://www.cve.org/CVERecord?id=CVE-2023-53498 Référence CVE CVE-2024-47666 https://www.cve.org/CVERecord?id=CVE-2024-47666 Référence CVE CVE-2024-50143 https://www.cve.org/CVERecord?id=CVE-2024-50143 Référence CVE CVE-2024-57947 https://www.cve.org/CVERecord?id=CVE-2024-57947 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-21887 https://www.cve.org/CVERecord?id=CVE-2025-21887 Référence CVE CVE-2025-22058 https://www.cve.org/CVERecord?id=CVE-2025-22058 Référence CVE CVE-2025-23143 https://www.cve.org/CVERecord?id=CVE-2025-23143 Référence CVE CVE-2025-38678 https://www.cve.org/CVERecord?id=CVE-2025-38678 Référence CVE CVE-2025-39866 https://www.cve.org/CVERecord?id=CVE-2025-39866 Référence CVE CVE-2025-39869 https://www.cve.org/CVERecord?id=CVE-2025-39869 Référence CVE CVE-2025-39876 https://www.cve.org/CVERecord?id=CVE-2025-39876 Référence CVE CVE-2025-39883 https://www.cve.org/CVERecord?id=

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

lévation de privilèges Systèmes affectés Debian LTS bullseye versions antérieures à 6.1.158-1~deb11u1 Résumé De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à un attaquant de provoquer une élévation de privilèges, une atteinte à la confidentialité des données et une atteinte à l'intégrité des données. Solutions Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Debian LTS DLA-4379-1 du 25 novembre 2025 https://lists.debian.org/debian-lts-announce/2025/11/msg00022.html Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-39929 https://www.cve.org/CVERecord?id=CVE-2025-39929 Référence CVE CVE-2025-39931 https://www.cve.org/CVERecord?id=CVE-2025-39931 Référence CVE CVE-2025-39934 https://www.cve.org/CVERecord?id=CVE-2025-39934 Référence CVE CVE-2025-39937 https://www.cve.org/CVERecord?id=CVE-2025-39937 Référence CVE CVE-2025-39938 https://www.cve.org/CVERecord?id=CVE-2025-39938 Référence CVE CVE-2025-39942 https://www.cve.org/CVERecord?id=CVE-2025-39942 Référence CVE CVE-2025-39943 https://www.cve.org/CVERecord?id=CVE-2025-39943 Référence CVE CVE-2025-39944 https://www.cve.org/CVERecord?id=

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

lité des données Déni de service à distance Élévation de privilèges Systèmes affectés Debian bookworm versions antérieures à 6.1.158-1 Résumé De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provoquer une élévation de privilèges, un déni de service à distance et une atteinte à la confidentialité des données. Solutions Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Debian DSA-6053-1 du 11 novembre 2025 https://lists.debian.org/debian-security-announce/2025/msg00219.html Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-39929 https://www.cve.org/CVERecord?id=CVE-2025-39929 Référence CVE CVE-2025-39931 https://www.cve.org/CVERecord?id=CVE-2025-39931 Référence CVE CVE-2025-39934 https://www.cve.org/CVERecord?id=CVE-2025-39934 Référence CVE CVE-2025-39937 https://www.cve.org/CVERecord?id=CVE-2025-39937 Référence CVE CVE-2025-39938 https://www.cve.org/CVERecord?id=CVE-2025-39938 Référence CVE CVE-2025-39942 https://www.cve.org/CVERecord?id=CVE-2025-39942 Référence CVE CVE-2025-39943 https://www.cve.org/CVERecord?id=CVE-2025-39943 Référence CVE CVE-2025-39944 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21847 Référence CVE CVE-2025-21848 https://www.cve.org/CVERecord?id=CVE-2025-21848 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-21855 https://www.cve.org/CVERecord?id=CVE-2025-21855 Référence CVE CVE-2025-21856 https://www.cve.org/CVERecord?id=CVE-2025-21856 Référence CVE CVE-2025-21857 https://www.cve.org/CVERecord?id=CVE-2025-21857 Référence CVE CVE-2025-21858 https://www.cve.org/CVERecord?id=CVE-2025-21858 Référence CVE CVE-2025-21859 https://www.cve.org/CVERecord?id=CVE-2025-21859 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-21862 https://www.cve.org/CVERecord?id=CVE-2025-21862 Référence CVE CVE-2025-21863 https://www.cve.org/CVERecord?id=CVE-2025-21863 Référence CVE CVE-2025-21864 https://www.cve.org/CVERecord?id=CVE-2025-21864 Référence CVE CVE-2025-21866 https://www.cve.org/CVERecord?id=CVE-2025-21866 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=CVE-2025-21867 Référence CVE CVE-2025-21868 https://www.cve.org/CVERecord?id=CVE-2025-21868 Référence CVE CVE-2025-21869 https://www.cve.org/CVERecord?id=CVE-2025-21869 Référence CVE CVE-2025-21870 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21847 Référence CVE CVE-2025-21848 https://www.cve.org/CVERecord?id=CVE-2025-21848 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-21855 https://www.cve.org/CVERecord?id=CVE-2025-21855 Référence CVE CVE-2025-21856 https://www.cve.org/CVERecord?id=CVE-2025-21856 Référence CVE CVE-2025-21857 https://www.cve.org/CVERecord?id=CVE-2025-21857 Référence CVE CVE-2025-21858 https://www.cve.org/CVERecord?id=CVE-2025-21858 Référence CVE CVE-2025-21859 https://www.cve.org/CVERecord?id=CVE-2025-21859 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-21862 https://www.cve.org/CVERecord?id=CVE-2025-21862 Référence CVE CVE-2025-21863 https://www.cve.org/CVERecord?id=CVE-2025-21863 Référence CVE CVE-2025-21864 https://www.cve.org/CVERecord?id=CVE-2025-21864 Référence CVE CVE-2025-21866 https://www.cve.org/CVERecord?id=CVE-2025-21866 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=CVE-2025-21867 Référence CVE CVE-2025-21868 https://www.cve.org/CVERecord?id=CVE-2025-21868 Référence CVE CVE-2025-21869 https://www.cve.org/CVERecord?id=CVE-2025-21869 Référence CVE CVE-2025-21870 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21847 Référence CVE CVE-2025-21848 https://www.cve.org/CVERecord?id=CVE-2025-21848 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-21855 https://www.cve.org/CVERecord?id=CVE-2025-21855 Référence CVE CVE-2025-21856 https://www.cve.org/CVERecord?id=CVE-2025-21856 Référence CVE CVE-2025-21857 https://www.cve.org/CVERecord?id=CVE-2025-21857 Référence CVE CVE-2025-21858 https://www.cve.org/CVERecord?id=CVE-2025-21858 Référence CVE CVE-2025-21859 https://www.cve.org/CVERecord?id=CVE-2025-21859 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-21862 https://www.cve.org/CVERecord?id=CVE-2025-21862 Référence CVE CVE-2025-21863 https://www.cve.org/CVERecord?id=CVE-2025-21863 Référence CVE CVE-2025-21864 https://www.cve.org/CVERecord?id=CVE-2025-21864 Référence CVE CVE-2025-21866 https://www.cve.org/CVERecord?id=CVE-2025-21866 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=CVE-2025-21867 Référence CVE CVE-2025-21868 https://www.cve.org/CVERecord?id=CVE-2025-21868 Référence CVE CVE-2025-21869 https://www.cve.org/CVERecord?id=CVE-2025-21869 Référence CVE CVE-2025-21870 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21847 Référence CVE CVE-2025-21848 https://www.cve.org/CVERecord?id=CVE-2025-21848 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-21855 https://www.cve.org/CVERecord?id=CVE-2025-21855 Référence CVE CVE-2025-21856 https://www.cve.org/CVERecord?id=CVE-2025-21856 Référence CVE CVE-2025-21857 https://www.cve.org/CVERecord?id=CVE-2025-21857 Référence CVE CVE-2025-21858 https://www.cve.org/CVERecord?id=CVE-2025-21858 Référence CVE CVE-2025-21859 https://www.cve.org/CVERecord?id=CVE-2025-21859 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-21862 https://www.cve.org/CVERecord?id=CVE-2025-21862 Référence CVE CVE-2025-21863 https://www.cve.org/CVERecord?id=CVE-2025-21863 Référence CVE CVE-2025-21864 https://www.cve.org/CVERecord?id=CVE-2025-21864 Référence CVE CVE-2025-21866 https://www.cve.org/CVERecord?id=CVE-2025-21866 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=CVE-2025-21867 Référence CVE CVE-2025-21868 https://www.cve.org/CVERecord?id=CVE-2025-21868 Référence CVE CVE-2025-21869 https://www.cve.org/CVERecord?id=CVE-2025-21869 Référence CVE CVE-2025-21870 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-21850 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-21855 https://www.cve.org/CVERecord?id=CVE-2025-21855 Référence CVE CVE-2025-21856 https://www.cve.org/CVERecord?id=CVE-2025-21856 Référence CVE CVE-2025-21857 https://www.cve.org/CVERecord?id=CVE-2025-21857 Référence CVE CVE-2025-21858 https://www.cve.org/CVERecord?id=CVE-2025-21858 Référence CVE CVE-2025-21859 https://www.cve.org/CVERecord?id=CVE-2025-21859 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-21862 https://www.cve.org/CVERecord?id=CVE-2025-21862 Référence CVE CVE-2025-21863 https://www.cve.org/CVERecord?id=CVE-2025-21863 Référence CVE CVE-2025-21864 https://www.cve.org/CVERecord?id=CVE-2025-21864 Référence CVE CVE-2025-21865 https://www.cve.org/CVERecord?id=CVE-2025-21865 Référence CVE CVE-2025-21866 https://www.cve.org/CVERecord?id=CVE-2025-21866 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=CVE-2025-21867 Référence CVE CVE-2025-21868 https://www.cve.org/CVERecord?id=CVE-2025-21868 Référence CVE CVE-2025-21869 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-21850 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-21855 https://www.cve.org/CVERecord?id=CVE-2025-21855 Référence CVE CVE-2025-21856 https://www.cve.org/CVERecord?id=CVE-2025-21856 Référence CVE CVE-2025-21857 https://www.cve.org/CVERecord?id=CVE-2025-21857 Référence CVE CVE-2025-21858 https://www.cve.org/CVERecord?id=CVE-2025-21858 Référence CVE CVE-2025-21859 https://www.cve.org/CVERecord?id=CVE-2025-21859 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-21862 https://www.cve.org/CVERecord?id=CVE-2025-21862 Référence CVE CVE-2025-21863 https://www.cve.org/CVERecord?id=CVE-2025-21863 Référence CVE CVE-2025-21864 https://www.cve.org/CVERecord?id=CVE-2025-21864 Référence CVE CVE-2025-21865 https://www.cve.org/CVERecord?id=CVE-2025-21865 Référence CVE CVE-2025-21866 https://www.cve.org/CVERecord?id=CVE-2025-21866 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=CVE-2025-21867 Référence CVE CVE-2025-21869 https://www.cve.org/CVERecord?id=CVE-2025-21869 Référence CVE CVE-2025-21870 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21846 Référence CVE CVE-2025-21847 https://www.cve.org/CVERecord?id=CVE-2025-21847 Référence CVE CVE-2025-21848 https://www.cve.org/CVERecord?id=CVE-2025-21848 Référence CVE CVE-2025-21850 https://www.cve.org/CVERecord?id=CVE-2025-21850 Référence CVE CVE-2025-21855 https://www.cve.org/CVERecord?id=CVE-2025-21855 Référence CVE CVE-2025-21856 https://www.cve.org/CVERecord?id=CVE-2025-21856 Référence CVE CVE-2025-21857 https://www.cve.org/CVERecord?id=CVE-2025-21857 Référence CVE CVE-2025-21858 https://www.cve.org/CVERecord?id=CVE-2025-21858 Référence CVE CVE-2025-21859 https://www.cve.org/CVERecord?id=CVE-2025-21859 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-21862 https://www.cve.org/CVERecord?id=CVE-2025-21862 Référence CVE CVE-2025-21864 https://www.cve.org/CVERecord?id=CVE-2025-21864 Référence CVE CVE-2025-21865 https://www.cve.org/CVERecord?id=CVE-2025-21865 Référence CVE CVE-2025-21866 https://www.cve.org/CVERecord?id=CVE-2025-21866 Référence CVE CVE-2025-21869 https://www.cve.org/CVERecord?id=CVE-2025-21869 Référence CVE CVE-2025-21870 https://www.cve.org/CVERecord?id=CVE-2025-21870 Référence CVE CVE-2025-21871 https://www.cve.org/CVERecord?id=CVE-2025-21871 Référence CVE CVE-2025-21876 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-002408Linux の 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: < 4.14, 5.4.300 ≤ 5.4.*, 5.10.245 ≤ 5.10.*, 5.15.194 ≤ 5.15.*, 6.1.155 ≤ 6.1.*, 6.6.109 ≤ 6.6.*, 6.12.17 ≤ 6.12.*, 6.13.5 ≤ 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
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
04

Evidence and provenance

Published 12 Mar 2025 · Last source change 8 Sept 2026, 08:40 UTC · CWE-416 · Use After Free

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-7599
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceCISA ADP
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 ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    8763cb45ab967a92a5ee49e9c544c0f0ea90e2d6 < 61fa824e304ed162fe965f64999068e6fcff2059; 8763cb45ab967a92a5ee49e9c544c0f0ea90e2d6 < 64397b0cb7c09e3ef3f9f5c7c17299c4eebd3875; 8763cb45ab967a92a5ee49e9c544c0f0ea90e2d6 < 4f52f7c50f5b6f5eeb06823e21fe546d90f9c595; 8763cb45ab967a92a5ee49e9c544c0f0ea90e2d6 < 20fb6fc51863fbff7868de8b5f6d249d2094df1f; 8763cb45ab967a92a5ee49e9c544c0f0ea90e2d6 < 78f579cb7d825134e071a1714d8d0c4fd0ffe459; 8763cb45ab967a92a5ee49e9c544c0f0ea90e2d6 < 3f9240d59e9a95d19f06120bfd1d0e681c6c0ac7; 8763cb45ab967a92a5ee49e9c544c0f0ea90e2d6 < 069dd21ea8262204f94737878389c2815a054a9e; 8763cb45ab967a92a5ee49e9c544c0f0ea90e2d6 < 41cddf83d8b00f29fd105e7a0777366edc69a5cf · Fixed: < 4.14; 5.4.300 ≤ 5.4.*; 5.10.245 ≤ 5.10.*; 5.15.194 ≤ 5.15.*; 6.1.155 ≤ 6.1.*; 6.6.109 ≤ 6.6.*; 6.12.17 ≤ 6.12.*; 6.13.5 ≤ 6.13.*
    After
    Linux: 8763cb45ab967a92a5ee49e9c544c0f0ea90e2d6 < 61fa824e304ed162fe965f64999068e6fcff2059, 8763cb45ab967a92a5ee49e9c544c0f0ea90e2d6 < 64397b0cb7c09e3ef3f9f5c7c17299c4eebd3875, 8763cb45ab967a92a5ee49e9c544c0f0ea90e2d6 < 4f52f7c50f5b6f5eeb06823e21fe546d90f9c595, 8763cb45ab967a92a5ee49e9c544c0f0ea90e2d6 < 20fb6fc51863fbff7868de8b5f6d249d2094df1f, 8763cb45ab967a92a5ee49e9c544c0f0ea90e2d6 < 78f579cb7d825134e071a1714d8d0c4fd0ffe459, 8763cb45ab967a92a5ee49e9c544c0f0ea90e2d6 < 3f9240d59e9a95d19f06120bfd1d0e681c6c0ac7, 8763cb45ab967a92a5ee49e9c544c0f0ea90e2d6 < 069dd21ea8262204f94737878389c2815a054a9e, 8763cb45ab967a92a5ee49e9c544c0f0ea90e2d6 < 41cddf83d8b00f29fd105e7a0777366edc69a5cf, 4.14 · Fixed: Linux: < 4.14, 5.4.300 ≤ 5.4.*, 5.10.245 ≤ 5.10.*, 5.15.194 ≤ 5.15.*, 6.1.155 ≤ 6.1.*, 6.6.109 ≤ 6.6.*, 6.12.17 ≤ 6.12.*, 6.13.5 ≤ 6.13.*, 6.14 ≤ *
    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-7599↗Vendor CSAF · Siemens ProductCERT · Siemens SSA-019113↗Patch or update reference↗Patch or update reference↗Patch or update reference↗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-21861 · cve.blacktree.nl