[ciq-kernel-automation]

Summary

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

Commit Message(s)

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

[CIQ] v6.18.54 - updated spec

[CIQ] v6.18.55 - updated spec

kernel-clk6.18: only require ciq-kmod on el9

ciq-kmod is a synthetic provide added by the patched el9 kmod (weak-modules
fix for xz-compressed symvers). EL10's stock kmod already handles xz and zstd
symvers and nothing there provides ciq-kmod, so the unconditional Requires
makes kernel-clk6.18 uninstallable on EL10. Guard it to rhel == 9 so other
EL versions do not depend on the el9-only patched kmod.

configs: Enable LIVEPATCH

[CIQ] v6.18.56 - updated spec

[CIQ] v6.18.57 - updated spec

[CIQ] v6.18.58 - updated spec

[CIQ] v6.18.59 - updated spec

configs: minimal: Sync with full x86 config

configs: minimal: Disable X86_KERNEL_IBT

[CIQ] ciq_kernel-6.18.59-2 - updated spec

[CIQ] v6.18.60 - updated spec

[CIQ] v6.18.62 - updated spec

Test Results

✅ Build Stage

Architecture	Build Time	Total Time
x86_64	34m 14s	34m 54s
aarch64	26m 32s	27m 15s

• View build logs

✅ Boot Verification

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

✅ Kernel Selftests

Architecture	Passed	Failed	Compared Against	Status
x86_64	443	61	ciq-6.18.y-next	⚠️ No baseline available
aarch64	372	56	ciq-6.18.y-next	⚠️ No baseline available

• View kselftest logs

✅ LTP Results

Architecture	Passed	Failed	Compared Against	Status
x86_64	1540	5	ciq-6.18.y-next	⚠️ No baseline available
aarch64	1513	6	ciq-6.18.y-next	⚠️ No baseline available

• View LTP logs

---

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

[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 f45ed76d6791cf72ff1265ee93511175bbbc2f18..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 f45ed76d6791cf72ff1265ee93511175bbbc2f18..origin/ciq-6.18.y-next
[fips-check] Number of commits to check:  1006
[fips-check] Checking modifications of shas
[fips-check] Checked 100 of 1006 commits
[fips-check] Checked commit b'9d275d40b6ece705ba1f10410883b6c374b9e24b' touched 1 FIPS protected files
  - b'crypto/'
[fips-check] Checked 200 of 1006 commits
[fips-check] Checked 300 of 1006 commits
[fips-check] Checked 400 of 1006 commits
[fips-check] Checked 500 of 1006 commits
[fips-check] Checked 600 of 1006 commits
[fips-check] Checked commit b'220e3f51071bdeef20bb23ec508b0c14a3d1d1a8' touched 1 FIPS protected files
  - b'drivers/crypto/'
[fips-check] Checked commit b'80cb14cc834a2a30cd1a043f737449c410ebcc28' touched 1 FIPS protected files
  - b'drivers/crypto/'
[fips-check] Checked commit b'9bfa6187948e267cbf406256ae944d4195daf99a' touched 1 FIPS protected files
  - b'drivers/crypto/'
[fips-check] Checked 700 of 1006 commits
[fips-check] Checked 800 of 1006 commits
[fips-check] Checked commit b'7823cf4f9bc93619a207498a791009068aea2639' touched 1 FIPS protected files
  - b'drivers/crypto/'
[fips-check] Checked 900 of 1006 commits
[fips-check] Checked 1000 of 1006 commits
[fips-check] 5 of 1006 commits have FIPS protected changes

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

## Commit 9d275d40b6ece705ba1f10410883b6c374b9e24b
commit 9d275d40b6ece705ba1f10410883b6c374b9e24b
Author: Hazem Mohamed Abuelfotoh <abuehaze@amazon.com>
Date:   Tue Nov 3 17:45:41 2026 +0000

    Revert "net: Convert proto_ops bind() callbacks to use sockaddr_unsized"
    
    Revert commit 946dc5835c8fbe5eb5ceb13f5717778911ff4586 which is commit
    0e50474fa514822e9d990874e554bf8043a201d7 upstream.
    
    Commit 946dc5835c8f ("net: Convert proto_ops bind() callbacks to use
    sockaddr_unsized") is a backport of upstream commit 0e50474fa514. It was
    queued for v6.18.57 only as a Stable-dep-of commit 56e78b670356
    ("Bluetooth: hci_sync: hold conn in hci_connect_big_sync() callback"),
    but it is not a dependency of that fix:
    
     - Commit 56e78b670356 ("Bluetooth: hci_sync: hold conn in
       hci_connect_big_sync() callback") touches only
       net/bluetooth/hci_sync.c. Commit 0e50474fa514 ("net: Convert
       proto_ops bind() callbacks to use sockaddr_unsized") changes 74
       files and none of them is net/bluetooth/hci_sync.c.
    
     - The same fix went into 6.12.y as commit 117d8bcaf1ab ("Bluetooth:
       hci_sync: hold conn in hci_connect_big_sync() callback") without
       commit 0e50474fa514 ("net: Convert proto_ops bind() callbacks to use
       sockaddr_unsized"). Its +/- lines are identical to the 6.18.y
       version, commit ff5625d27415 ("Bluetooth: hci_sync: hold conn in
       hci_connect_big_sync() callback").
    
     - Commit ff5625d27415 ("Bluetooth: hci_sync: hold conn in
       hci_connect_big_sync() callback") cherry-picks cleanly onto the
       parent of commit 946dc5835c8f ("net: Convert proto_ops bind()
       callbacks to use sockaddr_unsized"), and the resulting
       net/bluetooth/hci_sync.c matches the one in v6.18.57.
    
    Upstream commit 0e50474fa514 ("net: Convert proto_ops bind() callbacks
    to use sockaddr_unsized") carries no Fixes: or Cc: stable tag. It is an
    API conversion ("No binary changes expected"), not a fix. It also
    needed non-trivial adaptation for 6.18.y. Commit bf33247a90d3 ("net:
    Add struct sockaddr_unsized for sockaddr of unknown length") is not in
    6.18.y, so the backport adds its own definition of struct
    sockaddr_unsized to include/linux/socket.h.
    
    The result is a half-converted in-kernel socket API, which no mainline
    release ever had:
    
                   kernel_bind()               kernel_connect()
      v6.18.56     struct sockaddr *           struct sockaddr *
      v6.18.57+    struct sockaddr_unsized *   struct sockaddr *
      v6.19        struct sockaddr_unsized *   struct sockaddr_unsized *
    
    Code that probes for struct sockaddr_unsized via kernel_bind() and then
    assumes the mainline (v6.19+) kernel_connect() signature breaks on
    6.18.57+ with -Werror=incompatible-pointer-types.
    
    Nothing in 6.18.y after v6.18.57 depends on this commit. With it
    reverted on top of v6.18.59, the tree contains no references to
    struct sockaddr_unsized.
    
    Signed-off-by: Hazem Mohamed Abuelfotoh <abuehaze@amazon.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 crypto/af_alg.c                                      |  2 +-
 drivers/block/drbd/drbd_receiver.c                   |  4 ++--
 drivers/infiniband/hw/erdma/erdma_cm.c               |  4 ++--
 drivers/infiniband/sw/siw/siw_cm.c                   |  6 +++---
 drivers/isdn/mISDN/l1oip_core.c                      |  2 +-
 drivers/isdn/mISDN/socket.c                          |  4 ++--
 drivers/net/ppp/pptp.c                               |  4 ++--
 drivers/nvme/host/tcp.c                              |  2 +-
 drivers/nvme/target/tcp.c                            |  2 +-
 drivers/target/iscsi/iscsi_target_login.c            |  2 +-
 drivers/xen/pvcalls-back.c                           |  2 +-
 fs/afs/rxrpc.c                                       |  6 +++---
 fs/dlm/lowcomms.c                                    |  6 +++---
 fs/ocfs2/cluster/tcp.c                               |  4 ++--
 fs/smb/client/connect.c                              |  2 +-
 fs/smb/server/transport_tcp.c                        |  4 ++--
 include/linux/net.h                                  |  4 ++--
 include/linux/socket.h                               | 17 -----------------
 include/net/inet_common.h                            |  2 +-
 include/net/ipv6.h                                   |  2 +-
 include/net/sock.h                                   |  2 +-
 net/9p/trans_fd.c                                    |  2 +-
 net/appletalk/ddp.c                                  |  2 +-
 net/atm/pvc.c                                        |  4 ++--
 net/atm/svc.c                                        |  2 +-
 net/ax25/af_ax25.c                                   |  2 +-
 net/bluetooth/hci_sock.c                             |  2 +-
 net/bluetooth/iso.c                                  |  4 ++--
 net/bluetooth/l2cap_sock.c                           |  2 +-
 net/bluetooth/rfcomm/core.c                          |  4 ++--
 net/bluetooth/rfcomm/sock.c                          |  2 +-
 net/bluetooth/sco.c                                  |  2 +-
 net/can/isotp.c                                      |  2 +-
 net/can/j1939/socket.c                               |  2 +-
 net/can/raw.c                                        |  2 +-
 net/core/sock.c                                      |  2 +-
 net/ieee802154/socket.c                              |  4 ++--
 net/ipv4/af_inet.c                                   |  4 ++--
 net/ipv4/udp_tunnel_core.c                           |  2 +-
 net/ipv6/af_inet6.c                                  |  4 ++--
 net/ipv6/ip6_udp_tunnel.c                            |  2 +-
 net/iucv/af_iucv.c                                   |  2 +-
 net/l2tp/l2tp_core.c                                 |  4 ++--
 net/llc/af_llc.c                                     |  2 +-
 net/mctp/af_mctp.c                                   |  2 +-
 net/mctp/test/route-test.c                           |  2 +-
 net/mctp/test/utils.c                                |  2 +-
 net/mptcp/protocol.c                                 |  6 +++---
 net/mptcp/subflow.c                                  |  2 +-
 net/netfilter/ipvs/ip_vs_sync.c                      |  4 ++--
 net/netlink/af_netlink.c                             |  2 +-
 net/netrom/af_netrom.c                               |  2 +-
 net/nfc/llcp_sock.c                                  |  4 ++--
 net/packet/af_packet.c                               | 11 +++++------
 net/phonet/socket.c                                  |  8 ++++----
 net/qrtr/af_qrtr.c                                   |  2 +-
 net/qrtr/ns.c                                        |  2 +-
 net/rds/bind.c                                       |  2 +-
 net/rds/rds.h                                        |  2 +-
 net/rds/tcp_connect.c                                |  2 +-
 net/rds/tcp_listen.c                                 |  2 +-
 net/rose/af_rose.c                                   |  2 +-
 net/rxrpc/af_rxrpc.c                                 |  2 +-
 net/rxrpc/rxperf.c                                   |  2 +-
 net/smc/af_smc.c                                     |  2 +-
 net/smc/smc.h                                        |  2 +-
 net/socket.c                                         |  6 +++---
 net/sunrpc/clnt.c                                    |  4 ++--
 net/sunrpc/svcsock.c                                 |  2 +-
 net/sunrpc/xprtsock.c                                |  4 ++--
 net/tipc/socket.c                                    |  4 ++--
 net/unix/af_unix.c                                   |  4 ++--
 net/vmw_vsock/af_vsock.c                             |  4 ++--
 net/x25/af_x25.c                                     |  2 +-
 net/xdp/xsk.c                                        |  2 +-
 tools/testing/selftests/bpf/test_kmods/bpf_testmod.c |  2 +-
 76 files changed, 113 insertions(+), 131 deletions(-)

  FIPS directory: crypto/

## Commit 220e3f51071bdeef20bb23ec508b0c14a3d1d1a8
commit 220e3f51071bdeef20bb23ec508b0c14a3d1d1a8
Author: David C.C.M. Gall <david.ccm.gall@googlemail.com>
Date:   Fri Aug 7 18:22:00 2026 +0200

    crypto: keembay - use crypto_memneq() to compare CCM AEAD tags
    
    [ Upstream commit ff2ac77a034e03b64e2ba34f775097427dfa5547 ]
    
    Use crypto_memneq() for constant-time comparison.
    
    The CCM path in ocs-aes.c verifes the received authentication tag with
    memcmp(), which returns early on the first mismatched byte. This leaks
    valid-prefix length and allows for valid tag forgery which violates the
    INT-CTXT guarantee of AEAD.
    
    Assisted-by: gregkh_clanker_t1000
    Signed-off-by: David C.C.M. Gall <david.ccm.gall@googlemail.com>
    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 drivers/crypto/intel/keembay/ocs-aes.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

  FIPS directory: drivers/crypto/

## Commit 80cb14cc834a2a30cd1a043f737449c410ebcc28
commit 80cb14cc834a2a30cd1a043f737449c410ebcc28
Author: David C.C.M. Gall <david.ccm.gall@googlemail.com>
Date:   Fri Aug 7 17:44:16 2026 +0200

    crypto: sa2ul - use crypto_memneq() to compare AEAD tag
    
    [ Upstream commit 7064af16d2b418d61571dba9bb0116a547ade124 ]
    
    Use crypto_memneq() for a constant-time comparison.
    
    sa_aead_dma_in_callback() compares the computed authentication tag
    against the received tag with memcmp(), which short-circuits on the
    first differing byte. An attacker who can submit decrypt requests and
    observe completion latency could recover the expected tag byte by byte.
    
    Valid tag forgery for AEAD breaks the INT-CTXT guarantee.
    
    Assisted-by: gregkh_clanker_t1000
    Signed-off-by: David C.C.M. Gall <david.ccm.gall@googlemail.com>
    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 drivers/crypto/sa2ul.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

  FIPS directory: drivers/crypto/

## Commit 9bfa6187948e267cbf406256ae944d4195daf99a
commit 9bfa6187948e267cbf406256ae944d4195daf99a
Author: David C.C.M. Gall <david.ccm.gall@googlemail.com>
Date:   Fri Aug 7 18:13:52 2026 +0200

    crypto: keembay - use crypto_memneq() to compare GCM AEAD tags
    
    [ Upstream commit 353b3a85136f2a0cf3e872acf8ad6c1dec0b7a8e ]
    
    Use crypto_memneq() for constant-time comparison.
    
    The GCM path in keembay-ocs-aes-core.c verifes the received
    authentication tag with memcmp(), which returns early on the first
    mismatched byte. This leaks valid-prefix length and allows for valid
    tag forgery which violates the INT-CTXT guarantee of AEAD.
    
    Assisted-by: gregkh_clanker_t1000
    Signed-off-by: David C.C.M. Gall <david.ccm.gall@googlemail.com>
    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 drivers/crypto/intel/keembay/keembay-ocs-aes-core.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

  FIPS directory: drivers/crypto/

## Commit 7823cf4f9bc93619a207498a791009068aea2639
commit 7823cf4f9bc93619a207498a791009068aea2639
Author: Pengpeng Hou <pengpeng@iscas.ac.cn>
Date:   Sat Jul 4 20:46:09 2026 +0800

    crypto: keembay - add missing MODULE_DEVICE_TABLE()
    
    [ Upstream commit b73b71df4cb4ca241165ad31218c82dfe489147c ]
    
    The driver has an OF match table wired to .of_match_table, but does
    not export the table with MODULE_DEVICE_TABLE().
    
    Add the missing MODULE_DEVICE_TABLE(of, ...) entry so module alias
    information is generated for OF based module autoloading.
    
    This is a source-level fix.  It does not claim dynamic hardware
    reproduction; the evidence is the driver-owned match table, its use by
    the platform driver, and the missing module alias publication.
    
    Signed-off-by: Pengpeng Hou <pengpeng@iscas.ac.cn>
    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 drivers/crypto/intel/keembay/keembay-ocs-ecc.c | 1 +
 1 file changed, 1 insertion(+)

  FIPS directory: drivers/crypto/

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