KASAN: slab-use-after-free Write in rfcomm_dev_ioctl

Status: upstream: reported on 2026/11/22 04:49
Subsystems: bluetooth
Labels: prio:normal actionable
[Documentation on labels]
Reported-by: syzbot+11542ff1d167fdffa1fc@syzkaller.appspotmail.com
First crash: 1d04h, last: 45m
✨ AI cause bisection: introduced by (AI job) :
commit 5b899241874dcc1a2b932a668731c80a3a869575
Author: Gianluca Anzolin <gianluca@sottospazio.it>
Date: Mon Jan 6 20:23:50 2014 +0000

  Bluetooth: Release RFCOMM port when the last user closes the TTY

✨ AI-generated root cause summary:

In net/bluetooth/rfcomm/tty.c, __rfcomm_dev_add() publishes a newly allocated struct rfcomm_dev in rfcomm_dev_list and releases rfcomm_dev_lock while holding only the initial port reference (refcount 1), without taking a reference for rfcomm_dev_add() to finish registration. When RFCOMM_RELEASE_ONHUP is set, a concurrent task can open and close the RFCOMM TTY device during or right after tty_port_register_device(), causing rfcomm_tty_install() to take ownership of that single reference and release_one_tty() -> rfcomm_tty_cleanup() -> tty_port_put() -> rfcomm_dev_destruct() to free dev. rfcomm_dev_add() then performs a slab-use-after-free write to dev->tty_dev (offset 992) and continues accessing the freed rfcomm_dev.

▶ ▼ ✨ Full AI root cause analysis
Based on kernel commit 909ef7a9a30f:

Root Cause Analysis

The bug is a reference-counting / premature publication race in net/bluetooth/rfcomm/tty.c between device creation in rfcomm_dev_add() (via RFCOMMCREATEDEV ioctl) and concurrent TTY open/close in rfcomm_tty_install() / rfcomm_tty_cleanup().

Involved Functions, Structs, and Fields

Triggering Sequence and Lifecycle Violation

  1. Creation and premature publication with only 1 reference: rfcomm_dev_ioctl() (RFCOMMCREATEDEV) calls rfcomm_create_dev() -> __rfcomm_create_dev() -> rfcomm_dev_add(). Inside rfcomm_dev_add() (net/bluetooth/rfcomm/tty.c:322), __rfcomm_dev_add() allocates struct rfcomm_dev *dev (kzalloc_obj), initializes dev->port via tty_port_init(&dev->port) (initial kref = 1), copies RFCOMM_RELEASE_ONHUP into dev->flags, inserts dev into rfcomm_dev_list (net/bluetooth/rfcomm/tty.c:260), unlocks rfcomm_dev_lock, and returns dev. Crucially, rfcomm_dev_add() does not hold its own extra reference on dev->port before dev becomes reachable in rfcomm_dev_list, and rfcomm_ioctl_mutex does not synchronize against TTY open/install/close paths (which only acquire rfcomm_dev_lock via rfcomm_dev_get()).

  2. Concurrent TTY install takes ownership of the sole tty_port reference: While rfcomm_dev_add() is executing tty_port_register_device(&dev->port, rfcomm_tty_driver, dev->id, NULL) (net/bluetooth/rfcomm/tty.c:328-329), or immediately after tty_port_register_device() returns before line 335, a concurrent task opens the RFCOMM TTY device (/dev/rfcomm<id>). rfcomm_tty_install() (net/bluetooth/rfcomm/tty.c:703) calls rfcomm_dev_get(tty->index), which finds dev in rfcomm_dev_list and increments dev->port refcount from 1 to 2. After tty_port_install(), lines 727-729 check:

    if (test_bit(RFCOMM_RELEASE_ONHUP, &dev->flags) &&
        !test_and_set_bit(RFCOMM_TTY_OWNED, &dev->status))
        tty_port_put(&dev->port);
    

    This drops dev->port refcount from 2 back to 1, transferring the sole remaining reference to the tty_struct (to be released on rfcomm_tty_cleanup()).

  3. TTY release frees dev while rfcomm_dev_add() is still initializing it: When the concurrent task closes the TTY, release_one_tty() (drivers/tty/tty_io.c:1497) runs on a workqueue and invokes rfcomm_tty_cleanup(tty) -> tty_port_put(&dev->port) (net/bluetooth/rfcomm/tty.c:690). This drops dev->port's refcount from 1 to 0, invoking rfcomm_dev_destruct(&dev->port), which removes dev from rfcomm_dev_list and frees dev via kfree(dev) at net/bluetooth/rfcomm/tty.c:99. Note that because dev->tty_dev is still NULL at this point, if (dev->tty_dev) tty_unregister_device(...) at lines 92-93 is skipped.

  4. Use-after-free in rfcomm_dev_add(): rfcomm_dev_add() resumes at net/bluetooth/rfcomm/tty.c:335:

    dev->tty_dev = tty;
    

    This writes 8 bytes (tty) to dev->tty_dev at offset 992 inside the already-freed kmalloc-2k struct rfcomm_dev object, triggering the KASAN slab-use-after-free write report. rfcomm_dev_add() subsequently performs additional use-after-free accesses in rfcomm_reparent_device(dev) (line 336), dev_set_drvdata(dev->tty_dev, dev) (line 337), device_create_file() (lines 339-343), and return dev->id (line 345). (Additionally, on the IS_ERR(tty) error path at line 331, tty_port_put(&dev->port) would similarly operate on a potentially freed dev.)

Fix Direction

rfcomm_dev_add() (or __rfcomm_dev_add()) must hold an extra tty_port_get(&dev->port) reference across tty_port_register_device() and the remaining initialization (dev->tty_dev = tty, rfcomm_reparent_device(dev), dev_set_drvdata(), device_create_file(), reading dev->id)β€”or defer inserting dev into rfcomm_dev_list / initialize dev->tty_dev appropriately before releasing the creation reference with tty_port_put(&dev->port). (If dev can already be torn down while rfcomm_dev_add() holds that reference, rfcomm_dev_add() / rfcomm_dev_destruct() must also ensure tty_unregister_device() is properly paired with tty_port_register_device().)

▶ ▼ ✨ AI Jobs (3)
ID Workflow Result Correct Bug Created Started Finished Revision
bf830f01 moderation Actionable: βœ… ❓ KASAN: slab-use-after-free Write in rfcomm_dev_ioctl 2026/11/22 04:17 2026/11/22 04:17 2026/11/22 04:48 b2c69459
4e48c0c4 assessment-security DenialOfService: βœ… Exploitable: βœ… FilesystemTrigger: ❌ FuzzingArtifact: ❌ MemoryCorruption: βœ… NetworkNeedsSetup: ❌ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ❌ UserNamespace: ❌ VMGuestTrigger: ❌ VMHostTrigger: ❌ ❓ KASAN: slab-use-after-free Write in rfcomm_dev_ioctl 2026/11/21 02:14 2026/11/21 02:14 2026/11/21 03:17 60a1d40d
0137c921 bisect-cause IsRelease: ❌ ❓ KASAN: slab-use-after-free Write in rfcomm_dev_ioctl 2026/11/21 02:10 2026/11/21 02:10 2026/11/21 03:13 60a1d40d
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [bluetooth?] KASAN: slab-use-after-free Write in rfcomm_dev_ioctl 0 (1) 2026/11/22 04:49

Sample crash report:
==================================================================
BUG: KASAN: slab-use-after-free in rfcomm_dev_add net/bluetooth/rfcomm/tty.c:335 [inline]
BUG: KASAN: slab-use-after-free in __rfcomm_create_dev net/bluetooth/rfcomm/tty.c:421 [inline]
BUG: KASAN: slab-use-after-free in rfcomm_create_dev net/bluetooth/rfcomm/tty.c:477 [inline]
BUG: KASAN: slab-use-after-free in rfcomm_dev_ioctl+0x1bb1/0x21c0 net/bluetooth/rfcomm/tty.c:576
Write of 
Write of size 8 at addr ffff88803a5ca488 by task syz.4.582/8261

CPU: 1 UID: 0 PID: 8261 Comm: syz.4.582 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/06/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_address_description+0x55/0x1e0 mm/kasan/report.c:378
 print_report+0x58/0x70 mm/kasan/report.c:482
 kasan_report+0x117/0x150 mm/kasan/report.c:595
 rfcomm_dev_add net/bluetooth/rfcomm/tty.c:335 [inline]
 __rfcomm_create_dev net/bluetooth/rfcomm/tty.c:421 [inline]
 rfcomm_create_dev net/bluetooth/rfcomm/tty.c:477 [inline]
 rfcomm_dev_ioctl+0x1bb1/0x21c0 net/bluetooth/rfcomm/tty.c:576
 sock_do_ioctl+0x101/0x320 net/socket.c:1328
 sock_ioctl+0x57d/0x7f0 net/socket.c:1449
 vfs_ioctl fs/ioctl.c:52 [inline]
 __do_sys_ioctl fs/ioctl.c:598 [inline]
 __se_sys_ioctl+0xff/0x170 fs/ioctl.c:584
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x171/0x540 arch/x86/entry/syscall_64.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f8414939559
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f8412b44028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f8414bb6180 RCX: 00007f8414939559
RDX: 0000200000000000 RSI: 00000000400452c8 RDI: 0000000000000006
RBP: 00007f84149c8136 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f8414bb6218 R14: 00007f8414bb6180 R15: 00007fff0689ea28
 </TASK>

Allocated by task 8261:
 kasan_save_stack mm/kasan/common.c:57 [inline]
 kasan_save_track+0x3f/0x90 mm/kasan/common.c:79
 poison_kmalloc_redzone mm/kasan/common.c:412 [inline]
 __kasan_kmalloc+0x93/0xb0 mm/kasan/common.c:429
 kasan_kmalloc include/linux/kasan.h:267 [inline]
 __kmalloc_cache_noprof+0x3d0/0x670 mm/slub.c:5680
 _kmalloc_noprof include/linux/slab.h:991 [inline]
 _kzalloc_noprof include/linux/slab.h:1312 [inline]
 __rfcomm_dev_add net/bluetooth/rfcomm/tty.c:221 [inline]
 rfcomm_dev_add net/bluetooth/rfcomm/tty.c:322 [inline]
 __rfcomm_create_dev net/bluetooth/rfcomm/tty.c:421 [inline]
 rfcomm_create_dev net/bluetooth/rfcomm/tty.c:477 [inline]
 rfcomm_dev_ioctl+0xc11/0x21c0 net/bluetooth/rfcomm/tty.c:576
 sock_do_ioctl+0x101/0x320 net/socket.c:1328
 sock_ioctl+0x57d/0x7f0 net/socket.c:1449
 vfs_ioctl fs/ioctl.c:52 [inline]
 __do_sys_ioctl fs/ioctl.c:598 [inline]
 __se_sys_ioctl+0xff/0x170 fs/ioctl.c:584
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x171/0x540 arch/x86/entry/syscall_64.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Freed by task 5743:
 kasan_save_stack mm/kasan/common.c:57 [inline]
 kasan_save_track+0x3f/0x90 mm/kasan/common.c:79
 kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:599
 poison_slab_object mm/kasan/common.c:267 [inline]
 __kasan_slab_free+0x70/0x90 mm/kasan/common.c:299
 kasan_slab_free include/linux/kasan.h:239 [inline]
 slab_free_hook mm/slub.c:2780 [inline]
 slab_free mm/slub.c:6637 [inline]
 kfree+0x1c7/0x6d0 mm/slub.c:6930
 rfcomm_dev_destruct+0x25c/0x300 net/bluetooth/rfcomm/tty.c:99
 release_one_tty+0xb4/0x280 drivers/tty/tty_io.c:1497
 process_one_work kernel/workqueue.c:3495 [inline]
 process_scheduled_works+0xc3d/0x1630 kernel/workqueue.c:3578
 worker_thread+0xa47/0xfb0 kernel/workqueue.c:3659
 kthread+0x38b/0x470 kernel/kthread.c:436
 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

The buggy address belongs to the object at ffff88803a5ca000
 which belongs to the cache kmalloc-2k of size 2048
The buggy address is located 1160 bytes inside of
 freed 2048-byte region [ffff88803a5ca000, ffff88803a5ca800)

The buggy address belongs to the physical page:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x3a5c8
head: order:3 mapcount:0 entire_mapcount:0 nr_pages_mapped:0 pincount:0
flags: 0x80000000000040(head|node=0|zone=1)
page_type: f5(slab)
raw: 0080000000000040 ffff88813ff16000 dead000000000100 dead000000000122
raw: 0000000000000000 0000000000080008 00000000f5000000 0000000000000000
head: 0080000000000040 ffff88813ff16000 dead000000000100 dead000000000122
head: 0000000000000000 0000000000080008 00000000f5000000 0000000000000000
head: 0080000000000003 fffffffffffffe01 00000000ffffffff 00000000ffffffff
head: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000008
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 3, migratetype Unmovable, gfp_mask 0xd20c0(__GFP_IO|__GFP_FS|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC), pid 4960, tgid 4960 (klogd), ts 391333836001
 set_page_owner include/linux/page_owner.h:33 [inline]
 post_alloc_hook+0x1f9/0x250 mm/page_alloc.c:1873
 prep_new_page+0x22/0xb0 mm/page_alloc.c:1881
 get_page_from_freelist+0x280d/0x2850 mm/page_alloc.c:3963
 __alloc_frozen_pages_noprof+0x230/0x470 mm/page_alloc.c:5505
 alloc_slab_page mm/slub.c:3384 [inline]
 allocate_slab+0x7d/0x5e0 mm/slub.c:3499
 new_slab mm/slub.c:3550 [inline]
 refill_objects+0x2d8/0x350 mm/slub.c:7546
 refill_sheaf mm/slub.c:2917 [inline]
 __pcs_replace_empty_main+0x339/0x690 mm/slub.c:4811
 alloc_from_pcs mm/slub.c:4887 [inline]
 slab_alloc_node mm/slub.c:5021 [inline]
 __kmalloc_cache_noprof+0x46a/0x670 mm/slub.c:5676
 _kmalloc_noprof include/linux/slab.h:991 [inline]
 syslog_print+0x103/0x610 kernel/printk/printk.c:1585
 do_syslog+0x583/0x7d0 kernel/printk/printk.c:1763
 __do_sys_syslog kernel/printk/printk.c:1855 [inline]
 __se_sys_syslog kernel/printk/printk.c:1853 [inline]
 __x64_sys_syslog+0x7c/0x90 kernel/printk/printk.c:1853
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x171/0x540 arch/x86/entry/syscall_64.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
page last free pid 7877 tgid 7877 ts 391328941417 stack trace:
 reset_page_owner include/linux/page_owner.h:26 [inline]
 __free_pages_prepare mm/page_alloc.c:1415 [inline]
 __free_frozen_pages+0xfb6/0x1090 mm/page_alloc.c:2971
 __slab_free+0x26e/0x2c0 mm/slub.c:5926
 qlink_free mm/kasan/quarantine.c:163 [inline]
 qlist_free_all+0x99/0x100 mm/kasan/quarantine.c:179
 kasan_quarantine_reduce+0x148/0x160 mm/kasan/quarantine.c:286
 __kasan_slab_alloc+0x22/0x80 mm/kasan/common.c:364
 kasan_slab_alloc include/linux/kasan.h:257 [inline]
 slab_post_alloc_hook mm/slub.c:4720 [inline]
 slab_alloc_node mm/slub.c:5033 [inline]
 kmem_cache_alloc_lru_noprof+0x358/0x680 mm/slub.c:5066
 __d_alloc+0x37/0x830 fs/dcache.c:1967
 d_alloc+0x4b/0x190 fs/dcache.c:2053
 lookup_one_qstr_excl+0xd8/0x360 fs/namei.c:1812
 __start_dirop fs/namei.c:2926 [inline]
 start_dirop+0x5c/0x90 fs/namei.c:2948
 simple_start_creating+0xcc/0x110 fs/libfs.c:2281
 debugfs_start_creating+0xca/0x1b0 fs/debugfs/inode.c:397
 debugfs_create_dir+0x24/0x350 fs/debugfs/inode.c:575
 nsim_dev_hwstats_init+0x112/0x3c0 drivers/net/netdevsim/hwstats.c:418
 nsim_drv_probe+0x87f/0xbc0 drivers/net/netdevsim/dev.c:1651
 call_driver_probe drivers/base/dd.c:-1 [inline]
 really_probe+0x254/0xae0 drivers/base/dd.c:707

Memory state around the buggy address:
 ffff88803a5ca380: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
 ffff88803a5ca400: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff88803a5ca480: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
                      ^
 ffff88803a5ca500: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
 ffff88803a5ca580: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/11/22 05:02 upstream c44104f3642d b2c69459 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root KASAN: slab-use-after-free Write in rfcomm_dev_ioctl
2026/11/21 00:58 linux-next 909ef7a9a30f b2c69459 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root KASAN: slab-use-after-free Write in rfcomm_dev_ioctl
* Struck through repros no longer work on HEAD.