[syzbot] [usb?] memory leak in f_uac2_opts_p_srate_store

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: fc02acf6ac0c Merge tag 'platform-drivers-x86-v7.2-4' of gi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11b3a49e580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ba7c2d1679fb08a2
dashboard link: https://syzkaller.appspot.com/bug?extid=87c10526d2cfa8d14ff6
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=148cd1b9580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=141f38c6580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b9d1b7c8f45c/disk-fc02acf6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a68eafefb074/vmlinux-fc02acf6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/89c624fcb62b/bzImage-fc02acf6.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+87c105...@syzkaller.appspotmail.com

2026/07/29 19:24:36 executed programs: 7
BUG: memory leak
unreferenced object 0xffff888112f1fd80 (size 64):
comm "syz.0.21", pid 5964, jiffies 4294942888
hex dump (first 32 bytes):
34 34 31 30 30 00 34 38 30 30 30 00 38 38 32 30 44100.48000.8820
30 00 39 36 30 30 30 00 31 37 36 34 30 30 00 31 0.96000.176400.1
backtrace (crc 6cdecf20):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4597 [inline]
slab_alloc_node mm/slub.c:4917 [inline]
__do_kmalloc_node mm/slub.c:5333 [inline]
__kmalloc_node_track_caller_noprof+0x3d3/0x570 mm/slub.c:5471
__kmemdup_nul mm/util.c:64 [inline]
kstrdup+0x3c/0x80 mm/util.c:84
f_uac2_opts_p_srate_store+0xbb/0x170 drivers/usb/gadget/function/f_uac2.c:2087
flush_write_buffer fs/configfs/file.c:207 [inline]
configfs_write_iter+0x10d/0x1a0 fs/configfs/file.c:229
new_sync_write fs/read_write.c:595 [inline]
vfs_write+0x3ac/0x720 fs/read_write.c:687
ksys_write+0xa5/0x170 fs/read_write.c:739
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xf8/0x610 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f

BUG: memory leak
unreferenced object 0xffff888113454dc0 (size 64):
comm "syz.0.23", pid 5967, jiffies 4294943452
hex dump (first 32 bytes):
34 34 31 30 30 00 34 38 30 30 30 00 38 38 32 30 44100.48000.8820
30 00 39 36 30 30 30 00 31 37 36 34 30 30 00 31 0.96000.176400.1
backtrace (crc 6cdecf20):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4597 [inline]
slab_alloc_node mm/slub.c:4917 [inline]
__do_kmalloc_node mm/slub.c:5333 [inline]
__kmalloc_node_track_caller_noprof+0x3d3/0x570 mm/slub.c:5471
__kmemdup_nul mm/util.c:64 [inline]
kstrdup+0x3c/0x80 mm/util.c:84
f_uac2_opts_p_srate_store+0xbb/0x170 drivers/usb/gadget/function/f_uac2.c:2087
flush_write_buffer fs/configfs/file.c:207 [inline]
configfs_write_iter+0x10d/0x1a0 fs/configfs/file.c:229
new_sync_write fs/read_write.c:595 [inline]
vfs_write+0x3ac/0x720 fs/read_write.c:687
ksys_write+0xa5/0x170 fs/read_write.c:739
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xf8/0x610 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f

connection error: failed to recv *flatrpc.ExecutorMessageRawT: EOF


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup