From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] {linux, linux-headers}: security bump 4.{14, 19}.x / 5.{4, 10, 15}.x / 6.{1, 4}.x series
Date: Wed, 9 Aug 2023 19:41:28 +0200 [thread overview]
Message-ID: <20230809194128.0effdfb9@windsurf> (raw)
In-Reply-To: <20230808193157.2042920-1-bernd@kuhls.net>
On Tue, 8 Aug 2023 21:31:56 +0200
Bernd Kuhls <bernd@kuhls.net> wrote:
> Fixes CVE-2022-40982:
> https://downfall.page/
> https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00828.html
> https://www.phoronix.com/news/Linux-Git-INCEPTION-DOWNFALL
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> ---
> linux/Config.in | 2 +-
> linux/linux.hash | 14 +++++++-------
> package/linux-headers/Config.in.host | 14 +++++++-------
> 3 files changed, 15 insertions(+), 15 deletions(-)
And the fun of a new hardware vulnerability begins!
Both applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-08-09 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 19:31 [Buildroot] [PATCH 1/2] {linux, linux-headers}: security bump 4.{14, 19}.x / 5.{4, 10, 15}.x / 6.{1, 4}.x series Bernd Kuhls
2023-08-08 19:31 ` [Buildroot] [PATCH 2/2] package/intel-microcode: security bump version to 20230808 Bernd Kuhls
2023-09-11 19:17 ` Peter Korsgaard
2023-08-09 17:41 ` Thomas Petazzoni via buildroot [this message]
2023-09-11 19:16 ` [Buildroot] [PATCH 1/2] {linux, linux-headers}: security bump 4.{14, 19}.x / 5.{4, 10, 15}.x / 6.{1, 4}.x series Peter Korsgaard
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=20230809194128.0effdfb9@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.