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

zram: fix NULL pointer in comp_algorithm_show()

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.22% 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.12.3-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.12.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.3-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.

2 current
CVE-2024-53222 · CSAF 2.0 · revision 77 · interimSUSE Product Security TeamCVE-2024-53222
19 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Live Patching 15 SP6
  • kernel-default-livepatch as component of SUSE Linux Enterprise Live Patching 15 SP6
  • kernel-default-livepatch-devel as component of SUSE Linux Enterprise Live Patching 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Live Patching 15 SP6
  • SLES 15 SP1 CHOST Images for Amazon EC2
  • SLES 15 SP2 CHOST Images for Amazon EC2
  • SLES 15 SP3 CHOST Images for Amazon EC2
  • SLES 15 SP4 CHOST Images for Amazon EC2
  • SLES 15 SP5 CHOST Images for Amazon EC2
  • SLES 15 SP1 CHOST Images for Google
  • SLES 15 SP2 CHOST Images for Google
  • SLES 15 SP3 CHOST Images for Google
Summary
In the Linux kernel, the following vulnerability has been resolved: zram: fix NULL pointer in comp_algorithm_show() LTP reported a NULL pointer dereference as followed: CPU: 7 UID: 0 PID: 5995 Comm: cat Kdump: loaded Not tainted 6.12.0-rc6+ #3 Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 pstate: 40400005 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __pi_strcmp+0x24/0x140 lr : zcomp_available_show+0x60/0x100 [zram] sp : ffff800088b93b90 x29: ffff800088b93b90 x28: 0000000000000001 x27: 0000000000400cc0 x26: 0000000000000ffe x25: ffff80007b3e2388 x24: 0000000000000000 x23: ffff80007b3e2390 x22: ffff0004041a9000 x21: ffff80007b3e2900 x20: 0000000000000000 x19: 0000000000000000 x18: 0000000000000000 x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000 x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000 x11: 0000000000000000 x10: ffff80007b3e2900 x9 : ffff80007b3cb280 x8 : 0101010101010101 x7 : 0000000000000000 x6 : 0000000000000000 x5 : 0000000000000040 x4 : 0000000000000000 x3 : 00656c722d6f7a6c x2 : 0000000000000000 x1 : ffff80007b3e2900 x0 : 0000000000000000 Call trace: __pi_strcmp+0x24/0x140 comp_algorithm_show+0x40/0x70 [zram] dev_attr_show+0x28/0x80 sysfs_kf_seq_show+0x90/0x140 kernfs_seq_show+0x34/0x48 seq_read_iter+0x1d4/0x4e8 kernfs_fop_read_iter+0x40/0x58 new_sync_read+0x9c/0x168 vfs_read+0x1a8/0x1f8 ksys_read+0x74/0x108 __arm64_sys_read+0x24/0x38 invoke_syscall+0x50/0x120 el0_svc_common.constprop.0+0xc8/0xf0 do_el0_svc+0x24/0x38 el0_svc+0x38/0x138 el0t_64_sync_handler+0xc0/0xc8 el0t_64_sync+0x188/0x190 The zram->comp_algs[ZRAM_PRIMARY_COMP] can be NULL in zram_add() if comp_algorithm_set() has not been called. User can access the zram device by sysfs after device_add_disk(), so there is a time window to trigger the NULL pointer dereference. Move it ahead device_add_disk() to make sure when user can access the zram device, it is ready. comp_algorithm_set() is protected by zram->init_lock in other places and no such problem.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2024-53222 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: zram: fix NULL pointer in comp_algorithm_show()
50 known affected

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

  • bpftool as a component of Red Hat Enterprise Linux 7
  • kernel as a component of Red Hat Enterprise Linux 7
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 7
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 7
  • kernel-debug as a component of Red Hat Enterprise Linux 7
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 7
  • kernel-devel as a component of Red Hat Enterprise Linux 7
  • kernel-doc as a component of Red Hat Enterprise Linux 7
  • kernel-headers as a component of Red Hat Enterprise Linux 7
  • kernel-kdump as a component of Red Hat Enterprise Linux 7
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 7
  • kernel-rt as a component of Red Hat Enterprise Linux 7
Summary
A flaw was found in the Linux kernel's zram driver. This vulnerability can lead to a Denial of Service (DoS) by causing a system crash. During device initialization, a timing window allows a local user to access the device attributes through the sysfs interface before compression algorithms are properly initialized, triggering a NULL pointer dereference.
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-51894

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: zram: fix NULL pointer in comp_algorithm_show() LTP reported a NULL pointer dereference as followed: CPU: 7 UID: 0 PID: 5995 Comm: cat Kdump: loaded Not tainted 6.12.0-rc6+ #3 Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 pstate: 40400005 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __pi_strcmp+0x24/0x140 lr : zcomp_available_show+0x60/0x100 [zram] sp : ffff800088b93b90 x29: ffff800088b93b90 x28: 0000000000000001 x27: 0000000000400cc0 x26: 0000000000000ffe x25: ffff80007b3e2388 x24: 0000000000000000 x23: ffff80007b3e2390 x22: ffff0004041a9000 x21: ffff80007b3e2900 x20: 0000000000000000 x19: 0000000000000000 x18: 0000000000000000 x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000 x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000 x11: 0000000000000000 x10: ffff80007b3e2900 x9 : ffff80007b3cb280 x8 : 0101010101010101 x7 : 0000000000000000 x6 : 0000000000000000 x5 : 0000000000000040 x4 : 0000000000000000 x3 : 00656c722d6f7a6c x2 : 0000000000000000 x1 : ffff80007b3e2900 x0 : 0000000000000000 Call trace: __pi_strcmp+0x24/0x140 comp_algorithm_show+0x40/0x70 [zram] dev_attr_show+0x28/0x80 sysfs_kf_seq_show+0x90/0x140 kernfs_seq_show+0x34/0x48 seq_read_iter+0x1d4/0x4e8 kernfs_fop_read_iter+0x40/0x58 new_sync_read+0x9c/0x168 vfs_read+0x1a8/0x1f8 ksys_read+0x74/0x108 __arm64_sys_read+0x24/0x38 invoke_syscall+0x50/0x120 el0_svc_common.constprop.0+0xc8/0xf0 do_el0_svc+0x24/0x38 el0_svc+0x38/0x138 el0t_64_sync_handler+0xc0/0xc8 el0t_64_sync+0x188/0x190 The zram->comp_algs[ZRAM_PRIMARY_COMP] can be NULL in zram_add() if comp_algorithm_set() has not been called. User can access the zram device by sysfs after device_add_disk(), so there is a time window to trigger the NULL pointer dereference. Move it ahead device_add_disk() to make sure when user can access the zram device, it is ready. comp_algorithm_set() is protected by zram->init_lock in other places and no such problem.

What

In the Linux kernel, the following vulnerability has been resolved: zram: fix NULL pointer in comp_algorithm_show() LTP reported a NULL pointer dereference as followed: CPU: 7 UID: 0 PID: 5995 Comm: cat Kdump: loaded Not tainted 6.12.0-rc6+ #3 Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 pstate: 40400005 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __pi_strcmp+0x24/0x140 lr : zcomp_available_show+0x60/0x100 [zram] sp : ffff800088b93b90 x29: ffff800088b93b90 x28: 0000000000000001 x27: 0000000000400cc0 x26: 0000000000000ffe x25: ffff80007b3e2388 x24: 0000000000000000 x23: ffff80007b3e2390 x22: ffff0004041a9000 x21: ffff80007b3e2900 x20: 0000000000000000 x19: 0000000000000000 x18: 0000000000000000 x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000 x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000 x11: 0000000000000000 x10: ffff80007b3e2900 x9 : ffff80007b3cb280 x8 : 0101010101010101 x7 : 0000000000000000 x6 : 0000000000000000 x5 : 0000000000000040 x4 : 0000000000000000 x3 : 00656c722d6f7a6c x2 : 0000000000000000 x1 : ffff80007b3e2900 x0 : 0000000000000000 Call trace: __pi_strcmp+0x24/0x140 comp_algorithm_show+0x40/0x70 [zram] dev_attr_show+0x28/0x80 sysfs_kf_seq_show+0x90/0x140 kernfs_seq_show+0x34/0x48 seq_read_iter+0x1d4/0x4e8 kernfs_fop_read_iter+0x40/0x58 new_sync_read+0x9c/0x168 vfs_read+0x1a8/0x1f8 ksys_read+0x74/0x108 __arm64_sys_read+0x24/0x38 invoke_syscall+0x50/0x120 el0_svc_common.constprop.0+0xc8/0xf0 do_el0_svc+0x24/0x38 el0_svc+0x38/0x138 el0t_64_sync_handler+0xc0/0xc8 el0t_64_sync+0x188/0x190 The zram->comp_algs[ZRAM_PRIMARY_COMP] can be NULL in zram_add() if comp_algorithm_set() has not been called. User can access the zram device by sysfs after device_add_disk(), so there is a time window to trigger the NULL pointer dereference. Move it ahead device_add_disk() to make sure when user can access the zram device, it is ready. comp_algorithm_set() is protected by zram->init_lock in other places and no such problem.

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: zram: fix NULL pointer in comp_algorithm_show() LTP reported a NULL pointer dereference as followed: CPU: 7 UID: 0 PID: 5995 Comm: cat Kdump: loaded Not tainted 6.12.0-rc6+ #3 Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 pstate: 40400005 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __pi_strcmp+0x24/0x140 lr : zcomp_available_show+0x60/0x100 [zram] sp : ffff800088b93b90 x29: ffff800088b93b90 x28: 0000000000000001 x27: 0000000000400cc0 x26: 0000000000000ffe x25: ffff80007b3e2388 x24: 0000000000000000 x23: ffff80007b3e2390 x22: ffff0004041a9000 x21: ffff80007b3e2900 x20: 0000000000000000 x19: 0000000000000000 x18: 0000000000000000 x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000 x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000 x11: 0000000000000000 x10: ffff80007b3e2900 x9 : ffff80007b3cb280 x8 : 0101010101010101 x7 : 0000000000000000 x6 : 0000000000000000 x5 : 0000000000000040 x4 : 0000000000000000 x3 : 00656c722d6f7a6c x2 : 0000000000000000 x1 : ffff80007b3e2900 x0 : 0000000000000000 Call trace: __pi_strcmp+0x24/0x140 comp_algorithm_show+0x40/0x70 [zram] dev_attr_show+0x28/0x80 sysfs_kf_seq_show+0x90/0x140 kernfs_seq_show+0x34/0x48 seq_read_iter+0x1d4/0x4e8 kernfs_fop_read_iter+0x40/0x58 new_sync_read+0x9c/0x168 vfs_read+0x1a8/0x1f8 ksys_read+0x74/0x108 __arm64_sys_read+0x24/0x38 invoke_syscall+0x50/0x120 el0_svc_common.constprop.0+0xc8/0xf0 do_el0_svc+0x24/0x38 el0_svc+0x38/0x138 el0t_64_sync_handler+0xc0/0xc8 el0t_64_sync+0x188/0x190 The zram->comp_algs[ZRAM_PRIMARY_COMP] can be NULL in zram_add() if comp_algorithm_set() has not been called. User can access the zram device by sysfs after device_add_disk(), so there is a time window to trigger the NULL pointer dereference. Move it ahead device_add_disk() to make sure when user can access the zram device, it is ready. comp_algorithm_set() is protected by zram->init_lock in other places and no such problem.

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-2025-AVI-1057Multiples vulnérabilités dans les produits VMware

d?id=CVE-2024-53178 Référence CVE CVE-2024-53185 https://www.cve.org/CVERecord?id=CVE-2024-53185 Référence CVE CVE-2024-53189 https://www.cve.org/CVERecord?id=CVE-2024-53189 Référence CVE CVE-2024-53202 https://www.cve.org/CVERecord?id=CVE-2024-53202 Référence CVE CVE-2024-53206 https://www.cve.org/CVERecord?id=CVE-2024-53206 Référence CVE CVE-2024-53207 https://www.cve.org/CVERecord?id=CVE-2024-53207 Référence CVE CVE-2024-53208 https://www.cve.org/CVERecord?id=CVE-2024-53208 Référence CVE CVE-2024-53213 https://www.cve.org/CVERecord?id=CVE-2024-53213 Référence CVE CVE-2024-53215 https://www.cve.org/CVERecord?id=CVE-2024-53215 Référence CVE CVE-2024-53222 https://www.cve.org/CVERecord?id=CVE-2024-53222 Référence CVE CVE-2024-53225 https://www.cve.org/CVERecord?id=CVE-2024-53225 Référence CVE CVE-2024-53229 https://www.cve.org/CVERecord?id=CVE-2024-53229 Référence CVE CVE-2024-53230 https://www.cve.org/CVERecord?id=CVE-2024-53230 Référence CVE CVE-2024-53231 https://www.cve.org/CVERecord?id=CVE-2024-53231 Référence CVE CVE-2024-53232 https://www.cve.org/CVERecord?id=CVE-2024-53232 Référence CVE CVE-2024-53236 https://www.cve.org/CVERecord?id=CVE-2024-53236 Référence CVE CVE-2024-53238 https://www.cve.org/CVERecord?id=CVE-2024-53238 Référence CVE CVE-2024-53681 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46812 Référence CVE CVE-2024-46821 https://www.cve.org/CVERecord?id=CVE-2024-46821 Référence CVE CVE-2024-49958 https://www.cve.org/CVERecord?id=CVE-2024-49958 Référence CVE CVE-2024-50047 https://www.cve.org/CVERecord?id=CVE-2024-50047 Référence CVE CVE-2024-50116 https://www.cve.org/CVERecord?id=CVE-2024-50116 Référence CVE CVE-2024-53051 https://www.cve.org/CVERecord?id=CVE-2024-53051 Référence CVE CVE-2024-53144 https://www.cve.org/CVERecord?id=CVE-2024-53144 Référence CVE CVE-2024-53171 https://www.cve.org/CVERecord?id=CVE-2024-53171 Référence CVE CVE-2024-53197 https://www.cve.org/CVERecord?id=CVE-2024-53197 Référence CVE CVE-2024-53222 https://www.cve.org/CVERecord?id=CVE-2024-53222 Référence CVE CVE-2024-56551 https://www.cve.org/CVERecord?id=CVE-2024-56551 Référence CVE CVE-2024-56596 https://www.cve.org/CVERecord?id=CVE-2024-56596 Référence CVE CVE-2024-56608 https://www.cve.org/CVERecord?id=CVE-2024-56608 Référence CVE CVE-2024-56662 https://www.cve.org/CVERecord?id=CVE-2024-56662 Référence CVE CVE-2024-56664 https://www.cve.org/CVERecord?id=CVE-2024-56664 Référence CVE CVE-2024-57850 https://www.cve.org/CVERecord?id=CVE-2024-57850 Référence CVE CVE-2024-58092 https://www.cve.org/CVERecord?id=CVE-2024-58092 Référence CVE CVE-2024-58093 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-49958 Référence CVE CVE-2024-50047 https://www.cve.org/CVERecord?id=CVE-2024-50047 Référence CVE CVE-2024-50116 https://www.cve.org/CVERecord?id=CVE-2024-50116 Référence CVE CVE-2024-50157 https://www.cve.org/CVERecord?id=CVE-2024-50157 Référence CVE CVE-2024-53051 https://www.cve.org/CVERecord?id=CVE-2024-53051 Référence CVE CVE-2024-53124 https://www.cve.org/CVERecord?id=CVE-2024-53124 Référence CVE CVE-2024-53144 https://www.cve.org/CVERecord?id=CVE-2024-53144 Référence CVE CVE-2024-53168 https://www.cve.org/CVERecord?id=CVE-2024-53168 Référence CVE CVE-2024-53197 https://www.cve.org/CVERecord?id=CVE-2024-53197 Référence CVE CVE-2024-53222 https://www.cve.org/CVERecord?id=CVE-2024-53222 Référence CVE CVE-2024-56551 https://www.cve.org/CVERecord?id=CVE-2024-56551 Référence CVE CVE-2024-56599 https://www.cve.org/CVERecord?id=CVE-2024-56599 Référence CVE CVE-2024-56608 https://www.cve.org/CVERecord?id=CVE-2024-56608 Référence CVE CVE-2024-56664 https://www.cve.org/CVERecord?id=CVE-2024-56664 Référence CVE CVE-2024-56721 https://www.cve.org/CVERecord?id=CVE-2024-56721 Référence CVE CVE-2024-57834 https://www.cve.org/CVERecord?id=CVE-2024-57834 Référence CVE CVE-2024-57924 https://www.cve.org/CVERecord?id=CVE-2024-57924 Référence CVE CVE-2024-57948 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-53210 Référence CVE CVE-2024-53213 https://www.cve.org/CVERecord?id=CVE-2024-53213 Référence CVE CVE-2024-53214 https://www.cve.org/CVERecord?id=CVE-2024-53214 Référence CVE CVE-2024-53215 https://www.cve.org/CVERecord?id=CVE-2024-53215 Référence CVE CVE-2024-53217 https://www.cve.org/CVERecord?id=CVE-2024-53217 Référence CVE CVE-2024-53218 https://www.cve.org/CVERecord?id=CVE-2024-53218 Référence CVE CVE-2024-53219 https://www.cve.org/CVERecord?id=CVE-2024-53219 Référence CVE CVE-2024-53220 https://www.cve.org/CVERecord?id=CVE-2024-53220 Référence CVE CVE-2024-53221 https://www.cve.org/CVERecord?id=CVE-2024-53221 Référence CVE CVE-2024-53222 https://www.cve.org/CVERecord?id=CVE-2024-53222 Référence CVE CVE-2024-53223 https://www.cve.org/CVERecord?id=CVE-2024-53223 Référence CVE CVE-2024-53224 https://www.cve.org/CVERecord?id=CVE-2024-53224 Référence CVE CVE-2024-53226 https://www.cve.org/CVERecord?id=CVE-2024-53226 Référence CVE CVE-2024-53227 https://www.cve.org/CVERecord?id=CVE-2024-53227 Référence CVE CVE-2024-53228 https://www.cve.org/CVERecord?id=CVE-2024-53228 Référence CVE CVE-2024-53229 https://www.cve.org/CVERecord?id=CVE-2024-53229 Référence CVE CVE-2024-53230 https://www.cve.org/CVERecord?id=CVE-2024-53230 Référence CVE CVE-2024-53231 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-53210 Référence CVE CVE-2024-53213 https://www.cve.org/CVERecord?id=CVE-2024-53213 Référence CVE CVE-2024-53214 https://www.cve.org/CVERecord?id=CVE-2024-53214 Référence CVE CVE-2024-53215 https://www.cve.org/CVERecord?id=CVE-2024-53215 Référence CVE CVE-2024-53217 https://www.cve.org/CVERecord?id=CVE-2024-53217 Référence CVE CVE-2024-53218 https://www.cve.org/CVERecord?id=CVE-2024-53218 Référence CVE CVE-2024-53219 https://www.cve.org/CVERecord?id=CVE-2024-53219 Référence CVE CVE-2024-53220 https://www.cve.org/CVERecord?id=CVE-2024-53220 Référence CVE CVE-2024-53221 https://www.cve.org/CVERecord?id=CVE-2024-53221 Référence CVE CVE-2024-53222 https://www.cve.org/CVERecord?id=CVE-2024-53222 Référence CVE CVE-2024-53223 https://www.cve.org/CVERecord?id=CVE-2024-53223 Référence CVE CVE-2024-53224 https://www.cve.org/CVERecord?id=CVE-2024-53224 Référence CVE CVE-2024-53226 https://www.cve.org/CVERecord?id=CVE-2024-53226 Référence CVE CVE-2024-53227 https://www.cve.org/CVERecord?id=CVE-2024-53227 Référence CVE CVE-2024-53228 https://www.cve.org/CVERecord?id=CVE-2024-53228 Référence CVE CVE-2024-53229 https://www.cve.org/CVERecord?id=CVE-2024-53229 Référence CVE CVE-2024-53230 https://www.cve.org/CVERecord?id=CVE-2024-53230 Référence CVE CVE-2024-53231 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-53207 Référence CVE CVE-2024-53208 https://www.cve.org/CVERecord?id=CVE-2024-53208 Référence CVE CVE-2024-53209 https://www.cve.org/CVERecord?id=CVE-2024-53209 Référence CVE CVE-2024-53210 https://www.cve.org/CVERecord?id=CVE-2024-53210 Référence CVE CVE-2024-53213 https://www.cve.org/CVERecord?id=CVE-2024-53213 Référence CVE CVE-2024-53214 https://www.cve.org/CVERecord?id=CVE-2024-53214 Référence CVE CVE-2024-53215 https://www.cve.org/CVERecord?id=CVE-2024-53215 Référence CVE CVE-2024-53216 https://www.cve.org/CVERecord?id=CVE-2024-53216 Référence CVE CVE-2024-53217 https://www.cve.org/CVERecord?id=CVE-2024-53217 Référence CVE CVE-2024-53222 https://www.cve.org/CVERecord?id=CVE-2024-53222 Référence CVE CVE-2024-53224 https://www.cve.org/CVERecord?id=CVE-2024-53224 Référence CVE CVE-2024-53227 https://www.cve.org/CVERecord?id=CVE-2024-53227 Référence CVE CVE-2024-53229 https://www.cve.org/CVERecord?id=CVE-2024-53229 Référence CVE CVE-2024-53230 https://www.cve.org/CVERecord?id=CVE-2024-53230 Référence CVE CVE-2024-53231 https://www.cve.org/CVERecord?id=CVE-2024-53231 Référence CVE CVE-2024-53232 https://www.cve.org/CVERecord?id=CVE-2024-53232 Référence CVE CVE-2024-53233 https://www.cve.org/CVERecord?id=CVE-2024-53233 Référence CVE CVE-2024-53234 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-53207 Référence CVE CVE-2024-53208 https://www.cve.org/CVERecord?id=CVE-2024-53208 Référence CVE CVE-2024-53209 https://www.cve.org/CVERecord?id=CVE-2024-53209 Référence CVE CVE-2024-53210 https://www.cve.org/CVERecord?id=CVE-2024-53210 Référence CVE CVE-2024-53213 https://www.cve.org/CVERecord?id=CVE-2024-53213 Référence CVE CVE-2024-53214 https://www.cve.org/CVERecord?id=CVE-2024-53214 Référence CVE CVE-2024-53215 https://www.cve.org/CVERecord?id=CVE-2024-53215 Référence CVE CVE-2024-53216 https://www.cve.org/CVERecord?id=CVE-2024-53216 Référence CVE CVE-2024-53217 https://www.cve.org/CVERecord?id=CVE-2024-53217 Référence CVE CVE-2024-53222 https://www.cve.org/CVERecord?id=CVE-2024-53222 Référence CVE CVE-2024-53224 https://www.cve.org/CVERecord?id=CVE-2024-53224 Référence CVE CVE-2024-53229 https://www.cve.org/CVERecord?id=CVE-2024-53229 Référence CVE CVE-2024-53234 https://www.cve.org/CVERecord?id=CVE-2024-53234 Référence CVE CVE-2024-53237 https://www.cve.org/CVERecord?id=CVE-2024-53237 Référence CVE CVE-2024-53239 https://www.cve.org/CVERecord?id=CVE-2024-53239 Référence CVE CVE-2024-53240 https://www.cve.org/CVERecord?id=CVE-2024-53240 Référence CVE CVE-2024-53241 https://www.cve.org/CVERecord?id=CVE-2024-53241 Référence CVE CVE-2024-56536 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-53207 Référence CVE CVE-2024-53208 https://www.cve.org/CVERecord?id=CVE-2024-53208 Référence CVE CVE-2024-53209 https://www.cve.org/CVERecord?id=CVE-2024-53209 Référence CVE CVE-2024-53210 https://www.cve.org/CVERecord?id=CVE-2024-53210 Référence CVE CVE-2024-53213 https://www.cve.org/CVERecord?id=CVE-2024-53213 Référence CVE CVE-2024-53214 https://www.cve.org/CVERecord?id=CVE-2024-53214 Référence CVE CVE-2024-53215 https://www.cve.org/CVERecord?id=CVE-2024-53215 Référence CVE CVE-2024-53216 https://www.cve.org/CVERecord?id=CVE-2024-53216 Référence CVE CVE-2024-53217 https://www.cve.org/CVERecord?id=CVE-2024-53217 Référence CVE CVE-2024-53222 https://www.cve.org/CVERecord?id=CVE-2024-53222 Référence CVE CVE-2024-53224 https://www.cve.org/CVERecord?id=CVE-2024-53224 Référence CVE CVE-2024-53229 https://www.cve.org/CVERecord?id=CVE-2024-53229 Référence CVE CVE-2024-53234 https://www.cve.org/CVERecord?id=CVE-2024-53234 Référence CVE CVE-2024-53237 https://www.cve.org/CVERecord?id=CVE-2024-53237 Référence CVE CVE-2024-53240 https://www.cve.org/CVERecord?id=CVE-2024-53240 Référence CVE CVE-2024-53241 https://www.cve.org/CVERecord?id=CVE-2024-53241 Référence CVE CVE-2024-56536 https://www.cve.org/CVERecord?id=CVE-2024-56536 Référence CVE CVE-2024-56539 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-016350Linux の 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.2, 6.6.84 ≤ 6.6.*, 6.12.2 ≤ 6.12.*, 6.13 ≤ *
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:53 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-51894
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

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

Material change intelligence

What changed after publication

View recent updates ↗

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

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2024-51894↗Vendor CSAF · SUSE Product Security Team↗Patch or update reference↗Patch or update reference↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-53222 · cve.blacktree.nl