linux-ext4 - BUG? a suspected race bug at ext3_xattr_block

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 for Android: free password hash cracker in your pocket

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

Message-ID: <2014bcab0911240327r68afb4a3r6e9cf238ce0df532@mail.gmail.com>
Date:	Tue, 24 Nov 2009 20:27:41 +0900
From:	홍신 shin hong <hongshin@...il.com>
To:	linux-ext4@...r.kernel.org
Subject: BUG? a suspected race bug at ext3_xattr_block_set()

Hello.
I am reporting a suspected data race bug from ext3/xattr.c in Linux 2.6.31.

In ext3_xattr_block_set(), it accesses bs->bh->b_data
while it does not hold lock_buffer(bs->bh).

However, there is no lock_buffer(bs->bh) and unlock_buffer(bs->bh)
for guarding the access (at line 794).

Due to the lack of synchronization, it seems that data race on
bs->bh->b_data might be possible.

Please examine the code to check whether it is problematic or not.
Thank you.

Sincerely
Shin Hong
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html