In the Linux kernel, the following vulnerability has been resolved: zram: fix out-of-bounds access in read_block_state() read_block_state()… (CVE-2026-89719)
A vulnerability in the Linux kernel's zram component was resolved that involved an out-of-bounds access in the read_block_state() function. The issue occurred because nr_pages was calculated before acquiring the device lock, which could lead to accessing memory beyond the bounds of the newly allocated table if the device was reset and reinitialized with a smaller disk size. The fix involved reading the disk size after acquiring the device lock to ensure stability during the scan.
AI Analysis
Technical Summary
The Linux kernel's zram module had a vulnerability (CVE-2026-89719) where read_block_state() calculated the number of pages (nr_pages) before locking the device. If the device was reset and reinitialized with a smaller disk size before the lock was acquired, nr_pages would reflect the old, larger table size. This could cause the subsequent loop to call slot_lock() beyond the end of the newly allocated table, resulting in out-of-bounds memory access. The fix ensures that the disk size is read after acquiring the device lock and verifying device initialization, stabilizing the table bounds during the scan.
Potential Impact
This vulnerability could lead to out-of-bounds memory access within the kernel's zram module, potentially causing kernel instability or crashes. No information is provided about exploitation in the wild or further impact such as privilege escalation.
Mitigation Recommendations
A fix has been applied to the Linux kernel to address this vulnerability by changing the order of operations in read_block_state(). Users should update to a kernel version that includes this fix. Since no patch links are provided, check the official Linux kernel advisories or vendor updates for the fixed version.
In the Linux kernel, the following vulnerability has been resolved: zram: fix out-of-bounds access in read_block_state() read_block_state()… (CVE-2026-89719)
Description
A vulnerability in the Linux kernel's zram component was resolved that involved an out-of-bounds access in the read_block_state() function. The issue occurred because nr_pages was calculated before acquiring the device lock, which could lead to accessing memory beyond the bounds of the newly allocated table if the device was reset and reinitialized with a smaller disk size. The fix involved reading the disk size after acquiring the device lock to ensure stability during the scan.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's zram module had a vulnerability (CVE-2026-89719) where read_block_state() calculated the number of pages (nr_pages) before locking the device. If the device was reset and reinitialized with a smaller disk size before the lock was acquired, nr_pages would reflect the old, larger table size. This could cause the subsequent loop to call slot_lock() beyond the end of the newly allocated table, resulting in out-of-bounds memory access. The fix ensures that the disk size is read after acquiring the device lock and verifying device initialization, stabilizing the table bounds during the scan.
Potential Impact
This vulnerability could lead to out-of-bounds memory access within the kernel's zram module, potentially causing kernel instability or crashes. No information is provided about exploitation in the wild or further impact such as privilege escalation.
Mitigation Recommendations
A fix has been applied to the Linux kernel to address this vulnerability by changing the order of operations in read_block_state(). Users should update to a kernel version that includes this fix. Since no patch links are provided, check the official Linux kernel advisories or vendor updates for the fixed version.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-5pfc-pqwh-23px
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-89719"]
Threat ID: 6aa49fff55bf5e2cf5a865ff
Added to database: 09/12/2026, 00:42:39 UTC
Last enriched: 09/12/2026, 00:54:04 UTC
Last updated: 09/12/2026, 00:54:04 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.