summaryrefslogtreecommitdiff
path: root/tools/build/feature/test-libbfd-buildid.c
diff options
context:
space:
mode:
authorVasily Gorbik <gor@linux.ibm.com>2023-01-30 01:47:23 +0300
committerHeiko Carstens <hca@linux.ibm.com>2023-01-31 20:54:21 +0300
commit7ab41c2c08a32132ba8c14624910e2fe8ce4ba4b (patch)
treee9f0816b94fbb11674e832cd5e12c648171c6525 /tools/build/feature/test-libbfd-buildid.c
parent32e40f9506b9e32917eb73154f93037b443124d1 (diff)
downloadlinux-7ab41c2c08a32132ba8c14624910e2fe8ce4ba4b.tar.xz
s390/decompressor: specify __decompress() buf len to avoid overflow
Historically calls to __decompress() didn't specify "out_len" parameter on many architectures including s390, expecting that no writes beyond uncompressed kernel image are performed. This has changed since commit 2aa14b1ab2c4 ("zstd: import usptream v1.5.2") which includes zstd library commit 6a7ede3dfccb ("Reduce size of dctx by reutilizing dst buffer (#2751)"). Now zstd decompression code might store literal buffer in the unwritten portion of the destination buffer. Since "out_len" is not set, it is considered to be unlimited and hence free to use for optimization needs. On s390 this might corrupt initrd or ipl report which are often placed right after the decompressor buffer. Luckily the size of uncompressed kernel image is already known to the decompressor, so to avoid the problem simply specify it in the "out_len" parameter. Link: https://github.com/facebook/zstd/commit/6a7ede3dfccb Signed-off-by: Vasily Gorbik <gor@linux.ibm.com> Tested-by: Alexander Egorenkov <egorenar@linux.ibm.com> Link: https://lore.kernel.org/r/patch-1.thread-41c676.git-41c676c2d153.your-ad-here.call-01675030179-ext-9637@work.hours Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
Diffstat (limited to 'tools/build/feature/test-libbfd-buildid.c')
0 files changed, 0 insertions, 0 deletions