From: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
To: Guangshuo Li <liguangshuo@mail.sdu.edu.cn>
Cc: Lee Jones <lee@kernel.org>,
stable@vger.kernel.org, Manivannan Sadhasivam <mani@kernel.org>,
Cristian Ciocaltea <cristian.ciocaltea@gmail.com>,
linux-actions@lists.infradead.org, mfd@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/6] mfd: atc260x: Fix potential use-after-free on probe failure
Date: Sat, 31 Oct 2026 14:13:52 +0200 [thread overview]
Message-ID: <auXbgFi3pmoaYhI2@collabws.localdomain> (raw)
In-Reply-To: <344536111bef51c4ee95740e2e17af26ca26929e.1793377422.git.liguangshuo@mail.sdu.edu.cn>
On 2026/10/31, Guangshuo Li wrote:
> The IRQ chip is device-managed, but the child registration failure path
> also deletes it explicitly. Subsequent devres cleanup can then access
> the freed IRQ-chip data. Let devres perform the IRQ-chip teardown.
>
> This issue was found by our static analysis tool under development.
>
> Fixes: f7cb7fe34db9 ("mfd: Add MFD driver for ATC260x PMICs")
> Cc: stable@vger.kernel.org
> Assisted-by: OpenAI:gpt-6-astra
> Signed-off-by: Guangshuo Li <liguangshuo@mail.sdu.edu.cn>
Reviewed-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
next prev parent reply other threads:[~2026-10-31 12:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 16:54 [PATCH 0/6] mfd: Fix potential cleanup ordering and lifetime bugs Guangshuo Li
2026-10-30 16:54 ` [PATCH 1/6] mfd: da9055: Fix potential use-after-free during removal Guangshuo Li
2026-10-30 16:54 ` [PATCH 2/6] mfd: atc260x: Fix potential use-after-free on probe failure Guangshuo Li
2026-10-31 12:13 ` Cristian Ciocaltea [this message]
2026-10-30 16:54 ` [PATCH 3/6] mfd: palmas: Fix potential IRQ action leaks on removal Guangshuo Li
2026-10-30 16:54 ` [PATCH 4/6] mfd: stmpe: Fix potential use-after-free during removal Guangshuo Li
2026-10-30 16:54 ` [PATCH 5/6] mfd: stmfx: Fix potential IRQ action leaks on removal Guangshuo Li
2026-10-30 16:54 ` [PATCH 6/6] mfd: wm8994: Fix potential use-after-free during removal Guangshuo Li
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=auXbgFi3pmoaYhI2@collabws.localdomain \
--to=cristian.ciocaltea@collabora.com \
--cc=cristian.ciocaltea@gmail.com \
--cc=lee@kernel.org \
--cc=liguangshuo@mail.sdu.edu.cn \
--cc=linux-actions@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mfd@lists.linux.dev \
--cc=stable@vger.kernel.org \
/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
all inboxes | Powered by JetHome®