5 matches found
CVE-2026-89718
A flaw was found in the zram component of the Linux kernel. This vulnerability occurs because the writebackstore function calculates table scan bounds before acquiring a necessary lock. If the zram device is reinitialized with a smaller disk size during this window, the function may attempt to...
CVE-2026-89718
In the Linux kernel, the following vulnerability has been resolved: zram: fix out-of-bounds access in writebackstore Patch series "zram: fix stale scan bounds after reinitialization". Both writebackstore and readblockstate derive their table scan bounds from zram-disksize before acquiring devlock...
EUVD-2026-76630
In the Linux kernel, the following vulnerability has been resolved: zram: fix out-of-bounds access in writebackstore Patch series "zram: fix stale scan bounds after reinitialization". Both writebackstore and readblockstate derive their table scan bounds from zram-disksize before acquiring devlock...
CVE-2026-89718 zram: fix out-of-bounds access in writeback_store()
In the Linux kernel, the following vulnerability has been resolved: zram: fix out-of-bounds access in writebackstore Patch series "zram: fix stale scan bounds after reinitialization". Both writebackstore and readblockstate derive their table scan bounds from zram-disksize before acquiring devlock...
CVE-2026-89718
CVE-2026-89718 is an out-of-bounds access in the Linux kernel's zram module , specifically in the writeback_store() function. The root cause is a race condition: scan bounds are derived from zram->disksize before acquiring dev_lock. If the zram device is reset and reinitialized with a smaller ...