From: Jean Delvare <jdelvare@suse.de>
To: cve@kernel.org, linux-kernel@vger.kernel.org,
linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: CVE-2024-26827: i2c: qcom-geni: Correct I2C TRE sequence
Date: Thu, 18 Apr 2024 14:56:33 +0200 [thread overview]
Message-ID: <a1f56653f2e2be923ed47f7e968230ca8a856553.camel@suse.de> (raw)
In-Reply-To: <2024041703-CVE-2024-26827-67c1@gregkh>
Hi Greg,
On Wed, 2024-04-17 at 11:44 +0200, Greg Kroah-Hartman wrote:
> Description
> ===========
>
> In the Linux kernel, the following vulnerability has been resolved:
>
> i2c: qcom-geni: Correct I2C TRE sequence
>
> For i2c read operation in GSI mode, we are getting timeout
> due to malformed TRE basically incorrect TRE sequence
> in gpi(drivers/dma/qcom/gpi.c) driver.
> (...)
I was assigned the task to backport this security fix to the SUSE
kernels. However, from the description, I fail to see how this fix
qualifies as a security fix. I can't find the reason why a CVE was
assigned to the issue.
What is the considered attack vector? Or if there is no attack vector,
what consequence does this bug have, which would put the system
security at stake?
From my perspective, all we have here is a functional bug in newly
introduced code. It's not even a regression.
--
Jean Delvare
SUSE L3 Support
next parent reply other threads:[~2024-04-18 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024041703-CVE-2024-26827-67c1@gregkh>
2024-04-18 12:56 ` Jean Delvare [this message]
2024-04-18 13:05 ` Greg Kroah-Hartman
2024-04-18 14:44 ` Jean Delvare
2024-04-18 14:52 ` Greg Kroah-Hartman
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=a1f56653f2e2be923ed47f7e968230ca8a856553.camel@suse.de \
--to=jdelvare@suse.de \
--cc=cve@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-cve-announce@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
all inboxes | Powered by JetHome®