From: Mikhail Zolotaryov <lebon@lebon.org.ua>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] FAT: buffer overflow with FAT12/16
Date: Wed, 20 Oct 2010 10:23:51 +0300 [thread overview]
Message-ID: <4CBE9907.5010307@lebon.org.ua> (raw)
In-Reply-To: <1287557505-3955-1-git-send-email-sbabic@denx.de>
Stefano,
you're right, sorry for that. Isn't it better to define LINEAR_PREFETCH_SIZE as
2 (blocks) and change get_vfatname() to something like that in such case:
__u8 *buflimit = cluster + ((curclust == 0) ?
LINEAR_PREFETCH_SIZE :
mydata->clust_size
) * SECTOR_SIZE;
Regards,
Mikhail
On 20.10.10 09:51, Stefano Babic wrote:
> Last commit 3831530dcb7b71329c272ccd6181f8038b6a6dd0a was intended
> "explicitly specify FAT12/16 root directory parsing buffer size, instead
> of relying on cluster size". Howver, the underlying function requires
> the size of the buffer in blocks, not in bytes, and instead of passing
> a double sector size a request for 1024 blocks is sent. This generates
> a buffer overflow with overwriting of other structure (in the case seen,
> USB structures were overwritten).
>
> Signed-off-by: Stefano Babic <sbabic@denx.de>
> CC: Mikhail Zolotaryov <lebon@lebon.org.ua>
>
> ---
> fs/fat/fat.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/fs/fat/fat.c b/fs/fat/fat.c
> index 744e961..a75e4f2 100644
> --- a/fs/fat/fat.c
> +++ b/fs/fat/fat.c
> @@ -858,7 +858,7 @@ do_fat_read (const char *filename, void *buffer, unsigned long maxsize,
> if (disk_read(cursect,
> (mydata->fatsize == 32) ?
> (mydata->clust_size) :
> - LINEAR_PREFETCH_SIZE,
> + LINEAR_PREFETCH_SIZE / SECTOR_SIZE,
> do_fat_read_block) < 0) {
> debug("Error: reading rootdir block\n");
> return -1;
prev parent reply other threads:[~2010-10-20 7:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 6:51 [U-Boot] [PATCH] FAT: buffer overflow with FAT12/16 Stefano Babic
2010-10-20 7:15 ` Wolfgang Denk
2010-10-20 7:23 ` Mikhail Zolotaryov [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=4CBE9907.5010307@lebon.org.ua \
--to=lebon@lebon.org.ua \
--cc=u-boot@lists.denx.de \
/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