From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: <linux-kernel@vger.kernel.org>, <linux-tip-commits@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, <x86@kernel.org>, <maz@kernel.org>
Subject: Re: [tip: irq/urgent] genirq/ipi: Fix NULL pointer deref in irq_data_get_affinity_mask()
Date: Fri, 24 Feb 2023 13:37:42 +0300 [thread overview]
Message-ID: <491f6ae2-408b-fa3a-58e1-31a7e4d9bb74@omp.ru> (raw)
In-Reply-To: <167689775708.387.18354451760866911184.tip-bot2@tip-bot2>
On 2/20/23 3:55 PM, tip-bot2 for Sergey Shtylyov wrote:
> The following commit has been merged into the irq/urgent branch of tip:
>
> Commit-ID: feabecaff5902f896531dde90646ca5dfa9d4f7d
> Gitweb: https://git.kernel.org/tip/feabecaff5902f896531dde90646ca5dfa9d4f7d
> Author: Sergey Shtylyov <s.shtylyov@omp.ru>
> AuthorDate: Wed, 17 Aug 2022 23:00:45 +03:00
> Committer: Thomas Gleixner <tglx@linutronix.de>
> CommitterDate: Mon, 20 Feb 2023 13:53:41 +01:00
>
> genirq/ipi: Fix NULL pointer deref in irq_data_get_affinity_mask()
>
> If ipi_send_{mask|single}() is called with an invalid interrupt number, all
> the local variables there will be NULL. ipi_send_verify() which is invoked
> from these functions does verify its 'data' parameter, resulting in a
^^^^
Looks like you spoiled the commit log: it should be "doesn't" -- as in my
original patch. :-/
> kernel oops in irq_data_get_affinity_mask() as the passed NULL pointer gets
> dereferenced.
>
> Add a missing NULL pointer check in ipi_send_verify()...
>
> Found by Linux Verification Center (linuxtesting.org) with the SVACE static
> analysis tool.
>
> Fixes: 3b8e29a82dd1 ("genirq: Implement ipi_send_mask/single()")
> Signed-off-by: Sergey Shtylyov <s.shtylyov@omp.ru>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Link: https://lore.kernel.org/r/b541232d-c2b6-1fe9-79b4-a7129459e4d0@omp.ru
>
>
> ---
> kernel/irq/ipi.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/irq/ipi.c b/kernel/irq/ipi.c
> index bbd945b..961d4af 100644
> --- a/kernel/irq/ipi.c
> +++ b/kernel/irq/ipi.c
> @@ -188,9 +188,9 @@ EXPORT_SYMBOL_GPL(ipi_get_hwirq);
> static int ipi_send_verify(struct irq_chip *chip, struct irq_data *data,
> const struct cpumask *dest, unsigned int cpu)
> {
> - const struct cpumask *ipimask = irq_data_get_affinity_mask(data);
> + const struct cpumask *ipimask;
>
> - if (!chip || !ipimask)
> + if (!chip || !data)
> return -EINVAL;
>
> if (!chip->ipi_send_single && !chip->ipi_send_mask)
> @@ -199,6 +199,10 @@ static int ipi_send_verify(struct irq_chip *chip, struct irq_data *data,
> if (cpu >= nr_cpu_ids)
> return -EINVAL;
>
> + ipimask = irq_data_get_affinity_mask(data);
> + if (!ipimask)
> + return -EINVAL;
> +
> if (dest) {
> if (!cpumask_subset(dest, ipimask))
> return -EINVAL;
MBR, Sergey
prev parent reply other threads:[~2023-02-24 10:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 20:00 [PATCH] irq: ipi: fix " Sergey Shtylyov
2023-02-08 18:35 ` Sergey Shtylyov
2023-02-09 10:49 ` Thomas Gleixner
2023-02-19 10:20 ` Sergey Shtylyov
2023-02-20 12:55 ` [tip: irq/urgent] genirq/ipi: Fix " tip-bot2 for Sergey Shtylyov
2023-02-24 10:37 ` Sergey Shtylyov [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=491f6ae2-408b-fa3a-58e1-31a7e4d9bb74@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=maz@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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®