From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Imkanmod Khan <imkanmodkhan@gmail.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1.y] ssb: Fix potential NULL pointer dereference in ssb_device_uevent()
Date: Thu, 23 Jan 2025 15:57:28 -0500 [thread overview]
Message-ID: <20250123153451-55c7ac098ad381c7@stable.kernel.org> (raw)
In-Reply-To: <20250123083551.3400-1-imkanmodkhan@gmail.com>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: 789c17185fb0f39560496c2beab9b57ce1d0cbe7
WARNING: Author mismatch between patch and upstream commit:
Backport author: Imkanmod Khan<imkanmodkhan@gmail.com>
Commit author: Rand Deeb<rand.sec96@gmail.com>
Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: c5dc2d8eb398)
6.1.y | Not found
Note: The patch differs from the upstream commit:
---
1: 789c17185fb0f ! 1: 53b764260405d ssb: Fix potential NULL pointer dereference in ssb_device_uevent()
@@ Metadata
## Commit message ##
ssb: Fix potential NULL pointer dereference in ssb_device_uevent()
+ [ Upstream commit 789c17185fb0f39560496c2beab9b57ce1d0cbe7 ]
+
The ssb_device_uevent() function first attempts to convert the 'dev' pointer
to 'struct ssb_device *'. However, it mistakenly dereferences 'dev' before
performing the NULL check, potentially leading to a NULL pointer
@@ Commit message
Signed-off-by: Rand Deeb <rand.sec96@gmail.com>
Signed-off-by: Kalle Valo <kvalo@kernel.org>
Link: https://msgid.link/20240306123028.164155-1-rand.sec96@gmail.com
+ Signed-off-by: Imkanmod Khan <imkanmodkhan@gmail.com>
## drivers/ssb/main.c ##
@@ drivers/ssb/main.c: static int ssb_bus_match(struct device *dev, struct device_driver *drv)
- static int ssb_device_uevent(const struct device *dev, struct kobj_uevent_env *env)
+ static int ssb_device_uevent(struct device *dev, struct kobj_uevent_env *env)
{
-- const struct ssb_device *ssb_dev = dev_to_ssb_dev(dev);
-+ const struct ssb_device *ssb_dev;
+- struct ssb_device *ssb_dev = dev_to_ssb_dev(dev);
++ struct ssb_device *ssb_dev;
if (!dev)
return -ENODEV;
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
next prev parent reply other threads:[~2025-01-23 20:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 8:35 [PATCH 6.1.y] ssb: Fix potential NULL pointer dereference in ssb_device_uevent() Imkanmod Khan
2025-01-23 20:57 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-24 8:37 jianqi.ren.cn
2025-02-24 12:38 ` Sasha Levin
2025-02-24 12:54 ` Greg KH
2024-12-11 10:15 jianqi.ren.cn
2024-12-11 16:32 ` Sasha Levin
2024-12-11 9:58 jianqi.ren.cn
2024-12-11 16:32 ` Sasha Levin
2024-12-09 6:33 jianqi.ren.cn
2024-12-09 14:35 ` Sasha Levin
2024-12-06 9:32 jianqi.ren.cn
2024-12-06 17:11 ` Sasha Levin
2024-12-11 8:15 ` 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=20250123153451-55c7ac098ad381c7@stable.kernel.org \
--to=sashal@kernel.org \
--cc=imkanmodkhan@gmail.com \
--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