Vulnerability · Published Sep 11, 2026 · Assigned by Linux

CVE-2026-81001slip: fix use-after-free in sl_sync()

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.

Severity (CVSS 3.1)7.8High
Exploit odds (30 days)0.2%top 94.3% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: slip: fix use-after-free in sl_sync() slip_devs[] stores bare net_device pointers and takes no reference on them. sl_sync() and sl_alloc() walk that table from slip_open() under rtnl_lock(), while an entry is dropped by sl_free_netdev(), which sl_setup() installs as dev->priv_destructor. priv_destructor is called from netdev_run_todo(), which deliberately runs with the RTNL semaphore released so that it can sleep while waiting for the device refcount to drop: /* Snapshot list, allow later requests */ list_replace_init(&net_todo_list, &list); __rtnl_unlock(); ... if (dev->priv_destructor) dev->priv_destructor(dev); /* slip_devs[i] = NULL */ if (dev->needs_free_netdev) free_netdev(dev); ... /* Free network device */ kobject_put(&dev->dev.kobj); So rtnl_lock() does not serialise slip_open() against the teardown at all. sl_sync() can load slip_devs[i] while the entry is still published and dereference it after netdev_run_todo() has run the destructor and released the device: CPU0 (slip_open) CPU1 (slip_close) unregister_netdev() rtnl_unlock() netdev_run_todo() __rtnl_unlock() rtnl_lock() sl_sync() dev = slip_devs[i] priv_destructor(dev) slip_devs[i] = NULL kobject_put(&dev->dev.kobj) /* dev is freed */ sl = netdev_priv(dev) if (sl->tty || sl->leased) /* use-after-free */ BUG: KASAN: use-after-free in sl_sync drivers/net/slip/slip.c:730 [inline] BUG: KASAN: use-after-free in slip_open+0xef4/0x1210 drivers/net/slip/slip.c:806 Read of size 1 at addr ffff8880712dac71 by task syz-executor.2/6506 CPU: 2 PID: 6506 Comm: syz-executor.2 Not tainted 6.1.134-syzkaller-00260-g0c8fc3469765 #0 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 Call Trace: sl_sync drivers/net/slip/slip.c:730 [inline] slip_open+0xef4/0x1210 drivers/net/slip/slip.c:806 tty_ldisc_open+0xa2/0x120 drivers/tty/tty_ldisc.c:433 tty_set_ldisc+0x324/0x720 drivers/tty/tty_ldisc.c:564 tiocsetd drivers/tty/tty_io.c:2428 [inline] tty_ioctl+0x5f0/0x1530 drivers/tty/tty_io.c:2712 Allocated by task 6502: alloc_netdev_mqs+0x98/0xfe0 net/core/dev.c:10719 sl_alloc drivers/net/slip/slip.c:756 [inline] slip_open+0x36d/0x1210 drivers/net/slip/slip.c:817 tty_ldisc_open+0xa2/0x120 drivers/tty/tty_ldisc.c:433 tty_set_ldisc+0x324/0x720 drivers/tty/tty_ldisc.c:564 Freed by task 6497: device_release+0xa2/0x240 drivers/base/core.c:2507 kobject_put+0x179/0x280 lib/kobject.c:729 netdev_run_todo+0x6c8/0xef0 net/core/dev.c:10509 slip_close+0x166/0x1c0 drivers/net/slip/slip.c:906 tty_ldisc_close+0x113/0x1a0 drivers/tty/tty_ldisc.c:456 tty_ldisc_kill+0x94/0x160 drivers/tty/tty_ldisc.c:614 tty_ldisc_release+0xe3/0x2b0 drivers/tty/tty_ldisc.c:782 tty_release+0xbcc/0xe70 drivers/tty/tty_io.c:1860 Commit e58c19124189 ("slip: Fix use-after-free Read in slip_open") fixed a different source of stale entries - a device left in slip_devs[] after slip_open() freed it on the registration error path - and does not address this race, which is why the report survives it. Drop the entry from ndo_uninit instead. unregister_netdevice() calls ndo_uninit under RTNL, before the device is queued to netdev_run_todo(), so an entry that sl_sync() can still see while holding RTNL belongs to a device that cannot be freed until RTNL is dropped. sl_free_netdev() stays only for the slip_open() error path, where register_netdevice() may have failed before ndo_init and ndo_uninit is then not called either. Both running for the same device is harmless: the ---truncated---

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.190-1DEBIAN-CVE-2026-81001
Debian:13linux6.12.111-1DEBIAN-CVE-2026-81001
Debian:14linux7.2.6-1DEBIAN-CVE-2026-81001
Debian:12linux-6.126.12.111-1~deb12u1DEBIAN-CVE-2026-81001
Ubuntu:22.04:LTSlinux5.15.0-202.212UBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-81001
Ubuntu:26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-aws5.15.0-1119.126UBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-81001
Ubuntu:26.04:LTSlinux-aws7.0.0-1016.17UBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-aws-7.0no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-azure5.15.0-1125.134UBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-81001
Ubuntu:26.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-azure-7.0no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1124.133UBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-81001
Ubuntu:26.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-azure-fde-7.0no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-gcp5.15.0-1120.130UBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-81001
Ubuntu:26.04:LTSlinux-gcp7.0.0-1016.18UBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-gcp-7.0no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-gke5.15.0-1115.121UBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-81001
Ubuntu:26.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1102.110UBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-ibm5.15.0-1113.117UBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-81001
Ubuntu:26.04:LTSlinux-ibm7.0.0-1017.17UBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1114.120UBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-kvm5.15.0-1111.116UBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-197.207UBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1114.115UBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-81001
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-nvidia-7.0no fix listedUBUNTU-CVE-2026-81001
Ubuntu:26.04:LTSlinux-nvidia-bosno fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1070.72UBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1038.42UBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1059.59UBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-81001
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1017.17UBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-oracle5.15.0-1116.122UBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-81001
Ubuntu:26.04:LTSlinux-oracle7.0.0-1015.16UBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-oracle-7.0no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-81001
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-81001
Ubuntu:26.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-81001
Ubuntu:26.04:LTSlinux-riscv7.0.0-42.42.1UBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-81001
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-81001
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-81001

Affected products (as reported)

VendorProductVersions
Linux Linux 5342b77c4123ba39f911d92a813295fb3bb21f69 – before 045e307ac21fbd735b789d8817b21be4d8ead0545342b77c4123ba39f911d92a813295fb3bb21f69 – before 87398cdec8bdf84096a8af4dbccdb04f1972f32c5342b77c4123ba39f911d92a813295fb3bb21f69 – before e93ace1f46177a4f7b5a8e5996606cdf77e1e8905342b77c4123ba39f911d92a813295fb3bb21f69 – before 70e20456bcbf7f3ae145bb96e5548f827a37c6405342b77c4123ba39f911d92a813295fb3bb21f69 – before a235b20972bbd98ca1fb127d6269434edc607f195342b77c4123ba39f911d92a813295fb3bb21f69 – before 486577db807891d0f964fdf13c1640c7f54b0ad15342b77c4123ba39f911d92a813295fb3bb21f69 – before d6f25e5bd777b05880da8673daf74a84194805455342b77c4123ba39f911d92a813295fb3bb21f69 – before 2c4e7c42d77e78ad595dbb9e4b5886b58b45d89d
Linux Linux 2.6.32

References