Skip to content
Systems

CVE-2026-63797

8.4
High
EPSS 0.15%Patch availableJul 21, 2026

Linux kernel rpmsg use-after-free allowing kernel crash or local privilege escalation

common questions

Is CVE-2026-63797 being exploited?

Not confirmed. CVE-2026-63797 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.15% probability of exploitation in the next 30 days.

How severe is CVE-2026-63797?

CVE-2026-63797 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-63797?

Yes. A fix has been recorded for CVE-2026-63797. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-63797 affect?

CVE-2026-63797 affects Linux kernel (rpmsg char driver), Embedded/SoC devices using remoteproc/rpmsg, Linux distributions with rpmsg-enabled kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-63797?

Install kernel updates with rpmsg probe-path fix or apply vendor backport and reboot devices.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (rpmsg char driver)Embedded/SoC devices using remoteproc/rpmsgLinux distributions with rpmsg-enabled kernels
impact

Malformed rpmsg messages can trigger a kernel use-after-free in the rpmsg char driver, causing crash (DoS) or possible local privilege escalation.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= bc69d10665690492421d926b1cd9a7a36bffd691 and < 1306fc4f76f765727a6d5aefbf08ef0c8f32996f
  • affected>= bc69d10665690492421d926b1cd9a7a36bffd691 and < ddf13f91ca82c94ef7ad9c41a434a03313f8eb1b
  • affected>= bc69d10665690492421d926b1cd9a7a36bffd691 and < c5ebb06c7e24d531b68707168e04698859d642bc
  • affected>= bc69d10665690492421d926b1cd9a7a36bffd691 and < 104d100212396801f1d9d388282f746e23e2bfd6
  • affected>= bc69d10665690492421d926b1cd9a7a36bffd691 and < ff268cd9ccbce6472a0658791b417bf11c31ee39
  • affected>= bc69d10665690492421d926b1cd9a7a36bffd691 and < 1ff3f528e67d20e2b1483dcaba899dc7832b2e6b
  • affected5.18
vendor says fixed in< 5.18, >= 6.1.178 and <= 6.1.*, >= 6.6.144 and <= 6.6.*, >= 6.12.95 and <= 6.12.*, >= 6.18.38 and <= 6.18.*, >= 7.1.3 and <= 7.1.*, >= 7.2 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free