Description (CNA)
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.
Affected (CNA)
| Vendor / product | Versions |
|---|---|
| Linux / Linux | affected 8e654f8fbff52ac483fb69957222853d7e2fc588 before 0c2821665ff71be3f4b07ecece384669f2877f6a; affected 8e654f8fbff52ac483fb69957222853d7e2fc588 before 77a602b505ce4802915853cfc435a4722fab3e64; affected 8e654f8fbff52ac483fb69957222853d7e2fc588 before c96786d6ff1acc1d54d9241e97767554c1dfdd5b; affected 8e654f8fbff52ac483fb69957222853d7e2fc588 before 198b5a14cca27263b9c14b20114c8092de15dfcb; affected 8e654f8fbff52ac483fb69957222853d7e2fc588 before 732fd9f0b9c1cdc6dfd77162ded60df005182cc0 |
| Linux / Linux | affected 4.14; unaffected 0 before 4.14; unaffected 6.6.143 through 6.6.*; unaffected 6.12.94 through 6.12.*; unaffected 6.18.36 through 6.18.*; unaffected 7.0.13 through 7.0.*; unaffected 7.1 through * |
CWE
No CWE identifiers supplied.
References
- https://git.kernel.org/stable/c/0c2821665ff71be3f4b07ecece384669f2877f6a
- https://git.kernel.org/stable/c/77a602b505ce4802915853cfc435a4722fab3e64
- https://git.kernel.org/stable/c/c96786d6ff1acc1d54d9241e97767554c1dfdd5b
- https://git.kernel.org/stable/c/198b5a14cca27263b9c14b20114c8092de15dfcb
- https://git.kernel.org/stable/c/732fd9f0b9c1cdc6dfd77162ded60df005182cc0
ADP enrichment
A flaw was found in the Linux kernel, specifically within the zram module. This vulnerability is a use-after-free error, where the system attempts to use a piece of memory after it has been freed. This occurs when the `zram_bvec_write_partial()` function allows an asynchronous read to write into a page that has already been deallocated. Such a flaw can lead to system instability, causing crashes, or in some scenarios, could be exploited by a local attacker to escalate privileges or execute arbitrary code.
- https://access.redhat.com/security/cve/CVE-2026-53185
- https://bugzilla.redhat.com/show_bug.cgi?id=2492735
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-53185.json
- https://access.redhat.com/errata/RHSA-2026:61887
- https://access.redhat.com/errata/RHSA-2026:65708
- https://access.redhat.com/errata/RHSA-2026:59723
- https://access.redhat.com/errata/RHSA-2026:63014
- https://access.redhat.com/errata/RHSA-2026:63013
No English description supplied.
No references supplied.