Strix
64.3K

CVE-2026-89719

UnknownEPSS 0.17%

Last modified

CVE-2026-89719 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.17% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.17%

6.3th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= c0265342bff4fcaa2cdf13f4596244c18d4a7ae5, < 6d52c1f43ff39ea1ebf8f016e847677f0b60cf2b; >= c0265342bff4fcaa2cdf13f4596244c18d4a7ae5, < e7dbcb7a561a21e9a8f5b5fa90bb95aefbd0739d; >= c0265342bff4fcaa2cdf13f4596244c18d4a7ae5, < 5e458fa714a55b6b64a9fe0c6d4fa609609f9ec3; >= c0265342bff4fcaa2cdf13f4596244c18d4a7ae5, < 391f057f44a51cc9418da5cba78b014324174264
LinuxLinux4.18

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-89719?
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.
How severe is CVE-2026-89719?
Severity scoring for CVE-2026-89719 is pending analysis. The EPSS model estimates a 0.17% probability of exploitation in the next 30 days.
How do I fix CVE-2026-89719?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-89719?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST