From: Hank Yang <s950343@gmail.com>
To: marvin24@gmx.de
Cc: gregkh@linuxfoundation.org, ac100@lists.launchpad.net,
linux-tegra@vger.kernel.org, linux-staging@lists.linux.dev,
Hank Yang <s950343@gmail.com>
Subject: [PATCH] staging: nvec: fix race between power-off callback and driver removal
Date: Sun, 6 Sep 2026 21:15:29 +0800 [thread overview]
Message-ID: <20260906131529.11422-1-s950343@gmail.com> (raw)
tegra_nvec_remove() checks pm_power_off against nvec_power_off and
then clears it in two separate steps:
if (pm_power_off == nvec_power_off)
pm_power_off = NULL;
If a shutdown is triggered between the check and the clear, the
system's power-off path can call nvec_power_off() while
tegra_nvec_remove() is concurrently tearing down the device (freeing
resources via mfd_remove_devices(), cancel_work_sync(), etc.),
leading to a use-after-free on nvec_power_handle.
Use cmpxchg() to make the check-and-clear atomic, closing this race
window.
Compile-tested (ARM, tegra_defconfig) only; I don't have access to
Tegra Paz00 hardware to test this at runtime.
Assisted-by: Claude:claude-sonnet-5
Signed-off-by: Hank Yang <s950343@gmail.com>
---
drivers/staging/nvec/nvec.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/staging/nvec/nvec.c b/drivers/staging/nvec/nvec.c
index 41cbdfdc1da6..b9ebfdf46002 100644
--- a/drivers/staging/nvec/nvec.c
+++ b/drivers/staging/nvec/nvec.c
@@ -906,8 +906,7 @@ static void tegra_nvec_remove(struct platform_device *pdev)
nvec_unregister_notifier(nvec, &nvec->nvec_status_notifier);
cancel_work_sync(&nvec->rx_work);
cancel_work_sync(&nvec->tx_work);
- if (pm_power_off == nvec_power_off)
- pm_power_off = NULL;
+ cmpxchg(&pm_power_off, nvec_power_off, NULL);
}
#ifdef CONFIG_PM_SLEEP
--
2.43.0
next reply other threads:[~2026-09-06 13:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 13:15 Hank Yang [this message]
2026-09-07 14:24 ` [PATCH] staging: nvec: fix race between power-off callback and driver removal Greg KH
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=20260906131529.11422-1-s950343@gmail.com \
--to=s950343@gmail.com \
--cc=ac100@lists.launchpad.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-tegra@vger.kernel.org \
--cc=marvin24@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox