CVE-2024-53222: zram: fix NULL pointer in comp_algorithm_show()
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 843d366ff19708668d95cda16bb8aba109a93dba, c7ee791e538537b281f60945298796f0a3971bbd, f364cdeb38938f9d03061682b8ff3779dd1730e5; azl3 kernel 6.6.85.1-1 on Azure Linux 3.0 6.6.85.1-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.85.1-1.
Low priority for now. Upgrade to Linux Linux 843d366ff19708668d95cda16bb8aba109a93dba, c7ee791e538537b281f60945298796f0a3971bbd, f364cdeb38938f9d03061682b8ff3779dd1730e5; azl3 kernel 6.6.85.1-1 on Azure Linux 3.0 6.6.85.1-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.85.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Dec 27, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-476
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.2 and later · before 6.12.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.2affected
- 7ac07a26dea79c3892436bce41cce03dcbd3c4c7 and later · before c7ee791e538537b281f60945298796f0a3971bbdaffected · git
- 7ac07a26dea79c3892436bce41cce03dcbd3c4c7 and later · before 843d366ff19708668d95cda16bb8aba109a93dbaaffected · git
- 7ac07a26dea79c3892436bce41cce03dcbd3c4c7 and later · before f364cdeb38938f9d03061682b8ff3779dd1730e5affected · git
- before 6.2not affected · semver
- 6.6.84 and later · up to and including 6.6.*not affected · semver
- 6.12.2 and later · up to and including 6.12.*not affected · semver
- 6.13 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
| AlmaLinux:10 | kernel-core | before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-53220Dec 27, 2024 · f2fs: fix to account dirty data in __get_secs_required()22Monitor
- ← EarlierCVE-2024-53221Dec 27, 2024 · f2fs: fix null-ptr-deref in f2fs_submit_page_bio()22Monitor
- Later →CVE-2024-53223Dec 27, 2024 · clk: ralink: mtmips: fix clocks probe order in oldest ralink SoCs22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 843d366ff19708668d95cda16bb8aba109a93dba | Vendor (CNA) |
| Linux Linux | c7ee791e538537b281f60945298796f0a3971bbd | Vendor (CNA) |
| Linux Linux | f364cdeb38938f9d03061682b8ff3779dd1730e5 | Vendor (CNA) |
| azl3 kernel 6.6.85.1-1 on Azure Linux 3.0 | 6.6.85.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 | 6.6.85.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:kernel | 6.12.0-124.8.1.el10_1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k | 6.12.0-124.8.1.el10_1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-core | 6.12.0-124.8.1.el10_1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 6.12.0-124.8.1.el10_1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 6.12.0-124.8.1.el10_1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 6.12.0-124.8.1.el10_1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 6.12.0-124.8.1.el10_1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 6.12.0-124.8.1.el10_1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 6.12.0-124.8.1.el10_1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 6.12.0-124.8.1.el10_1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 6.12.0-124.8.1.el10_1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 6.12.0-124.8.1.el10_1 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.12.3-1 · Debian:13 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:kernel-debuginfo-common-ppc64le | 0:6.12.0-124.8.1.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
+1
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.