CVE-2026-53185
Last modified
CVE-2026-53185 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: zram: fix use-after-free in zram_bvec_write_partial() zram_read_page() picks the sync or async backing device read path based on whether the parent bio is NULL. zram_bvec_write_partial() passes its parent bio down, so for ZRAM_WB slots the read is dispatched asynchronously and zram_read_page() returns 0 while the bio is still in flight. EPSS estimates a 0.10% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: zram: fix use-after-free in zram_bvec_write_partial() zram_read_page() picks the sync or async backing device read path based on whether the parent bio is NULL. zram_bvec_write_partial() passes its parent bio down, so for ZRAM_WB slots the read is dispatched asynchronously and zram_read_page() returns 0 while the bio is still in flight. The caller then runs memcpy_from_bvec(), zram_write_page() and __free_page() on the buffer, leaving the async read to write into a freed page. zram_bvec_read_partial() was switched to NULL in commit 4e3c87b9421d ("zram: fix synchronous reads") for the same reason; the write_partial counterpart was missed.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.14, < 6.6.143 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.94 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.36 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.13 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
- https://access.redhat.com/security/cve/CVE-2026-53185Third Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=2492735Issue Tracking, Third Party Advisory
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-53185.jsonThird Party Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53185?
How severe is CVE-2026-53185?
How do I fix CVE-2026-53185?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-5318A weakness has been identified in LibRaw up to 0.22.0. This …4.3
- CVE-2026-53180In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-53181In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53182In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53183In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-53184In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-53186In the Linux kernel, the following vulnerability has been re…9.1
- CVE-2026-53187In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-53188In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-53189In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-5319A security vulnerability has been detected in itsourcecode P…4.3
- CVE-2026-53190In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-53185?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
