CVE-2026-68398ppp: defer channel free to an RCU grace period to fix pppol2tp RX UAF
- 7.8HighCVSS base score
- 0.23%Exploitation in 30 daysEPSS · top 86% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: ppp: defer channel free to an RCU grace period to fix pppol2tp RX UAF pppol2tp_recv() runs in the L2TP UDP-encap softirq RX path: l2tp_udp_encap_recv() -> l2tp_recv_common() -> pppol2tp_recv() -> ppp_input(&po->chan) It runs under rcu_read_lock() holding only an l2tp_session reference and takes NO reference on the internal PPP channel (struct channel, chan->ppp) that ppp_input() dereferences. The pppox socket is SOCK_RCU_FREE, so 'po' and the embedded ppp_channel are RCU-safe. But the internal struct channel is a separate allocation that ppp_release_channel() frees with a plain kfree(): close(data socket) -> pppol2tp_release() -> pppox_unbind_sock() -> ppp_unregister_channel() -> ppp_release_channel() -> kfree(pch) For a channel that is bound (PPPIOCGCHAN) but not attached to a ppp unit (no PPPIOCCONNECT, pch->ppp == NULL) and not bridged, teardown skips both ppp_disconnect_channel()'s synchronize_net() and ppp_unbridge_channels()'s synchronize_rcu(), so the kfree() has no grace period. rcu_read_lock() in pppol2tp_recv() does not protect against a plain kfree(), so an in-flight ppp_input() on one CPU can dereference the channel just freed by close() on another CPU. The bug is reachable by an unprivileged user. Defer the channel free to an RCU callback via call_rcu() so the grace period fences any in-flight ppp_input(). The disconnect and unbridge teardown paths already fence with synchronize_net()/synchronize_rcu(); call_rcu() does the same here without stalling the close() path.
Timeline
ID reserved
By Linux
- 11 days later
· 11 days later
Published
- 2 months later
· 2 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.23% · top 86% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected ee40fb2e1eb5bc0ddd3f2f83c6e39a454ef5a741 – < 4e47f1ac188ece11d6fdabe44166a2776cc5bd4e
- affected ee40fb2e1eb5bc0ddd3f2f83c6e39a454ef5a741 – < 110b765744b147c63882f5e9cb12931c5dc8d85f
- affected ee40fb2e1eb5bc0ddd3f2f83c6e39a454ef5a741 – < 4bb84e964ff0fe0a171c965362de72f9820dbce9
- affected ee40fb2e1eb5bc0ddd3f2f83c6e39a454ef5a741 – < 3ab32218d7182705dae5c86f13925f458072da2c
- affected ee40fb2e1eb5bc0ddd3f2f83c6e39a454ef5a741 – < c9574b8a8edeb4edd3ac6472c27ef7184bdb2baa
- affected ee40fb2e1eb5bc0ddd3f2f83c6e39a454ef5a741 – < 06213c85d8c0994f786c093b8b2a517987943ca6
- affected ee40fb2e1eb5bc0ddd3f2f83c6e39a454ef5a741 – < ec4215683e47424c9c4762fd3c60f552a3119142
- affected d36e5ba7bbed5d7bd26e8609ffed503c2def401b
- affected 9bcc0508576b2d50efd958f2ea1c5906749c2c89
- affected c2984681fe15cfb803a9132aaaf1140ab20a72c1
- affected 5803ecd7f6ac6f747582e775caa62ac9d0489261
- affected 26f8819ddd10141ebe7bbce700fbab36bfa5f478
- affected 3.2.99 – < 3.3
- affected 3.16.54 – < 3.17
- affected 4.4.225 – < 4.5
- affected 4.9.225 – < 4.10
- affected 4.14.182 – < 4.15
- affected 4.15
- unaffected < 4.15
- unaffected 5.15.216 – ≤ 5.15.*
- unaffected 6.1.183 – ≤ 6.1.*
- unaffected 6.6.148 – ≤ 6.6.*
- unaffected 6.12.101 – ≤ 6.12.*
- unaffected 6.18.42 – ≤ 6.18.*
- unaffected 7.1.6 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References7
- https://git.kernel.org/stable/c/4e47f1ac188ece11d6fdabe44166a2776cc5bd4e (opens in a new tab)
- https://git.kernel.org/stable/c/110b765744b147c63882f5e9cb12931c5dc8d85f (opens in a new tab)
- https://git.kernel.org/stable/c/4bb84e964ff0fe0a171c965362de72f9820dbce9 (opens in a new tab)
- https://git.kernel.org/stable/c/3ab32218d7182705dae5c86f13925f458072da2c (opens in a new tab)
- https://git.kernel.org/stable/c/c9574b8a8edeb4edd3ac6472c27ef7184bdb2baa (opens in a new tab)
- https://git.kernel.org/stable/c/06213c85d8c0994f786c093b8b2a517987943ca6 (opens in a new tab)
- https://git.kernel.org/stable/c/ec4215683e47424c9c4762fd3c60f552a3119142 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-55584 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-68398)Record last updated .