From: Wolfram Sang <wsa@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Marek Szyprowski <m.szyprowski@samsung.com>,
Sylwester Nawrocki <snawrocki@kernel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Tomasz Figa <tomasz.figa@gmail.com>
Subject: Re: [RESEND PATCH] i2c: s3c2410: fix possible NULL pointer deref on read message after write
Date: Fri, 28 May 2021 10:17:42 +0200 [thread overview]
Message-ID: <YLCnJgjVmJ7uMBxz@kunai> (raw)
In-Reply-To: <20210526123937.22958-1-krzysztof.kozlowski@canonical.com>
[-- Attachment #1.1: Type: text/plain, Size: 1798 bytes --]
On Wed, May 26, 2021 at 08:39:37AM -0400, Krzysztof Kozlowski wrote:
> Interrupt handler processes multiple message write requests one after
> another, till the driver message queue is drained. However if driver
> encounters a read message without preceding START, it stops the I2C
> transfer as it is an invalid condition for the controller. At least the
> comment describes a requirement "the controller forces us to send a new
> START when we change direction". This stop results in clearing the
> message queue (i2c->msg = NULL).
>
> The code however immediately jumped back to label "retry_write" which
> dereferenced the "i2c->msg" making it a possible NULL pointer
> dereference.
>
> The Coverity analysis:
> 1. Condition !is_msgend(i2c), taking false branch.
> if (!is_msgend(i2c)) {
>
> 2. Condition !is_lastmsg(i2c), taking true branch.
> } else if (!is_lastmsg(i2c)) {
>
> 3. Condition i2c->msg->flags & 1, taking true branch.
> if (i2c->msg->flags & I2C_M_RD) {
>
> 4. write_zero_model: Passing i2c to s3c24xx_i2c_stop, which sets i2c->msg to NULL.
> s3c24xx_i2c_stop(i2c, -EINVAL);
>
> 5. Jumping to label retry_write.
> goto retry_write;
>
> 6. var_deref_model: Passing i2c to is_msgend, which dereferences null i2c->msg.
> if (!is_msgend(i2c)) {"
>
> All previous calls to s3c24xx_i2c_stop() in this interrupt service
> routine are followed by jumping to end of function (acknowledging
> the interrupt and returning). This seems a reasonable choice also here
> since message buffer was entirely emptied.
>
> Addresses-Coverity: Explicit null dereferenced
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
>
Applied to for-current, thanks!
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-05-28 8:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 12:39 [RESEND PATCH] i2c: s3c2410: fix possible NULL pointer deref on read message after write Krzysztof Kozlowski
2021-05-28 8:17 ` Wolfram Sang [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=YLCnJgjVmJ7uMBxz@kunai \
--to=wsa@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=snawrocki@kernel.org \
--cc=tomasz.figa@gmail.com \
/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