From: Daniel Leidert <dleidert@debian.org>
To: u-boot@lists.denx.de
Subject: Has CVE-2024-42040 ever been addressed?
Date: Wed, 26 Mar 2025 02:46:39 +0100 [thread overview]
Message-ID: <1f48a22cb1376fb09e6efcaa696e0602831a2f3e.camel@debian.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 215 bytes --]
Hello,
CVE-2024-42040 was published last year. But I cannot find any response
to it, nor does it seem that it has been addressed yet. Has it been
missed? Will it be addressed in the future?
Regards, Daniel
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2025-03-26 5:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1f48a22cb1376fb09e6efcaa696e0602831a2f3e.camel@debian.org \
--to=dleidert@debian.org \
--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