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

> A race condition in the Linux kernel zram driver allows out-of-bounds memory access, potentially leading to system crashes or code execution.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-100860, BELL-CVE-2026-89719, DEBIAN-CVE-2026-89719, GHSA-5pfc-pqwh-23px, UBUNTU-CVE-2026-89719

## What is CVE-2026-89719?

CVE-2026-89719 is a memory corruption vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-89719?


## How do I fix CVE-2026-89719?

Apply the vendor's patch.

## Is CVE-2026-89719 being exploited?

There is no known exploitation of CVE-2026-89719 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-89719 and fix it if it is affected.

What it is: CVE-2026-89719 is a memory corruption vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-89719 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-89719/ (Markdown: https://insights.sbomify.com/CVE-2026-89719/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-89719
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-89719
- OSV: https://osv.dev/vulnerability/CVE-2026-89719

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-89719/
Summaries are generated and may contain mistakes; the official description above is the record.