Answer in brief
CVE-2026-53185 records a High severity (CVSS 7.8) vulnerability in zram: fix use-after-free in zram_bvec_write_partial(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-53185 records a High severity (CVSS 7.8) vulnerability in zram: fix use-after-free in zram_bvec_write_partial(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=8e654f8fbff52ac483fb69957222853d7e2fc588 <0c2821665ff71be3f4b07ecece384669f2877f6a || >=8e654f8fbff52ac483fb69957222853d7e2fc588 <77a602b505ce4802915853cfc435a4722fab3e64 || >=8e654f8fbff52ac483fb69957222853d7e2fc588 <c96786d6ff1acc1d54d9241e97767554c1dfdd5b || >=8e654f8fbff52ac483fb69957222853d7e2fc588 <198b5a14cca27263b9c14b20114c8092de15dfcb || >=8e654f8fbff52ac483fb69957222853d7e2fc588 <732fd9f0b9c1cdc6dfd77162ded60df005182cc0 | 0c2821665ff71be3f4b07ecece384669f2877f6a, 77a602b505ce4802915853cfc435a4722fab3e64, c96786d6ff1acc1d54d9241e97767554c1dfdd5b, 198b5a14cca27263b9c14b20114c8092de15dfcb, 732fd9f0b9c1cdc6dfd77162ded60df005182cc0 |
| Linux/Linuxgeneric | 4.14 | Not reported |
Published upstream
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=8e654f8fbff52ac483fb69957222853d7e2fc588 <0c2821665ff71be3f4b07ecece384669f2877f6a || >=8e654f8fbff52ac483fb69957222853d7e2fc588 <77a602b505ce4802915853cfc435a4722fab3e64 || >=8e654f8fbff52ac483fb69957222853d7e2fc588 <c96786d6ff1acc1d54d9241e97767554c1dfdd5b || >=8e654f8fbff52ac483fb69957222853d7e2fc588 <198b5a14cca27263b9c14b20114c8092de15dfcb || >=8e654f8fbff52ac483fb69957222853d7e2fc588 <732fd9f0b9c1cdc6dfd77162ded60df005182cc0 | 0c2821665ff71be3f4b07ecece384669f2877f6a, 77a602b505ce4802915853cfc435a4722fab3e64, c96786d6ff1acc1d54d9241e97767554c1dfdd5b, 198b5a14cca27263b9c14b20114c8092de15dfcb, 732fd9f0b9c1cdc6dfd77162ded60df005182cc0 |
| Linux/Linuxgeneric | 4.14 | Not reported |
Published upstream
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.