- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: zram: fix out-of-bounds access in writeback_store() Patch series "zram: fix stale scan bounds after reinitialization". Both writeback_store() and read_block_state() derive their table scan bounds from zram->disksize before acquiring dev_lock. If the device is reset and reinitialized with a smaller disksize between that read and lock acquisition, the bound can describe the old table while the scan operates on the new one. This can lead to out-of-bounds slot accesses. Move both bound calculations under dev_lock so each bound remains consistent with the table throughout its scan. Keep the fixes separate because the affected interfaces originate from different commits and can be backported independently. This patch (of 2): writeback_store() calculates the table scan bounds before taking dev_lock. A reset followed by reconfiguration with a smaller disksize can therefore replace zram->table while writeback_store() is waiting for the lock. Once it acquires the lock, it sees an initialized device but scans the new table using the old upper bound, resulting in an out-of-bounds access. Calculate the number of pages while holding dev_lock so the scan bound matches the table protected by the lock.
Timeline
ID reserved
By Linux
Published
- 49 days later
· 49 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (12 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected a939888ec38bf1f33e4a903056677e92a4844244 – < f1c5611f699a3aa2a85ebd5fec03dc9bc501e6d0
- affected a939888ec38bf1f33e4a903056677e92a4844244 – < c2745e657f0974871fbc60d46d48c2b04e581330
- affected a939888ec38bf1f33e4a903056677e92a4844244 – < 4d82d60178b02797dbe529e01ac211b26670c49f
- affected a939888ec38bf1f33e4a903056677e92a4844244 – < ef073edd7cfd31aeb90eeab23273102c601f4d8e
- affected a939888ec38bf1f33e4a903056677e92a4844244 – < 07a82a66f8c1894d92e51d97542c32ebf2c51b09
- affected a939888ec38bf1f33e4a903056677e92a4844244 – < 894913e2d35c46ff19a77530907771ae57862b96
- affected 5.0
- unaffected < 5.0
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.111 – ≤ 6.12.*
- unaffected 6.18.57 – ≤ 6.18.*
- unaffected 7.2.4 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/f1c5611f699a3aa2a85ebd5fec03dc9bc501e6d0 (opens in a new tab)
- https://git.kernel.org/stable/c/c2745e657f0974871fbc60d46d48c2b04e581330 (opens in a new tab)
- https://git.kernel.org/stable/c/4d82d60178b02797dbe529e01ac211b26670c49f (opens in a new tab)
- https://git.kernel.org/stable/c/ef073edd7cfd31aeb90eeab23273102c601f4d8e (opens in a new tab)
- https://git.kernel.org/stable/c/07a82a66f8c1894d92e51d97542c32ebf2c51b09 (opens in a new tab)
- https://git.kernel.org/stable/c/894913e2d35c46ff19a77530907771ae57862b96 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-76630 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-89718)Record last updated .