Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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() on every per-proto timer. detach_hdlc_protocol() invokes proto->detach(dev) before kfree(hdlc->state), so timer_shutdown_sync() now runs on both free paths. timer_shutdown_sync() is used instead of timer_delete_sync() because the keepalive path re-arms the timer through add_timer()/mod_timer() and shutdown blocks any re-activation during teardown. Initialize the per-protocol timers in ppp_ioctl() when the protocol is attached, and remove the now-redundant timer_setup() from ppp_start(), so that the timers are initialized exactly once at attach time and ppp_timer_release() never operates on uninitialized timer_list structures. attach_hdlc_protocol() uses kmalloc() (not kzalloc), so struct ppp's protos[i].timer is uninitialized garbage until the first timer_setup(); without this init-at-attach, attaching the PPP protocol without ever bringing the device up would leave timer_shutdown_sync() operating on uninitialized memory in .detach. Moving the init out of ppp_start() (which only runs on NETDEV_UP) into the attach path makes the initialization unconditional and avoids initializing the same timer_list twice. This bug was found by static analysis.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-63803, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 86d80a231bde4cfb64bfbfbfffd83056fc93628f
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 8308122bc9c065b1f376e081ed300129a2ac9545
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < ce8f9ddca0c9f217342a8b49efd309aa35b81a36
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 508a0139d3bf60f6a03d2fbfb63a89a9463d983a
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < c64dbef1c0fbd36f9530aa75112acdf6a6d3cfd8
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 5a84398101bf9f11e84b176343e4e3ba83e668c0
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < a594debfd4e7ec39413647458907f689ef57fd2f
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < c78a4e41ab5ead6193ad8a2dd92e8906bae659fa
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.211 – ≤ 5.15.*
    • unaffected 6.1.177 – ≤ 6.1.*
    • unaffected 6.6.144 – ≤ 6.6.*
    • unaffected 6.12.95 – ≤ 6.12.*
    • unaffected 6.18.38 – ≤ 6.18.*
    • unaffected 7.1.3 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-63803 badge
[![CVE-2026-63803](https://cveledger.app/badge/CVE-2026-63803.svg)](https://cveledger.app/cve/CVE-2026-63803)

Record last updated .