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

mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

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

Distribution package intelligence

Release-specific package status

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

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 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.5-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.5-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.5-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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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-56611 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM
112 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. A local user can cause a Denial of Service (DoS) by crashing the system during page migration operations. The issue stems from the memory policy subsystem incorrectly assuming an address space contains at least one virtual memory area, resulting in a null pointer dereference when attempting to access non-existent memory mappings.
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-53259

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

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM We currently assume that there is at least one VMA in a MM, which isn't true. So we might end up having find_vma() return NULL, to then de-reference NULL. So properly handle find_vma() returning NULL. This fixes the report: Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN PTI KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 1 UID: 0 PID: 6021 Comm: syz-executor284 Not tainted 6.12.0-rc7-syzkaller-00187-gf868cd251776 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024 RIP: 0010:migrate_to_node mm/mempolicy.c:1090 [inline] RIP: 0010:do_migrate_pages+0x403/0x6f0 mm/mempolicy.c:1194 Code: ... RSP: 0018:ffffc9000375fd08 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffffc9000375fd78 RCX: 0000000000000000 RDX: ffff88807e171300 RSI: dffffc0000000000 RDI: ffff88803390c044 RBP: ffff88807e171428 R08: 0000000000000014 R09: fffffbfff2039ef1 R10: ffffffff901cf78f R11: 0000000000000000 R12: 0000000000000003 R13: ffffc9000375fe90 R14: ffffc9000375fe98 R15: ffffc9000375fdf8 FS: 00005555919e1380(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005555919e1ca8 CR3: 000000007f12a000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> kernel_migrate_pages+0x5b2/0x750 mm/mempolicy.c:1709 __do_sys_migrate_pages mm/mempolicy.c:1727 [inline] __se_sys_migrate_pages mm/mempolicy.c:1723 [inline] __x64_sys_migrate_pages+0x96/0x100 mm/mempolicy.c:1723 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f [akpm@linux-foundation.org: add unlikely()]

What

In the Linux kernel, the following vulnerability has been resolved: mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM We currently assume that there is at least one VMA in a MM, which isn't true. So we might end up having find_vma() return NULL, to then de-reference NULL. So properly handle find_vma() returning NULL. This fixes the report: Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN PTI KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 1 UID: 0 PID: 6021 Comm: syz-executor284 Not tainted 6.12.0-rc7-syzkaller-00187-gf868cd251776 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024 RIP: 0010:migrate_to_node mm/mempolicy.c:1090 [inline] RIP: 0010:do_migrate_pages+0x403/0x6f0 mm/mempolicy.c:1194 Code: ... RSP: 0018:ffffc9000375fd08 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffffc9000375fd78 RCX: 0000000000000000 RDX: ffff88807e171300 RSI: dffffc0000000000 RDI: ffff88803390c044 RBP: ffff88807e171428 R08: 0000000000000014 R09: fffffbfff2039ef1 R10: ffffffff901cf78f R11: 0000000000000000 R12: 0000000000000003 R13: ffffc9000375fe90 R14: ffffc9000375fe98 R15: ffffc9000375fdf8 FS: 00005555919e1380(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005555919e1ca8 CR3: 000000007f12a000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> kernel_migrate_pages+0x5b2/0x750 mm/mempolicy.c:1709 __do_sys_migrate_pages mm/mempolicy.c:1727 [inline] __se_sys_migrate_pages mm/mempolicy.c:1723 [inline] __x64_sys_migrate_pages+0x96/0x100 mm/mempolicy.c:1723 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f [akpm@linux-foundation.org: add unlikely()]

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM We currently assume that there is at least one VMA in a MM, which isn't true. So we might end up having find_vma() return NULL, to then de-reference NULL. So properly handle find_vma() returning NULL. This fixes the report: Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN PTI KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 1 UID: 0 PID: 6021 Comm: syz-executor284 Not tainted 6.12.0-rc7-syzkaller-00187-gf868cd251776 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024 RIP: 0010:migrate_to_node mm/mempolicy.c:1090 [inline] RIP: 0010:do_migrate_pages+0x403/0x6f0 mm/mempolicy.c:1194 Code: ... RSP: 0018:ffffc9000375fd08 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffffc9000375fd78 RCX: 0000000000000000 RDX: ffff88807e171300 RSI: dffffc0000000000 RDI: ffff88803390c044 RBP: ffff88807e171428 R08: 0000000000000014 R09: fffffbfff2039ef1 R10: ffffffff901cf78f R11: 0000000000000000 R12: 0000000000000003 R13: ffffc9000375fe90 R14: ffffc9000375fe98 R15: ffffc9000375fdf8 FS: 00005555919e1380(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005555919e1ca8 CR3: 000000007f12a000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> kernel_migrate_pages+0x5b2/0x750 mm/mempolicy.c:1709 __do_sys_migrate_pages mm/mempolicy.c:1727 [inline] __se_sys_migrate_pages mm/mempolicy.c:1723 [inline] __x64_sys_migrate_pages+0x96/0x100 mm/mempolicy.c:1723 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f [akpm@linux-foundation.org: add unlikely()]

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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 → NULL Pointer Dereference → 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-476 ↗

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

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-476
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-3762Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher beschriebene Effekte zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250101Security Bulletin 01 Jan 2025

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

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

d?id=CVE-2024-56566 Référence CVE CVE-2024-56583 https://www.cve.org/CVERecord?id=CVE-2024-56583 Référence CVE CVE-2024-56584 https://www.cve.org/CVERecord?id=CVE-2024-56584 Référence CVE CVE-2024-56588 https://www.cve.org/CVERecord?id=CVE-2024-56588 Référence CVE CVE-2024-56591 https://www.cve.org/CVERecord?id=CVE-2024-56591 Référence CVE CVE-2024-56592 https://www.cve.org/CVERecord?id=CVE-2024-56592 Référence CVE CVE-2024-56604 https://www.cve.org/CVERecord?id=CVE-2024-56604 Référence CVE CVE-2024-56607 https://www.cve.org/CVERecord?id=CVE-2024-56607 Référence CVE CVE-2024-56609 https://www.cve.org/CVERecord?id=CVE-2024-56609 Référence CVE CVE-2024-56611 https://www.cve.org/CVERecord?id=CVE-2024-56611 Référence CVE CVE-2024-56639 https://www.cve.org/CVERecord?id=CVE-2024-56639 Référence CVE CVE-2024-56641 https://www.cve.org/CVERecord?id=CVE-2024-56641 Référence CVE CVE-2024-56647 https://www.cve.org/CVERecord?id=CVE-2024-56647 Référence CVE CVE-2024-56657 https://www.cve.org/CVERecord?id=CVE-2024-56657 Référence CVE CVE-2024-56660 https://www.cve.org/CVERecord?id=CVE-2024-56660 Référence CVE CVE-2024-56665 https://www.cve.org/CVERecord?id=CVE-2024-56665 Référence CVE CVE-2024-56671 https://www.cve.org/CVERecord?id=CVE-2024-56671 Référence CVE CVE-2024-56674 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56566 Référence CVE CVE-2024-56583 https://www.cve.org/CVERecord?id=CVE-2024-56583 Référence CVE CVE-2024-56584 https://www.cve.org/CVERecord?id=CVE-2024-56584 Référence CVE CVE-2024-56588 https://www.cve.org/CVERecord?id=CVE-2024-56588 Référence CVE CVE-2024-56591 https://www.cve.org/CVERecord?id=CVE-2024-56591 Référence CVE CVE-2024-56592 https://www.cve.org/CVERecord?id=CVE-2024-56592 Référence CVE CVE-2024-56604 https://www.cve.org/CVERecord?id=CVE-2024-56604 Référence CVE CVE-2024-56607 https://www.cve.org/CVERecord?id=CVE-2024-56607 Référence CVE CVE-2024-56609 https://www.cve.org/CVERecord?id=CVE-2024-56609 Référence CVE CVE-2024-56611 https://www.cve.org/CVERecord?id=CVE-2024-56611 Référence CVE CVE-2024-56639 https://www.cve.org/CVERecord?id=CVE-2024-56639 Référence CVE CVE-2024-56641 https://www.cve.org/CVERecord?id=CVE-2024-56641 Référence CVE CVE-2024-56647 https://www.cve.org/CVERecord?id=CVE-2024-56647 Référence CVE CVE-2024-56657 https://www.cve.org/CVERecord?id=CVE-2024-56657 Référence CVE CVE-2024-56660 https://www.cve.org/CVERecord?id=CVE-2024-56660 Référence CVE CVE-2024-56665 https://www.cve.org/CVERecord?id=CVE-2024-56665 Référence CVE CVE-2024-56671 https://www.cve.org/CVERecord?id=CVE-2024-56671 Référence CVE CVE-2024-56674 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-56602 Référence CVE CVE-2024-56603 https://www.cve.org/CVERecord?id=CVE-2024-56603 Référence CVE CVE-2024-56604 https://www.cve.org/CVERecord?id=CVE-2024-56604 Référence CVE CVE-2024-56605 https://www.cve.org/CVERecord?id=CVE-2024-56605 Référence CVE CVE-2024-56606 https://www.cve.org/CVERecord?id=CVE-2024-56606 Référence CVE CVE-2024-56607 https://www.cve.org/CVERecord?id=CVE-2024-56607 Référence CVE CVE-2024-56608 https://www.cve.org/CVERecord?id=CVE-2024-56608 Référence CVE CVE-2024-56609 https://www.cve.org/CVERecord?id=CVE-2024-56609 Référence CVE CVE-2024-56610 https://www.cve.org/CVERecord?id=CVE-2024-56610 Référence CVE CVE-2024-56611 https://www.cve.org/CVERecord?id=CVE-2024-56611 Référence CVE CVE-2024-56613 https://www.cve.org/CVERecord?id=CVE-2024-56613 Référence CVE CVE-2024-56614 https://www.cve.org/CVERecord?id=CVE-2024-56614 Référence CVE CVE-2024-56615 https://www.cve.org/CVERecord?id=CVE-2024-56615 Référence CVE CVE-2024-56616 https://www.cve.org/CVERecord?id=CVE-2024-56616 Référence CVE CVE-2024-56619 https://www.cve.org/CVERecord?id=CVE-2024-56619 Référence CVE CVE-2024-56620 https://www.cve.org/CVERecord?id=CVE-2024-56620 Référence CVE CVE-2024-56621 https://www.cve.org/CVERecord?id=CVE-2024-56621 Référence CVE CVE-2024-56622 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-56602 Référence CVE CVE-2024-56603 https://www.cve.org/CVERecord?id=CVE-2024-56603 Référence CVE CVE-2024-56604 https://www.cve.org/CVERecord?id=CVE-2024-56604 Référence CVE CVE-2024-56605 https://www.cve.org/CVERecord?id=CVE-2024-56605 Référence CVE CVE-2024-56606 https://www.cve.org/CVERecord?id=CVE-2024-56606 Référence CVE CVE-2024-56607 https://www.cve.org/CVERecord?id=CVE-2024-56607 Référence CVE CVE-2024-56608 https://www.cve.org/CVERecord?id=CVE-2024-56608 Référence CVE CVE-2024-56609 https://www.cve.org/CVERecord?id=CVE-2024-56609 Référence CVE CVE-2024-56610 https://www.cve.org/CVERecord?id=CVE-2024-56610 Référence CVE CVE-2024-56611 https://www.cve.org/CVERecord?id=CVE-2024-56611 Référence CVE CVE-2024-56613 https://www.cve.org/CVERecord?id=CVE-2024-56613 Référence CVE CVE-2024-56614 https://www.cve.org/CVERecord?id=CVE-2024-56614 Référence CVE CVE-2024-56615 https://www.cve.org/CVERecord?id=CVE-2024-56615 Référence CVE CVE-2024-56616 https://www.cve.org/CVERecord?id=CVE-2024-56616 Référence CVE CVE-2024-56619 https://www.cve.org/CVERecord?id=CVE-2024-56619 Référence CVE CVE-2024-56620 https://www.cve.org/CVERecord?id=CVE-2024-56620 Référence CVE CVE-2024-56621 https://www.cve.org/CVERecord?id=CVE-2024-56621 Référence CVE CVE-2024-56622 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56602 Référence CVE CVE-2024-56603 https://www.cve.org/CVERecord?id=CVE-2024-56603 Référence CVE CVE-2024-56604 https://www.cve.org/CVERecord?id=CVE-2024-56604 Référence CVE CVE-2024-56605 https://www.cve.org/CVERecord?id=CVE-2024-56605 Référence CVE CVE-2024-56606 https://www.cve.org/CVERecord?id=CVE-2024-56606 Référence CVE CVE-2024-56607 https://www.cve.org/CVERecord?id=CVE-2024-56607 Référence CVE CVE-2024-56608 https://www.cve.org/CVERecord?id=CVE-2024-56608 Référence CVE CVE-2024-56609 https://www.cve.org/CVERecord?id=CVE-2024-56609 Référence CVE CVE-2024-56610 https://www.cve.org/CVERecord?id=CVE-2024-56610 Référence CVE CVE-2024-56611 https://www.cve.org/CVERecord?id=CVE-2024-56611 Référence CVE CVE-2024-56613 https://www.cve.org/CVERecord?id=CVE-2024-56613 Référence CVE CVE-2024-56614 https://www.cve.org/CVERecord?id=CVE-2024-56614 Référence CVE CVE-2024-56615 https://www.cve.org/CVERecord?id=CVE-2024-56615 Référence CVE CVE-2024-56616 https://www.cve.org/CVERecord?id=CVE-2024-56616 Référence CVE CVE-2024-56617 https://www.cve.org/CVERecord?id=CVE-2024-56617 Référence CVE CVE-2024-56618 https://www.cve.org/CVERecord?id=CVE-2024-56618 Référence CVE CVE-2024-56619 https://www.cve.org/CVERecord?id=CVE-2024-56619 Référence CVE CVE-2024-56620 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56601 Référence CVE CVE-2024-56602 https://www.cve.org/CVERecord?id=CVE-2024-56602 Référence CVE CVE-2024-56603 https://www.cve.org/CVERecord?id=CVE-2024-56603 Référence CVE CVE-2024-56605 https://www.cve.org/CVERecord?id=CVE-2024-56605 Référence CVE CVE-2024-56606 https://www.cve.org/CVERecord?id=CVE-2024-56606 Référence CVE CVE-2024-56607 https://www.cve.org/CVERecord?id=CVE-2024-56607 Référence CVE CVE-2024-56608 https://www.cve.org/CVERecord?id=CVE-2024-56608 Référence CVE CVE-2024-56609 https://www.cve.org/CVERecord?id=CVE-2024-56609 Référence CVE CVE-2024-56610 https://www.cve.org/CVERecord?id=CVE-2024-56610 Référence CVE CVE-2024-56611 https://www.cve.org/CVERecord?id=CVE-2024-56611 Référence CVE CVE-2024-56614 https://www.cve.org/CVERecord?id=CVE-2024-56614 Référence CVE CVE-2024-56615 https://www.cve.org/CVERecord?id=CVE-2024-56615 Référence CVE CVE-2024-56616 https://www.cve.org/CVERecord?id=CVE-2024-56616 Référence CVE CVE-2024-56617 https://www.cve.org/CVERecord?id=CVE-2024-56617 Référence CVE CVE-2024-56619 https://www.cve.org/CVERecord?id=CVE-2024-56619 Référence CVE CVE-2024-56620 https://www.cve.org/CVERecord?id=CVE-2024-56620 Référence CVE CVE-2024-56622 https://www.cve.org/CVERecord?id=CVE-2024-56622 Référence CVE CVE-2024-56623 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56601 Référence CVE CVE-2024-56602 https://www.cve.org/CVERecord?id=CVE-2024-56602 Référence CVE CVE-2024-56603 https://www.cve.org/CVERecord?id=CVE-2024-56603 Référence CVE CVE-2024-56605 https://www.cve.org/CVERecord?id=CVE-2024-56605 Référence CVE CVE-2024-56606 https://www.cve.org/CVERecord?id=CVE-2024-56606 Référence CVE CVE-2024-56607 https://www.cve.org/CVERecord?id=CVE-2024-56607 Référence CVE CVE-2024-56608 https://www.cve.org/CVERecord?id=CVE-2024-56608 Référence CVE CVE-2024-56609 https://www.cve.org/CVERecord?id=CVE-2024-56609 Référence CVE CVE-2024-56610 https://www.cve.org/CVERecord?id=CVE-2024-56610 Référence CVE CVE-2024-56611 https://www.cve.org/CVERecord?id=CVE-2024-56611 Référence CVE CVE-2024-56614 https://www.cve.org/CVERecord?id=CVE-2024-56614 Référence CVE CVE-2024-56615 https://www.cve.org/CVERecord?id=CVE-2024-56615 Référence CVE CVE-2024-56616 https://www.cve.org/CVERecord?id=CVE-2024-56616 Référence CVE CVE-2024-56617 https://www.cve.org/CVERecord?id=CVE-2024-56617 Référence CVE CVE-2024-56619 https://www.cve.org/CVERecord?id=CVE-2024-56619 Référence CVE CVE-2024-56620 https://www.cve.org/CVERecord?id=CVE-2024-56620 Référence CVE CVE-2024-56622 https://www.cve.org/CVERecord?id=CVE-2024-56622 Référence CVE CVE-2024-56623 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2024-56599 Référence CVE CVE-2024-5660 https://www.cve.org/CVERecord?id=CVE-2024-5660 Référence CVE CVE-2024-56602 https://www.cve.org/CVERecord?id=CVE-2024-56602 Référence CVE CVE-2024-56603 https://www.cve.org/CVERecord?id=CVE-2024-56603 Référence CVE CVE-2024-56604 https://www.cve.org/CVERecord?id=CVE-2024-56604 Référence CVE CVE-2024-56605 https://www.cve.org/CVERecord?id=CVE-2024-56605 Référence CVE CVE-2024-56606 https://www.cve.org/CVERecord?id=CVE-2024-56606 Référence CVE CVE-2024-56607 https://www.cve.org/CVERecord?id=CVE-2024-56607 Référence CVE CVE-2024-56609 https://www.cve.org/CVERecord?id=CVE-2024-56609 Référence CVE CVE-2024-56611 https://www.cve.org/CVERecord?id=CVE-2024-56611 Référence CVE CVE-2024-56614 https://www.cve.org/CVERecord?id=CVE-2024-56614 Référence CVE CVE-2024-56615 https://www.cve.org/CVERecord?id=CVE-2024-56615 Référence CVE CVE-2024-56616 https://www.cve.org/CVERecord?id=CVE-2024-56616 Référence CVE CVE-2024-56617 https://www.cve.org/CVERecord?id=CVE-2024-56617 Référence CVE CVE-2024-56619 https://www.cve.org/CVERecord?id=CVE-2024-56619 Référence CVE CVE-2024-56620 https://www.cve.org/CVERecord?id=CVE-2024-56620 Référence CVE CVE-2024-56622 https://www.cve.org/CVERecord?id=CVE-2024-56622 Référence CVE CVE-2024-56623 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-015761Linux の Linux Kernel における NULL ポインタデリファレンスに関する脆弱性

Linux の Linux Kernel には、NULL ポインタデリファレンスに関する脆弱性が存在します。

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 27 Dec 2024 · Last source change 11 May 2026, 20:55 UTC · CWE-476 · NULL Pointer Dereference

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-53259
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-53259↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor 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-56611 · cve.blacktree.nl