From: Greg KH <gregkh@linuxfoundation.org>
To: wzs <wangzhengshu39@gmail.com>
Cc: rafael@kernel.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: kernel v6.7 warn in add_uevent_var: buffer size too small
Date: Wed, 4 Dec 2024 10:41:52 +0100 [thread overview]
Message-ID: <2024120410-overact-rocking-fe93@gregkh> (raw)
In-Reply-To: <CAGXGE_JSs1iBw+EtZxsXvRrcNCmpiNFh-xFGOyzuPzXNwTatCA@mail.gmail.com>
On Wed, Dec 04, 2024 at 05:29:26PM +0800, wzs wrote:
> Hello,
> when fuzzing the Linux kernel 6.7.0,
> the following crash was triggered.
>
> kernel config : https://pastebin.com/3JeQFdUr
> console output : https://pastebin.com/9ADtBQtP
>
> Basically, we use gadget module to simulate the connection and interaction
> process of a USB device
> (device type code : 0003, vendor id : 046D, product id : C312, serial
> number : 27B4, with function : input event).
>
> It seems to be caused by a mismatch between the uevent's environmental
> limit and the buffer size used to receive the uevent, which triggers such
> kernel warning.
>
> The crash report is as follow:
> 、、、
> [203835.102225] input: wingfuz Keyboard as
> /devices/platform/dummy_hcd.0/usb3/3-1/3-1:1.0/0003:046D:C312.27B4/input/input5893
> [203835.155527] ------------[ cut here ]------------
> [203835.155533] add_uevent_var: buffer size too small
> [203835.162092] WARNING: CPU: 11 PID: 57434 at lib/kobject_uevent.c:671
> add_uevent_var+0x2fe/0x390
I think this is already fixed in newer kernel versions. 6.7.0 is very
old and obsolete. Can you test this on 6.12.1?
thanks,
greg k-h
parent reply other threads:[~2024-12-04 9:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAGXGE_JSs1iBw+EtZxsXvRrcNCmpiNFh-xFGOyzuPzXNwTatCA@mail.gmail.com>]
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=2024120410-overact-rocking-fe93@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=stable@vger.kernel.org \
--cc=wangzhengshu39@gmail.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