History log of /openbmc/linux/lib/lzo/lzo1x_compress_safe.c (Results 1 – 2 of 2)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
# 4d75f5c6 04-Jun-2025 Andrew Jeffery <andrew@codeconstruct.com.au>

Merge tag 'v6.6.93' into for/openbmc/dev-6.6

This is the 6.6.93 stable release


Revision tags: v6.6.93, v6.6.92, v6.6.91, v6.6.90, v6.6.89, v6.6.88, v6.6.87, v6.6.86, v6.6.85, v6.6.84, v6.6.83, v6.6.82, v6.6.81, v6.6.80
# 0acdc4d6 27-Feb-2025 Herbert Xu <herbert@gondor.apana.org.au>

crypto: lzo - Fix compression buffer overrun

[ Upstream commit cc47f07234f72cbd8e2c973cdbf2a6730660a463 ]

Unlike the decompression code, the compression code in LZO never
checked for output overrun

crypto: lzo - Fix compression buffer overrun

[ Upstream commit cc47f07234f72cbd8e2c973cdbf2a6730660a463 ]

Unlike the decompression code, the compression code in LZO never
checked for output overruns. It instead assumes that the caller
always provides enough buffer space, disregarding the buffer length
provided by the caller.

Add a safe compression interface that checks for the end of buffer
before each write. Use the safe interface in crypto/lzo.

Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: Sasha Levin <sashal@kernel.org>

show more ...