mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>,
	Jonathan Bar Or <jonathanbaror@gmail.com>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH 0/5] Filesystem memory corruption fixes
Date: Mon, 3 Mar 2025 09:51:12 +0100	[thread overview]
Message-ID: <0febcf92-f6b9-4717-a374-da93c1b4c205@pengutronix.de> (raw)
In-Reply-To: <Z8AyD_cHzW_Wxcqz@pengutronix.de>

Hi,

On 27.02.25 10:36, Sascha Hauer wrote:
> 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...

In a way, yes, but most users will probably only find out about this
once their CVE tooling reports that they are using a barebox version
that doesn't fix e.g. CVE-2025-26722.

CVE-2025-26722 (and I assume the others) are reserved right now, but
lack a description of the issue and its possible security implications.

We should probably write down some extra policy here:

  - Should CVE numbers even be mentioned for yet-undisclosed issues?

  - An explicit policy about disclosure timeline. Bugs are fixed all the
    time and I think, it's desirable that disclosure is postponed until
    after a release, so users informed of the issue directly know
    what to do about it. For critical security issues, a point release
    can be done on short notice

@Jonathan, March 19th is ok for us, but we don't object to any earlier
date.

Cheers,
Ahmad

> 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 |



      reply	other threads:[~2025-03-03  8:58 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
2025-03-03  8:51       ` Ahmad Fatoum [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=0febcf92-f6b9-4717-a374-da93c1b4c205@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=jonathanbaror@gmail.com \
    --cc=s.hauer@pengutronix.de \
    /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