All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Paul Menzel <pmenzel+linux-usb@molgen.mpg.de>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: BUG: KASAN: use-after-free in xhci_trb_virt_to_dma.part.24+0x1c/0x80
Date: Fri, 20 Jul 2018 11:54:10 +0200	[thread overview]
Message-ID: <20180720095410.GA11904@kroah.com> (raw)
In-Reply-To: <95b4bdb2-962f-561e-ac14-79cd44395915@molgen.mpg.de>

On Fri, Jul 20, 2018 at 11:44:49AM +0200, Paul Menzel wrote:
> Dear Linux folks,
> 
> 
> Using Linux 4.18-rc5+ with kmemleak enabled on a MSI B350M MORTAR (MS-7A37)
> with an AMD Ryzen 3 2200G, the memory leak below is suspected.
> 
> ```
> $ sudo less /sys/kernel/debug/kmemleak
> unreferenced object 0xffff894f8874a2b8 (size 8):
>   comm "systemd-udevd", pid 119, jiffies 4294893109 (age 908.348s)
>   hex dump (first 8 bytes):
>     34 01 05 00 00 00 00 00                          4.......
>   backtrace:
>     [<00000000308e4456>] xhci_init+0x81/0x170 [xhci_hcd]
>     [<00000000269aa18f>] xhci_gen_setup+0x2cb/0x510 [xhci_hcd]
>     [<000000007b70d85f>] xhci_pci_setup+0x4d/0x120 [xhci_pci]
>     [<0000000059f49127>] usb_add_hcd+0x2b6/0x800 [usbcore]
>     [<000000009a16d67c>] usb_hcd_pci_probe+0x1f3/0x460 [usbcore]
>     [<0000000001295c2e>] xhci_pci_probe+0x27/0x1d7 [xhci_pci]
>     [<00000000395bd8f9>] local_pci_probe+0x41/0x90
>     [<00000000a344e362>] pci_device_probe+0x189/0x1a0
>     [<00000000318999e5>] driver_probe_device+0x2b9/0x460
>     [<00000000c29d8a55>] __driver_attach+0xdd/0x110
>     [<00000000975b7f46>] bus_for_each_dev+0x76/0xc0
>     [<000000006bc40955>] bus_add_driver+0x152/0x230
>     [<00000000840ed63c>] driver_register+0x6b/0xb0
>     [<00000000123908c4>] do_one_initcall+0x46/0x1c3
>     [<00000000ce69c793>] do_init_module+0x5a/0x210
>     [<0000000091d4aef2>] load_module+0x21c4/0x2410
> […]
> ```

That's really vague.  Any chance for a reproducer or some other types of
hints as to what you feel the problem is here?

thanks,

greg k-h

  reply	other threads:[~2018-07-20  9:54 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-20  9:44 BUG: KASAN: use-after-free in xhci_trb_virt_to_dma.part.24+0x1c/0x80 Paul Menzel
2018-07-20  9:54 ` Greg KH [this message]
2018-07-23 11:23   ` Paul Menzel
2020-01-02 14:10     ` Paul Menzel
2020-01-03 11:04       ` Mika Westerberg
2020-01-07 12:09         ` Mathias Nyman
2020-01-07 15:35           ` Paul Menzel
2020-01-08  9:34             ` Mathias Nyman
2020-01-08 15:17               ` [RFT PATCH] xhci: Fix memory leak when caching protocol extended capability PSI tables Mathias Nyman
2020-01-08 15:40                 ` Greg KH
2020-01-08 15:56                   ` Mathias Nyman
2020-02-11 10:56                 ` Marek Szyprowski
2020-02-11 12:23                   ` Greg KH
2020-02-11 12:29                     ` Mathias Nyman
2020-02-11 14:08                       ` Mathias Nyman
2020-02-11 15:01                         ` [RFT PATCH v2] " Mathias Nyman
2020-02-11 15:12                           ` Marek Szyprowski
2020-02-11 16:13                             ` Greg KH
2020-02-12  9:01                               ` Mathias Nyman
2020-02-12 17:51                                 ` Greg KH
2020-02-13 13:33                           ` Jon Hunter
2020-02-13 13:33                             ` Jon Hunter
2020-02-14  7:47                             ` Mathias Nyman
2020-02-14  8:35                               ` Jon Hunter
2020-02-14  8:35                                 ` Jon Hunter
2020-01-09  8:53         ` BUG: KASAN: use-after-free in xhci_trb_virt_to_dma.part.24+0x1c/0x80 Felipe Balbi
  -- strict thread matches above, loose matches on Subject: below --
2018-01-28 21:43 Paul Menzel
2018-01-29 11:48 ` Mathias Nyman

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=20180720095410.GA11904@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=pmenzel+linux-usb@molgen.mpg.de \
    /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.