]> git.ipfire.org Git - thirdparty/openembedded/openembedded-core.git/log
thirdparty/openembedded/openembedded-core.git
9 days agouseradd_base.bbclass: Emulate the groupmems command using usermod
Peter Kjellerstedt [Tue, 26 May 2026 12:44:18 +0000 (14:44 +0200)] 
useradd_base.bbclass: Emulate the groupmems command using usermod

The groupmems command does to support the --prefix option, which is
being used since commit a7b846ba7d6d63a5e59939d75d9c5fe3e4cbb0e9.
However, the groupmems command can easily be emulated using the usermod
command.

[YOCTO#16277]

Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
9 days agouseradd.bbclass: Add support for USERMOD_PARAM
Peter Kjellerstedt [Tue, 12 May 2026 19:04:12 +0000 (21:04 +0200)] 
useradd.bbclass: Add support for USERMOD_PARAM

The groupmems command will be removed in shadow 4.20. The same
functionality as provided by groupmems can be achieved with the usermod
command. Add support for USERMOD_PARAM variables to specify the options
to use.

The following GROUPMEMS_PARAM:

GROUPMEMS_PARAM:${PN} = "--add user --group group1; \
                         --add user --group group2"

would be directly converted to the following USERMOD_PARAM:

USERMOD_PARAM:${PN} = "--append --groups group1 user; \
                       --append --groups group2 user"

It can also be simplified to:

USERMOD_PARAM:${PN} = "--append --groups group1,group2 user"

Add USERMOD_PARAM to PACKAGEVARS similarly to the USERADD_PARAM and
GROUPADD_PARAM variables.

[YOCTO#16277]

Co-authored-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
9 days agouseradd.bbclass: Some clean-ups and simplifications
Peter Kjellerstedt [Tue, 12 May 2026 19:04:11 +0000 (21:04 +0200)] 
useradd.bbclass: Some clean-ups and simplifications

* Improve some odd function names, e.g., groupmemsadd_sysroot and
  user_group_groupmems_add_sysroot. These were introduced in commit
  322ef726132a47d977d2c6ee41de5358f1e85994 (useradd.bbclass: Fix order
  of postinst-useradd-*).
* Make common_useradd_sysroot() look for the actually used command
  instead of always looking for useradd.
* Simplification of common_useradd_sysroot() by using case/esac.
* A bit of whitespace clean-up.

Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
9 days agou-boot: move DT validation yaml removal patch to SRC_URI
Ricardo Salveti [Wed, 20 May 2026 00:21:52 +0000 (21:21 -0300)] 
u-boot: move DT validation yaml removal patch to SRC_URI

Commit 5e97f3c1e2cf ("u-boot-tools: drop yaml in DT validation") added the
backport through SRC_URI_RISCV, so only RISC-V u-boot builds picked it up.

This issue is because the v1 of the patch was merged instead the v2 (which
is also not fully correct as it is not patching u-boot-tools). Drop the
patch from SRC_URI_RISCV and add it directly to both u-boot_2026.04.bb and
u-boot-tools_2026.04.bb, so it is applied to both recipes without
affecting external recipes including u-boot-common.inc.

Fixes: 5e97f3c1e2cf ("u-boot-tools: drop yaml in DT validation")
Signed-off-by: Ricardo Salveti <ricardo.salveti@oss.qualcomm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
9 days agoxwayland: upgrade 24.1.9 -> 24.1.11
Richard Purdie [Fri, 1 May 2026 12:46:21 +0000 (12:46 +0000)] 
xwayland: upgrade 24.1.9 -> 24.1.11

License-Update: The change was only to add a missing author, licenses
are unchanged.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
9 days agoxserver-xorg/xwayland: 'Clarify' xserver license
Richard Purdie [Thu, 21 May 2026 13:50:39 +0000 (14:50 +0100)] 
xserver-xorg/xwayland: 'Clarify' xserver license

The Xserver license, https://gitlab.freedesktop.org/xorg/xserver/-/blob/main/COPYING
is a bit of a challenge to decode. Whilst overall thought to be MIT, there
are many other simlar/related licences included in there.

The make our license data more accurate, update to include all the license
variants present.

I have submitted a patch upstream to add identifiers to the COPYING file to
make it clearer where these come from and save others from repeating this painful
exercise:

https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/2218

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
11 days agostaging.bbclass: Correct a typo
Peter Kjellerstedt [Tue, 26 May 2026 14:03:38 +0000 (16:03 +0200)] 
staging.bbclass: Correct a typo

This corrects a typo (us -> is) in the description of
extend_recipe_sysroot().

Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agolinux-firmware: upgrade 20260410 -> 20260519
Vivek Puar [Wed, 20 May 2026 05:11:36 +0000 (10:41 +0530)] 
linux-firmware: upgrade 20260410 -> 20260519

Upgrade the firmware package to latest release. Add compute package
for shikra. Add packages ${PN}-ath12k-{ipq5424, qcc2072} for ath12k
based chips. Add Texas Instruments PCM6240 firmware, firmware for
tas2783A projects, firmware for Lontium LT7911EXC and LT9611C. Move
lt*_fw.bin firmware to Lontium subdir. Add HP ISH firmware for Intel
Panther Lake systems. Add RDEPENDS on ${PN}-qcom-license for Dell
XPS13 packages as qcom/NOTICE.txt is applicable to those firmwares.

Signed-off-by: Vivek Puar <vpuar@qti.qualcomm.com>
Cc: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agogroff: build less in groff-native
Ross Burton [Tue, 19 May 2026 14:15:07 +0000 (15:15 +0100)] 
groff: build less in groff-native

When building groff-native we only really need enough of groff to build
manpages, and don't need documentation or extra tools.

Patch the Makefile to stop building the doc and contrib directories,
which both take time and have incomplete build dependencies that cause
intermittent failures[1][2].

This makes groff-native faster to build:

  groff-native    do_compile   -30.6s   -33.7%     90.9s -> 60.3s

And some tools are removed, which I don't believe are needed by anything
we build:

  /usr/bin/chem was removed
  /usr/bin/eqn2graph was removed
  /usr/bin/gdiffmk was removed
  /usr/bin/gperl was removed
  /usr/bin/gpinyin was removed
  /usr/bin/mmroff was removed
  /usr/bin/pic2graph was removed
  /usr/share/groff/1.24.1/tmac/chem.pic was removed
  /usr/share/groff/1.24.1/tmac/hdmisc.tmac was removed
  /usr/share/groff/1.24.1/tmac/hdtbl.tmac was removed
  /usr/share/groff/1.24.1/tmac/mm was removed
  /usr/share/groff/1.24.1/tmac/mm/0.MT was removed
  /usr/share/groff/1.24.1/tmac/mm/4.MT was removed
  /usr/share/groff/1.24.1/tmac/mm/5.MT was removed
  /usr/share/groff/1.24.1/tmac/mm/ms.cov was removed
  /usr/share/groff/1.24.1/tmac/mm/se_ms.cov was removed
  /usr/share/groff/1.24.1/tmac/mmse.tmac was removed
  /usr/share/groff/1.24.1/tmac/mm.tmac was removed
  /usr/share/groff/1.24.1/tmac/mom.tmac was removed
  /usr/share/groff/1.24.1/tmac/mse.tmac was removed
  /usr/share/groff/1.24.1/tmac/m.tmac was removed
  /usr/share/groff/1.24.1/tmac/om.tmac was removed
  /usr/share/groff/1.24.1/tmac/refer-mm.tmac was removed
  /usr/share/groff/1.24.1/tmac/rfc1345.tmac was removed
  /usr/share/groff/1.24.1/tmac/sboxes.tmac was removed

[1] oe-core d1a02bdd242 ("groff: Fix occasional build race failure")
[2] https://bugzilla.yoctoproject.org/show_bug.cgi?id=16279

Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agonasm: remove groff-native dependency
Ross Burton [Tue, 19 May 2026 14:01:05 +0000 (15:01 +0100)] 
nasm: remove groff-native dependency

The documentation hasn't been built with groff since 2013[1], remove the
dependency.

This exposes the fact that nasm depends on zlib, so add it to DEPENDS.

[1] nasm 1a63699c ("man: Generate manpages from asciidoc format")

Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agoinitramfs-framework: overlayroot: switch_root instead of chroot
Marcus Flyckt [Tue, 19 May 2026 11:19:47 +0000 (13:19 +0200)] 
initramfs-framework: overlayroot: switch_root instead of chroot

Use a proper switch_root instead of a plain chroot when transitioning to
the overlay root filesystem.

Some Linux features, like unshare(2), check for chrooted
environments and may return EPERM when running inside one.

This is particularly an issue when running unprivileged containers.

Signed-off-by: Marcus Flyckt <marcus.flyckt@kvaser.com>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agogcc/libgfortran: package libcaf libraries
Hemanth Kumar M D [Tue, 19 May 2026 07:25:30 +0000 (00:25 -0700)] 
gcc/libgfortran: package libcaf libraries

Package libcaf static libraries installed by GCC 16 to
avoid installed-vs-shipped QA errors.

Signed-off-by: Hemanth Kumar M D <Hemanth.KumarMD@windriver.com>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agolibc-test: add libatomic-staticdev to ptest RDEPENDS
Hemanth Kumar M D [Tue, 19 May 2026 07:25:33 +0000 (00:25 -0700)] 
libc-test: add libatomic-staticdev to ptest RDEPENDS

GCC 16 adds libatomic_asneeded.a which is required when statically
linking. The libc-test static tests fail on musl without it. Add
libatomic-staticdev alongside musl-staticdev for the same reason.

Signed-off-by: Hemanth Kumar M D <Hemanth.KumarMD@windriver.com>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agoelfutils: add libatomic-dev to ptest RDEPENDS
Hemanth Kumar M D [Tue, 19 May 2026 07:25:32 +0000 (00:25 -0700)] 
elfutils: add libatomic-dev to ptest RDEPENDS

GCC 16 adds libatomic_asneeded.so which is referenced by the GCC spec
at link time. Add libatomic-dev to ptest RDEPENDS so it is available
on the target when ptests compile code, following the same pattern as
libgcc-dev.

Signed-off-by: Hemanth Kumar M D <Hemanth.KumarMD@windriver.com>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agogn: fix build with GCC 16 on musl
Hemanth Kumar M D [Tue, 19 May 2026 07:25:31 +0000 (00:25 -0700)] 
gn: fix build with GCC 16 on musl

Add missing <cstdint> include in src/gn/pool.h for int64_t.

Fixes:
| ../sources/gn-0+git/src/gn/pool.h:26:3: error: 'int64_t' does not name a type

Upstream-Status: Submitted [https://gn-review.googlesource.com/c/gn/+/22740]

Signed-off-by: Hemanth Kumar M D <Hemanth.KumarMD@windriver.com>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agorxvt-unicode: backport a fix for building with gcc-16
Hemanth Kumar M D [Tue, 19 May 2026 07:25:24 +0000 (00:25 -0700)] 
rxvt-unicode: backport a fix for building with gcc-16

rename lerp to avoid conflict with the non-identical function std::lerp

Upstream-Status: Submitted [https://lists.schmorp.de/pipermail/rxvt-unicode/2026q2/002707.html]

Signed-off-by: Hemanth Kumar M D <Hemanth.KumarMD@windriver.com>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agopiglit:backport a fix for building with gcc-16
Hemanth Kumar M D [Tue, 19 May 2026 07:25:23 +0000 (00:25 -0700)] 
piglit:backport a fix for building with gcc-16

Avoid conflict with C++20 std::lerp from <cmath>, which
causes redefinition and ambiguous call errors with newer
toolchains.

Upstream-Status: Backport [https://gitlab.freedesktop.org/mesa/piglit/-/commit/ec0fc2fef0755b1595c3799ab25129174a4b2007]

Signed-off-by: Hemanth Kumar M D <Hemanth.KumarMD@windriver.com>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agokernel-fit-image: Validate key files expected by mkimage for the selected algorithm
Jamin Lin [Tue, 19 May 2026 09:17:24 +0000 (09:17 +0000)] 
kernel-fit-image: Validate key files expected by mkimage for the selected algorithm

The signing key validation in run_mkimage_sign() unconditionally
required <keyname>.key and <keyname>.crt regardless of the signing
algorithm.

However, mkimage handles RSA and ECDSA keys differently. RSA signing
uses separate .key and .crt files, while ECDSA signing uses a single
.pem file.

As a result, OE/fitimage.py required users of ECDSA signing to provide
unused .key and .crt files only to satisfy the validation checks.

Refactor the validation logic into _check_sign_key_files() and validate
the required files according to the selected signing algorithm:
- ECDSA: requires <keyname>.pem
- RSA: requires <keyname>.key and <keyname>.crt

Detect the algorithm by scanning all comma-separated parts of the algo
string so the field order does not matter (e.g. "sha256,ecdsa384").

Signed-off-by: Jamin Lin <jamin_lin@aspeedtech.com>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agosquashfs-tools: add another CPE
Quentin Schulz [Mon, 18 May 2026 16:41:39 +0000 (18:41 +0200)] 
squashfs-tools: add another CPE

The NVD has two additional CPEs for squashfs-tools pointing at the same
GitHub git repo, squashfs_project:squashfs-tools[1] and
squashfs-tools_project:squashfs-tools[2].

There are no other matches for squashfs-tools in the NVD except those
two, so don't specify the vendor for now and match both vendors with
only one entry in CVE_PRODUCT.

[1] https://nvd.nist.gov/products/cpe/detail/029FFEC5-FB40-4591-A864-90CB97E80FEA
[2] https://nvd.nist.gov/products/cpe/detail/ADE3E55D-5CBD-49B3-85B4-2035A9B380B3

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agocargo_common.bbclass: add subdir argument to git dependency to let cargo find crate
George Refseth [Mon, 18 May 2026 13:07:30 +0000 (15:07 +0200)] 
cargo_common.bbclass: add subdir argument to git dependency to let cargo find crate

When git referenced crate dependency dependens on (root) workspace virtual
manifest, when patching path the path to the folder containing the crate
within the referenced repo need to be added to the patching process.
A subdir argument is added to address this need.

Example usage when repo contains an api crate defining the api for org/repo:
SRC_URI:append = "git://git@github.com/<org>/<repo>.git;name=api;destsuffix=repo-api;subdir=crates/api;type=git-dependency"

Cc: Erik Wierich <erik@riscstar.com>
Signed-off-by: George Refseth <george.refseth@remarkable.no>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agopython3targetconfig: pull in nativesdk python when building nativesdk recipes
Alexander Kanavin [Mon, 18 May 2026 11:16:59 +0000 (13:16 +0200)] 
python3targetconfig: pull in nativesdk python when building nativesdk recipes

For the class to work, target python needs to be present in the target
sysroot. This was done only for :target builds but not for :nativesdk
ones, and this patch addresses that.

The issue was reported in
https://lists.openembedded.org/g/openembedded-core/message/237188
(but the proposed fix there isn't right).

Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agopython3-installer: upgrade 0.7.0 -> 1.0.1
Ross Burton [Mon, 18 May 2026 10:36:24 +0000 (11:36 +0100)] 
python3-installer: upgrade 0.7.0 -> 1.0.1

v1.0.1 (May 11, 2026)
- Include docs and tests in sdist again (#322)
- Fix long path issue on Windows (#321)
- Fix date in changelog (#324)
- Use `os.path.abspath()` instead of `Path.resolve()` for performance (#326)

v1.0.0 (Mar 28, 2026)

- Drop support for Python 3.9, 3.8, and 3.7 (#305, #242, #206)
- Add support and Python 3.13 and 3.14 (#201, #282)
- Add `--overwrite-existing` CLI option (#216)
- Add `--validate-record` CLI option (#161)
- Support installing multiple wheels (#203)
- Handle invalid hash algorithms (#179)
- Stream-based validation instead of in-memory (#98)
- Add validate_stream methods (#99)
- Consolidate and refine validation APIs (#108, #111)
- Sort entries before writing RECORD (#245)
- Do not install __pycache__ from wheels (#307)
- Fix a path traversal bug (#317)
- Update launcher scripts and Windows behavior (#212, #181)
- Fix Windows relpath bug (#286)
- Migrate to dataclasses (#200)
- Use cached_property for memoization (#243)
- Refactor installer.scripts (#239)
- Decouple test modules (#104)
- Avoid cross-module imports from .utils (#102)
- Lazy imports for performance (#226)
- Complete type annotations and enforce strict mypy (#173)
- Deprecate RecordEntry.validate (#186)
- Fix documentation typos and grammar (#309, #210)
- Improve docstrings and internal documentation (#100)

Remove an upstreamed patch, and rewrite the patch adding an --interpreter
option.

Verified that building everything in oe-core that uses the pep517 class
is identical before and after the upgrade.

Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agocargo-c: update 0.10.21 -> 0.10.22
Yash Shinde [Sat, 16 May 2026 09:52:32 +0000 (15:22 +0530)] 
cargo-c: update 0.10.21 -> 0.10.22

cargo-c version updated to stable version 0.10.22+cargo-0.96.0.

https://crates.io/crates/cargo-c/0.10.22+cargo-0.96.0
https://github.com/lu-zero/cargo-c/compare/v0.10.21...v0.10.22

Signed-off-by: Yash Shinde <Yash.Shinde.oss.dev@gmail.com>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agoscripts: Fix typo in pull-spdx-licenses script name
Richard Purdie [Sat, 16 May 2026 06:56:37 +0000 (07:56 +0100)] 
scripts: Fix typo in pull-spdx-licenses script name

Fix the typo in the script name since I can't unsee it now!

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agolicenses: Update with the pull-sdpx-licenses.py script to 3.28.0
Richard Purdie [Sat, 16 May 2026 06:56:36 +0000 (07:56 +0100)] 
licenses: Update with the pull-sdpx-licenses.py script to 3.28.0

Run the update script to update our licenses to version 3.28.0 which
adds 28 new licenses.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agolibrsvg: upgrade 2.61.3 -> 2.62.2
Ross Burton [Fri, 15 May 2026 15:10:04 +0000 (16:10 +0100)] 
librsvg: upgrade 2.61.3 -> 2.62.2

Selected highlights from the release notes:

Version 2.62.2
==============

- #1142: Fix blurry embeded SVG images by rasterizing them at
  device resolution (Dylan Sechet).

- #1229: Fix build when gobject-introspection is enabled but
  gdk-pixbuf is disabled.

Version 2.62.0
==============

- The minimum supported Rust version (MSRV) is 1.92.0.

- #1218: Fix rendering of markers at the end of open subpaths.

- #1216: Small optimization for userLanguage so regexes only get
  compiled if needed (Adetoye Anointing).

Update cross-query-loaders.patch to the final version that was submitted
upstream.

Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agolibrsvg: add PACKAGECONFIGs for avif and gdkpixbuf
Ross Burton [Fri, 15 May 2026 15:10:03 +0000 (16:10 +0100)] 
librsvg: add PACKAGECONFIGs for avif and gdkpixbuf

The existing gdkpixbuf PACKAGECONFIG is actually for the gdk-pixbuf SVG
loader.  Rename this to gdkpixbuf-loader and add another PACKAGECONFIG
that controls whether gdk-pixbuf support is enabled, and enable this by
default to preserve behaviour.

Add a new PACKAGECONFIG to enable support for embedded AVIF[1] files.
This is disabled out of the box as it depends on dav1d, part of meta-oe.

[1] https://en.wikipedia.org/wiki/AVIF

Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agolibrsvg: remove dependency on liberation-fonts
Ross Burton [Fri, 15 May 2026 15:10:02 +0000 (16:10 +0100)] 
librsvg: remove dependency on liberation-fonts

librsvg 2.42 onwards[1] from 2018 ship the fonts they need for the test
suite instead of assuming the system has the right fonts, so we don't
need to depend on liberation-fonts for the tests.

[1] librsvg ec3353e89 ("Use a hard-coded font file to render test images,
    for predictable font rendering")

Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agobusybox: 1.37.0 -> 1.38.0
Andrej Valek [Fri, 15 May 2026 09:18:50 +0000 (11:18 +0200)] 
busybox: 1.37.0 -> 1.38.0

- update to next version 1.38.0
 - refresh defconfig
  - disable new applets (SHA384SUM, USE_BB_CRYPT_YES, SSL_SERVER,
    FEATURE_TELNETD_*, VMSTAT, HUSH_*, LSBLK)
  - enable new applets (FEATURE_VERSION, UUIDGEN)
 - remove and refresh already merged patches

Signed-off-by: Andrej Valek <andrej.v@skyrain.eu>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agognutls: upgrade 3.8.12 -> 3.8.13
Peter Marko [Mon, 11 May 2026 21:18:39 +0000 (23:18 +0200)] 
gnutls: upgrade 3.8.12 -> 3.8.13

Solves CVE-2026-33846, CVE-2026-42009, CVE-2026-33845, CVE-2026-42010,
CVE-2026-3833, CVE-2026-42011, CVE-2026-42012, CVE-2026-42013,
CVE-2026-42014, CVE-2026-5260, CVE-2026-42015, CVE-2026-3832 and
CVE-2026-5419.

Release notes: [1]

Rebase patches and drop patch included in this release.
Add patches to fix linking with musl libc.
Increase memory needed to successfully run test key-openssl.
Drop code for previous release tarball problem.

[1] https://github.com/gnutls/gnutls/blob/3.8.13/NEWS

Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agodefault-distrovars.inc: add missing spaces in append overrides
João Marcos Costa [Thu, 14 May 2026 19:14:28 +0000 (21:14 +0200)] 
default-distrovars.inc: add missing spaces in append overrides

DISTRO_FEATURES_OPTED_OUT is a space-separated list, so the missing
space leads to:

$ bitbake-getvar DISTRO_FEATURES_OPTED_OUT
(...)
   set /src/build/conf/local.conf:277
     "x11"
(...)
   :append[loongarch64] /src/openembedded-core/meta/conf/distro/include/default-distrovars.inc:26
     "seccomp"
(...)
DISTRO_FEATURES_OPTED_OUT="x11seccomp"

Signed-off-by: João Marcos Costa <joaomarcos.costa@bootlin.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agorust: Upgrade 1.94.1 -> 1.95.0
Deepesh Varatharajan [Fri, 15 May 2026 06:16:40 +0000 (23:16 -0700)] 
rust: Upgrade 1.94.1 -> 1.95.0

Rust Changes:
https://github.com/rust-lang/rust/releases/tag/1.95.0

Cargo Changes:
https://doc.rust-lang.org/nightly/cargo/CHANGELOG.html#cargo-195-2026-04-16

Drop merged patches:
0001-Adjust-loongarch-assembly-test.patch
0001-Fix-flaky-assertions-in-oneshot-tests.patch
0001-Update-amdgpu-data-layout.patch

Updated patches:
0001-src-core-build_steps-tool.rs-switch-off-lto-for-rust.patch
rust-oe-selftest.patch

New patch:
0002-Fix-rust-build-failure-with-unstable-options.patch

Fix rust build failure with unstable options.
Remove the check that errors out when -Zunstable-options is not provided
for custom targets.The original upstream change (and its follow-up) mainly
ensured GitHub workflows and tests work correctly by explicitly passing
"-Zunstable-options", along with related testcase updates. Reverting the
entire commit would also undo those unrelated workflow and test adjustments,
so this patch only targets the specific enforcement logic without affecting
the rest of the changes.
https://github.com/rust-lang/rust/issues/155963

Selftest Changes:
Skip two failing tests
src/librustdoc
src/tools/rustdoc
https://github.com/rust-lang/rust/pull/153409

Excluded tests:
+--------+----------+---------+
| Before  |  After  | Skipped |
+---------+---------+---------+
|   37    |   39    |   +2    |
+--------+----------+---------+

Test results:

rust v1.95.0
+-------------+---------+---------+
| Machine     | Passed  | Skipped |
+-------------+---------+---------+
| qemux86-64  |  22187  |   689   |
| qemux86     |  21929  |   947   |
| qemuarm64   |  21994  |   882   |
| qemuarm     |  21910  |   966   |
| qemuriscv64 |  21955  |   921   |
+-------------+---------+---------+

Test results difference (1.95.0 - 1.94.1):

+-------------+--------+---------+
| Machine     | Passed | Skipped |
+-------------+--------+---------+
| qemux86-64  |  +276  |   +29   |
| qemux86     |  +271  |   +34   |
| qemuarm64   |  +271  |   +34   |
| qemuarm     |  +271  |   +34   |
| qemuriscv64 |  +270  |   +35   |
+-------------+--------+---------+

Signed-off-by: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agoxrandr: upgrade 1.5.3 -> 1.5.4
Li Zhou [Fri, 15 May 2026 02:44:41 +0000 (10:44 +0800)] 
xrandr: upgrade 1.5.3 -> 1.5.4

Changelog:
==========
- meson: Add option to build with meson
- COPYING: Add missing copyright notices from source files
- gitlab CI: drop the ci-fairy check-mr job
- set_gamma_info: fix heap-buffer-overflow with empty gamma ramps
- Add more checks for malloc()/calloc() failure
- Strip trailing whitespace from source files
- man page: fix warnings from `mandoc -T lint`
- xrandr man page NAME line doesn't give functionality
- Additional man page formatting fixes
- xrandr.1: some editorial changes for this man page
- Improve man page formatting
- xrandr: Warn when running with Xwayland

License-Update: The COPYING changes in upstream commit d29cb495 add
missing copyright notices from source files. No license change, no
impact on the recipe licensing.

Signed-off-by: Li Zhou <li.zhou@windriver.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agopython3-uv-build: Update python3-uv-build from 0.11.8 to 0.11.14
Khem Raj [Fri, 15 May 2026 02:37:24 +0000 (19:37 -0700)] 
python3-uv-build: Update python3-uv-build from 0.11.8 to 0.11.14

Notable fixes
- packaging-related changes include fixing editable builds to include data files
- improved lock/build option handling
- cache compatibility fixes
- Python discovery/runtime updates.

Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agonativesdk.bbclass: remove obsolete comment
João Marcos Costa [Thu, 14 May 2026 21:48:50 +0000 (23:48 +0200)] 
nativesdk.bbclass: remove obsolete comment

Instead of removing it, one could just uncomment the line. However,
the final value of HOST_SYS would then be the very same of HOST_SYS as
currently defined in bitbake.conf:

- bitbake.conf:
"${HOST_ARCH}${HOST_VENDOR}-${HOST_OS}" -> HOST_SYS="x86_64-oesdk-linux"

- nativesdk.bbclass:
"${HOST_ARCH}${TARGET_VENDOR}-${HOST_OS}" -> HOST_SYS="x86_64-oesdk-linux"

That is because both TARGET_VENDOR and HOST_VENDOR equals SDK_VENDOR
in nativesdk.bbclass.

Signed-off-by: João Marcos Costa <joaomarcos.costa@bootlin.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agoovmf: add support for Clang toolchain
João Marcos Costa [Thu, 14 May 2026 14:15:17 +0000 (16:15 +0200)] 
ovmf: add support for Clang toolchain

ovmf can be built with clang by using "CLANGDWARF" toolchain, so add
TARGET_TOOLS variable to represent the switch between "GCC" and
"CLANGDWARF".

Since the targets represented by FIXED_GCCVER were deprecated upstream,
remove them (and FIXED_GCCVER itself) from the recipe and use "GCC"
instead.

Signed-off-by: João Marcos Costa <joaomarcos.costa@bootlin.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agoovmf: drop upstreamed BUILD_CFLAGS setting
João Marcos Costa [Thu, 14 May 2026 14:15:16 +0000 (16:15 +0200)] 
ovmf: drop upstreamed BUILD_CFLAGS setting

This same gcc (v12) warning was handled upstream a while ago:

22130dcd98b4 ("Basetools: turn off gcc12 warning")

This change is available in the tag we currently use: edk2-stable202511.

In fact, it is available since edk2-stable202205, and the
-Wno-error=stringop-overflow flag [1] was added for the same reason we have
it in ovmf's recipe.

[1] https://github.com/tianocore/edk2/blob/master/BaseTools/Source/C/DevicePath/GNUmakefile#L27

Signed-off-by: João Marcos Costa <joaomarcos.costa@bootlin.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agoovmf: simplify PACKAGECONFIG's default value
João Marcos Costa [Thu, 14 May 2026 14:15:15 +0000 (16:15 +0200)] 
ovmf: simplify PACKAGECONFIG's default value

The two append operations call bb.utils.contains, while a single
contains_any() does the trick in a cleaner way.

Regarding the default value, if tpm is not enabled, PACKAGECONFIG ends
up with a couple empty spaces, and this can be avoided by redefining the
default value to the result of contains_any().

Even though this replacement comes with a change in behaviour (at least
in edge cases), we prefer a consistent PACKAGECONFIG (weak) default
assignment across recipes.

Signed-off-by: João Marcos Costa <joaomarcos.costa@bootlin.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agovim: simplify PACKAGECONFIG's default value
João Marcos Costa [Thu, 14 May 2026 14:11:13 +0000 (16:11 +0200)] 
vim: simplify PACKAGECONFIG's default value

GTK+3 UI was disabled [1] by default, and the resulting call to
bb.utils.contains() could be replaced by a bb.utils.filter() as in a
similar change [2].

Better than that, just move 'x11' to the bb.utils.filter() above.

[1] a07763f03d4f ("vim: disable GTK+3 UI by default")
[2] f38320c9646a ("meta: simplify conditional operations with bb.utils.filter")

Signed-off-by: João Marcos Costa <joaomarcos.costa@bootlin.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agobluez5: add patches to fix 8.56 gatt issue
Jinwang Li [Thu, 14 May 2026 12:00:28 +0000 (20:00 +0800)] 
bluez5: add patches to fix 8.56 gatt issue

btd_gatt_client_service_removed() can be called reentrantly via
bt_gatt_client_unref() after the services queue has already been freed,
resulting in a use-after-free.

Reset client->ready to false before destroying the services queue to
prevent reentrant calls from dereferencing freed memory.

Upstream-Status: Backport [bluez/bluez@d01616f]
Signed-off-by: Jinwang Li <jinwang.li@oss.qualcomm.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agospdx: Add SHA 512 support
Joshua Watt [Wed, 13 May 2026 15:00:58 +0000 (09:00 -0600)] 
spdx: Add SHA 512 support

Adds support for adding SHA-512 hashes (where possible). This is to
improve compliance with SBoM standards, in particular BSI TR-03181 [1].

SHA 256 hashes are still included for each file, and still used to index
files in the database. Also, while SHA 512 is supported as a hash for
downloads, most recipes are still using SHA 256 and would need to be
upgraded for full compliance with BSI TR-03183

[1]: https://www.bsi.bund.de/EN/Themen/Unternehmen-und-Organisationen/Standards-und-Zertifizierung/Technische-Richtlinien/TR-nach-Thema-sortiert/tr03183/TR-03183_node.html

Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agospdx: Use checksum list from bitbake
Joshua Watt [Wed, 13 May 2026 15:00:57 +0000 (09:00 -0600)] 
spdx: Use checksum list from bitbake

Instead of manually curating a hardcoded list of checksums, use the same
list that bitbake uses.

Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agogcr: package the ssh-agent into a separate package
Ross Burton [Wed, 13 May 2026 13:35:57 +0000 (14:35 +0100)] 
gcr: package the ssh-agent into a separate package

The agent is a separate component to the library, so package it into a
new package.

The systemd dependency is only relevant to the ssh-agent, so don't
enable it by default as we don't enable the agent either.

Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agogcr: remove obsolete packaging
Ross Burton [Wed, 13 May 2026 13:35:56 +0000 (14:35 +0100)] 
gcr: remove obsolete packaging

Previously the package contained UI libraries but they were removed
in the 4.0.0 release:

- gcr4 will no longer ship UI libraries, i.e. gcr-gtk3 or gcr-gtk4.

Remove a large amount of packaging metadata that is no longer needed,
and add an optional and disabled PACKAGECONFIG for the viewer tool which
is packaged separately from the libraries.

Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agogcr: remove obsolete DEPENDS
Ross Burton [Wed, 13 May 2026 13:35:55 +0000 (14:35 +0100)] 
gcr: remove obsolete DEPENDS

libxslt-native was added back in 2017 to gcr-3.2.0 as a needed
dependency when building with gobject-introspection[1], but this no
longer appears to be the case.

gnupg-native was added in 2020[1] but we now pass the correct paths to
Meson so this is no longer needed.

[1] oe-core 58922a43f93 ("gcr: add missing dependency on xsltproc if introspection is enabled")
[2] oe-core afa5ec0dee8 ("gcr: depends on gnupg-native")

Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agolibportal: split out GTK libraries into sub-packages
Ross Burton [Wed, 13 May 2026 13:35:54 +0000 (14:35 +0100)] 
libportal: split out GTK libraries into sub-packages

We shouldn't package the bare libportal and the GTK3 and GTK4 libraries
into one package. Instead package the UI libraries into separate
packages, so that dependencies are contained.

Add PACKAGECONFIGs for the gtk3 and gtk3 libraries so that they can be
controlled individually. Keep the existing behaviour of enabling both
GTK 3 and 4 as various recipes use both, but this allows building
libportal without any GTK dependencies if required.

The PACKAGECONFIG logic is "fun": if either of wayland or x11 are
enabled then we can enable GTK+3 by default, and if either of those
_and_ opengl are enabled then we can also do GTK 4.

Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agolibportal: add explicit PACKAGECONFIG for gtk4 support
Ross Burton [Wed, 13 May 2026 13:35:53 +0000 (14:35 +0100)] 
libportal: add explicit PACKAGECONFIG for gtk4 support

Instead of using the presence of the opengl DISTRO_FEATURE to control
whether the GTK 4 integration is built, add a PACKAGECONFIG for it.

Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agocve-check-map.conf: fix typo in comment
Thomas Perrot [Wed, 13 May 2026 08:55:59 +0000 (10:55 +0200)] 
cve-check-map.conf: fix typo in comment

Fix a typo in the comment for the fixed-version status: "verion" -> "version".

Signed-off-by: Thomas Perrot <thomas.perrot@bootlin.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2 weeks agolayer.conf: Update to use blacksail release series name
Richard Purdie [Mon, 18 May 2026 13:44:28 +0000 (14:44 +0100)] 
layer.conf: Update to use blacksail release series name

For now we remain compatible with wrynose so just start the transition.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agosstate: Detect broken sstate paths containing tmpdir
Richard Purdie [Wed, 13 May 2026 23:11:26 +0000 (00:11 +0100)] 
sstate: Detect broken sstate paths containing tmpdir

sstate objects should not contain TMPDIR paths. Detect this and error
if found as the side effects are quite problematic.

[YOCTO #16281]

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agosstate: Improve confusing debug message
Richard Purdie [Wed, 13 May 2026 23:10:51 +0000 (00:10 +0100)] 
sstate: Improve confusing debug message

The entry being removed is a file, not a manifest, so improve the debug
message to reflect that and be slightly less confusing.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agoglib-2.0-native: Remove problematic path reference
Richard Purdie [Wed, 13 May 2026 23:07:44 +0000 (00:07 +0100)] 
glib-2.0-native: Remove problematic path reference

The gdb helper scripts are installed to a path that matches the installed
binary path. Whilst technically correct, we relocate native tools and this
path isn't relocated correctly.

The paths mean the build directory leaks into sstate objects and native
sstate objects can have differing path contents as a result, which causes
problems.

Whilst we could relocate it, gdb would not be searching in these paths for
helpers anyway so the tools aren't needed and we can simply remove them in
the native case.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agopseudo: Upgrade 1.9.6 -> 1.9.7
Richard Purdie [Wed, 13 May 2026 11:50:22 +0000 (12:50 +0100)] 
pseudo: Upgrade 1.9.6 -> 1.9.7

Pulls in fixes to rename/renameat/renameat2:

Changqing Li (1):
  renameat2/renameat: only ignore when both old and new path are not in PSEUDO_INCLUDE_PATHS

Mark Hatle (4):
  run_tests.sh: Allow the user to specify specific tests to run
  tests: Add mv then hardlink testing
  rename: only ignore when both old and new path are not in PSEUDO_INCLUDE_PATHS
  Makefile.in: Bump version to 1.9.7

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agolinux-yocto/6.18: update CVE exclusions (6.18.28)
Bruce Ashfield [Mon, 11 May 2026 20:25:13 +0000 (16:25 -0400)] 
linux-yocto/6.18: update CVE exclusions (6.18.28)

Data pulled from: https://github.com/CVEProject/cvelistV5

    1/1 [
        Author: cvelistV5 Github Action
        Email: github_action@example.com
        Subject: 1537 changes (14 new | 1523 updated): - 14 new CVEs: CVE-2022-4988, CVE-2026-2614, CVE-2026-42565, CVE-2026-42869, CVE-2026-42870, CVE-2026-42872, CVE-2026-42873, CVE-2026-42874, CVE-2026-42875, CVE-2026-42876, CVE-2026-45025, CVE-2026-45026, CVE-2026-6146, CVE-2026-8319 - 1523 updated CVEs: CVE-2022-21546, CVE-2022-48626, CVE-2022-48627, CVE-2022-48628, CVE-2022-48629, CVE-2022-48630, CVE-2022-48631, CVE-2022-48632, CVE-2022-48633, CVE-2022-48634, CVE-2022-48635, CVE-2022-48636, CVE-2022-48637, CVE-2022-48638, CVE-2022-48639, CVE-2022-48640, CVE-2022-48641, CVE-2022-48642, CVE-2022-48643, CVE-2022-48644, CVE-2022-48645, CVE-2022-48646, CVE-2022-48647, CVE-2022-48648, CVE-2022-48649, CVE-2022-48650, CVE-2022-48651, CVE-2022-48652, CVE-2022-48653, CVE-2022-48654, CVE-2022-48655, CVE-2022-48656, CVE-2022-48657, CVE-2022-48658, CVE-2022-48659, CVE-2022-48660, CVE-2022-48661, CVE-2022-48662, CVE-2022-48663, CVE-2022-48664, CVE-2022-48665, CVE-2022-48666, CVE-2022-48667, CVE-2022-48668, CVE-2022-48669, CVE-2022-48670, CVE-2022-48671, CVE-2022-48672, CVE-2022-48673, CVE-2022-48674, CVE-2022-48675, CVE-2022-48686, CVE-2022-48687, CVE-2022-48688, CVE-2022-48689, CVE-2022-48690, CVE-2022-48691, CVE-2022-48692, CVE-2022-48693, CVE-2022-48694, CVE-2022-48695, CVE-2022-48696, CVE-2022-48697, CVE-2022-48698, CVE-2022-48699, CVE-2022-48701, CVE-2022-48702, CVE-2022-48703, CVE-2022-48704, CVE-2022-48705, CVE-2022-48706, CVE-2022-48707, CVE-2022-48708, CVE-2022-48709, CVE-2022-48710, CVE-2022-48711, CVE-2022-48712, CVE-2022-48713, CVE-2022-48714, CVE-2022-48715, CVE-2022-48716, CVE-2022-48717, CVE-2022-48718, CVE-2022-48719, CVE-2022-48720, CVE-2022-48721, CVE-2022-48722, CVE-2022-48723, CVE-2022-48724, CVE-2022-48725, CVE-2022-48726, CVE-2022-48727, CVE-2022-48728, CVE-2022-48729, CVE-2022-48730, CVE-2022-48731, CVE-2022-48732, CVE-2022-48733, CVE-2022-48734, CVE-2022-48735, CVE-2022-48738, CVE-2022-48739, CVE-2022-48740, CVE-2022-48741, CVE-2022-48742, CVE-2022-48743, CVE-2022-48744, CVE-2022-48745, CVE-2022-48746, CVE-2022-48747, CVE-2022-48748, CVE-2022-48749, CVE-2022-48750, CVE-2022-48751, CVE-2022-48752, CVE-2022-48753, CVE-2022-48754, CVE-2022-48755, CVE-2022-48756, CVE-2022-48757, CVE-2022-48758, CVE-2022-48759, CVE-2022-48760, CVE-2022-48761, CVE-2022-48762, CVE-2022-48763, CVE-2022-48764, CVE-2022-48765, CVE-2022-48766, CVE-2022-48767, CVE-2022-48768, CVE-2022-48769, CVE-2022-48770, CVE-2022-48771, CVE-2022-48772, CVE-2022-48773, CVE-2022-48774, CVE-2022-48775, CVE-2022-48776, CVE-2022-48777, CVE-2022-48778, CVE-2022-48779, CVE-2022-48780, CVE-2022-48781, CVE-2022-48782, CVE-2022-48783, CVE-2022-48784, CVE-2022-48785, CVE-2022-48786, CVE-2022-48787, CVE-2022-48788, CVE-2022-48789, CVE-2022-48790, CVE-2022-48791, CVE-2022-48792, CVE-2022-48793, CVE-2022-48794, CVE-2022-48795, CVE-2022-48796, CVE-2022-48797, CVE-2022-48798, CVE-2022-48799, CVE-2022-48800, CVE-2022-48801, CVE-2022-48802, CVE-2022-48803, CVE-2022-48804, CVE-2022-48805, CVE-2022-48806, CVE-2022-48807, CVE-2022-48808, CVE-2022-48809, CVE-2022-48810, CVE-2022-48811, CVE-2022-48812, CVE-2022-48813, CVE-2022-48814, CVE-2022-48815, CVE-2022-48816, CVE-2022-48817, CVE-2022-48818, CVE-2022-48819, CVE-2022-48820, CVE-2022-48821, CVE-2022-48822, CVE-2022-48823, CVE-2022-48824, CVE-2022-48825, CVE-2022-48826, CVE-2022-48827, CVE-2022-48828, CVE-2022-48829, CVE-2022-48830, CVE-2022-48831, CVE-2022-48832, CVE-2022-48833, CVE-2022-48834, CVE-2022-48835, CVE-2022-48836, CVE-2022-48837, CVE-2022-48838, CVE-2022-48839, CVE-2022-48840, CVE-2022-48841, CVE-2022-48842, CVE-2022-48844, CVE-2022-48845, CVE-2022-48846, CVE-2022-48847, CVE-2022-48848, CVE-2022-48849, CVE-2022-48850, CVE-2022-48851, CVE-2022-48852, CVE-2022-48853, CVE-2022-48854, CVE-2022-48855, CVE-2022-48856, CVE-2022-48857, CVE-2022-48858, CVE-2022-48859, CVE-2022-48860, CVE-2022-48861, CVE-2022-48862, CVE-2022-48863, CVE-2022-48864, CVE-2022-48865, CVE-2022-48866, CVE-2022-48867, CVE-2022-48868, CVE-2022-48869, CVE-2022-48870, CVE-2022-48871, CVE-2022-48872, CVE-2022-48873, CVE-2022-48874, CVE-2022-48875, CVE-2022-48876, CVE-2022-48877, CVE-2022-48878, CVE-2022-48879, CVE-2022-48880, CVE-2022-48881, CVE-2022-48882, CVE-2022-48883, CVE-2022-48884, CVE-2022-48885, CVE-2022-48886, CVE-2022-48887, CVE-2022-48888, CVE-2022-48889, CVE-2022-48890, CVE-2022-48891, CVE-2022-48892, CVE-2022-48893, CVE-2022-48894, CVE-2022-48895, CVE-2022-48896, CVE-2022-48897, CVE-2022-48898, CVE-2022-48899, CVE-2022-48901, CVE-2022-48902, CVE-2022-48903, CVE-2022-48904, CVE-2022-48905, CVE-2022-48906, CVE-2022-48907, CVE-2022-48908, CVE-2022-48909, CVE-2022-48910, CVE-2022-48911, CVE-2022-48912, CVE-2022-48913, CVE-2022-48914, CVE-2022-48915, CVE-2022-48916, CVE-2022-48918, CVE-2022-48919, CVE-2022-48920, CVE-2022-48921, CVE-2022-48922, CVE-2022-48923, CVE-2022-48924, CVE-2022-48925, CVE-2022-48926, CVE-2022-48927, CVE-2022-48928, CVE-2022-48929, CVE-2022-48930, CVE-2022-48931, CVE-2022-48932, CVE-2022-48933, CVE-2022-48934, CVE-2022-48935, CVE-2022-48937, CVE-2022-48938, CVE-2022-48939, CVE-2022-48940, CVE-2022-48941, CVE-2022-48942, CVE-2022-48943, CVE-2022-48944, CVE-2022-48945, CVE-2022-48946, CVE-2022-48947, CVE-2022-48948, CVE-2022-48949, CVE-2022-48950, CVE-2022-48951, CVE-2022-48952, CVE-2022-48953, CVE-2022-48954, CVE-2022-48955, CVE-2022-48956, CVE-2022-48957, CVE-2022-48958, CVE-2022-48959, CVE-2022-48960, CVE-2022-48961, CVE-2022-48962, CVE-2022-48963, CVE-2022-48964, CVE-2022-48965, CVE-2022-48966, CVE-2022-48967, CVE-2022-48968, CVE-2022-48969, CVE-2022-48970, CVE-2022-48971, CVE-2022-48972, CVE-2022-48973, CVE-2022-48974, CVE-2022-48975, CVE-2022-48976, CVE-2022-48977, CVE-2022-48978, CVE-2022-48979, CVE-2022-48980, CVE-2022-48981, CVE-2022-48982, CVE-2022-48983, CVE-2022-48984, CVE-2022-48985, CVE-2022-48986, CVE-2022-48987, CVE-2022-48988, CVE-2022-48989, CVE-2022-48990, CVE-2022-48991, CVE-2022-48992, CVE-2022-48994, CVE-2022-48995, CVE-2022-48996, CVE-2022-48997, CVE-2022-48998, CVE-2022-48999, CVE-2022-49000, CVE-2022-49001, CVE-2022-49002, CVE-2022-49003, CVE-2022-49004, CVE-2022-49005, CVE-2022-49006, CVE-2022-49007, CVE-2022-49008, CVE-2022-49009, CVE-2022-49010, CVE-2022-49011, CVE-2022-49012, CVE-2022-49013, CVE-2022-49014, CVE-2022-49015, CVE-2022-49016, CVE-2022-49017, CVE-2022-49018, CVE-2022-49019, CVE-2022-49020, CVE-2022-49021, CVE-2022-49022, CVE-2022-49023, CVE-2022-49024, CVE-2022-49025, CVE-2022-49026, CVE-2022-49027, CVE-2022-49028, CVE-2022-49029, CVE-2022-49030, CVE-2022-49031, CVE-2022-49032, CVE-2022-49033, CVE-2022-49034, CVE-2022-49035, CVE-2022-49044, CVE-2022-49046, CVE-2022-49047, CVE-2022-49048, CVE-2022-49049, CVE-2022-49050, CVE-2022-49051, CVE-2022-49052, CVE-2022-49053, CVE-2022-49054, CVE-2022-49055, CVE-2022-49057, CVE-2022-49058, CVE-2022-49059, CVE-2022-49060, CVE-2022-49061, CVE-2022-49062, CVE-2022-49063, CVE-2022-49064, CVE-2022-49065, CVE-2022-49066, CVE-2022-49067, CVE-2022-49068, CVE-2022-49069, CVE-2022-49070, CVE-2022-49071, CVE-2022-49072, CVE-2022-49073, CVE-2022-49074, CVE-2022-49075, CVE-2022-49076, CVE-2022-49077, CVE-2022-49078, CVE-2022-49079, CVE-2022-49080, CVE-2022-49081, CVE-2022-49082, CVE-2022-49083, CVE-2022-49084, CVE-2022-49085, CVE-2022-49086, CVE-2022-49087, CVE-2022-49088, CVE-2022-49089, CVE-2022-49090, CVE-2022-49091, CVE-2022-49092, CVE-2022-49093, CVE-2022-49094, CVE-2022-49095, CVE-2022-49096, CVE-2022-49097, CVE-2022-49098, CVE-2022-49099, CVE-2022-49100, CVE-2022-49102, CVE-2022-49103, CVE-2022-49104, CVE-2022-49105, CVE-2022-49106, CVE-2022-49107, CVE-2022-49108, CVE-2022-49109, CVE-2022-49110, CVE-2022-49111, CVE-2022-49112, CVE-2022-49113, CVE-2022-49114, CVE-2022-49115, CVE-2022-49116, CVE-2022-49117, CVE-2022-49118, CVE-2022-49119, CVE-2022-49120, CVE-2022-49121, CVE-2022-49122, CVE-2022-49123, CVE-2022-49124, CVE-2022-49125, CVE-2022-49126, CVE-2022-49127, CVE-2022-49128, CVE-2022-49129, CVE-2022-49130, CVE-2022-49131, CVE-2022-49132, CVE-2022-49133, CVE-2022-49134, CVE-2022-49135, CVE-2022-49136, CVE-2022-49137, CVE-2022-49138, CVE-2022-49139, CVE-2022-49141, CVE-2022-49142, CVE-2022-49144, CVE-2022-49145, CVE-2022-49146, CVE-2022-49147, CVE-2022-49148, CVE-2022-49149, CVE-2022-49150, CVE-2022-49151, CVE-2022-49152, CVE-2022-49153, CVE-2022-49154, CVE-2022-49155, CVE-2022-49156, CVE-2022-49157, CVE-2022-49158, CVE-2022-49159, CVE-2022-49160, CVE-2022-49161, CVE-2022-49162, CVE-2022-49163, CVE-2022-49164, CVE-2022-49165, CVE-2022-49166, CVE-2022-49167, CVE-2022-49168, CVE-2022-49169, CVE-2022-49170, CVE-2022-49171, CVE-2022-49172, CVE-2022-49173, CVE-2022-49174, CVE-2022-49175, CVE-2022-49176, CVE-2022-49177, CVE-2022-49178, CVE-2022-49179, CVE-2022-49180, CVE-2022-49182, CVE-2022-49183, CVE-2022-49184, CVE-2022-49185, CVE-2022-49186, CVE-2022-49187, CVE-2022-49188, CVE-2022-49189, CVE-2022-49190, CVE-2022-49191, CVE-2022-49192, CVE-2022-49193, CVE-2022-49194, CVE-2022-49195, CVE-2022-49196, CVE-2022-49197, CVE-2022-49198, CVE-2022-49199, CVE-2022-49200, CVE-2022-49201, CVE-2022-49202, CVE-2022-49203, CVE-2022-49204, CVE-2022-49205, CVE-2022-49206, CVE-2022-49207, CVE-2022-49208, CVE-2022-49209, CVE-2022-49210, CVE-2022-49211, CVE-2022-49212, CVE-2022-49213, CVE-2022-49214, CVE-2022-49215, CVE-2022-49216, CVE-2022-49217, CVE-2022-49218, CVE-2022-49219, CVE-2022-49220, CVE-2022-49221, CVE-2022-49222, CVE-2022-49223, CVE-2022-49224, CVE-2022-49225, CVE-2022-49226, CVE-2022-49227, CVE-2022-49228, CVE-2022-49229, CVE-2022-49230, CVE-2022-49231, CVE-2022-49232, CVE-2022-49233, CVE-2022-49234, CVE-2022-49235, CVE-2022-49236, CVE-2022-49237, CVE-2022-49238, CVE-2022-49239, CVE-2022-49240, CVE-2022-49241, CVE-2022-49242, CVE-2022-49243, CVE-2022-49244, CVE-2022-49245, CVE-2022-49246, CVE-2022-49247, CVE-2022-49248, CVE-2022-49249, CVE-2022-49250, CVE-2022-49251, CVE-2022-49252, CVE-2022-49253, CVE-2022-49254, CVE-2022-49255, CVE-2022-49256, CVE-2022-49257, CVE-2022-49258, CVE-2022-49259, CVE-2022-49260, CVE-2022-49261, CVE-2022-49262, CVE-2022-49263, CVE-2022-49264, CVE-2022-49265, CVE-2022-49266, CVE-2022-49268, CVE-2022-49269, CVE-2022-49270, CVE-2022-49271, CVE-2022-49272, CVE-2022-49273, CVE-2022-49274, CVE-2022-49275, CVE-2022-49276, CVE-2022-49277, CVE-2022-49278, CVE-2022-49279, CVE-2022-49280, CVE-2022-49281, CVE-2022-49282, CVE-2022-49283, CVE-2022-49284, CVE-2022-49285, CVE-2022-49286, CVE-2022-49287, CVE-2022-49288, CVE-2022-49289, CVE-2022-49290, CVE-2022-49291, CVE-2022-49292, CVE-2022-49293, CVE-2022-49294, CVE-2022-49295, CVE-2022-49296, CVE-2022-49297, CVE-2022-49298, CVE-2022-49300, CVE-2022-49301, CVE-2022-49302, CVE-2022-49303, CVE-2022-49304, CVE-2022-49305, CVE-2022-49306, CVE-2022-49307, CVE-2022-49308, CVE-2022-49309, CVE-2022-49310, CVE-2022-49311, CVE-2022-49312, CVE-2022-49313, CVE-2022-49314, CVE-2022-49315, CVE-2022-49316, CVE-2022-49317, CVE-2022-49318, CVE-2022-49319, CVE-2022-49320, CVE-2022-49321, CVE-2022-49322, CVE-2022-49323, CVE-2022-49324, CVE-2022-49325, CVE-2022-49326, CVE-2022-49327, CVE-2022-49328, CVE-2022-49329, CVE-2022-49330, CVE-2022-49331, CVE-2022-49332, CVE-2022-49333, CVE-2022-49334, CVE-2022-49335, CVE-2022-49336, CVE-2022-49337, CVE-2022-49338, CVE-2022-49339, CVE-2022-49340, CVE-2022-49341, CVE-2022-49342, CVE-2022-49343, CVE-2022-49344, CVE-2022-49345, CVE-2022-49346, CVE-2022-49347, CVE-2022-49348, CVE-2022-49349, CVE-2022-49350, CVE-2022-49351, CVE-2022-49352, CVE-2022-49353, CVE-2022-49354, CVE-2022-49356, CVE-2022-49357, CVE-2022-49358, CVE-2022-49359, CVE-2022-49360, CVE-2022-49361, CVE-2022-49362, CVE-2022-49363, CVE-2022-49364, CVE-2022-49365, CVE-2022-49366, CVE-2022-49367, CVE-2022-49368, CVE-2022-49369, CVE-2022-49370, CVE-2022-49371, CVE-2022-49372, CVE-2022-49373, CVE-2022-49374, CVE-2022-49375, CVE-2022-49376, CVE-2022-49377, CVE-2022-49378, CVE-2022-49379, CVE-2022-49380, CVE-2022-49381, CVE-2022-49382, CVE-2022-49383, CVE-2022-49384, CVE-2022-49385, CVE-2022-49386, CVE-2022-49387, CVE-2022-49388, CVE-2022-49389, CVE-2022-49390, CVE-2022-49391, CVE-2022-49392, CVE-2022-49393, CVE-2022-49394, CVE-2022-49395, CVE-2022-49396, CVE-2022-49397, CVE-2022-49398, CVE-2022-49399, CVE-2022-49400, CVE-2022-49401, CVE-2022-49402, CVE-2022-49403, CVE-2022-49404, CVE-2022-49405, CVE-2022-49406, CVE-2022-49407, CVE-2022-49408, CVE-2022-49409, CVE-2022-49410, CVE-2022-49411, CVE-2022-49412, CVE-2022-49413, CVE-2022-49414, CVE-2022-49415, CVE-2022-49416, CVE-2022-49417, CVE-2022-49418, CVE-2022-49419, CVE-2022-49420, CVE-2022-49421, CVE-2022-49422, CVE-2022-49423, CVE-2022-49424, CVE-2022-49425, CVE-2022-49426, CVE-2022-49427, CVE-2022-49428, CVE-2022-49429, CVE-2022-49430, CVE-2022-49431, CVE-2022-49432, CVE-2022-49433, CVE-2022-49434, CVE-2022-49435, CVE-2022-49436, CVE-2022-49437, CVE-2022-49438, CVE-2022-49439, CVE-2022-49440, CVE-2022-49441, CVE-2022-49442, CVE-2022-49443, CVE-2022-49444, CVE-2022-49445, CVE-2022-49446, CVE-2022-49447, CVE-2022-49448, CVE-2022-49449, CVE-2022-49450, CVE-2022-49451, CVE-2022-49452, CVE-2022-49453, CVE-2022-49454, CVE-2022-49455, CVE-2022-49456, CVE-2022-49457, CVE-2022-49458, CVE-2022-49459, CVE-2022-49460, CVE-2022-49461, CVE-2022-49462, CVE-2022-49463, CVE-2022-49464, CVE-2022-49465, CVE-2022-49466, CVE-2022-49467, CVE-2022-49468, CVE-2022-49469, CVE-2022-49470, CVE-2022-49471, CVE-2022-49472, CVE-2022-49473, CVE-2022-49474, CVE-2022-49475, CVE-2022-49476, CVE-2022-49477, CVE-2022-49478, CVE-2022-49479, CVE-2022-49480, CVE-2022-49481, CVE-2022-49482, CVE-2022-49483, CVE-2022-49484, CVE-2022-49485, CVE-2022-49486, CVE-2022-49487, CVE-2022-49488, CVE-2022-49489, CVE-2022-49490, CVE-2022-49491, CVE-2022-49492, CVE-2022-49493, CVE-2022-49494, CVE-2022-49495, CVE-2022-49496, CVE-2022-49497, CVE-2022-49498, CVE-2022-49499, CVE-2022-49500, CVE-2022-49501, CVE-2022-49502, CVE-2022-49503, CVE-2022-49504, CVE-2022-49505, CVE-2022-49506, CVE-2022-49507, CVE-2022-49508, CVE-2022-49509, CVE-2022-49510, CVE-2022-49511, CVE-2022-49512, CVE-2022-49513, CVE-2022-49514, CVE-2022-49515, CVE-2022-49516, CVE-2022-49517, CVE-2022-49518, CVE-2022-49519, CVE-2022-49520, CVE-2022-49521, CVE-2022-49522, CVE-2022-49523, CVE-2022-49524, CVE-2022-49525, CVE-2022-49526, CVE-2022-49527, CVE-2022-49528, CVE-2022-49529, CVE-2022-49530, CVE-2022-49531, CVE-2022-49532, CVE-2022-49533, CVE-2022-49534, CVE-2022-49535, CVE-2022-49536, CVE-2022-49537, CVE-2022-49538, CVE-2022-49539, CVE-2022-49540, CVE-2022-49541, CVE-2022-49542, CVE-2022-49543, CVE-2022-49544, CVE-2022-49545, CVE-2022-49546, CVE-2022-49547, CVE-2022-49548, CVE-2022-49549, CVE-2022-49550, CVE-2022-49551, CVE-2022-49552, CVE-2022-49553, CVE-2022-49554, CVE-2022-49555, CVE-2022-49556, CVE-2022-49557, CVE-2022-49558, CVE-2022-49559, CVE-2022-49560, CVE-2022-49561, CVE-2022-49562, CVE-2022-49563, CVE-2022-49564, CVE-2022-49565, CVE-2022-49566, CVE-2022-49567, CVE-2022-49568, CVE-2022-49569, CVE-2022-49570, CVE-2022-49571, CVE-2022-49572, CVE-2022-49573, CVE-2022-49574, CVE-2022-49575, CVE-2022-49576, CVE-2022-49577, CVE-2022-49578, CVE-2022-49579, CVE-2022-49580, CVE-2022-49581, CVE-2022-49582, CVE-2022-49583, CVE-2022-49584, CVE-2022-49585, CVE-2022-49586, CVE-2022-49587, CVE-2022-49588, CVE-2022-49589, CVE-2022-49590, CVE-2022-49591, CVE-2022-49592, CVE-2022-49593, CVE-2022-49594, CVE-2022-49595, CVE-2022-49596, CVE-2022-49597, CVE-2022-49598, CVE-2022-49599, CVE-2022-49600, CVE-2022-49601, CVE-2022-49602, CVE-2022-49603, CVE-2022-49604, CVE-2022-49605, CVE-2022-49606, CVE-2022-49607, CVE-2022-49608, CVE-2022-49609, CVE-2022-49610, CVE-2022-49611, CVE-2022-49612, CVE-2022-49613, CVE-2022-49615, CVE-2022-49616, CVE-2022-49617, CVE-2022-49618, CVE-2022-49619, CVE-2022-49620, CVE-2022-49621, CVE-2022-49622, CVE-2022-49623, CVE-2022-49624, CVE-2022-49625, CVE-2022-49626, CVE-2022-49627, CVE-2022-49628, CVE-2022-49629, CVE-2022-49630, CVE-2022-49631, CVE-2022-49632, CVE-2022-49633, CVE-2022-49634, CVE-2022-49635, CVE-2022-49636, CVE-2022-49637, CVE-2022-49638, CVE-2022-49639, CVE-2022-49640, CVE-2022-49641, CVE-2022-49642, CVE-2022-49643, CVE-2022-49644, CVE-2022-49645, CVE-2022-49646, CVE-2022-49647, CVE-2022-49648, CVE-2022-49649, CVE-2022-49650, CVE-2022-49651, CVE-2022-49652, CVE-2022-49653, CVE-2022-49654, CVE-2022-49655, CVE-2022-49656, CVE-2022-49657, CVE-2022-49658, CVE-2022-49659, CVE-2022-49661, CVE-2022-49662, CVE-2022-49663, CVE-2022-49664, CVE-2022-49665, CVE-2022-49666, CVE-2022-49667, CVE-2022-49668, CVE-2022-49669, CVE-2022-49670, CVE-2022-49671, CVE-2022-49672, CVE-2022-49673, CVE-2022-49674, CVE-2022-49675, CVE-2022-49676, CVE-2022-49677, CVE-2022-49678, CVE-2022-49679, CVE-2022-49680, CVE-2022-49681, CVE-2022-49682, CVE-2022-49683, CVE-2022-49684, CVE-2022-49685, CVE-2022-49686, CVE-2022-49687, CVE-2022-49688, CVE-2022-49691, CVE-2022-49692, CVE-2022-49693, CVE-2022-49694, CVE-2022-49695, CVE-2022-49696, CVE-2022-49697, CVE-2022-49698, CVE-2022-49699, CVE-2022-49700, CVE-2022-49701, CVE-2022-49702, CVE-2022-49703, CVE-2022-49704, CVE-2022-49705, CVE-2022-49706, CVE-2022-49707, CVE-2022-49708, CVE-2022-49709, CVE-2022-49710, CVE-2022-49711, CVE-2022-49712, CVE-2022-49713, CVE-2022-49714, CVE-2022-49715, CVE-2022-49716, CVE-2022-49717, CVE-2022-49718, CVE-2022-49719, CVE-2022-49720, CVE-2022-49721, CVE-2022-49722, CVE-2022-49723, CVE-2022-49724, CVE-2022-49725, CVE-2022-49726, CVE-2022-49727, CVE-2022-49728, CVE-2022-49729, CVE-2022-49731, CVE-2022-49732, CVE-2022-49733, CVE-2022-49738, CVE-2022-49739, CVE-2022-49740, CVE-2022-49741, CVE-2022-49742, CVE-2022-49743, CVE-2022-49744, CVE-2022-49745, CVE-2022-49746, CVE-2022-49747, CVE-2022-49748, CVE-2022-49749, CVE-2022-49750, CVE-2022-49751, CVE-2022-49752, CVE-2022-49753, CVE-2022-49754, CVE-2022-49755, CVE-2022-49756, CVE-2022-49757, CVE-2022-49758, CVE-2022-49759, CVE-2022-49760, CVE-2022-49761, CVE-2022-49762, CVE-2022-49763, CVE-2022-49764, CVE-2022-49765, CVE-2022-49766, CVE-2022-49767, CVE-2022-49768, CVE-2022-49769, CVE-2022-49770, CVE-2022-49771, CVE-2022-49772, CVE-2022-49773, CVE-2022-49774, CVE-2022-49775, CVE-2022-49776, CVE-2022-49777, CVE-2022-49778, CVE-2022-49779, CVE-2022-49780, CVE-2022-49781, CVE-2022-49782, CVE-2022-49783, CVE-2022-49784, CVE-2022-49785, CVE-2022-49786, CVE-2022-49787, CVE-2022-49788, CVE-2022-49789, CVE-2022-49790, CVE-2022-49791, CVE-2022-49792, CVE-2022-49793, CVE-2022-49794, CVE-2022-49795, CVE-2022-49796, CVE-2022-49797, CVE-2022-49798, CVE-2022-49799, CVE-2022-49800, CVE-2022-49801, CVE-2022-49802, CVE-2022-49803, CVE-2022-49804, CVE-2022-49805, CVE-2022-49806, CVE-2022-49807, CVE-2022-49808, CVE-2022-49809, CVE-2022-49810, CVE-2022-49811, CVE-2022-49812, CVE-2022-49813, CVE-2022-49814, CVE-2022-49815, CVE-2022-49817, CVE-2022-49818, CVE-2022-49819, CVE-2022-49820, CVE-2022-49821, CVE-2022-49822, CVE-2022-49823, CVE-2022-49824, CVE-2022-49825, CVE-2022-49826, CVE-2022-49827, CVE-2022-49828, CVE-2022-49829, CVE-2022-49830, CVE-2022-49831, CVE-2022-49832, CVE-2022-49833, CVE-2022-49834, CVE-2022-49835, CVE-2022-49836, CVE-2022-49837, CVE-2022-49838, CVE-2022-49839, CVE-2022-49840, CVE-2022-49841, CVE-2022-49842, CVE-2022-49844, CVE-2022-49845, CVE-2022-49846, CVE-2022-49847, CVE-2022-49848, CVE-2022-49849, CVE-2022-49850, CVE-2022-49851, CVE-2022-49852, CVE-2022-49853, CVE-2022-49854, CVE-2022-49855, CVE-2022-49857, CVE-2022-49858, CVE-2022-49859, CVE-2022-49860, CVE-2022-49861, CVE-2022-49862, CVE-2022-49863, CVE-2022-49864, CVE-2022-49865, CVE-2022-49866, CVE-2022-49867, CVE-2022-49868, CVE-2022-49869, CVE-2022-49870, CVE-2022-49871, CVE-2022-49872, CVE-2022-49873, CVE-2022-49874, CVE-2022-49875, CVE-2022-49876, CVE-2022-49877, CVE-2022-49878, CVE-2022-49879, CVE-2022-49880, CVE-2022-49881, CVE-2022-49882, CVE-2022-49883, CVE-2022-49884, CVE-2022-49885, CVE-2022-49886, CVE-2022-49887, CVE-2022-49888, CVE-2022-49889, CVE-2022-49890, CVE-2022-49891, CVE-2022-49892, CVE-2022-49893, CVE-2022-49894, CVE-2022-49895, CVE-2022-49896, CVE-2022-49898, CVE-2022-49899, CVE-2022-49900, CVE-2022-49901, CVE-2022-49902, CVE-2022-49903, CVE-2022-49904, CVE-2022-49905, CVE-2022-49906, CVE-2022-49907, CVE-2022-49908, CVE-2022-49910, CVE-2022-49911, CVE-2022-49912, CVE-2022-49913, CVE-2022-49914, CVE-2022-49915, CVE-2022-49916, CVE-2022-49917, CVE-2022-49918, CVE-2022-49919, CVE-2022-49920, CVE-2022-49921, CVE-2022-49922, CVE-2022-49923, CVE-2022-49924, CVE-2022-49925, CVE-2022-49926, CVE-2022-49927, CVE-2022-49928, CVE-2022-49929, CVE-2022-49930, CVE-2022-49931, CVE-2022-49932, CVE-2022-49934, CVE-2022-49935, CVE-2022-49936, CVE-2022-49937, CVE-2022-49938, CVE-2022-49939, CVE-2022-49940, CVE-2022-49942, CVE-2022-49943, CVE-2022-49944, CVE-2022-49945, CVE-2022-49946, CVE-2022-49947, CVE-2022-49948, CVE-2022-49949, CVE-2022-49950, CVE-2022-49951, CVE-2022-49952, CVE-2022-49953, CVE-2022-49954, CVE-2022-49955, CVE-2022-49956, CVE-2022-49957, CVE-2022-49958, CVE-2022-49959, CVE-2022-49960, CVE-2022-49961, CVE-2022-49962, CVE-2022-49963, CVE-2022-49964, CVE-2022-49965, CVE-2022-49966, CVE-2022-49967, CVE-2022-49968, CVE-2022-49969, CVE-2022-49970, CVE-2022-49971, CVE-2022-49972, CVE-2022-49973, CVE-2022-49974, CVE-2022-49975, CVE-2022-49976, CVE-2022-49977, CVE-2022-49978, CVE-2022-49979, CVE-2022-49980, CVE-2022-49981, CVE-2022-49982, CVE-2022-49983, CVE-2022-49984, CVE-2022-49985, CVE-2022-49986, CVE-2022-49987, CVE-2022-49989, CVE-2022-49990, CVE-2022-49991, CVE-2022-49992, CVE-2022-49993, CVE-2022-49994, CVE-2022-49995, CVE-2022-49996, CVE-2022-49997, CVE-2022-49998, CVE-2022-49999, CVE-2022-50000, CVE-2022-50001, CVE-2022-50002, CVE-2022-50003, CVE-2022-50004, CVE-2022-50005, CVE-2022-50006, CVE-2022-50007, CVE-2022-50008, CVE-2022-50009, CVE-2022-50010, CVE-2022-50011, CVE-2022-50012, CVE-2022-50013, CVE-2022-50014, CVE-2022-50015, CVE-2022-50016, CVE-2022-50017, CVE-2022-50019, CVE-2022-50020, CVE-2022-50021, CVE-2022-50022, CVE-2022-50023, CVE-2022-50024, CVE-2022-50025, CVE-2022-50026, CVE-2022-50027, CVE-2022-50028, CVE-2022-50029, CVE-2022-50030, CVE-2022-50032, CVE-2022-50033, CVE-2022-50034, CVE-2022-50035, CVE-2022-50036, CVE-2022-50037, CVE-2022-50038, CVE-2022-50039, CVE-2022-50040, CVE-2022-50041, CVE-2022-50042, CVE-2022-50043, CVE-2022-50044, CVE-2022-50045, CVE-2022-50046, CVE-2022-50047, CVE-2022-50048, CVE-2022-50049, CVE-2022-50050, CVE-2022-50051, CVE-2022-50052, CVE-2022-50053, CVE-2022-50054, CVE-2022-50055, CVE-2022-50056, CVE-2022-50057, CVE-2022-50058, CVE-2022-50059, CVE-2022-50060, CVE-2022-50061, CVE-2022-50062, CVE-2022-50063, CVE-2022-50064, CVE-2022-50065, CVE-2022-50066, CVE-2022-50067, CVE-2022-50068, CVE-2022-50069, CVE-2022-50070, CVE-2022-50071, CVE-2022-50072, CVE-2022-50073, CVE-2022-50074, CVE-2022-50075, CVE-2022-50076, CVE-2022-50077, CVE-2022-50078, CVE-2022-50079, CVE-2022-50080, CVE-2022-50082, CVE-2022-50084, CVE-2022-50085, CVE-2022-50086, CVE-2022-50087, CVE-2022-50088, CVE-2022-50089, CVE-2022-50090, CVE-2022-50091, CVE-2022-50092, CVE-2022-50093, CVE-2022-50094, CVE-2022-50095, CVE-2022-50096, CVE-2022-50097, CVE-2022-50098, CVE-2022-50099, CVE-2022-50100, CVE-2022-50101, CVE-2022-50102, CVE-2022-50103, CVE-2022-50104, CVE-2022-50105, CVE-2022-50106, CVE-2022-50107, CVE-2022-50108, CVE-2022-50109, CVE-2022-50110, CVE-2022-50111, CVE-2022-50112, CVE-2022-50113, CVE-2022-50114, CVE-2022-50115, CVE-2022-50116, CVE-2022-50117, CVE-2022-50118, CVE-2022-50119, CVE-2022-50120, CVE-2022-50121, CVE-2022-50122, CVE-2022-50123, CVE-2022-50124, CVE-2022-50125, CVE-2022-50126, CVE-2022-50127, CVE-2022-50129, CVE-2022-50130, CVE-2022-50131, CVE-2022-50132, CVE-2022-50133, CVE-2022-50134, CVE-2022-50135, CVE-2022-50136, CVE-2022-50137, CVE-2022-50138, CVE-2022-50139, CVE-2022-50140, CVE-2022-50141, CVE-2022-50142, CVE-2022-50143, CVE-2022-50144, CVE-2022-50145, CVE-2022-50146, CVE-2022-50147, CVE-2022-50148, CVE-2022-50149, CVE-2022-50151, CVE-2022-50152, CVE-2022-50153, CVE-2022-50154, CVE-2022-50155, CVE-2022-50156, CVE-2022-50157, CVE-2022-50158, CVE-2022-50159, CVE-2022-50160, CVE-2022-50161, CVE-2022-50162, CVE-2022-50163, CVE-2022-50164, CVE-2022-50165, CVE-2022-50166, CVE-2023-42346, CVE-2025-10908, CVE-2025-61305, CVE-2025-61306, CVE-2025-61307, CVE-2025-61308, CVE-2025-61309, CVE-2025-61310, CVE-2025-65417, CVE-2025-67887, CVE-2025-69599, CVE-2026-2393, CVE-2026-36906, CVE-2026-41308, CVE-2026-41506, CVE-2026-41511, CVE-2026-41517, CVE-2026-42312, CVE-2026-42314, CVE-2026-42612, CVE-2026-42843, CVE-2026-42856, CVE-2026-42866, CVE-2026-43638, CVE-2026-43894, CVE-2026-43968, CVE-2026-43969, CVE-2026-44200, CVE-2026-44336, CVE-2026-44413, CVE-2026-44658, CVE-2026-44737, CVE-2026-44996, CVE-2026-45002, CVE-2026-45223, CVE-2026-7210, CVE-2026-7308, CVE-2026-7790, CVE-2026-8318
        Date: Mon, 11 May 2026 19:18:58 +0000

    ]

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agolinux-yocto/6.18: update to v6.18.28
Bruce Ashfield [Mon, 11 May 2026 20:25:12 +0000 (16:25 -0400)] 
linux-yocto/6.18: update to v6.18.28

Updating linux-yocto/6.18 to the latest korg -stable release that comprises
the following commits:

    c31b94a4231c Linux 6.18.28
    71a1d9d985d2 xfrm: esp: avoid in-place decrypt on shared skb frags
    ce685b6a03dc Linux 6.18.27
    97d35052a816 ipmi:ssif: NULL thread on error
    52a7c9a2823d ipmi:ssif: Remove unnecessary indention
    6f820139d16a netfilter: reject zero shift in nft_bitwise
    b778b6d09542 net: ipv6: fix NOREF dst use in seg6 and rpl lwtunnels
    a8d95d274be2 mm/slab: return NULL early from kmalloc_nolock() in NMI on UP
    05b4ed8bef30 mm/page_alloc: return NULL early from alloc_frozen_pages_nolock() in NMI on UP
    e9b057a44def vmalloc: fix buffer overflow in vrealloc_node_align()
    bdd9503c3d22 ALSA: aloop: Fix peer runtime UAF during format-change stop
    6153878c5255 ALSA: caiaq: fix usb_dev refcount leak on probe failure
    30c000a49094 drm/amdgpu: fix zero-size GDS range init on RDNA4
    c261d07a8057 ipv6: rpl: reserve mac_len headroom when recompressed SRH grows
    3d46009e2ad4 ALSA: caiaq: Don't abort when no input device is available
    1d160e30aa42 ALSA: caiaq: Fix potentially leftover ep1_in_urb at error path
    b8c5acce56e0 driver core: Add kernel-doc for DEV_FLAG_COUNT enum value
    b42821c15445 crypto: authencesn - reject short ahash digests during instance creation
    5cf6d5e5e3b8 net: qrtr: ns: Limit the total number of nodes
    20855cef7e65 net: qrtr: ns: Limit the maximum number of lookups
    35fb4a0c077c net: qrtr: ns: Limit the maximum server registration per node
    5e9f1bad26df iio: frequency: admv1013: fix NULL pointer dereference on str
    c772e9efe2b1 iio: frequency: admv1013: add dev variable
    0adac0ee2c42 media: rc: igorplugusb: heed coherency rules
    7ba734027b2b media: rc: ttusbir: respect DMA coherency rules
    7d7863018f40 wifi: mt76: mt792x: fix mt7925u USB WFSYS reset handling
    0bc155c4ca47 wifi: mt76: mt792x: describe USB WFSYS reset with a descriptor
    09e1c96594af phy: qcom: m31-eusb2: clear PLL_EN during init
    37ef11ab2cf3 phy: qcom: m31-eusb2: Update init sequence to set PHY_ENABLE
    da4a33e739dc mei: me: add nova lake point H DID
    09033be12a82 mei: me: use PCI_DEVICE_DATA macro
    38f113f81d3f lib: test_hmm: evict device pages on file close to avoid use-after-free
    1e67c82fb778 arm64: mm: Fix rodata=full block mapping support for realm guests
    5e07126d7ab8 arm64: mm: Simplify check in arch_kfence_init_pool()
    6f977b0472f7 mm: prevent droppable mappings from being locked
    bbc4bfae9e43 seg6: fix seg6 lwtunnel output redirect for L2 reduced encap mode
    13e550fbfccd scsi: sd: fix missing put_disk() when device_add(&disk_dev) fails
    9da6e314ea5f sched_ext: Documentation: Clarify ops.dispatch() role in task lifecycle
    43222ac484f9 rxgk: Fix potential integer overflow in length check
    3fb7394a8377 rtmutex: Use waiter::task instead of current in remove_waiter()
    f1af27cec07a ntfs3: fix integer overflow in run_unpack() volume boundary check
    d3012690a706 ntfs3: add buffer boundary checks to run_unpack()
    83e31039e0d7 NFSv4.1: Apply session size limits on clone path
    fc8d81f189f0 ktest: Fix the month in the name of the failure directory
    9f4ba5966c78 IB/core: Fix zero dmac race in neighbor resolution
    4db061a40543 gtp: disable BH before calling udp_tunnel_xmit_skb()
    b91e535f208c ceph: only d_add() negative dentries when they are unhashed
    87c99a50e0fd dm mirror: fix integer overflow in create_dirty_log()
    a616126cb080 crypto: nx - Fix packed layout in struct nx842_crypto_header
    354a27e28447 crypto: nx - fix context leak in nx842_crypto_free_ctx
    5c07962fed66 crypto: nx - fix bounce buffer leaks in nx842_crypto_{alloc,free}_ctx
    2ae365e32998 crypto: atmel-sha204a - Fix uninitialized data access on OTP read error
    1193c12126d3 crypto: atmel-sha204a - Fix potential UAF and memory leak in remove path
    64ea9dbf4c77 crypto: atmel-sha204a - Fix error codes in OTP reads
    863d11b39277 crypto: atmel-tdes - fix DMA sync direction
    910f335786a0 crypto: ccree - fix a memory leak in cc_mac_digest()
    808685bfd124 crypto: hisilicon - Fix dma_unmap_single() direction
    9c032781c2b1 crypto: atmel-ecc - Release client on allocation failure
    61516b4a5b26 crypto: atmel-aes - Fix 3-page memory leak in atmel_aes_buff_cleanup
    4d713333dd32 crypto: arm64/aes - Fix 32-bit aes_mac_update() arg treated as 64-bit
    343a5bf68a8f crypto: acomp - fix wrong pointer stored by acomp_save_req()
    c524c124e309 can: ucan: fix devres lifetime
    1656698656f6 bus: mhi: host: pci_generic: Switch to async power up to avoid boot delays
    e08d75753db1 Bluetooth: hci_event: fix potential UAF in SSP passkey handlers
    b4339521bb43 apparmor: use target task's context in apparmor_getprocattr()
    b7a953374db9 mfd: core: Preserve OF node when ACPI handle is present
    e88827bb0399 taskstats: set version in TGID exit notifications
    83bb57635d7c tcp: call sk_data_ready() after listener migration
    69c4d137b22d wifi: rtl8xxxu: fix potential use of uninitialized value
    4f3374c990fb x86/shstk: Prevent deadlock during shstk sigreturn
    ef7ce8f4a341 x86/cpu: Disable FRED when PTI is forced on
    fdaa42ca370d inotify: fix watch count leak when fsnotify_add_inode_mark_locked() fails
    371f4dc80601 HID: apple: ensure the keyboard backlight is off if suspending
    ea43a34452a6 check-uapi: link into shared objects
    73ce72edd113 md/raid5: validate payload size before accessing journal metadata
    1985cb3247e8 md/raid5: fix soft lockup in retry_aligned_read()
    9142f00a9287 md/md-llbitmap: raise barrier before state machine transition
    98623c7e2a51 md/md-llbitmap: skip reading rdevs that are not in_sync
    f7d9d0e4a64f amdgpu/jpeg: fix deepsleep register for jpeg 5_0_0 and 5_0_2
    ac858718219f mtd: spinand: winbond: Declare the QE bit on W25NxxJW
    134975be170b mtd: spi-nor: sst: Fix write enable before AAI sequence
    1e6b0a69bf2c ext4: fix missing brelse() in ext4_xattr_inode_dec_ref_all()
    537e06597702 ext4: fix bounds check in check_xattrs() to prevent out-of-bounds access
    6b4bf6519e50 ring-buffer: Do not double count the reader_page
    f9c279ffee6b ARM: 9472/1: fix race condition on PG_dcache_clean in __sync_icache_dcache()
    cd2689d625b0 perf annotate: Use jump__delete when freeing LoongArch jumps
    5955e053ff00 KVM: nSVM: Always intercept VMMCALL when L2 is active
    009c0f726abe KVM: nSVM: Raise #UD if unhandled VMMCALL isn't intercepted by L1
    83f7e055c138 KVM: nSVM: Add missing consistency check for nCR3 validity
    0d1f3fd2664b KVM: nSVM: Drop the non-architectural consistency check for NP_ENABLE
    aabd785f9565 KVM: nSVM: Add missing consistency check for EFER, CR0, CR4, and CS
    d79720fc9959 KVM: nSVM: Clear tracking of L1->L2 NMI and soft IRQ on nested #VMEXIT
    b6656ba26525 KVM: nSVM: Clear EVENTINJ fields in vmcb12 on nested #VMEXIT
    c2fad967e652 KVM: nSVM: Clear GIF on nested #VMEXIT(INVALID)
    d6f6371bbea6 KVM: nSVM: Triple fault if mapping VMCB12 fails on nested #VMEXIT
    410ea5575c66 KVM: nSVM: Refactor writing vmcb12 on nested #VMEXIT as a helper
    72fe7d04a669 KVM: nSVM: Refactor checking LBRV enablement in vmcb12 into a helper
    49c8b2395bac KVM: nSVM: Always inject a #GP if mapping VMCB12 fails on nested VMRUN
    2b922a42b531 KVM: SVM: Add missing save/restore handling of LBR MSRs
    18ff4ab16412 KVM: SVM: Switch svm_copy_lbrs() to a macro
    a5ea402844f1 KVM: nSVM: Delay setting soft IRQ RIP tracking fields until vCPU run
    a3f0981a5a0e KVM: nSVM: Avoid clearing VMCB_LBR in vmcb12
    88572f9d83d7 KVM: nSVM: Use vcpu->arch.cr2 when updating vmcb12 on nested #VMEXIT
    3a95eb7c6950 KVM: nSVM: Delay stuffing L2's current RIP into NextRIP until vCPU run
    3428ed1529a1 KVM: nSVM: Always use NextRIP as vmcb02's NextRIP after first L2 VMRUN
    46b3827abc44 KVM: nSVM: Ensure AVIC is inhibited when restoring a vCPU to guest mode
    8302e9be9f9c KVM: SVM: Explicitly mark vmcb01 dirty after modifying VMCB intercepts
    c15392ed9e49 KVM: SVM: Inject #UD for INVLPGA if EFER.SVME=0
    497f6af9679f KVM: nSVM: Sync interrupt shadow to cached vmcb12 after VMRUN of L2
    076ab13fe321 KVM: nSVM: Sync NextRIP to cached vmcb12 after VMRUN of L2
    e07ad47e53e9 KVM: nSVM: Mark all of vmcb02 dirty when restoring nested state
    c098979293da KVM: x86: Defer non-architectural deliver of exception payload to userspace read
    26f01d03775e LoongArch: KVM: Use CSR_CRMD_PLV in kvm_arch_vcpu_in_kernel()
    fe06ea2f7b7f userfaultfd: allow registration of ranges below mmap_min_addr
    0fedd09ef952 mm/damon/core: use time_in_range_open() for damos quota window start
    b09958e235f2 mm/damon/core: validate damos_quota_goal->nid for node_mem_{used,free}_bp
    8a62c58411cb mm/damon/stat: fix memory leak on damon_start() failure in damon_stat_start()
    c42a7efb9060 mm/mempolicy: fix memory leaks in weighted_interleave_auto_store()
    687ccdf58216 mm/vmalloc: take vmap_purge_lock in shrinker
    5184e2c065e3 rtc: ntxec: fix OF node reference imbalance
    b5856e85a1f0 tpm: tpm_tis: stop transmit if retries are exhausted
    6503775a5c41 tpm: tpm_tis: add error logging for data transfer
    53e6d2d834df tpm: Use kfree_sensitive() to free auth session in tpm_dev_release()
    726ce5042359 tpm: Fix auth session leak in tpm2_get_random() error path
    f8775d9d9062 tpm2-sessions: Fix missing tpm_buf_destroy() in tpm2_read_public()
    82aa32a4d697 pwm: imx-tpm: Count the number of enabled channels in probe
    dedaa897b9d7 crypto: talitos - rename first/last to first_desc/last_desc
    4861d6cd923f crypto: talitos - fix SEC1 32k ahash request limitation
    75d40ccf38ca firmware: google: framebuffer: Do not unregister platform device
    5c293a1e1ef0 xfs: fix a resource leak in xfs_alloc_buftarg()
    fe570daa5193 xfs: start gc on zonegc_low_space attribute updates
    27f561bf894e crypto: qat - fix IRQ cleanup on 6xxx probe failure
    6d8087a7d0f3 arm64: dts: ti: am62-verdin: Enable pullup for eMMC data pins
    52e1a80bacc6 mmc: sdhci-of-dwcmshc: Disable clock before DLL configuration
    d73c3a4070dc mmc: block: use single block write in retry
    d780f24a4939 randomize_kstack: Maintain kstack_offset per task
    95d48e37a130 hwmon: (pt5161l) Fix bugs in pt5161l_read_block_data()
    6b11dfb3c517 ASoC: Intel: avs: replace strcmp with sysfs_streq
    77eb3e79a3e7 drm/amd: Fix set but not used warnings
    b3166d165753 fs: prepare for adding LSM blob to backing_file
    b69a8729f84a hwmon: (isl28022) Fix integer overflow in power calculation on 32-bit
    bff7dbfc326a power: supply: axp288_charger: Do not cancel work before initializing it
    988eff645be4 LoongArch: Show CPU vulnerabilites correctly
    c5dfddc57f1b tpm: avoid -Wunused-but-set-variable
    80f54d6f9142 extract-cert: Wrap key_pass with '#ifdef USE_PKCS11_ENGINE'
    11baa8b24bcb spi: fix resource leaks on device setup failure
    016bc6636573 libceph: Prevent potential null-ptr-deref in ceph_handle_auth_reply()
    c2178ff1c70e ipv4: icmp: validate reply type before using icmp_pointers
    9b924f3a26b2 RDMA/rxe: Validate pad and ICRC before payload_size() in rxe_rcv
    f344f04e33bf tracing/fprobe: Reject registration of a registered fprobe before init
    38387ccc0fbe slub: fix data loss and overflow in krealloc()
    9eed57e9defd drm/arcpgu: fix device node leak
    e9be7d2fb0b1 net: ks8851: Avoid excess softirq scheduling
    f826f0000100 net: mctp: fix don't require received header reserved bits to be zero
    20ba739bd627 netconsole: avoid out-of-bounds access on empty string in trim_newline()
    5424e678f9b3 net: bridge: use a stable FDB dst snapshot in RCU readers
    be8aad558b46 net: ks8851: Reinstate disabling of BHs around IRQ handler
    ea0b5d0fe963 net/smc: avoid early lgr access in smc_clc_wait_msg
    1c2afc4a1dd1 net: txgbe: fix firmware version check
    033370ffb3c9 net: rds: fix MR cleanup on copy error
    154fc7fe3f62 net: qrtr: ns: Free the node during ctrl_cmd_bye()
    7ef5b521785b arm64: dts: marvell: uDPU: add ethernet aliases
    d29cafc7e4ee net: txgbe: fix RTNL assertion warning when remove module
    491344b826a5 tools/accounting: handle truncated taskstats netlink messages
    ff591df2cd7f EDAC/versalnet: Fix memory leak in remove and probe error paths
    761c37b761ed rxrpc: Fix rxrpc_input_call_event() to only unshare DATA packets
    76cb9a2d2522 rxrpc: Fix re-decryption of RESPONSE packets
    293095ef6188 rxrpc: Fix error handling in rxgk_extract_token()
    f0d3efd03b2a rxrpc: Fix rxkad crypto unalignment handling
    ca71ac2de389 rxrpc: Fix conn-level packet handling to unshare RESPONSE packets
    861b9a0a1823 rxrpc: Fix memory leaks in rxkad_verify_response()
    996b0487b3cd rxrpc: Fix potential UAF after skb_unshare() failure
    d42d5404782f iio: adc: ad7768-1: remove switch to one-shot mode
    4ca3746d9492 iio: adc: ad7768-1: fix one-shot mode data acquisition
    54af1a51bb8b ALSA: pcmtest: Fix resource leaks in module init error paths
    91c8e75ba1f1 ALSA: pcmtest: fix reference leak on failed device registration
    89ed38540e6b ALSA: hda/realtek - Add mute LED support for HP Victus 15-fa2xxx
    1ac67f49ae2c ALSA: 6fire: Fix input volume change detection
    e59ecd4ee3a4 ALSA: caiaq: Handle probe errors properly
    30bd9ed68c84 ALSA: caiaq: Fix control_put() result and cache rollback
    33df74673674 ALSA: core: Fix potential data race at fasync handling
    9678e1b7f512 io_uring/poll: ensure EPOLL_ONESHOT is propagated for EPOLL_URING_WAKE
    ea0697129807 io_uring/poll: fix signed comparison in io_poll_get_ownership()
    23b4b18bac28 iio: adc: ti-ads7950: use iio_push_to_buffers_with_ts_unaligned()
    8661370e0865 block: relax pgmap check in bio_add_page for compatible zone device pages
    dd154d768db5 io_uring/timeout: check unused sqe fields
    81880f84cb36 block: fix zone write plugs refcount handling in disk_zone_wplug_schedule_bio_work()
    ad0126ffcba8 rbd: fix null-ptr-deref when device_add_disk() fails
    4d79d0cf6538 selftests/landlock: Skip stale records in audit_match_record()
    127ae2e73e61 selftests/landlock: Fix snprintf truncation checks in audit helpers
    1e85a1ae1452 selftests/landlock: Fix format warning for __u64 in net_test
    a496488e1702 selftests/landlock: Drain stale audit records on init
    2fcde49092aa landlock: Fix LOG_SUBDOMAINS_OFF inheritance across fork()
    df865a3bb91b selftests/mqueue: Fix incorrectly named file
    558aa1e2cd11 sched: Use u64 for bandwidth ratio calculations
    961db0b89200 reset: rzv2h-usb2phy: Keep PHY clock enabled for entire device lifetime
    06d0bed2552f remoteproc: xlnx: Only access buffer information if IPI is buffered
    8ba804869382 RDMA/mana_ib: Disable RX steering on RSS QP destroy
    dffdcbeabaac PCI: cadence: Use cdns_pcie_read_sz() for byte or word read access
    1fe317364cb5 parisc: Drop ip_fast_csum() inline assembly implementation
    e6e3724c7870 parisc: _llseek syscall is only available for 32-bit userspace
    c2462d54af3c nvme: respect NVME_QUIRK_DISABLE_WRITE_ZEROES when wzsl is set
    8bcc66896e01 nvme-pci: add NVME_QUIRK_DISABLE_WRITE_ZEROES for Kingston OM3SGP4
    d89044889ecd mtd: docg3: fix use-after-free in docg3_release()
    2774bcf71473 mm/hugetlb: fix early boot crash on parameters without '=' separator
    2691332ad88b mm/damon/core: fix damon_call() vs kdamond_fn() exit race
    d5b495ba9de0 mm/alloc_tag: clear codetag for pages allocated before page_ext initialization
    3c52d0946977 mfd: stpmic1: Attempt system shutdown twice in case PMIC is confused
    377f5ad257fb io_uring/register: fix ring resizing with mixed/large SQEs/CQEs
    cac2106bb9a2 md/raid10: fix deadlock with check operation and nowait requests
    bdf33ba450af KVM: selftests: Fix reserved value WRMSR testcase for multi-feature MSRs
    2b2fee890250 jbd2: fix deadlock in jbd2_journal_cancel_revoke()
    858bc8b9edb6 ipmi:ssif: Clean up kthread on errors
    8ebb951a284b erofs: fix the out-of-bounds nameoff handling for trailing dirents
    33074b1e6c18 ALSA: seq_oss: return full count for successful SEQ_FULLSIZE writes
    09496158f6eb ALSA: ctxfi: Add fallback to default RSR for S/PDIF
    8d3124290a03 ALSA: aoa: Skip devices with no codecs in i2sbus_resume()
    df462e82e82c ALSA: aoa: i2sbus: fix OF node lifetime handling
    e79427ee11a8 ALSA: aoa: i2sbus: clear stale prepared state
    0ae7d28dda5c mm/zsmalloc: copy KMSAN metadata in zs_page_migrate()
    2dde6377ab2e ext2: reject inodes with zero i_nlink and valid mode in ext2_iget()
    2e127ceb1c41 net: qrtr: ns: Fix use-after-free in driver remove()
    da47f8a5958c media: i2c: imx219: Check return value of devm_gpiod_get_optional() in imx219_probe()
    4d3a4638e9d2 lib/ts_kmp: fix integer overflow in pattern length calculation
    dca29d20ab23 PCI: epf-mhi: Return 0, not remaining timeout, when eDMA ops complete
    127a1fe59c78 Revert "ALSA: usb: Increase volume range that triggers a warning"
    65fc57c8b8f0 PCI: endpoint: pci-epf-ntb: Remove duplicate resource teardown
    4ca4351d269f crypto: atmel-sha204a - Fix OTP sysfs read and error handling
    26506a30e0e2 media: mtk-jpeg: fix use-after-free in release path due to uncancelled work
    19ca9475f18f net: strparser: fix skb_head leak in strp_abort_strp()
    63d21a3aa010 net: caif: clear client service pointer on teardown
    654c818a69c2 ALSA: control: Validate buf_len before strnlen() in snd_ctl_elem_init_enum_names()
    fdc150dac1ad media: amphion: Fix race between m2m job_abort and device_run
    e0a621459c61 PCI: imx6: Skip waiting for L2/L3 Ready on i.MX6SX
    b6e61356ad24 EDAC/versalnet: Fix device_node leak in mc_probe()
    b6cb07f02253 hwmon: (powerz) Fix missing usb_kill_urb() on signal interrupt
    5b6122a67a29 of: unittest: fix use-after-free in testdrv_probe()
    7f0f0926f301 of: unittest: fix use-after-free in of_unittest_changeset()
    824897e69d7a dt-bindings: display: ti, am65x-dss: Fix AM62L DSS reg and clock constraints
    77d55bc8675e crypto: pcrypt - Fix handling of MAY_BACKLOG requests
    ebc235675f24 crypto: algif_aead - snapshot IV for async AEAD requests
    efc52947247a mm: call ->free_folio() directly in folio_unmap_invalidate()
    ff8a7996dc8b spi: ch341: fix memory leaks on probe failures
    132e47030b0b spi: imx: fix use-after-free on unbind
    75f8f3c3e091 thermal: core: Fix thermal zone governor cleanup issues
    2810fc760aaf um: drivers: call kernel_strrchr() explicitly in cow_user.c
    5d6c349c9823 vfio/cdx: Fix NULL pointer dereference in interrupt trigger path
    7b436ade16cc vfio/cdx: Serialize VFIO_DEVICE_SET_IRQS with a per-device mutex
    08da3594c8ba vfio/virtio: Convert list_lock from spinlock to mutex
    7aa27b20e938 vfio: selftests: Fix VLA initialisation in vfio_pci_irq_set()
    4e179a60a60c wifi: mwifiex: fix use-after-free in mwifiex_adapter_cleanup()
    000134a20bbf wifi: rtw88: check for PCI upstream bridge existence
    a02363f71a79 zram: do not forget to endio for partial discard requests
    a516d4388662 Input: edt-ft5x06 - fix use-after-free in debugfs teardown
    3c636a3edca9 ocfs2: split transactions in dio completion to avoid credit exhaustion
    944a6864aa06 mm: migrate: requeue destination folio on deferred split queue
    3f8805b8ca23 arm64/mm: Enable batched TLB flush in unmap_hotplug_range()
    ecb3e4fa31ff firmware: google: framebuffer: Do not mark framebuffer as busy
    f51f85c04480 fs: afs: revert mmap_prepare() change
    d4d0c91a0afc kbuild: rust: allow `clippy::uninlined_format_args`
    5447be57b311 rust: dma: remove DMA_ATTR_NO_KERNEL_MAPPING from public attrs
    4404d7d2dda4 drm/nouveau: fix nvkm_device leak on aperture removal failure
    fa9a4c5e69aa device property: Make modifications of fwnode "flags" thread safe
    3e8fefd2997c driver core: Don't let a device probe until it's ready
    c1c2417c60db ibmasm: fix heap over-read in ibmasm_send_i2o_message()
    ee5737891464 ibmasm: fix OOB reads in command_file_write due to missing size checks
    22a16d3eafee misc: ibmasm: fix OOB MMIO read in ibmasm_handle_mouse_interrupt()
    b2801647c203 greybus: gb-beagleplay: fix sleep in atomic context in hdlc_tx_frames()
    fb91d4e49fcb greybus: gb-beagleplay: bound bootloader receive buffering
    438e357b3cc6 leds: qcom-lpg: Check for array overflow when selecting the high resolution
    332884f5eb79 drm/nouveau: fix u32 overflow in pushbuf reloc bounds check
    85cbf7fb568a LoongArch: Add spectre boundry for syscall dispatch table
    c578b48b9fdf ALSA: usb-audio: Evaluate packsize caps at the right place
    b216de91c0c0 usb: chipidea: core: allow ci_irq_handler() handle both ID and VBUS change
    6f480aa64d4d usb: chipidea: otg: not wait vbus drop if use role_switch
    49340680d41f usb: xhci: Make usb_host_endpoint.hcpriv survive endpoint_disable()
    f28a8281792b ALSA: usb-audio: Fix Audio Advantage Micro II SPDIF switch
    9bbbbbd404d3 ALSA: usb-audio: Avoid false E-MU sample-rate notifications
    4d7893a137ea ALSA: usb-audio: stop parsing UAC2 rates at MAX_NR_RATES

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agolinux-yocto/6.18: update CVE exclusions (6.18.26)
Bruce Ashfield [Mon, 11 May 2026 20:25:11 +0000 (16:25 -0400)] 
linux-yocto/6.18: update CVE exclusions (6.18.26)

Data pulled from: https://github.com/CVEProject/cvelistV5

    1/1 [
        Author: cvelistV5 Github Action
        Email: github_action@example.com
        Subject: 4 changes (3 new | 1 updated): - 3 new CVEs: CVE-2026-7718, CVE-2026-7719, CVE-2026-7720 - 1 updated CVEs: CVE-2026-4878
        Date: Mon, 4 May 2026 01:53:11 +0000

    ]

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agolinux-yocto/6.18: update to v6.18.26
Bruce Ashfield [Mon, 11 May 2026 20:25:10 +0000 (16:25 -0400)] 
linux-yocto/6.18: update to v6.18.26

Updating linux-yocto/6.18 to the latest korg -stable release that comprises
the following commits:

    1fe06068166d4 Linux 6.18.26
    d5f59216650c5 Buffer overflow in drivers/xen/sys-hypervisor.c
    446ee446d9ae6 xen/privcmd: fix double free via VMA splitting

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agolinux-yocto/6.18: update CVE exclusions (6.18.25)
Bruce Ashfield [Mon, 11 May 2026 20:25:09 +0000 (16:25 -0400)] 
linux-yocto/6.18: update CVE exclusions (6.18.25)

Data pulled from: https://github.com/CVEProject/cvelistV5

    1/1 [
        Author: cvelistV5 Github Action
        Email: github_action@example.com
        Subject: 83 changes (9 new | 74 updated): - 9 new CVEs: CVE-2026-27760, CVE-2026-40556, CVE-2026-40968, CVE-2026-7282, CVE-2026-7320, CVE-2026-7321, CVE-2026-7322, CVE-2026-7323, CVE-2026-7324 - 74 updated CVEs: CVE-2024-46636, CVE-2025-10539, CVE-2025-48431, CVE-2026-24354, CVE-2026-24361, CVE-2026-24367, CVE-2026-24368, CVE-2026-24369, CVE-2026-24370, CVE-2026-24371, CVE-2026-24373, CVE-2026-24374, CVE-2026-24375, CVE-2026-24376, CVE-2026-24377, CVE-2026-24378, CVE-2026-24379, CVE-2026-24380, CVE-2026-24381, CVE-2026-24382, CVE-2026-24383, CVE-2026-24384, CVE-2026-24385, CVE-2026-24386, CVE-2026-24387, CVE-2026-24388, CVE-2026-24389, CVE-2026-24390, CVE-2026-24391, CVE-2026-24392, CVE-2026-24521, CVE-2026-24522, CVE-2026-24523, CVE-2026-24525, CVE-2026-24526, CVE-2026-24528, CVE-2026-24529, CVE-2026-24530, CVE-2026-24531, CVE-2026-24532, CVE-2026-25422, CVE-2026-25423, CVE-2026-25428, CVE-2026-25432, CVE-2026-25451, CVE-2026-25453, CVE-2026-25459, CVE-2026-25463, CVE-2026-25472, CVE-2026-25473, CVE-2026-28130, CVE-2026-28131, CVE-2026-28132, CVE-2026-28133, CVE-2026-28134, CVE-2026-28136, CVE-2026-28137, CVE-2026-28138, CVE-2026-40966, CVE-2026-41365, CVE-2026-41371, CVE-2026-41525, CVE-2026-41602, CVE-2026-4805, CVE-2026-5779, CVE-2026-5780, CVE-2026-5781, CVE-2026-7156, CVE-2026-7178, CVE-2026-7237, CVE-2026-7244, CVE-2026-7267, CVE-2026-7272, CVE-2026-7309
        Date: Tue, 28 Apr 2026 14:21:46 +0000

    ]

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agolinux-yocto/6.18: update to v6.18.25
Bruce Ashfield [Mon, 11 May 2026 20:25:08 +0000 (16:25 -0400)] 
linux-yocto/6.18: update to v6.18.25

Updating linux-yocto/6.18 to the latest korg -stable release that comprises
the following commits:

    a256b1e6892e7 Linux 6.18.25
    ce383ba615339 rxrpc: Fix missing validation of ticket length in non-XDR key preparsing
    2937f17bbeefb crypto: ccp: Don't attempt to copy ID to userspace if PSP command failed
    051e51aa55fd4 crypto: ccp: Don't attempt to copy PDH cert to userspace if PSP command failed
    111dcc6d0f016 crypto: ccp: Don't attempt to copy CSR to userspace if PSP command failed
    28324a3b62d9c net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd()
    6473ed16df1fe ALSA: caiaq: take a reference on the USB device in create_card()
    f8397fc0ff9a4 ALSA: hda/realtek: Add quirk for Legion S7 15IMH
    1d30e8d4a07c1 ALSA: usb-audio: apply quirk for MOONDROP JU Jiu
    c76cf339b8797 f2fs: fix use-after-free of sbi in f2fs_compress_write_end_io()
    028103656b842 writeback: Fix use after free in inode_switch_wbs_work_fn()
    feefd5d5b5ee2 ksmbd: reset rcount per connection in ksmbd_conn_wait_idle_sess_id()
    5e7b8f3c539d6 ksmbd: use check_add_overflow() to prevent u16 DACL size overflow
    790304c02bf9b ksmbd: fix out-of-bounds write in smb2_get_ea() EA alignment
    3e5360b422dd7 ksmbd: validate num_aces and harden ACE walk in smb_inherit_dacl()
    299db777ea0cf ksmbd: validate response sizes in ipc_validate_msg()
    078fae8f50ade smb: client: fix OOB read in smb2_ioctl_query_info QUERY_INFO path
    38a69f08ee82c smb: client: require a full NFS mode SID before reading mode bits
    3943e4565aae7 smb: server: fix max_connections off-by-one in tcp accept path
    283027aa93380 smb: server: fix active_num_conn leak on transport allocation failure
    90089584b2e25 ksmbd: require minimum ACE size in smb_check_perm_dacl()
    3fa185e320197 fuse: fuse_dev_ioctl_clone() should wait for device file to be initialized
    9ef130452eaf1 fuse: quiet down complaints in fuse_conn_limit_write
    1381635aeb7f8 fuse: Check for large folio with SPLICE_F_MOVE
    0c7fca880a40a fuse: abort on fatal signal during sync init
    7de93abfaae1b fuse: reject oversized dirents in page cache
    59970b2586fef f2fs: fix to avoid uninit-value access in f2fs_sanity_check_node_footer
    047c0aef6af37 f2fs: fix to avoid memory leak in f2fs_rename()
    963d2e24d9d92 f2fs: fix UAF caused by decrementing sbi->nr_pages[] in f2fs_write_end_io()
    748c5d08f1a92 f2fs: fix to do sanity check on dcc->discard_cmd_cnt conditionally
    0112e6279420d fs/ntfs3: validate rec->used in journal-replay file record check
    f218fb82877b1 scripts/dtc: Remove unused dts_version in dtc-lexer.l
    c846ed5ac80fa lib/crypto: tests: Drop the default to CRYPTO_SELFTESTS
    ca47b87f24571 kunit: configs: Enable all crypto library tests in all_tests.config
    95c05443aa34e lib/crypto: tests: Introduce CRYPTO_LIB_ENABLE_ALL_FOR_KUNIT
    b0ca42c018837 lib/crypto: tests: Add a .kunitconfig file
    05f723be4d641 kunit: configs: Enable all CRC tests in all_tests.config
    04c61029a3b76 lib/crc: tests: Add a .kunitconfig file
    6897bdfa505f9 lib/crc: tests: Add CRC_ENABLE_ALL_FOR_KUNIT
    e70c01412893c lib/crc: tests: Make crc_kunit test only the enabled CRC variants
    28f77fca44497 sched/debug: Fix avg_vruntime() usage
    c6c87a23de4bd arm64: errata: Work around early CME DVMSync acknowledgement
    ee5ce483d4280 arm64: cputype: Add C1-Pro definitions
    456d6040bb3b2 arm64: tlb: Pass the corresponding mm to __tlbi_sync_s1ish()
    e785d2751b1db arm64: tlb: Introduce __tlbi_sync_s1ish_{kernel,batch}() for TLB maintenance
    243cec136a748 arm64: tlb: Optimize ARM64_WORKAROUND_REPEAT_TLBI
    609624576b6fd arm64: tlb: Allow XZR argument to TLBI ops
    00ce8d6789dae ksmbd: validate owner of durable handle on reconnect
    3d6682726c2d3 ksmbd: fix use-after-free in __ksmbd_close_fd() via durable scavenger
    377bbec04e167 scripts: generate_rust_analyzer.py: define scripts
    07cbb1bd42437 crypto: krb5enc - fix async decrypt skipping hash verification
    41d151254caa7 crypto: krb5enc - fix sleepable flag handling in encrypt dispatch
    b7cddf6c01751 drm/amdgpu: replace PASID IDR with XArray
    e97593f32bd57 net: ethernet: mtk_eth_soc: initialize PPE per-tag-layer MTU registers
    c5cedee5d9738 ipv6: add NULL checks for idev in SRv6 paths
    ecc0eb147806f crypto: authencesn - Fix src offset when decrypting in-place

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agoexpat: Upgrade 2.8.0 -> 2.8.1
Richard Purdie [Wed, 13 May 2026 11:52:18 +0000 (12:52 +0100)] 
expat: Upgrade 2.8.0 -> 2.8.1

https://blog.hartwork.org/posts/expat-2-8-1-released/

Security fixes:
  #1216  CVE-2026-45186 -- Fix quadratic runtime from attribute name
            collision checks that allowed denial of service attacks
            through moderately sized crafted XML input (CWE-407).
            Please note that a layer of compression around XML can
            significantly reduce the minimum attack payload size.

Other changes:
  #1209 #1213  Drop more casts related to `void *` that C99 does not need
  #1213        xmlwf: Streamline use of `mmap`
  #1214 #1217  Version info bumped from 13:0:12 (libexpat*.so.1.12.0)
                    to 13:1:12 (libexpat*.so.1.12.1); see https://verbump.de/
                    for what these numbers do

Infrastructure:
  #1210  CI: Cover compilation with Visual Studio 18 2026 on Windows
  #1215  CI: Cover compilation for ARM64 on Windows
  #1212  CI: Bump WASI SDK from 32 to 33

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agopython3: upgrade 3.14.4 -> 3.14.5
Peter Marko [Mon, 11 May 2026 22:34:19 +0000 (00:34 +0200)] 
python3: upgrade 3.14.4 -> 3.14.5

Release notes: [1] and [2].

Resolves following CVEs from reports:
* CVE-2026-1502
* CVE-2026-3087 (Windows specific)
* CVE-2026-3298 (Windows specific)
* CVE-2026-4786 (explicitly set, see Debian security tracker)
* CVE-2026-5713 (explicitly set, see Debian security tracker)
* CVE-2026-6019 (explicitly set, see Debian security tracker)
* CVE-2026-6100 (explicitly set, see Debian security tracker)
Also some security issues without CVE assignment.

Refresh patches.

[1] https://docs.python.org/3/whatsnew/changelog.html#python-3-14-5-final
[2] https://docs.python.org/3/whatsnew/changelog.html#python-3-14-5-release-candidate-1

Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agolibhandy: remove
Ross Burton [Tue, 12 May 2026 16:30:54 +0000 (17:30 +0100)] 
libhandy: remove

This library was added for epiphany which no longer uses it and there
are no other users, so remove it.

The recipe will be added to meta-gnome for the GTK+3 applications there.

Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agolibdazzle: remove
Ross Burton [Tue, 12 May 2026 16:30:53 +0000 (17:30 +0100)] 
libdazzle: remove

This library was added for epiphany which no longer uses it and there
are no other users, so remove it.

The recipe will be added to meta-gnome for the GTK+3 applications there.

Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agoepiphany: remove obsolete build dependencies
Ross Burton [Tue, 12 May 2026 16:30:52 +0000 (17:30 +0100)] 
epiphany: remove obsolete build dependencies

Epiphany ported to GTK 4 in v44 onwards[1] and as part of this work the
dependencies on libdazzle and libhandy were removed.

[1] epiphany 6e5357947 ("Port to GTK4")

Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agoepiphany: use GTK3DISTROFEATURES in features check
Ross Burton [Tue, 12 May 2026 16:30:51 +0000 (17:30 +0100)] 
epiphany: use GTK3DISTROFEATURES in features check

Epiphany uses GTK 4, so it depends on both opengl and either x11 or
wayland (as set by GTK3DISTROFEATURES).

I've verified that Epiphany builds in wayland-only configurations without
x11 enabled.

Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agolibrsvg: rewrite cross gdk-pixbuf-query-loaders handling
Ross Burton [Tue, 12 May 2026 13:54:07 +0000 (14:54 +0100)] 
librsvg: rewrite cross gdk-pixbuf-query-loaders handling

There's been a number of attempts at fixing the logic as to when to run
gdk-pixbuf-query-loaders in cross builds. Originally the build failed in
cross so we worked around that, then upstream changed it so that if exe
wrappers are enabled it will run those but our target sysroot doesn't
have binaries so that also fails.

This rework should be upstreamable once it's been shaken out in OE for a
while, and improves the logic so that in cross builds the existance of
gdk-pixbuf-query-loaders is an optional dependency, which is ideal for
our needs as we won't be running it at install-time anyway.

Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agolibrsvg: consolidate PACKAGECONFIG
Ross Burton [Tue, 12 May 2026 13:54:06 +0000 (14:54 +0100)] 
librsvg: consolidate PACKAGECONFIG

Explictly appending PACKAGECONFIG makes it harder to directly control
PACKAGECONFIG, merge the assignments to keep it simple.

This does not change the behaviour of native builds as G-I is disabled
in native.

Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agolibrsvg: consolidate DEPENDS
Ross Burton [Tue, 12 May 2026 13:54:05 +0000 (14:54 +0100)] 
librsvg: consolidate DEPENDS

There's no reason to append cargo-native to BASEDEPENDS when it can just
be added to DEPENDS.

Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agolibrsvg: remove obsolete .la deletion
Ross Burton [Tue, 12 May 2026 13:54:04 +0000 (14:54 +0100)] 
librsvg: remove obsolete .la deletion

librsvg is built with Meson now, so there's no need to delete .a or .la
files that don't exist.

Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agoweston: remove obsolete .la deletion
Ross Burton [Tue, 12 May 2026 13:54:03 +0000 (14:54 +0100)] 
weston: remove obsolete .la deletion

Weston is built with Meson now, so there's no need to delete .la files
that don't exist.

Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agosbom-cve-check: set PV from upstream tags and ensure version checks are correct
Alexander Kanavin [Tue, 12 May 2026 10:10:02 +0000 (12:10 +0200)] 
sbom-cve-check: set PV from upstream tags and ensure version checks are correct

These recipes didn't set PV, which by default is 1.0. This isn't correct:
upstream does provide date-based tags that can be used to perform version upgrades.

Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agoqemu: fix iotlb_to_section() for different AddressSpace
Quan Sun [Mon, 11 May 2026 20:52:02 +0000 (13:52 -0700)] 
qemu: fix iotlb_to_section() for different AddressSpace

Backport upstream commit 854cd16e318e ("accel/tcg: Fix iotlb_to_section()
for different AddressSpace") to qemu 10.2.0.

The bug causes incorrect memory load/store when CPU access goes through
an IOMMUMemoryRegion that returns a different target AddressSpace, and the
fix replaces the section_index lookup with a direct MemoryRegionSection
pointer stored in CPUTLBEntryFull.

Note that the fix primarily targets ARM/RISC-V, but since it eliminates
iotlb_to_section() and performs the lookup based on CPUTLBEntryFull,
it may also help address some currently observed QEMU boot issues
on x86, e.g. the https://bugzilla.yoctoproject.org/show_bug.cgi?id=16259.

AI-Generated: kiro-cli

Signed-off-by: Quan Sun <Quan.Sun@windriver.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agooe/lsb: Only read /etc/os-release
Paul Barker [Mon, 11 May 2026 13:51:21 +0000 (14:51 +0100)] 
oe/lsb: Only read /etc/os-release

Over time, distros have standardised on providing distro name and
version information via /etc/os-release. All of our currently supported
distros contain this file, so we can drop support for gathering distro
name and version information via other methods.

Signed-off-by: Paul Barker <paul@pbarker.dev>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agooe-pkgdata-util: fix runtime-rprovides handling in lookup_pkg error path
Thomas Perrot [Mon, 11 May 2026 10:13:54 +0000 (12:13 +0200)] 
oe-pkgdata-util: fix runtime-rprovides handling in lookup_pkg error path

Commit 678c1c207731 applied os.path.isdir() + non-empty check to three
functions, but the error-reporting path in lookup_pkg introduced by
commit 46ff3a8d2c18 was left using os.path.exists() + os.listdir().
This is fragile: it raises NotADirectoryError if the path exists but is
a file, and silently falls through to the generic error on an empty
directory rather than skipping the rprovides block.

Apply the same pattern used elsewhere for consistency.

Signed-off-by: Thomas Perrot <thomas.perrot@bootlin.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agoscripts/makefile-getvar: quote MAKEFILE variable
Thomas Perrot [Mon, 11 May 2026 10:13:27 +0000 (12:13 +0200)] 
scripts/makefile-getvar: quote MAKEFILE variable

$MAKEFILE was unquoted in the -f test and the error echo, causing
word-splitting on paths that contain spaces.

Signed-off-by: Thomas Perrot <thomas.perrot@bootlin.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agosbom-cve-check-update-nvd-native: Update source revision
Benjamin Robin (Schneider Electric) [Fri, 8 May 2026 09:49:27 +0000 (11:49 +0200)] 
sbom-cve-check-update-nvd-native: Update source revision

Update source revision to v2026.05.07-000006

Signed-off-by: Benjamin Robin (Schneider Electric) <benjamin.robin@bootlin.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agosbom-cve-check-update-cvelist-native: Update source revision
Benjamin Robin (Schneider Electric) [Fri, 8 May 2026 09:49:26 +0000 (11:49 +0200)] 
sbom-cve-check-update-cvelist-native: Update source revision

Update source revision to cve_2026-05-07_1300Z

Signed-off-by: Benjamin Robin (Schneider Electric) <benjamin.robin@bootlin.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agopython3-sbom-cve-check: Update to version 1.3.1
Benjamin Robin (Schneider Electric) [Fri, 8 May 2026 09:49:25 +0000 (11:49 +0200)] 
python3-sbom-cve-check: Update to version 1.3.1

For details on this new release which fixes various bugs, see:
https://github.com/bootlin/sbom-cve-check/releases/tag/v1.3.1

Also, update the LICENSE, which is now GPL-2.0-or-later instead of
GPL-2.0-only, to be compatible with the licence dependencies.

Signed-off-by: Benjamin Robin (Schneider Electric) <benjamin.robin@bootlin.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agoffmpeg: upgrade 8.0.1 -> 8.1.1
Peter Marko [Wed, 6 May 2026 21:28:40 +0000 (23:28 +0200)] 
ffmpeg: upgrade 8.0.1 -> 8.1.1

Solves CVE-2025-12343, CVE-2025-69693 and CVE-2026-40962.

Remove patches included in this release and refresh remaining patch.

Remove obsolete CVE_STATUS assigments for CVEs no longer reported as
unpatched with this new version.

Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agoglibc: stable 2.43 branch updates
Peter Marko [Thu, 7 May 2026 22:48:13 +0000 (00:48 +0200)] 
glibc: stable 2.43 branch updates

$ git log --oneline ce1013a197eb4a3b8ff2b07e0672f4d0b976ce7c..e9517114acc77c0b8af9da6700107df16882b701
e9517114ac (origin/release/2.43/master) abilist.awk: Handle weak unversioned defined symbols
1634cc11a5 Linux: Only define OPEN_TREE_* macros in <sys/mount.h> if undefined (bug 33921)
d1d8d27164 include: isolate __O_CLOEXEC flag for sys/mount.h and fcntl.h
8362e8ce10 Use pending character state in IBM1390, IBM1399 character sets (CVE-2026-4046)

Testing Results:
+--------------+--------+--------+------+
| Result       | Before | After  | Diff |
+--------------+--------+--------+------+
| PASS         | 6629   | 6632   | +3   |
| XPASS        | 4      | 4      |  0   |
| FAIL         | 105    | 103    | -2   |
| XFAIL        | 16     | 16     |  0   |
| UNSUPPORTED  | 559    | 559    |  0   |
+--------------+--------+--------+------+

Changes in failed testcases:
malloc/tst-malloc-fork-deadlock-malloc-check  FAIL  PASS
malloc/tst-malloc-too-large-malloc-check      PASS  FAIL
nptl/tst-getpid3                              FAIL  PASS
stdlib/tst-qsort3                             FAIL  PASS

Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agogo: upgrade 1.26.2 -> 1.26.3
Peter Marko [Thu, 7 May 2026 19:53:38 +0000 (21:53 +0200)] 
go: upgrade 1.26.2 -> 1.26.3

Upgrade to latest 1.26.x release [1]:

$ git --no-pager log --oneline go1.26.2..go1.26.3
2dc996f71b (tag: go1.26.3) [release-branch.go1.26] go1.26.3
8282c628a0 [release-branch.go1.26] cmd/go: reject sumdb response lacking module hash
3baf3eec3b [release-branch.go1.26] all: avoid unsafe StringToUTF16Ptr on Windows
0bec63330d [release-branch.go1.26] net/mail: fix quadratic consumePhrase behavior
7136366ebf [release-branch.go1.26] cmd/go: invalidate test cache when -coverpkg dependencies change
722b68ceca [release-branch.go1.26] cmd/compile: keep blank nodes alive in b.loop
3ae315a8cd [release-branch.go1.26] os: avoid panic when RemoveAll fails to remove a symlink
c9f97f50c4 [release-branch.go1.26] html/template: fix escaping of URLs in meta content attributes
40fa774fff [release-branch.go1.26] cmd/pack: refuse to extract files with directory components
d9389d318b [release-branch.go1.26] net/mail: fix quadratic complexity in consumeComment
dd29b59a2b [release-branch.go1.26] cmd/compile: fix loopvar version detection with line directives
18fa391f45 [release-branch.go1.26] crypto/fips140: add package docs
e0f5c054cb [release-branch.go1.26] net: avoid double-free of cgo pointer when handling large DNS response
2992086cf8 [release-branch.go1.26] lib/fips140: add certified pointing to v1.0.0-c2097c7c
f43caf8712 [release-branch.go1.26] lib/fips140: update inprocess to v1.26.0
19d2ce3401 [release-branch.go1.26] runtime: fix timespec definition on 32bits systems
e9df527f06 [release-branch.go1.26] crypto/tls: wrap ML-KEM hybrids in fips140.WithoutEnforcement
73f417a37c [release-branch.go1.26] go/types, types2: handle unconstrained type parameters correctly in a few places
50856a181c [release-branch.go1.26] cmd/go: use MkdirTemp to create temp directory for "go bug"
e137885d68 [release-branch.go1.26] cmd/compile/internal/devirtualize: use pointer identity for type comparison
c9712872cc [release-branch.go1.26] crypto/internal/fips140/drbg: build tag out entropy generation on Wasm
cb994d85ff [release-branch.go1.26] cmd/fix: change -diff to exit 1 if diffs exist
95470667eb [release-branch.go1.26] net/http/httputil: reencode queries with many parameters in proxy
9b01c04815 [release-branch.go1.26] html/template: fix escaper bypass by treating empty script type as JavaScript
be12fe151c [release-branch.go1.26] runtime: use uname version check for 64-bit time on 32-bit arch codepaths
ec5ebece41 [release-branch.go1.26] all: update x/net to 705de46f
710f29a758 [release-branch.go1.26] runtime: add sysUnreserve to undo sysReserve
efdc0fb354 [release-branch.go1.26] cmd/compile: handle min integer step in loop
ba4554f03b [release-branch.go1.26] cmd/go: specify full path to go command when running go tool covdata
f4e425d342 [release-branch.go1.26] fix incorrect loop trip counts
0b4d5f85e6 [release-branch.go1.26] cmd/link: use bfd ld 2.36+ on linux/arm64 instead of gold

Fixes CVE-2026-42501, CVE-2026-39825, CVE-2026-39836, CVE-2026-42499,
      CVE-2026-39820, CVE-2026-39819, CVE-2026-39817, CVE-2026-33814,
      CVE-2026-39826, CVE-2026-33811 and CVE-2026-39823.

Drop patch handling gold linker as upstream implemented gold linker
availability autodetection with [3].

Release information: [2]

[1] https://github.com/golang/go/compare/go1.26.2...go1.26.3
[2] https://groups.google.com/g/golang-announce/c/qcCIEXso47M
[3] https://github.com/golang/go/commit/0b4d5f85e68ea79b61de9989f9f37a984eb11289

Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agotime: 1.9 -> 1.10
Robert Yang [Fri, 8 May 2026 14:44:59 +0000 (07:44 -0700)] 
time: 1.9 -> 1.10

* Remove uneed patch, the src/resuse.c has been removed in 1.10:
  0001-include-string.h-for-memset.patch

* Remove backported patches:
  0002-maint-remove-K-R-declarations.patch
  0003-maint-fix-compilation-errors-with-GCC-15.patch
  0004-maint-remove-obsolete-autoconf-macros.patch

Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agofeatures-check.bbclass: add reference to required TUNE_FEATURES
Robert P. J. Day [Fri, 8 May 2026 15:13:13 +0000 (11:13 -0400)] 
features-check.bbclass: add reference to required TUNE_FEATURES

While commit a8ef7339ecb9eee909224e7cf23ccd48ef105d93 added the
string 'TUNE' to add support for checking required TUNE_FEATURES,
the comment was not adjusted appropriately.

Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agoshadow-native: Change upstream status of disable_syslog.patch
Dmitry Sakhonchik [Thu, 7 May 2026 12:14:34 +0000 (15:14 +0300)] 
shadow-native: Change upstream status of disable_syslog.patch

Upstream has accepted configure option and merged it into their master branch.

https://github.com/shadow-maint/shadow/pull/1618

After they release v4.20 we can remove the patch and rewrite recipe with the configure option.

Fixes [YOCTO #15785]

Signed-off-by: Dmitry Sakhonchik <frezidok1@gmail.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agoutils: Handle unexpanded variables in DISTRO_FEATURES
Richard Purdie [Fri, 8 May 2026 06:46:05 +0000 (07:46 +0100)] 
utils: Handle unexpanded variables in DISTRO_FEATURES

If you have an unset variable in DISTRO_FEATURES, very strange things appear to
happen. Currently, this shows up as seccomp appearing in PACKAGECONFIG for
gnutls-native which isn't what the user configured.

The issue happens if you have a variable in DISTRO_FEATURES which cannot be
expanded.

Add some code to detect, warn and work around such a thing. Create a function to
allow this to be done in one place.

[YOCTO #16275]

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agoinitramfs-framework: overlayroot: Don't assume rootfs location
Marcus Flyckt [Fri, 8 May 2026 08:50:53 +0000 (10:50 +0200)] 
initramfs-framework: overlayroot: Don't assume rootfs location

Instead of assuming that the old rootfs is located at /rootfs, use the
ROOTFS_DIR variable.

This makes it possible to change rootfs location between the rootfs
module and the overlayroot module.

Signed-off-by: Marcus Flyckt <marcus.flyckt@kvaser.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agogstreamer1.0-plugins-bad: disble vulkan when x11/wayland not enabled
Changqing Li [Sat, 9 May 2026 05:01:29 +0000 (13:01 +0800)] 
gstreamer1.0-plugins-bad: disble vulkan when x11/wayland not enabled

When vulkan is enabled in DISTRO_FEATURES without x11 or wayland,
do_configure will failed with error:
gst-libs/gst/vulkan/meson.build:311:4: ERROR: Problem encountered: No Windowing system found. vulkansink will not work

disable vulkan from PACKAGECONFIG when x11 and wayland is not enabled

Signed-off-by: Changqing Li <changqing.li@windriver.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agogo: ptest: fix GOROOT detection and improve cleanup/exit handling
Pratik Farkase [Fri, 8 May 2026 14:42:19 +0000 (16:42 +0200)] 
go: ptest: fix GOROOT detection and improve cleanup/exit handling

Changes:
  - Derive GOROOT dynamically from PTEST_DIR instead of hardcoding
    /usr/lib/go, which breaks on distros using lib64.
  - Track and clean up VERSION and pkg/include files that were copied
    into GOROOT, preventing stale artifacts after ptest runs.
  - Track failures with RC variable and exit non-zero when tests fail,
    consistent with other ptest scripts.

Signed-off-by: Pratik Farkase <pratik.farkase@est.tech>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agokernel: Disable module deploy tarball by default
Richard Purdie [Thu, 7 May 2026 12:16:44 +0000 (13:16 +0100)] 
kernel: Disable module deploy tarball by default

These module tarballs were once useful for certain development workflows. They
are not that useful when deployed in CI, taking up space as release artefacts.

Not generating them by default saves time/space and users who need/use them can
enable them, this makes more sense as a modern default.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agobusybox: patch CVE-2024-58251
Peter Marko [Sun, 10 May 2026 09:26:34 +0000 (11:26 +0200)] 
busybox: patch CVE-2024-58251

Pick patch applied by Debian [1].

I did not find any reference on busybox mailing list that this patch was
submitted. Submitting patch for someone else would be inappropriate,
and busybox is currently known to be very inactive, hence the unwanted
Pending Upstream-Status status.
Also note that the related busybox bugreport [2] is currently not
public, so it is possible that it was submitted there.

[1] https://sources.debian.org/patches/busybox/1:1.37.0-10.1/netstat-sanitize-argv0-for-p-CVE-2024-58251.patch/
[2] https://bugs.busybox.net/show_bug.cgi?id=15922

Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agolibsoup: patch CVE-2026-2708
Peter Marko [Sun, 10 May 2026 09:26:18 +0000 (11:26 +0200)] 
libsoup: patch CVE-2026-2708

Pick patch per [1].

[1] https://security-tracker.debian.org/tracker/CVE-2026-2708

Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agoxserver-xorg: set status for CVE-2026-34000 and CVE-2026-34002
Peter Marko [Sat, 9 May 2026 22:45:36 +0000 (00:45 +0200)] 
xserver-xorg: set status for CVE-2026-34000 and CVE-2026-34002

These are version-less RedHat CVEs.

[1] points to [2].
This was backported as [3 ]in v22.1.22.

[4] points to [5].
This was backported as [6] in v22.1.22.

[1] https://security-tracker.debian.org/tracker/CVE-2026-34000
[2] https://gitlab.freedesktop.org/xorg/xserver/-/commit/81b6a34f90b28c32ad499a78a4f391b7c06daea2
[3] https://gitlab.freedesktop.org/xorg/xserver/-/commit/a48d67f38753de551cd177e471b545bd8b9b1b64
[4] https://security-tracker.debian.org/tracker/CVE-2026-34002
[5] https://gitlab.freedesktop.org/xorg/xserver/-/commit/f056ce1cc96ed9261052c31524162c78e458f98c
[6] https://gitlab.freedesktop.org/xorg/xserver/-/commit/5328a544ba6c32ecdd1758283ee69058dec100f8

Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agogdk-pixbuf: set status for 2.44.6
Peter Marko [Sat, 9 May 2026 22:45:35 +0000 (00:45 +0200)] 
gdk-pixbuf: set status for 2.44.6

This is a version-less RedHat CVE.
[1] points to [2] included in v2.44.6.

[1] https://security-tracker.debian.org/tracker/CVE-2026-5201
[2] https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/commit/6cce9311e70b969cbcc6e3e1e74ae1756ed02d5b

Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agolibxml2: set status for CVE-2026-6732
Peter Marko [Sat, 9 May 2026 22:45:34 +0000 (00:45 +0200)] 
libxml2: set status for CVE-2026-6732

This is a version-less RedHat CVE.
[1] points to [2] and [3].
These were backported as [4] and [5] in v2.15.3.

[1] https://security-tracker.debian.org/tracker/CVE-2026-6732
[2] https://gitlab.gnome.org/GNOME/libxml2/-/commit/226b560837b90dea9b14431eca6e6fda8fb01ab4
[3] https://gitlab.gnome.org/GNOME/libxml2/-/commit/7cea3fd1557437b88f2c7b5e1b71a2d5fb152b55
[4] https://gitlab.gnome.org/GNOME/libxml2/-/commit/ad0f009a8366860272acb8e05c41a401798f2855
[5] https://gitlab.gnome.org/GNOME/libxml2/-/commit/65d0fe61c6f36ee40431aeb041ea703e839ff60d

Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3 weeks agorpm-sequoia: set status for CVE-2026-2625
Peter Marko [Sat, 9 May 2026 22:45:33 +0000 (00:45 +0200)] 
rpm-sequoia: set status for CVE-2026-2625

This is a version-less RedHat CVE.
[1] points to [2] included in v1.10.2.

[1] https://security-tracker.debian.org/tracker/CVE-2026-2625
[2] https://github.com/rpm-software-management/rpm-sequoia/commit/fa3c60094fa853ede6b4862e936f246412d700de

Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 weeks agopython3-requests: update to 2.33.1
Daniel McGregor [Thu, 30 Apr 2026 19:51:20 +0000 (13:51 -0600)] 
python3-requests: update to 2.33.1

OE Core includes chardet 6.0, while requests warns for any version
greater than or equal to 6.0. requests > 2.33 support chardet up
to version 8, so import the new release.

Signed-off-by: Daniel McGregor <daniel.mcgregor@vecima.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
4 weeks agooe-pkgdata-util: fix empty runtime-rprovides directory handling
Sam Kent [Tue, 5 May 2026 18:28:42 +0000 (19:28 +0100)] 
oe-pkgdata-util: fix empty runtime-rprovides directory handling

An empty runtime-provides directory caused lookup-recipe, package-info
and list-pkg-files to skip the runtime-reverse fallback.

Use os.listdir() to ensure the folder is not empty and use
os.path.isdir( to ensure it is not a file.

Signed-off-by: Sam Kent <sam.john.kent@gmail.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 weeks agoperf: make libraries for install_headers configurable
Peter Marko [Tue, 5 May 2026 09:46:01 +0000 (11:46 +0200)] 
perf: make libraries for install_headers configurable

Older kernels don't support install_headers for all libraries.
For instance kernel 6.1 fails for two (api and symbol) with:
make: *** No rule to make target 'install_headers'.  Stop.

Also sort the list when moving to variable.

Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 weeks agoefivar: Backport patch to fix -march issue for ppc64le
Andrew Geissler [Tue, 5 May 2026 14:36:54 +0000 (09:36 -0500)] 
efivar: Backport patch to fix -march issue for ppc64le

Backport upstream commit 9711b8aa5acc to fix compilation errors on ppc64le
architecture. The issue occurs because GCC on ppc64le does not recognize the
'-march=native' option and suggests using '-mcpu=native' instead.

Upstream commit:
https://github.com/rhboot/efivar/commit/9711b8aa5acc63c54a12ba5505fe68b4475c8a13

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4 weeks agoglibc: Fix recipe bug that disabled stack protector
Ivan Nestlerode [Mon, 4 May 2026 21:28:43 +0000 (17:28 -0400)] 
glibc: Fix recipe bug that disabled stack protector

Fixes [YOCTO #16265]

The glibc recipe is supposed to be building with
--enable-stack-protector=strong, but some CACHED_CONFIGVARS values are
actually breaking this, causing glibc to be built with no stack
protector at all.

Remove these CACHED_CONFIGVARS values so that stack protector support is
detected properly in do_configure and then enabled properly during
do_compile.

Full details are here:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=16265

Signed-off-by: Ivan Nestlerode <ivan.nestlerode@sonos.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>