From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Nikolaus Schulz <microschulz@web.de>,
Al Viro <viro@zeniv.linux.org.uk>, Marton Balint <cus@fazekas.hu>,
Alexey Dobriyan <adobriyan@gmail.com>,
Kevin Dankwardt <k@kcomputing.com>,
Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org, stable@kernel.org
Subject: [PATCH] fat: fix buffer overflow in vfat_create_shortname()
Date: Thu, 01 Apr 2010 02:21:10 +0900 [thread overview]
Message-ID: <87wrwsh0ft.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <20100331120816.GA3430@penelope.zusammrottung.local> (Nikolaus Schulz's message of "Wed, 31 Mar 2010 14:08:16 +0200")
Nikolaus Schulz <microschulz@web.de> writes:
> Ping?
>
> I really think this should go into 2.6.34 and the next stable kernel
> updates.
I was testing a bit.
OK, please apply.
From: Nikolaus Schulz <microschulz@web.de>
When using the string representation of a random counter as part of the base
name, ensure that it is no longer than 4 bytes.
Since we are repeatedly decrementing the counter in a loop until we have found a
unique base name, the counter may wrap around zero; therefore, it is not enough
to mask its higher bits before entering the loop, this must be done inside the
loop.
[hirofumi@mail.parknet.co.jp: use snprintf()]
Signed-off-by: Nikolaus Schulz <microschulz@web.de>
Cc: stable@kernel.org
Signed-off-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
---
fs/fat/namei_vfat.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff -puN fs/fat/namei_vfat.c~fat-fix-numtail-logic fs/fat/namei_vfat.c
--- linux-2.6/fs/fat/namei_vfat.c~fat-fix-numtail-logic 2010-03-25 22:10:45.000000000 +0900
+++ linux-2.6-hirofumi/fs/fat/namei_vfat.c 2010-03-25 22:17:52.000000000 +0900
@@ -309,7 +309,7 @@ static int vfat_create_shortname(struct
{
struct fat_mount_options *opts = &MSDOS_SB(dir->i_sb)->options;
wchar_t *ip, *ext_start, *end, *name_start;
- unsigned char base[9], ext[4], buf[8], *p;
+ unsigned char base[9], ext[4], buf[5], *p;
unsigned char charbuf[NLS_MAX_CHARSET_SIZE];
int chl, chi;
int sz = 0, extlen, baselen, i, numtail_baselen, numtail2_baselen;
@@ -467,7 +467,7 @@ static int vfat_create_shortname(struct
return 0;
}
- i = jiffies & 0xffff;
+ i = jiffies;
sz = (jiffies >> 16) & 0x7;
if (baselen > 2) {
baselen = numtail2_baselen;
@@ -476,7 +476,7 @@ static int vfat_create_shortname(struct
name_res[baselen + 4] = '~';
name_res[baselen + 5] = '1' + sz;
while (1) {
- sprintf(buf, "%04X", i);
+ snprintf(buf, sizeof(buf), "%04X", i & 0xffff);
memcpy(&name_res[baselen], buf, 4);
if (vfat_find_form(dir, name_res) < 0)
break;
_
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
prev parent reply other threads:[~2010-03-31 17:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 3:50 Nikolaus Schulz
2010-03-25 5:30 ` OGAWA Hirofumi
2010-03-25 12:24 ` Nikolaus Schulz
2010-03-25 12:33 ` OGAWA Hirofumi
2010-03-25 12:52 ` OGAWA Hirofumi
2010-03-31 12:08 ` Nikolaus Schulz
2010-03-31 17:21 ` OGAWA Hirofumi [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=87wrwsh0ft.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=adobriyan@gmail.com \
--cc=cus@fazekas.hu \
--cc=hch@lst.de \
--cc=k@kcomputing.com \
--cc=linux-kernel@vger.kernel.org \
--cc=microschulz@web.de \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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
Powered by JetHome