CVE-2026-53185

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.8
EG Score
7.8(high)
EPSS
1.0%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 6, 2026

Advisory Details (5)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

zram: fix use-after-free in zram_bvec_write_partial() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c96786d6ff1acc1d54d9241e97767554c1dfdd5b
generic

zram: fix use-after-free in zram_bvec_write_partial() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/77a602b505ce4802915853cfc435a4722fab3e64
generic

zram: fix use-after-free in zram_bvec_write_partial() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/732fd9f0b9c1cdc6dfd77162ded60df005182cc0
generic

zram: fix use-after-free in zram_bvec_write_partial() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/198b5a14cca27263b9c14b20114c8092de15dfcb
generic

zram: fix use-after-free in zram_bvec_write_partial() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0c2821665ff71be3f4b07ecece384669f2877f6a

Vendor Advisories for CVE-2026-53185(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 36× in last 7d / 54× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 01:52 UTCEG score recompute
  2. 2026-07-07 01:52 UTCGHSA enrichment
  3. 2026-07-06 13:43 UTCEG score recompute
  4. 2026-07-06 13:43 UTCGHSA enrichment
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-06 01:34 UTCEG score recompute
  8. 2026-07-06 01:34 UTCGHSA enrichment
  9. 2026-07-05 13:24 UTCEG score recompute
  10. 2026-07-05 13:24 UTCGHSA enrichment
  11. 2026-07-05 02:31 UTCEPSS rescore
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-05 01:15 UTCEG score recompute
  14. 2026-07-05 01:15 UTCGHSA enrichment
  15. 2026-07-04 12:53 UTCEG score recompute
  16. 2026-07-04 12:53 UTCGHSA enrichment
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-04 00:45 UTCEG score recompute
  20. 2026-07-04 00:45 UTCGHSA enrichment
  21. 2026-07-03 12:37 UTCEG score recompute
  22. 2026-07-03 12:37 UTCGHSA enrichment
  23. 2026-07-03 00:25 UTCEG score recompute
  24. 2026-07-03 00:25 UTCGHSA enrichment
  25. 2026-07-02 12:16 UTCEG score recompute
Show 29 more
  1. 2026-07-02 12:15 UTCGHSA enrichment
  2. 2026-07-02 00:07 UTCEG score recompute
  3. 2026-07-02 00:06 UTCGHSA enrichment
  4. 2026-07-01 15:07 UTCEPSS rescore
  5. 2026-07-01 11:58 UTCEG score recompute
  6. 2026-07-01 11:58 UTCGHSA enrichment
  7. 2026-06-30 23:50 UTCEG score recompute
  8. 2026-06-30 23:50 UTCGHSA enrichment
  9. 2026-06-30 23:22 UTCEPSS rescore
  10. 2026-06-30 11:41 UTCEG score recompute
  11. 2026-06-30 11:41 UTCGHSA enrichment
  12. 2026-06-29 23:33 UTCEG score recompute
  13. 2026-06-29 23:32 UTCGHSA enrichment
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-29 11:22 UTCEG score recompute
  17. 2026-06-29 11:22 UTCGHSA enrichment
  18. 2026-06-28 23:13 UTCEG score recompute
  19. 2026-06-28 23:13 UTCGHSA enrichment
  20. 2026-06-28 14:07 UTCEPSS rescore
  21. 2026-06-28 11:04 UTCEG score recompute 7.80
  22. 2026-06-28 11:04 UTCGHSA enrichment
  23. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-28 04:56 UTCEPSS rescore
  26. 2026-06-27 03:08 UTCEPSS rescore
  27. 2026-06-25 13:49 UTCEPSS rescore
  28. 2026-06-25 10:07 UTCEG score recompute
  29. 2026-06-25 10:07 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-53185?
CVE-2026-53185 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: zram: fix use-after-free in zrambvecwrite_partial() zramreadpage() picks the sync or async backing device read path based on whether the parent bio is NULL. zrambvecwrite_partial() passes its parent bio down, so for ZRAM_WB slots…
When was CVE-2026-53185 disclosed?
CVE-2026-53185 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53185 actively exploited?
CVE-2026-53185 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53185?
CVE-2026-53185 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53185?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53185, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53185

Explore →

Is Your Infrastructure Affected by CVE-2026-53185?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.