From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Tom Rini <trini@konsulko.com>
Cc: Jonathan Bar Or <jonathanbaror@gmail.com>,
Gao Xiang <hsiangkao@linux.alibaba.com>,
Huang Jianan <jnhuang95@gmail.com>,
Joao Marcos Costa <jmcosta944@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
u-boot@lists.denx.de, linux-erofs@lists.ozlabs.org
Subject: Re: Security vulnerabilities report to Das-U-Boot
Date: Wed, 12 Feb 2025 09:24:18 +0100 [thread overview]
Message-ID: <8734gjsh8t.fsf@bootlin.com> (raw)
In-Reply-To: <20250211212909.GI1233568@bill-the-cat> (Tom Rini's message of "Tue, 11 Feb 2025 15:29:09 -0600")
Hello Tom,
On 11/02/2025 at 15:29:09 -06, Tom Rini <trini@konsulko.com> wrote:
> On Tue, Feb 11, 2025 at 08:26:37AM -0800, Jonathan Bar Or wrote:
>> Hi Tom and the rest of the team,
>>
>> Please let me know about fix time, whether this is acknowledged and
>> whether you're going to request CVE IDs for those or if I should do
>> it.
>> The reason is that I found similar issues in other bootloaders, so I'm
>> trying to synchronize all of them. For what it's worth, Barebox has
>> similar issues and are currently fixing.
>
> Yes, these seem valid. We don't have a CVE requesting authority so if
> you want them, go ahead and request them. You saw Gao Xiang's response
> for erofs, and I'm hoping one of the squashfs maintainers will chime
> in.
Either João or me, we will have a look.
Thanks,
Miquèl
next prev parent reply other threads:[~2025-02-12 8:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 3:47 Security vulnerabilities report to Das-U-Boot Jonathan Bar Or
2025-02-07 15:50 ` Tom Rini
2025-02-07 17:53 ` Jonathan Bar Or
2025-02-10 16:41 ` Tom Rini
2025-02-11 3:51 ` Gao Xiang
2025-02-11 16:26 ` Jonathan Bar Or
2025-02-11 21:29 ` Tom Rini
2025-02-11 23:28 ` Jonathan Bar Or
2025-02-12 8:24 ` Miquel Raynal [this message]
2025-02-15 3:17 ` Jonathan Bar Or
2025-02-15 3:24 ` Jonathan Bar Or
2025-02-22 20:47 ` Jonathan Bar Or
2025-02-25 17:59 ` Tom Rini
2025-02-25 18:18 ` Jonathan Bar Or
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=8734gjsh8t.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=jmcosta944@gmail.com \
--cc=jnhuang95@gmail.com \
--cc=jonathanbaror@gmail.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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