[ciq-6.18.y-next] Multiple patches tested (100 commits)

[ciq-kernel-automation]

Summary

This PR has been automatically created after successful completion of all CI stages.

Commit Message(s)

[CIQ] v6.18.20 - updated spec

[CIQ] v6.18.21 - updated spec

github actions: Inherit the Kernel CI Automated workflow from main

spec: Skip certificate setup for noarch builds

Update spec for ciq_kernel-6.18.21-2

We've picked up a source code change to fix a kallsym issue and
a spec file change to address noarch builds while secure boot signing

github actions: Use trigger for kernelCI

Signed-off-by: Brett Mastbergen <bmastbergen@ciq.com>

github actions: Trigger kernelCI on ciq-6.18.y-next branches

[CIQ] v6.18.22 - updated spec

spec: Fix posttrans script to handle noarch package expansion

[CIQ] ciq_kernel-6.18.22-2 - updated spec

spec: update branding in package descriptions and log messages

github actions: add RPM build workflow for x86_64 and aarch64

configs: enable legacy iptables/ip6tables support for all architectures

A customer running anetd (Google's GKE networking agent, a fork of
Cilium) reported that their nodes fail to reach Ready status because
anetd fatally exits when it cannot load the ip6_tables, ip6table_filter,
ip6table_mangle, and ip6table_raw kernel modules.

Add generic kernel Provides to spec

Adds 'Provides: kernel = version' to base package for compatibility
with packages depending on generic kernel capability.

Add generic kernel-headers and kernel-devel Provides to spec

Add versioned Provides for kernel-headers, kernel-devel, and
kernel-devel-<arch> so the namespaced CLK packages satisfy the same
dependency capabilities as stock Rocky kernel packages.

bundle_bindgen: add set -e, curl --fail, and SHA256 verification

- Add set -e so the script exits on any command failure
- Add -f (--fail) to curl so HTTP errors are caught
- Verify the downloaded crate against the known SHA256 from crates.io
  before extracting

[CIQ] v6.18.27 - rebased configs

ARM64_ERRATUM_4193714 was added and defaults to y if
you have ARM64 (which our aarch64 configs have)
 arm64: errata: Work around early CME DVMSync acknowledgement
 Upstream: 0baba94a9779c13c857f6efc55807e6a45b1d4e4

[CIQ] v6.18.27 - updated spec

generate_tarball: Also strip leading v from tags

[CIQ] v6.18.28 - updated spec

[CIQ] ciq_kernel-6.18.28-2 - updated spec

[CIQ] v6.18.31 - updated spec

[CIQ] v6.18.33 - updated spec

bundle_bindgen: add User-Agent header to crates.io request

crates.io returns 403 for API requests without a User-Agent header.

[CIQ] ciq_kernel-6.18.33-2 - updated spec

kernel-clk6.18: require ciq-kmod and ship %clk_version macro file

- Add Requires: ciq-kmod to the main meta package
- Install macros.kernel-clk6.18-<ver>-<rel> into %{buildroot}/usr/lib/rpm/macros.d/
  during BuildKernel() (base variant only); defines %clk_version for kmod builds
- Versioned filename avoids collisions when multiple installonly devel packages coexist
- Ship as a real file in kernel-clk6.18-devel (no ghost, no scriptlets)

random: Add hook to override device reads and getrandom(2)

commit-author Herbert Xu <herbert.xu@redhat.com>
commit 6892c65de813d311f20443401e528b4dc56872ff
commit-source https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10

crypto: rng - Override drivers/char/random in FIPS mode

commit-author Herbert Xu <herbert.xu@redhat.com>
commit 8b0beca705b3877e24cccdd672422c66bbd75635
commit-source https://gitlab.com/cki-project/kernel-ark

not upstream: Disable vdso getrandom when FIPS is enabled

commit-author Herbert Xu <herbert.xu@redhat.com>
commit 248b8056b11ed8e4b9004f401c75b7c72c3b27e4
commit-source https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10

crypto: ecdh - implement FIPS PCT

commit -
commit-source https://build.opensuse.org/public/source/SUSE:SLE-15-SP6:GA/kernel-source/patches.suse.tar.bz2
commit-patch-path patches.suse/crypto-ecdh-implement-FIPS-PCT.patch

crypto: essiv - Zeroize keys on exit in essiv_aead_setkey()

In essiv_aead_setkey(), use the same logic as crypto_authenc_esn_setkey()
to zeroize keys on exit.

crypto: drbg - Align buffers to at least a cache line

None of the ciphers used by the DRBG have an alignment requirement; thus,
they all return 0 from .crypto_init, resulting in inconsistent alignment
across all buffers.

mm/gup: introduce pin_user_pages_fast_only()

Like pin_user_pages_fast(), but with the internal-only FOLL_FAST_ONLY flag.

crypto: rng - Convert crypto_default_rng_refcnt into an unsigned int

There is no reason this refcount should be a signed int. Convert it to an
unsigned int, thereby also making it less likely to ever overflow.

crypto: rng - Fix priority inversions due to mutex locks

Since crypto_devrandom_read_iter() is invoked directly by user tasks and is
accessible by every task in the system, there are glaring priority
inversions on crypto_reseed_rng_lock and crypto_default_rng_lock.

crypto: rng - Implement fast per-CPU DRBG instances

When the kernel is booted with fips=1, the RNG exposed to userspace is
hijacked away from the CRNG and redirects to crypto_devrandom_read_iter(),
which utilizes the DRBG.

lib/crypto: Add FIPS self-tests for SHA-1 and SHA-2

commit-author Eric Biggers <ebiggers@kernel.org>
commit 04cadb4fe0341304741ef60a297366b553f0ce36

byteorder: Add le64_to_cpu_array() and cpu_to_le64_array()

commit-author Eric Biggers <ebiggers@kernel.org>
commit c99d30706043481a1d631bbd9c7a4b70fe002a2b

lib/crypto: blake2b: Add BLAKE2b library functions

commit-author Eric Biggers <ebiggers@kernel.org>
commit 23a16c9533ed92cc639c8f5bd9eb104809fe2919

btrfs: switch to library APIs for checksums

commit-author Eric Biggers <ebiggers@kernel.org>
commit fe11ac191ce0ad910f6fda0c628bcff19fcff47d
upstream-diff |
    NB. This was a back-port not a cherry-pick as some of
    the underlying code had been changed in prior upstream
    commits: cc38d178ff33543cdb0bd58cfbb9a7c41372ff75
	btrfs: enable large data folio support under CONFIG_BTRFS_EXPERIMENTAL
    and commit: 62bcbdca0ea9b1add9c22f400b51c56184902053
	btrfs: make btrfs_csum_one_bio() handle bs > ps without large folios
    and others unknown.
    These changes were judged too large to bring back
    from upstream as they are CONFIG_BTRFS_EXPERIMENTAL.

crypto: testmgr - block Crypto API xxhash64 in FIPS mode

commit-author Joachim Vandersmissen <git@jvdsn.com>
commit -
commit-source https://lore.kernel.org/linux-crypto/20260303060509.246038-1-git@jvdsn.com/

When in fips mode, self-test errors must panic.

Requested by the lab.

When in fips mode, self-test errors must panic.

Requested by the lab.

Change CONFIG_CRYPTO_JITTERENTROPY_OSR from 1 to 3 in all configs.

Retquested by the lab.

dh_compute_value misses the check SP800-56Arev3, 5.6.2.1.4 which is typically implemented after dh_is_pubkey_valid.

Requested by lab.

In crypto_kdf108_ctr_generate() there is no minimum length check for the digest to be generated - it must be at least 112 bits.

Requested by the lab.

Add fips_approved flag to SHA1 and HMAC-SHA1 structs.

Ensure this is initialized correctly based on system state
and key length.

Add fips_approved flag to SHA224 and HMAC-SHA224 structs.

Ensure this is initialized correctly based on system state
and key length.

Add fips_approved flag to SHA256 and HMAC-SHA256 structs.

Ensure this is initialized correctly based on system state
and key length.

Add fips_approved flag to SHA384 and HMAC-SHA384 structs.

Ensure this is initialized correctly based on system state
and key length.

Add fips_approved flag to SHA512 and HMAC-SHA512 structs.

Ensure this is initialized correctly based on system state
and key length.

Add fips_approved indicator to struct crypto_aes_ctx.

Requested by lab.

Add CONFIG_CRYPTO_FIPS_CUSTOM_VERSION=y, CONFIG_CRYPTO_FIPS_VERSION="ciq.6.18.20260531"

Requested by lab. Will be changed for rpm builds.

Unset CRYPTO_JITTERENTROPY_MEMSIZE_2, set CRYPTO_JITTERENTROPY_MEMSIZE_128.

Requested by lab.

github actions: Add FIPS protected directory check for PRs

Adds a workflow that runs on PRs targeting ciq-*-next branches and
checks whether new upstream commits touch FIPS protected directories.
Posts a PR comment alerting reviewers if changes are found.

Restore CRYPTO_TFM_FIPS_COMPLIANCE flag as an indicator to differentiate between internal and external IV generation when AES-GCM
encryption is performed.

Required by lab.

[CIQ] v6.18.35 - updated spec

[CIQ] ciq_kernel-6.18.35-2 - updated spec

github-actions: extend trigger glob to match suffix branches

Catches *_ciq-6.18.y-no-ltp, *_ciq-6.18.y-pr-only, and other branch-name
suffix variants used by the kernelCI skip-stages feature.

crypto: Kconfig - Make CRYPTO_FIPS depend on the DRBG being built-in

When FIPS mode is enabled (via fips=1), there is an absolute need for the
DRBG to be available. This is at odds with the fact that the DRBG can be
built as a module when in FIPS mode, leaving critical RNG functionality at
the whims of userspace.

random: Restrict extrng registration to init time

It is technically a risk to permit extrng registration by modules after
kernel init completes. Since there is only one user of the extrng interface
and it is imperative that it is the _only_ registered extrng for FIPS
compliance, restrict the extrng registration interface to only permit
registration during kernel init and only from built-in drivers.

crypto: rng - Only allow the DRBG to register as "stdrng" in FIPS mode

In FIPS mode, the DRBG must take precedence over all stdrng algorithms.
The only problem standing in the way of this is that a different stdrng
algorithm could get registered and utilized before the DRBG is registered,
and since crypto_alloc_rng() only allocates an stdrng algorithm when
there's no existing allocation, this means that it's possible for the wrong
stdrng algorithm to remain in use indefinitely.

crypto: rng - Fix tabs vs spaces in the per-CPU DRBG code

The 6.18.y version of "crypto: rng - Implement fast per-CPU DRBG instances"
picked up a few spots that use spaces where the ciqlts9_6 tree's version
[1] uses tabs: the lock_default_rng() comment's numbered list, the line
continuations in the unlock_local_rng() macro, and a brace in
crypto_devrandom_read_iter(). A nearby block comment was also missing the
space before its '*'. Fix them up.

crypto: rng - Make the per-CPU DRBG instances permanent

The per-CPU DRBG instances used to be torn down by crypto_del_default_rng()
under del_pcpu_rwsem, and the read path took that rwsem as a reader to keep
an instance from being freed out from under it. That machinery only made
sense back when the extrng override could be unregistered and the DRBG
could be built as a module.

crypto: rng - Skip leading zero-length iovec segments

The fast per-CPU DRBG path computes its initial user destination address
straight from the iov_iter. For an ITER_IOVEC iter it reads iter_iov_addr()
and iter_iov_len() of the current segment, but when the iovec leads with
one or more zero-length segments, the current segment is one of those empty
entries. iter_iov_addr() then hands back the base of an empty segment,
which is whatever userspace put there: its base can be NULL or some other
unwritable address, since a zero-length segment is never actually touched.

crypto: rng - Fix spurious EFAULT when the destination PTE is zapped

While GUP pinning makes it possible to pin the page _backing_ a user
address, it *doesn't* pin the page table entry (PTE) for that mapping. This
means the pinned physical page can be separated from the user address it
was backing, and even back a _different_ user address within the same
process. PTE zapping naturally happens during memory reclaim when memory
pressure is elevated, and can even be done directly by userspace via
madvise(MADV_DONTNEED).

Revert "mm/gup: reintroduce pin_user_pages_fast_only()"

This reverts commit ef467f3c43338f72f4173c98b15bc8021f79c3a1.

[CIQ] ciq_kernel-6.18.35-3 - updated spec

[CIQ] v6.18.36 - rebased configs

[CIQ] v6.18.36 - updated spec

[CIQ] v6.18.38 - updated spec

Add x86_64 minimal kernel variant to spec

Add a new "minimal" x86_64 kernel variant built with a stripped-down
config targeting server/cloud/VM workloads. Enabled by default on
x86_64, disableable with --without x86_64_minimal. A --with minimalonly
convenience option is also provided.

[CIQ] ciq_kernel-6.18.38-2 - updated spec

[CIQ] v6.18.39 - updated spec

[CIQ] v6.18.40 - rebased configs

[CIQ] v6.18.40 - updated spec

spec: relax UKI systemd requirement to 252-31 on RHEL

The UKI packages unconditionally required systemd >= 254-1, making them
uninstallable on Rocky 9 which ships systemd 252. The required
kernel-install UKI support (90-uki-copy.install, --entry-type) was
backported to RHEL/Rocky 9's systemd 252-31.

[CIQ] v6.18.41 - updated spec

[CIQ] v6.18.42 - updated spec

Set kpatch/driver certs for all builds

- Kpatch and driver (DUP) certs should be embedded in all builds -
  official and local (unsigned)
- No version increment here - this change doesn't affect any releases,
  only local builds

[CIQ] v6.18.43 - updated spec

spec: use %{rhel} for el version and conditionally use system bindgen

Replace the hardcoded el_version with %{rhel} directly, which is set
automatically by the buildroot.  This allows the same branch to produce
el9 packages in a Rocky 9 mock and el10 packages in a Rocky 10 mock.

crypto: rng - Fix double percpu offset in local_unlock() calls

local_unlock() is supposed to take a percpu pointer, which it then offsets
for the current CPU. The problem is that the per-CPU DRBG code passes
local_unlock() a pointer that has *already been offset for the current
CPU*, so the percpu offset gets added twice. `pcri` is the percpu pointer
and `cri` is the offset `pcri` pointer for the current CPU; passing `cri`
to local_unlock() results in the current CPU's offset getting added again
and thus the resulting pointer is garbage.

bpf: Support BPF_F_EGRESS with bpf_redirect_peer

commit-author Jordan Rife <jordan@jrife.io>
commit 509ca545d425512f83ca70093f6d836ec8ab5bd1

selftests/bpf: Add tests for bpf_redirect_peer with BPF_F_EGRESS

commit-author Jordan Rife <jordan@jrife.io>
commit 006b9456e9f4e8a5cada19409d26bec8193acc13

net: Clear the dst when performing encap / decap

commit-author Jakub Kicinski <kuba@kernel.org>
commit 699f47e616fed11d5074e7bbee2f4f920028c4a2

bpf: Name the enum for BPF_FUNC_skb_adjust_room flags

commit-author Nick Hudson <nhudson@akamai.com>
commit 5e4bcad6171d4baf426e49a39580cdb79254ea36

bpf: Refactor masks for ADJ_ROOM flags and encap validation

commit-author Nick Hudson <nhudson@akamai.com>
commit 7b2ea1151e04d3506030db8734c48c5c2bec1392
Refactor the helper masks for bpf_skb_adjust_room() flags to simplify
validation logic and introduce:

bpf: Add BPF_F_ADJ_ROOM_DECAP_* flags for tunnel decapsulation

commit-author Nick Hudson <nhudson@akamai.com>
commit da199070bc6209bf5db970f8f84c7db4210fe511

bpf: Allow new DECAP flags and add guard rails

commit-author Nick Hudson <nhudson@akamai.com>
commit 3a39c214fd2c3dd8266649e7f9f85ca1439eb738

bpf: Clear decap state on skb_adjust_room shrink path

commit-author Nick Hudson <nhudson@akamai.com>
commit ec20dee2f2c4796c0f7c0a7d8a3a3e8a9e9da7a4

selftests/bpf: tc_tunnel - validate decap GSO and encapsulation state

commit-author Nick Hudson <nhudson@akamai.com>
commit adb771973026efe54627bcbe927e7205d04d6c68
upstream-diff |
  The upstream patch targets bpf-next where the BPF program has been
  converted to use vmlinux.h (commit 86433db93256) and the test runner
  has been migrated from a shell script to a C-based test_progs harness
  (commit 8517b1abe5ea). This tree has neither of those prerequisites,
  so the following upstream changes were dropped:
  - Post-decap GSO gso_type and skb->encapsulation validation
    via bpf_cast_to_kern_ctx/bpf_core_cast into skb_shared_info.
    These require vmlinux.h to access kernel-internal structs
    (sk_buff, skb_shared_info) and SKB_GSO_* constants.
  - TSO disable removal from prog_tests/test_tc_tunnel.c (file absent;
    this tree still uses test_tc_tunnel.sh).
  The CO-RE enum existence checks, functional flag-passing changes
  (DECAP_L4_GRE, DECAP_L4_UDP, DECAP_IPXIP4, DECAP_IPXIP6), and
  ipxip_flag parameter plumbing through decap_internal/decap_ipv4/
  decap_ipv6 are applied as in upstream. The test exercises the new
  kernel flag acceptance path and will fail to load on kernels lacking
  the new enum values, but does not validate post-decap skb state.

[CIQ] ciq_kernel-6.18.43-2 - updated spec

[CIQ] v6.18.48 - rebased configs

CXL_RAS was added as a def_bool y depending on ACPI_APEI_GHES,
PCIEAER, and CXL_PCI.
 cxl/pci: Remove CXL VH handling in CONFIG_PCIEAER_CXL conditional blocks from core/pci.c
 Upstream: 7ff8b1d60881c5f97b5ae426e14d2822917d3b69

[CIQ] v6.18.48 - updated spec

[CIQ] v6.18.49 - updated spec

[CIQ] v6.18.50 - updated spec

[CIQ] v6.18.52 - updated spec

[CIQ] v6.18.53 - rebased configs

CONFIG_HAVE_ARCH_GET_SECUREBOOT was added to indicate archs
that supply arch_get_secureboot().  All of our supported archs
do, so all of the configs are =y

[CIQ] v6.18.53 - updated spec

Test Results

✅ Build Stage

Architecture	Build Time	Total Time
x86_64	30m 45s	31m 23s
aarch64	24m 53s	25m 30s

• View build logs

✅ Boot Verification

• Status: Passed (all architectures)
• View boot logs

✅ Kernel Selftests

Architecture	Passed	Failed	Compared Against	Status
x86_64	444	58	ciq-6.18.y-next	⚠️ No baseline available
aarch64	371	55	ciq-6.18.y-next	⚠️ No baseline available

• View kselftest logs

✅ LTP Results

Architecture	Passed	Failed	Compared Against	Status
x86_64	1479	81	ciq-6.18.y-next	⚠️ No baseline available
aarch64	1452	82	ciq-6.18.y-next	⚠️ No baseline available

• View LTP logs

---

🤖 This PR was automatically generated by GitHub Actions
Run ID: 35762326924

[ciq-kernel-automation]

⚠️ FIPS Protected Directory Changes Detected

New upstream commits in this rebase touch FIPS protected directories.
Please consult the CIQ FIPS / Security team before merging.

Details

[fips-check] Checking for FIPS protected changes in 8f3741e6feb045da5b406df0a80b42a1adfb289b..origin/ciq-6.18.y-next
[fips-check] Protected directories: arch/x86/crypto/, crypto/asymmetric_keys/, crypto/, drivers/crypto/, drivers/char/random.c, include/crypto
[fips-check] Checking for FIPS protected changes
[fips-check] Getting SHAS 8f3741e6feb045da5b406df0a80b42a1adfb289b..origin/ciq-6.18.y-next
[fips-check] Number of commits to check:  1253
[fips-check] Checking modifications of shas
[fips-check] Checked 125 of 1253 commits
[fips-check] Checked commit b'ffd3a3df92be697eb78118a146c6a5d5e6c1f724' touched 1 FIPS protected files
  - b'drivers/crypto/'
[fips-check] Checked 250 of 1253 commits
[fips-check] Checked commit b'5206e1b65a49b6265bc76cafe613db7ecabc62ba' touched 1 FIPS protected files
  - b'arch/x86/crypto/'
[fips-check] Checked commit b'8764a17eab6b2c9e483fc5ba8f68776d78baf6e7' touched 1 FIPS protected files
  - b'arch/x86/crypto/'
[fips-check] Checked 375 of 1253 commits
[fips-check] Checked 500 of 1253 commits
[fips-check] Checked 625 of 1253 commits
[fips-check] Checked 750 of 1253 commits
[fips-check] Checked 875 of 1253 commits
[fips-check] Checked 1000 of 1253 commits
[fips-check] Checked commit b'182bec9f9e37a80ec33d63f1ea4075df6b8ae00b' touched 1 FIPS protected files
  - b'drivers/crypto/'
[fips-check] Checked 1125 of 1253 commits
[fips-check] Checked commit b'99e7269a9152668f5d1b0fca2406a1ea16180d14' touched 1 FIPS protected files
  - b'drivers/crypto/'
[fips-check] Checked commit b'7fb387afd60c5d7c7a7cad03dd1e80d9d9ef2cf4' touched 1 FIPS protected files
  - b'crypto/'
[fips-check] Checked commit b'1931e06034c7dae0cb05bb90e7156f5aa4521bc7' touched 1 FIPS protected files
  - b'drivers/crypto/'
[fips-check] Checked commit b'028a7f4f3d69e551f6bf9f728d547bbf4cfc707d' touched 1 FIPS protected files
  - b'drivers/crypto/'
[fips-check] Checked 1250 of 1253 commits
[fips-check] 8 of 1253 commits have FIPS protected changes

[fips-check] ========================================
[fips-check] FIPS protected changes detected
[fips-check] ========================================
[fips-check] 8 commit(s) touch FIPS protected directories:

## Commit ffd3a3df92be697eb78118a146c6a5d5e6c1f724
commit ffd3a3df92be697eb78118a146c6a5d5e6c1f724
Author: Atish Patra <atishp@meta.com>
Date:   Tue Jun 2 15:36:34 2026 -0700

    crypto: ccp - Fix possible deadlock in SEV init failure path
    
    [ Upstream commit b0e7ec0dab242c5e480121ba12400d0513e37ca2 ]
    
    __sev_platform_init_handle_init_ex_path() calls
    rmp_mark_pages_firmware() with locked=false while the parent
    function of init_ex_path already acquired the sev_cmd_mutex.
    In the case of an RMPUPDATE failure for any page after the first, the cleanup
    path would invoke reclaim pages which would result in a deadlock in
    sev_do_cmd.
    
    Pass locked=true to honor the lock status of the parent function.
    
    Fixes: 7364a6fbca45 ("crypto: ccp: Handle non-volatile INIT_EX data when SNP is enabled")
    
    Reported-by: Chris Mason <clm@meta.com>
    Assisted-by: Claude:claude-opus-4-6
    Fixes: 7364a6fbca45 ("crypto: ccp: Handle non-volatile INIT_EX data when SNP is enabled")
    Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com>
    Signed-off-by: Atish Patra <atishp@meta.com>
    Acked-by: Herbert Xu <herbert@gondor.apana.org.au>
    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 drivers/crypto/ccp/sev-dev.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

  FIPS directory: drivers/crypto/

## Commit 5206e1b65a49b6265bc76cafe613db7ecabc62ba
commit 5206e1b65a49b6265bc76cafe613db7ecabc62ba
Author: Eric Biggers <ebiggers@kernel.org>
Date:   Mon Aug 31 14:18:12 2026 -0700

    crypto: x86/aria - add missing vzeroupper in AVX-512 code
    
    commit 60892a384aa1e65d0e703e1c513417bdf0c80777 upstream.
    
    Since the AVX-512 optimized ARIA code uses ZMM registers, execute
    vzeroupper before returning from it.  This is needed to avoid degrading
    the performance of any later SSE code that may happen to be executed.
    
    Fixes: c970d42001f2 ("crypto: x86/aria - implement aria-avx512")
    Cc: stable@vger.kernel.org
    Cc: Taehee Yoo <ap420073@gmail.com>
    Signed-off-by: Eric Biggers <ebiggers@kernel.org>
    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 arch/x86/crypto/aria-gfni-avx512-asm_64.S | 3 +++
 1 file changed, 3 insertions(+)

  FIPS directory: arch/x86/crypto/

## Commit 8764a17eab6b2c9e483fc5ba8f68776d78baf6e7
commit 8764a17eab6b2c9e483fc5ba8f68776d78baf6e7
Author: Eric Biggers <ebiggers@kernel.org>
Date:   Mon Aug 31 14:17:15 2026 -0700

    crypto: x86/aria - add missing vzeroupper in AVX2 code
    
    commit ac53977611428db3bc0b4ac0225e19c3e08ae50b upstream.
    
    Since the AVX2 optimized ARIA code uses YMM registers, execute
    vzeroupper before returning from it.  This is needed to avoid degrading
    the performance of any later SSE code that may happen to be executed.
    
    Fixes: 37d8d3ae7a58 ("crypto: x86/aria - implement aria-avx2")
    Cc: stable@vger.kernel.org
    Cc: Taehee Yoo <ap420073@gmail.com>
    Signed-off-by: Eric Biggers <ebiggers@kernel.org>
    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 arch/x86/crypto/aria-aesni-avx2-asm_64.S | 6 ++++++
 1 file changed, 6 insertions(+)

  FIPS directory: arch/x86/crypto/

## Commit 182bec9f9e37a80ec33d63f1ea4075df6b8ae00b
commit 182bec9f9e37a80ec33d63f1ea4075df6b8ae00b
Author: Thorsten Blum <thorsten.blum@linux.dev>
Date:   Sun May 17 14:37:07 2026 +0200

    crypto: atmel-sha204a - remove sysfs group before hwrng
    
    [ Upstream commit d58b4a09d7f06750a706b70d068f5a678dad8233 ]
    
    atmel_sha204a_probe() registers the hwrng before creating the sysfs
    group. Mirror this order in atmel_sha204a_remove() by removing the sysfs
    group before unregistering the hwrng.
    
    Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 drivers/crypto/atmel-sha204a.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

  FIPS directory: drivers/crypto/

## Commit 99e7269a9152668f5d1b0fca2406a1ea16180d14
commit 99e7269a9152668f5d1b0fca2406a1ea16180d14
Author: Thorsten Blum <thorsten.blum@linux.dev>
Date:   Sun Apr 12 11:56:43 2026 +0200

    crypto: atmel-ecc - add support for atecc608b
    
    [ Upstream commit b668edaf8dcc8d09f6f1e71797422b44d4bd22a3 ]
    
    Tested on hardware with an ATECC608B at 0x60. The device binds
    successfully, passes the driver's sanity check, and registers the
    ecdh-nist-p256 KPP algorithm.
    
    The hardware ECDH path was also exercised using a minimal KPP test
    module, covering private key generation, public key derivation, and
    shared secret computation.
    
    Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 drivers/crypto/atmel-ecc.c | 3 +++
 1 file changed, 3 insertions(+)

  FIPS directory: drivers/crypto/

## Commit 7fb387afd60c5d7c7a7cad03dd1e80d9d9ef2cf4
commit 7fb387afd60c5d7c7a7cad03dd1e80d9d9ef2cf4
Author: Lukas Wunner <lukas@wunner.de>
Date:   Wed May 6 15:27:49 2026 +0200

    crypto: ecc - Unbreak the build on arm with CONFIG_KASAN_STACK=y
    
    [ Upstream commit c64ba13e2033c3c6dc1a097bf35f9f1fe457c3f7 ]
    
    Andrew reports build breakage of arm allmodconfig, reproducible with gcc
    14.2.0 and 15.2.0:
    
      crypto/ecc.c: In function 'ecc_point_mult':
      crypto/ecc.c:1380:1: error: the frame size of 1360 bytes is larger than 1280 bytes [-Werror=frame-larger-than=]
    
    gcc aggressively inlines functions called by ecc_point_mult() (without
    there being any explicit inline declarations), which pushes stack usage
    close to the limit imposed by CONFIG_FRAME_WARN.  allmodconfig implies
    CONFIG_KASAN_STACK=y, which increases the stack above that limit.
    
    In the bugzilla entry linked below, gcc maintainers explain that gcc
    estimates extra stack usage caused by inlining, but ASAN instrumentation
    is added in post-IPA passes and thus the inlining heuristics cannot
    account for it.
    
    It could be argued that -Werror=frame-larger-than=1280 instructs the
    compiler to avoid inlining beyond that limit lest the build breaks,
    which would imply gcc behaves incorrectly.  But gcc maintainers reject
    this notion and believe that a warning switch should never affect code
    generation, even if it is promoted to an error.
    
    One way to unbreak the build is to limit inlining via -finline-limit=100
    or by explicitly declaring some functions noinline.  However while it
    does keep stack usage of individual functions below the limit, *total*
    stack usage increases.
    
    A longterm solution is to refactor ecc.c for reduced stack usage.  It
    currently performs ECC point multiplication with a Montgomery ladder
    which uses co-Z (conjugate) addition to trade off memory for speed.
    The algorithm is susceptible to timing attacks and needs to be replaced
    with a constant time Montgomery ladder, which should consume less memory
    and thus resolve the stack usage issue as a side effect.
    
    In the interim, raise the limit for ecc.c, as is already done for
    several other files in the source tree.
    
    Constrain to gcc because clang 19.1.7 does not exhibit the issue.  It
    makes do with a 724 bytes stack frame even though it inlines almost the
    same functions as gcc.
    
    Link: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=124949
    Reported-by: Andrew Morton <akpm@linux-foundation.org> # off-list
    Signed-off-by: Lukas Wunner <lukas@wunner.de>
    Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 crypto/Makefile | 5 +++++
 1 file changed, 5 insertions(+)

  FIPS directory: crypto/

## Commit 1931e06034c7dae0cb05bb90e7156f5aa4521bc7
commit 1931e06034c7dae0cb05bb90e7156f5aa4521bc7
Author: Thorsten Blum <thorsten.blum@linux.dev>
Date:   Mon Apr 27 19:20:19 2026 +0200

    crypto: omap - add omap_des_unregister_algs helper
    
    [ Upstream commit 9ab1392b1163daab674484d6ddacf16f0ad4c040 ]
    
    Add a new helper omap_des_unregister_algs() and replace two for loops in
    omap_des_probe() and omap_des_remove(), which also ensure ->registered
    is reset to 0.
    
    Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 drivers/crypto/omap-des.c | 26 ++++++++++++++++----------
 1 file changed, 16 insertions(+), 10 deletions(-)

  FIPS directory: drivers/crypto/

## Commit 028a7f4f3d69e551f6bf9f728d547bbf4cfc707d
commit 028a7f4f3d69e551f6bf9f728d547bbf4cfc707d
Author: Ruoyu Wang <ruoyuw560@gmail.com>
Date:   Thu Apr 23 19:19:56 2026 +0800

    crypto: ixp4xx - fix buffer chain unwind on allocation failure
    
    [ Upstream commit 25056329384010a8672552b134f609601dc4f80e ]
    
    chainup_buffers() builds a linked list of buffer descriptors for a
    scatterlist. If dma_pool_alloc() fails while constructing the list, the
    current code sets buf to NULL and later dereferences it unconditionally
    at the end of the function:
    
      buf->next = NULL;
      buf->phys_next = 0;
    
    This can lead to a null-pointer dereference on allocation failure.
    
    If the failure happens after part of the descriptor chain has already
    been allocated and DMA-mapped, the partially constructed chain also
    needs to be released.
    
    Fix this by terminating the partially constructed chain on allocation
    failure and letting the callers unwind it via their existing cleanup
    paths. Also fix ablk_perform() to preserve the hook pointers before
    checking for failure, so partially built chains can be freed correctly.
    
    Signed-off-by: Ruoyu Wang <ruoyuw560@gmail.com>
    Acked-by: Linus Walleij <linusw@kernel.org>
    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 drivers/crypto/intel/ixp4xx/ixp4xx_crypto.c | 25 ++++++++++++++-----------
 1 file changed, 14 insertions(+), 11 deletions(-)

  FIPS directory: drivers/crypto/

[fips-check] --fips-override set, continuing despite FIPS protected changes