CVE-2026-89719
zram: fix out-of-bounds access in read_block_state()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.111, 6.18.51, 7.2.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: zram: fix out-of-bounds access in read_block_state() read_block_state() calculates nr_pages before taking dev_lock. If the device is reset and reinitialized with a smaller disksize before lock acquisition, nr_pages still describes the old table. The subsequent loop can then call slot_lock() past the end of the newly allocated table. Read disksize after acquiring dev_lock and checking that the device is initialized. The read lock then keeps the table and its bound stable for the duration of the scan.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
4.18
- KernelLinux
From 4.18.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.111; From 6.13.0 · fixed in 6.18.51; From 6.19.0 · fixed in 7.2.4
References 8
git.kernel.org
- stable/c/fee53224c8261541cf310b57ac7c77a80e144483
- stable/c/26a55336be91004dbd438f3b89b0c31617459976
- stable/c/a189cae92e97d90a9553740f5558d6f74446d3d1
- stable/c/f5e9f3a75efc774f17ab3f33826630d7fe30c7ea
- stable/c/6d52c1f43ff39ea1ebf8f016e847677f0b60cf2b
- stable/c/e7dbcb7a561a21e9a8f5b5fa90bb95aefbd0739d
- stable/c/5e458fa714a55b6b64a9fe0c6d4fa609609f9ec3
- stable/c/391f057f44a51cc9418da5cba78b014324174264