linux-kernel - Re: linux/rmi4 driver: "BUG: kernel NULL pointer dereference" when accessing update_fw_status or bootloader

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <47raihg6bjitnwsqbl3uja4vfnwggunyjjzxdr5ppzicvwain2@ggaoaotuxd76>
Date: Mon, 5 May 2025 16:28:26 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Hanno Böck <hanno@...eck.de>
Cc: linux-input@...r.kernel.org, linux-kernel@...r.kernel.org, 
	david@...t.cz
Subject: Re: linux/rmi4 driver: "BUG: kernel NULL pointer dereference" when
 accessing update_fw_status or bootloader_id

On Thu, May 01, 2025 at 09:50:49AM +0200, Hanno Böck wrote:
> On Wed, 30 Apr 2025 20:03:11 -0700
> Dmitry Torokhov <dmitry.torokhov@...il.com> wrote:
> 
> > Do you have anything earlier in your dmesg referencing "F34" by
> > chance?
> 
> Probably this?
> 
> [    3.297406] hub 2-1.2:1.0: 4 ports detected
> [    3.324410] rmi4_f34 rmi4-00.fn34: rmi_f34v7_probe: Unrecognized bootloader v) 16 (\x10)(
> [    3.326641] rmi4_f34 rmi4-00.fn34: probe with driver rmi4_f34 failed with error -22
> [    3.350673] rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer:
> Synaptics, product: TM3288-011, fw id: 2812761

Yes, thank you. As I expected, if F34 does not finish initialization for
some reason we are leaving the device in a bad state. I CCed you on a
patch that ties to plug the most glaring hole (but more work is needed
in that area).

Thanks.

-- 
Dmitry