From: Sergey Shtylyov <s.shtylyov@auroraos.dev>
To: Ilya Krutskih <devsec@tpz.ru>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: <lvc-project@linuxtesting.org>, Kees Cook <kees@kernel.org>,
Hans Verkuil <hverkuil+cisco@kernel.org>,
Patrick Boettcher <pboettcher@dibcom.fr>,
Olivier Grenie <Olivier.Grenie@dibcom.fr>,
<linux-media@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>
Subject: Re: [PATCH] media: dib8000: validate SNR exponent before shifting
Date: Thu, 22 Oct 2026 22:13:49 +0300 [thread overview]
Message-ID: <04a4490d-ac6e-4e90-bec4-dd3c0525e62d@auroraos.dev> (raw)
In-Reply-To: <20261022172308.224576-1-devsec@tpz.ru>
On 10/22/26 8:23 PM, Ilya Krutskih wrote:
Please consider using --no-git-fallback with scripts/get_maintainer.pl --
I don't see what do I have to do with this patch (other than fixing another
bug in this driver earlier).
> Decode the SNR exponent as a signed value instead of storing it in a
> u32.
I don't see where are you changing the type from u32 in this version of
patch -- this phrase seems to be copied from the 1st (internal) version...
> Subtracting 0x40 from the unsigned exponent currently causes it
> to wrap around when the encoded value represents a negative number.
Seems to be the intended effect...
> Keep the signal and noise mantissas unsigned, as they are used in
> unsigned fixed-point arithmetic.
Again, this phrase seems to be (mindlessly?) copied from the 1st
version... :-)
> Check exponent values before shifting by check_shl_overflow().
Yes, that's what the patch below actually does! :-)
> Return the existing invalid SNR value when the exponent cannot be
> represented safely.
>
> Fixes: 77e2c0f5d471 ("V4L/DVB (12900): DiB8000: added support for DiBcom ISDB-T/ISDB-Tsb demodulator DiB8000")
> Cc: stable@vger.kernel.org
> Signed-off-by: Ilya Krutskih <devsec@tpz.ru>
> ---
> drivers/media/dvb-frontends/dib8000.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/media/dvb-frontends/dib8000.c b/drivers/media/dvb-frontends/dib8000.c
> index d291113291e0..442ec06e34dc 100644
> --- a/drivers/media/dvb-frontends/dib8000.c
> +++ b/drivers/media/dvb-frontends/dib8000.c
[...]> @@ -3873,7 +3874,8 @@ static u32 dib8000_get_snr(struct dvb_frontend *fe)
> exp = (val & 0x3f);
> if ((exp & 0x20) != 0)
> exp -= 0x40;
> - n <<= exp+16;
> + if (check_shl_overflow(n, exp + 16, &n))
The question is whether the hardware can actually return exp < -16 or > 15...
> + return 0xffffffff;
>
> if (state->revision != 0x8090)
> val = dib8000_read_word(state, 543);
> @@ -3883,7 +3885,8 @@ static u32 dib8000_get_snr(struct dvb_frontend *fe)
> exp = (val & 0x3f);
> if ((exp & 0x20) != 0)
> exp -= 0x40;
> - s <<= exp+16;
> + if (check_shl_overflow(s, exp + 16, &s))
> + return 0xffffffff;
>
> if (n > 0) {
> u32 t = (s/n) << 16;[...]
MBR, Sergey
prev parent reply other threads:[~2026-10-22 19:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 17:23 Ilya Krutskih
2026-10-22 19:13 ` 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=04a4490d-ac6e-4e90-bec4-dd3c0525e62d@auroraos.dev \
--to=s.shtylyov@auroraos.dev \
--cc=Olivier.Grenie@dibcom.fr \
--cc=devsec@tpz.ru \
--cc=hverkuil+cisco@kernel.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=mchehab@kernel.org \
--cc=pboettcher@dibcom.fr \
--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®