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
[Bug 2151281] [NEW] ETA for updated Ubuntu EKS AMI with fix for CVE-2026-31431
*** This bug is a security vulnerability *** Public security bug reported: 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? ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public Security -- 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: New 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
[Bug 2146292] Re: No audio on Intel Panther Lake systems with CS42L43+CS35L57 SoundWire codecs
This bug was fixed in the package linux-oem-6.17 - 6.17.0-1020.20 --------------- linux-oem-6.17 (6.17.0-1020.20) noble; urgency=medium * noble/linux-oem-6.17: 6.17.0-1020.20 -proposed tracker (LP: #2149863) * intel-ipu7 / intel-ipu7-isys modules are shipped unsigned in latest Resolute kernels, breaking Secure Boot systems (LP: #2148718) - [packaging] add intel-ipu7 to signature inclusion list -- Kuan-Ying Lee <kuan-ying.lee@canonical.com> Wed, 22 Apr 2026 13:38:55 +0800 ** Changed in: linux-oem-6.17 (Ubuntu Noble) Status: Fix Committed => Fix Released -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2146292 Title: No audio on Intel Panther Lake systems with CS42L43+CS35L57 SoundWire codecs Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: Won't Fix Status in linux-oem-6.17 source package in Noble: Fix Released Status in linux source package in Questing: In Progress Status in linux-oem-6.17 source package in Questing: Invalid Status in linux source package in Resolute: Fix Released Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: SRU Justification: [ Impact ] No audio on Intel Panther Lake systems with CS42L43 + CS35L57 SoundWire codecs. SOF driver selects a non-existent topology file instead of falling through to function topologies. [ Fix ] Cherry-pick upstream commits: - 3bcdbc221d676 ("ASoC: Intel: soc-acpi-intel-ptl-match: Remove cs42l43 match from sdw link3") - da230e2323527 ("ASoC: SOF: ipc4-topology: set playback channel mask") [ Test Plan ] 1. Boot patched kernel on PTL system with CS42L43+CS35L57 2. Verify audio playback and recording work 3. Verify no UBSAN warnings in dmesg [ Where problems could occur ] No audio on PTL systems with cs42l43-only on SoundWire link 3 (no amplifiers) that previously matched the removed static table entry. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2146292/+subscriptions
[Bug 2142389] Re: amdgpu (R9 380) fails to resume from suspend (deep sleep) – black screen, requires hard reboot
It seems that, in my case, the issue started somewhere between kernels 6.14 and 6.17. I successfully ran Ubuntu 24.04.3 LTS (kernel 6.14.0-0.27) with no issues while running 3D applications. ** Attachment added: "Imagem colada.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142389/+attachment/5968793/+files/Imagem%20colada.png -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2142389 Title: amdgpu (R9 380) fails to resume from suspend (deep sleep) – black screen, requires hard reboot Status in linux package in Ubuntu: Confirmed Bug description: AMDGPU suspend → display black / no video after resume on Radeon R9 380 (No EDID read) Summary: After system suspend from Zorin OS 18 (Ubuntu 24.10 base, kernel 6.17.0-14), the system sometimes resumes but the display remains black (no signal). System continues running (fans/LEDs active), but monitor shows no output. Only hard reboot restores video. Steps to reproduce: Boot Zorin OS 18 (Ubuntu 24.10 kernel 6.17). Suspend system (e.g., via GNOME “Suspend”). Wait short period. Attempt to resume (mouse/keyboard). System wakes but display either shows garbled video or no output. Observed behavior: System appears not crashed (fans/LEDs/keyboard continue). Screen stays black or displays remnants but no usable video. Sometimes resume works, sometimes fails. Relevant log excerpt: amdgpu 0000:01:00.0: [drm] *ERROR* No EDID read. Hardware: Motherboard: Gigabyte B450 AORUS PRO WIFI CPU: AMD Ryzen 5 5500 GPU: AMD Radeon R9 380 Series (Tonga, amdgpu driver) Software environment: Zorin OS 18 Core (Ubuntu 24.10 base) kernel: 6.17.0-14-generic X11 session Workaround currently applied: Suspend disabled. System remains stable without suspend. Note: Bug appears related to video resume rather than system freeze; display subsystem (EDID handshake) may fail after suspend. Additional info: Similar reports of amdgpu black screen / suspend issues exist (e.g., Launchpad #2141216) and community discussions on black screen resume after suspend for AMD GPUs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142389/+subscriptions
[Bug 2151305] [NEW] Kernel panic in i915 driver on Ice Lake (Iris Plus G1, 8086:8a56) since 6.17.0 - Lenovo IdeaPad S340-14IIL
Public bug reported: Hi guys, I am experiencing an issue with my notebook that i cannot boot with the 6.17.0-x kernel. I am not too familiar with kernel stuff, so I had a long debug session with claude, which in the end suggested that it is a bug and created this report for me. HTH and Thx for looking into it: == Problem == Kernel 6.17.0 (tested multiple versions: -20, -23) causes a kernel panic on boot when the i915 driver is loaded. The issue is present since the first 6.17.0 release. Kernel 6.14.0 works fine. == Symptoms == - With i915 in initramfs: Kernel panic before LUKS password prompt (blinking Caps Lock LED) - Without i915 in initramfs: LUKS prompt works, then black screen (i915 never loads) - With nomodeset: System boots, but no GPU acceleration - modprobe i915 (with nomodeset): "ERROR: could not insert 'i915': No such device" == Hardware == - Laptop: Lenovo IdeaPad S340-14IIL - GPU: Intel Iris Plus Graphics G1 (Ice Lake), PCI ID 8086:8a56 (rev 07) - Full-disk encryption: LUKS == Tested kernel parameters (none resolved the panic) == - i915.enable_guc=0 → no panic, but black screen - i915.enable_psr=0 → kernel panic - i915.enable_dc=0 → kernel panic - i915.enable_dc=0 i915.enable_psr=0 → kernel panic - i915.enable_guc=0 i915.enable_psr=0 i915.enable_dc=0 → kernel panic - i915.force_probe=8a56 → kernel panic - i915.panel_use_ssc=0 → kernel panic - i915.fastboot=0 → kernel panic - nomodeset → works (but no GPU acceleration) == Working kernel == 6.14.0 (latest working version) == Steps to reproduce == 1. Boot Lenovo IdeaPad S340-14IIL with kernel 6.17.0-23-generic 2. Observe blinking Caps Lock LED (kernel panic) or black screen == Additional info == - linux-firmware was reinstalled (resolved panic in some cases, but display remained black) - i915 module exists in /lib/modules/6.17.0-23-generic/ and modinfo shows it correctly - i915 firmware files (icl_dmc, icl_guc, icl_huc) are present in /lib/firmware/i915/ - i915 was NOT automatically included in initramfs despite MODULES=most in initramfs.conf (possible related issue) == PCI ID == 00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics G1 (Ice Lake) (rev 07) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: i915 ice-lake kernel-panic regression -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2151305 Title: Kernel panic in i915 driver on Ice Lake (Iris Plus G1, 8086:8a56) since 6.17.0 - Lenovo IdeaPad S340-14IIL Status in linux package in Ubuntu: New Bug description: Hi guys, I am experiencing an issue with my notebook that i cannot boot with the 6.17.0-x kernel. I am not too familiar with kernel stuff, so I had a long debug session with claude, which in the end suggested that it is a bug and created this report for me. HTH and Thx for looking into it: == Problem == Kernel 6.17.0 (tested multiple versions: -20, -23) causes a kernel panic on boot when the i915 driver is loaded. The issue is present since the first 6.17.0 release. Kernel 6.14.0 works fine. == Symptoms == - With i915 in initramfs: Kernel panic before LUKS password prompt (blinking Caps Lock LED) - Without i915 in initramfs: LUKS prompt works, then black screen (i915 never loads) - With nomodeset: System boots, but no GPU acceleration - modprobe i915 (with nomodeset): "ERROR: could not insert 'i915': No such device" == Hardware == - Laptop: Lenovo IdeaPad S340-14IIL - GPU: Intel Iris Plus Graphics G1 (Ice Lake), PCI ID 8086:8a56 (rev 07) - Full-disk encryption: LUKS == Tested kernel parameters (none resolved the panic) == - i915.enable_guc=0 → no panic, but black screen - i915.enable_psr=0 → kernel panic - i915.enable_dc=0 → kernel panic - i915.enable_dc=0 i915.enable_psr=0 → kernel panic - i915.enable_guc=0 i915.enable_psr=0 i915.enable_dc=0 → kernel panic - i915.force_probe=8a56 → kernel panic - i915.panel_use_ssc=0 → kernel panic - i915.fastboot=0 → kernel panic - nomodeset → works (but no GPU acceleration) == Working kernel == 6.14.0 (latest working version) == Steps to reproduce == 1. Boot Lenovo IdeaPad S340-14IIL with kernel 6.17.0-23-generic 2. Observe blinking Caps Lock LED (kernel panic) or black screen == Additional info == - linux-firmware was reinstalled (resolved panic in some cases, but display remained black) - i915 module exists in /lib/modules/6.17.0-23-generic/ and modinfo shows it correctly - i915 firmware files (icl_dmc, icl_guc, icl_huc) are present in /lib/firmware/i915/ - i915 was NOT automatically included in initramfs despite MODULES=most in initramfs.conf (possible related issue) == PCI ID == 00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics G1 (Ice Lake) (rev 07) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2151305/+subscriptions
[Bug 2148768] Re: Fix internal speaker fail to output left/right only on CS42L45+CS35L57 audio solution
This bug is awaiting verification that the linux-oem-6.17/6.17.0-1021.21 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-oem-6.17' to 'verification-done- noble-linux-oem-6.17'. If the problem still exists, change the tag 'verification-needed-noble-linux-oem-6.17' to 'verification-failed- noble-linux-oem-6.17'. 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-oem-6.17-v2 verification-needed-noble-linux-oem-6.17 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148768 Title: Fix internal speaker fail to output left/right only on CS42L45+CS35L57 audio solution Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: Fix Committed Status in linux source package in Resolute: Fix Released Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [Impact] Dell Renegade/Huracan PTL platform with CirrusLogic audio solution CS42L45+CS35L57 only output on both channels but can't output on left/right only. [Fix] Fix the backport commit: ffcd44f1bedb ("ASoC: cs35l56: Support for reading speaker ID from on-chip GPIOs") which may cause the incorrect speaker to be involved. [Test Case] 1. Boot up the machine of new Dell Renegade/Huracan PTL platforms with CirrusLogic audio solution 2. Go to g-s-d and select sound --> output (speaker) --> Test, and click on "Front Left" and "Front Right" 3. Make sure the audio output is from left only and right only [Where problems could occur] It corrects the speaker ID identification for CirrusLogic amplifiers. The risk of regression is limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2148768/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-oracle/6.8.0-1051.52+1)
All autopkgtests for the newly accepted linux-restricted-modules-oracle (6.8.0-1051.52+1) for noble have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-470/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://ubuntu-archive-team.ubuntu.com/proposed- migration/noble/update_excuses.html#linux-restricted-modules-oracle [1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest- failure/ Thank you! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
среда
[Bug 2151281] Re: ETA for updated Ubuntu EKS AMI with fix for CVE-2026-31431
** 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/2151281 Title: ETA for updated Ubuntu EKS AMI with fix for CVE-2026-31431 Status in linux package in Ubuntu: New 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
[Bug 2142682] Comment bridged from LTC Bugzilla
------- Comment From Boris.mail@de.ibm.com 2026-04-15 12:27 EDT------- This feature consists of almost a hundred patches which have been merged into the kernel over time during the past 2 years. As the last required patches went into kernel v7.0, the feature is available since a couple of days with the release of kernel 7.0. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2142682 Title: [26.04 FEAT] [VS2215] KVM: Rewrite gmap using MMU notifiers Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Feature Description: This is an item with the goal to improve the guest memory management for 1M and 2G page sizes using hugetlbfs and transparent huge pages, also in nested KVM setups while retaining backward compatibility. This rework became a requirement for the new hardware work areas and to ease the memory management support for 1M and 2G page sizes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2142682/+subscriptions
[Bug 2151327] [NEW] System hangs at "Reached target sockets.target" on normal boot - X1 Carbon Gen 11 - kernel 6.17 - Intel Xe graphics
Public bug reported: System: Lenovo ThinkPad X1 Carbon Gen 11 Ubuntu version: 25.10 (Questing) Kernel: 6.17.0-22-generic Graphics: Intel Xe (integrated) Problem: System hangs completely after "Reached target sockets.target - Socket Units" on every normal boot. The system is not fully frozen as Ctrl+Alt+Del triggers reboot. No further boot messages appear on screen after sockets.target. Workaround: Booting via GRUB "Advanced options" → Recovery mode → Resume works and produces a functional desktop. Recovery boot cmdline: ro recovery nomodeset dis_ucode_ldr What was tried: Multiple kernel versions (6.17.0-14, 6.17.0-20, 6.17.0-22) — all hang identically Kernel parameters: nomodeset, i915.modeset=0, i915.enable_psr=0, i915.enable_dc=0, dis_ucode_ldr — no effect on normal boot Downgrading intel-microcode to 3.20250512.1ubuntu1 — no effect Blacklisting btusb — no effect Observation from journalctl: Last logged entries before hang show Bluetooth firmware loading successfully, then silence. The i915 driver does not load in recovery mode (simple-framebuffer is used instead). ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2151327 Title: System hangs at "Reached target sockets.target" on normal boot - X1 Carbon Gen 11 - kernel 6.17 - Intel Xe graphics Status in linux package in Ubuntu: New Bug description: System: Lenovo ThinkPad X1 Carbon Gen 11 Ubuntu version: 25.10 (Questing) Kernel: 6.17.0-22-generic Graphics: Intel Xe (integrated) Problem: System hangs completely after "Reached target sockets.target - Socket Units" on every normal boot. The system is not fully frozen as Ctrl+Alt+Del triggers reboot. No further boot messages appear on screen after sockets.target. Workaround: Booting via GRUB "Advanced options" → Recovery mode → Resume works and produces a functional desktop. Recovery boot cmdline: ro recovery nomodeset dis_ucode_ldr What was tried: Multiple kernel versions (6.17.0-14, 6.17.0-20, 6.17.0-22) — all hang identically Kernel parameters: nomodeset, i915.modeset=0, i915.enable_psr=0, i915.enable_dc=0, dis_ucode_ldr — no effect on normal boot Downgrading intel-microcode to 3.20250512.1ubuntu1 — no effect Blacklisting btusb — no effect Observation from journalctl: Last logged entries before hang show Bluetooth firmware loading successfully, then silence. The i915 driver does not load in recovery mode (simple-framebuffer is used instead). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2151327/+subscriptions