All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][dunfell 0/5] Patch review
Date: Wed, 10 Apr 2024 06:10:53 -0700	[thread overview]
Message-ID: <cover.1712754495.git.steve@sakoman.com> (raw)

Please review this set of changes for dunfell and have comments back by
end of day Friday, April 12

Passed a-full on autobuilder:

https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6774

The following changes since commit 47ce772102b45db14dc21112367534ea1c37e33c:

  perf: bump PR to deal with sstate corruption on autobuilder (2024-04-02 05:46:56 -1000)

are available in the Git repository at:

  https://git.openembedded.org/openembedded-core-contrib stable/dunfell-nut
  http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-nut

Ashish Sharma (3):
  go: Backport fix for CVE-2024-24784
  xserver-xorg: Backport fix for CVE-2024-31081
  xserver-xorg: Backport fix for CVE-2024-31080

Colin McAllister (1):
  licenses.conf: Add missing LGPLv2.0+ license

Vijay Anusuri (1):
  ncurses: Backport fix for CVE-2023-50495

 meta/conf/licenses.conf                       |   1 +
 .../ncurses/files/CVE-2023-50495.patch        |  79 +++++++
 meta/recipes-core/ncurses/ncurses_6.2.bb      |   1 +
 meta/recipes-devtools/go/go-1.14.inc          |   1 +
 .../go/go-1.14/CVE-2024-24784.patch           | 205 ++++++++++++++++++
 .../xserver-xorg/CVE-2024-31080.patch         |  49 +++++
 .../xserver-xorg/CVE-2024-31081.patch         |  47 ++++
 .../xorg-xserver/xserver-xorg_1.20.14.bb      |   2 +
 8 files changed, 385 insertions(+)
 create mode 100644 meta/recipes-core/ncurses/files/CVE-2023-50495.patch
 create mode 100644 meta/recipes-devtools/go/go-1.14/CVE-2024-24784.patch
 create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2024-31080.patch
 create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2024-31081.patch

-- 
2.34.1



             reply	other threads:[~2024-04-10 13:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10 13:10 Steve Sakoman [this message]
2024-04-10 13:10 ` [OE-core][dunfell 1/5] ncurses: Backport fix for CVE-2023-50495 Steve Sakoman
2024-04-10 13:10 ` [OE-core][dunfell 2/5] go: Backport fix for CVE-2024-24784 Steve Sakoman
2024-04-10 13:10 ` [OE-core][dunfell 3/5] xserver-xorg: Backport fix for CVE-2024-31081 Steve Sakoman
2024-04-10 13:10 ` [OE-core][dunfell 4/5] xserver-xorg: Backport fix for CVE-2024-31080 Steve Sakoman
2024-04-10 13:10 ` [OE-core][dunfell 5/5] licenses.conf: Add missing LGPLv2.0+ license Steve Sakoman
  -- strict thread matches above, loose matches on Subject: below --
2024-01-05 14:03 [OE-core][dunfell 0/5] Patch review Steve Sakoman
2023-12-19 13:48 Steve Sakoman
2023-09-04 14:22 Steve Sakoman
2023-06-14 14:04 Steve Sakoman
2022-09-22 21:47 Steve Sakoman
2021-09-07 14:44 Steve Sakoman
2021-09-03 14:10 Steve Sakoman
2020-11-21  0:13 Steve Sakoman
2020-06-03 15:33 Steve Sakoman
2020-06-03 17:33 ` akuster
2020-06-03 17:36   ` Denys Dmytriyenko
2020-06-03 17:45     ` akuster
2020-06-03 23:33       ` Martin Jansa
2020-06-04  0:11         ` Joshua Watt
2020-06-04  0:38           ` Martin Jansa
2020-06-03 18:17     ` akuster
2020-06-03 18:18       ` Denys Dmytriyenko

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=cover.1712754495.git.steve@sakoman.com \
    --to=steve@sakoman.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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.