Vulnerability · Published Jul 19, 2026 · Assigned by Linux
CVE-2026-63918l2tp: use refcount_inc_not_zero in l2tp_session_get_by_ifname
High 7.8
In plain English
A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 6% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: l2tp: use refcount_inc_not_zero in l2tp_session_get_by_ifname A reader in l2tp_session_get_by_ifname() can return a pointer to a session whose refcount has reached zero. The getter takes its reference with plain refcount_inc(), but every other session getter in the same file (l2tp_v2_session_get, l2tp_v3_session_get, and the corresponding _get_next variants) uses refcount_inc_not_zero() because the IDR/RCU lookup can race with refcount_dec_and_test() -> l2tp_session_free() -> kfree_rcu(). The ifname getter is the only outlier; the inconsistency was raised on-list after 979c017803c4 ("l2tp: use list_del_rcu in l2tp_session_unhash"). A reader inside rcu_read_lock_bh() that matches session->ifname can be preempted between the strcmp() and the refcount_inc(). If the last reference drops on another CPU in that window, the reader's refcount_inc() runs on a counter that has reached zero. refcount_t catches the addition-on-zero, prints "refcount_t: addition on 0; use-after-free", saturates the counter, and returns the saturated pointer to the caller. Session memory is held live by the in-flight RCU read section, but the kfree_rcu() callback queued from l2tp_session_free() will free it once the grace period closes; a caller that dereferences the returned session past that point hits a slab-use-after-free. On PREEMPT_RT local_bh_disable() is a per-CPU sleeping lock and the preemption window is real; on stock PREEMPT kernels local_bh_disable() is a preempt_count increment that closes the cross-CPU race in practice (see below). Use refcount_inc_not_zero() and continue the list walk on failure, matching the other session getters in the file. The ifname getter is the only session getter in net/l2tp/ that still uses the bare refcount_inc() pattern; this change restores file-internal consistency. The success path is unchanged.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| AlmaLinux:10 | kernel | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-64k | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-64k-core | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-64k-debug | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-64k-debug-core | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-64k-debug-devel | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-64k-debug-modules | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-64k-devel | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-64k-devel-matched | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-64k-modules | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-64k-modules-core | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-64k-modules-extra | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-abi-stablelists | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-core | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-cross-headers | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-debug | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-debug-core | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-debug-devel | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-debug-devel-matched | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-debug-modules | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-debug-modules-core | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-debug-modules-extra | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-debug-uki-virt | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-devel | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-devel-matched | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-doc | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-headers | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-modules | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-modules-core | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-modules-extra | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-modules-extra-matched | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-rt | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-rt-64k | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-rt-64k-core | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-rt-64k-debug | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-rt-64k-debug-core | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-rt-64k-debug-devel | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-rt-64k-debug-modules | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-rt-64k-debug-modules-core | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-rt-64k-debug-modules-extra | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-rt-64k-devel | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-rt-64k-modules | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-rt-64k-modules-core | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-rt-64k-modules-extra | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-rt-core | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-rt-debug | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-rt-debug-core | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-rt-debug-devel | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-rt-debug-modules | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-rt-debug-modules-core | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-rt-debug-modules-extra | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-rt-devel | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-rt-modules | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-rt-modules-core | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-rt-modules-extra | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-tools | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-tools-libs | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-tools-libs-devel | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-uki-virt | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-uki-virt-addons | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-zfcpdump | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-zfcpdump-core | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-zfcpdump-devel | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-zfcpdump-devel-matched | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-zfcpdump-modules | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-zfcpdump-modules-core | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | kernel-zfcpdump-modules-extra | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | libperf | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | perf | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | python3-perf | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | rtla | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| AlmaLinux:10 | rv | 6.12.0-211.63.1.el10_2 | ALSA-2026:76738 |
| Debian:13 | linux | 6.12.94-1 | DEBIAN-CVE-2026-63918 |
| Debian:14 | linux | 7.0.12-1 | DEBIAN-CVE-2026-63918 |
| Ubuntu:26.04:LTS | linux | 7.0.0-28.28 | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:26.04:LTS | linux-aws | 7.0.0-1009.9 | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:26.04:LTS | linux-azure | 7.0.0-1010.10 | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-azure-7.0 | 7.0.0-1014.14~24.04.1 | UBUNTU-CVE-2026-63918 |
| Ubuntu:26.04:LTS | linux-azure-fde | 7.0.0-1009.9 | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-azure-fde-7.0 | 7.0.0-1013.13~24.04.1 | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:26.04:LTS | linux-gcp | 7.0.0-1008.8 | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-gcp-7.0 | 7.0.0-1011.11~24.04.1 | UBUNTU-CVE-2026-63918 |
| Ubuntu:26.04:LTS | linux-gke | 7.0.0-1003.4 | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-hwe-7.0 | 7.0.0-28.28~24.04.1 | UBUNTU-CVE-2026-63918 |
| Ubuntu:26.04:LTS | linux-ibm | 7.0.0-1010.10 | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:26.04:LTS | linux-nvidia | 7.0.0-1016.16 | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-nvidia-7.0 | 7.0.0-1016.16~24.04.1 | UBUNTU-CVE-2026-63918 |
| Ubuntu:26.04:LTS | linux-nvidia-bos | 7.0.0-2016.16 | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:26.04:LTS | linux-oem-7.0 | 7.0.0-1009.9 | UBUNTU-CVE-2026-63918 |
| Ubuntu:26.04:LTS | linux-oracle | 7.0.0-1008.8 | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-oracle-7.0 | 7.0.0-1011.11~24.04.1 | UBUNTU-CVE-2026-63918 |
| Ubuntu:26.04:LTS | linux-raspi | 7.0.0-1015.15 | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:26.04:LTS | linux-realtime | 7.0.0-28.28.1 | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:26.04:LTS | linux-riscv | 7.0.0-28.28.1 | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:24.04:LTS | linux-riscv-7.0 | 7.0.0-28.28.1~24.04.3 | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2026-63918 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2026-63918 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | abe7a1a7d0b69e63b1bca5f9531023a52336784f – before ee80455feffb9cb62b5b58715cabeff495e666b2abe7a1a7d0b69e63b1bca5f9531023a52336784f – before 947013fd7c8c35dd5856557b215840098a3f67f8abe7a1a7d0b69e63b1bca5f9531023a52336784f – before 782d60a6596aee9b29c2eecfa70033899278bf65abe7a1a7d0b69e63b1bca5f9531023a52336784f – before 05f95729ca844704d15e49ce14868af4b403b32b |
| Linux | Linux | 6.12 |