linux-ext4 - [Bug 199865] out-of-bound write in ext4_init_block_bitmap() when mounting and operating a crafted ext4 image

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: <bug-199865-13602-EJQSVYvwZy@https.bugzilla.kernel.org/>
Date:   Thu, 14 Jun 2018 05:04:22 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...nel.org
Subject: [Bug 199865] out-of-bound write in ext4_init_block_bitmap() when
 mounting and operating a crafted ext4 image

https://bugzilla.kernel.org/show_bug.cgi?id=199865

Theodore Tso (tytso@....edu) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #5 from Theodore Tso (tytso@....edu) ---
This is triggered by the fact that allocation bitmaps are marked as
uninitialized for block group #0.  Ext4 shouldn't have paid attention to these
flags, since the prerequisite file system feature (uninit_bg or metadata_csum)
was not set.  In addition, even if one of those two feature flags were set,
ext4 should report an file system corruption if bitmaps for bg 0 are marked as
uninitialized and refuse to try to clear those bitmaps, since nothing good can
happen.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.