From: Torsten Hilbrich <torsten.hilbrich@secunet.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Sasha Levin <sashal@kernel.org>, <linux-input@vger.kernel.org>,
Brad Spengler <spender@grsecurity.net>
Subject: Re: v6.8-rc4: Crash in rmi_unregister_function still present
Date: Wed, 21 Feb 2024 08:24:32 +0100 [thread overview]
Message-ID: <2bbe3f64-8f5e-3171-96c5-95202d6015da@secunet.com> (raw)
In-Reply-To: <3401abdc-32c5-4b88-8edf-75d4683d4be0@moroto.mountain>
On 21.02.24 08:15, Dan Carpenter wrote:
> On Wed, Feb 21, 2024 at 07:55:40AM +0100, Torsten Hilbrich wrote:
>> Hello,
>>
>> updating our codebase to v6.8-rc4 which contains:
>>
>> eb988e46da2e Input: synaptics-rmi4 - fix use after free in rmi_unregister_function()
>>
>> I noticed that the previously noticed crash in the rmi4 was present again.
>>
>> Previously, we were using a fix from the grsecurity codebase which changed the function in the following way:
>>
>> void rmi_unregister_function(struct rmi_function *fn)
>> {
>> int i;
>>
>> rmi_dbg(RMI_DEBUG_CORE, &fn->dev, "Unregistering F%02X.\n",
>> fn->fd.function_number);
>>
>> for (i = 0; i < fn->num_of_irqs; i++)
>> irq_dispose_mapping(fn->irq[i]);
>>
>> device_del(&fn->dev);
>> of_node_put(fn->dev.of_node);
>> put_device(&fn->dev);
>> }
>>
>> With this version of the fix the crash didn't happen. Please note, that the crash happens in device_del which is before the irq_dispose_mapping call in eb988e46da2e.
>>
>> Attached is a kernel log from the crash with a kernel based on v6.8-rc4.
>
> Hi Torsten,
>
> Thanks for the bug report. The truth is that I don't really understand
> how IRQ mappings work. It would be simple enough to apply the same
> fix that grsecurity does. The only question how to assign authorship
> credit. Dmitry, how do you want to handle this?
The original patch was supplied to me by Brad Spengler <spender@grsecurity.net>
There is also a bugreport https://bugzilla.kernel.org/show_bug.cgi?id=215604 related to that problem.
Torsten
prev parent reply other threads:[~2024-02-21 7:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 6:55 v6.8-rc4: Crash in rmi_unregister_function still present Torsten Hilbrich
2024-02-21 7:15 ` Dan Carpenter
2024-02-21 7:24 ` Torsten Hilbrich [this message]
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=2bbe3f64-8f5e-3171-96c5-95202d6015da@secunet.com \
--to=torsten.hilbrich@secunet.com \
--cc=dan.carpenter@linaro.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=spender@grsecurity.net \
/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