From: Oliver Neukum <oneukum@suse.com>
To: Greg KH <gregkh@linuxfoundation.org>,
Nicholas Carlini <npc@anthropic.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: Stack buffer overflow (write) in kvaser_usb_leaf_wait_cmd via malicious USB
Date: Tue, 24 Feb 2026 09:44:35 +0100 [thread overview]
Message-ID: <a38ccefc-6233-4be4-bbae-0ae0d4f4499b@suse.com> (raw)
In-Reply-To: <2026021847-acclaim-coil-fe7a@gregkh>
On 18.02.26 06:12, Greg KH wrote:
> And is this the only place in this driver where it treats data in an
> untrusted way? As you know, once a driver is bound to a device, we
> trust the hardware to work properly, so this really is just a "let's be
> careful" type of fix, not any real bug to be handled as a real device
> will not trigger this.
Do we know this? I am afraid we need to make up our minds.
We are including patches that verify endpoints are present,
are of the correct type and so on.
What is the logic behind that? If we can trust that a device
is what it claims to be and operates like it is supposed to
be, why do we verify?
Regards
Oliver
next prev parent reply other threads:[~2026-02-24 8:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 2:13 Stack buffer overflow (write) in kvaser_usb_leaf_wait_cmd via malicious USB Nicholas Carlini
2026-02-18 5:12 ` Greg KH
2026-02-24 8:44 ` Oliver Neukum [this message]
2026-02-24 15:52 ` Alan Stern
2026-02-24 16:04 ` Oliver Neukum
2026-02-24 18:43 ` Alan Stern
2026-02-27 4:29 ` Greg KH
2026-02-28 2:22 ` Alan Stern
2026-10-21 16:53 ` Linux USB threat-model document Alan Stern
2026-10-21 18:26 ` Greg KH
2026-10-22 17:53 ` Alan Stern
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=a38ccefc-6233-4be4-bbae-0ae0d4f4499b@suse.com \
--to=oneukum@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=npc@anthropic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.