CVE-2026-63803: hdlc_ppp: sync per-proto timers before freeing hdlc state

Published Jul 19, 2026
·
Updated

hdlcppp: sync per-proto timers before freeing hdlc state

Affected Software

14 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=2.6.12.1<5.10.261
Linux Linux kernel>=5.11<5.15.211
Linux Linux kernel>=5.16<6.1.177
Linux Linux kernel>=6.2<6.6.144
Linux Linux kernel>=6.7<6.12.95
Linux Linux kernel>=6.13<6.18.38
Linux Linux kernel>=6.19<7.1.3
Linux Linux kernel=2.6.12
Linux Linux kernel=2.6.12-rc2
Linux Linux kernel=2.6.12-rc3
Linux Linux kernel=2.6.12-rc4
Linux Linux kernel=2.6.12-rc5
Microsoft azl3 kernel 6.6.143.1-1<6.6.150.1-1
6.6.150.1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.150.1-1
  2. Configuration

    Implement a .detach helper for each PPP control protocol (LCP/IPCP/IPV6CP) embedded in struct ppp that calls timer_shutdown_sync() to synchronize per-protocol timers before teardown frees memory (avoid use-after-free in detach_hdlc_protocol()).

    Linux kernel PPP driver (hdlc_ppp / ppp) ppp proto detach behavior for per-protocol timers (proto->detach) = Call timer_shutdown_sync() in new .detach helper before freeing/detaching state
  3. Configuration

    Move initialization of per-protocol timers out of ppp_start() into ppp_ioctl() (attach/registration path). Remove the now-redundant timer_setup() from ppp_start() so proto->timer is initialized exactly once at attach time and ppp_timer callback teardown uses synchronized shutdown.

    Linux kernel ppp protocol initialization (in struct ppp / ppp_ioctl / attach path) Per-protocol timers initialization timing = Initialize in ppp_ioctl() when protocol is selected; remove redundant timer_setup() from ppp_start()
  4. Operational

    Ensure teardown calls proto->detach(dev) (via detach_hdlc_protocol()) only after per-protocol timers have been synchronized with timer_shutdown_sync(), including both teardown paths: unregister_hdlc_device() and the re-attach/second free path where hdlc->state is freed with kfree().

Event History

Jul 19, 2026
CVE Published
via MITRE·12:02 PM
Data Sourced
via MITRE·12:02 PM
DescriptionSeverity
Data Sourced
via NVD·12:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jul 20, 2026
Data Sourced
via Microsoft·08:05 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:05 AM
Affected Software
Updated
via Microsoft·08:05 AM
DescriptionSeverity

Frequently Asked Questions

1

What is the severity of CVE-2026-63803?

CVE-2026-63803 has a high severity rating of 7.8 according to the CVSS 3.1 scoring system.

2

What does CVE-2026-63803 affect?

CVE-2026-63803 affects the Linux kernel, specifically within the hdlc_ppp component.

3

How do I fix CVE-2026-63803?

To fix CVE-2026-63803, you should update your Linux kernel to the latest version that includes the patch.

4

What is the risk associated with CVE-2026-63803?

The risk associated with CVE-2026-63803 is categorized as high, with a risk score of 72.

5

What kind of vulnerability is CVE-2026-63803 categorized as?

CVE-2026-63803 is categorized as a Use After Free vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203