From: Sascha Hauer <s.hauer@pengutronix.de>
To: Jonathan Bar Or <jonathanbaror@gmail.com>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH 0/5] Filesystem memory corruption fixes
Date: Thu, 27 Feb 2025 10:36:15 +0100 [thread overview]
Message-ID: <Z8AyD_cHzW_Wxcqz@pengutronix.de> (raw)
In-Reply-To: <CABMsoEGDcxSCSfdnV0B1dKvvJaQYBYhpAu2R_t31j5g_Q8fVBg@mail.gmail.com>
On Sat, Feb 22, 2025 at 12:46:18PM -0800, Jonathan Bar Or wrote:
> Those are awesome, thank you.
> We intend to publicly disclose March 19th, is that okay?
Well, this is a public list, so they are already disclosed...
Sascha
>
> Jonathan
>
> On Thu, Feb 20, 2025 at 11:33 PM Sascha Hauer <s.hauer@pengutronix.de> wrote:
> >
> >
> > On Wed, 19 Feb 2025 15:18:39 +0100, Sascha Hauer wrote:
> > > These are some fixes for memory corruptions that can occur on corrupted
> > > or manipulated filesystems.
> > >
> > > In case you use one of the affected filesystems in a secure boot chain
> > > you should apply these patches.
> > >
> > > Normally you shouldn't use a barebox filesystem in a secure boot chain,
> > > but instead use FIT images on a raw partition. We never made this explicit
> > > though. Ahmad has done this recently:
> > >
> > > [...]
> >
> > Applied, thanks!
> >
> > [1/5] CVE-2025-26722: fs: squashfs: Ensure positive inode length
> > https://git.pengutronix.de/cgit/barebox/commit/?id=6281a871e2c6 (link may not be stable)
> > [2/5] CVE-2025-26724: fs: cramfs: fix malloc(size + constant) buffer overflow issues
> > https://git.pengutronix.de/cgit/barebox/commit/?id=f86e528c8fba (link may not be stable)
> > [3/5] CVE-2025-26723: fs: ext4: fix malloc(size + constant) buffer overflow issues
> > https://git.pengutronix.de/cgit/barebox/commit/?id=51eea5c16fd2 (link may not be stable)
> > [4/5] CVE-2025-26725: fs: jffs2: fix malloc(size + constant) buffer overflow issues
> > https://git.pengutronix.de/cgit/barebox/commit/?id=e7397340359d (link may not be stable)
> > [5/5] CVE-2025-26721: fs: pstore: fix malloc(size + constant) buffer overflow issues
> > https://git.pengutronix.de/cgit/barebox/commit/?id=7563f5722dfd (link may not be stable)
> >
> > Best regards,
> > --
> > Sascha Hauer <s.hauer@pengutronix.de>
> >
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2025-02-27 9:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 14:18 Sascha Hauer
2025-02-19 14:18 ` [PATCH 1/5] CVE-2025-26722: fs: squashfs: Ensure positive inode length Sascha Hauer
2025-02-19 16:49 ` Ahmad Fatoum
2025-02-19 14:18 ` [PATCH 2/5] CVE-2025-26724: fs: cramfs: fix malloc(size + constant) buffer overflow issues Sascha Hauer
2025-02-19 16:50 ` Ahmad Fatoum
2025-02-19 14:18 ` [PATCH 3/5] CVE-2025-26723: fs: ext4: " Sascha Hauer
2025-02-19 16:51 ` Ahmad Fatoum
2025-02-19 14:18 ` [PATCH 4/5] CVE-2025-26725: fs: jffs2: " Sascha Hauer
2025-02-19 16:54 ` Ahmad Fatoum
2025-02-19 14:18 ` [PATCH 5/5] CVE-2025-26721: fs: pstore: " Sascha Hauer
2025-02-19 16:54 ` Ahmad Fatoum
2025-02-19 16:47 ` [PATCH 0/5] Filesystem memory corruption fixes Ahmad Fatoum
2025-02-21 7:33 ` Sascha Hauer
2025-02-22 20:46 ` Jonathan Bar Or
2025-02-27 9:36 ` Sascha Hauer [this message]
2025-03-03 8:51 ` Ahmad Fatoum
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=Z8AyD_cHzW_Wxcqz@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=jonathanbaror@gmail.com \
/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