CVE-2026-63951·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: zram: fix use-after-free in zram_writeback_endio A crash was observed in zram_writeback_endio due to a NULL pointer dereference in wake_up. The root cause is a race condition between the bio completion handler (zram_writeback_endio) and the writeback task. In zram_writeback_endio, wake_up() is called on &wb_ctl->done_wait after releasing wb_ctl->done_lock. This creates a race window where the writeback task can see num_inflight become 0, return, and free wb_ctl before zram_writeback_endio calls wake_up(). CPU 0 (zram_writeback_endio) CPU 1 (writeback_store) ============================ ============================ zram_writeback_slots zram_submit_wb_request zram_submit_wb_request wait_event(wb_ctl->done_wait) spin_lock(&wb_ctl->done_lock); list_add(&req->entry, &wb_ctl->done_reqs); spin_unlock(&wb_ctl->done_lock); wake_up(&wb_ctl->done_wait); zram_complete_done_reqs spin_lock(&wb_ctl->done_lock); list_add(&req->entry, &wb_ctl->done_reqs); spin_unlock(&wb_ctl->done_lock); while (num_inflight) > 0) spin_lock(&wb_ctl->done_lock); list_del(&req->entry); spin_unlock(&wb_ctl->done_lock); // num_inflight becomes 0 atomic_dec(num_inflight); // Leave zram_writeback_slots // Free wb_ctl release_wb_ctl(wb_ctl); // UAF crash! wake_up(&wb_ctl->done_wait); This patch fixes this race by using RCU. By protecting wb_ctl with rcu_read_lock() in zram_writeback_endio and using kfree_rcu() to free it, we ensure that wb_ctl remains valid during the execution of zram_writeback_endio.
- Severity
- high
- Software
- Kernel
- Fixed in
- 7.0.12
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.18% — higher than 7% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-63951 scores 7.8 on CVSS, so a successful attack would be serious — but at 0.18%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 6.19
Until: 7.0.12
Fixed in: 7.0.12
How to fix this CVE
Update your Linux kernel to version 7.0.12 or later to resolve this use-after-free vulnerability in the zram writeback mechanism. The vulnerability stems from a race condition where the bio completion handler attempts to access memory that has already been freed by the writeback task. Systems running kernels between 6.19 and 7.0.11 should prioritize this patch to prevent potential kernel crashes and denial of service conditions.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Check current kernel version: uname -r — verify it is NOT between 6.19 and 7.0.11
- Confirm zram is enabled: cat /proc/swaps | grep zram — if present, the system uses the vulnerable component
- Search system logs for zram writeback errors: grep -i 'zram_writeback\|use.after.free\|NULL pointer' /var/log/kern.log /var/log/messages
- Verify kernel patch applied: grep -i 'zram.*rcu\|kfree_rcu' /boot/config-$(uname -r) — should contain RCU protection references
FAQ
What is CVE-2026-63951?
This vulnerability is a use-after-free race condition in the Linux kernel's zram (compressed RAM) writeback handler. When the bio completion function attempts to wake up a waiting task after the writeback controller has already freed the associated memory structure, it causes a kernel crash.
Is CVE-2026-63951 being actively exploited?
No, this CVE is not listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available. However, it can be triggered by local attackers with sufficient privileges to trigger zram writeback operations.
What versions of Kernel are affected by CVE-2026-63951?
Linux kernel versions 6.19 through 7.0.11 are vulnerable. The vulnerability is fixed in kernel version 7.0.12 and later.
How do I check if my server is vulnerable to CVE-2026-63951?
Run 'uname -r' to check your kernel version — if it returns a version between 6.19 and 7.0.11, your system is vulnerable. Additionally, verify zram is in use with 'cat /proc/swaps | grep zram'.
Does Defensia detect CVE-2026-63951?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2026-63951 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-63951. Free for 1 server.
Get started free