From: Shuangpeng Bai <shuangpeng.kernel@gmail.com>
To: hansg@kernel.org, ilpo.jarvinen@linux.intel.com, W_Armin@gmx.de,
Dell.Client.Kernel@dell.com, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [BUG] KASAN: slab-use-after-free in _copy_to_user from platform/x86/dell-smbios-wmi
Date: Sun, 14 Jun 2026 15:15:20 -0400 [thread overview]
Message-ID: <178144969601.60470.13396800403157907003@gmail.com> (raw)
Hi Kernel Maintainers,
I hit the following report while testing current upstream kernel:
KASAN: slab-use-after-free in _copy_to_user from platform/x86/dell-smbios-wmi
on commit: e8c2f9fdadee7cbc75134dc463c1e0d856d6e5c7 (May 25 2026)
The reproducer and .config files are here.
https://gist.github.com/shuangpengbai/f5b15c099e80897486b4238ddb91df79
I'm happy to test debug patches or provide additional information.
Reported-by: Shuangpeng Bai <shuangpeng.kernel@gmail.com>
[ 92.502430][ T8394] BUG: KASAN: slab-use-after-free in _copy_to_user (include/linux/instrumented.h:129 include/linux/uaccess.h:205 lib/usercopy.c:26)
[ 92.504528][ T8394] Read of size 8 at addr ffff888126eec360 by task dell_smbios_wmi/8394
[ 92.506899][ T8394] Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
[ 92.506905][ T8394] Call Trace:
[ 92.506914][ T8394] <TASK>
[ 92.506919][ T8394] dump_stack_lvl (lib/dump_stack.c:94 lib/dump_stack.c:120)
[ 92.506931][ T8394] print_report (mm/kasan/report.c:378 mm/kasan/report.c:482)
[ 92.506956][ T8394] kasan_report (mm/kasan/report.c:595)
[ 92.506972][ T8394] kasan_check_range (mm/kasan/generic.c:? mm/kasan/generic.c:200)
[ 92.506979][ T8394] _copy_to_user (include/linux/instrumented.h:129 include/linux/uaccess.h:205 lib/usercopy.c:26)
[ 92.506986][ T8394] simple_read_from_buffer (include/linux/uaccess.h:236 fs/libfs.c:1155)
[ 92.506998][ T8394] vfs_read (fs/read_write.c:572)
[ 92.507049][ T8394] ksys_read (fs/read_write.c:717)
[ 92.507072][ T8394] do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)
[ 92.507095][ T8394] entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)
[ 92.507163][ T8394] </TASK>
[ 92.530149][ T8394] Freed by task 8394 on cpu 0 at 92.299564s:
[ 92.530733][ T8394] kasan_save_track (mm/kasan/common.c:57 mm/kasan/common.c:78)
[ 92.531183][ T8394] kasan_save_free_info (mm/kasan/generic.c:584)
[ 92.531673][ T8394] __kasan_slab_free (mm/kasan/common.c:253 mm/kasan/common.c:285)
[ 92.532133][ T8394] kfree (include/linux/kasan.h:235 mm/slub.c:2689 mm/slub.c:6251 mm/slub.c:6566)
[ 92.532509][ T8394] devres_release_all (drivers/base/devres.c:50 drivers/base/devres.c:547 drivers/base/devres.c:576)
[ 92.533000][ T8394] device_release_driver_internal (drivers/base/dd.c:598 drivers/base/dd.c:1357 drivers/base/dd.c:1375)
[ 92.533574][ T8394] unbind_store (drivers/base/bus.c:244)
[ 92.534021][ T8394] kernfs_fop_write_iter (fs/kernfs/file.c:352)
[ 92.534531][ T8394] vfs_write (fs/read_write.c:595 fs/read_write.c:688)
[ 92.534950][ T8394] ksys_write (fs/read_write.c:740)
[ 92.535364][ T8394] do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)
[ 92.535811][ T8394] entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)
[ 92.536610][ T8394] The buggy address belongs to the object at ffff888126eec300
[ 92.536610][ T8394] which belongs to the cache kmalloc-192 of size 192
[ 92.537941][ T8394] The buggy address is located 96 bytes inside of
[ 92.537941][ T8394] freed 192-byte region [ffff888126eec300, ffff888126eec3c0)
Best,
Shuangpeng
next reply other threads:[~2026-06-14 19:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-14 19:15 Shuangpeng Bai [this message]
2026-06-15 12:19 ` Armin Wolf
2026-06-15 13:30 ` gregkh
2026-06-15 15:28 ` Arnd Bergmann
2026-06-15 20:21 ` Armin Wolf
2026-06-15 21:00 ` Arnd Bergmann
2026-06-15 22:28 ` Armin Wolf
2026-06-16 2:44 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178144969601.60470.13396800403157907003@gmail.com \
--to=shuangpeng.kernel@gmail.com \
--cc=Dell.Client.Kernel@dell.com \
--cc=W_Armin@gmx.de \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome