Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-89719zram: fix out-of-bounds access in read_block_state()

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 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.18% · top 93% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected c0265342bff4fcaa2cdf13f4596244c18d4a7ae5 – < fee53224c8261541cf310b57ac7c77a80e144483
    • affected c0265342bff4fcaa2cdf13f4596244c18d4a7ae5 – < 26a55336be91004dbd438f3b89b0c31617459976
    • affected c0265342bff4fcaa2cdf13f4596244c18d4a7ae5 – < a189cae92e97d90a9553740f5558d6f74446d3d1
    • affected c0265342bff4fcaa2cdf13f4596244c18d4a7ae5 – < f5e9f3a75efc774f17ab3f33826630d7fe30c7ea
    • affected c0265342bff4fcaa2cdf13f4596244c18d4a7ae5 – < 6d52c1f43ff39ea1ebf8f016e847677f0b60cf2b
    • affected c0265342bff4fcaa2cdf13f4596244c18d4a7ae5 – < e7dbcb7a561a21e9a8f5b5fa90bb95aefbd0739d
    • affected c0265342bff4fcaa2cdf13f4596244c18d4a7ae5 – < 5e458fa714a55b6b64a9fe0c6d4fa609609f9ec3
    • affected c0265342bff4fcaa2cdf13f4596244c18d4a7ae5 – < 391f057f44a51cc9418da5cba78b014324174264
  • Linux · Linux

    • affected 4.18
    • unaffected < 4.18
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89719 badge
[![CVE-2026-89719](https://cveledger.app/badge/CVE-2026-89719.svg)](https://cveledger.app/cve/CVE-2026-89719)

Record last updated .