CVE-2026-53024

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 if write is called after disconnect

If a user writes to the chardev after disconnect has been called, the kernel panics with the following trace (with CONFIG_INIT_ON_FREE_DEFAULT_ON=y):

BUG: kernel NULL pointer dereference, address: 0000000000000218 ... Call Trace: gb_operation_create_common+0x61/0x180 gb_operation_create_flags+0x28/0xa0 gb_operation_sync_timeout+0x6f/0x100 raw_write+0x7b/0xc7 [gb_raw] vfs_write+0xcf/0x420 ? task_mm_cid_work+0x136/0x220 ksys_write+0x63/0xe0 do_syscall_64+0xa4/0x290 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Disconnect calls gb_connection_destroy, which ends up freeing the connection object. When gb_operation_sync is called in the write file operations, its gets a freed connection as parameter and the kernel panics.

The gb_connection_destroy cannot be moved out of the disconnect function, as the Greybus subsystem expect all connections belonging to a bundle to be destroyed when disconnect returns.

To prevent this bug, use a rw lock to synchronize access between write and disconnect. This guarantees that the write function doesn't try to use a disconnected connection.

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 if write is called after disconnect - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/84265cbd96b97058ef67e3f8be3933667a000835
generic

greybus: raw: fix use-after-free if write is called after disconnect - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/48d6c32bc049abd114e8f0836c0e7d7cbfba7827

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

Frequently asked(5)

What is CVE-2026-53024?
CVE-2026-53024 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 if write is called after disconnect If a user writes to the chardev after disconnect has been called, the kernel panics with the following trace (with CONFIGINITONFREEDEFAULT_ON=y): BUG: kernel NULL…
When was CVE-2026-53024 disclosed?
CVE-2026-53024 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-53024 actively exploited?
CVE-2026-53024 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-53024?
CVE-2026-53024 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53024?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53024, 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-53024

Explore →

Is Your Infrastructure Affected by CVE-2026-53024?

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

Start Free Scan →Browse All CVEs