Skip to content

[ciqlts9_2] Multiple patches tested (8 commits)#1348

Open
ciq-kernel-automation[bot] wants to merge 8 commits into
ciqlts9_2from
{ciq_kernel_automation}_ciqlts9_2
Open

[ciqlts9_2] Multiple patches tested (8 commits)#1348
ciq-kernel-automation[bot] wants to merge 8 commits into
ciqlts9_2from
{ciq_kernel_automation}_ciqlts9_2

Conversation

@ciq-kernel-automation

@ciq-kernel-automation ciq-kernel-automation Bot commented Jun 15, 2026

Copy link
Copy Markdown

Summary

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

Commit Message(s)

kprobes/x86: Use copy_from_kernel_nofault() to read from unsafe address

jira VULN-37443
cve CVE-2024-26946
commit-author Masami Hiramatsu (Google) <mhiramat@kernel.org>
commit 4e51653d5d871f40f1bd5cf95cc7f2d8b33d063b
wifi: mac80211: check/clear fast rx for non-4addr sta VLAN changes

jira VULN-47154
cve CVE-2024-35789
commit-author Felix Fietkau <nbd@nbd.name>
commit 4f2bdb3c5e3189297e156b3ff84b140423d64685
scsi: mpi3mr: Avoid memcpy field-spanning write WARNING

jira VULN-47431
cve CVE-2024-36920
commit-author Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
commit 429846b4b6ce9853e0d803a2357bb2e55083adf0
i40e: fix vf may be used uninitialized in this function warning

jira VULN-5279
cve CVE-2024-36020
commit-author Aleksandr Loktionov <aleksandr.loktionov@intel.com>
commit f37c4eac99c258111d414d31b740437e1925b8e8
xen-netfront: Add missing skb_mark_for_recycle

jira VULN-3103
cve CVE-2024-27393
commit-author Jesper Dangaard Brouer <hawk@kernel.org>
commit 037965402a010898d34f4e35327d22c0a95cd51f
gro: fix ownership transfer

jira VULN-37821
cve CVE-2024-35890
commit-author Antoine Tenart <atenart@kernel.org>
commit ed4cccef64c1d0d5b91e69f7a8a6697c3a865486
net: fix memory leak in skb_segment_list for GRO packets

jira VULN-174746
cve CVE-2026-22979
commit-author Mohammad Heib <mheib@redhat.com>
commit 238e03d0466239410b72294b79494e43d4fabe77
mlxbf_gige: stop interface during shutdown

jira VULN-37795
cve CVE-2024-35885
commit-author David Thompson <davthompson@nvidia.com>
commit 09ba28e1cd3cf715daab1fca6e1623e22fd754a6

Test Results

✅ Build Stage

Architecture Build Time Total Time
x86_64 24m 25s 25m 15s
aarch64 12m 48s 13m 22s

✅ Boot Verification

✅ Kernel Selftests

Architecture Passed Failed Compared Against Status
x86_64 174 24 ciqlts9_2 ✅ No regressions
aarch64 140 28 ciqlts9_2 ✅ No regressions

✅ LTP Results

Architecture Passed Failed Compared Against Status
x86_64 1439 81 ciqlts9_2 ✅ No regressions
aarch64 1409 83 ciqlts9_2 ✅ No regressions

aarch64 newly passing:

  • fcntl14 (FAIL -> PASS)
  • fcntl14_64 (FAIL -> PASS)
  • fork14 (FAIL -> PASS)
  • futex_cmp_requeue01 (FAIL -> PASS)
  • mmap16 (FAIL -> PASS)

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

@ciq-kernel-automation ciq-kernel-automation Bot added the created-by-kernelci Tag PRs that were automatically created when a user branch was pushed to the repo (kernelCI) label Jun 15, 2026
@github-actions

Copy link
Copy Markdown

🤖 Validation Checks In Progress Workflow run: https://github.com/ctrliq/kernel-src-tree/actions/runs/27556375466

@github-actions

Copy link
Copy Markdown

🔍 Interdiff Analysis

  • ⚠️ PR commit 78c848fd959 (net: fix memory leak in skb_segment_list for GRO packets) → upstream 238e03d04662
    Differences found:
================================================================================
*    CONTEXT DIFFERENCES - surrounding code differences between the patches    *
================================================================================

--- b/net/core/skbuff.c
+++ b/net/core/skbuff.c
@@ -4015,4 +4644,4 @@
 
 	skb_push(skb, -skb_network_offset(skb) + offset);
 
-	skb_shinfo(skb)->frag_list = NULL;
+	/* Ensure the head is writeable before touching the shared info */
@@ -4062,5 +4696,5 @@
-
-	} while (list_skb);
+			goto err_linearize;
+	}
 
 	skb->truesize = skb->truesize - delta_truesize;
 	skb->data_len = skb->data_len - delta_len;

This is an automated interdiff check for backported commits.

@github-actions

Copy link
Copy Markdown

JIRA PR Check Results

86 commit(s) with issues found:

Commit d38622996959

Summary: arm64: errata: Mitigate TLBI errata on Microsoft Azure Cobalt 100 CPU

❌ Errors:

  • VULN-187521: Status is 'Done', expected 'In Progress'

Commit fb7b641c2421

Summary: arm64: errata: Mitigate TLBI errata on NVIDIA Olympus CPU

❌ Errors:

  • VULN-187521: Status is 'Done', expected 'In Progress'

Commit 72fbbaf2fb1a

Summary: arm64: errata: Mitigate TLBI errata on various Arm CPUs

❌ Errors:

  • VULN-187521: Status is 'Done', expected 'In Progress'

Commit b9b315ad55fd

Summary: arm64: cputype: Add C1-Premium definitions

❌ Errors:

  • VULN-187521: Status is 'Done', expected 'In Progress'

Commit 61af6a9fbdb3

Summary: arm64: cputype: Add C1-Ultra definitions

❌ Errors:

  • VULN-187521: Status is 'Done', expected 'In Progress'

Commit b08eac74804c

Summary: arm64: cputype: Add NVIDIA Olympus definitions

❌ Errors:

  • VULN-187521: Status is 'Done', expected 'In Progress'

Commit dc80cb350d7b

Summary: arm64: cputype: Add C1-Pro definitions

❌ Errors:

  • VULN-187521: Status is 'Done', expected 'In Progress'

Commit faa19e6bfb7d

Summary: arm64: cputype: Add Neoverse-V3AE definitions

❌ Errors:

  • VULN-187521: Status is 'Done', expected 'In Progress'

Commit 8544ec262d7a

Summary: arm64: cputype: Add Neoverse-N3 definitions

❌ Errors:

  • VULN-187521: Status is 'Done', expected 'In Progress'

Commit 05a06ade0aeb

Summary: arm64: cputype: Add Cortex-A720AE definitions

❌ Errors:

  • VULN-187521: Status is 'Done', expected 'In Progress'

Commit 30b48bb5f465

Summary: arm64: cputype: Add Cortex-A725 definitions

❌ Errors:

  • VULN-187521: Status is 'Done', expected 'In Progress'

Commit 60e8f4c54dbd

Summary: arm64: Subscribe Microsoft Azure Cobalt 100 to ARM Neoverse N2 errata

❌ Errors:

  • VULN-187521: Status is 'Done', expected 'In Progress'

Commit f85162db395b

Summary: arm64: cputype: Add Cortex-X925 definitions

❌ Errors:

  • VULN-187521: Status is 'Done', expected 'In Progress'

Commit c58354e931b5

Summary: arm64: cputype: Add Neoverse-V3 definitions

❌ Errors:

  • VULN-187521: Status is 'Done', expected 'In Progress'

Commit 87c99755c42b

Summary: arm64: cputype: Add Cortex-X4 definitions

❌ Errors:

  • VULN-187521: Status is 'Done', expected 'In Progress'

Commit 4fa650214be6

Summary: arm64: cputype: Add Cortex-A720 definitions

❌ Errors:

  • VULN-187521: Status is 'Done', expected 'In Progress'

Commit c1cfc9b452e0

Summary: arm64: Add Neoverse-V2 part

❌ Errors:

  • VULN-187521: Status is 'Done', expected 'In Progress'

Commit 4eb4a74799ce

Summary: arm64: cputype: Add Cortex-X3 definitions

❌ Errors:

  • VULN-187521: Status is 'Done', expected 'In Progress'

Commit 958889b256ba

Summary: arm64: cputype: Add Cortex-X1C definitions

❌ Errors:

  • VULN-187521: Status is 'Done', expected 'In Progress'

Commit f807da37bfba

Summary: arm64: cputype: Add MIDR_CORTEX_A76AE

❌ Errors:

  • VULN-187521: Status is 'Done', expected 'In Progress'

Commit 982a49d9ebf6

Summary: ip6_tunnel: clear skb2->cb[] in ip4ip6_err()

❌ Errors:

  • VULN-183731: Status is 'Done', expected 'In Progress'

Commit f01206a4a971

Summary: ipv6: icmp: clear skb2->cb[] in ip6_err_gen_icmpv6_unreach()

❌ Errors:

  • VULN-183737: Status is 'Done', expected 'In Progress'

Commit 02aa6f4153fb

Summary: net/sched: sch_cake: Fix incorrect qlen reduction in cake_drop

❌ Errors:

  • VULN-187517: Status is 'Done', expected 'In Progress'

Commit 195e5dc6b012

Summary: net/sched: Make cake_enqueue return NET_XMIT_CN when past buffer_limit

❌ Errors:

  • VULN-152970: Status is 'Done', expected 'In Progress'

Commit 40080203cd45

Summary: net: sched: fix ordering of qlen adjustment

❌ Errors:

  • VULN-46603: Status is 'Done', expected 'In Progress'

Commit 697905776c09

Summary: netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate()

❌ Errors:

  • VULN-176072: Status is 'Done', expected 'In Progress'

Commit 435af4f1f4b6

Summary: netfilter: nf_tables: do not compare internal table flags on updates

❌ Errors:

  • VULN-4986: Status is 'Done', expected 'In Progress'

Commit 2d2b563a476d

Summary: octeontx2-af: Use separate handlers for interrupts

❌ Errors:

  • VULN-37687: Status is 'Done', expected 'In Progress'

Commit 60e898ba4825

Summary: dm: call the resume method on internal suspend

❌ Errors:

  • VULN-37132: Status is 'Done', expected 'In Progress'

Commit e0047cb8c74d

Summary: nfp: flower: handle acti_netdevs allocation failure

❌ Errors:

  • VULN-37723: Status is 'Done', expected 'In Progress'

Commit 831028cb3487

Summary: scsi: lpfc: Move NPIV's transport unregistration to after resource clean up

❌ Errors:

  • VULN-47578: Status is 'Done', expected 'In Progress'

Commit 31bc7323ed64

Summary: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up()

❌ Errors:

  • VULN-47487: Status is 'Done', expected 'In Progress'

Commit 15016e4ce174

Summary: scsi: qla2xxx: Fix command flush on cable pull

❌ Errors:

  • VULN-37382: Status is 'Done', expected 'In Progress'

Commit 034be15ae09f

Summary: netfilter: nf_tables: disallow anonymous set with timeout flag

❌ Errors:

  • VULN-828: Status is 'Done', expected 'In Progress'

Commit 84c48b17c96d

Summary: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache

❌ Errors:

  • VULN-180163: Status is 'Done', expected 'In Progress'

Commit 15f65a192965

Summary: NFSD: Fix crash in nfsd4_read_release()

❌ Errors:

  • VULN-161290: Status is 'Done', expected 'In Progress'

Commit f2244de83ca4

Summary: nfsd: call op_release, even when op_func returns an error

❌ Errors:

  • VULN-154845: Status is 'Done', expected 'In Progress'

Commit 9a55104d838a

Summary: can: raw: fix ro->uniq use-after-free in raw_rcv()

❌ Errors:

  • VULN-182364: Status is 'Done', expected 'In Progress'

Commit 66fce69467df

Summary: RDMA/umad: Reject negative data_len in ib_umad_write

❌ Errors:

  • VULN-178540: Status is 'Done', expected 'In Progress'

Commit e3f5fbc0e1ae

Summary: blk-mq: fix IO hang from sbitmap wakeup race

❌ Errors:

  • VULN-860: Status is 'Done', expected 'In Progress'

Commit 753361483fd7

Summary: PM / devfreq: Synchronize devfreq_monitor_[start/stop]

❌ Errors:

  • VULN-35274: Status is 'Done', expected 'In Progress'

Commit d31ec9714663

Summary: wifi: ath10k: fix NULL pointer dereference in ath10k_wmi_tlv_op_pull_mgmt_tx_compl_ev()

❌ Errors:

  • VULN-35352: Status is 'Done', expected 'In Progress'

Commit 786a1793123e

Summary: gfs2: Fix kernel NULL pointer dereference in gfs2_rgrp_dump

❌ Errors:

  • VULN-518: Status is 'Done', expected 'In Progress'

Commit 02140632878a

Summary: block: add check that partition length needs to be aligned with block size

❌ Errors:

  • VULN-34806: Status is 'Done', expected 'In Progress'

Commit ff3f81b1bbbc

Summary: pstore/ram: Fix crash when setting number of cpus to an odd number

❌ Errors:

  • VULN-4502: Status is 'Done', expected 'In Progress'

Commit 64c6f93dc2fe

Summary: tcp: do not accept ACK of bytes we never sent

❌ Errors:

  • VULN-36192: Status is 'Done', expected 'In Progress'

Commit 18156adc35ab

Summary: perf/x86/intel/uncore: Fix NULL pointer dereference issue in upi_fill_topology()

❌ Errors:

  • VULN-34776: Status is 'Done', expected 'In Progress'

Commit a65f82f87dc3

Summary: scsi: libfc: Fix potential NULL pointer dereference in fc_lport_ptp_setup()

❌ Errors:

  • VULN-35889: Status is 'Done', expected 'In Progress'

Commit b64691d0cdfb

Summary: scsi: ibmvfc: Remove BUG_ON in the case of an empty event pool

❌ Errors:

  • VULN-4654: Status is 'Done', expected 'In Progress'

Commit 3a6db402aca2

Summary: Bluetooth: hci_codec: Fix leaking content of local_codecs

❌ Errors:

  • VULN-35032: Status is 'Done', expected 'In Progress'

Commit 0077ab073f15

Summary: Bluetooth: Fix support for Read Local Supported Codecs V2

❌ Errors:

  • VULN-35032: Status is 'Done', expected 'In Progress'

Commit 908bee4d3cdc

Summary: mm/slab_common: fix slab_caches list corruption after kmem_cache_destroy()

❌ Errors:

  • VULN-6753: Status is 'Done', expected 'In Progress'

Commit d8fcb9e02ece

Summary: tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc

❌ Errors:

  • VULN-36184: Status is 'Done', expected 'In Progress'

Commit 52abe0c2e07a

Summary: vxlan: Fix nexthop hash size

❌ Errors:

  • VULN-154381: Status is 'Done', expected 'In Progress'

Commit fc7143c78b2e

Summary: blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats()

❌ Errors:

  • VULN-155913: Status is 'Done', expected 'In Progress'

Commit b91ef7fa5f5d

Summary: ptrace: slightly saner 'get_dumpable()' logic

❌ Errors:

  • VULN-185426: Status is 'Done', expected 'In Progress'

Commit 70b87459079b

Summary: net: skbuff: propagate shared-frag marker through frag-transfer helpers

❌ Errors:

  • VULN-185346: Status is 'Done', expected 'In Progress'

Commit b9ea22e0e20e

Summary: xfrm: esp: avoid in-place decrypt on shared skb frags

❌ Errors:

  • VULN-184830: Status is 'Done', expected 'In Progress'

Commit 441c7ea1550c

Summary: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count()

❌ Errors:

  • VULN-176313: Status is 'Done', expected 'In Progress'

Commit 86d094c11e26

Summary: scsi: ses: Fix slab-out-of-bounds in ses_intf_remove()

❌ Errors:

  • VULN-157177: Status is 'Done', expected 'In Progress'

Commit 26cf99c81443

Summary: scsi: ses: Fix slab-out-of-bounds in ses_enclosure_data_process()

❌ Errors:

  • VULN-169340: Status is 'Done', expected 'In Progress'

Commit 674462ecd784

Summary: cgroup/cpuset: Fix wrong check in update_parent_subparts_cpumask()

❌ Errors:

  • VULN-55110: Status is 'Done', expected 'In Progress'

Commit be8b74b46b64

Summary: bpf, sockmap: Avoid using sk_socket after free when sending

❌ Errors:

  • VULN-71872: Status is 'Done', expected 'In Progress'

Commit 40396b360d78

Summary: sock_map: avoid race between sock_map_close and sk_psock_put

❌ Errors:

  • VULN-43557: Status is 'Done', expected 'In Progress'

Commit 68b2a48155b1

Summary: bpf, sockmap: Don't let sock_map_{close,destroy,unhash} call itself

❌ Errors:

  • VULN-35577: Status is 'Done', expected 'In Progress'

Commit 7aeeec8ac081

Summary: Bluetooth: hci_conn: Fix crash on hci_create_cis_sync

❌ Errors:

  • VULN-156737: Status is 'Done', expected 'In Progress'

Commit f14e1cacc553

Summary: EDAC/i10nm: fix refcount leak in pci_get_dev_wrapper()

❌ Errors:

  • VULN-168502: Status is 'Done', expected 'In Progress'

Commit f70b4a018b4f

Summary: objtool: Fix SEGFAULT

❌ Errors:

  • VULN-173009: Status is 'Done', expected 'In Progress'

Commit 7d033beb18ed

Summary: net: genl: fix error path memory leak in policy dumping

❌ Errors:

  • VULN-69357: Status is 'Done', expected 'In Progress'

Commit a1fac0a428d9

Summary: crypto: algif_aead - snapshot IV for async AEAD requests

❌ Errors:

  • VULN-181879: Status is 'Done', expected 'In Progress'

Commit 75e31518673b

Summary: crypto: algif_aead - Fix minimum RX size check for decryption

❌ Errors:

  • VULN-181879: Status is 'Done', expected 'In Progress'

Commit 3dc6b0a75326

Summary: crypto: authencesn - reject short ahash digests during instance creation

❌ Errors:

  • VULN-181879: Status is 'Done', expected 'In Progress'

Commit 5aa64d636016

Summary: crypto: authencesn - Fix src offset when decrypting in-place

❌ Errors:

  • VULN-181879: Status is 'Done', expected 'In Progress'

Commit 01a882048511

Summary: crypto: authencesn - Do not place hiseq at end of dst for out-of-place decryption

❌ Errors:

  • VULN-181879: Status is 'Done', expected 'In Progress'

Commit ca6d12fdea71

Summary: crypto: authencesn - reject too-short AAD (assoclen<8) to match ESP/ESN spec

❌ Errors:

  • VULN-175567: Status is 'Done', expected 'In Progress'

Commit 9e1d2f257723

Summary: crypto: af_alg - Fix page reassignment overflow in af_alg_pull_tsgl

❌ Errors:

  • VULN-182989: Status is 'Done', expected 'In Progress'

Commit c40da5c6fc89

Summary: crypto: af_alg - limit RX SG extraction by receive buffer budget

❌ Errors:

  • VULN-182989: Status is 'Done', expected 'In Progress'

Commit e2ce9f2cb88b

Summary: crypto: algif_aead - Revert to operating out-of-place

❌ Errors:

  • VULN-181879: Status is 'Done', expected 'In Progress'

Commit 9fb217d2c561

Summary: crypto: af-alg - fix NULL pointer dereference in scatterwalk

❌ Errors:

  • VULN-181879: Status is 'Done', expected 'In Progress'

Commit b2740b43062d

Summary: vt: fix memory overlapping when deleting chars in the buffer

❌ Errors:

  • VULN-241: Status is 'Done', expected 'In Progress'

Commit 872d60b03187

Summary: um: Fix out-of-bounds read in LDT setup

❌ Errors:

  • VULN-51243: Status is 'Done', expected 'In Progress'

Commit 73788615067e

Summary: net: amd-xgbe: Fix skb data length underflow

❌ Errors:

  • VULN-4427: Status is 'Done', expected 'In Progress'

Commit b7d26c479448

Summary: ethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in hns_dsaf_ge_srst_by_port()

❌ Errors:

  • VULN-4395: Status is 'Done', expected 'In Progress'

Commit 8ec9494cc961

Summary: hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary structure field

❌ Errors:

  • VULN-63632: Status is 'Done', expected 'In Progress'

Commit 5442314412da

Summary: hwmon: (w83792d) Fix NULL pointer dereference by removing unnecessary structure field

❌ Errors:

  • VULN-63624: Status is 'Done', expected 'In Progress'

Commit 55a8a460264d

Summary: net: hns3: do not allow call hns3_nic_net_open repeatedly

❌ Errors:

  • VULN-3098: Status is 'Done', expected 'In Progress'

Summary: Checked 100 commit(s) total.

@github-actions

Copy link
Copy Markdown

Validation checks completed with issues View full results: https://github.com/ctrliq/kernel-src-tree/actions/runs/27556375466

CIQ Kernel Automation added 8 commits June 16, 2026 13:19
jira VULN-37443
cve CVE-2024-26946
commit-author Masami Hiramatsu (Google) <mhiramat@kernel.org>
commit 4e51653

Read from an unsafe address with copy_from_kernel_nofault() in
arch_adjust_kprobe_addr() because this function is used before checking
the address is in text or not. Syzcaller bot found a bug and reported
the case if user specifies inaccessible data area,
arch_adjust_kprobe_addr() will cause a kernel panic.

[ mingo: Clarified the comment. ]

Fixes: cc66bb9 ("x86/ibt,kprobes: Cure sym+0 equals fentry woes")
	Reported-by: Qiang Zhang <zzqq0103.hey@gmail.com>
	Tested-by: Jinghao Jia <jinghao7@illinois.edu>
	Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
	Signed-off-by: Ingo Molnar <mingo@kernel.org>
Link: https://lore.kernel.org/r/171042945004.154897.2221804961882915806.stgit@devnote2
(cherry picked from commit 4e51653)
	Signed-off-by: CIQ Kernel Automation <ciq_kernel_automation@ciq.com>
jira VULN-47154
cve CVE-2024-35789
commit-author Felix Fietkau <nbd@nbd.name>
commit 4f2bdb3

When moving a station out of a VLAN and deleting the VLAN afterwards, the
fast_rx entry still holds a pointer to the VLAN's netdev, which can cause
use-after-free bugs. Fix this by immediately calling ieee80211_check_fast_rx
after the VLAN change.

	Cc: stable@vger.kernel.org
	Reported-by: ranygh@riseup.net
	Signed-off-by: Felix Fietkau <nbd@nbd.name>
Link: https://msgid.link/20240316074336.40442-1-nbd@nbd.name
	Signed-off-by: Johannes Berg <johannes.berg@intel.com>
(cherry picked from commit 4f2bdb3)
	Signed-off-by: CIQ Kernel Automation <ciq_kernel_automation@ciq.com>
jira VULN-47431
cve CVE-2024-36920
commit-author Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
commit 429846b

When the "storcli2 show" command is executed for eHBA-9600, mpi3mr driver
prints this WARNING message:

  memcpy: detected field-spanning write (size 128) of single field "bsg_reply_buf->reply_buf" at drivers/scsi/mpi3mr/mpi3mr_app.c:1658 (size 1)
  WARNING: CPU: 0 PID: 12760 at drivers/scsi/mpi3mr/mpi3mr_app.c:1658 mpi3mr_bsg_request+0x6b12/0x7f10 [mpi3mr]

The cause of the WARN is 128 bytes memcpy to the 1 byte size array "__u8
replay_buf[1]" in the struct mpi3mr_bsg_in_reply_buf. The array is intended
to be a flexible length array, so the WARN is a false positive.

To suppress the WARN, remove the constant number '1' from the array
declaration and clarify that it has flexible length. Also, adjust the
memory allocation size to match the change.

	Suggested-by: Sathya Prakash Veerichetty <sathya.prakash@broadcom.com>
	Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Link: https://lore.kernel.org/r/20240323084155.166835-1-shinichiro.kawasaki@wdc.com
	Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
(cherry picked from commit 429846b)
	Signed-off-by: CIQ Kernel Automation <ciq_kernel_automation@ciq.com>
jira VULN-5279
cve CVE-2024-36020
commit-author Aleksandr Loktionov <aleksandr.loktionov@intel.com>
commit f37c4ea

To fix the regression introduced by commit 52424f9, which causes
servers hang in very hard to reproduce conditions with resets races.
Using two sources for the information is the root cause.
In this function before the fix bumping v didn't mean bumping vf
pointer. But the code used this variables interchangeably, so stale vf
could point to different/not intended vf.

Remove redundant "v" variable and iterate via single VF pointer across
whole function instead to guarantee VF pointer validity.

Fixes: 52424f9 ("i40e: Fix VF hang when reset is triggered on another VF")
	Signed-off-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
	Reviewed-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
	Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
	Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>
	Tested-by: Rafal Romanowski <rafal.romanowski@intel.com>
	Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
(cherry picked from commit f37c4ea)
	Signed-off-by: CIQ Kernel Automation <ciq_kernel_automation@ciq.com>
jira VULN-3103
cve CVE-2024-27393
commit-author Jesper Dangaard Brouer <hawk@kernel.org>
commit 0379654

Notice that skb_mark_for_recycle() is introduced later than fixes tag in
commit 6a5bcd8 ("page_pool: Allow drivers to hint on SKB recycling").

It is believed that fixes tag were missing a call to page_pool_release_page()
between v5.9 to v5.14, after which is should have used skb_mark_for_recycle().
Since v6.6 the call page_pool_release_page() were removed (in
commit 535b9c6 ("net: page_pool: hide page_pool_release_page()")
and remaining callers converted (in commit 6bfef2e ("Merge branch
'net-page_pool-remove-page_pool_release_page'")).

This leak became visible in v6.8 via commit dba1b8a ("mm/page_pool: catch
page_pool memory leaks").

	Cc: stable@vger.kernel.org
Fixes: 6c5aa6f ("xen networking: add basic XDP support for xen-netfront")
	Reported-by: Leonidas Spyropoulos <artafinde@archlinux.com>
Link: https://bugzilla.kernel.org/show_bug.cgi?id=218654
	Reported-by: Arthur Borsboom <arthurborsboom@gmail.com>
	Signed-off-by: Jesper Dangaard Brouer <hawk@kernel.org>
Link: https://lore.kernel.org/r/171154167446.2671062.9127105384591237363.stgit@firesoul
	Signed-off-by: Jakub Kicinski <kuba@kernel.org>
(cherry picked from commit 0379654)
	Signed-off-by: CIQ Kernel Automation <ciq_kernel_automation@ciq.com>
jira VULN-37821
cve CVE-2024-35890
commit-author Antoine Tenart <atenart@kernel.org>
commit ed4ccce

If packets are GROed with fraglist they might be segmented later on and
continue their journey in the stack. In skb_segment_list those skbs can
be reused as-is. This is an issue as their destructor was removed in
skb_gro_receive_list but not the reference to their socket, and then
they can't be orphaned. Fix this by also removing the reference to the
socket.

For example this could be observed,

  kernel BUG at include/linux/skbuff.h:3131!  (skb_orphan)
  RIP: 0010:ip6_rcv_core+0x11bc/0x19a0
  Call Trace:
   ipv6_list_rcv+0x250/0x3f0
   __netif_receive_skb_list_core+0x49d/0x8f0
   netif_receive_skb_list_internal+0x634/0xd40
   napi_complete_done+0x1d2/0x7d0
   gro_cell_poll+0x118/0x1f0

A similar construction is found in skb_gro_receive, apply the same
change there.

Fixes: 5e10da5 ("skbuff: allow 'slow_gro' for skb carring sock reference")
	Signed-off-by: Antoine Tenart <atenart@kernel.org>
	Reviewed-by: Willem de Bruijn <willemb@google.com>
	Signed-off-by: David S. Miller <davem@davemloft.net>
(cherry picked from commit ed4ccce)
	Signed-off-by: CIQ Kernel Automation <ciq_kernel_automation@ciq.com>
jira VULN-174746
cve CVE-2026-22979
commit-author Mohammad Heib <mheib@redhat.com>
commit 238e03d

When skb_segment_list() is called during packet forwarding, it handles
packets that were aggregated by the GRO engine.

Historically, the segmentation logic in skb_segment_list assumes that
individual segments are split from a parent SKB and may need to carry
their own socket memory accounting. Accordingly, the code transfers
truesize from the parent to the newly created segments.

Prior to commit ed4ccce ("gro: fix ownership transfer"), this
truesize subtraction in skb_segment_list() was valid because fragments
still carry a reference to the original socket.

However, commit ed4ccce ("gro: fix ownership transfer") changed
this behavior by ensuring that fraglist entries are explicitly
orphaned (skb->sk = NULL) to prevent illegal orphaning later in the
stack. This change meant that the entire socket memory charge remained
with the head SKB, but the corresponding accounting logic in
skb_segment_list() was never updated.

As a result, the current code unconditionally adds each fragment's
truesize to delta_truesize and subtracts it from the parent SKB. Since
the fragments are no longer charged to the socket, this subtraction
results in an effective under-count of memory when the head is freed.
This causes sk_wmem_alloc to remain non-zero, preventing socket
destruction and leading to a persistent memory leak.

The leak can be observed via KMEMLEAK when tearing down the networking
environment:

unreferenced object 0xffff8881e6eb9100 (size 2048):
  comm "ping", pid 6720, jiffies 4295492526
  backtrace:
    kmem_cache_alloc_noprof+0x5c6/0x800
    sk_prot_alloc+0x5b/0x220
    sk_alloc+0x35/0xa00
    inet6_create.part.0+0x303/0x10d0
    __sock_create+0x248/0x640
    __sys_socket+0x11b/0x1d0

Since skb_segment_list() is exclusively used for SKB_GSO_FRAGLIST
packets constructed by GRO, the truesize adjustment is removed.

The call to skb_release_head_state() must be preserved. As documented in
commit cf673ed ("net: fix fraglist segmentation reference count
leak"), it is still required to correctly drop references to SKB
extensions that may be overwritten during __copy_skb_header().

Fixes: ed4ccce ("gro: fix ownership transfer")
	Signed-off-by: Mohammad Heib <mheib@redhat.com>
	Reviewed-by: Willem de Bruijn <willemb@google.com>
Link: https://patch.msgid.link/20260104213101.352887-1-mheib@redhat.com
	Signed-off-by: Jakub Kicinski <kuba@kernel.org>
(cherry picked from commit 238e03d)
	Signed-off-by: CIQ Kernel Automation <ciq_kernel_automation@ciq.com>
jira VULN-37795
cve CVE-2024-35885
commit-author David Thompson <davthompson@nvidia.com>
commit 09ba28e

The mlxbf_gige driver intermittantly encounters a NULL pointer
exception while the system is shutting down via "reboot" command.
The mlxbf_driver will experience an exception right after executing
its shutdown() method.  One example of this exception is:

Unable to handle kernel NULL pointer dereference at virtual address 0000000000000070
Mem abort info:
  ESR = 0x0000000096000004
  EC = 0x25: DABT (current EL), IL = 32 bits
  SET = 0, FnV = 0
  EA = 0, S1PTW = 0
  FSC = 0x04: level 0 translation fault
Data abort info:
  ISV = 0, ISS = 0x00000004
  CM = 0, WnR = 0
user pgtable: 4k pages, 48-bit VAs, pgdp=000000011d373000
[0000000000000070] pgd=0000000000000000, p4d=0000000000000000
Internal error: Oops: 96000004 [#1] SMP
CPU: 0 PID: 13 Comm: ksoftirqd/0 Tainted: G S         OE     5.15.0-bf.6.gef6992a #1
Hardware name: https://www.mellanox.com BlueField SoC/BlueField SoC, BIOS 4.0.2.12669 Apr 21 2023
pstate: 20400009 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : mlxbf_gige_handle_tx_complete+0xc8/0x170 [mlxbf_gige]
lr : mlxbf_gige_poll+0x54/0x160 [mlxbf_gige]
sp : ffff8000080d3c10
x29: ffff8000080d3c10 x28: ffffcce72cbb7000 x27: ffff8000080d3d58
x26: ffff0000814e7340 x25: ffff331cd1a05000 x24: ffffcce72c4ea008
x23: ffff0000814e4b40 x22: ffff0000814e4d10 x21: ffff0000814e4128
x20: 0000000000000000 x19: ffff0000814e4a80 x18: ffffffffffffffff
x17: 000000000000001c x16: ffffcce72b4553f4 x15: ffff80008805b8a7
x14: 0000000000000000 x13: 0000000000000030 x12: 0101010101010101
x11: 7f7f7f7f7f7f7f7f x10: c2ac898b17576267 x9 : ffffcce720fa5404
x8 : ffff000080812138 x7 : 0000000000002e9a x6 : 0000000000000080
x5 : ffff00008de3b000 x4 : 0000000000000000 x3 : 0000000000000001
x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
 mlxbf_gige_handle_tx_complete+0xc8/0x170 [mlxbf_gige]
 mlxbf_gige_poll+0x54/0x160 [mlxbf_gige]
 __napi_poll+0x40/0x1c8
 net_rx_action+0x314/0x3a0
 __do_softirq+0x128/0x334
 run_ksoftirqd+0x54/0x6c
 smpboot_thread_fn+0x14c/0x190
 kthread+0x10c/0x110
 ret_from_fork+0x10/0x20
Code: 8b070000 f9000ea0 f95056c0 f86178a1 (b9407002)
---[ end trace 7cc3941aa0d8e6a4 ]---
Kernel panic - not syncing: Oops: Fatal exception in interrupt
Kernel Offset: 0x4ce722520000 from 0xffff800008000000
PHYS_OFFSET: 0x80000000
CPU features: 0x000005c1,a3330e5a
Memory Limit: none
---[ end Kernel panic - not syncing: Oops: Fatal exception in interrupt ]---

During system shutdown, the mlxbf_gige driver's shutdown() is always executed.
However, the driver's stop() method will only execute if networking interface
configuration logic within the Linux distribution has been setup to do so.

If shutdown() executes but stop() does not execute, NAPI remains enabled
and this can lead to an exception if NAPI is scheduled while the hardware
interface has only been partially deinitialized.

The networking interface managed by the mlxbf_gige driver must be properly
stopped during system shutdown so that IFF_UP is cleared, the hardware
interface is put into a clean state, and NAPI is fully deinitialized.

Fixes: f92e186 ("Add Mellanox BlueField Gigabit Ethernet driver")
	Signed-off-by: David Thompson <davthompson@nvidia.com>
Link: https://lore.kernel.org/r/20240325210929.25362-1-davthompson@nvidia.com
	Signed-off-by: Jakub Kicinski <kuba@kernel.org>
(cherry picked from commit 09ba28e)
	Signed-off-by: CIQ Kernel Automation <ciq_kernel_automation@ciq.com>
@roxanan1996 roxanan1996 force-pushed the {ciq_kernel_automation}_ciqlts9_2 branch from 16e3d40 to 00a230a Compare June 16, 2026 11:19
@github-actions

Copy link
Copy Markdown

🤖 Validation Checks In Progress Workflow run: https://github.com/ctrliq/kernel-src-tree/actions/runs/27614305100

@github-actions

Copy link
Copy Markdown

🔍 Interdiff Analysis

  • ⚠️ PR commit abdf3971b76 (net: fix memory leak in skb_segment_list for GRO packets) → upstream 238e03d04662
    Differences found:
================================================================================
*    CONTEXT DIFFERENCES - surrounding code differences between the patches    *
================================================================================

--- b/net/core/skbuff.c
+++ b/net/core/skbuff.c
@@ -4015,4 +4644,4 @@
 
 	skb_push(skb, -skb_network_offset(skb) + offset);
 
-	skb_shinfo(skb)->frag_list = NULL;
+	/* Ensure the head is writeable before touching the shared info */
@@ -4062,5 +4696,5 @@
-
-	} while (list_skb);
+			goto err_linearize;
+	}
 
 	skb->truesize = skb->truesize - delta_truesize;
 	skb->data_len = skb->data_len - delta_len;

This is an automated interdiff check for backported commits.

@github-actions

Copy link
Copy Markdown

🤖 Validation Checks In Progress Workflow run: https://github.com/ctrliq/kernel-src-tree/actions/runs/27614314441

@github-actions

Copy link
Copy Markdown

🔍 Interdiff Analysis

  • ⚠️ PR commit abdf3971b76 (net: fix memory leak in skb_segment_list for GRO packets) → upstream 238e03d04662
    Differences found:
================================================================================
*    CONTEXT DIFFERENCES - surrounding code differences between the patches    *
================================================================================

--- b/net/core/skbuff.c
+++ b/net/core/skbuff.c
@@ -4015,4 +4644,4 @@
 
 	skb_push(skb, -skb_network_offset(skb) + offset);
 
-	skb_shinfo(skb)->frag_list = NULL;
+	/* Ensure the head is writeable before touching the shared info */
@@ -4062,5 +4696,5 @@
-
-	} while (list_skb);
+			goto err_linearize;
+	}
 
 	skb->truesize = skb->truesize - delta_truesize;
 	skb->data_len = skb->data_len - delta_len;

This is an automated interdiff check for backported commits.

@github-actions

Copy link
Copy Markdown

Validation checks completed successfully View full results: https://github.com/ctrliq/kernel-src-tree/actions/runs/27614305100

@github-actions

Copy link
Copy Markdown

Validation checks completed successfully View full results: https://github.com/ctrliq/kernel-src-tree/actions/runs/27614314441

@bmastbergen bmastbergen self-requested a review June 17, 2026 15:41

@bmastbergen bmastbergen left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🥌

@bmastbergen bmastbergen requested a review from a team June 17, 2026 15:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

created-by-kernelci Tag PRs that were automatically created when a user branch was pushed to the repo (kernelCI)

Development

Successfully merging this pull request may close these issues.

1 participant