nday
CVE-2026-81001

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

Linux / Linux

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

local
AV:L in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
no user interaction
UI:N in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
Linux kernel
affected products in the CVE record: Linux · Linux
operating system
affected products in the CVE record: Linux · Linuxthe product type of Linux kernel in nday's product registry
stage
DIS
disclosed
cvss
7.8 HIGH v3.1

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
09-11T19:42Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

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

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:L
Local: needs a local or SSH session, or a user tricked into acting on the machine
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:L
Low: ordinary user privileges
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS 3.1 vector from the CVE record, scored by the CNA Linux.

Event log

+DISdisclosed

CVE record published by Linux. CVSS 7.8, high.

src cvelist · nday , bulk import · raw
{
  "id": 446921,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-81001",
  "occurred_at": "2026-09-11T19:42:54.846Z",
  "observed_at": "2026-11-13T05:40:11.364625Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "version": "3.1",
      "base_score": 7.8,
      "base_severity": "HIGH"
    },
    "ssvc": {
      "timestamp": "2026-10-16T19:22:06.585249Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2026-09-11T19:42:54.846Z",
    "assigner_short_name": "Linux"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.