All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Philipp Leskovitz <philipp.leskovitz@secunet.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: use-after-free with Lenovo Ultra Docking Station
Date: Tue, 18 Feb 2025 08:16:14 +0100	[thread overview]
Message-ID: <2025021853-stained-scared-9e60@gregkh> (raw)
In-Reply-To: <76af1506-3425-4d6a-b388-3304823fdd82@secunet.com>

On Tue, Feb 18, 2025 at 07:52:34AM +0100, Philipp Leskovitz wrote:
> [1.] One line summary of the problem:
> A use-after-free is triggered when the device ThinkPad Ultra Docking Station is connected.
> 
> [2.] Full description of the problem/report:
> 
> When I click the notebook into the docking station (ThinkPad Ultra Docking
> Station, Type 40AJ), a kernel crash sometimes occurs. I think the function
> kernfs_new_node (fs/kernfs/dir.c) accesses a memory that has already been
> released. It looks to me that an access in this function occurs with the
> query "parent->mode & S_ISGID". The error occurs with kernel version 6.8.12
> and 6.12.x.
> 
> general protection fault, probably for non-canonical address 0xfefefefefefeff3d: 0000 [#1] PREEMPT SMP NOPTI
> CPU: 7 PID: 2433 Comm: kworker/7:3 Tainted: P O T 6.8.12-grsec+ #1

6.8.12 is a very old, and obsolete, unsupported, and known-buggy kernel
version.  Does this also happen on the latest release (i.3. 6.13.3 or
our development tree (6.14-rc3)?

Lots of work has happened in the year in this driver since 6.8 was
released.

thanks,

greg k-h

  reply	other threads:[~2025-02-18  7:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18  6:52 use-after-free with Lenovo Ultra Docking Station Philipp Leskovitz
2025-02-18  7:16 ` Greg KH [this message]
2025-02-19  7:35   ` Philipp Leskovitz
2025-02-19  7:41     ` Greg KH
2025-02-20  9:34   ` Philipp Leskovitz
2025-02-20 10:17     ` Greg KH
2025-02-21  7:48       ` Philipp Leskovitz
2025-02-21  8:08         ` Greg KH
2025-02-21 11:54           ` Philipp Leskovitz

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=2025021853-stained-scared-9e60@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=philipp.leskovitz@secunet.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.