diff options
author | Theodore Ts'o <tytso@mit.edu> | 2018-06-14 07:58:00 +0300 |
---|---|---|
committer | Theodore Ts'o <tytso@mit.edu> | 2018-06-14 07:58:00 +0300 |
commit | 8844618d8aa7a9973e7b527d038a2a589665002c (patch) | |
tree | 73e3eeb52d03d548d6cab2c600984f07a72b9e10 /fs/jfs/namei.c | |
parent | 77260807d1170a8cf35dbb06e07461a655f67eee (diff) | |
download | linux-8844618d8aa7a9973e7b527d038a2a589665002c.tar.xz |
ext4: only look at the bg_flags field if it is valid
The bg_flags field in the block group descripts is only valid if the
uninit_bg or metadata_csum feature is enabled. We were not
consistently looking at this field; fix this.
Also block group #0 must never have uninitialized allocation bitmaps,
or need to be zeroed, since that's where the root inode, and other
special inodes are set up. Check for these conditions and mark the
file system as corrupted if they are detected.
This addresses CVE-2018-10876.
https://bugzilla.kernel.org/show_bug.cgi?id=199403
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Cc: stable@kernel.org
Diffstat (limited to 'fs/jfs/namei.c')
0 files changed, 0 insertions, 0 deletions