mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Zhiling Zou <zhilinz@nebusec.ai>
Cc: linux-kernel@vger.kernel.org, kyungsik.lee@lge.com, vega@nebusec.ai
Subject: Re: [PATCH 0/1] lib: validate in-memory LZ4 chunk length
Date: Mon, 14 Sep 2026 21:45:44 -0700	[thread overview]
Message-ID: <20260914214544.071700ae78d44ca276bb3b44@linux-foundation.org> (raw)
In-Reply-To: <cover.1789219453.git.zhilinz@nebusec.ai>

On Sat, 12 Sep 2026 21:32:16 +0800 Zhiling Zou <zhilinz@nebusec.ai> wrote:

> Hi Linux kernel maintainers,
> 
> We found and validated an issue in lib/decompress_unlz4.c.

Thanks.

> The bug is
> reachable by a root user through kexec_file_load() with a crafted
> external initrd.
> 
> We've tested it, and it should not affect any other functionality.

OK.  I don't feel that a cc:stable backport is justified for this.  If
there was (or even might be) a non-root callsite then yes, backport it.

Do you agree that these:

hp2:/usr/src/linux-7.3-rc1> grep -rl unlz4 .
./lib/decompress_unlz4.c
./lib/Makefile
./lib/decompress.c
./scripts/sbom/tests/cmd_graph/test_savedcmd_parser.py
./include/linux/decompress/unlz4.h
./arch/parisc/boot/compressed/misc.c
./arch/mips/boot/compressed/decompress.c
./arch/s390/boot/decompressor.c
./arch/x86/boot/compressed/misc.c
./arch/arm/boot/compressed/decompress.c
hp2:/usr/src/linux-7.3-rc1> 

are the only callers?



      parent reply	other threads:[~2026-09-15  4:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-12 13:32 Zhiling Zou
2026-09-12 13:32 ` [PATCH 1/1] " Zhiling Zou
2026-09-15  4:45 ` Andrew Morton [this message]

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=20260914214544.071700ae78d44ca276bb3b44@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=kyungsik.lee@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vega@nebusec.ai \
    --cc=zhilinz@nebusec.ai \
    /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

all inboxes | Powered by JetHome®