ppp_synctty: ensure a writeable skb header (Linux Linux)

CVE-2026-97964
Non disponible

En bref

Source
NVD
EPSS
EPSS 0.17 % · centile 7 ()
État
PUBLISHED
Publiée
Mise à jour
Attribuée par
Linux
Statut NVD
Received

Description

In the Linux kernel, the following vulnerability has been resolved: ppp_synctty: ensure a writeable skb header ppp_sync_txmunge() checks headroom before prepending the address and control bytes, but does not ensure that the skb header is writable. A received skb can reach this function through PPP channel bridging without passing through ppp_start_xmit(), which calls skb_cow_head(). For example, a PPPoE frame may share its buffer with a clone queued to an AF_PACKET socket. If it is bridged to a synchronous tty channel, the address/control bytes can overwrite data still visible to that socket. Use skb_cow_head() to ensure both sufficient headroom and a writable header.

Références

Références européennes

Avis du CERT-FR

Produits affectés

ProduitVersions
Linux · Linuxaffected 4cf476ced45d7f12df30a68e833b263e7a2202d1 < 25e03eeead2c49748c7582dfb64c205f93a42d00 ; affected 4cf476ced45d7f12df30a68e833b263e7a2202d1 < a256f9925288ef47de8febed5c38d5cc21340211 ; affected 4cf476ced45d7f12df30a68e833b263e7a2202d1 < 7953946f68262a8bb137aa101249adef6e029652 ; affected 4cf476ced45d7f12df30a68e833b263e7a2202d1 < 3af7797fbabc84992e0ca5ad2bc0ca8537d053ef ; affected 4cf476ced45d7f12df30a68e833b263e7a2202d1 < 0996c3e6bcc6ae08cb371ed43648c9f7f748ae6e ; affected 4cf476ced45d7f12df30a68e833b263e7a2202d1 < 15d0a6c9a42df2d745c37510dba828f6dbe60d9f
Linux · Linuxaffected 5.11 ; unaffected 0 < 5.11 ; unaffected 5.15.222 ≤ 5.15.* ; unaffected 6.1.189 ≤ 6.1.* ; unaffected 6.6.158 ≤ 6.6.* ; unaffected 6.12.111 ≤ 6.12.*

Sources

SourceLicence
CVE List (CVEProject cvelistV5)CVE Program Terms of Use
EPSS (FIRST.org)FIRST — attribution requested
ENISA EUVDENISA — reproduction authorised, source acknowledged
CERT-FR (ANSSI)Licence Ouverte / Etalab 2.0
NVD (NIST) via fkie-cad/nvd-json-data-feedsPublic domain — this product uses data from the NVD API but is not endorsed or certified by the NVD