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

sched/numa: Fix the potential null pointer dereference in task_numa_work()

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.7-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.11.7-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.11.7-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-50223 · CSAF 2.0 · revision 68 · interimSUSE Product Security TeamCVE-2024-50223
80 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
Summary
In the Linux kernel, the following vulnerability has been resolved: sched/numa: Fix the potential null pointer dereference in task_numa_work() When running stress-ng-vm-segv test, we found a null pointer dereference error in task_numa_work(). Here is the backtrace: [323676.066985] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000020 ...... [323676.067108] CPU: 35 PID: 2694524 Comm: stress-ng-vm-se ...... [323676.067113] pstate: 23401009 (nzCv daif +PAN -UAO +TCO +DIT +SSBS BTYPE=--) [323676.067115] pc : vma_migratable+0x1c/0xd0 [323676.067122] lr : task_numa_work+0x1ec/0x4e0 [323676.067127] sp : ffff8000ada73d20 [323676.067128] x29: ffff8000ada73d20 x28: 0000000000000000 x27: 000000003e89f010 [323676.067130] x26: 0000000000080000 x25: ffff800081b5c0d8 x24: ffff800081b27000 [323676.067133] x23: 0000000000010000 x22: 0000000104d18cc0 x21: ffff0009f7158000 [323676.067135] x20: 0000000000000000 x19: 0000000000000000 x18: ffff8000ada73db8 [323676.067138] x17: 0001400000000000 x16: ffff800080df40b0 x15: 0000000000000035 [323676.067140] x14: ffff8000ada73cc8 x13: 1fffe0017cc72001 x12: ffff8000ada73cc8 [323676.067142] x11: ffff80008001160c x10: ffff000be639000c x9 : ffff8000800f4ba4 [323676.067145] x8 : ffff000810375000 x7 : ffff8000ada73974 x6 : 0000000000000001 [323676.067147] x5 : 0068000b33e26707 x4 : 0000000000000001 x3 : ffff0009f7158000 [323676.067149] x2 : 0000000000000041 x1 : 0000000000004400 x0 : 0000000000000000 [323676.067152] Call trace: [323676.067153] vma_migratable+0x1c/0xd0 [323676.067155] task_numa_work+0x1ec/0x4e0 [323676.067157] task_work_run+0x78/0xd8 [323676.067161] do_notify_resume+0x1ec/0x290 [323676.067163] el0_svc+0x150/0x160 [323676.067167] el0t_64_sync_handler+0xf8/0x128 [323676.067170] el0t_64_sync+0x17c/0x180 [323676.067173] Code: d2888001 910003fd f9000bf3 aa0003f3 (f9401000) [323676.067177] SMP: stopping secondary CPUs [323676.070184] Starting crashdump kernel... stress-ng-vm-segv in stress-ng is used to stress test the SIGSEGV error handling function of the system, which tries to cause a SIGSEGV error on return from unmapping the whole address space of the child process. Normally this program will not cause kernel crashes. But before the munmap system call returns to user mode, a potential task_numa_work() for numa balancing could be added and executed. In this scenario, since the child process has no vma after munmap, the vma_next() in task_numa_work() will return a null pointer even if the vma iterator restarts from 0. Recheck the vma pointer before dereferencing it in task_numa_work().
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

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

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

Official European source

ENISA European Vulnerability Database

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

1 current
ENISA EUVD identifier

EUVD-2024-44725

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: sched/numa: Fix the potential null pointer dereference in task_numa_work() When running stress-ng-vm-segv test, we found a null pointer dereference error in task_numa_work(). Here is the backtrace: [323676.066985] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000020 ...... [323676.067108] CPU: 35 PID: 2694524 Comm: stress-ng-vm-se ...... [323676.067113] pstate: 23401009 (nzCv daif +PAN -UAO +TCO +DIT +SSBS BTYPE=--) [323676.067115] pc : vma_migratable+0x1c/0xd0 [323676.067122] lr : task_numa_work+0x1ec/0x4e0 [323676.067127] sp : ffff8000ada73d20 [323676.067128] x29: ffff8000ada73d20 x28: 0000000000000000 x27: 000000003e89f010 [323676.067130] x26: 0000000000080000 x25: ffff800081b5c0d8 x24: ffff800081b27000 [323676.067133] x23: 0000000000010000 x22: 0000000104d18cc0 x21: ffff0009f7158000 [323676.067135] x20: 0000000000000000 x19: 0000000000000000 x18: ffff8000ada73db8 [323676.067138] x17: 0001400000000000 x16: ffff800080df40b0 x15: 0000000000000035 [323676.067140] x14: ffff8000ada73cc8 x13: 1fffe0017cc72001 x12: ffff8000ada73cc8 [323676.067142] x11: ffff80008001160c x10: ffff000be639000c x9 : ffff8000800f4ba4 [323676.067145] x8 : ffff000810375000 x7 : ffff8000ada73974 x6 : 0000000000000001 [323676.067147] x5 : 0068000b33e26707 x4 : 0000000000000001 x3 : ffff0009f7158000 [323676.067149] x2 : 0000000000000041 x1 : 0000000000004400 x0 : 0000000000000000 [323676.067152] Call trace: [323676.067153] vma_migratable+0x1c/0xd0 [323676.067155] task_numa_work+0x1ec/0x4e0 [323676.067157] task_work_run+0x78/0xd8 [323676.067161] do_notify_resume+0x1ec/0x290 [323676.067163] el0_svc+0x150/0x160 [323676.067167] el0t_64_sync_handler+0xf8/0x128 [323676.067170] el0t_64_sync+0x17c/0x180 [323676.067173] Code: d2888001 910003fd f9000bf3 aa0003f3 (f9401000) [323676.067177] SMP: stopping secondary CPUs [323676.070184] Starting crashdump kernel... stress-ng-vm-segv in stress-ng is used to stress test the SIGSEGV error handling function of the system, which tries to cause a SIGSEGV error on return from unmapping the whole address space of the child process. Normally this program will not cause kernel crashes. But before the munmap system call returns to user mode, a potential task_numa_work() for numa balancing could be added and executed. In this scenario, since the child process has no vma after munmap, the vma_next() in task_numa_work() will return a null pointer even if the vma iterator restarts from 0. Recheck the vma pointer before dereferencing it in task_numa_work().

What

In the Linux kernel, the following vulnerability has been resolved: sched/numa: Fix the potential null pointer dereference in task_numa_work() When running stress-ng-vm-segv test, we found a null pointer dereference error in task_numa_work(). Here is the backtrace: [323676.066985] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000020 ...... [323676.067108] CPU: 35 PID: 2694524 Comm: stress-ng-vm-se ...... [323676.067113] pstate: 23401009 (nzCv daif +PAN -UAO +TCO +DIT +SSBS BTYPE=--) [323676.067115] pc : vma_migratable+0x1c/0xd0 [323676.067122] lr : task_numa_work+0x1ec/0x4e0 [323676.067127] sp : ffff8000ada73d20 [323676.067128] x29: ffff8000ada73d20 x28: 0000000000000000 x27: 000000003e89f010 [323676.067130] x26: 0000000000080000 x25: ffff800081b5c0d8 x24: ffff800081b27000 [323676.067133] x23: 0000000000010000 x22: 0000000104d18cc0 x21: ffff0009f7158000 [323676.067135] x20: 0000000000000000 x19: 0000000000000000 x18: ffff8000ada73db8 [323676.067138] x17: 0001400000000000 x16: ffff800080df40b0 x15: 0000000000000035 [323676.067140] x14: ffff8000ada73cc8 x13: 1fffe0017cc72001 x12: ffff8000ada73cc8 [323676.067142] x11: ffff80008001160c x10: ffff000be639000c x9 : ffff8000800f4ba4 [323676.067145] x8 : ffff000810375000 x7 : ffff8000ada73974 x6 : 0000000000000001 [323676.067147] x5 : 0068000b33e26707 x4 : 0000000000000001 x3 : ffff0009f7158000 [323676.067149] x2 : 0000000000000041 x1 : 0000000000004400 x0 : 0000000000000000 [323676.067152] Call trace: [323676.067153] vma_migratable+0x1c/0xd0 [323676.067155] task_numa_work+0x1ec/0x4e0 [323676.067157] task_work_run+0x78/0xd8 [323676.067161] do_notify_resume+0x1ec/0x290 [323676.067163] el0_svc+0x150/0x160 [323676.067167] el0t_64_sync_handler+0xf8/0x128 [323676.067170] el0t_64_sync+0x17c/0x180 [323676.067173] Code: d2888001 910003fd f9000bf3 aa0003f3 (f9401000) [323676.067177] SMP: stopping secondary CPUs [323676.070184] Starting crashdump kernel... stress-ng-vm-segv in stress-ng is used to stress test the SIGSEGV error handling function of the system, which tries to cause a SIGSEGV error on return from unmapping the whole address space of the child process. Normally this program will not cause kernel crashes. But before the munmap system call returns to user mode, a potential task_numa_work() for numa balancing could be added and executed. In this scenario, since the child process has no vma after munmap, the vma_next() in task_numa_work() will return a null pointer even if the vma iterator restarts from 0. Recheck the vma pointer before dereferencing it in task_numa_work().

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 disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: sched/numa: Fix the potential null pointer dereference in task_numa_work() When running stress-ng-vm-segv test, we found a null pointer dereference error in task_numa_work(). Here is the backtrace: [323676.066985] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000020 ...... [323676.067108] CPU: 35 PID: 2694524 Comm: stress-ng-vm-se ...... [323676.067113] pstate: 23401009 (nzCv daif +PAN -UAO +TCO +DIT +SSBS BTYPE=--) [323676.067115] pc : vma_migratable+0x1c/0xd0 [323676.067122] lr : task_numa_work+0x1ec/0x4e0 [323676.067127] sp : ffff8000ada73d20 [323676.067128] x29: ffff8000ada73d20 x28: 0000000000000000 x27: 000000003e89f010 [323676.067130] x26: 0000000000080000 x25: ffff800081b5c0d8 x24: ffff800081b27000 [323676.067133] x23: 0000000000010000 x22: 0000000104d18cc0 x21: ffff0009f7158000 [323676.067135] x20: 0000000000000000 x19: 0000000000000000 x18: ffff8000ada73db8 [323676.067138] x17: 0001400000000000 x16: ffff800080df40b0 x15: 0000000000000035 [323676.067140] x14: ffff8000ada73cc8 x13: 1fffe0017cc72001 x12: ffff8000ada73cc8 [323676.067142] x11: ffff80008001160c x10: ffff000be639000c x9 : ffff8000800f4ba4 [323676.067145] x8 : ffff000810375000 x7 : ffff8000ada73974 x6 : 0000000000000001 [323676.067147] x5 : 0068000b33e26707 x4 : 0000000000000001 x3 : ffff0009f7158000 [323676.067149] x2 : 0000000000000041 x1 : 0000000000004400 x0 : 0000000000000000 [323676.067152] Call trace: [323676.067153] vma_migratable+0x1c/0xd0 [323676.067155] task_numa_work+0x1ec/0x4e0 [323676.067157] task_work_run+0x78/0xd8 [323676.067161] do_notify_resume+0x1ec/0x290 [323676.067163] el0_svc+0x150/0x160 [323676.067167] el0t_64_sync_handler+0xf8/0x128 [323676.067170] el0t_64_sync+0x17c/0x180 [323676.067173] Code: d2888001 910003fd f9000bf3 aa0003f3 (f9401000) [323676.067177] SMP: stopping secondary CPUs [323676.070184] Starting crashdump kernel... stress-ng-vm-segv in stress-ng is used to stress test the SIGSEGV error handling function of the system, which tries to cause a SIGSEGV error on return from unmapping the whole address space of the child process. Normally this program will not cause kernel crashes. But before the munmap system call returns to user mode, a potential task_numa_work() for numa balancing could be added and executed. In this scenario, since the child process has no vma after munmap, the vma_next() in task_numa_work() will return a null pointer even if the vma iterator restarts from 0. Recheck the vma pointer before dereferencing it in task_numa_work().

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 disrupt the affected service.

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 → disrupt the affected service
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.
Denial of serviceCWE-476
A

Official authority intelligence

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

BSI · German · WID-SEC-2024-3397Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20241113Security Bulletin 13 Nov 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 13 Nov 2024, published on 13 November 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-50172 Référence CVE CVE-2024-50182 https://www.cve.org/CVERecord?id=CVE-2024-50182 Référence CVE CVE-2024-50186 https://www.cve.org/CVERecord?id=CVE-2024-50186 Référence CVE CVE-2024-50189 https://www.cve.org/CVERecord?id=CVE-2024-50189 Référence CVE CVE-2024-50197 https://www.cve.org/CVERecord?id=CVE-2024-50197 Référence CVE CVE-2024-50200 https://www.cve.org/CVERecord?id=CVE-2024-50200 Référence CVE CVE-2024-50207 https://www.cve.org/CVERecord?id=CVE-2024-50207 Référence CVE CVE-2024-50215 https://www.cve.org/CVERecord?id=CVE-2024-50215 Référence CVE CVE-2024-50216 https://www.cve.org/CVERecord?id=CVE-2024-50216 Référence CVE CVE-2024-50223 https://www.cve.org/CVERecord?id=CVE-2024-50223 Référence CVE CVE-2024-50226 https://www.cve.org/CVERecord?id=CVE-2024-50226 Référence CVE CVE-2024-50235 https://www.cve.org/CVERecord?id=CVE-2024-50235 Référence CVE CVE-2024-50250 https://www.cve.org/CVERecord?id=CVE-2024-50250 Référence CVE CVE-2024-50252 https://www.cve.org/CVERecord?id=CVE-2024-50252 Référence CVE CVE-2024-50255 https://www.cve.org/CVERecord?id=CVE-2024-50255 Référence CVE CVE-2024-50259 https://www.cve.org/CVERecord?id=CVE-2024-50259 Référence CVE CVE-2024-50261 https://www.cve.org/CVERecord?id=CVE-2024-50261 Référence CVE CVE-2024-50271 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-2024-49994 Référence CVE CVE-2024-50038 https://www.cve.org/CVERecord?id=CVE-2024-50038 Référence CVE CVE-2024-50056 https://www.cve.org/CVERecord?id=CVE-2024-50056 Référence CVE CVE-2024-50083 https://www.cve.org/CVERecord?id=CVE-2024-50083 Référence CVE CVE-2024-50106 https://www.cve.org/CVERecord?id=CVE-2024-50106 Référence CVE CVE-2024-50126 https://www.cve.org/CVERecord?id=CVE-2024-50126 Référence CVE CVE-2024-50140 https://www.cve.org/CVERecord?id=CVE-2024-50140 Référence CVE CVE-2024-50162 https://www.cve.org/CVERecord?id=CVE-2024-50162 Référence CVE CVE-2024-50163 https://www.cve.org/CVERecord?id=CVE-2024-50163 Référence CVE CVE-2024-50223 https://www.cve.org/CVERecord?id=CVE-2024-50223 Référence CVE CVE-2024-50290 https://www.cve.org/CVERecord?id=CVE-2024-50290 Référence CVE CVE-2024-53057 https://www.cve.org/CVERecord?id=CVE-2024-53057 Référence CVE CVE-2024-53063 https://www.cve.org/CVERecord?id=CVE-2024-53063 Référence CVE CVE-2024-53124 https://www.cve.org/CVERecord?id=CVE-2024-53124 Référence CVE CVE-2024-53135 https://www.cve.org/CVERecord?id=CVE-2024-53135 Référence CVE CVE-2024-53139 https://www.cve.org/CVERecord?id=CVE-2024-53139 Référence CVE CVE-2024-53140 https://www.cve.org/CVERecord?id=CVE-2024-53140 Référence CVE CVE-2024-53163 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-2024-50038 Référence CVE CVE-2024-50056 https://www.cve.org/CVERecord?id=CVE-2024-50056 Référence CVE CVE-2024-50083 https://www.cve.org/CVERecord?id=CVE-2024-50083 Référence CVE CVE-2024-50106 https://www.cve.org/CVERecord?id=CVE-2024-50106 Référence CVE CVE-2024-50126 https://www.cve.org/CVERecord?id=CVE-2024-50126 Référence CVE CVE-2024-50140 https://www.cve.org/CVERecord?id=CVE-2024-50140 Référence CVE CVE-2024-50152 https://www.cve.org/CVERecord?id=CVE-2024-50152 Référence CVE CVE-2024-50162 https://www.cve.org/CVERecord?id=CVE-2024-50162 Référence CVE CVE-2024-50163 https://www.cve.org/CVERecord?id=CVE-2024-50163 Référence CVE CVE-2024-50223 https://www.cve.org/CVERecord?id=CVE-2024-50223 Référence CVE CVE-2024-50290 https://www.cve.org/CVERecord?id=CVE-2024-50290 Référence CVE CVE-2024-50294 https://www.cve.org/CVERecord?id=CVE-2024-50294 Référence CVE CVE-2024-52559 https://www.cve.org/CVERecord?id=CVE-2024-52559 Référence CVE CVE-2024-53057 https://www.cve.org/CVERecord?id=CVE-2024-53057 Référence CVE CVE-2024-53063 https://www.cve.org/CVERecord?id=CVE-2024-53063 Référence CVE CVE-2024-53124 https://www.cve.org/CVERecord?id=CVE-2024-53124 Référence CVE CVE-2024-53135 https://www.cve.org/CVERecord?id=CVE-2024-53135 Référence CVE CVE-2024-53139 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-50208 Référence CVE CVE-2024-50209 https://www.cve.org/CVERecord?id=CVE-2024-50209 Référence CVE CVE-2024-50211 https://www.cve.org/CVERecord?id=CVE-2024-50211 Référence CVE CVE-2024-50215 https://www.cve.org/CVERecord?id=CVE-2024-50215 Référence CVE CVE-2024-50216 https://www.cve.org/CVERecord?id=CVE-2024-50216 Référence CVE CVE-2024-50218 https://www.cve.org/CVERecord?id=CVE-2024-50218 Référence CVE CVE-2024-50220 https://www.cve.org/CVERecord?id=CVE-2024-50220 Référence CVE CVE-2024-50221 https://www.cve.org/CVERecord?id=CVE-2024-50221 Référence CVE CVE-2024-50222 https://www.cve.org/CVERecord?id=CVE-2024-50222 Référence CVE CVE-2024-50223 https://www.cve.org/CVERecord?id=CVE-2024-50223 Référence CVE CVE-2024-50224 https://www.cve.org/CVERecord?id=CVE-2024-50224 Référence CVE CVE-2024-50225 https://www.cve.org/CVERecord?id=CVE-2024-50225 Référence CVE CVE-2024-50226 https://www.cve.org/CVERecord?id=CVE-2024-50226 Référence CVE CVE-2024-50229 https://www.cve.org/CVERecord?id=CVE-2024-50229 Référence CVE CVE-2024-50230 https://www.cve.org/CVERecord?id=CVE-2024-50230 Référence CVE CVE-2024-50231 https://www.cve.org/CVERecord?id=CVE-2024-50231 Référence CVE CVE-2024-50232 https://www.cve.org/CVERecord?id=CVE-2024-50232 Référence CVE CVE-2024-50233 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-50209 Référence CVE CVE-2024-50210 https://www.cve.org/CVERecord?id=CVE-2024-50210 Référence CVE CVE-2024-50211 https://www.cve.org/CVERecord?id=CVE-2024-50211 Référence CVE CVE-2024-50215 https://www.cve.org/CVERecord?id=CVE-2024-50215 Référence CVE CVE-2024-50216 https://www.cve.org/CVERecord?id=CVE-2024-50216 Référence CVE CVE-2024-50218 https://www.cve.org/CVERecord?id=CVE-2024-50218 Référence CVE CVE-2024-50220 https://www.cve.org/CVERecord?id=CVE-2024-50220 Référence CVE CVE-2024-50221 https://www.cve.org/CVERecord?id=CVE-2024-50221 Référence CVE CVE-2024-50222 https://www.cve.org/CVERecord?id=CVE-2024-50222 Référence CVE CVE-2024-50223 https://www.cve.org/CVERecord?id=CVE-2024-50223 Référence CVE CVE-2024-50224 https://www.cve.org/CVERecord?id=CVE-2024-50224 Référence CVE CVE-2024-50225 https://www.cve.org/CVERecord?id=CVE-2024-50225 Référence CVE CVE-2024-50226 https://www.cve.org/CVERecord?id=CVE-2024-50226 Référence CVE CVE-2024-50229 https://www.cve.org/CVERecord?id=CVE-2024-50229 Référence CVE CVE-2024-50230 https://www.cve.org/CVERecord?id=CVE-2024-50230 Référence CVE CVE-2024-50231 https://www.cve.org/CVERecord?id=CVE-2024-50231 Référence CVE CVE-2024-50232 https://www.cve.org/CVERecord?id=CVE-2024-50232 Référence CVE CVE-2024-50233 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-50213 Référence CVE CVE-2024-50214 https://www.cve.org/CVERecord?id=CVE-2024-50214 Référence CVE CVE-2024-50215 https://www.cve.org/CVERecord?id=CVE-2024-50215 Référence CVE CVE-2024-50216 https://www.cve.org/CVERecord?id=CVE-2024-50216 Référence CVE CVE-2024-50217 https://www.cve.org/CVERecord?id=CVE-2024-50217 Référence CVE CVE-2024-50218 https://www.cve.org/CVERecord?id=CVE-2024-50218 Référence CVE CVE-2024-50220 https://www.cve.org/CVERecord?id=CVE-2024-50220 Référence CVE CVE-2024-50221 https://www.cve.org/CVERecord?id=CVE-2024-50221 Référence CVE CVE-2024-50222 https://www.cve.org/CVERecord?id=CVE-2024-50222 Référence CVE CVE-2024-50223 https://www.cve.org/CVERecord?id=CVE-2024-50223 Référence CVE CVE-2024-50224 https://www.cve.org/CVERecord?id=CVE-2024-50224 Référence CVE CVE-2024-50225 https://www.cve.org/CVERecord?id=CVE-2024-50225 Référence CVE CVE-2024-50226 https://www.cve.org/CVERecord?id=CVE-2024-50226 Référence CVE CVE-2024-50227 https://www.cve.org/CVERecord?id=CVE-2024-50227 Référence CVE CVE-2024-50229 https://www.cve.org/CVERecord?id=CVE-2024-50229 Référence CVE CVE-2024-50230 https://www.cve.org/CVERecord?id=CVE-2024-50230 Référence CVE CVE-2024-50231 https://www.cve.org/CVERecord?id=CVE-2024-50231 Référence CVE CVE-2024-50232 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-50213 Référence CVE CVE-2024-50214 https://www.cve.org/CVERecord?id=CVE-2024-50214 Référence CVE CVE-2024-50215 https://www.cve.org/CVERecord?id=CVE-2024-50215 Référence CVE CVE-2024-50216 https://www.cve.org/CVERecord?id=CVE-2024-50216 Référence CVE CVE-2024-50217 https://www.cve.org/CVERecord?id=CVE-2024-50217 Référence CVE CVE-2024-50218 https://www.cve.org/CVERecord?id=CVE-2024-50218 Référence CVE CVE-2024-50220 https://www.cve.org/CVERecord?id=CVE-2024-50220 Référence CVE CVE-2024-50221 https://www.cve.org/CVERecord?id=CVE-2024-50221 Référence CVE CVE-2024-50222 https://www.cve.org/CVERecord?id=CVE-2024-50222 Référence CVE CVE-2024-50223 https://www.cve.org/CVERecord?id=CVE-2024-50223 Référence CVE CVE-2024-50224 https://www.cve.org/CVERecord?id=CVE-2024-50224 Référence CVE CVE-2024-50225 https://www.cve.org/CVERecord?id=CVE-2024-50225 Référence CVE CVE-2024-50226 https://www.cve.org/CVERecord?id=CVE-2024-50226 Référence CVE CVE-2024-50227 https://www.cve.org/CVERecord?id=CVE-2024-50227 Référence CVE CVE-2024-50229 https://www.cve.org/CVERecord?id=CVE-2024-50229 Référence CVE CVE-2024-50230 https://www.cve.org/CVERecord?id=CVE-2024-50230 Référence CVE CVE-2024-50231 https://www.cve.org/CVERecord?id=CVE-2024-50231 Référence CVE CVE-2024-50232 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-012583Linux の 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
Linux: < 6.3, 6.6.60 ≤ 6.6.*, 6.11.7 ≤ 6.11.*, 6.12 ≤ *
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 9 Nov 2024 · Last source change 11 May 2026, 20:47 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-44725
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
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-44725↗Vendor CSAF · SUSE Product Security Team↗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-50223 · cve.blacktree.nl