From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Edward Adam Davis <eadavis@qq.com>
Cc: laurent.pinchart@ideasonboard.com, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, mchehab@kernel.org,
syzbot+031d0cfd7c362817963f@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH Next V2] media: mc: Clear minor number before put device
Date: Thu, 11 Sep 2025 13:43:17 +0300 [thread overview]
Message-ID: <aMKnxavyXHFJdwuq@kekkonen.localdomain> (raw)
In-Reply-To: <tencent_3DA367CA06CB92C5C64C49A4AED42ECA4C06@qq.com>
Hi Edward,
On Wed, Sep 10, 2025 at 06:31:45PM +0800, Edward Adam Davis wrote:
> syzbot report a slab-use-after-free in media_devnode_unregister.
>
> The following calltrace shows the entire process of UAF generation:
>
> hub_event()->
> port_event()->
> hub_port_connect_change()->
> hub_port_connect()->
> usb_disconnect()->
> usb_disable_device()->
> device_del()->
> bus_remove_device()->
> device_release_driver_internal()->
> __device_release_driver()->
> device_remove()->
> usb_unbind_interface()->
> em28xx_usb_disconnect()->
> em28xx_release_resources()->
> em28xx_unregister_media_device()->
> media_device_unregister()->
> media_devnode_unregister()->
> put_device()->
> media_devnode_release()->
> kfree(devnode)
> clear_bit(devnode->minor, media_devnode_nums)
>
> [1] kfree(devnode), after this code is executed, devnode is released.
> [2] clear_bit(devnode->minor, media_devnode_nums), this accesses the
> freed devnode, trigger uaf
>
> We clear the device's minor num before freeing devnode to avoid a UAF.
>
> Fixes: 9e14868dc952 ("media: mc: Clear minor number reservation at unregistration time")
> Reported-by: syzbot+031d0cfd7c362817963f@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=031d0cfd7c362817963f
> Tested-by: syzbot+031d0cfd7c362817963f@syzkaller.appspotmail.com
> Signed-off-by: Edward Adam Davis <eadavis@qq.com>
Thanks for the update. However, v1 was already merged. I'll mark this as
"not applicable".
--
Kind regards,
Sakari Ailus
prev parent reply other threads:[~2025-09-11 10:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 21:10 [syzbot] [media?] KASAN: slab-use-after-free Read in media_devnode_unregister syzbot
2025-09-10 0:42 ` Edward Adam Davis
2025-09-10 1:09 ` syzbot
2025-09-10 1:15 ` [PATCH Next] media: mc: Clear minor number before put device Edward Adam Davis
2025-09-10 9:22 ` Laurent Pinchart
2025-09-10 10:31 ` [PATCH Next V2] " Edward Adam Davis
2025-09-11 10:43 ` Sakari Ailus [this message]
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=aMKnxavyXHFJdwuq@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=eadavis@qq.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=syzbot+031d0cfd7c362817963f@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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
all inboxes | Powered by JetHome®