CVE-2026-63797

HIGHPre-NVD 8.48.4
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: None knownExposed: 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:

rpmsg: char: Fix use-after-free on probe error path

rpmsg_chrdev_probe() stores the newly allocated eptdev in the default endpoint's priv pointer before calling rpmsg_chrdev_eptdev_add(). If rpmsg_chrdev_eptdev_add() then fails, its error path frees eptdev while the default endpoint may still dispatch callbacks with the stale priv pointer.

Avoid publishing eptdev through the default endpoint until rpmsg_chrdev_eptdev_add() succeeds. Messages received before the priv pointer is published should be ignored by rpmsg_ept_cb(). Flow-control updates can hit rpmsg_ept_flow_cb() in the same window, so make both callbacks return success when priv is NULL.

CVSS v3
8.4
EG Score
8.4(high)
EG Risk
42(Track)
EG Risk 42/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
Severity84% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

July 19, 2026

Last Modified

July 24, 2026

Advisory Details (5)

Auto-updated Jul 20, 2026
No patch confirmed yet.
generic

rpmsg: char: Fix use-after-free on probe error path - kernel/git/stable/linux.git - Linux kernel stable tree

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

rpmsg: char: Fix use-after-free on probe error path - kernel/git/stable/linux.git - Linux kernel stable tree

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

rpmsg: char: Fix use-after-free on probe error path - kernel/git/stable/linux.git - Linux kernel stable tree

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

rpmsg: char: Fix use-after-free on probe error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1ff3f528e67d20e2b1483dcaba899dc7832b2e6b
generic

rpmsg: char: Fix use-after-free on probe error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/104d100212396801f1d9d388282f746e23e2bfd6

Vendor Advisories for CVE-2026-63797(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 24× in last 7d / 27× 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-27 04:35 UTCGHSA enrichment
  2. 2026-07-26 16:30 UTCEG score recompute
  3. 2026-07-26 16:30 UTCGHSA enrichment
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-26 04:32 UTCEG score recompute
  7. 2026-07-26 04:32 UTCGHSA enrichment
  8. 2026-07-25 14:18 UTCEPSS rescore
  9. 2026-07-25 14:18 UTCEPSS rescore
  10. 2026-07-24 14:18 UTCEPSS rescore
  11. 2026-07-24 14:18 UTCEPSS rescore
  12. 2026-07-23 14:18 UTCEPSS rescore
  13. 2026-07-23 14:18 UTCEPSS rescore
  14. 2026-07-23 03:22 UTCEG score recompute
  15. 2026-07-22 14:08 UTCEPSS rescore
  16. 2026-07-22 14:08 UTCEPSS rescore
  17. 2026-07-21 15:25 UTCEPSS rescore
  18. 2026-07-21 15:25 UTCEPSS rescore
  19. 2026-07-20 17:46 UTCEG score recompute
  20. 2026-07-20 17:46 UTCGHSA enrichment
  21. 2026-07-20 17:08 UTCEPSS rescore
  22. 2026-07-20 14:46 UTCEG score recompute 8.40
  23. 2026-07-20 14:45 UTCGHSA enrichment
  24. 2026-07-20 14:32 UTCMITRE cvelistV5CVSS v3 → 8.4 · severity → HIGH
  25. 2026-07-19 12:26 UTCNVD update
Show 2 more
  1. 2026-07-19 12:14 UTCEG score recompute
  2. 2026-07-19 12:10 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-63797?
CVE-2026-63797 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: rpmsg: char: Fix use-after-free on probe error path rpmsgchrdevprobe() stores the newly allocated eptdev in the default endpoint's priv pointer before calling rpmsgchrdeveptdev_add(). If rpmsgchrdeveptdev_add() then fails, its…
When was CVE-2026-63797 disclosed?
CVE-2026-63797 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63797 actively exploited?
CVE-2026-63797 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 96.4% of all scored CVEs.
What is the CVSS score of CVE-2026-63797?
CVE-2026-63797 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-63797?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63797, 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-63797

Explore →

Is Your Infrastructure Affected by CVE-2026-63797?

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