From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Abdun Nihaal <nihaal@cse.iitm.ac.in>
Cc: Shravan Sudhakar <s.shravan@intel.com>,
Hans de Goede <hansg@kernel.org>,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org, Sashiko <sashiko-bot@kernel.org>
Subject: Re: [PATCH 2/2] platform/x86: int1092: Fix info leak in parse_package()
Date: Tue, 21 Jul 2026 19:32:17 +0300 (EEST) [thread overview]
Message-ID: <a41c1ab7-49a3-39c8-637c-6b3011ed4a2a@linux.intel.com> (raw)
In-Reply-To: <20260713-platx86-v1-2-c8991bff03a0@cse.iitm.ac.in>
On Mon, 13 Jul 2026, Abdun Nihaal wrote:
> Sashiko reports a possible information leak due to a non-zeroized
> memory allocation for device_mode_info. Fix that by switching to use
> devm_kcalloc() for allocation.
Hi,
Please also explain here through which path the information is leaked to
permanently record it into commit itself.
You can mostly base it on Sashiko's findings but please avoid making it
too verbose (AI tends to be overly verbose about trivialities).
> Reported-by: Sashiko <sashiko-bot@kernel.org>
> Closes: https://sashiko.dev/#/patchset/20260710052806.100107-1-nihaal%40cse.iitm.ac.in
> Signed-off-by: Abdun Nihaal <nihaal@cse.iitm.ac.in>
--
i.
> ---
> Newly added in v3
> ---
> drivers/platform/x86/intel/int1092/intel_sar.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/platform/x86/intel/int1092/intel_sar.c b/drivers/platform/x86/intel/int1092/intel_sar.c
> index 7263114f0b3d..f506155f35d4 100644
> --- a/drivers/platform/x86/intel/int1092/intel_sar.c
> +++ b/drivers/platform/x86/intel/int1092/intel_sar.c
> @@ -91,10 +91,10 @@ static acpi_status parse_package(struct wwan_sar_context *context, union acpi_ob
> item->package.count <= data->total_dev_mode)
> return AE_ERROR;
>
> - data->device_mode_info = devm_kmalloc_array(&context->sar_device->dev,
> - data->total_dev_mode,
> - sizeof(*data->device_mode_info),
> - GFP_KERNEL);
> + data->device_mode_info = devm_kcalloc(&context->sar_device->dev,
> + data->total_dev_mode,
> + sizeof(*data->device_mode_info),
> + GFP_KERNEL);
> if (!data->device_mode_info)
> return AE_ERROR;
>
>
>
prev parent reply other threads:[~2026-07-21 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 11:02 [PATCH 0/2] platform/x86: int1092: Fix two bugs in SAR driver Abdun Nihaal
2026-07-13 11:02 ` [PATCH 1/2] platform/x86: int1092: Fix potential memory leak in sar_probe() Abdun Nihaal
2026-07-13 11:02 ` [PATCH 2/2] platform/x86: int1092: Fix info leak in parse_package() Abdun Nihaal
2026-07-21 16:32 ` Ilpo Järvinen [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=a41c1ab7-49a3-39c8-637c-6b3011ed4a2a@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nihaal@cse.iitm.ac.in \
--cc=platform-driver-x86@vger.kernel.org \
--cc=s.shravan@intel.com \
--cc=sashiko-bot@kernel.org \
--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®