This bug is awaiting verification that the linux-nvidia- tegra/6.8.0-1012.12 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-nvidia-tegra' to 'verification-done-noble-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-noble-linux-nvidia-tegra' to 'verification-failed-noble-linux-nvidia-tegra'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-nvidia-tegra-v2 verification-needed-noble-linux-nvidia-tegra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.14 in Ubuntu. https://bugs.launchpad.net/bugs/2119713 Title: UBSAN: shift-out-of-bounds in drivers/edac/skx_common.c:452:16 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.14 package in Ubuntu: Invalid Status in linux source package in Noble: Fix Committed Status in linux-oem-6.14 source package in Noble: Fix Released Status in linux source package in Plucky: In Progress Status in linux-oem-6.14 source package in Plucky: Invalid Status in linux source package in Questing: Fix Released Status in linux-oem-6.14 source package in Questing: Invalid Bug description: [Impact] Shows the following UBSAN warning messages in dmesg Jul 21 08:37:25 localhost kernel: UBSAN: shift-out-of-bounds in /build/linux-oem-6.14-44jeWy/linux-oem-6.14-6.14.0/drivers/edac/skx_common.c:452:16 Jul 21 08:37:25 localhost kernel: shift exponent -66 is negative Jul 21 08:37:25 localhost kernel: CPU: 79 UID: 0 PID: 2454 Comm: (udev-worker) Not tainted 6.14.0-1006-oem #6-Ubuntu Jul 21 08:37:25 localhost kernel: Hardware name: Dell Inc. Dell Pro Max Tower T6 FCT6260/, BIOS 0.9.39 07/09/2025 Jul 21 08:37:25 localhost kernel: Call Trace: Jul 21 08:37:25 localhost kernel: <TASK> Jul 21 08:37:25 localhost kernel: dump_stack_lvl+0x76/0xa0 Jul 21 08:37:25 localhost kernel: dump_stack+0x10/0x20 Jul 21 08:37:25 localhost kernel: __ubsan_handle_shift_out_of_bounds+0x1a5/0x380 Jul 21 08:37:25 localhost kernel: skx_get_dimm_info.cold+0x2a/0x17f [skx_edac_common] Jul 21 08:37:25 localhost kernel: i10nm_get_dimm_config+0x1f9/0x300 [i10nm_edac] Jul 21 08:37:25 localhost kernel: skx_register_mci+0x139/0x1e0 [skx_edac_common] Jul 21 08:37:25 localhost kernel: ? __pfx_i10nm_get_dimm_config+0x10/0x10 [i10nm_edac] Jul 21 08:37:25 localhost kernel: i10nm_init+0x42b/0xff0 [i10nm_edac] Jul 21 08:37:25 localhost kernel: ? __pfx_i10nm_init+0x10/0x10 [i10nm_edac] [Fix] In linux-next 2e6fe1bbefd9 EDAC/i10nm: Skip DIMM enumeration on a disabled memory controller Intel provides a fix for this issue https://lore.kernel.org/lkml/[email protected]/ [Test] Boot up the Intel Granite Rapids and check dmesg log, there should be no UBSAN shift-out-of-bounds message. [Where problems could occur] It adds extra check for edac i10nm driver, the impact should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2119713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
