BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-53105High confidence

mm: page_alloc: move mlocked flag clearance into free_pages_prepare()

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 19 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 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.24% 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 19 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.

23 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 19 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.11.10-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.123-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.11.10-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.11.10-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2024-53105 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: mm: page_alloc: move mlocked flag clearance into free_pages_prepare()
42 known affected

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

  • kernel as a component of Red Hat Enterprise Linux 6
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 6
  • kernel-debug as a component of Red Hat Enterprise Linux 6
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 6
  • kernel-devel as a component of Red Hat Enterprise Linux 6
  • kernel-doc as a component of Red Hat Enterprise Linux 6
  • kernel-firmware as a component of Red Hat Enterprise Linux 6
  • kernel-headers as a component of Red Hat Enterprise Linux 6
  • kernel-kdump as a component of Red Hat Enterprise Linux 6
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 6
  • kernel.src as a component of Red Hat Enterprise Linux 6
Summary
A flaw was found in the Linux kernel's memory management subsystem. When certain memory pages are freed while still marked as locked in memory, the kernel detects an inconsistent page state and permanently takes those pages out of service. A local user could exploit this vulnerability through specific memory operations to trigger kernel warnings and cause memory leaks, potentially leading to a denial of service (DoS).
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
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-2024-51777

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 19 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: page_alloc: move mlocked flag clearance into free_pages_prepare() Syzbot reported a bad page state problem caused by a page being freed using free_page() still having a mlocked flag at free_pages_prepare() stage: BUG: Bad page state in process syz.5.504 pfn:61f45 page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x61f45 flags: 0xfff00000080204(referenced|workingset|mlocked|node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000080204 0000000000000000 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: PAGE_FLAGS_CHECK_AT_FREE flag(s) set page_owner tracks the page as allocated page last allocated via order 0, migratetype Unmovable, gfp_mask 0x400dc0(GFP_KERNEL_ACCOUNT|__GFP_ZERO), pid 8443, tgid 8442 (syz.5.504), ts 201884660643, free_ts 201499827394 set_page_owner include/linux/page_owner.h:32 [inline] post_alloc_hook+0x1f3/0x230 mm/page_alloc.c:1537 prep_new_page mm/page_alloc.c:1545 [inline] get_page_from_freelist+0x303f/0x3190 mm/page_alloc.c:3457 __alloc_pages_noprof+0x292/0x710 mm/page_alloc.c:4733 alloc_pages_mpol_noprof+0x3e8/0x680 mm/mempolicy.c:2265 kvm_coalesced_mmio_init+0x1f/0xf0 virt/kvm/coalesced_mmio.c:99 kvm_create_vm virt/kvm/kvm_main.c:1235 [inline] kvm_dev_ioctl_create_vm virt/kvm/kvm_main.c:5488 [inline] kvm_dev_ioctl+0x12dc/0x2240 virt/kvm/kvm_main.c:5530 __do_compat_sys_ioctl fs/ioctl.c:1007 [inline] __se_compat_sys_ioctl+0x510/0xc90 fs/ioctl.c:950 do_syscall_32_irqs_on arch/x86/entry/common.c:165 [inline] __do_fast_syscall_32+0xb4/0x110 arch/x86/entry/common.c:386 do_fast_syscall_32+0x34/0x80 arch/x86/entry/common.c:411 entry_SYSENTER_compat_after_hwframe+0x84/0x8e page last free pid 8399 tgid 8399 stack trace: reset_page_owner include/linux/page_owner.h:25 [inline] free_pages_prepare mm/page_alloc.c:1108 [inline] free_unref_folios+0xf12/0x18d0 mm/page_alloc.c:2686 folios_put_refs+0x76c/0x860 mm/swap.c:1007 free_pages_and_swap_cache+0x5c8/0x690 mm/swap_state.c:335 __tlb_batch_free_encoded_pages mm/mmu_gather.c:136 [inline] tlb_batch_pages_flush mm/mmu_gather.c:149 [inline] tlb_flush_mmu_free mm/mmu_gather.c:366 [inline] tlb_flush_mmu+0x3a3/0x680 mm/mmu_gather.c:373 tlb_finish_mmu+0xd4/0x200 mm/mmu_gather.c:465 exit_mmap+0x496/0xc40 mm/mmap.c:1926 __mmput+0x115/0x390 kernel/fork.c:1348 exit_mm+0x220/0x310 kernel/exit.c:571 do_exit+0x9b2/0x28e0 kernel/exit.c:926 do_group_exit+0x207/0x2c0 kernel/exit.c:1088 __do_sys_exit_group kernel/exit.c:1099 [inline] __se_sys_exit_group kernel/exit.c:1097 [inline] __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1097 x64_sys_call+0x2634/0x2640 arch/x86/include/generated/asm/syscalls_64.h:232 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Modules linked in: CPU: 0 UID: 0 PID: 8442 Comm: syz.5.504 Not tainted 6.12.0-rc6-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 bad_page+0x176/0x1d0 mm/page_alloc.c:501 free_page_is_bad mm/page_alloc.c:918 [inline] free_pages_prepare mm/page_alloc.c:1100 [inline] free_unref_page+0xed0/0xf20 mm/page_alloc.c:2638 kvm_destroy_vm virt/kvm/kvm_main.c:1327 [inline] kvm_put_kvm+0xc75/0x1350 virt/kvm/kvm_main.c:1386 kvm_vcpu_release+0x54/0x60 virt/kvm/kvm_main.c:4143 __fput+0x23f/0x880 fs/file_table.c:431 task_work_run+0x24f/0x310 kernel/task_work.c:239 exit_task_work include/linux/task_work.h:43 [inline] do_exit+0xa2f/0x28e0 kernel/exit.c:939 do_group_exit+0x207/0x2c0 kernel/exit.c:1088 __do_sys_exit_group kernel/exit.c:1099 [in ---truncated---

What

In the Linux kernel, the following vulnerability has been resolved: mm: page_alloc: move mlocked flag clearance into free_pages_prepare() Syzbot reported a bad page state problem caused by a page being freed using free_page() still having a mlocked flag at free_pages_prepare() stage: BUG: Bad page state in process syz.5.504 pfn:61f45 page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x61f45 flags: 0xfff00000080204(referenced|workingset|mlocked|node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000080204 0000000000000000 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: PAGE_FLAGS_CHECK_AT_FREE flag(s) set page_owner tracks the page as allocated page last allocated via order 0, migratetype Unmovable, gfp_mask 0x400dc0(GFP_KERNEL_ACCOUNT|__GFP_ZERO), pid 8443, tgid 8442 (syz.5.504), ts 201884660643, free_ts 201499827394 set_page_owner include/linux/page_owner.h:32 [inline] post_alloc_hook+0x1f3/0x230 mm/page_alloc.c:1537 prep_new_page mm/page_alloc.c:1545 [inline] get_page_from_freelist+0x303f/0x3190 mm/page_alloc.c:3457 __alloc_pages_noprof+0x292/0x710 mm/page_alloc.c:4733 alloc_pages_mpol_noprof+0x3e8/0x680 mm/mempolicy.c:2265 kvm_coalesced_mmio_init+0x1f/0xf0 virt/kvm/coalesced_mmio.c:99 kvm_create_vm virt/kvm/kvm_main.c:1235 [inline] kvm_dev_ioctl_create_vm virt/kvm/kvm_main.c:5488 [inline] kvm_dev_ioctl+0x12dc/0x2240 virt/kvm/kvm_main.c:5530 __do_compat_sys_ioctl fs/ioctl.c:1007 [inline] __se_compat_sys_ioctl+0x510/0xc90 fs/ioctl.c:950 do_syscall_32_irqs_on arch/x86/entry/common.c:165 [inline] __do_fast_syscall_32+0xb4/0x110 arch/x86/entry/common.c:386 do_fast_syscall_32+0x34/0x80 arch/x86/entry/common.c:411 entry_SYSENTER_compat_after_hwframe+0x84/0x8e page last free pid 8399 tgid 8399 stack trace: reset_page_owner include/linux/page_owner.h:25 [inline] free_pages_prepare mm/page_alloc.c:1108 [inline] free_unref_folios+0xf12/0x18d0 mm/page_alloc.c:2686 folios_put_refs+0x76c/0x860 mm/swap.c:1007 free_pages_and_swap_cache+0x5c8/0x690 mm/swap_state.c:335 __tlb_batch_free_encoded_pages mm/mmu_gather.c:136 [inline] tlb_batch_pages_flush mm/mmu_gather.c:149 [inline] tlb_flush_mmu_free mm/mmu_gather.c:366 [inline] tlb_flush_mmu+0x3a3/0x680 mm/mmu_gather.c:373 tlb_finish_mmu+0xd4/0x200 mm/mmu_gather.c:465 exit_mmap+0x496/0xc40 mm/mmap.c:1926 __mmput+0x115/0x390 kernel/fork.c:1348 exit_mm+0x220/0x310 kernel/exit.c:571 do_exit+0x9b2/0x28e0 kernel/exit.c:926 do_group_exit+0x207/0x2c0 kernel/exit.c:1088 __do_sys_exit_group kernel/exit.c:1099 [inline] __se_sys_exit_group kernel/exit.c:1097 [inline] __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1097 x64_sys_call+0x2634/0x2640 arch/x86/include/generated/asm/syscalls_64.h:232 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Modules linked in: CPU: 0 UID: 0 PID: 8442 Comm: syz.5.504 Not tainted 6.12.0-rc6-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 bad_page+0x176/0x1d0 mm/page_alloc.c:501 free_page_is_bad mm/page_alloc.c:918 [inline] free_pages_prepare mm/page_alloc.c:1100 [inline] free_unref_page+0xed0/0xf20 mm/page_alloc.c:2638 kvm_destroy_vm virt/kvm/kvm_main.c:1327 [inline] kvm_put_kvm+0xc75/0x1350 virt/kvm/kvm_main.c:1386 kvm_vcpu_release+0x54/0x60 virt/kvm/kvm_main.c:4143 __fput+0x23f/0x880 fs/file_table.c:431 task_work_run+0x24f/0x310 kernel/task_work.c:239 exit_task_work include/linux/task_work.h:43 [inline] do_exit+0xa2f/0x28e0 kernel/exit.c:939 do_group_exit+0x207/0x2c0 kernel/exit.c:1088 __do_sys_exit_group kernel/exit.c:1099 [in ---truncated---

Why

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

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: page_alloc: move mlocked flag clearance into free_pages_prepare() Syzbot reported a bad page state problem caused by a page being freed using free_page() still having a mlocked flag at free_pages_prepare() stage: BUG: Bad page state in process syz.5.504 pfn:61f45 page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x61f45 flags: 0xfff00000080204(referenced|workingset|mlocked|node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000080204 0000000000000000 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: PAGE_FLAGS_CHECK_AT_FREE flag(s) set page_owner tracks the page as allocated page last allocated via order 0, migratetype Unmovable, gfp_mask 0x400dc0(GFP_KERNEL_ACCOUNT|__GFP_ZERO), pid 8443, tgid 8442 (syz.5.504), ts 201884660643, free_ts 201499827394 set_page_owner include/linux/page_owner.h:32 [inline] post_alloc_hook+0x1f3/0x230 mm/page_alloc.c:1537 prep_new_page mm/page_alloc.c:1545 [inline] get_page_from_freelist+0x303f/0x3190 mm/page_alloc.c:3457 __alloc_pages_noprof+0x292/0x710 mm/page_alloc.c:4733 alloc_pages_mpol_noprof+0x3e8/0x680 mm/mempolicy.c:2265 kvm_coalesced_mmio_init+0x1f/0xf0 virt/kvm/coalesced_mmio.c:99 kvm_create_vm virt/kvm/kvm_main.c:1235 [inline] kvm_dev_ioctl_create_vm virt/kvm/kvm_main.c:5488 [inline] kvm_dev_ioctl+0x12dc/0x2240 virt/kvm/kvm_main.c:5530 __do_compat_sys_ioctl fs/ioctl.c:1007 [inline] __se_compat_sys_ioctl+0x510/0xc90 fs/ioctl.c:950 do_syscall_32_irqs_on arch/x86/entry/common.c:165 [inline] __do_fast_syscall_32+0xb4/0x110 arch/x86/entry/common.c:386 do_fast_syscall_32+0x34/0x80 arch/x86/entry/common.c:411 entry_SYSENTER_compat_after_hwframe+0x84/0x8e page last free pid 8399 tgid 8399 stack trace: reset_page_owner include/linux/page_owner.h:25 [inline] free_pages_prepare mm/page_alloc.c:1108 [inline] free_unref_folios+0xf12/0x18d0 mm/page_alloc.c:2686 folios_put_refs+0x76c/0x860 mm/swap.c:1007 free_pages_and_swap_cache+0x5c8/0x690 mm/swap_state.c:335 __tlb_batch_free_encoded_pages mm/mmu_gather.c:136 [inline] tlb_batch_pages_flush mm/mmu_gather.c:149 [inline] tlb_flush_mmu_free mm/mmu_gather.c:366 [inline] tlb_flush_mmu+0x3a3/0x680 mm/mmu_gather.c:373 tlb_finish_mmu+0xd4/0x200 mm/mmu_gather.c:465 exit_mmap+0x496/0xc40 mm/mmap.c:1926 __mmput+0x115/0x390 kernel/fork.c:1348 exit_mm+0x220/0x310 kernel/exit.c:571 do_exit+0x9b2/0x28e0 kernel/exit.c:926 do_group_exit+0x207/0x2c0 kernel/exit.c:1088 __do_sys_exit_group kernel/exit.c:1099 [inline] __se_sys_exit_group kernel/exit.c:1097 [inline] __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1097 x64_sys_call+0x2634/0x2640 arch/x86/include/generated/asm/syscalls_64.h:232 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Modules linked in: CPU: 0 UID: 0 PID: 8442 Comm: syz.5.504 Not tainted 6.12.0-rc6-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 bad_page+0x176/0x1d0 mm/page_alloc.c:501 free_page_is_bad mm/page_alloc.c:918 [inline] free_pages_prepare mm/page_alloc.c:1100 [inline] free_unref_page+0xed0/0xf20 mm/page_alloc.c:2638 kvm_destroy_vm virt/kvm/kvm_main.c:1327 [inline] kvm_put_kvm+0xc75/0x1350 virt/kvm/kvm_main.c:1386 kvm_vcpu_release+0x54/0x60 virt/kvm/kvm_main.c:4143 __fput+0x23f/0x880 fs/file_table.c:431 task_work_run+0x24f/0x310 kernel/task_work.c:239 exit_task_work include/linux/task_work.h:43 [inline] do_exit+0xa2f/0x28e0 kernel/exit.c:939 do_group_exit+0x207/0x2c0 kernel/exit.c:1088 __do_sys_exit_group kernel/exit.c:1099 [in ---truncated---

Why

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

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 → Missing Release of Memory after Effective Lifetime → 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-401 ↗

CWE-401: Missing Release of Memory after Effective Lifetime. The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

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

Official authority intelligence

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

BSI · German · WID-SEC-2025-2855IBM DataPower Gateway: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM DataPower Gateway ausnutzen, um beliebigen Programmcode auszuführen, Daten zu manipulieren, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand zu verursachen oder andere, nicht spezifizierte Angriffe durchzuführen.

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

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20241204Security Bulletin 04 Dec 2024

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

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

d?id=CVE-2024-53064 Référence CVE CVE-2024-53070 https://www.cve.org/CVERecord?id=CVE-2024-53070 Référence CVE CVE-2024-53072 https://www.cve.org/CVERecord?id=CVE-2024-53072 Référence CVE CVE-2024-53073 https://www.cve.org/CVERecord?id=CVE-2024-53073 Référence CVE CVE-2024-53074 https://www.cve.org/CVERecord?id=CVE-2024-53074 Référence CVE CVE-2024-53082 https://www.cve.org/CVERecord?id=CVE-2024-53082 Référence CVE CVE-2024-53085 https://www.cve.org/CVERecord?id=CVE-2024-53085 Référence CVE CVE-2024-53091 https://www.cve.org/CVERecord?id=CVE-2024-53091 Référence CVE CVE-2024-53097 https://www.cve.org/CVERecord?id=CVE-2024-53097 Référence CVE CVE-2024-53105 https://www.cve.org/CVERecord?id=CVE-2024-53105 Référence CVE CVE-2024-53109 https://www.cve.org/CVERecord?id=CVE-2024-53109 Référence CVE CVE-2024-53110 https://www.cve.org/CVERecord?id=CVE-2024-53110 Référence CVE CVE-2024-53113 https://www.cve.org/CVERecord?id=CVE-2024-53113 Référence CVE CVE-2024-53117 https://www.cve.org/CVERecord?id=CVE-2024-53117 Référence CVE CVE-2024-53118 https://www.cve.org/CVERecord?id=CVE-2024-53118 Référence CVE CVE-2024-53120 https://www.cve.org/CVERecord?id=CVE-2024-53120 Référence CVE CVE-2024-53123 https://www.cve.org/CVERecord?id=CVE-2024-53123 Référence CVE CVE-2024-53134 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53093 Référence CVE CVE-2024-53094 https://www.cve.org/CVERecord?id=CVE-2024-53094 Référence CVE CVE-2024-53095 https://www.cve.org/CVERecord?id=CVE-2024-53095 Référence CVE CVE-2024-53096 https://www.cve.org/CVERecord?id=CVE-2024-53096 Référence CVE CVE-2024-53099 https://www.cve.org/CVERecord?id=CVE-2024-53099 Référence CVE CVE-2024-53100 https://www.cve.org/CVERecord?id=CVE-2024-53100 Référence CVE CVE-2024-53101 https://www.cve.org/CVERecord?id=CVE-2024-53101 Référence CVE CVE-2024-53103 https://www.cve.org/CVERecord?id=CVE-2024-53103 Référence CVE CVE-2024-53104 https://www.cve.org/CVERecord?id=CVE-2024-53104 Référence CVE CVE-2024-53105 https://www.cve.org/CVERecord?id=CVE-2024-53105 Référence CVE CVE-2024-53106 https://www.cve.org/CVERecord?id=CVE-2024-53106 Référence CVE CVE-2024-53107 https://www.cve.org/CVERecord?id=CVE-2024-53107 Référence CVE CVE-2024-53108 https://www.cve.org/CVERecord?id=CVE-2024-53108 Référence CVE CVE-2024-53109 https://www.cve.org/CVERecord?id=CVE-2024-53109 Référence CVE CVE-2024-53110 https://www.cve.org/CVERecord?id=CVE-2024-53110 Référence CVE CVE-2024-53111 https://www.cve.org/CVERecord?id=CVE-2024-53111 Référence CVE CVE-2024-53112 https://www.cve.org/CVERecord?id=CVE-2024-53112 Référence CVE CVE-2024-53113 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53093 Référence CVE CVE-2024-53094 https://www.cve.org/CVERecord?id=CVE-2024-53094 Référence CVE CVE-2024-53095 https://www.cve.org/CVERecord?id=CVE-2024-53095 Référence CVE CVE-2024-53096 https://www.cve.org/CVERecord?id=CVE-2024-53096 Référence CVE CVE-2024-53097 https://www.cve.org/CVERecord?id=CVE-2024-53097 Référence CVE CVE-2024-53099 https://www.cve.org/CVERecord?id=CVE-2024-53099 Référence CVE CVE-2024-53100 https://www.cve.org/CVERecord?id=CVE-2024-53100 Référence CVE CVE-2024-53101 https://www.cve.org/CVERecord?id=CVE-2024-53101 Référence CVE CVE-2024-53104 https://www.cve.org/CVERecord?id=CVE-2024-53104 Référence CVE CVE-2024-53105 https://www.cve.org/CVERecord?id=CVE-2024-53105 Référence CVE CVE-2024-53106 https://www.cve.org/CVERecord?id=CVE-2024-53106 Référence CVE CVE-2024-53107 https://www.cve.org/CVERecord?id=CVE-2024-53107 Référence CVE CVE-2024-53108 https://www.cve.org/CVERecord?id=CVE-2024-53108 Référence CVE CVE-2024-53109 https://www.cve.org/CVERecord?id=CVE-2024-53109 Référence CVE CVE-2024-53110 https://www.cve.org/CVERecord?id=CVE-2024-53110 Référence CVE CVE-2024-53111 https://www.cve.org/CVERecord?id=CVE-2024-53111 Référence CVE CVE-2024-53112 https://www.cve.org/CVERecord?id=CVE-2024-53112 Référence CVE CVE-2024-53113 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53061 Référence CVE CVE-2024-53063 https://www.cve.org/CVERecord?id=CVE-2024-53063 Référence CVE CVE-2024-53066 https://www.cve.org/CVERecord?id=CVE-2024-53066 Référence CVE CVE-2024-53096 https://www.cve.org/CVERecord?id=CVE-2024-53096 Référence CVE CVE-2024-53097 https://www.cve.org/CVERecord?id=CVE-2024-53097 Référence CVE CVE-2024-53099 https://www.cve.org/CVERecord?id=CVE-2024-53099 Référence CVE CVE-2024-53101 https://www.cve.org/CVERecord?id=CVE-2024-53101 Référence CVE CVE-2024-53103 https://www.cve.org/CVERecord?id=CVE-2024-53103 Référence CVE CVE-2024-53104 https://www.cve.org/CVERecord?id=CVE-2024-53104 Référence CVE CVE-2024-53105 https://www.cve.org/CVERecord?id=CVE-2024-53105 Référence CVE CVE-2024-53112 https://www.cve.org/CVERecord?id=CVE-2024-53112 Référence CVE CVE-2024-53119 https://www.cve.org/CVERecord?id=CVE-2024-53119 Référence CVE CVE-2024-53121 https://www.cve.org/CVERecord?id=CVE-2024-53121 Référence CVE CVE-2024-53124 https://www.cve.org/CVERecord?id=CVE-2024-53124 Référence CVE CVE-2024-53125 https://www.cve.org/CVERecord?id=CVE-2024-53125 Référence CVE CVE-2024-53127 https://www.cve.org/CVERecord?id=CVE-2024-53127 Référence CVE CVE-2024-53128 https://www.cve.org/CVERecord?id=CVE-2024-53128 Référence CVE CVE-2024-53130 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53094 Référence CVE CVE-2024-53095 https://www.cve.org/CVERecord?id=CVE-2024-53095 Référence CVE CVE-2024-53097 https://www.cve.org/CVERecord?id=CVE-2024-53097 Référence CVE CVE-2024-53098 https://www.cve.org/CVERecord?id=CVE-2024-53098 Référence CVE CVE-2024-53099 https://www.cve.org/CVERecord?id=CVE-2024-53099 Référence CVE CVE-2024-53100 https://www.cve.org/CVERecord?id=CVE-2024-53100 Référence CVE CVE-2024-53101 https://www.cve.org/CVERecord?id=CVE-2024-53101 Référence CVE CVE-2024-53103 https://www.cve.org/CVERecord?id=CVE-2024-53103 Référence CVE CVE-2024-53104 https://www.cve.org/CVERecord?id=CVE-2024-53104 Référence CVE CVE-2024-53105 https://www.cve.org/CVERecord?id=CVE-2024-53105 Référence CVE CVE-2024-53106 https://www.cve.org/CVERecord?id=CVE-2024-53106 Référence CVE CVE-2024-53107 https://www.cve.org/CVERecord?id=CVE-2024-53107 Référence CVE CVE-2024-53108 https://www.cve.org/CVERecord?id=CVE-2024-53108 Référence CVE CVE-2024-53109 https://www.cve.org/CVERecord?id=CVE-2024-53109 Référence CVE CVE-2024-53110 https://www.cve.org/CVERecord?id=CVE-2024-53110 Référence CVE CVE-2024-53111 https://www.cve.org/CVERecord?id=CVE-2024-53111 Référence CVE CVE-2024-53112 https://www.cve.org/CVERecord?id=CVE-2024-53112 Référence CVE CVE-2024-53113 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53093 Référence CVE CVE-2024-53094 https://www.cve.org/CVERecord?id=CVE-2024-53094 Référence CVE CVE-2024-53095 https://www.cve.org/CVERecord?id=CVE-2024-53095 Référence CVE CVE-2024-53098 https://www.cve.org/CVERecord?id=CVE-2024-53098 Référence CVE CVE-2024-53099 https://www.cve.org/CVERecord?id=CVE-2024-53099 Référence CVE CVE-2024-53100 https://www.cve.org/CVERecord?id=CVE-2024-53100 Référence CVE CVE-2024-53101 https://www.cve.org/CVERecord?id=CVE-2024-53101 Référence CVE CVE-2024-53103 https://www.cve.org/CVERecord?id=CVE-2024-53103 Référence CVE CVE-2024-53104 https://www.cve.org/CVERecord?id=CVE-2024-53104 Référence CVE CVE-2024-53105 https://www.cve.org/CVERecord?id=CVE-2024-53105 Référence CVE CVE-2024-53106 https://www.cve.org/CVERecord?id=CVE-2024-53106 Référence CVE CVE-2024-53107 https://www.cve.org/CVERecord?id=CVE-2024-53107 Référence CVE CVE-2024-53108 https://www.cve.org/CVERecord?id=CVE-2024-53108 Référence CVE CVE-2024-53109 https://www.cve.org/CVERecord?id=CVE-2024-53109 Référence CVE CVE-2024-53110 https://www.cve.org/CVERecord?id=CVE-2024-53110 Référence CVE CVE-2024-53111 https://www.cve.org/CVERecord?id=CVE-2024-53111 Référence CVE CVE-2024-53112 https://www.cve.org/CVERecord?id=CVE-2024-53112 Référence CVE CVE-2024-53113 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53057 Référence CVE CVE-2024-53064 https://www.cve.org/CVERecord?id=CVE-2024-53064 Référence CVE CVE-2024-53072 https://www.cve.org/CVERecord?id=CVE-2024-53072 Référence CVE CVE-2024-53090 https://www.cve.org/CVERecord?id=CVE-2024-53090 Référence CVE CVE-2024-53091 https://www.cve.org/CVERecord?id=CVE-2024-53091 Référence CVE CVE-2024-53095 https://www.cve.org/CVERecord?id=CVE-2024-53095 Référence CVE CVE-2024-53099 https://www.cve.org/CVERecord?id=CVE-2024-53099 Référence CVE CVE-2024-53101 https://www.cve.org/CVERecord?id=CVE-2024-53101 Référence CVE CVE-2024-53103 https://www.cve.org/CVERecord?id=CVE-2024-53103 Référence CVE CVE-2024-53105 https://www.cve.org/CVERecord?id=CVE-2024-53105 Référence CVE CVE-2024-53110 https://www.cve.org/CVERecord?id=CVE-2024-53110 Référence CVE CVE-2024-53111 https://www.cve.org/CVERecord?id=CVE-2024-53111 Référence CVE CVE-2024-53112 https://www.cve.org/CVERecord?id=CVE-2024-53112 Référence CVE CVE-2024-53113 https://www.cve.org/CVERecord?id=CVE-2024-53113 Référence CVE CVE-2024-53114 https://www.cve.org/CVERecord?id=CVE-2024-53114 Référence CVE CVE-2024-53117 https://www.cve.org/CVERecord?id=CVE-2024-53117 Référence CVE CVE-2024-53118 https://www.cve.org/CVERecord?id=CVE-2024-53118 Référence CVE CVE-2024-53119 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53055 Référence CVE CVE-2024-53056 https://www.cve.org/CVERecord?id=CVE-2024-53056 Référence CVE CVE-2024-53064 https://www.cve.org/CVERecord?id=CVE-2024-53064 Référence CVE CVE-2024-53072 https://www.cve.org/CVERecord?id=CVE-2024-53072 Référence CVE CVE-2024-53090 https://www.cve.org/CVERecord?id=CVE-2024-53090 Référence CVE CVE-2024-53095 https://www.cve.org/CVERecord?id=CVE-2024-53095 Référence CVE CVE-2024-53099 https://www.cve.org/CVERecord?id=CVE-2024-53099 Référence CVE CVE-2024-53101 https://www.cve.org/CVERecord?id=CVE-2024-53101 Référence CVE CVE-2024-53103 https://www.cve.org/CVERecord?id=CVE-2024-53103 Référence CVE CVE-2024-53105 https://www.cve.org/CVERecord?id=CVE-2024-53105 Référence CVE CVE-2024-53111 https://www.cve.org/CVERecord?id=CVE-2024-53111 Référence CVE CVE-2024-53113 https://www.cve.org/CVERecord?id=CVE-2024-53113 Référence CVE CVE-2024-53114 https://www.cve.org/CVERecord?id=CVE-2024-53114 Référence CVE CVE-2024-53117 https://www.cve.org/CVERecord?id=CVE-2024-53117 Référence CVE CVE-2024-53118 https://www.cve.org/CVERecord?id=CVE-2024-53118 Référence CVE CVE-2024-53119 https://www.cve.org/CVERecord?id=CVE-2024-53119 Référence CVE CVE-2024-53120 https://www.cve.org/CVERecord?id=CVE-2024-53120 Référence CVE CVE-2024-53122 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-50272 Référence CVE CVE-2024-50278 https://www.cve.org/CVERecord?id=CVE-2024-50278 Référence CVE CVE-2024-50279 https://www.cve.org/CVERecord?id=CVE-2024-50279 Référence CVE CVE-2024-50280 https://www.cve.org/CVERecord?id=CVE-2024-50280 Référence CVE CVE-2024-53050 https://www.cve.org/CVERecord?id=CVE-2024-53050 Référence CVE CVE-2024-53064 https://www.cve.org/CVERecord?id=CVE-2024-53064 Référence CVE CVE-2024-53090 https://www.cve.org/CVERecord?id=CVE-2024-53090 Référence CVE CVE-2024-53099 https://www.cve.org/CVERecord?id=CVE-2024-53099 Référence CVE CVE-2024-53103 https://www.cve.org/CVERecord?id=CVE-2024-53103 Référence CVE CVE-2024-53105 https://www.cve.org/CVERecord?id=CVE-2024-53105 Référence CVE CVE-2024-53111 https://www.cve.org/CVERecord?id=CVE-2024-53111 Référence CVE CVE-2024-53113 https://www.cve.org/CVERecord?id=CVE-2024-53113 Référence CVE CVE-2024-53117 https://www.cve.org/CVERecord?id=CVE-2024-53117 Référence CVE CVE-2024-53118 https://www.cve.org/CVERecord?id=CVE-2024-53118 Référence CVE CVE-2024-53119 https://www.cve.org/CVERecord?id=CVE-2024-53119 Référence CVE CVE-2024-53120 https://www.cve.org/CVERecord?id=CVE-2024-53120 Référence CVE CVE-2024-53122 https://www.cve.org/CVERecord?id=CVE-2024-53122 Référence CVE CVE-2024-53125 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-028169Linux の 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
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 2 Dec 2024 · Last source change 11 May 2026, 20:50 UTC · CWE-401 · Missing Release of Memory after Effective Lifetime

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-2024-51777
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
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 ↗

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

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