From: Utkal Singh <singhutkal015@gmail.com>
To: linux-erofs@lists.ozlabs.org
Cc: hsiangkao@linux.alibaba.com, Utkal Singh <singhutkal015@gmail.com>
Subject: [PATCH] erofs-utils: lib: add capacity ceiling in deflate partial decompression
Date: Sat, 14 Mar 2026 22:35:58 +0000 [thread overview]
Message-ID: <20260314223558.33094-1-singhutkal015@gmail.com> (raw)
In z_erofs_inflate_partial(), the dynamic buffer growth loop doubles
decodedcapacity on every LIBDEFLATE_INSUFFICIENT_SPACE return with no
upper bound. A crafted DEFLATE stream can trigger repeated realloc()
calls, leading to unbounded memory consumption and an OOM crash in
fsck.erofs or erofsfuse.
Introduce Z_EROFS_MAX_DECOMP_CAPACITY (64 MiB) and check the capacity
before each doubling. If the limit is reached, log an error and abort
with -EFSCORRUPTED via the existing out_inflate_end cleanup path.
This also prevents a theoretical integer overflow on the left-shift when
decodedcapacity approaches the size_t limit.
Signed-off-by: Utkal Singh <singhutkal015@gmail.com>
---
lib/decompress.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/lib/decompress.c b/lib/decompress.c
index 3e7a173..f87efd5 100644
--- a/lib/decompress.c
+++ b/lib/decompress.c
@@ -240,6 +240,7 @@ int z_erofs_load_deflate_config(struct erofs_sb_info *sbi,
#ifdef HAVE_LIBDEFLATE
/* if libdeflate is available, use libdeflate instead. */
#include <libdeflate.h>
+#define Z_EROFS_MAX_DECOMP_CAPACITY (64U << 20) /* 64 MiB ceiling */
static int z_erofs_decompress_deflate(struct z_erofs_decompress_req *rq)
{
@@ -281,6 +282,11 @@ static int z_erofs_decompress_deflate(struct z_erofs_decompress_req *rq)
ret = -EIO;
goto out_inflate_end;
}
+ if (decodedcapacity >= Z_EROFS_MAX_DECOMP_CAPACITY) {
+ erofs_err("deflate partial decompression capacity limit exceeded");
+ ret = -EFSCORRUPTED;
+ goto out_inflate_end;
+ }
decodedcapacity = decodedcapacity << 1;
dest = realloc(buff, decodedcapacity);
if (!dest) {
--
2.43.0
reply other threads:[~2026-03-14 22:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260314223558.33094-1-singhutkal015@gmail.com \
--to=singhutkal015@gmail.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox