CVE-2026-63803
Gravedad CVSS v3.1:
ALTA
Tipo:
No Disponible / Otro tipo
Fecha de publicación:
19/07/2026
Última modificación:
20/07/2026
Descripción
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br />
<br />
hdlc_ppp: sync per-proto timers before freeing hdlc state<br />
<br />
Each PPP control protocol (LCP/IPCP/IPV6CP) embedded in struct ppp<br />
registers a timer via timer_setup(). That struct ppp is the<br />
hdlc->state allocation, which detach_hdlc_protocol() frees with kfree()<br />
in both teardown paths: unregister_hdlc_device() and the re-attach inside<br />
attach_hdlc_protocol().<br />
<br />
The ppp proto never registered a .detach callback, so<br />
detach_hdlc_protocol() performs no timer synchronization before the<br />
kfree(). The only cancel, timer_delete(&proto->timer) in ppp_cp_event(),<br />
is partial (it does not wait for a running callback) and only runs on the<br />
->CLOSED transition; ppp_stop()/ppp_close() do not sync either. A<br />
ppp_timer callback already executing (blocked on ppp->lock) survives the<br />
kfree and then dereferences proto->state / ppp->lock in freed memory,<br />
leading to a use-after-free.<br />
<br />
Fix this by adding a .detach helper that calls timer_shutdown_sync() on<br />
every per-proto timer. detach_hdlc_protocol() invokes proto->detach(dev)<br />
before kfree(hdlc->state), so timer_shutdown_sync()<br />
now runs on both free paths.<br />
timer_shutdown_sync() is used instead of timer_delete_sync() because the<br />
keepalive path re-arms the timer through add_timer()/mod_timer() and<br />
shutdown blocks any re-activation during teardown.<br />
<br />
Initialize the per-protocol timers in ppp_ioctl() when the protocol is<br />
attached, and remove the now-redundant timer_setup() from ppp_start(), so<br />
that the timers are initialized exactly once at attach time and<br />
ppp_timer_release() never operates on uninitialized timer_list<br />
structures. attach_hdlc_protocol() uses kmalloc() (not kzalloc), so<br />
struct ppp&#39;s protos[i].timer is uninitialized garbage until the first<br />
timer_setup(); without this init-at-attach, attaching the PPP protocol<br />
without ever bringing the device up would leave timer_shutdown_sync()<br />
operating on uninitialized memory in .detach. Moving the init out of<br />
ppp_start() (which only runs on NETDEV_UP) into the attach path makes the<br />
initialization unconditional and avoids initializing the same timer_list<br />
twice.<br />
<br />
This bug was found by static analysis.
Impacto
Puntuación base 3.x
7.80
Gravedad 3.x
ALTA
Referencias a soluciones, herramientas e información
- https://git.kernel.org/stable/c/508a0139d3bf60f6a03d2fbfb63a89a9463d983a
- https://git.kernel.org/stable/c/5a84398101bf9f11e84b176343e4e3ba83e668c0
- https://git.kernel.org/stable/c/8308122bc9c065b1f376e081ed300129a2ac9545
- https://git.kernel.org/stable/c/a594debfd4e7ec39413647458907f689ef57fd2f
- https://git.kernel.org/stable/c/c64dbef1c0fbd36f9530aa75112acdf6a6d3cfd8
- https://git.kernel.org/stable/c/c78a4e41ab5ead6193ad8a2dd92e8906bae659fa
- https://git.kernel.org/stable/c/ce8f9ddca0c9f217342a8b49efd309aa35b81a36



