diff options
| author | Theodore Ts'o <tytso@mit.edu> | 2018-06-13 00:51:28 -0400 |
|---|---|---|
| committer | Siddharth Kapoor <ksiddharth@google.com> | 2018-11-29 07:16:41 +0000 |
| commit | c72ec0abd9242daa5e1b0cdf1b78dc965d3846a2 (patch) | |
| tree | 5a6697cce74e6d182f363413c16a997bbb8d46f1 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 87a895c7cbd74650473f9a71afb9a01c64412444 (diff) | |
ext4: always verify the magic number in xattr blocks
commit 513f86d73855ce556ea9522b6bfd79f87356dc3a upstream.
If there an inode points to a block which is also some other type of
metadata block (such as a block allocation bitmap), the
buffer_verified flag can be set when it was validated as that other
metadata block type; however, it would make a really terrible external
attribute block. The reason why we use the verified flag is to avoid
constantly reverifying the block. However, it doesn't take much
overhead to make sure the magic number of the xattr block is correct,
and this will avoid potential crashes.
This addresses CVE-2018-10879.
https://bugzilla.kernel.org/show_bug.cgi?id=200001
Bug: 116406063
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Reviewed-by: Andreas Dilger <adilger@dilger.ca>
Cc: stable@kernel.org
[ghackmann@google.com: 3.18 backport: adjust context]
Signed-off-by: Greg Hackmann <ghackmann@google.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Change-Id: I29aca13d06b69577c2f83e8cc68c21e6fbbaac07
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions