CVE-2026-53024

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

June 24, 2026

Last Modified

August 5, 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.

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1—

Weakness Classification(1)

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

All Vendor Advisories

(8)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 86× 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.

Showing the most recent 100 of 264 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-02 14:12 UTCEPSS rescore
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 04:40 UTCEPSS rescore
  10. 2026-08-30 20:07 UTCEG score recompute
  11. 2026-08-30 20:07 UTCVendor advisory
  12. 2026-08-30 20:07 UTCGHSA enrichment
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-28 04:44 UTCEG score recompute
  17. 2026-08-28 04:44 UTCVendor advisory
  18. 2026-08-28 04:44 UTCGHSA enrichment
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-25 00:53 UTCEG score recompute
  23. 2026-08-25 00:53 UTCVendor advisory
  24. 2026-08-25 00:53 UTCGHSA enrichment
  25. 2026-08-24 13:41 UTCEG score recompute
Show 75 more
  1. 2026-08-24 13:41 UTCVendor advisory
  2. 2026-08-24 13:41 UTCGHSA enrichment
  3. 2026-08-23 23:20 UTCVendor advisory
  4. 2026-08-23 23:20 UTCGHSA enrichment
  5. 2026-08-23 12:09 UTCVendor advisory
  6. 2026-08-23 12:09 UTCGHSA enrichment
  7. 2026-08-23 00:55 UTCEG score recompute
  8. 2026-08-23 00:55 UTCVendor advisory
  9. 2026-08-23 00:55 UTCGHSA enrichment
  10. 2026-08-23 00:19 UTCEPSS rescore
  11. 2026-08-22 13:02 UTCEG score recompute
  12. 2026-08-22 13:02 UTCVendor advisory
  13. 2026-08-22 13:02 UTCGHSA enrichment
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 17:29 UTCVendor advisory
  16. 2026-08-21 17:29 UTCGHSA enrichment
  17. 2026-08-21 05:50 UTCEG score recompute
  18. 2026-08-21 05:50 UTCVendor advisory
  19. 2026-08-21 05:50 UTCGHSA enrichment
  20. 2026-08-20 22:55 UTCEPSS rescore
  21. 2026-08-20 18:38 UTCVendor advisory
  22. 2026-08-20 18:38 UTCGHSA enrichment
  23. 2026-08-20 07:27 UTCEG score recompute
  24. 2026-08-20 07:27 UTCVendor advisory
  25. 2026-08-20 07:27 UTCGHSA enrichment
  26. 2026-08-19 17:04 UTCEPSS rescore
  27. 2026-08-19 13:30 UTCVendor advisory
  28. 2026-08-19 13:30 UTCGHSA enrichment
  29. 2026-08-19 02:09 UTCEG score recompute
  30. 2026-08-19 02:09 UTCVendor advisory
  31. 2026-08-19 02:09 UTCGHSA enrichment
  32. 2026-08-18 13:48 UTCEPSS rescore
  33. 2026-08-17 13:47 UTCEPSS rescore
  34. 2026-08-17 07:19 UTCVendor advisory
  35. 2026-08-17 07:19 UTCGHSA enrichment
  36. 2026-08-16 20:08 UTCEG score recompute
  37. 2026-08-16 20:08 UTCVendor advisory
  38. 2026-08-16 20:08 UTCGHSA enrichment
  39. 2026-08-16 14:56 UTCEPSS rescore
  40. 2026-08-16 07:53 UTCEG score recompute
  41. 2026-08-16 07:53 UTCVendor advisory
  42. 2026-08-16 07:53 UTCGHSA enrichment
  43. 2026-08-16 02:14 UTCEPSS rescore
  44. 2026-08-15 20:43 UTCVendor advisory
  45. 2026-08-15 20:43 UTCGHSA enrichment
  46. 2026-08-15 09:27 UTCEG score recompute
  47. 2026-08-15 09:27 UTCVendor advisory
  48. 2026-08-15 09:27 UTCGHSA enrichment
  49. 2026-08-15 01:30 UTCEPSS rescore
  50. 2026-08-14 22:14 UTCVendor advisory
  51. 2026-08-14 22:14 UTCGHSA enrichment
  52. 2026-08-14 11:03 UTCVendor advisory
  53. 2026-08-14 11:03 UTCGHSA enrichment
  54. 2026-08-13 23:52 UTCEG score recompute
  55. 2026-08-13 23:52 UTCVendor advisory
  56. 2026-08-13 23:52 UTCGHSA enrichment
  57. 2026-08-13 22:00 UTCEPSS rescore
  58. 2026-08-13 12:40 UTCVendor advisory
  59. 2026-08-13 12:40 UTCGHSA enrichment
  60. 2026-08-13 01:16 UTCVendor advisory
  61. 2026-08-13 01:16 UTCGHSA enrichment
  62. 2026-08-12 14:05 UTCEG score recompute
  63. 2026-08-12 14:05 UTCVendor advisory
  64. 2026-08-12 14:05 UTCGHSA enrichment
  65. 2026-08-12 13:51 UTCEPSS rescore
  66. 2026-08-12 02:52 UTCVendor advisory
  67. 2026-08-12 02:52 UTCGHSA enrichment
  68. 2026-08-11 15:41 UTCEG score recompute
  69. 2026-08-11 15:41 UTCVendor advisory
  70. 2026-08-11 15:41 UTCGHSA enrichment
  71. 2026-08-11 04:30 UTCEG score recompute
  72. 2026-08-11 04:30 UTCVendor advisory
  73. 2026-08-11 04:30 UTCGHSA enrichment
  74. 2026-08-11 00:00 UTCEPSS rescore
  75. 2026-08-10 17:19 UTCVendor advisory

Related CVEs(same vendor + same CWE)

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 August 5, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 97.1% of all scored CVEs.
What is the CVSS score of CVE-2026-53024?
CVE-2026-53024 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
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

See which npm, PyPI, Go, and Maven packages are affected by 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