Menu

Star on GitHub · 3.2k

CVE-2026-63803

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: hdlc_ppp: sync per-proto timers before freeing hdlc state Each PPP control protocol (LCP/IPCP/IPV6CP) embedded in struct ppp re…

Published Jul 19, 2026CWE-416EPSS 0.13%

Overview

CVE-2026-63803 is a high-severity vulnerability. It was published on July 19, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

hdlc_ppp: sync per-proto timers before freeing hdlc state

Each PPP control protocol (LCP/IPCP/IPV6CP) embedded in struct ppp

registers a timer via timer_setup(). That struct ppp is the

hdlc->state allocation, which detach_hdlc_protocol() frees with kfree()

in both teardown paths: unregister_hdlc_device() and the re-attach inside

attach_hdlc_protocol().

The ppp proto never registered a .detach callback, so

detach_hdlc_protocol() performs no timer synchronization before the

kfree(). The only cancel, timer_delete(&proto->timer) in ppp_cp_event(),

is partial (it does not wait for a running callback) and only runs on the

->CLOSED transition; ppp_stop()/ppp_close() do not sync either. A

ppp_timer callback already executing (blocked on ppp->lock) survives the

kfree and then dereferences proto->state / ppp->lock in freed memory,

leading to a use-after-free.

Fix this by adding a .detach helper that calls timer_shutdown_sync

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-63803?

CVE-2026-63803 is a high-severity vulnerability. It was published on July 19, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-63803?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-63803?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-63803?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-63803 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all