CVE-2026-53025

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. 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:

greybus: raw: fix use-after-free on cdev close

This addresses a use-after-free bug when a raw bundle is disconnected but its chardev is still opened by an application. When the application releases the cdev, it causes the following panic when init on free is enabled (CONFIG_INIT_ON_FREE_DEFAULT_ON=y):

refcount_t: underflow; use-after-free. WARNING: CPU: 0 PID: 139 at lib/refcount.c:28 refcount_warn_saturate+0xd0/0x130 ... Call Trace: cdev_put+0x18/0x30 __fput+0x255/0x2a0 __x64_sys_close+0x3d/0x80 do_syscall_64+0xa4/0x290 entry_SYSCALL_64_after_hwframe+0x77/0x7f

The cdev is contained in the "gb_raw" structure, which is freed in the disconnect operation. When the cdev is released at a later time, cdev_put gets an address that points to freed memory.

To fix this use-after-free, convert the struct device from a pointer to being embedded, that makes the lifetime of the cdev and of this device the same. Then, use cdev_device_add, which guarantees that the device won't be released until all references to the cdev have been released. Finally, delegate the freeing of the structure to the device release function, instead of freeing immediately in the disconnect callback.

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

Published

June 24, 2026

Last Modified

June 28, 2026

Advisory Details (2)

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

greybus: raw: fix use-after-free on cdev close - kernel/git/stable/linux.git - Linux kernel stable tree

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

greybus: raw: fix use-after-free on cdev close - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/983cc2c7efbce04ecbf6328448d895044dd6ab31

Vendor Advisories for CVE-2026-53025(2)

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

Data Freshness Timeline

(refreshed 38× in last 7d / 50× 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 03:14 UTCEG score recompute
  2. 2026-07-07 03:13 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 16:07 UTCEG score recompute
  6. 2026-07-06 16:06 UTCGHSA enrichment
  7. 2026-07-06 04:55 UTCEG score recompute
  8. 2026-07-06 04:55 UTCGHSA enrichment
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 17:35 UTCEG score recompute
  12. 2026-07-05 17:35 UTCGHSA enrichment
  13. 2026-07-05 06:27 UTCEG score recompute
  14. 2026-07-05 06:27 UTCGHSA enrichment
  15. 2026-07-05 02:31 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 19:19 UTCEG score recompute
  18. 2026-07-04 19:19 UTCGHSA enrichment
  19. 2026-07-04 08:13 UTCEG score recompute
  20. 2026-07-04 08:12 UTCGHSA enrichment
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-03 21:05 UTCEG score recompute
  23. 2026-07-03 21:05 UTCGHSA enrichment
  24. 2026-07-03 09:59 UTCEG score recompute
  25. 2026-07-03 09:59 UTCGHSA enrichment
Show 25 more
  1. 2026-07-02 22:49 UTCEG score recompute
  2. 2026-07-02 22:48 UTCGHSA enrichment
  3. 2026-07-02 11:42 UTCEG score recompute
  4. 2026-07-02 11:41 UTCGHSA enrichment
  5. 2026-07-02 00:32 UTCEG score recompute
  6. 2026-07-02 00:32 UTCGHSA enrichment
  7. 2026-07-01 13:24 UTCEG score recompute
  8. 2026-07-01 13:24 UTCGHSA enrichment
  9. 2026-07-01 02:18 UTCEG score recompute
  10. 2026-07-01 02:18 UTCGHSA enrichment
  11. 2026-06-30 23:22 UTCEPSS rescore
  12. 2026-06-30 15:12 UTCEG score recompute 7.80
  13. 2026-06-30 15:12 UTCGHSA enrichment
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-28 14:07 UTCEPSS rescore
  17. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-27 16:46 UTCEG score recompute
  21. 2026-06-27 16:46 UTCGHSA enrichment
  22. 2026-06-27 03:08 UTCEPSS rescore
  23. 2026-06-25 13:49 UTCEPSS rescore
  24. 2026-06-24 18:20 UTCEG score recompute
  25. 2026-06-24 18:02 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-53025?
CVE-2026-53025 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: greybus: raw: fix use-after-free on cdev close This addresses a use-after-free bug when a raw bundle is disconnected but its chardev is still opened by an application. When the application releases the cdev, it causes the following…
When was CVE-2026-53025 disclosed?
CVE-2026-53025 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53025 actively exploited?
CVE-2026-53025 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53025?
CVE-2026-53025 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53025?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53025, 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-53025

Explore →

Is Your Infrastructure Affected by CVE-2026-53025?

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