public inbox for linux-arm-msm@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Andy Gross <agross@kernel.org>, Bjorn Andersson <andersson@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Missing qcom/mdt_loader.c fix for CVE-2022-40540?
Date: Tue, 18 Apr 2023 09:47:02 +0200	[thread overview]
Message-ID: <87ttxd4op5.wl-tiwai@suse.de> (raw)
In-Reply-To: <87ileq5ktl.wl-tiwai@suse.de>

On Fri, 24 Mar 2023 14:40:38 +0100,
Takashi Iwai wrote:
> 
> Hi,
> 
> I was asked about the handling for CVE-2022-40540 [*] on SUSE kernels,
> and through a quick glance, the upstream code still misses the fix.
> Namely, the downstream fix for the integer overflow check of the
> firmware size below:
>   https://git.codelinaro.org/clo/la/kernel/msm-5.10/-/commit/dae3214cd3495e5c4b37537cacf665d2cdeaea24
> ... can be applied to the current upstream code (as of 6.3-rc3) as far
> as I understand.
> 
> Could you guys check it and apply the fix if really needed?

Any news on this?  This security issue seems still present in the
latest upstream and linux-next.


thanks,

Takashi

> 
> 
> Thanks!
> 
> Takashi
> 
> [*]
>   http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40540
>   https://bugzilla.redhat.com/show_bug.cgi?id=2180513
>   https://www.cve.org/CVERecord?id=CVE-2022-40540
>   https://www.qualcomm.com/company/product-security/bulletins/march-2023-bulletin

      reply	other threads:[~2023-04-18  7:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24 13:40 Missing qcom/mdt_loader.c fix for CVE-2022-40540? Takashi Iwai
2023-04-18  7:47 ` Takashi Iwai [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=87ttxd4op5.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@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