From: Jan Kara <jack@suse.cz>
To: Roman Smirnov <r.smirnov@omp.ru>
Cc: Jan Kara <jack@suse.com>,
linux-kernel@vger.kernel.org, Sergey Shtylyov <s.shtylyov@omp.ru>,
lvc-project@linuxtesting.org, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH v2] udf: udftime: prevent overflow in udf_disk_stamp_to_time()
Date: Wed, 10 Apr 2024 13:09:42 +0200 [thread overview]
Message-ID: <20240410110942.ajj6i3eup4ycvhml@quack3> (raw)
In-Reply-To: <20240410110406.ax4mpguev7jiszyh@quack3>
On Wed 10-04-24 13:04:06, Jan Kara wrote:
> On Wed 27-03-24 16:27:55, Roman Smirnov wrote:
> > An overflow can occur in a situation where src.centiseconds
> > takes the value of 255. This situation is unlikely, but there
> > is no validation check anywere in the code.
> >
> > Found by Linux Verification Center (linuxtesting.org) with Svace.
> >
> > Suggested-by: Jan Kara <jack@suse.cz>
> > Signed-off-by: Roman Smirnov <r.smirnov@omp.ru>
>
> Thanks! I've added the patch to my tree.
Actually, there's a small typo that needed fixing up. Corrected on commit.
> > diff --git a/fs/udf/udftime.c b/fs/udf/udftime.c
> > index 758163af39c2..3113785af3cf 100644
> > --- a/fs/udf/udftime.c
> > +++ b/fs/udf/udftime.c
> > @@ -46,13 +46,18 @@ udf_disk_stamp_to_time(struct timespec64 *dest, struct timestamp src)
> > dest->tv_sec = mktime64(year, src.month, src.day, src.hour, src.minute,
> > src.second);
> > dest->tv_sec -= offset * 60;
> > - dest->tv_nsec = 1000 * (src.centiseconds * 10000 +
> > - src.hundredsOfMicroseconds * 100 + src.microseconds);
> > +
> > /*
> > * Sanitize nanosecond field since reportedly some filesystems are
> > * recorded with bogus sub-second values.
> > */
> > - dest->tv_nsec %= NSEC_PER_SEC;
> > + if (src.centiseconds < 100 && src.hundredsOfMicroseconds < 100 &&
> > + src.microseconds < 100) {
> > + dest->tv_nsec = 1000 * (src.centiseconds * 10000 +
> > + src.hundredsOfMicroseconds * 100 + src.microseconds);
> > + } else {
> > + desk->tv_nsec = 0;
^^^^ Here
> > + }
> > }
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2024-04-10 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 13:27 Roman Smirnov
2024-03-27 15:15 ` Sergey Shtylyov
2024-04-10 11:04 ` Jan Kara
2024-04-10 11:09 ` Jan Kara [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=20240410110942.ajj6i3eup4ycvhml@quack3 \
--to=jack@suse.cz \
--cc=jack@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=r.smirnov@omp.ru \
--cc=s.shtylyov@omp.ru \
/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®