Re: [syzbot] [jfs?] KASAN: invalid-free in sys_mount

[Mark Brown]

On Tue, Mar 21, 2023 at 10:04:46AM -0700, syzbot wrote:

> The issue was bisected to:
> 
> commit a0b6e4048228829485a43247c12c7774531728c4
> Author: Charles Keepax <ckeepax@xxxxxxxxxxxxxxxxxxxxx>
> Date:   Thu Jun 23 12:52:28 2022 +0000
> 
>     ASoC: cx20442: Remove now redundant non_legacy_dai_naming flag

> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=12756e1cc80000
> final oops:     https://syzkaller.appspot.com/x/report.txt?x=11756e1cc80000
> console output: https://syzkaller.appspot.com/x/log.txt?x=16756e1cc80000

This does not seem especially credible for the backtrace provided:

>  slab_free mm/slub.c:3787 [inline]
>  __kmem_cache_free+0xaf/0x2d0 mm/slub.c:3800
>  __do_sys_mount fs/namespace.c:3596 [inline]
>  __se_sys_mount fs/namespace.c:3571 [inline]
>  __x64_sys_mount+0x212/0x300 fs/namespace.c:3571
>  do_syscall_x64 arch/x86/entry/common.c:50 [inline]
>  do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
>  entry_SYSCALL_64_after_hwframe+0x63/0xcd

which is nowhere near ASoC, let alone that specific driver.

Attachment: signature.asc
Description: PGP signature