[Bug 2150769] Re: There is a conflict between the pc-kernel snap and additional firmware packages

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150769 Title: There is a conflict between the pc-kernel snap and additional firmware packages Status in linux package in Ubuntu: Confirmed Status in linux-firmware-intel-wireless package in Ubuntu: Confirmed Bug description: I described in detail here, in case I miss anything in this description: https://discourse.ubuntu.com/t/the-pc-kernel-snap- on-26-04-prevents-users-from-installing-additional-firmware/81404 This bug report is pretty wordy so here's a top-line summary: 1. The pc-kernel snap uses an unfortunately unreliable method of including firmware, which means some firmware gets missed 2. The apt dependencies of `boot-managed-by-snapd` preclude installing `linux-firmware` but do not preclude installing any other firmware packages making it possible to break your system in a pretty dramatic way that many users might have a very difficult time figuring out or resolving. Reproduction steps: 1. Install Ubuntu using the `pc-kernel` snap rather than apt kernel packages 2. Install the `linux-firmware-intel-wireless` package Okay, now on to the verbose part of the bug report which I hope is at least partially understandable. Circumstance: 1. I'm running Ubuntu 26.04 using the pc-kernel snapo (because of hardware FDE I guess) 2. My laptop has a pretty new Arrow Lake chipset with an Intel wifi adapter 3. My wifi doesn't work What I discovered while debugging: the `iwlwifi` module won't load properly because it can't find the firmware file it wants, as it is not present in the `pc-kernel` snap, so wifi doesn't work. This took me in a few different directions and this is what I found: * Unspecified incompatibility between pc-kernel and additional firmware packages First, the pc-kernel snap creates symlinks to everything in its 'firmware' directory into the filesystem that gets mounted at /usr/lib/firmware, but it links everything at the top-level. That means firmware can be added to e.g. /usr/lib/firmware/somefile.fw, because that's a directory, but not /usr/lib/firmware/intel/somefile.fw because /usr/lib/firmware/intel is a symlink to a directory on the squashfs filesystem. This means that installing the `linux-firmware-intel-wireless` package, which has the firmware I need: 1. Breaks when trying to install because it tries to write some files to /usr/lib/firmware/intel/ 2. Refuses to uninstall until it's installed correctly, because dpkg recognizes it as being in an extremely broken state. I say 'unspecified' because `boot-managed-by-snapd` explicitly conflicts with `linux-firmware` (showing the intention to not allow both at once), but it does not conflict with any additional firmware packages. * Incomplete firmware inventory in the pc-kernel snap I dug into it a bit and found that the pc-kernel snap builds using the following steps: 1. Get the kernel and the modules together 2. Ask each module what firmware it wants (via `modinfo`) 3. Bundle those firmwares into the pc-kernel snap Unfortunately, for whatever reason, the `iwlwifi` firmware does not specify the firmware that my system seems to insist on, which is `bz-b0-fm-c0-c101.ucode`, so it does not get included into the pc- kernel snap. The `linux-firmware-intel-wireless` debian package *does* include this firmware, presumably because it just includes all available Intel wireless firmware unconditionally. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic (not installed) ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: dan 6392 F.... wireplumber /dev/snd/controlC1: dan 6392 F.... wireplumber /dev/snd/controlC0: dan 6392 F.... wireplumber /dev/snd/seq: dan 6354 F.... pipewire CasperMD5CheckMismatches: ./EFI/boot/bootx64.efi ./EFI/boot/grubx64.efi ./EFI/boot/mmx64.efi CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 10:29:41 2026 MachineType: Dell Inc. Dell Pro Max 14 Premium MA14250 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/zsh TERM=xterm-ghostty XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: snapd_recovery_mode=run console=ttyS0,115200n8 console=tty1 panic=-1 quiet splash snapd.xkb="us,pc105,," RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2025 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 06XRHN dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd12/11/2025:br1.7:efr1.6:svnDellInc.:pnDellProMax14PremiumMA14250:pvr:rvnDellInc.:rn06XRHN:rvrA02:cvnDellInc.:ct10:cvr:sku0D32:pfaDellProMaxLaptops: dmi.product.family: Dell Pro Max Laptops dmi.product.name: Dell Pro Max 14 Premium MA14250 dmi.product.sku: 0D32 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150769/+subscriptions

[Bug 2150621] Re: regression: booting instability and large variance in booting success

as mentioned above, in the meantime i observe the same behavior also on another similar thinkpad (e14 gen 6, ryzen 5, radeon). i am attaching an unsuccessful appearance of the gdm greeter and one successful one, in case the diff will give you any hints of where the race condition might be. ** Attachment added: "journal of the unsuccessful gmd start with kernel 7.0.0-15" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150621/+attachment/5968964/+files/journal-wilmon-failed_gdm_start-linux-7.0.0-15.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150621 Title: regression: booting instability and large variance in booting success Status in linux package in Ubuntu: New Bug description: fresh install of ubuntu 26.04 from the installation media works fine and flawlessly. the laptop (thinkpad e14 gen 6, ryzen 5, radeon) boots fine each time etc. but as soon as i install our usual set of packages, which includes xfce4, all hell breaks loose. xfce4 namely pulls in lightdm and even when gdb3 is chosen over it, i observe the following spiral of events: first boot after a reboot is usually fine. second boot usually gets hung on a "underscore screen of death" where only a single underscore is shown in the upper left corner and the rest is just a black screen. the kernel is still running since ctrl- alt-del works and also REISUB but one cannot do anything else with it, ie no linux console accessible. so the booting usually does not go beyond the third time. i say "usually" since to triage the problem i have now made a fresh install of ubuntu already for the 11th time. always the same story. vanilla install works fine. as soon as (i guess non-wayland x11 stuff is installed) the booting experience is very different each time and finally fails. sometimes instead of the underscore screen i end up with a message about kdump-tools being started and ucsi_acpi USBC000:00: error -ETIMEOUT: PPM failed, but sometimes not. btw, i had to remove "splash" from the kernel options to see this stuff, with splash running the boots end up either spinning for ever, or with underscore black screen, or simply frozen spinner, which unfreezes on ctrl-alt-del and spews out all the shutdown messages. this has been very frustrating indeed, but with this laptop there were glimpses of this starting already with ubuntu 25.04 and then also in 25.10. what helped there was simply to disconnect the thinkpad docking station for boot and connect it back when fully booted and the gdm3 login appears. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic 7.0.0-14.14 ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 09:42:06 2026 InstallationDate: Installed on 2026-04-28 (1 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlp2s0Link: Not connected. MachineType: LENOVO 21M3002TGE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-14-generic root=UUID=28776a6c-f402-431c-ba0d-61e0053cdb0e ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2025 dmi.bios.release: 1.16 dmi.bios.vendor: LENOVO dmi.bios.version: R2KET33W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 21M3002TGE dmi.board.vendor: LENOVO dmi.board.version: ThinkPad dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrR2KET33W(1.16):bd05/09/2025:br1.16:efr1.16:svnLENOVO:pn21M3002TGE:pvrThinkPadE14Gen6:rvnLENOVO:rn21M3002TGE:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21M3_BU_Think_FM_ThinkPadE14Gen6:pfaThinkPadE14Gen6: dmi.product.family: ThinkPad E14 Gen 6 dmi.product.name: 21M3002TGE dmi.product.sku: LENOVO_MT_21M3_BU_Think_FM_ThinkPad E14 Gen 6 dmi.product.version: ThinkPad E14 Gen 6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150621/+subscriptions

[Bug 2151842] Re: aa-rootns.c bypasses apparmor_restrict_unprivileged_userns

** No longer affects: linux (Ubuntu) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2151842 Title: aa-rootns.c bypasses apparmor_restrict_unprivileged_userns Status in AppArmor: New Status in apparmor package in Ubuntu: New Bug description: Please find a way to stop https://github.com/0xdeadbeefnetwork/Copy_Fail2-Electric_Boogaloo/blob/main/aa- rootns.c from working. See also https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/2151831 but the apparmor_restrict_unprivileged_userns bypass is separate from the copy.fail or dirty frag vulnerabilities. This doesn't affect me because I disabled that sysctl to make unshare work, but a fix would reduce the attack surface for others. If a fix isn't readily available, then please disable that sysctl to reduce inconvenience and the illusion of security. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2151842/+subscriptions

[Bug 2152056] [NEW] Lenovo Legion Y9000P IAX10 (17aa:3907) speakers - missing AW88399 amp quirk

Public bug reported: Lenovo Legion Y9000P IAX10, ALC287 + AW88399 amplifier PCI SSID: 17aa:3907 dmesg: "ALC287: picked fixup for PCI SSID 17aa:0000" (no specific quirk match) Result: bottom 2 speakers (woofers) silent, only top tweeters audible Existing patch (not yet upstream): https://github.com/nadimkobeissi/16iax10h-linux-sound-saga ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2152056 Title: Lenovo Legion Y9000P IAX10 (17aa:3907) speakers - missing AW88399 amp quirk Status in linux package in Ubuntu: New Bug description: Lenovo Legion Y9000P IAX10, ALC287 + AW88399 amplifier PCI SSID: 17aa:3907 dmesg: "ALC287: picked fixup for PCI SSID 17aa:0000" (no specific quirk match) Result: bottom 2 speakers (woofers) silent, only top tweeters audible Existing patch (not yet upstream): https://github.com/nadimkobeissi/16iax10h-linux-sound-saga To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152056/+subscriptions

[Bug 2138991] Re: Dell 16 Premium DA16250 webcam (OV02C10) not working - INT3472 GPIO type 0x02 unknown

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ipu6-drivers (Ubuntu Noble) Status: New => Confirmed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2138991 Title: Dell 16 Premium DA16250 webcam (OV02C10) not working - INT3472 GPIO type 0x02 unknown Status in ipu6-drivers package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in ipu6-drivers source package in Noble: Confirmed Status in linux source package in Noble: Confirmed Bug description: ## Description ### Summary The integrated webcam on Dell 16 Premium (DA16250) with Intel Meteor Lake CPU does not work on Ubuntu 24.04 with OEM kernel. The camera sensor (OV02C10) is detected but fails to initialize due to unsupported GPIO type 0x02 in the INT3472 discrete driver. ### System Information - **Hardware:** Dell 16 Premium DA16250 - **CPU:** Intel Core Ultra 9 285H (Meteor Lake) - **Camera Sensor:** OmniVision OV02C10 (ACPI: OVTI02C1:00) - **OS:** Ubuntu 24.04.3 LTS - **Kernel:** 6.14.0-1019-oem ### Steps to Reproduce 1. Install Ubuntu 24.04 on Dell 16 Premium DA16250 2. Install OEM kernel: `sudo apt install linux-oem-24.04` 3. Install IPU6 modules: `sudo apt install linux-modules-ipu6-6.14.0-1019-oem` 4. Install camera HAL: `sudo apt install libcamhal-ipu6epmtl` (from OEM PPA) 5. Reboot and try to use the webcam ### Expected Behavior Webcam should be detected and functional in applications like Cheese, Firefox, Chromium. ### Actual Behavior Camera is detected by the IPU6 driver but fails to initialize. The sensor does not register in the media pipeline. ### Error Messages (from dmesg) ``` int3472-discrete INT3472:0c: GPIO type 0x02 unknown; the sensor may not work intel-ipu6 0000:00:05.0: Found supported sensor OVTI02C1:00 intel-ipu6 0000:00:05.0: Connected 1 cameras ``` ### Error Messages (from GStreamer test) ``` CamHAL[INF] aiqb file name AR0234_TGL_10bits.aiqb CamHAL[ERR] Stream config is not supported. format:V4L2_PIX_FMT_NV12 (1920x1080) ``` The camera HAL loads the wrong config file (AR0234 instead of OV02C10) because the sensor is not bound to the I2C bus. ### Diagnosis The ov02c10 kernel module is loaded but not bound to any device: ``` $ ls /sys/bus/i2c/drivers/ov02c10/ bind module uevent unbind ``` The ACPI device exists and is enabled (status 15): ``` $ cat /sys/bus/acpi/devices/OVTI02C1:00/status 15 ``` But there is no physical_node because the INT3472 GPIO initialization fails. ### Root Cause GPIO type 0x02 is a "strobe" GPIO used for LED/IR control on Meteor Lake systems. The int3472-discrete driver does not recognize this GPIO type, preventing proper camera power-up. ### Existing Kernel Patch A patch exists that adds support for GPIO type 0x02 (strobe): https://patchwork.kernel.org/project/linux-media/patch/20231007021309.9332-1-hao.yao@intel.com/ ### Related Issues - Intel IPU6 drivers: https://github.com/intel/ipu6-drivers/issues/413 - Intel IPU6 drivers: https://github.com/intel/ipu6-drivers/issues/40 - Ubuntu Bug #2117188: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2117188 ### Workarounds Attempted (None Successful) 1. Added `intel_iommu=on` to kernel parameters 2. Fixed /dev/ipu-psys0 permissions with udev rules 3. Installed libcamhal-ipu6epmtl from OEM PPA 4. Tried Dell OEM archive packages ### Request Please backport the INT3472 GPIO strobe patch to the Ubuntu OEM kernel to support Dell 16 Premium and other Meteor Lake laptops with OV02C10 cameras. ## Attachments ### uname -a ``` Linux Dell-16-Premium-DA16250 6.14.0-1019-oem #19-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 18 05:40:21 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux ``` ### CPU Info ``` vendor_id : GenuineIntel cpu family : 6 model : 197 model name : Intel(R) Core(TM) Ultra 9 285H ``` ### lspci (IPU6 device) ``` 0000:00:05.0 Multimedia controller [0480]: Intel Corporation Device [8086:7d19] (rev 05) Subsystem: Dell Device [1028:0ce7] Flags: bus master, fast devsel, latency 0, IRQ 16, IOMMU group 3 Memory at 581c000000 (64-bit, non-prefetchable) [size=16M] Kernel driver in use: intel-ipu6 Kernel modules: intel_ipu6 ``` ### dmesg (camera related) ``` [ 16.744854] int3472-discrete INT3472:0c: GPIO type 0x02 unknown; the sensor may not work [ 16.764935] intel-ipu6 0000:00:05.0: enabling device (0000 -> 0002) [ 16.781627] intel-ipu6 0000:00:05.0: Found supported sensor OVTI02C1:00 [ 16.781717] intel-ipu6 0000:00:05.0: Connected 1 cameras [ 16.784617] intel-ipu6 0000:00:05.0: Sending BOOT_LOAD to CSE [ 16.821495] intel-ipu6 0000:00:05.0: Sending AUTHENTICATE_RUN to CSE [ 16.879001] intel-ipu6 0000:00:05.0: CSE authenticate_run done [ 16.879013] intel-ipu6 0000:00:05.0: IPU6-v4[7d19] hardware version 6 [ 17.565317] intel_ipu6_psys.psys intel_ipu6.psys.40: pkg_dir entry count:8 [ 17.565808] intel_ipu6_psys.psys intel_ipu6.psys.40: psys probe minor: 0 [ 2663.927955] intel-ipu6 0000:00:05.0: IPU6 in secure mode [ 7592.628584] intel-ipu6 0000:00:05.0: IPU6 in secure mode ``` ### Installed packages (camera related) ``` ii gstreamer1.0-icamera 0~git202509260937.4fb31db~ubuntu24.04.7 amd64 ii libcamhal-common 0~git202601200757.9899efa~ubuntu24.04.1 all ii libcamhal-ipu6ep 0~git202601200757.9899efa~ubuntu24.04.1 amd64 ii libcamhal-ipu6epmtl 0~git202601200757.9899efa~ubuntu24.04.1 amd64 ii libcamhal0 0~git202601200757.9899efa~ubuntu24.04.1 amd64 ii linux-image-6.14.0-1019-oem 6.14.0-1019.19 amd64 ii linux-image-6.14.0-37-generic 6.14.0-37.37~24.04.1 amd64 ii linux-image-generic-hwe-24.04 6.14.0-37.37~24.04.1 amd64 ii linux-image-oem-24.04 6.14.0-1019.19 amd64 ii linux-modules-6.14.0-1019-oem 6.14.0-1019.19 amd64 ii linux-modules-6.14.0-37-generic 6.14.0-37.37~24.04.1 amd64 ii linux-modules-extra-6.14.0-37-generic 6.14.0-37.37~24.04.1 amd64 ii linux-modules-ipu6-6.14.0-1019-oem 6.14.0-1019.19 amd64 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2138991/+subscriptions

[Bug 2151831] Re: Dirty Frag LPE security vulnerability

@ebarretto disapproved my merge proposal, so I guess Ubuntu is pursuing 2 kernel patches instead of a kmod-based mitigation. See also https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2151842 I am no longer working on this ticket and will leave it to him or someone who can easily compile the kernel. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2151831 Title: Dirty Frag LPE security vulnerability Status in kmod package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: The dirty frag vulnerability is like the copy.fail vulnerability. See: * https://www.openwall.com/lists/oss-security/2026/05/07/8 * https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md * https://askubuntu.com/q/1566558/1004020 kmod should mitigate this via `install ... /bin/false` like done for copy.fail. linux-* should receive a full patch once that's available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/2151831/+subscriptions

[Bug 2151784] Re: No ALS (ambient light sensor) exposed on ThinkPad T14s Gen 6 – Chicony 04F2:B83F HID sensor hub only provides proximity IIO devices

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2151784 Title: No ALS (ambient light sensor) exposed on ThinkPad T14s Gen 6 – Chicony 04F2:B83F HID sensor hub only provides proximity IIO devices Status in linux package in Ubuntu: New Bug description: On a Lenovo ThinkPad T14s Gen 6, the integrated camera module (Chicony 04F2:B83F) exposes a HID sensor hub that creates two IIO devices, but both appear to be proximity sensors only. No ambient light sensor (ALS) / illuminance channels are exposed to userspace, so desktop auto‑brightness cannot work. This looks similar to other cases where a combined proximity + ALS HID sensor is only partially supported by the HID/IIO stack. System information: Hardware: Lenovo ThinkPad T14s Gen 6 OS: Ubuntu 26.04 LTS (“resolute”) Kernel: Linux Laptopx 7.0.0-15-generic #15-Ubuntu SMP PREEMPT_DYNAMIC Wed Apr 22 16:06:43 UTC 2026 x86_64 GNU/Linux (If you file with ubuntu-bug linux, this will be collected automatically.) Observed behavior: The integrated camera is detected as: Chicony Electronics Co.,Ltd. Integrated Camera (04F2:B83F) hid-sensor-hub 0003:04F2:B83F.0001 HID-SENSOR-200011.2.auto -> iio:device0 HID-SENSOR-200011.4.auto -> iio:device1 Relevant dmesg lines: hid: raw HID events driver (C) Jiri Kosina usbcore: registered new interface driver usbhid usbhid: USB HID core driver hid-generic 0003:04F2:B83F.0001: hiddev0,hidraw0: USB HID v1.11 Device [Chicony Electronics Co.,Ltd. Integrated Camera] on usb-0000:00:14.0-4/input4 hid-sensor-hub 0003:04F2:B83F.0001: hiddev0,hidraw0: USB HID v1.11 Device [Chicony Electronics Co.,Ltd. Integrated Camera] on usb-0000:00:14.0-4/input4 input: Intel HID events as /devices/platform/INTC107B:00/input/input12 hid-sensor-hub 0003:04F2:B83F.0001: No report with id 0xffffffff found hid-sensor-hub 0003:04F2:B83F.0001: No report with id 0xffffffff found hid-sensor-hub 0003:04F2:B83F.0001: No report with id 0xffffffff found udevadm info -a /sys/bus/iio/devices/iio:device0 (excerpt): looking at device '/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.4/0003:04F2:B83F.0001/HID-SENSOR-200011.2.auto/iio:device0': KERNEL=="iio:device0" SUBSYSTEM=="iio" DRIVER=="" ATTR{buffer/data_available}=="0" ATTR{buffer/direction}=="in" ATTR{buffer/enable}=="0" ATTR{buffer/length}=="2" ATTR{buffer/watermark}=="1" ATTR{buffer0/data_available}=="0" ATTR{buffer0/direction}=="in" ATTR{buffer0/enable}=="0" ATTR{buffer0/in_attention_en}=="0" ATTR{buffer0/in_attention_index}=="2" ATTR{buffer0/in_attention_type}=="le:s8/32>>0" ATTR{buffer0/in_proximity0_en}=="0" ATTR{buffer0/in_proximity0_index}=="0" ATTR{buffer0/in_proximity0_type}=="le:s8/32>>0" ATTR{buffer0/in_proximity1_en}=="0" ATTR{buffer0/in_proximity1_index}=="1" udevadm info -a /sys/bus/iio/devices/iio:device1 (excerpt): looking at device '/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.4/0003:04F2:B83F.0001/HID-SENSOR-200011.4.auto/iio:device1': KERNEL=="iio:device1" SUBSYSTEM=="iio" DRIVER=="" ATTR{buffer/data_available}=="0" ATTR{buffer/direction}=="in" ATTR{buffer/enable}=="0" ATTR{buffer/length}=="2" ATTR{buffer/watermark}=="1" ATTR{buffer0/data_available}=="0" ATTR{buffer0/direction}=="in" ATTR{buffer0/enable}=="0" ATTR{buffer0/in_attention_en}=="0" ATTR{buffer0/in_attention_index}=="2" ATTR{buffer0/in_attention_type}=="le:s16/32>>0" ATTR{buffer0/in_proximity0_en}=="0" ATTR{buffer0/in_proximity0_index}=="0" ATTR{buffer0/in_proximity0_type}=="le:s16/32>>0" ATTR{buffer0/in_proximity1_en}=="0" ATTR{buffer0/in_proximity1_index}=="1" Under /sys/bus/iio/devices/iio:device* there are only proximity‑related attributes (in_proximity*, in_attention*). There are no ALS‑related attributes such as in_illuminance*, in_lux*, or anything with light / als in the name. As a result: iio-sensor-proxy does not expose any ALS to userspace. GNOME/KDE auto‑brightness cannot function. There is no ALS data available for user scripts either. Expected behavior: If the camera module / HID sensor hub includes an ALS (which is typical for modern laptop camera modules), I would expect: The HID sensor hub driver and related hid_sensor_* drivers to expose an IIO device with ALS channels (e.g. in_illuminance_raw, in_illuminance_scale, etc.), or A clear indication that the hardware does not provide ALS at all. Right now, only proximity sensors are visible, and ALS (if present) is not exposed. Steps to reproduce: Boot Ubuntu 26.04 on a Lenovo ThinkPad T14s Gen 6. Run: uname -a lsb_release -a dmesg | egrep -i 'hid|sensor|iio' ls /sys/bus/iio/devices ls -R /sys/bus/iio/devices/iio:device* Observe that: Only HID-SENSOR-200011.* devices exist for the Chicony 04F2:B83F camera. IIO attributes are limited to proximity / attention; no ALS / illuminance attributes are present. Impact: Users of this ThinkPad model on Ubuntu cannot use automatic screen brightness based on ambient light. Desktop environments relying on iio-sensor-proxy see no ALS, reducing usability and power efficiency. Test case: On a ThinkPad T14s Gen 6, install Ubuntu 26.04 with the stock linux-image-generic kernel. Log in to a GNOME session. Check: monitor-sensor output (from iio-sensor-proxy). Contents of /sys/bus/iio/devices/iio:device*. Confirm that: No ALS / illuminance readings are available. Only proximity‑related attributes exist. Regression potential: A fix would likely involve adding or adjusting HID/IIO support for the Chicony 04F2:B83F sensor hub. Main regression risk: mis‑interpreting HID descriptors and affecting other devices using the same HID sensor ID. Careful matching on USB VID:PID and/or HID usage pages/IDs should limit the change to this hardware. Additional information / willingness to help: I can provide on request: lsusb -v -d 04f2:b83f Raw HID reports (e.g. from hid-recorder on /dev/hidraw0) Full udevadm info output for the HID and IIO devices I am also happy if this bug is forwarded upstream to the Linux kernel HID/IIO maintainers. Thank you for looking into this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2151784/+subscriptions

[Bug 2151784] [NEW] No ALS (ambient light sensor) exposed on ThinkPad T14s Gen 6 – Chicony 04F2:B83F HID sensor hub only provides proximity IIO devices

Public bug reported: On a Lenovo ThinkPad T14s Gen 6, the integrated camera module (Chicony 04F2:B83F) exposes a HID sensor hub that creates two IIO devices, but both appear to be proximity sensors only. No ambient light sensor (ALS) / illuminance channels are exposed to userspace, so desktop auto‑brightness cannot work. This looks similar to other cases where a combined proximity + ALS HID sensor is only partially supported by the HID/IIO stack. System information: Hardware: Lenovo ThinkPad T14s Gen 6 OS: Ubuntu 26.04 LTS (“resolute”) Kernel: Linux Laptopx 7.0.0-15-generic #15-Ubuntu SMP PREEMPT_DYNAMIC Wed Apr 22 16:06:43 UTC 2026 x86_64 GNU/Linux (If you file with ubuntu-bug linux, this will be collected automatically.) Observed behavior: The integrated camera is detected as: Chicony Electronics Co.,Ltd. Integrated Camera (04F2:B83F) hid-sensor-hub 0003:04F2:B83F.0001 HID-SENSOR-200011.2.auto -> iio:device0 HID-SENSOR-200011.4.auto -> iio:device1 Relevant dmesg lines: hid: raw HID events driver (C) Jiri Kosina usbcore: registered new interface driver usbhid usbhid: USB HID core driver hid-generic 0003:04F2:B83F.0001: hiddev0,hidraw0: USB HID v1.11 Device [Chicony Electronics Co.,Ltd. Integrated Camera] on usb-0000:00:14.0-4/input4 hid-sensor-hub 0003:04F2:B83F.0001: hiddev0,hidraw0: USB HID v1.11 Device [Chicony Electronics Co.,Ltd. Integrated Camera] on usb-0000:00:14.0-4/input4 input: Intel HID events as /devices/platform/INTC107B:00/input/input12 hid-sensor-hub 0003:04F2:B83F.0001: No report with id 0xffffffff found hid-sensor-hub 0003:04F2:B83F.0001: No report with id 0xffffffff found hid-sensor-hub 0003:04F2:B83F.0001: No report with id 0xffffffff found udevadm info -a /sys/bus/iio/devices/iio:device0 (excerpt): looking at device '/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.4/0003:04F2:B83F.0001/HID-SENSOR-200011.2.auto/iio:device0': KERNEL=="iio:device0" SUBSYSTEM=="iio" DRIVER=="" ATTR{buffer/data_available}=="0" ATTR{buffer/direction}=="in" ATTR{buffer/enable}=="0" ATTR{buffer/length}=="2" ATTR{buffer/watermark}=="1" ATTR{buffer0/data_available}=="0" ATTR{buffer0/direction}=="in" ATTR{buffer0/enable}=="0" ATTR{buffer0/in_attention_en}=="0" ATTR{buffer0/in_attention_index}=="2" ATTR{buffer0/in_attention_type}=="le:s8/32>>0" ATTR{buffer0/in_proximity0_en}=="0" ATTR{buffer0/in_proximity0_index}=="0" ATTR{buffer0/in_proximity0_type}=="le:s8/32>>0" ATTR{buffer0/in_proximity1_en}=="0" ATTR{buffer0/in_proximity1_index}=="1" udevadm info -a /sys/bus/iio/devices/iio:device1 (excerpt): looking at device '/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.4/0003:04F2:B83F.0001/HID-SENSOR-200011.4.auto/iio:device1': KERNEL=="iio:device1" SUBSYSTEM=="iio" DRIVER=="" ATTR{buffer/data_available}=="0" ATTR{buffer/direction}=="in" ATTR{buffer/enable}=="0" ATTR{buffer/length}=="2" ATTR{buffer/watermark}=="1" ATTR{buffer0/data_available}=="0" ATTR{buffer0/direction}=="in" ATTR{buffer0/enable}=="0" ATTR{buffer0/in_attention_en}=="0" ATTR{buffer0/in_attention_index}=="2" ATTR{buffer0/in_attention_type}=="le:s16/32>>0" ATTR{buffer0/in_proximity0_en}=="0" ATTR{buffer0/in_proximity0_index}=="0" ATTR{buffer0/in_proximity0_type}=="le:s16/32>>0" ATTR{buffer0/in_proximity1_en}=="0" ATTR{buffer0/in_proximity1_index}=="1" Under /sys/bus/iio/devices/iio:device* there are only proximity‑related attributes (in_proximity*, in_attention*). There are no ALS‑related attributes such as in_illuminance*, in_lux*, or anything with light / als in the name. As a result: iio-sensor-proxy does not expose any ALS to userspace. GNOME/KDE auto‑brightness cannot function. There is no ALS data available for user scripts either. Expected behavior: If the camera module / HID sensor hub includes an ALS (which is typical for modern laptop camera modules), I would expect: The HID sensor hub driver and related hid_sensor_* drivers to expose an IIO device with ALS channels (e.g. in_illuminance_raw, in_illuminance_scale, etc.), or A clear indication that the hardware does not provide ALS at all. Right now, only proximity sensors are visible, and ALS (if present) is not exposed. Steps to reproduce: Boot Ubuntu 26.04 on a Lenovo ThinkPad T14s Gen 6. Run: uname -a lsb_release -a dmesg | egrep -i 'hid|sensor|iio' ls /sys/bus/iio/devices ls -R /sys/bus/iio/devices/iio:device* Observe that: Only HID-SENSOR-200011.* devices exist for the Chicony 04F2:B83F camera. IIO attributes are limited to proximity / attention; no ALS / illuminance attributes are present. Impact: Users of this ThinkPad model on Ubuntu cannot use automatic screen brightness based on ambient light. Desktop environments relying on iio-sensor-proxy see no ALS, reducing usability and power efficiency. Test case: On a ThinkPad T14s Gen 6, install Ubuntu 26.04 with the stock linux-image-generic kernel. Log in to a GNOME session. Check: monitor-sensor output (from iio-sensor-proxy). Contents of /sys/bus/iio/devices/iio:device*. Confirm that: No ALS / illuminance readings are available. Only proximity‑related attributes exist. Regression potential: A fix would likely involve adding or adjusting HID/IIO support for the Chicony 04F2:B83F sensor hub. Main regression risk: mis‑interpreting HID descriptors and affecting other devices using the same HID sensor ID. Careful matching on USB VID:PID and/or HID usage pages/IDs should limit the change to this hardware. Additional information / willingness to help: I can provide on request: lsusb -v -d 04f2:b83f Raw HID reports (e.g. from hid-recorder on /dev/hidraw0) Full udevadm info output for the HID and IIO devices I am also happy if this bug is forwarded upstream to the Linux kernel HID/IIO maintainers. Thank you for looking into this. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2151784 Title: No ALS (ambient light sensor) exposed on ThinkPad T14s Gen 6 – Chicony 04F2:B83F HID sensor hub only provides proximity IIO devices Status in linux package in Ubuntu: New Bug description: On a Lenovo ThinkPad T14s Gen 6, the integrated camera module (Chicony 04F2:B83F) exposes a HID sensor hub that creates two IIO devices, but both appear to be proximity sensors only. No ambient light sensor (ALS) / illuminance channels are exposed to userspace, so desktop auto‑brightness cannot work. This looks similar to other cases where a combined proximity + ALS HID sensor is only partially supported by the HID/IIO stack. System information: Hardware: Lenovo ThinkPad T14s Gen 6 OS: Ubuntu 26.04 LTS (“resolute”) Kernel: Linux Laptopx 7.0.0-15-generic #15-Ubuntu SMP PREEMPT_DYNAMIC Wed Apr 22 16:06:43 UTC 2026 x86_64 GNU/Linux (If you file with ubuntu-bug linux, this will be collected automatically.) Observed behavior: The integrated camera is detected as: Chicony Electronics Co.,Ltd. Integrated Camera (04F2:B83F) hid-sensor-hub 0003:04F2:B83F.0001 HID-SENSOR-200011.2.auto -> iio:device0 HID-SENSOR-200011.4.auto -> iio:device1 Relevant dmesg lines: hid: raw HID events driver (C) Jiri Kosina usbcore: registered new interface driver usbhid usbhid: USB HID core driver hid-generic 0003:04F2:B83F.0001: hiddev0,hidraw0: USB HID v1.11 Device [Chicony Electronics Co.,Ltd. Integrated Camera] on usb-0000:00:14.0-4/input4 hid-sensor-hub 0003:04F2:B83F.0001: hiddev0,hidraw0: USB HID v1.11 Device [Chicony Electronics Co.,Ltd. Integrated Camera] on usb-0000:00:14.0-4/input4 input: Intel HID events as /devices/platform/INTC107B:00/input/input12 hid-sensor-hub 0003:04F2:B83F.0001: No report with id 0xffffffff found hid-sensor-hub 0003:04F2:B83F.0001: No report with id 0xffffffff found hid-sensor-hub 0003:04F2:B83F.0001: No report with id 0xffffffff found udevadm info -a /sys/bus/iio/devices/iio:device0 (excerpt): looking at device '/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.4/0003:04F2:B83F.0001/HID-SENSOR-200011.2.auto/iio:device0': KERNEL=="iio:device0" SUBSYSTEM=="iio" DRIVER=="" ATTR{buffer/data_available}=="0" ATTR{buffer/direction}=="in" ATTR{buffer/enable}=="0" ATTR{buffer/length}=="2" ATTR{buffer/watermark}=="1" ATTR{buffer0/data_available}=="0" ATTR{buffer0/direction}=="in" ATTR{buffer0/enable}=="0" ATTR{buffer0/in_attention_en}=="0" ATTR{buffer0/in_attention_index}=="2" ATTR{buffer0/in_attention_type}=="le:s8/32>>0" ATTR{buffer0/in_proximity0_en}=="0" ATTR{buffer0/in_proximity0_index}=="0" ATTR{buffer0/in_proximity0_type}=="le:s8/32>>0" ATTR{buffer0/in_proximity1_en}=="0" ATTR{buffer0/in_proximity1_index}=="1" udevadm info -a /sys/bus/iio/devices/iio:device1 (excerpt): looking at device '/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.4/0003:04F2:B83F.0001/HID-SENSOR-200011.4.auto/iio:device1': KERNEL=="iio:device1" SUBSYSTEM=="iio" DRIVER=="" ATTR{buffer/data_available}=="0" ATTR{buffer/direction}=="in" ATTR{buffer/enable}=="0" ATTR{buffer/length}=="2" ATTR{buffer/watermark}=="1" ATTR{buffer0/data_available}=="0" ATTR{buffer0/direction}=="in" ATTR{buffer0/enable}=="0" ATTR{buffer0/in_attention_en}=="0" ATTR{buffer0/in_attention_index}=="2" ATTR{buffer0/in_attention_type}=="le:s16/32>>0" ATTR{buffer0/in_proximity0_en}=="0" ATTR{buffer0/in_proximity0_index}=="0" ATTR{buffer0/in_proximity0_type}=="le:s16/32>>0" ATTR{buffer0/in_proximity1_en}=="0" ATTR{buffer0/in_proximity1_index}=="1" Under /sys/bus/iio/devices/iio:device* there are only proximity‑related attributes (in_proximity*, in_attention*). There are no ALS‑related attributes such as in_illuminance*, in_lux*, or anything with light / als in the name. As a result: iio-sensor-proxy does not expose any ALS to userspace. GNOME/KDE auto‑brightness cannot function. There is no ALS data available for user scripts either. Expected behavior: If the camera module / HID sensor hub includes an ALS (which is typical for modern laptop camera modules), I would expect: The HID sensor hub driver and related hid_sensor_* drivers to expose an IIO device with ALS channels (e.g. in_illuminance_raw, in_illuminance_scale, etc.), or A clear indication that the hardware does not provide ALS at all. Right now, only proximity sensors are visible, and ALS (if present) is not exposed. Steps to reproduce: Boot Ubuntu 26.04 on a Lenovo ThinkPad T14s Gen 6. Run: uname -a lsb_release -a dmesg | egrep -i 'hid|sensor|iio' ls /sys/bus/iio/devices ls -R /sys/bus/iio/devices/iio:device* Observe that: Only HID-SENSOR-200011.* devices exist for the Chicony 04F2:B83F camera. IIO attributes are limited to proximity / attention; no ALS / illuminance attributes are present. Impact: Users of this ThinkPad model on Ubuntu cannot use automatic screen brightness based on ambient light. Desktop environments relying on iio-sensor-proxy see no ALS, reducing usability and power efficiency. Test case: On a ThinkPad T14s Gen 6, install Ubuntu 26.04 with the stock linux-image-generic kernel. Log in to a GNOME session. Check: monitor-sensor output (from iio-sensor-proxy). Contents of /sys/bus/iio/devices/iio:device*. Confirm that: No ALS / illuminance readings are available. Only proximity‑related attributes exist. Regression potential: A fix would likely involve adding or adjusting HID/IIO support for the Chicony 04F2:B83F sensor hub. Main regression risk: mis‑interpreting HID descriptors and affecting other devices using the same HID sensor ID. Careful matching on USB VID:PID and/or HID usage pages/IDs should limit the change to this hardware. Additional information / willingness to help: I can provide on request: lsusb -v -d 04f2:b83f Raw HID reports (e.g. from hid-recorder on /dev/hidraw0) Full udevadm info output for the HID and IIO devices I am also happy if this bug is forwarded upstream to the Linux kernel HID/IIO maintainers. Thank you for looking into this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2151784/+subscriptions

[Bug 2151831] Re: Dirty Frag LPE security vulnerability

** Changed in: kmod (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2151831 Title: Dirty Frag LPE security vulnerability Status in kmod package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: The dirty frag vulnerability is like the copy.fail vulnerability. See: * https://www.openwall.com/lists/oss-security/2026/05/07/8 * https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md * https://askubuntu.com/q/1566558/1004020 kmod should mitigate this via `install ... /bin/false` like done for copy.fail. linux-* should receive a full patch once that's available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/2151831/+subscriptions

[Bug 2151831] Re: Dirty Frag LPE security vulnerability

Linkbacks: * https://www.openwall.com/lists/oss-security/2026/05/08/6 * https://github.com/linux-surface/linux-surface/issues/2116 ** Bug watch added: github.com/linux-surface/linux-surface/issues #2116 https://github.com/linux-surface/linux-surface/issues/2116 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2151831 Title: Dirty Frag LPE security vulnerability Status in kmod package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The dirty frag vulnerability is like the copy.fail vulnerability. See: * https://www.openwall.com/lists/oss-security/2026/05/07/8 * https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md * https://askubuntu.com/q/1566558/1004020 kmod should mitigate this via `install ... /bin/false` like done for copy.fail. linux-* should receive a full patch once that's available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/2151831/+subscriptions

[Bug 2151303] Comment bridged from LTC Bugzilla

------- Comment From Raman.Singh5@ibm.com 2026-05-05 05:30 EDT------- Problem Description:- Powepc tests in kselftest failed with following error log: In file included from test-vphn.c:3: In function ?vphn_unpack_associativity?, inlined from ?test_one? at test-vphn.c:371:2, inlined from ?test_vphn? at test-vphn.c:399:9: test-vphn.c:10:33: error: ?be_packed? may be used uninitialized [-Werror=maybe-uninitialized] 10 | #define be16_to_cpup(x) bswap_16(*x) | ^~~~~~~~ vphn.c:42:27: note: in expansion of macro ?be16_to_cpup? 42 | u16 new = be16_to_cpup(field++); | ^~~~~~~~~~~~ In file included from test-vphn.c:19: vphn.c: In function ?test_vphn?: vphn.c:27:16: note: ?be_packed? declared here 27 | __be64 be_packed[VPHN_REGISTER_COUNT]; | ^~~~~~~~~ cc1: all warnings being treated as errors make[2]: *** [../../lib.mk:222: /root/linux/tools/testing/selftests/powerpc/vphn/test-vphn] Error 1 make[2]: Target 'all' not remade because of errors. make[1]: *** [Makefile:40: vphn] Error 2 make[1]: Leaving directory '/root/linux/tools/testing/selftests/powerpc' make: *** [Makefile:203: all] Error 2 make: Leaving directory '/root/linux/tools/testing/selftests' Command used : make -C tools/testing/selftests TARGETS="powerpc" run_tests Comment 2 SEETEENA THOUFEEK 2026-03-27 06:44:05 CDT I had posted a v2 [1] base on the updates on the GCC bug and upstream review. The patch has also been tested by Venkat. [1] https://lore.kernel.org/all/20260313165426.43259-1-amachhiw@linux.ibm.com/ Comment 3 Raman Singh 2026-04-20 00:14:10 CDT The patch is in ppc-next now and should be included in the next PR https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next&id=6e65886fceb23605eff952d6b1975737b4c4b154 The patch is in upstream Linux now: 6e65886fceb2 ("selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15") ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2151303 Title: [Ubuntu 26.04] kselftest failed on Guest Status in linux package in Ubuntu: New Bug description: Powepc tests in kselftest failed with following error log: In file included from test-vphn.c:3: In function ?vphn_unpack_associativity?, inlined from ?test_one? at test-vphn.c:371:2, inlined from ?test_vphn? at test-vphn.c:399:9: test-vphn.c:10:33: error: ?be_packed? may be used uninitialized [-Werror=maybe-uninitialized] 10 | #define be16_to_cpup(x) bswap_16(*x) | ^~~~~~~~ vphn.c:42:27: note: in expansion of macro ?be16_to_cpup? 42 | u16 new = be16_to_cpup(field++); | ^~~~~~~~~~~~ In file included from test-vphn.c:19: vphn.c: In function ?test_vphn?: vphn.c:27:16: note: ?be_packed? declared here 27 | __be64 be_packed[VPHN_REGISTER_COUNT]; | ^~~~~~~~~ cc1: all warnings being treated as errors make[2]: *** [../../lib.mk:222: /root/linux/tools/testing/selftests/powerpc/vphn/test-vphn] Error 1 make[2]: Target 'all' not remade because of errors. make[1]: *** [Makefile:40: vphn] Error 2 make[1]: Leaving directory '/root/linux/tools/testing/selftests/powerpc' make: *** [Makefile:203: all] Error 2 make: Leaving directory '/root/linux/tools/testing/selftests' Command used : make -C tools/testing/selftests TARGETS="powerpc" run_tests With the following patch issue is fixed:- The patch is in upstream Linux now: 6e65886fceb2 ("selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15") ~Amit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2151303/+subscriptions

[Bug 2151273] Re: Kernel panic in path_is_under() at fs/namespace.c when running Docker containers on Ubuntu 26.04 with kernel 7.0.0

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2151273 Title: Kernel panic in path_is_under() at fs/namespace.c when running Docker containers on Ubuntu 26.04 with kernel 7.0.0 Status in linux package in Ubuntu: New Bug description: On Ubuntu 26.04 LTS (kernel 7.0.0-15-generic), the system crashes unpredictably with a general protection fault in path_is_under()+0x50/0x90 (fs/namespace.c). The crash occurs consistently when Docker containers are started or stopped — both privileged Docker and rootless Docker trigger it. The fault address is always a non-canonical (garbage) pointer, indicating memory corruption in the mount/namespace path. Environment: - OS: Ubuntu 26.04 LTS (Resolute Raccoon) - Kernel: 7.0.0-15-generic (also reproduced on 7.0.0-14-generic) - CPU: Intel Core i9-13900K - Docker: 29.4.2 (both privileged and rootless modes tested) - Storage driver: overlay2 / fuse-overlayfs (both tested) Steps to reproduce: 1. Boot into kernel 7.0.0-15-generic 2. Start any Docker container (docker run --rm hello-world is sufficient) 3. Container starts successfully, but during cleanup (mount namespace teardown / overlayfs unmount), the system crashes 4. kdump captures the vmcore; on next boot, systemd-fsck reports dirty filesystems Expected result: Docker container starts and exits cleanly without kernel panic. Actual result: System crashes with the following oops (from /var/crash/202605060957/dmesg): [ 267.477621] Oops: general protection fault, probably for non-canonical address 0xfb4c20ffffffffa4: 0000 [#1] SMP NOPTI [ 267.477631] RIP: 0010:path_is_under+0x50/0x90 [ 267.477644] Call Trace: [ 267.477682] RIP: 0033:0x7bdb36995210 The faulting address changes across crashes (e.g., 0xfb4c20ffffffffa4, 0x856023c00000415d, 0x75efb188ffff8d9c), consistent with use-after- free or memory corruption in the mount tree. What has been ruled out: - Not a hardware/PSU issue: crashes are 100% reproducible with Docker, never happen without Docker running - Not BIOS/ACPI: BIOS was updated; ACPI errors remain but are unrelated - Not split-lock detection: user-space split-lock traps are logged as warnings only; the panic is a GPF, not #AC - Not overlayfs-specific: rootless Docker with fuse-overlayfs storage driver crashes identically - Not container runtime-specific: both Docker (privileged) and rootless Docker trigger it ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: chenxuefei 6485 F.... wireplumber /dev/snd/controlC1: chenxuefei 6485 F.... wireplumber /dev/snd/seq: chenxuefei 6467 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 6 10:44:55 2026 InstallationDate: Installed on 2026-04-27 (9 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Micro-Star International Co., Ltd. MS-7E06 ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-15-generic root=UUID=6eeb9663-e340-4ac4-970b-8729a939c496 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2025 dmi.bios.release: 5.32 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.I0 dmi.board.asset.tag: Default string dmi.board.name: PRO Z790-P (MS-7E06) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.I0:bd07/31/2025:br5.32:svnMicro-StarInternationalCo.,Ltd.:pnMS-7E06:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ790-P(MS-7E06):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuDefaultstring:pfaDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7E06 dmi.product.sku: Default string dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2151273/+subscriptions

[Bug 2151281] Re: ETA for updated Ubuntu EKS AMI with fix for CVE-2026-31431

This is a bug tracking system, not a support forum. Please use discourse.ubuntu.com for support questions. ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2151281 Title: ETA for updated Ubuntu EKS AMI with fix for CVE-2026-31431 Status in linux package in Ubuntu: Invalid Bug description: We would like to know if there is any ETA for a new Ubuntu EKS AMI release that includes the fix for CVE-2026-31431. Currently, we are using the following AMI: ubuntu-eks/k8s_1.33/images/hvm-ssd-gp3/ubuntu- noble-24.04-arm64-server-20260429 Could you please share the expected timeline for the updated AMI availability? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2151281/+subscriptions