linux-kernel - Re: [PATCH] fat: fix buffer overflow in vfat_create

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87bpec4l8j.fsf@devron.myhome.or.jp>
Date:	Thu, 25 Mar 2010 21:52:12 +0900
From:	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
To:	Nikolaus Schulz <microschulz@....de>
Cc:	Al Viro <viro@...iv.linux.org.uk>, Marton Balint <cus@...ekas.hu>,
	Alexey Dobriyan <adobriyan@...il.com>,
	Kevin Dankwardt <k@...mputing.com>,
	Christoph Hellwig <hch@....de>, linux-kernel@...r.kernel.org,
	stable@...nel.org
Subject: Re: [PATCH] fat: fix buffer overflow in vfat_create_shortname()

OGAWA Hirofumi <hirofumi@...l.parknet.co.jp> writes:

> Nikolaus Schulz <microschulz@....de> writes:
>
>>> However, anyway, your patch is much better off than current one. So,
>>> I'll apply this in the next merge window.
>>> 
>>> Or should we apply this immediately?
>>> 
>>> Thanks.
>>
>> Given that this fixes a stack corruption which triggers the gcc stack
>> smashing protection and thus basically a crash, I vote for not
>> postponing it, but applying it immediately.
>
> Um..., where is a stack corruption? sprintf() overflow? But, it's
> actually snprintf(), not sprintf()...

Whoops, it was really sprintf().
-- 
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/