🛡️ CVE-2024-53222 — kernel

🟡 CVSS 5.5 — Medium ✅ No Known Exploit NVD
5.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

zram: fix NULL pointer in comp_algorithm_show()

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.

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

Affected software

CVE-2024-53222 is recorded against 2 packages.

  • kernel (from 6.7.0 up to 6.12.2)
  • linux-kernel (from 6.2 up to 6.12.2)

Timeline and source

Published on 27 December 2024 and last revised on 15 July 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

CVE-2024-53222 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity Medium
CVSS Score 5.5
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2024-12-27
Updated 2026-08-12
Modified 2026-07-15

Affected Packages

Software From version Fixed in
kernel 6.7.0 6.12.2
linux-kernel 6.2 6.12.2

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in kernel

CVE-2024-53222 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.