PoC Monitor
← All CVEs
CVE-2026-81001published 11 Sep 2026 19:42 UTCData: JSON · API

Linux

slip: fix use-after-free in sl_sync()

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---

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.8high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= 5342b77c4123ba39f911d92a813295fb3bb21f69, < 045e307ac21fbd735b789d8817b21be4d8ead054
  • >= 5342b77c4123ba39f911d92a813295fb3bb21f69, < 87398cdec8bdf84096a8af4dbccdb04f1972f32c
  • >= 5342b77c4123ba39f911d92a813295fb3bb21f69, < e93ace1f46177a4f7b5a8e5996606cdf77e1e890
  • >= 5342b77c4123ba39f911d92a813295fb3bb21f69, < 70e20456bcbf7f3ae145bb96e5548f827a37c640
  • >= 5342b77c4123ba39f911d92a813295fb3bb21f69, < a235b20972bbd98ca1fb127d6269434edc607f19
  • >= 5342b77c4123ba39f911d92a813295fb3bb21f69, < 486577db807891d0f964fdf13c1640c7f54b0ad1
  • >= 5342b77c4123ba39f911d92a813295fb3bb21f69, < d6f25e5bd777b05880da8673daf74a8419480545
  • >= 5342b77c4123ba39f911d92a813295fb3bb21f69, < 2c4e7c42d77e78ad595dbb9e4b5886b58b45d89d

Fixed in 045e307ac21fbd735b789d8817b21be4d8ead054, 87398cdec8bdf84096a8af4dbccdb04f1972f32c, e93ace1f46177a4f7b5a8e5996606cdf77e1e890, 70e20456bcbf7f3ae145bb96e5548f827a37c640, a235b20972bbd98ca1fb127d6269434edc607f19, 486577db807891d0f964fdf13c1640c7f54b0ad1, d6f25e5bd777b05880da8673daf74a8419480545, 2c4e7c42d77e78ad595dbb9e4b5886b58b45d89d

Linux Linux
  • 2.6.32

Fixed in 0, 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, 6.18.50, 7.2.4, 7.3

Mitigation

Upgrade Linux to 045e307ac21fbd735b789d8817b21be4d8ead054 or 87398cdec8bdf84096a8af4dbccdb04f1972f32c or e93ace1f46177a4f7b5a8e5996606cdf77e1e890 or 70e20456bcbf7f3ae145bb96e5548f827a37c640 or a235b20972bbd98ca1fb127d6269434edc607f19 or 486577db807891d0f964fdf13c1640c7f54b0ad1 or d6f25e5bd777b05880da8673daf74a8419480545 or 2c4e7c42d77e78ad595dbb9e4b5886b58b45d89d or later.

Upgrade Linux to 0 or 5.10.270 or 5.15.221 or 6.1.188 or 6.6.157 or 6.12.109 or 6.18.50 or 7.2.4 or 7.3 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published11 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.