From: Greg Kroah-Hartman Date: Wed, 29 Jul 2026 13:42:49 +0000 (+0200) Subject: 6.12-stable patches X-Git-Tag: v6.1.179~20 X-Git-Url: http://git.ipfire.org/gitweb/?a=commitdiff_plain;h=e1501a546950c6c09d1755fc8e8ea64e1122d0ee;p=thirdparty%2Fkernel%2Fstable-queue.git 6.12-stable patches added patches: arm64-syscall-ensure-saved-x0-is-kept-in-sync-with-tracer-updates.patch cdrom-fix-stack-out-of-bounds-read-in-cdromvolctrl.patch comedi-comedi_parport-deal-with-premature-interrupt.patch firmware-stratix10-svc-fix-memory-leaks-and-list-corruption-bugs.patch intel_th-fix-msc-output-device-reference-leak.patch loongarch-fix-oops-during-single-step-debugging.patch loongarch-move-jump_label_init-before-parse_early_param.patch loongarch-retrieve-cpu-package-id-from-pptt-when-available.patch mei-bus-access-mei_device-under-device_lock-on-cleanup.patch misc-nsm-only-unlock-nsm_dev-on-post-lock-error-paths.patch misc-nsm-pin-the-module-while-the-device-is-open.patch mptcp-decrement-subflows-counter-on-failed-passive-join.patch mptcp-only-set-data_fin-when-a-mapping-is-present.patch objtool-rust-add-one-more-noreturn-rust-function-for-rust-1.99.0.patch revert-arm64-syscall-ensure-saved-x0-is-kept-in-sync-with-tracer-updates.patch rust-allow-clippy-unwrap_or_default-globally.patch serial-8250_mid-fix-null-function-pointer-dereference-on-dnv-icx-d-snr-platforms.patch serial-sc16is7xx-implement-gpio-get_direction-callback.patch tracing-eprobe-fix-exact-system-name-matching-in-eprobe_dyn_event_match.patch tracing-fix-mmiotrace-possible-null-dereferencing-of-hiter-dev.patch tracing-fix-resource-leak-on-mmiotrace-trace_pipe-close.patch tracing-probes-avoid-temporary-buffer-truncation-in-trace_probe_match_command_args.patch tracing-probes-fix-potential-underflow-in-len_or_zero-macro.patch tracing-probes-prevent-out-of-bounds-write-in-__trace_probe_log_err.patch uio_hv_generic-bind-to-fcopy-device-by-default.patch x86-boot-compressed-disable-jump-tables.patch --- diff --git a/queue-6.12/arm64-syscall-ensure-saved-x0-is-kept-in-sync-with-tracer-updates.patch b/queue-6.12/arm64-syscall-ensure-saved-x0-is-kept-in-sync-with-tracer-updates.patch new file mode 100644 index 0000000000..39e74b8024 --- /dev/null +++ b/queue-6.12/arm64-syscall-ensure-saved-x0-is-kept-in-sync-with-tracer-updates.patch @@ -0,0 +1,104 @@ +From e057b94772328221405b067c3a85fe479b915dc8 Mon Sep 17 00:00:00 2001 +From: Will Deacon +Date: Thu, 16 Jul 2026 13:06:39 +0100 +Subject: arm64: syscall: Ensure saved x0 is kept in-sync with tracer updates + +From: Will Deacon + +commit e057b94772328221405b067c3a85fe479b915dc8 upstream. + +When seccomp support was originally added to arm64 in a1ae65b21941 +("arm64: add seccomp support"), seccomp was erroneously called _before_ +the ptrace syscall-enter-stop and therefore the tracer could trivially +manipulate the syscall register state after the seccomp check had +passed. This was subsequently fixed in a5cd110cb836 ("arm64/ptrace: run +seccomp after ptrace") by moving the seccomp check after the tracer has +run. Unfortunately, a decade later, that fix has been reported to be +incomplete. + +On arm64, both the first argument to a syscall and its eventual return +value are allocated to register x0. In order to facilitate syscall +restarting and querying of syscall arguments on the syscall exit path, +the original value of x0 is stashed in 'struct pt_regs::orig_x0' early +during the syscall entry path and is returned for the first argument by +syscall_get_arguments(). Unlike 32-bit Arm, this stashed value is not +directly exposed via ptrace() and so changes to register x0 made by the +tracer on a syscall-enter-stop are not reflected in 'orig_x0'. This +means that seccomp, syscall tracepoints and audit can observe a stale +value for the register compared to the argument that will be observed by +the actual syscall. + +Re-sync 'orig_x0' from x0 on the syscall entry path following a +potential ptrace stop (i.e. PTRACE_EVENTMSG_SYSCALL_ENTRY or +SECCOMP_RET_TRACE). This behaviour is limited to native tasks (because +compat tasks expose 'orig_r0' to ptrace) where the syscall is not being +skipped (because x0 is updated to hold the return value of -ENOSYS in +that case). + +Cc: Kees Cook +Cc: Jinjie Ruan +Cc: Mark Rutland +Cc: stable@vger.kernel.org +Reported-by: Yiqi Sun +Link: https://lore.kernel.org/all/20260529065444.1336608-1-sunyiqixm@gmail.com/ +Suggested-by: Catalin Marinas +Fixes: a5cd110cb836 ("arm64/ptrace: run seccomp after ptrace") +Reviewed-by: Jinjie Ruan +Tested-by: Jinjie Ruan +Signed-off-by: Will Deacon +Signed-off-by: Greg Kroah-Hartman +--- + arch/arm64/kernel/ptrace.c | 29 +++++++++++++++++++++++++++++ + 1 file changed, 29 insertions(+) + +--- a/arch/arm64/kernel/ptrace.c ++++ b/arch/arm64/kernel/ptrace.c +@@ -2285,6 +2285,21 @@ static void report_syscall(struct pt_reg + } + } + ++static void update_syscall_orig_x0_after_ptrace(struct pt_regs *regs) ++{ ++ /* ++ * Keep orig_x0 authoritative so that seccomp (via ++ * syscall_get_arguments()), audit and the restart path all see the same ++ * first argument the syscall is dispatched with, even if it has been ++ * updated by a tracer. Skip this for NO_SYSCALL (set either by the user ++ * or the tracer), as regs[0] holds the return value (see the comment in ++ * el0_svc_common()) and can be unwound using syscall_rollback(). ++ * For compat tasks, orig_r0 is provided directly through GPR index 17. ++ */ ++ if (!is_compat_task() && regs->syscallno != NO_SYSCALL) ++ regs->orig_x0 = regs->regs[0]; ++} ++ + int syscall_trace_enter(struct pt_regs *regs) + { + unsigned long flags = read_thread_flags(); +@@ -2293,12 +2308,26 @@ int syscall_trace_enter(struct pt_regs * + report_syscall(regs, PTRACE_SYSCALL_ENTER); + if (flags & _TIF_SYSCALL_EMU) + return NO_SYSCALL; ++ ++ /* ++ * Ensure ptrace changes to x0 during a regular ++ * syscall-enter-stop (PTRACE_SYSCALL) are visible to ++ * subsequent seccomp checks, tracepoints and audit. ++ */ ++ update_syscall_orig_x0_after_ptrace(regs); + } + + /* Do the secure computing after ptrace; failures should be fast. */ + if (secure_computing() == -1) + return NO_SYSCALL; + ++ /* ++ * Ensure tracer changes to x0 during seccomp ptrace exit ++ * processing (SECCOMP_RET_TRACE) are visible to tracepoints and ++ * audit. ++ */ ++ update_syscall_orig_x0_after_ptrace(regs); ++ + if (test_thread_flag(TIF_SYSCALL_TRACEPOINT)) + trace_sys_enter(regs, regs->syscallno); + diff --git a/queue-6.12/cdrom-fix-stack-out-of-bounds-read-in-cdromvolctrl.patch b/queue-6.12/cdrom-fix-stack-out-of-bounds-read-in-cdromvolctrl.patch new file mode 100644 index 0000000000..bc61776ae2 --- /dev/null +++ b/queue-6.12/cdrom-fix-stack-out-of-bounds-read-in-cdromvolctrl.patch @@ -0,0 +1,54 @@ +From b27e195d4db8dea263050bdbeb11881b2999c9c6 Mon Sep 17 00:00:00 2001 +From: Xu Rao +Date: Mon, 20 Jul 2026 20:44:21 +0100 +Subject: cdrom: fix stack out-of-bounds read in CDROMVOLCTRL + +From: Xu Rao + +commit b27e195d4db8dea263050bdbeb11881b2999c9c6 upstream. + +mmc_ioctl_cdrom_volume() first reads the audio control mode page into a +32-byte stack buffer with cgc->buflen set to 24. If the device reports a +block descriptor, the function increases cgc->buflen to include that +descriptor and reads the page again. + +For CDROMVOLCTRL, the function then builds a MODE SELECT parameter list +by moving cgc->buffer forward by offset - 8 bytes. This drops the block +descriptor from the outgoing payload and leaves a new 8-byte mode +parameter header in front of the audio control page. However, cgc->buflen +is left unchanged. + +With a standard 8-byte block descriptor, cgc->buffer points at buffer + 8 +but cgc->buflen remains 32. cdrom_mode_select() therefore asks the low +level packet path to write 32 bytes from that adjusted pointer, reading 8 +bytes past the end of the 32-byte stack buffer. + +This is not hit by CDROMVOLREAD, and CDROMVOLCTRL only triggers it on +drives that return a non-zero block descriptor length, which helps explain +why it has gone unnoticed. The overread is also sent to the device as +extra MODE SELECT payload, so it may not produce an obvious local failure. + +Reduce cgc->buflen by the same amount as the buffer pointer adjustment so +the MODE SELECT transfer covers only the intended parameter list. + +Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2") +Cc: stable@vger.kernel.org +Signed-off-by: Xu Rao +Signed-off-by: Phillip Potter +Link: https://patch.msgid.link/20260720194421.1497-2-phil@philpotter.co.uk +Signed-off-by: Jens Axboe +Signed-off-by: Greg Kroah-Hartman +--- + drivers/cdrom/cdrom.c | 1 + + 1 file changed, 1 insertion(+) + +--- a/drivers/cdrom/cdrom.c ++++ b/drivers/cdrom/cdrom.c +@@ -3191,6 +3191,7 @@ static noinline int mmc_ioctl_cdrom_volu + + /* set volume */ + cgc->buffer = buffer + offset - 8; ++ cgc->buflen -= offset - 8; + memset(cgc->buffer, 0, 8); + return cdrom_mode_select(cdi, cgc); + } diff --git a/queue-6.12/comedi-comedi_parport-deal-with-premature-interrupt.patch b/queue-6.12/comedi-comedi_parport-deal-with-premature-interrupt.patch new file mode 100644 index 0000000000..0caf94be8d --- /dev/null +++ b/queue-6.12/comedi-comedi_parport-deal-with-premature-interrupt.patch @@ -0,0 +1,76 @@ +From 17221216ae8ce6a24e8a4e787382e3ebc81b88a8 Mon Sep 17 00:00:00 2001 +From: Ian Abbott +Date: Wed, 27 May 2026 13:51:03 +0100 +Subject: comedi: comedi_parport: deal with premature interrupt + +From: Ian Abbott + +commit 17221216ae8ce6a24e8a4e787382e3ebc81b88a8 upstream. + +Syzbot reported a general protection fault in +`comedi_get_is_subdevice_running()`, which was called from the interrupt +handler `parport_interrupt()` in the "comedi_parport" driver, but it +does not currently have a C reproducer for the problem. It's +probably due to a premature interrupt for one of two reasons: + +1. The driver sets up the interrupt handler before the comedi subdevices + used by the interrupt handler have been allocated, but does not + disable the interrupt in the parallel port's CTRL register first. +2. The driver uses a user-supplied I/O port base address which Syzbot + would have supplied, but it might not be backed by real parallel port + hardware. + +Change the initialization order in the driver's comedi "attach" handler +(`parport_attach()`) so that the hardware registers are initialized +before the interrupt handler is requested. This should prevent +premature interrupts occurring for real hardware. + +Also add a test to the interrupt handler to ensure the comedi device is +fully attached and return early if it isn't. + +Fixes: 241ab6ad7108e ("Staging: comedi: add comedi_parport driver") +Reported-by: syzbot+f24c3d5d316011bacc70@syzkaller.appspotmail.com +Cc: stable +Signed-off-by: Ian Abbott +Link: https://patch.msgid.link/20260527125104.96596-1-abbotti@mev.co.uk +Signed-off-by: Greg Kroah-Hartman +--- + drivers/comedi/drivers/comedi_parport.c | 13 ++++++++++--- + 1 file changed, 10 insertions(+), 3 deletions(-) + +--- a/drivers/comedi/drivers/comedi_parport.c ++++ b/drivers/comedi/drivers/comedi_parport.c +@@ -211,6 +211,13 @@ static irqreturn_t parport_interrupt(int + unsigned int ctrl; + unsigned short val = 0; + ++ /* ++ * Check device is fully attached. Device interrupts should have ++ * been disabled, but do this in case of bad hardware. ++ */ ++ if (!dev->attached) ++ return IRQ_NONE; ++ + ctrl = inb(dev->iobase + PARPORT_CTRL_REG); + if (!(ctrl & PARPORT_CTRL_IRQ_ENA)) + return IRQ_NONE; +@@ -231,6 +238,9 @@ static int parport_attach(struct comedi_ + if (ret) + return ret; + ++ outb(0, dev->iobase + PARPORT_DATA_REG); ++ outb(0, dev->iobase + PARPORT_CTRL_REG); ++ + if (it->options[1]) { + ret = request_irq(it->options[1], parport_interrupt, 0, + dev->board_name, dev); +@@ -286,9 +296,6 @@ static int parport_attach(struct comedi_ + s->cancel = parport_intr_cancel; + } + +- outb(0, dev->iobase + PARPORT_DATA_REG); +- outb(0, dev->iobase + PARPORT_CTRL_REG); +- + return 0; + } + diff --git a/queue-6.12/firmware-stratix10-svc-fix-memory-leaks-and-list-corruption-bugs.patch b/queue-6.12/firmware-stratix10-svc-fix-memory-leaks-and-list-corruption-bugs.patch new file mode 100644 index 0000000000..2218ff48ac --- /dev/null +++ b/queue-6.12/firmware-stratix10-svc-fix-memory-leaks-and-list-corruption-bugs.patch @@ -0,0 +1,65 @@ +From 9119ceb76e987c2ec2b549ea100e3268ce3a1c7c Mon Sep 17 00:00:00 2001 +From: Tze Yee Ng +Date: Wed, 24 Jun 2026 03:06:35 -0700 +Subject: firmware: stratix10-svc: fix memory leaks and list corruption bugs + +From: Tze Yee Ng + +commit 9119ceb76e987c2ec2b549ea100e3268ce3a1c7c upstream. + +Fix a memory leak when gen_pool_alloc() fails by freeing pmem on the error +path. Switch pmem allocation from devm_kzalloc() to kzalloc() with +explicit kfree() in the free path to match its list-managed lifetime. +Remove the erroneous list_del(&svc_data_mem) which corrupted the list head +on failed lookups. + +Fixes: 7ca5ce896524 ("firmware: add Intel Stratix10 service layer driver") +Cc: stable@vger.kernel.org # 5.0+ +Signed-off-by: Tze Yee Ng +Signed-off-by: Dinh Nguyen +Signed-off-by: Greg Kroah-Hartman +--- + drivers/firmware/stratix10-svc.c | 10 ++++++---- + 1 file changed, 6 insertions(+), 4 deletions(-) + +--- a/drivers/firmware/stratix10-svc.c ++++ b/drivers/firmware/stratix10-svc.c +@@ -1083,14 +1083,16 @@ void *stratix10_svc_allocate_memory(stru + struct gen_pool *genpool = chan->ctrl->genpool; + size_t s = roundup(size, 1 << genpool->min_alloc_order); + +- pmem = devm_kzalloc(chan->ctrl->dev, sizeof(*pmem), GFP_KERNEL); ++ pmem = kzalloc_obj(*pmem); + if (!pmem) + return ERR_PTR(-ENOMEM); + + guard(mutex)(&svc_mem_lock); + va = gen_pool_alloc(genpool, s); +- if (!va) ++ if (!va) { ++ kfree(pmem); + return ERR_PTR(-ENOMEM); ++ } + + memset((void *)va, 0, s); + pa = gen_pool_virt_to_phys(genpool, va); +@@ -1116,6 +1118,7 @@ EXPORT_SYMBOL_GPL(stratix10_svc_allocate + void stratix10_svc_free_memory(struct stratix10_svc_chan *chan, void *kaddr) + { + struct stratix10_svc_data_mem *pmem; ++ + guard(mutex)(&svc_mem_lock); + + list_for_each_entry(pmem, &svc_data_mem, node) +@@ -1124,10 +1127,9 @@ void stratix10_svc_free_memory(struct st + (unsigned long)kaddr, pmem->size); + pmem->vaddr = NULL; + list_del(&pmem->node); ++ kfree(pmem); + return; + } +- +- list_del(&svc_data_mem); + } + EXPORT_SYMBOL_GPL(stratix10_svc_free_memory); + diff --git a/queue-6.12/intel_th-fix-msc-output-device-reference-leak.patch b/queue-6.12/intel_th-fix-msc-output-device-reference-leak.patch new file mode 100644 index 0000000000..8c47d95012 --- /dev/null +++ b/queue-6.12/intel_th-fix-msc-output-device-reference-leak.patch @@ -0,0 +1,74 @@ +From 761b785a0cfbce43761227bc42a7f984f31f8921 Mon Sep 17 00:00:00 2001 +From: Guangshuo Li +Date: Wed, 15 Jul 2026 15:08:51 +0800 +Subject: intel_th: fix MSC output device reference leak + +From: Guangshuo Li + +commit 761b785a0cfbce43761227bc42a7f984f31f8921 upstream. + +intel_th_output_open() looks up the output device with +bus_find_device_by_devt(), which returns the device with a reference that +must be dropped after use. + +commit 95fc36a234da ("intel_th: fix device leak on output open()") +attempted to drop the reference from intel_th_output_release(). However, +a successful open replaces file->f_op with the output driver file +operations before returning, so close runs the output driver release +callback instead. + +For MSC outputs, close runs intel_th_msc_release(), which only removes +the per-file iterator and does not drop the device reference taken by +intel_th_output_open(). Consequently, every successful MSC output open +leaks one device reference. + +Drop the device reference from intel_th_msc_release(), which is the +release path actually used for MSC output files. Remove the now-unused +intel_th_output_release() callback from intel_th_output_fops. + +Fixes: 95fc36a234da ("intel_th: fix device leak on output open()") +Cc: stable +Signed-off-by: Guangshuo Li +Reviewed-by: Johan Hovold +Link: https://patch.msgid.link/20260715070851.2077965-1-lgs201920130244@gmail.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Greg Kroah-Hartman +--- + drivers/hwtracing/intel_th/core.c | 10 ---------- + drivers/hwtracing/intel_th/msu.c | 2 ++ + 2 files changed, 2 insertions(+), 10 deletions(-) + +--- a/drivers/hwtracing/intel_th/core.c ++++ b/drivers/hwtracing/intel_th/core.c +@@ -843,18 +843,8 @@ out_put_device: + return err; + } + +-static int intel_th_output_release(struct inode *inode, struct file *file) +-{ +- struct intel_th_device *thdev = file->private_data; +- +- put_device(&thdev->dev); +- +- return 0; +-} +- + static const struct file_operations intel_th_output_fops = { + .open = intel_th_output_open, +- .release = intel_th_output_release, + .llseek = noop_llseek, + }; + +--- a/drivers/hwtracing/intel_th/msu.c ++++ b/drivers/hwtracing/intel_th/msu.c +@@ -1482,8 +1482,10 @@ static int intel_th_msc_release(struct i + { + struct msc_iter *iter = file->private_data; + struct msc *msc = iter->msc; ++ struct intel_th_device *thdev = msc->thdev; + + msc_iter_remove(iter, msc); ++ put_device(&thdev->dev); + + return 0; + } diff --git a/queue-6.12/loongarch-fix-oops-during-single-step-debugging.patch b/queue-6.12/loongarch-fix-oops-during-single-step-debugging.patch new file mode 100644 index 0000000000..f5f57ddc04 --- /dev/null +++ b/queue-6.12/loongarch-fix-oops-during-single-step-debugging.patch @@ -0,0 +1,43 @@ +From 73555fdab5e1e4f24ca000c41a616b34edf4b55d Mon Sep 17 00:00:00 2001 +From: Haoran Jiang +Date: Thu, 23 Jul 2026 22:27:30 +0800 +Subject: LoongArch: Fix oops during single-step debugging + +From: Haoran Jiang + +commit 73555fdab5e1e4f24ca000c41a616b34edf4b55d upstream. + +When entering KDB via a breakpoint and then performing single-step +debugging, an oops is triggered. Now during single-step debugging, +kdb_local() expects the reason to be KDB_REASON_SSTEP, but it is +actually KDB_REASON_OOPS. In kdb_stub(), when determining the reason, +the ex_vector for single-step should be 0, as already implemented on +other architectures such as arm64 and riscv. + +Before the patch: +[112]kdb> ss + +Entering kdb (current=0x900020009f520000, pid 10661) on +processor 112 Oops: (null) +due to oops @ 0x90000000005b57a4 + +Cc: stable@vger.kernel.org +Signed-off-by: Haoran Jiang +Signed-off-by: Huacai Chen +Signed-off-by: Greg Kroah-Hartman +--- + arch/loongarch/kernel/kgdb.c | 3 ++- + 1 file changed, 2 insertions(+), 1 deletion(-) + +--- a/arch/loongarch/kernel/kgdb.c ++++ b/arch/loongarch/kernel/kgdb.c +@@ -252,7 +252,8 @@ static int kgdb_loongarch_notify(struct + if (atomic_read(&kgdb_active) != -1) + kgdb_nmicallback(smp_processor_id(), regs); + +- if (kgdb_handle_exception(args->trapnr, args->signr, cmd, regs)) ++ if (kgdb_handle_exception(regs->csr_era == stepped_address ? 0 : args->trapnr, ++ args->signr, cmd, regs)) + return NOTIFY_DONE; + + if (atomic_read(&kgdb_setting_breakpoint)) diff --git a/queue-6.12/loongarch-move-jump_label_init-before-parse_early_param.patch b/queue-6.12/loongarch-move-jump_label_init-before-parse_early_param.patch new file mode 100644 index 0000000000..6a6f7fb623 --- /dev/null +++ b/queue-6.12/loongarch-move-jump_label_init-before-parse_early_param.patch @@ -0,0 +1,48 @@ +From ea68d444a658783234a06f05414e41cf93a18fb2 Mon Sep 17 00:00:00 2001 +From: Kanglong Wang +Date: Thu, 23 Jul 2026 22:27:29 +0800 +Subject: LoongArch: Move jump_label_init() before parse_early_param() + +From: Kanglong Wang + +commit ea68d444a658783234a06f05414e41cf93a18fb2 upstream. + +When enabling both CONFIG_MEM_ALLOC_PROFILING=y and +CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT=y, then diabling memory +profiling by adding the boot parameter 'sysctl.vm.mem_profiling=0' will +cause the kernel failed to boot. + +After analysis, this is because jump_label_init() must be called before +parse_early_param(), the early param handlers may modify static keys by +static_branch_enable/disable(). + +Fix this by moving jump_label_init() to before parse_early_param(). The +solution is similar to other architectures. + +Cc: +Signed-off-by: Kanglong Wang +Signed-off-by: Huacai Chen +Signed-off-by: Greg Kroah-Hartman +--- + arch/loongarch/kernel/setup.c | 3 +-- + 1 file changed, 1 insertion(+), 2 deletions(-) + +--- a/arch/loongarch/kernel/setup.c ++++ b/arch/loongarch/kernel/setup.c +@@ -610,6 +610,7 @@ void __init setup_arch(char **cmdline_p) + memblock_init(); + pagetable_init(); + bootcmdline_init(cmdline_p); ++ jump_label_init(); /* Initialise the static keys for early params */ + parse_early_param(); + reserve_initrd_mem(); + +@@ -617,8 +618,6 @@ void __init setup_arch(char **cmdline_p) + arch_mem_init(cmdline_p); + + resource_init(); +- jump_label_init(); /* Initialise the static keys for paravirtualization */ +- + #ifdef CONFIG_SMP + plat_smp_setup(); + prefill_possible_map(); diff --git a/queue-6.12/loongarch-retrieve-cpu-package-id-from-pptt-when-available.patch b/queue-6.12/loongarch-retrieve-cpu-package-id-from-pptt-when-available.patch new file mode 100644 index 0000000000..2bea9b9b5f --- /dev/null +++ b/queue-6.12/loongarch-retrieve-cpu-package-id-from-pptt-when-available.patch @@ -0,0 +1,127 @@ +From 4e8f58620f6717f72f3d88a2c8f25c0c656d0ba7 Mon Sep 17 00:00:00 2001 +From: Rong Bao +Date: Thu, 23 Jul 2026 22:27:29 +0800 +Subject: LoongArch: Retrieve CPU package ID from PPTT when available + +From: Rong Bao + +commit 4e8f58620f6717f72f3d88a2c8f25c0c656d0ba7 upstream. + +Currently, the LoongArch CPU topology initialization code calculates +each core's package ID by dividing its physical ID by loongson_sysconf. +cores_per_package. This relies on the assumption that cores_per_package +counts in the same domain as physical IDs. + +On Loongson-3B6000 (XB612B0V_1.2), cores_per_package matches the visible +core count -- 24 in this case. However, the physical IDs range from 0 to +31 in a noncontinuous fashion: + + $ cat /proc/cpuinfo | grep -i -F 'global_id' + global_id : 0 + global_id : 1 + global_id : 4 + global_id : 5 + global_id : 6 + global_id : 7 + global_id : 8 + global_id : 9 + global_id : 10 + global_id : 11 + global_id : 14 + global_id : 15 + global_id : 16 + global_id : 17 + global_id : 20 + global_id : 21 + global_id : 22 + global_id : 23 + global_id : 26 + global_id : 27 + global_id : 28 + global_id : 29 + global_id : 30 + global_id : 31 + +Retrieve the exact package ID from ACPI PPTT when available, in the same +style as retrieving the core ID and thread ID in parse_acpi_topology(). +Use this information in loongson_init_secondary() when the PPTT readout +is successful. The original division logic is kept as a fallback. + +Meanwhile, since some existing code paths like loongson3_cpufreq expect +a continuous integer sequence of package IDs in [0, MAX_PACKAGES) when +retrieving from cpu_data[], here we also canonicalize the package ID to +be filled in parse_acpi_topology() to meet such an expectation. + +Cc: stable@vger.kernel.org +Tested-by: Mingcong Bai +Co-developed-by: Xi Ruoyao +Signed-off-by: Xi Ruoyao +Signed-off-by: Rong Bao +Signed-off-by: Huacai Chen +Signed-off-by: Greg Kroah-Hartman +--- + arch/loongarch/kernel/acpi.c | 27 ++++++++++++++++++++++++++- + arch/loongarch/kernel/smp.c | 4 ++-- + 2 files changed, 28 insertions(+), 3 deletions(-) + +--- a/arch/loongarch/kernel/acpi.c ++++ b/arch/loongarch/kernel/acpi.c +@@ -200,10 +200,12 @@ static void __init acpi_process_madt(voi + } + + int pptt_enabled; ++static int acpi_nr_packages; ++static int acpi_package_ids[MAX_PACKAGES]; + + int __init parse_acpi_topology(void) + { +- int cpu, topology_id; ++ int i, cpu, topology_id; + + for_each_possible_cpu(cpu) { + topology_id = find_acpi_cpu_topology(cpu, 0); +@@ -221,6 +223,29 @@ int __init parse_acpi_topology(void) + + cpu_data[cpu].core = topology_id; + } ++ ++ topology_id = find_acpi_cpu_topology_package(cpu); ++ if (topology_id < 0) { ++ pr_warn("Invalid BIOS PPTT\n"); ++ return -ENOENT; ++ } ++ ++ for (i = 0; i < acpi_nr_packages; i++) ++ if (acpi_package_ids[i] == topology_id) ++ break; ++ ++ if (i == acpi_nr_packages) ++ acpi_package_ids[acpi_nr_packages++] = topology_id; ++ ++ cpu_data[cpu].package = topology_id; ++ } ++ ++ for_each_possible_cpu(cpu) { ++ for (i = 0; i < acpi_nr_packages; i++) ++ if (cpu_data[cpu].package == acpi_package_ids[i]) { ++ cpu_data[cpu].package = i; /* Canonicalize */ ++ break; ++ } + } + + pptt_enabled = 1; +--- a/arch/loongarch/kernel/smp.c ++++ b/arch/loongarch/kernel/smp.c +@@ -377,10 +377,10 @@ void loongson_init_secondary(void) + numa_add_cpu(cpu); + #endif + per_cpu(cpu_state, cpu) = CPU_ONLINE; +- cpu_data[cpu].package = +- cpu_logical_map(cpu) / loongson_sysconf.cores_per_package; + cpu_data[cpu].core = pptt_enabled ? cpu_data[cpu].core : + cpu_logical_map(cpu) % loongson_sysconf.cores_per_package; ++ cpu_data[cpu].package = pptt_enabled ? cpu_data[cpu].package : ++ cpu_logical_map(cpu) / loongson_sysconf.cores_per_package; + cpu_data[cpu].global_id = cpu_logical_map(cpu); + } + diff --git a/queue-6.12/mei-bus-access-mei_device-under-device_lock-on-cleanup.patch b/queue-6.12/mei-bus-access-mei_device-under-device_lock-on-cleanup.patch new file mode 100644 index 0000000000..0d4d0c166f --- /dev/null +++ b/queue-6.12/mei-bus-access-mei_device-under-device_lock-on-cleanup.patch @@ -0,0 +1,67 @@ +From f112ea910e554d58b4b39a4492b7d302f0f4204f Mon Sep 17 00:00:00 2001 +From: Alexander Usyskin +Date: Sun, 5 Jul 2026 18:12:59 +0300 +Subject: mei: bus: access mei_device under device_lock on cleanup + +From: Alexander Usyskin + +commit f112ea910e554d58b4b39a4492b7d302f0f4204f upstream. + +Fix couple of problems in mei_cl_bus_dev_release(): + +mei_cl_flush_queues() is running without lock. +bus->file_list access after mei_dev_bus_put(bus) can become a +use-after-free if this was the last reference to bus. + +Protect queues cleanup and WARN traversal by device lock there +to avoid the concurrent access problems. +Move WARN traversal before mei_dev_bus_put(bus). + +This file uses bus variable name for mei_device, adjust +code of mei_cl_bus_dev_release() to use bus variable too. + +Cc: stable +Fixes: 35e8a426b16a ("mei: bus: Check for still connected devices in mei_cl_bus_dev_release()") +Reviewed-by: Menachem Adin +Signed-off-by: Alexander Usyskin +Link: https://patch.msgid.link/20260705151259.3054795-1-alexander.usyskin@intel.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Greg Kroah-Hartman +--- + drivers/misc/mei/bus.c | 16 +++++++++------- + 1 file changed, 9 insertions(+), 7 deletions(-) + +--- a/drivers/misc/mei/bus.c ++++ b/drivers/misc/mei/bus.c +@@ -4,6 +4,7 @@ + * Intel Management Engine Interface (Intel MEI) Linux driver + */ + ++#include + #include + #include + #include +@@ -1353,15 +1354,16 @@ static void mei_dev_bus_put(struct mei_d + static void mei_cl_bus_dev_release(struct device *dev) + { + struct mei_cl_device *cldev = to_mei_cl_device(dev); +- struct mei_device *mdev = cldev->cl->dev; ++ struct mei_device *bus = cldev->bus; + struct mei_cl *cl; + +- mei_cl_flush_queues(cldev->cl, NULL); +- mei_me_cl_put(cldev->me_cl); +- mei_dev_bus_put(cldev->bus); +- +- list_for_each_entry(cl, &mdev->file_list, link) +- WARN_ON(cl == cldev->cl); ++ scoped_guard(mutex, &bus->device_lock) { ++ mei_cl_flush_queues(cldev->cl, NULL); ++ mei_me_cl_put(cldev->me_cl); ++ list_for_each_entry(cl, &bus->file_list, link) ++ WARN_ON(cl == cldev->cl); ++ } ++ mei_dev_bus_put(bus); + + kfree(cldev->cl); + kfree(cldev); diff --git a/queue-6.12/misc-nsm-only-unlock-nsm_dev-on-post-lock-error-paths.patch b/queue-6.12/misc-nsm-only-unlock-nsm_dev-on-post-lock-error-paths.patch new file mode 100644 index 0000000000..7c8c40f9a2 --- /dev/null +++ b/queue-6.12/misc-nsm-only-unlock-nsm_dev-on-post-lock-error-paths.patch @@ -0,0 +1,51 @@ +From ce1fed11d18e163baf7f875152a33bf80f625c1a Mon Sep 17 00:00:00 2001 +From: Runyu Xiao +Date: Wed, 17 Jun 2026 22:53:50 +0800 +Subject: misc: nsm: only unlock nsm_dev on post-lock error paths + +From: Runyu Xiao + +commit ce1fed11d18e163baf7f875152a33bf80f625c1a upstream. + +nsm_dev_ioctl() jumps to the common out label even when the initial +copy_from_user() fails before nsm->lock has been taken. The error path +then blindly unlocks a mutex that was never acquired. + +This issue was found by our static analysis tool and then manually +reviewed against the current tree. + +The grounded PoC kept the miscdevice ioctl entry and the pre-lock +copy_from_user(&raw, argp, _IOC_SIZE(cmd)) failure path by issuing +NSM_IOCTL_RAW with an invalid user pointer. That failure reaches the +shared out label before mutex_lock(&nsm->lock). Lockdep reported: + + WARNING: bad unlock balance detected! + exploit/193 is trying to release lock (&global_nsm.lock) at: + nsm_dev_ioctl+0x5f/0xcf [vuln_msv] + but there are no more locks to release! + no locks held by exploit/193. + +Return immediately on the pre-lock copy_from_user() failure and keep the +common unlock label for the post-lock paths only. + +Fixes: b9873755a6c8 ("misc: Add Nitro Secure Module driver") +Cc: stable +Signed-off-by: Runyu Xiao +Reviewed-by: Alexander Graf +Link: https://patch.msgid.link/20260617145350.513875-1-runyu.xiao@seu.edu.cn +Signed-off-by: Greg Kroah-Hartman +--- + drivers/misc/nsm.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +--- a/drivers/misc/nsm.c ++++ b/drivers/misc/nsm.c +@@ -367,7 +367,7 @@ static long nsm_dev_ioctl(struct file *f + /* Copy user argument struct to kernel argument struct */ + r = -EFAULT; + if (copy_from_user(&raw, argp, _IOC_SIZE(cmd))) +- goto out; ++ return r; + + mutex_lock(&nsm->lock); + diff --git a/queue-6.12/misc-nsm-pin-the-module-while-the-device-is-open.patch b/queue-6.12/misc-nsm-pin-the-module-while-the-device-is-open.patch new file mode 100644 index 0000000000..bcbbbe6960 --- /dev/null +++ b/queue-6.12/misc-nsm-pin-the-module-while-the-device-is-open.patch @@ -0,0 +1,41 @@ +From 3b231f1e9990f4c21220d0a69733ce2105891ff9 Mon Sep 17 00:00:00 2001 +From: Xu Rao +Date: Mon, 13 Jul 2026 13:55:23 +0800 +Subject: misc: nsm: pin the module while the device is open + +From: Xu Rao + +commit 3b231f1e9990f4c21220d0a69733ce2105891ff9 upstream. + +misc_open() installs a misc driver's file operations with fops_get(), +which pins file_operations::owner before replacing the file's f_op. The +NSM misc device leaves nsm_dev_fops.owner unset, so opening /dev/nsm does +not take a module reference on the nsm driver. + +If the driver is built as a module, an open file descriptor can therefore +survive rmmod of the module that provides its ioctl callbacks. A later +ioctl through that descriptor can call into unloaded module text. + +Set nsm_dev_fops.owner to THIS_MODULE so the misc core holds the module +while any /dev/nsm file descriptor is open, matching the lifetime +expectation for the installed file operations. + +Fixes: b9873755a6c8 ("misc: Add Nitro Secure Module driver") +Cc: stable +Signed-off-by: Xu Rao +Link: https://patch.msgid.link/BE6951D13B5E5513+20260713055523.3193089-1-raoxu@uniontech.com +Signed-off-by: Greg Kroah-Hartman +--- + drivers/misc/nsm.c | 1 + + 1 file changed, 1 insertion(+) + +--- a/drivers/misc/nsm.c ++++ b/drivers/misc/nsm.c +@@ -413,6 +413,7 @@ static int nsm_device_init_vq(struct vir + } + + static const struct file_operations nsm_dev_fops = { ++ .owner = THIS_MODULE, + .unlocked_ioctl = nsm_dev_ioctl, + .compat_ioctl = compat_ptr_ioctl, + }; diff --git a/queue-6.12/mptcp-decrement-subflows-counter-on-failed-passive-join.patch b/queue-6.12/mptcp-decrement-subflows-counter-on-failed-passive-join.patch new file mode 100644 index 0000000000..bb13360b04 --- /dev/null +++ b/queue-6.12/mptcp-decrement-subflows-counter-on-failed-passive-join.patch @@ -0,0 +1,40 @@ +From f3ca0ee2cc308e33896536789cbc5f3a12ca7b30 Mon Sep 17 00:00:00 2001 +From: Chenguang Zhao +Date: Wed, 22 Jul 2026 00:14:38 +0200 +Subject: mptcp: decrement subflows counter on failed passive join + +From: Chenguang Zhao + +commit f3ca0ee2cc308e33896536789cbc5f3a12ca7b30 upstream. + +mptcp_pm_allow_new_subflow() increments extra_subflows before +__mptcp_finish_join() on the passive MP_JOIN path. + +In case of race conditions, the subflow is dropped without calling +mptcp_close_ssk(), so the counter is not rolled back. + +Call mptcp_pm_close_subflow() when the join completion fails to +decrement the subflows counter. + +Fixes: 10f6d46c943d ("mptcp: fix race between MP_JOIN and close") +Cc: stable@vger.kernel.org +Signed-off-by: Chenguang Zhao +Reviewed-by: Matthieu Baerts (NGI0) +Signed-off-by: Matthieu Baerts (NGI0) +Link: https://patch.msgid.link/20260722-net-mptcp-misc-fixes-7-2-rc5-v1-1-6fb595bc86ef@kernel.org +Signed-off-by: Jakub Kicinski +Signed-off-by: Greg Kroah-Hartman +--- + net/mptcp/protocol.c | 1 + + 1 file changed, 1 insertion(+) + +--- a/net/mptcp/protocol.c ++++ b/net/mptcp/protocol.c +@@ -3825,6 +3825,7 @@ bool mptcp_finish_join(struct sock *ssk) + mptcp_data_unlock(parent); + + if (!ret) { ++ mptcp_pm_close_subflow(msk); + err_prohibited: + subflow->reset_reason = MPTCP_RST_EPROHIBIT; + return false; diff --git a/queue-6.12/mptcp-only-set-data_fin-when-a-mapping-is-present.patch b/queue-6.12/mptcp-only-set-data_fin-when-a-mapping-is-present.patch new file mode 100644 index 0000000000..abcb0f160d --- /dev/null +++ b/queue-6.12/mptcp-only-set-data_fin-when-a-mapping-is-present.patch @@ -0,0 +1,89 @@ +From b2ff91b752b0d85e8815e7f44fd85205c4268094 Mon Sep 17 00:00:00 2001 +From: Michael Bommarito +Date: Thu, 9 Jul 2026 15:19:25 -0400 +Subject: mptcp: only set DATA_FIN when a mapping is present + +From: Michael Bommarito + +commit b2ff91b752b0d85e8815e7f44fd85205c4268094 upstream. + +mptcp_get_options() clears only the status group of struct +mptcp_options_received; data_seq, subflow_seq and data_len are filled in +by mptcp_parse_option() exclusively inside the DSS mapping block, which +runs only when the DSS M (mapping present) bit is set. + +A peer can send a DSS option with the DATA_FIN flag set but the mapping +bit clear. The parser then records mp_opt->data_fin while leaving +data_len and data_seq uninitialized. For a zero-length segment +mptcp_incoming_options() evaluates + + if (mp_opt.data_fin && mp_opt.data_len == 1 && + mptcp_update_rcv_data_fin(msk, mp_opt.data_seq, mp_opt.dsn64)) + +which reads the uninitialized data_len and data_seq; KMSAN reports an +uninit-value in mptcp_incoming_options(). The stale data_seq can also be +fed into the receive-side DATA_FIN sequence tracking. + +Record the DATA_FIN flag only when the DSS option carries a mapping, so +data_fin is never set without data_seq and data_len also being present. +data_fin is part of the status group that mptcp_get_options() clears up +front, so on the no-map path it stays zero and the zero-length DATA_FIN +branch is simply skipped. A DATA_FIN is always transmitted together with +a mapping (mptcp_write_data_fin() sets use_map along with data_seq and +data_len), so legitimate DATA_FIN handling is unaffected. + +Move the pr_debug() that logs the parsed DSS flags below the mapping +block, so it reports the final data_fin value instead of the stale one +it would otherwise print before the assignment. + +Fixes: 43b54c6ee382 ("mptcp: Use full MPTCP-level disconnect state machine") +Suggested-by: Paolo Abeni +Cc: stable@vger.kernel.org +Signed-off-by: Michael Bommarito +Reviewed-by: Matthieu Baerts (NGI0) +Link: https://patch.msgid.link/20260709191925.2811195-1-michael.bommarito@gmail.com +Signed-off-by: Jakub Kicinski +Signed-off-by: Greg Kroah-Hartman +--- + net/mptcp/options.c | 12 ++++++------ + 1 file changed, 6 insertions(+), 6 deletions(-) + +--- a/net/mptcp/options.c ++++ b/net/mptcp/options.c +@@ -157,17 +157,11 @@ static void mptcp_parse_option(const str + ptr++; + + flags = (*ptr++) & MPTCP_DSS_FLAG_MASK; +- mp_opt->data_fin = (flags & MPTCP_DSS_DATA_FIN) != 0; + mp_opt->dsn64 = (flags & MPTCP_DSS_DSN64) != 0; + mp_opt->use_map = (flags & MPTCP_DSS_HAS_MAP) != 0; + mp_opt->ack64 = (flags & MPTCP_DSS_ACK64) != 0; + mp_opt->use_ack = (flags & MPTCP_DSS_HAS_ACK); + +- pr_debug("data_fin=%d dsn64=%d use_map=%d ack64=%d use_ack=%d\n", +- mp_opt->data_fin, mp_opt->dsn64, +- mp_opt->use_map, mp_opt->ack64, +- mp_opt->use_ack); +- + expected_opsize = TCPOLEN_MPTCP_DSS_BASE; + + if (mp_opt->use_ack) { +@@ -178,12 +172,18 @@ static void mptcp_parse_option(const str + } + + if (mp_opt->use_map) { ++ mp_opt->data_fin = (flags & MPTCP_DSS_DATA_FIN) != 0; + if (mp_opt->dsn64) + expected_opsize += TCPOLEN_MPTCP_DSS_MAP64; + else + expected_opsize += TCPOLEN_MPTCP_DSS_MAP32; + } + ++ pr_debug("data_fin=%d dsn64=%d use_map=%d ack64=%d use_ack=%d\n", ++ mp_opt->data_fin, mp_opt->dsn64, ++ mp_opt->use_map, mp_opt->ack64, ++ mp_opt->use_ack); ++ + /* Always parse any csum presence combination, we will enforce + * RFC 8684 Section 3.3.0 checks later in subflow_data_ready + */ diff --git a/queue-6.12/objtool-rust-add-one-more-noreturn-rust-function-for-rust-1.99.0.patch b/queue-6.12/objtool-rust-add-one-more-noreturn-rust-function-for-rust-1.99.0.patch new file mode 100644 index 0000000000..90b9eea533 --- /dev/null +++ b/queue-6.12/objtool-rust-add-one-more-noreturn-rust-function-for-rust-1.99.0.patch @@ -0,0 +1,51 @@ +From 5a81c35c3b18cd59ded56171a6a9f643b92a6759 Mon Sep 17 00:00:00 2001 +From: Miguel Ojeda +Date: Fri, 10 Jul 2026 19:32:52 +0200 +Subject: objtool/rust: add one more `noreturn` Rust function for Rust 1.99.0 + +From: Miguel Ojeda + +commit 5a81c35c3b18cd59ded56171a6a9f643b92a6759 upstream. + +Starting with Rust 1.99.0 (expected 2026-10-01), under +`CONFIG_RUST_DEBUG_ASSERTIONS=y`, `objtool` may report: + + rust/kernel.o: warning: objtool: _R..._6kernel12module_param9set_paramaEB4_() + falls through to next function _R..._6kernel12module_param9set_paramhEB4_() + +(and many others) due to calls to the `noreturn` symbol [1]: + + core::panicking::panic_null_reference_constructed + +Thus add the mangled one to the list so that `objtool` knows it is +actually `noreturn`. + +See commit 56d680dd23c3 ("objtool/rust: list `noreturn` Rust functions") +for more details. + +Cc: stable@vger.kernel.org # Needed in 6.12.y and later (Rust is pinned in older LTSs). +Cc: Josh Poimboeuf +Cc: Peter Zijlstra +Cc: Petr Pavlu +Link: https://github.com/rust-lang/rust/pull/158796 [1] +Reported-by: Alice Ryhl +Closes: https://lore.kernel.org/rust-for-linux/alEBInX9gD1M5NAr@google.com/ +Reviewed-by: Alice Ryhl +Tested-by: Alice Ryhl +Link: https://patch.msgid.link/20260710173252.191781-1-ojeda@kernel.org +Signed-off-by: Miguel Ojeda +Signed-off-by: Greg Kroah-Hartman +--- + tools/objtool/check.c | 1 + + 1 file changed, 1 insertion(+) + +--- a/tools/objtool/check.c ++++ b/tools/objtool/check.c +@@ -220,6 +220,7 @@ static bool is_rust_noreturn(const struc + str_ends_with(func->name, "_4core9panicking18panic_nounwind_fmt") || + str_ends_with(func->name, "_4core9panicking19assert_failed_inner") || + str_ends_with(func->name, "_4core9panicking30panic_null_pointer_dereference") || ++ str_ends_with(func->name, "_4core9panicking32panic_null_reference_constructed") || + str_ends_with(func->name, "_4core9panicking36panic_misaligned_pointer_dereference") || + str_ends_with(func->name, "_7___rustc17rust_begin_unwind") || + strstr(func->name, "_4core9panicking13assert_failed") || diff --git a/queue-6.12/revert-arm64-syscall-ensure-saved-x0-is-kept-in-sync-with-tracer-updates.patch b/queue-6.12/revert-arm64-syscall-ensure-saved-x0-is-kept-in-sync-with-tracer-updates.patch new file mode 100644 index 0000000000..f53b5d44ef --- /dev/null +++ b/queue-6.12/revert-arm64-syscall-ensure-saved-x0-is-kept-in-sync-with-tracer-updates.patch @@ -0,0 +1,81 @@ +From 26b483d52417253d88a3a01262ac85914a7aec8e Mon Sep 17 00:00:00 2001 +From: Will Deacon +Date: Fri, 17 Jul 2026 17:25:58 +0100 +Subject: Revert "arm64: syscall: Ensure saved x0 is kept in-sync with tracer updates" + +From: Will Deacon + +commit 26b483d52417253d88a3a01262ac85914a7aec8e upstream. + +This reverts commit e057b94772328221405b067c3a85fe479b915dc8. + +Sashiko points out that updating 'orig_x0' after secure_computing() +has returned is too late to handle the case where a seccomp filter is +re-evaluated after initially returning SECCOMP_RET_TRACE. This means +that a tracer can manipulate the first argument of the syscall behind +seccomp's back. + +For now, revert the initial fix and we'll have another crack at it soon. +Since the incorrect fix was cc'd to stable, do the same here with an +appropriate fixes tag. + +Cc: stable@vger.kernel.org +Fixes: e057b9477232 ("arm64: syscall: Ensure saved x0 is kept in-sync with tracer updates") +Link: https://sashiko.dev/#/patchset/20260716120640.6590-1-will@kernel.org +Signed-off-by: Will Deacon +Signed-off-by: Greg Kroah-Hartman +--- + arch/arm64/kernel/ptrace.c | 29 ----------------------------- + 1 file changed, 29 deletions(-) + +--- a/arch/arm64/kernel/ptrace.c ++++ b/arch/arm64/kernel/ptrace.c +@@ -2285,21 +2285,6 @@ static void report_syscall(struct pt_reg + } + } + +-static void update_syscall_orig_x0_after_ptrace(struct pt_regs *regs) +-{ +- /* +- * Keep orig_x0 authoritative so that seccomp (via +- * syscall_get_arguments()), audit and the restart path all see the same +- * first argument the syscall is dispatched with, even if it has been +- * updated by a tracer. Skip this for NO_SYSCALL (set either by the user +- * or the tracer), as regs[0] holds the return value (see the comment in +- * el0_svc_common()) and can be unwound using syscall_rollback(). +- * For compat tasks, orig_r0 is provided directly through GPR index 17. +- */ +- if (!is_compat_task() && regs->syscallno != NO_SYSCALL) +- regs->orig_x0 = regs->regs[0]; +-} +- + int syscall_trace_enter(struct pt_regs *regs) + { + unsigned long flags = read_thread_flags(); +@@ -2308,26 +2293,12 @@ int syscall_trace_enter(struct pt_regs * + report_syscall(regs, PTRACE_SYSCALL_ENTER); + if (flags & _TIF_SYSCALL_EMU) + return NO_SYSCALL; +- +- /* +- * Ensure ptrace changes to x0 during a regular +- * syscall-enter-stop (PTRACE_SYSCALL) are visible to +- * subsequent seccomp checks, tracepoints and audit. +- */ +- update_syscall_orig_x0_after_ptrace(regs); + } + + /* Do the secure computing after ptrace; failures should be fast. */ + if (secure_computing() == -1) + return NO_SYSCALL; + +- /* +- * Ensure tracer changes to x0 during seccomp ptrace exit +- * processing (SECCOMP_RET_TRACE) are visible to tracepoints and +- * audit. +- */ +- update_syscall_orig_x0_after_ptrace(regs); +- + if (test_thread_flag(TIF_SYSCALL_TRACEPOINT)) + trace_sys_enter(regs, regs->syscallno); + diff --git a/queue-6.12/rust-allow-clippy-unwrap_or_default-globally.patch b/queue-6.12/rust-allow-clippy-unwrap_or_default-globally.patch new file mode 100644 index 0000000000..a8c1b62978 --- /dev/null +++ b/queue-6.12/rust-allow-clippy-unwrap_or_default-globally.patch @@ -0,0 +1,62 @@ +From 4688cf884b3abcd12498e03b625d1916bf49a1e4 Mon Sep 17 00:00:00 2001 +From: Alexandre Courbot +Date: Wed, 8 Jul 2026 19:49:26 +0900 +Subject: rust: allow `clippy::unwrap_or_default` globally + +From: Alexandre Courbot + +commit 4688cf884b3abcd12498e03b625d1916bf49a1e4 upstream. + +Starting with rustc 1.88, the `clippy::unwrap_or_default` lint triggers +on `rust/kernel/soc.rs` if `CONFIG_CC_OPTIMIZE_FOR_SIZE=y`: + + warning: use of `unwrap_or` to construct default value + --> ../rust/kernel/soc.rs:66:10 + | + 66 | .unwrap_or(core::ptr::null()) + | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: try: `unwrap_or_default()` + +This is a clippy bug [1]: the lint decides whether an expression is +equivalent to `Default::default()` by inspecting the optimized MIR of +`<*const T as Default>::default` exported by `core`, so its outcome +depends on the optimization level `core` was built with. Moreover, its +suggestion ignores our MSRV of 1.85 (`Default` for `*const T` is only +stable since Rust 1.88), so we could not apply it anyway. + +Disable the lint globally rather than working around this single +occurrence; it can be re-enabled conditionally using `rustc-min-version` +once clippy is fixed. + +Link: https://github.com/rust-lang/rust-clippy/issues/17379 [1] +Suggested-by: Miguel Ojeda +Signed-off-by: Alexandre Courbot +Cc: stable@vger.kernel.org # Needed in 6.12.y and later (Rust is pinned in older LTSs). +Link: https://patch.msgid.link/20260708-soc_unwrap_or-v2-1-007ed724cc7b@nvidia.com +[ Moved to non-versioned group. - Miguel ] +Signed-off-by: Miguel Ojeda +Signed-off-by: Greg Kroah-Hartman +--- + Makefile | 5 +++++ + 1 file changed, 5 insertions(+) + +--- a/Makefile ++++ b/Makefile +@@ -443,6 +443,10 @@ KBUILD_USERLDFLAGS := $(USERLDFLAGS) + + # These flags apply to all Rust code in the tree, including the kernel and + # host programs. ++# ++# `-Aclippy::unwrap_or_default`: the lint is buggy [1] and ignores our ++# MSRV. It can trigger depending on the optimization level. ++# [1] https://github.com/rust-lang/rust-clippy/issues/17379 + export rust_common_flags := --edition=2021 \ + -Zbinary_dep_depinfo=y \ + -Astable_features \ +@@ -464,6 +468,7 @@ export rust_common_flags := --edition=20 + -Aclippy::uninlined_format_args \ + -Wclippy::unnecessary_safety_comment \ + -Wclippy::unnecessary_safety_doc \ ++ -Aclippy::unwrap_or_default \ + -Wrustdoc::missing_crate_level_docs \ + -Wrustdoc::unescaped_backticks + diff --git a/queue-6.12/serial-8250_mid-fix-null-function-pointer-dereference-on-dnv-icx-d-snr-platforms.patch b/queue-6.12/serial-8250_mid-fix-null-function-pointer-dereference-on-dnv-icx-d-snr-platforms.patch new file mode 100644 index 0000000000..850de08a7b --- /dev/null +++ b/queue-6.12/serial-8250_mid-fix-null-function-pointer-dereference-on-dnv-icx-d-snr-platforms.patch @@ -0,0 +1,68 @@ +From 7fb13fd7e9a59a37cd911efff83abe19e3ee029d Mon Sep 17 00:00:00 2001 +From: Jiangshan Yi +Date: Wed, 15 Jul 2026 15:35:46 +0800 +Subject: serial: 8250_mid: Fix NULL function pointer dereference on DNV/ICX-D/SNR platforms + +From: Jiangshan Yi + +commit 7fb13fd7e9a59a37cd911efff83abe19e3ee029d upstream. + +Commit b1b4efea05a5 ("serial: 8250_mid: Disable DMA for selected +platforms") replaced the dnv_board setup and exit callbacks with +PTR_IF(false, ...), which evaluates to NULL. However, the three call +sites in mid8250_probe() and mid8250_remove() unconditionally +dereference these function pointers without NULL checks, causing a NULL +pointer dereference (kernel oops) on any Denverton (DNV), Ice Lake Xeon +D (ICX-D/CDF), or Snowridge (SNR) platform. + +Fix this by adding the missing NULL checks before calling the setup and +exit callbacks. + +Fixes: b1b4efea05a5 ("serial: 8250_mid: Disable DMA for selected platforms") +Cc: stable +Reviewed-by: Andy Shevchenko +Signed-off-by: Jiangshan Yi +Link: https://patch.msgid.link/20260715073546.1875083-1-yijiangshan@kylinos.cn +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Greg Kroah-Hartman +--- + drivers/tty/serial/8250/8250_mid.c | 14 +++++++++----- + 1 file changed, 9 insertions(+), 5 deletions(-) + +--- a/drivers/tty/serial/8250/8250_mid.c ++++ b/drivers/tty/serial/8250/8250_mid.c +@@ -318,9 +318,11 @@ static int mid8250_probe(struct pci_dev + if (!uart.port.membase) + return -ENOMEM; + +- ret = mid->board->setup(mid, &uart.port); +- if (ret) +- return ret; ++ if (mid->board->setup) { ++ ret = mid->board->setup(mid, &uart.port); ++ if (ret) ++ return ret; ++ } + + ret = mid8250_dma_setup(mid, &uart); + if (ret) +@@ -336,7 +338,8 @@ static int mid8250_probe(struct pci_dev + return 0; + + err: +- mid->board->exit(mid); ++ if (mid->board->exit) ++ mid->board->exit(mid); + return ret; + } + +@@ -346,7 +349,8 @@ static void mid8250_remove(struct pci_de + + serial8250_unregister_port(mid->line); + +- mid->board->exit(mid); ++ if (mid->board->exit) ++ mid->board->exit(mid); + } + + static const struct mid8250_board pnw_board = { diff --git a/queue-6.12/serial-sc16is7xx-implement-gpio-get_direction-callback.patch b/queue-6.12/serial-sc16is7xx-implement-gpio-get_direction-callback.patch new file mode 100644 index 0000000000..625d7bcacd --- /dev/null +++ b/queue-6.12/serial-sc16is7xx-implement-gpio-get_direction-callback.patch @@ -0,0 +1,54 @@ +From af071d9e07e57cfff239e8d09d2f3b05ebc9c667 Mon Sep 17 00:00:00 2001 +From: Hugo Villeneuve +Date: Thu, 16 Jul 2026 17:08:09 -0400 +Subject: serial: sc16is7xx: implement gpio get_direction() callback + +From: Hugo Villeneuve + +commit af071d9e07e57cfff239e8d09d2f3b05ebc9c667 upstream. + +It's strongly recommended for GPIO drivers to always implement the +.get_direction() callback - even when the direction is tracked in +software. The GPIO core emits a warning when the callback is missing +and a user reads the direction of a line, e.g. via +/sys/kernel/debug/gpio. + +Fixes: dfeae619d781 ("serial: sc16is7xx") +Cc: stable +Signed-off-by: Hugo Villeneuve +Acked-by: Bartosz Golaszewski +Link: https://patch.msgid.link/20260716210813.2582826-1-hugo@hugovil.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Greg Kroah-Hartman +--- + drivers/tty/serial/sc16is7xx.c | 12 ++++++++++++ + 1 file changed, 12 insertions(+) + +--- a/drivers/tty/serial/sc16is7xx.c ++++ b/drivers/tty/serial/sc16is7xx.c +@@ -1302,6 +1302,17 @@ static void sc16is7xx_gpio_set(struct gp + val ? BIT(offset) : 0); + } + ++static int sc16is7xx_gpio_get_direction(struct gpio_chip *chip, unsigned int offset) ++{ ++ struct sc16is7xx_port *s = gpiochip_get_data(chip); ++ struct uart_port *port = &s->p[0].port; ++ unsigned int val; ++ ++ val = sc16is7xx_port_read(port, SC16IS7XX_IODIR_REG); ++ ++ return val & BIT(offset) ? GPIO_LINE_DIRECTION_OUT : GPIO_LINE_DIRECTION_IN; ++} ++ + static int sc16is7xx_gpio_direction_input(struct gpio_chip *chip, + unsigned offset) + { +@@ -1379,6 +1390,7 @@ static int sc16is7xx_setup_gpio_chip(str + s->gpio.parent = dev; + s->gpio.label = dev_name(dev); + s->gpio.init_valid_mask = sc16is7xx_gpio_init_valid_mask; ++ s->gpio.get_direction = sc16is7xx_gpio_get_direction; + s->gpio.direction_input = sc16is7xx_gpio_direction_input; + s->gpio.get = sc16is7xx_gpio_get; + s->gpio.direction_output = sc16is7xx_gpio_direction_output; diff --git a/queue-6.12/series b/queue-6.12/series index d21a77545b..83dc68c924 100644 --- a/queue-6.12/series +++ b/queue-6.12/series @@ -359,3 +359,29 @@ bluetooth-rfcomm-fix-session-uaf-in-set_termios.patch exec-fix-unsigned-loop-counter-wrap-in-transfer_args_to_stack.patch binfmt_misc-set-have_execfd-only-once-the-interpreter-is-opened.patch platform-loongarch-laptop-explicitly-reset-bl_powered-state-when-suspend.patch +rust-allow-clippy-unwrap_or_default-globally.patch +objtool-rust-add-one-more-noreturn-rust-function-for-rust-1.99.0.patch +loongarch-fix-oops-during-single-step-debugging.patch +loongarch-move-jump_label_init-before-parse_early_param.patch +loongarch-retrieve-cpu-package-id-from-pptt-when-available.patch +cdrom-fix-stack-out-of-bounds-read-in-cdromvolctrl.patch +firmware-stratix10-svc-fix-memory-leaks-and-list-corruption-bugs.patch +x86-boot-compressed-disable-jump-tables.patch +comedi-comedi_parport-deal-with-premature-interrupt.patch +uio_hv_generic-bind-to-fcopy-device-by-default.patch +serial-sc16is7xx-implement-gpio-get_direction-callback.patch +serial-8250_mid-fix-null-function-pointer-dereference-on-dnv-icx-d-snr-platforms.patch +mei-bus-access-mei_device-under-device_lock-on-cleanup.patch +intel_th-fix-msc-output-device-reference-leak.patch +misc-nsm-only-unlock-nsm_dev-on-post-lock-error-paths.patch +misc-nsm-pin-the-module-while-the-device-is-open.patch +tracing-fix-mmiotrace-possible-null-dereferencing-of-hiter-dev.patch +tracing-fix-resource-leak-on-mmiotrace-trace_pipe-close.patch +tracing-eprobe-fix-exact-system-name-matching-in-eprobe_dyn_event_match.patch +tracing-probes-avoid-temporary-buffer-truncation-in-trace_probe_match_command_args.patch +tracing-probes-fix-potential-underflow-in-len_or_zero-macro.patch +tracing-probes-prevent-out-of-bounds-write-in-__trace_probe_log_err.patch +arm64-syscall-ensure-saved-x0-is-kept-in-sync-with-tracer-updates.patch +revert-arm64-syscall-ensure-saved-x0-is-kept-in-sync-with-tracer-updates.patch +mptcp-decrement-subflows-counter-on-failed-passive-join.patch +mptcp-only-set-data_fin-when-a-mapping-is-present.patch diff --git a/queue-6.12/tracing-eprobe-fix-exact-system-name-matching-in-eprobe_dyn_event_match.patch b/queue-6.12/tracing-eprobe-fix-exact-system-name-matching-in-eprobe_dyn_event_match.patch new file mode 100644 index 0000000000..745d944194 --- /dev/null +++ b/queue-6.12/tracing-eprobe-fix-exact-system-name-matching-in-eprobe_dyn_event_match.patch @@ -0,0 +1,41 @@ +From f418d68d71fd4a0a9cef92377bc8c4c3334b5b53 Mon Sep 17 00:00:00 2001 +From: "Masami Hiramatsu (Google)" +Date: Mon, 20 Jul 2026 19:12:38 +0900 +Subject: tracing/eprobe: Fix exact system name matching in eprobe_dyn_event_match() + +From: Masami Hiramatsu (Google) + +commit f418d68d71fd4a0a9cef92377bc8c4c3334b5b53 upstream. + +eprobe_dyn_event_match() checks if the target event system in argv[0] +matches ep->event_system using strncmp(ep->event_system, argv[0], len). +However, if ep->event_system is longer than len (e.g. "eprobes" vs +"ep/event"), strncmp() still returns 0 because the first len characters +match. + +Check that ep->event_system[len] is '\0' to ensure exact system name +matching. + +Link: https://lore.kernel.org/all/178454235856.290363.14872590900774231133.stgit@devnote2/ + +Fixes: 7d5fda1c841f ("tracing: Fix event probe removal from dynamic events") +Cc: stable@vger.kernel.org +Assisted-by: Antigravity:gemini-3.5-flash +Signed-off-by: Masami Hiramatsu (Google) +Signed-off-by: Greg Kroah-Hartman +--- + kernel/trace/trace_eprobe.c | 3 ++- + 1 file changed, 2 insertions(+), 1 deletion(-) + +--- a/kernel/trace/trace_eprobe.c ++++ b/kernel/trace/trace_eprobe.c +@@ -168,7 +168,8 @@ static bool eprobe_dyn_event_match(const + if (!slash) + return false; + +- if (strncmp(ep->event_system, argv[0], slash - argv[0])) ++ if (strncmp(ep->event_system, argv[0], slash - argv[0]) || ++ ep->event_system[slash - argv[0]] != '\0') + return false; + if (strcmp(ep->event_name, slash + 1)) + return false; diff --git a/queue-6.12/tracing-fix-mmiotrace-possible-null-dereferencing-of-hiter-dev.patch b/queue-6.12/tracing-fix-mmiotrace-possible-null-dereferencing-of-hiter-dev.patch new file mode 100644 index 0000000000..e8451d6634 --- /dev/null +++ b/queue-6.12/tracing-fix-mmiotrace-possible-null-dereferencing-of-hiter-dev.patch @@ -0,0 +1,38 @@ +From 144f29e85702234b23d2a62abf723e6a17eb5427 Mon Sep 17 00:00:00 2001 +From: Steven Rostedt +Date: Tue, 21 Jul 2026 21:11:43 -0400 +Subject: tracing: Fix mmiotrace possible NULL dereferencing of hiter->dev + +From: Steven Rostedt + +commit 144f29e85702234b23d2a62abf723e6a17eb5427 upstream. + +If the mmio_pipe_open() fails to find a PCI device, the hiter->dev +will be assigned to NULL. The mmiotrace read() function dereferences the +hiter->dev if hiter exists. + +Change the test of the read to not only check hiter being NULL, but also +the hiter->dev before dereferencing it. + +Cc: stable@vger.kernel.org +Link: https://patch.msgid.link/20260721211143.36dbd559@gandalf.local.home +Fixes: f984b51e0779 ("ftrace: add mmiotrace plugin") +Reported-by: Sashiko +Link: https://sashiko.dev/#/patchset/20260715143604.14481-1-gaikwad.dcg%40gmail.com +Signed-off-by: Steven Rostedt +Signed-off-by: Greg Kroah-Hartman +--- + kernel/trace/trace_mmiotrace.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +--- a/kernel/trace/trace_mmiotrace.c ++++ b/kernel/trace/trace_mmiotrace.c +@@ -146,7 +146,7 @@ static ssize_t mmio_read(struct trace_it + goto print_out; + } + +- if (!hiter) ++ if (!hiter || !hiter->dev) + return 0; + + mmio_print_pcidev(s, hiter->dev); diff --git a/queue-6.12/tracing-fix-resource-leak-on-mmiotrace-trace_pipe-close.patch b/queue-6.12/tracing-fix-resource-leak-on-mmiotrace-trace_pipe-close.patch new file mode 100644 index 0000000000..821fe202f0 --- /dev/null +++ b/queue-6.12/tracing-fix-resource-leak-on-mmiotrace-trace_pipe-close.patch @@ -0,0 +1,62 @@ +From c1d87e724ae55e781b7cc7ccafb34d9e668582b2 Mon Sep 17 00:00:00 2001 +From: deepakraog +Date: Wed, 15 Jul 2026 20:06:04 +0530 +Subject: tracing: Fix resource leak on mmiotrace trace_pipe close + +From: deepakraog + +commit c1d87e724ae55e781b7cc7ccafb34d9e668582b2 upstream. + +The mmiotrace tracer was added May 12th 2008. At that time, resources +created in pipe_open() could not be freed because there was not +pipe_close function pointer of the tracer. The pipe_close function pointer +was added in December 7th, 2009, but the mmiotrace tracer was not updated. + +mmio_pipe_open() allocates a header_iter and takes a pci_dev reference +when trace_pipe is opened. mmio_close() frees them, but it was only +wired to the tracer's .close callback. + +tracing_release_pipe() invokes .pipe_close, not .close, when the +trace_pipe file is released. As a result, closing trace_pipe with the +mmiotrace tracer active leaked the header_iter allocation and left a +stale pci_dev reference. + +Set .pipe_close to mmio_close, matching how function_graph wires both +callbacks to the same handler. + +Note, if the trace_pipe is read to completion, it will clean up the +resources, but if one were to run: + + # head -n 1 /sys/kernel/tracing/trace_pipe + VERSION 20070824 + +Over and over again, it would trigger a massive leak. + +Cc: stable@vger.kernel.org +Fixes: c521efd1700a8 ("tracing: Add pipe_close interface) +Link: https://patch.msgid.link/20260715143604.14481-1-gaikwad.dcg@gmail.com +Signed-off-by: deepakraog +Signed-off-by: Steven Rostedt +Signed-off-by: Greg Kroah-Hartman +--- + kernel/trace/trace_mmiotrace.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +--- a/kernel/trace/trace_mmiotrace.c ++++ b/kernel/trace/trace_mmiotrace.c +@@ -109,7 +109,6 @@ static void mmio_pipe_open(struct trace_ + iter->private = hiter; + } + +-/* XXX: This is not called when the pipe is closed! */ + static void mmio_close(struct trace_iterator *iter) + { + struct header_iter *hiter = iter->private; +@@ -279,6 +278,7 @@ static struct tracer mmio_tracer __read_ + .start = mmio_trace_start, + .pipe_open = mmio_pipe_open, + .close = mmio_close, ++ .pipe_close = mmio_close, + .read = mmio_read, + .print_line = mmio_print_line, + .noboot = true, diff --git a/queue-6.12/tracing-probes-avoid-temporary-buffer-truncation-in-trace_probe_match_command_args.patch b/queue-6.12/tracing-probes-avoid-temporary-buffer-truncation-in-trace_probe_match_command_args.patch new file mode 100644 index 0000000000..d8cee7b091 --- /dev/null +++ b/queue-6.12/tracing-probes-avoid-temporary-buffer-truncation-in-trace_probe_match_command_args.patch @@ -0,0 +1,53 @@ +From 15f197856d68882af9416fc97516bb55079b7677 Mon Sep 17 00:00:00 2001 +From: "Masami Hiramatsu (Google)" +Date: Mon, 20 Jul 2026 19:12:10 +0900 +Subject: tracing/probes: Avoid temporary buffer truncation in trace_probe_match_command_args() + +From: Masami Hiramatsu (Google) + +commit 15f197856d68882af9416fc97516bb55079b7677 upstream. + +In trace_probe_match_command_args(), a stack buffer buf[MAX_ARGSTR_LEN + 1] +(256 bytes) is used to format "=". However, since name can +be up to 32 bytes (MAX_ARG_NAME_LEN) and comm up to 255 bytes +(MAX_ARGSTR_LEN), the formatted string can exceed 256 bytes and get +truncated by snprintf(), causing spurious argument matching failures. + +Instead of formatting into a temporary buffer on stack, compare the +argument name, the '=' delimiter, and the comm expression directly. + +Link: https://lore.kernel.org/all/178454233010.290363.10428767141343428804.stgit@devnote2/ + +Fixes: eb5bf81330a7 ("tracing/kprobe: Add per-probe delete from event") +Cc: stable@vger.kernel.org +Assisted-by: Antigravity:gemini-3.5-flash +Signed-off-by: Masami Hiramatsu (Google) +Signed-off-by: Greg Kroah-Hartman +--- + kernel/trace/trace_probe.c | 9 +++++---- + 1 file changed, 5 insertions(+), 4 deletions(-) + +--- a/kernel/trace/trace_probe.c ++++ b/kernel/trace/trace_probe.c +@@ -2212,16 +2212,17 @@ int trace_probe_compare_arg_type(struct + bool trace_probe_match_command_args(struct trace_probe *tp, + int argc, const char **argv) + { +- char buf[MAX_ARGSTR_LEN + 1]; + int i; + + if (tp->nr_args < argc) + return false; + + for (i = 0; i < argc; i++) { +- snprintf(buf, sizeof(buf), "%s=%s", +- tp->args[i].name, tp->args[i].comm); +- if (strcmp(buf, argv[i])) ++ int len = strlen(tp->args[i].name); ++ ++ if (strncmp(argv[i], tp->args[i].name, len) || ++ argv[i][len] != '=' || ++ strcmp(argv[i] + len + 1, tp->args[i].comm)) + return false; + } + return true; diff --git a/queue-6.12/tracing-probes-fix-potential-underflow-in-len_or_zero-macro.patch b/queue-6.12/tracing-probes-fix-potential-underflow-in-len_or_zero-macro.patch new file mode 100644 index 0000000000..cdc3c97e38 --- /dev/null +++ b/queue-6.12/tracing-probes-fix-potential-underflow-in-len_or_zero-macro.patch @@ -0,0 +1,38 @@ +From 8ce20bfba48902e1382187cd1a852f7cf3a1e739 Mon Sep 17 00:00:00 2001 +From: "Masami Hiramatsu (Google)" +Date: Mon, 20 Jul 2026 19:12:29 +0900 +Subject: tracing/probes: Fix potential underflow in LEN_OR_ZERO macro + +From: Masami Hiramatsu (Google) + +commit 8ce20bfba48902e1382187cd1a852f7cf3a1e739 upstream. + +In __set_print_fmt(), LEN_OR_ZERO is defined as (len ? len - pos : 0). +If len is non-zero but smaller than pos, len - pos evaluates to a negative +integer. When passed as a size argument to snprintf(), this negative value +is cast to a large unsigned size_t, bypassing buffer size limits. + +Ensure len > pos before subtracting to avoid integer underflow. + +Link: https://lore.kernel.org/all/178454234934.290363.15247317871499514139.stgit@devnote2/ + +Fixes: 5bf652aaf46c ("tracing/probes: Integrate duplicate set_print_fmt()") +Cc: stable@vger.kernel.org +Assisted-by: Antigravity:gemini-3.5-flash +Signed-off-by: Masami Hiramatsu (Google) +Signed-off-by: Greg Kroah-Hartman +--- + kernel/trace/trace_probe.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +--- a/kernel/trace/trace_probe.c ++++ b/kernel/trace/trace_probe.c +@@ -1886,7 +1886,7 @@ int traceprobe_update_arg(struct probe_a + } + + /* When len=0, we just calculate the needed length */ +-#define LEN_OR_ZERO (len ? len - pos : 0) ++#define LEN_OR_ZERO (len > pos ? len - pos : 0) + static int __set_print_fmt(struct trace_probe *tp, char *buf, int len, + enum probe_print_type ptype) + { diff --git a/queue-6.12/tracing-probes-prevent-out-of-bounds-write-in-__trace_probe_log_err.patch b/queue-6.12/tracing-probes-prevent-out-of-bounds-write-in-__trace_probe_log_err.patch new file mode 100644 index 0000000000..fc83b96748 --- /dev/null +++ b/queue-6.12/tracing-probes-prevent-out-of-bounds-write-in-__trace_probe_log_err.patch @@ -0,0 +1,38 @@ +From a9d6fb284039a5d3858a1d9f9a0d7e46cfb7c2d4 Mon Sep 17 00:00:00 2001 +From: "Masami Hiramatsu (Google)" +Date: Mon, 20 Jul 2026 19:12:20 +0900 +Subject: tracing/probes: Prevent out-of-bounds write in __trace_probe_log_err() + +From: Masami Hiramatsu (Google) + +commit a9d6fb284039a5d3858a1d9f9a0d7e46cfb7c2d4 upstream. + +If trace_probe_log.argc is 0 in __trace_probe_log_err(), the loop +constructing the command string will not execute and p will remain equal to +command. Writing to *(p - 1) will cause an out-of-bounds access before +command. This should not happen, but better to be treated. + +Reject if trace_probe_log.argc is 0. + +Link: https://lore.kernel.org/all/178454233992.290363.18323091580600697731.stgit@devnote2/ + +Fixes: ab105a4fb894 ("tracing: Use tracing error_log with probe events") +Cc: stable@vger.kernel.org +Assisted-by: Antigravity:gemini-3.5-flash +Signed-off-by: Masami Hiramatsu (Google) +Signed-off-by: Greg Kroah-Hartman +--- + kernel/trace/trace_probe.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +--- a/kernel/trace/trace_probe.c ++++ b/kernel/trace/trace_probe.c +@@ -187,7 +187,7 @@ void __trace_probe_log_err(int offset, i + + lockdep_assert_held(&dyn_event_ops_mutex); + +- if (!trace_probe_log.argv) ++ if (!trace_probe_log.argv || !trace_probe_log.argc) + return; + + /* Recalculate the length and allocate buffer */ diff --git a/queue-6.12/uio_hv_generic-bind-to-fcopy-device-by-default.patch b/queue-6.12/uio_hv_generic-bind-to-fcopy-device-by-default.patch new file mode 100644 index 0000000000..7e11f7de0a --- /dev/null +++ b/queue-6.12/uio_hv_generic-bind-to-fcopy-device-by-default.patch @@ -0,0 +1,46 @@ +From 87d3621ccc63b3999d756bb59f0cedd738c28eb3 Mon Sep 17 00:00:00 2001 +From: Ben Hutchings +Date: Mon, 25 May 2026 14:04:22 +0200 +Subject: uio_hv_generic: Bind to FCopy device by default + +From: Ben Hutchings + +commit 87d3621ccc63b3999d756bb59f0cedd738c28eb3 upstream. + +The Hyper-V kernel-mode fcopy driver was removed in 6.10 and the new +fcopy daemon requires this uio driver to function. However, by +default the driver does not bind to any devices, and must be +configured through the sysfs "new_id" file. + +Since the FCopy device is now only usable through this driver, add its +ID to the driver's ID table so that the daemon will work "out of the +box". + +Signed-off-by: Ben Hutchings +Fixes: ec314f61e4fc ("Drivers: hv: Remove fcopy driver") +Cc: stable +Link: https://patch.msgid.link/ahQ6xuhSReidmN-3@decadent.org.uk +Signed-off-by: Greg Kroah-Hartman +--- + drivers/uio/uio_hv_generic.c | 8 +++++++- + 1 file changed, 7 insertions(+), 1 deletion(-) + +--- a/drivers/uio/uio_hv_generic.c ++++ b/drivers/uio/uio_hv_generic.c +@@ -395,9 +395,15 @@ hv_uio_remove(struct hv_device *dev) + vmbus_free_ring(dev->channel); + } + ++static const struct hv_vmbus_device_id hv_uio_id_table[] = { ++ { HV_FCOPY_GUID }, ++ {} ++}; ++MODULE_DEVICE_TABLE(vmbus, hv_uio_id_table); ++ + static struct hv_driver hv_uio_drv = { + .name = "uio_hv_generic", +- .id_table = NULL, /* only dynamic id's */ ++ .id_table = hv_uio_id_table, + .probe = hv_uio_probe, + .remove = hv_uio_remove, + }; diff --git a/queue-6.12/x86-boot-compressed-disable-jump-tables.patch b/queue-6.12/x86-boot-compressed-disable-jump-tables.patch new file mode 100644 index 0000000000..eeacda5db8 --- /dev/null +++ b/queue-6.12/x86-boot-compressed-disable-jump-tables.patch @@ -0,0 +1,63 @@ +From 4a9ec5ec9555ad62dc5b81a37ac946025c2ea002 Mon Sep 17 00:00:00 2001 +From: Nathan Chancellor +Date: Wed, 22 Jul 2026 17:09:43 -0700 +Subject: x86/boot/compressed: Disable jump tables + +From: Nathan Chancellor + +commit 4a9ec5ec9555ad62dc5b81a37ac946025c2ea002 upstream. + +After a recent upstream LLVM change to start generating jump and lookup +tables in switch statements in more instances [1], linking the +compressed x86 boot image when CONFIG_KERNEL_ZSTD is enabled fails with: + + ld.lld: error: Unexpected run-time relocations (.rela) detected! + +Dumping the relocations in misc.o, which is the only file influenced by +CONFIG_KERNEL_ZSTD in the decompressor, shows dynamic relocations to +some string constants, which correspond to the string literals in the +switch statement in handle_zstd_error(): + + Relocation section '.rela.data.rel.ro' at offset 0x277b0 contains 31 entries: + Offset Info Type Symbol's Value Symbol's Name + Addend + 0000000000000000 0000006600000001 R_X86_64_64 0000000000000000 .rodata.str1.1 + 73a + 0000000000000008 0000006600000001 R_X86_64_64 0000000000000000 .rodata.str1.1 + 78e + 0000000000000010 0000006600000001 R_X86_64_64 0000000000000000 .rodata.str1.1 + 78e + 0000000000000018 0000006600000001 R_X86_64_64 0000000000000000 .rodata.str1.1 + 78e + ... + +This optimization is problematic for the decompressor environment, as it +is built as -fPIE without any explicit absolute references (as described +at the top of misc.c) while not applying any dynamic relocations, hence +the linker assertion. To opt out of this optimization, which is of +little value in this special early boot code, and to mirror the other +x86 startup code in arch/x86/boot/startup, disable jump tables in the +decompressor. + +Signed-off-by: Nathan Chancellor +Signed-off-by: Ingo Molnar +Acked-by: Ard Biesheuvel +Cc: Bill Wendling +Cc: Justin Stitt +Cc: Nick Desaulniers +Cc: "H. Peter Anvin" +Cc: Peter Zijlstra +Cc: stable@vger.kernel.org +Link: https://github.com/llvm/llvm-project/commit/fa02a6ed66b1700c996b49c96c6bc0eb014c9518 [1] +Link: https://patch.msgid.link/20260722-x86-boot-compressed-disable-jt-clang-v2-1-7373d38482fb@kernel.org +Closes: https://github.com/ClangBuiltLinux/linux/issues/2165 +Signed-off-by: Greg Kroah-Hartman +--- + arch/x86/boot/compressed/Makefile | 1 + + 1 file changed, 1 insertion(+) + +--- a/arch/x86/boot/compressed/Makefile ++++ b/arch/x86/boot/compressed/Makefile +@@ -27,6 +27,7 @@ targets := vmlinux vmlinux.bin vmlinux.b + KBUILD_CFLAGS := -m$(BITS) -O2 $(CLANG_FLAGS) + KBUILD_CFLAGS += -std=gnu11 + KBUILD_CFLAGS += -fno-strict-aliasing -fPIE ++KBUILD_CFLAGS += -fno-jump-tables + KBUILD_CFLAGS += -Wundef + KBUILD_CFLAGS += -DDISABLE_BRANCH_PROFILING + cflags-$(CONFIG_X86_32) := -march=i386