From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Richard Weinberger <richard@nod.at>
Subject: Re: [PATCH 0/6] squashfs: harden against crafted metadata
Date: Fri, 19 Jul 2024 08:36:28 +0200 [thread overview]
Message-ID: <172137098860.579873.6891369070499064659.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20240717063328.2810835-1-a.fatoum@pengutronix.de>
On Wed, 17 Jul 2024 08:33:22 +0200, Ahmad Fatoum wrote:
> Richard reports[1] that barebox is susceptible to a number of memory safety
> issues when parsing crafted squashfs files, which have been fixed in the
> upstream Linux implementation in the meantime.
>
> Import the mentioned commits from Linux to fix this:
>
> 01cfb7937a9af ("squashfs: be more careful about metadata corruption")
> d512584780d3e ("squashfs: more metadata hardening")
> cdbb65c4c7ead ("squashfs metadata 2: electric boogaloo")
> 71755ee5350b6 ("squashfs: more metadata hardening")
> a3f94cb99a854 ("Squashfs: Compute expected length from inode size rather than block length")
>
> [...]
Applied, thanks!
[1/6] squashfs: be more careful about metadata corruption
https://git.pengutronix.de/cgit/barebox/commit/?id=526642ffecd0 (link may not be stable)
[2/6] squashfs: more metadata hardening
https://git.pengutronix.de/cgit/barebox/commit/?id=2b601e956dc6 (link may not be stable)
[3/6] squashfs metadata 2: electric boogaloo
https://git.pengutronix.de/cgit/barebox/commit/?id=2bd8da6174f7 (link may not be stable)
[4/6] squashfs: more metadata hardening
https://git.pengutronix.de/cgit/barebox/commit/?id=2b601e956dc6 (link may not be stable)
[5/6] Squashfs: Compute expected length from inode size rather than block length
https://git.pengutronix.de/cgit/barebox/commit/?id=0f180583cb2d (link may not be stable)
[6/6] squashfs: refuse mount of squashfs images with non-128K block size
https://git.pengutronix.de/cgit/barebox/commit/?id=56d5844b1c83 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2024-07-19 6:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 6:33 Ahmad Fatoum
2024-07-17 6:33 ` [PATCH 1/6] squashfs: be more careful about metadata corruption Ahmad Fatoum
2024-07-17 6:33 ` [PATCH 2/6] squashfs: more metadata hardening Ahmad Fatoum
2024-07-17 6:33 ` [PATCH 3/6] squashfs metadata 2: electric boogaloo Ahmad Fatoum
2024-07-17 6:33 ` [PATCH 4/6] squashfs: more metadata hardening Ahmad Fatoum
2024-07-17 6:33 ` [PATCH 5/6] Squashfs: Compute expected length from inode size rather than block length Ahmad Fatoum
2024-07-17 6:33 ` [PATCH 6/6] squashfs: refuse mount of squashfs images with non-128K block size Ahmad Fatoum
2024-07-19 6:36 ` Sascha Hauer [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=172137098860.579873.6891369070499064659.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=richard@nod.at \
/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