CVE-2026-89719: Linux kernel · zram: fix out-of-bounds access in read_block_state()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f5e9f3a75efc774f17ab3f33826630d7fe30c7ea : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f5e9f3a75efc774f17ab3f33826630d7fe30c7ea, e7dbcb7a561a21e9a8f5b5fa90bb95aefbd0739d, 391f057f44a51cc9418da5cba78b014324174264 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 11 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
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.
References
- git.kernel.org/stable/c/f5e9f3a75efc774f17ab3f33826630d7fe30c7ea (opens in a new tab)
- git.kernel.org/stable/c/6d52c1f43ff39ea1ebf8f016e847677f0b60cf2b (opens in a new tab)
- git.kernel.org/stable/c/e7dbcb7a561a21e9a8f5b5fa90bb95aefbd0739d (opens in a new tab)
- git.kernel.org/stable/c/5e458fa714a55b6b64a9fe0c6d4fa609609f9ec3 (opens in a new tab)
- git.kernel.org/stable/c/391f057f44a51cc9418da5cba78b014324174264 (opens in a new tab)