UFS: uspi->s_3apb UBSAN: shift-out-of-bounds

Bug #2087853 reported by Alex Tesu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Committed
Low
Agathe Porte
Jammy
Fix Released
Low
Agathe Porte
Noble
Fix Released
Low
Agathe Porte
Oracular
Fix Released
Low
Agathe Porte

Bug Description

[ Impact ]

UBSAN shift-out-of-bounds warning appears on system when some UFS filesystems are mounted.

[ Test Plan ]

Mount the UFS partition with the proposed kernel and verify that the warning
is gone.

[ Where problems could occur ]

Should have zero impact, removes dead code.

[ Original Bug Report ]

Hello!

I have mounted UFS partition (ufstype=ufs2).
Ubuntu allows only read only mounts for UFS by default, so it is mounted with ro option.

I see those messages in the log:

kernel: ------------[ cut here ]------------
kernel: UBSAN: shift-out-of-bounds in /build/linux-21sZ5Q/linux-6.8.0/fs/ufs/super.c:1247:19
kernel: shift exponent 36 is too large for 32-bit type 'int'
kernel: CPU: 3 PID: 2212 Comm: mount Not tainted 6.8.0-48-generic #48-Ubuntu
kernel: Hardware name: SOYO SY-YL B550M/SY-YL B550M, BIOS 5.17 05/19/2023
kernel: Call Trace:
kernel: <TASK>
kernel: dump_stack_lvl+0x76/0xa0
kernel: dump_stack+0x10/0x20
kernel: __ubsan_handle_shift_out_of_bounds+0x199/0x370
kernel: ufs_fill_super.cold+0x16/0x1b7 [ufs]
kernel: ? sb_set_blocksize+0x1d/0x70
kernel: ? __pfx_ufs_fill_super+0x10/0x10 [ufs]
kernel: mount_bdev+0xf6/0x140
kernel: ufs_mount+0x15/0x30 [ufs]
kernel: legacy_get_tree+0x2b/0x60
kernel: vfs_get_tree+0x2a/0x100
kernel: do_new_mount+0x1a0/0x340
kernel: path_mount+0x1e0/0x830
kernel: ? putname+0x5b/0x80
kernel: __x64_sys_mount+0x127/0x160
kernel: x64_sys_call+0x1df5/0x25c0
kernel: do_syscall_64+0x7f/0x180
kernel: ? srso_return_thunk+0x5/0x5f
kernel: ? mntput+0x24/0x50
kernel: ? srso_return_thunk+0x5/0x5f
kernel: ? path_put+0x1e/0x30
kernel: ? srso_return_thunk+0x5/0x5f
kernel: ? do_faccessat+0x1c2/0x2f0
kernel: ? srso_return_thunk+0x5/0x5f
kernel: ? syscall_exit_to_user_mode+0x86/0x260
kernel: ? srso_return_thunk+0x5/0x5f
kernel: ? do_syscall_64+0x8c/0x180
kernel: ? srso_return_thunk+0x5/0x5f
kernel: ? syscall_exit_to_user_mode+0x86/0x260
kernel: ? srso_return_thunk+0x5/0x5f
kernel: ? do_syscall_64+0x8c/0x180
kernel: ? srso_return_thunk+0x5/0x5f
kernel: ? __do_sys_newfstatat+0x53/0x90
kernel: ? srso_return_thunk+0x5/0x5f
kernel: ? srso_return_thunk+0x5/0x5f
kernel: ? syscall_exit_to_user_mode+0x86/0x260
kernel: ? srso_return_thunk+0x5/0x5f
kernel: ? do_syscall_64+0x8c/0x180
kernel: ? srso_return_thunk+0x5/0x5f
kernel: ? irqentry_exit+0x43/0x50
kernel: ? srso_return_thunk+0x5/0x5f
kernel: ? exc_page_fault+0x94/0x1b0
kernel: entry_SYSCALL_64_after_hwframe+0x78/0x80
kernel: RIP: 0033:0x7417b2d2af0e
kernel: Code: 48 8b 0d 0d 7f 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d da 7e 0d 00 f7 d8 64 89 01 48
kernel: RSP: 002b:00007fff1145f4d8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
kernel: RAX: ffffffffffffffda RBX: 000059b6f92e7b00 RCX: 00007417b2d2af0e
kernel: RDX: 000059b6f92e7f10 RSI: 000059b6f92e81b0 RDI: 000059b6f92e83f0
kernel: RBP: 00007fff1145f540 R08: 000059b6f92e8150 R09: 00007fff1145f5b0
kernel: R10: 0000000000000401 R11: 0000000000000246 R12: 000059b6f92e83f0
kernel: R13: 000059b6f92e81b0 R14: 000059b6f92e7f10 R15: 000059b6f92e7c60
kernel: </TASK>
kernel: ---[ end trace ]---

kernel: ------------[ cut here ]------------
kernel: UBSAN: shift-out-of-bounds in /build/linux-21sZ5Q/linux-6.8.0/fs/ufs/super.c:1247:19
kernel: shift exponent 36 is too large for 32-bit type 'int'
kernel: CPU: 6 PID: 2113 Comm: mount Not tainted 6.8.0-48-generic #48-Ubuntu
kernel: Hardware name: SOYO SY-YL B550M/SY-YL B550M, BIOS 5.17 05/19/2023
kernel: Call Trace:
kernel: <TASK>
kernel: dump_stack_lvl+0x76/0xa0
kernel: dump_stack+0x10/0x20
kernel: __ubsan_handle_shift_out_of_bounds+0x199/0x370
kernel: ? srso_return_thunk+0x5/0x5f
kernel: ufs_fill_super.cold+0x16/0x1b7 [ufs]
kernel: ? sb_set_blocksize+0x1d/0x70
kernel: ? __pfx_ufs_fill_super+0x10/0x10 [ufs]
kernel: mount_bdev+0xf6/0x140
kernel: ufs_mount+0x15/0x30 [ufs]
kernel: legacy_get_tree+0x2b/0x60
kernel: vfs_get_tree+0x2a/0x100
kernel: do_new_mount+0x1a0/0x340
kernel: path_mount+0x1e0/0x830
kernel: ? putname+0x5b/0x80
kernel: __x64_sys_mount+0x127/0x160
kernel: x64_sys_call+0x1df5/0x25c0
kernel: do_syscall_64+0x7f/0x180
kernel: ? srso_return_thunk+0x5/0x5f
kernel: ? srso_return_thunk+0x5/0x5f
kernel: ? syscall_exit_to_user_mode+0x86/0x260
kernel: ? srso_return_thunk+0x5/0x5f
kernel: ? do_syscall_64+0x8c/0x180
kernel: ? srso_return_thunk+0x5/0x5f
kernel: ? do_syscall_64+0x8c/0x180
kernel: ? srso_return_thunk+0x5/0x5f
kernel: ? do_syscall_64+0x8c/0x180
kernel: ? srso_return_thunk+0x5/0x5f
kernel: ? irqentry_exit+0x43/0x50
kernel: ? srso_return_thunk+0x5/0x5f
kernel: ? exc_page_fault+0x94/0x1b0
kernel: entry_SYSCALL_64_after_hwframe+0x78/0x80
kernel: RIP: 0033:0x7b616d52af0e
kernel: Code: 48 8b 0d 0d 7f 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d da 7e 0d 00 f7 d8 64 89 01 48
kernel: RSP: 002b:00007ffc10c387b8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
kernel: RAX: ffffffffffffffda RBX: 00005d6eb3bc9b00 RCX: 00007b616d52af0e
kernel: RDX: 00005d6eb3bc9f10 RSI: 00005d6eb3bca1b0 RDI: 00005d6eb3bca3f0
kernel: RBP: 00007ffc10c38820 R08: 00005d6eb3bca150 R09: 00007ffc10c38890
kernel: R10: 0000000000000401 R11: 0000000000000246 R12: 00005d6eb3bca3f0
kernel: R13: 00005d6eb3bca1b0 R14: 00005d6eb3bc9f10 R15: 00005d6eb3bc9c60
kernel: </TASK>
kernel: ---[ end trace ]---

cat /proc/version_signature
Ubuntu 6.8.0-48.48-generic 6.8.12

Tags: kernel-daily-bug kernel-spammed-focal-linux-nvidia-tegra-5.15-v2 kernel-spammed-jammy-linux-mtk-v2 kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 kernel-spammed-jammy-linux-nvidia-tegra-v2 kernel-spammed-jammy-linux-v2 kernel-spammed-noble-linux-aws-6.11-v2 kernel-spammed-noble-linux-aws-fips-v2 kernel-spammed-noble-linux-azure-6.11-v2 kernel-spammed-noble-linux-azure-fips-v2 kernel-spammed-noble-linux-azure-nvidia-v2 kernel-spammed-noble-linux-azure-v2 kernel-spammed-noble-linux-fips-v2 kernel-spammed-noble-linux-gcp-6.11-v2 kernel-spammed-noble-linux-gcp-fips-v2 kernel-spammed-noble-linux-nvidia-6.11-v2 kernel-spammed-noble-linux-nvidia-tegra-pvw-v2 kernel-spammed-noble-linux-nvidia-tegra-v2 kernel-spammed-noble-linux-v2 kernel-spammed-noble-linux-xilinx-v2 kernel-spammed-oracular-linux-intel-v2 kernel-spammed-oracular-linux-v2 ufs verification-needed-focal-linux-nvidia-tegra-5.15 verification-needed-jammy-linux verification-needed-jammy-linux-mtk verification-needed-jammy-linux-nvidia-tegra verification-needed-jammy-linux-nvidia-tegra-igx verification-needed-noble-linux verification-needed-noble-linux-aws-6.11 verification-needed-noble-linux-aws-fips verification-needed-noble-linux-azure verification-needed-noble-linux-azure-6.11 verification-needed-noble-linux-azure-fips verification-needed-noble-linux-azure-nvidia verification-needed-noble-linux-fips verification-needed-noble-linux-gcp-6.11 verification-needed-noble-linux-gcp-fips verification-needed-noble-linux-nvidia-6.11 verification-needed-noble-linux-nvidia-tegra verification-needed-noble-linux-nvidia-tegra-pvw verification-needed-noble-linux-xilinx verification-needed-oracular-linux verification-needed-oracular-linux-intel

CVE References

Revision history for this message
Alex Tesu (atesu) wrote :
Revision history for this message
Agathe Porte (gagath) wrote :

Hi,

Are you able to access the filesystem at all despite the warning?
Are you able to access the filesystem on another system running a different operating system?

From reading the code in fs/ufs/super.c it seems that such high value should never be reached under normal conditions for usb1->fs_bshift, ie. the fs_bshift field of the UFS superblock:

struct ufs_super_block {
        ...
 __fs32 fs_bshift; /* ``lblkno'' calc of logical blkno */
        ...
};

This looks like a corrupted superblock from your filesystem.

Revision history for this message
Alex Tesu (atesu) wrote :

Hello, Agathe Porte!

Yes, I'm able to mount and read that filesystem under Linux.
And I'm able to mount, read and write on that FS under FreeBSD without any warnings.

Revision history for this message
Agathe Porte (gagath) wrote :

After a closer look, this seems to be generated from legacy code in the kernel. Please ignore previous comment. An upstream fix is on its way to the mainline kernel. After it lands then we can pick it and apply it to fix the problem in the Ubuntu kernel.

Changed in linux (Ubuntu):
assignee: nobody → Agathe Porte (gagath)
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Agathe Porte (gagath) wrote (last edit ):

Patch proposal submitted to upstream linux-kernel mailing list:
https://<email address hidden>/T/#u

Revision history for this message
Agathe Porte (gagath) wrote (last edit ):

Patch v2 to target stable kernels as well:
https://<email address hidden>/T/#t

Agathe Porte (gagath)
summary: - Kernel messages about UFS
+ UFS: uspi->s_3apbUBSAN: shift-out-of-bounds
summary: - UFS: uspi->s_3apbUBSAN: shift-out-of-bounds
+ UFS: uspi->s_3apb UBSAN: shift-out-of-bounds
Revision history for this message
Agathe Porte (gagath) wrote :

All kernels seem to be affected. However the priority is low and impact is none, upstream refused to take this as a stable patch: https://<email address hidden>/T/#t

The impact is basically none except for the releases that have UBSAN enabled, in which case it might show this warning.

Patch v3 without stable Cc: https://<email address hidden>/T/#t

Changed in linux (Ubuntu Oracular):
status: New → Triaged
importance: Undecided → Low
assignee: nobody → Agathe Porte (gagath)
Changed in linux (Ubuntu Noble):
status: New → Triaged
importance: Undecided → Low
assignee: nobody → Agathe Porte (gagath)
Changed in linux (Ubuntu Jammy):
status: New → Triaged
importance: Undecided → Low
assignee: nobody → Agathe Porte (gagath)
Changed in linux (Ubuntu Focal):
status: New → Won't Fix
Changed in linux (Ubuntu Bionic):
status: New → Won't Fix
Changed in linux (Ubuntu Xenial):
status: New → Won't Fix
Changed in linux (Ubuntu Trusty):
status: New → Won't Fix
Changed in linux (Ubuntu Focal):
importance: Undecided → Low
Changed in linux (Ubuntu Xenial):
importance: Undecided → Low
Changed in linux (Ubuntu Bionic):
importance: Undecided → Low
Changed in linux (Ubuntu Trusty):
importance: Undecided → Low
no longer affects: linux (Ubuntu Trusty)
no longer affects: linux (Ubuntu Xenial)
no longer affects: linux (Ubuntu Bionic)
no longer affects: linux (Ubuntu Focal)
Revision history for this message
Agathe Porte (gagath) wrote :

Removing old releases that will not need the fix in target series because they do not have CONFIG_UBSAN enabled.

Revision history for this message
Agathe Porte (gagath) wrote :

Filled SRU template for bug.

description: updated
Changed in linux (Ubuntu Jammy):
status: Triaged → In Progress
Changed in linux (Ubuntu Oracular):
status: Triaged → In Progress
Changed in linux (Ubuntu Noble):
status: Triaged → In Progress
Revision history for this message
Agathe Porte (gagath) wrote (last edit ):
Revision history for this message
Agathe Porte (gagath) wrote :

Marking as fix committed for the devel release because the patch has reached linux-next and will be imported at some point in the future.

Changed in linux (Ubuntu):
status: Triaged → Fix Committed
Stefan Bader (smb)
Changed in linux (Ubuntu Oracular):
status: In Progress → Fix Committed
Changed in linux (Ubuntu Noble):
status: In Progress → Fix Committed
Changed in linux (Ubuntu Jammy):
status: In Progress → Fix Committed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux/5.15.0-132.143 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-jammy-linux' to 'verification-done-jammy-linux'. If the problem still exists, change the tag 'verification-needed-jammy-linux' to 'verification-failed-jammy-linux'.

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-jammy-linux-v2 verification-needed-jammy-linux
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux/6.11.0-17.17 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-oracular-linux' to 'verification-done-oracular-linux'. If the problem still exists, change the tag 'verification-needed-oracular-linux' to 'verification-failed-oracular-linux'.

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-oracular-linux-v2 verification-needed-oracular-linux
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux/6.8.0-53.55 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' to 'verification-done-noble-linux'. If the problem still exists, change the tag 'verification-needed-noble-linux' to 'verification-failed-noble-linux'.

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-v2 verification-needed-noble-linux
Revision history for this message
Marietto (marietto2008) wrote :

On Ubuntu 24.04 :

34539.429634] ------------[ cut here ]------------
[34539.429635] UBSAN: shift-out-of-bounds in /build/linux-vCyKs5/linux-6.8.0/fs/ufs/super.c:1247:19
[34539.429637] shift exponent 36 is too large for 32-bit type 'int'
[34539.429639] CPU: 7 PID: 29594 Comm: mount Tainted: P O 6.8.0-51-generic #52-Ubuntu
[34539.429641] Hardware name: Gigabyte Technology Co., Ltd. Z390 AORUS PRO/Z390 AORUS PRO-CF, BIOS F12g GA9 06/08/2020
[34539.429642] Call Trace:
[34539.429644] <TASK>
[34539.429646] dump_stack_lvl+0x76/0xa0
[34539.429649] dump_stack+0x10/0x20
[34539.429650] __ubsan_handle_shift_out_of_bounds+0x199/0x370
[34539.429654] ufs_fill_super.cold+0x16/0x1b7 [ufs]
[34539.429658] ? sb_set_blocksize+0x1d/0x70
[34539.429682] ? __pfx_ufs_fill_super+0x10/0x10 [ufs]
[34539.429685] mount_bdev+0xf3/0x140
[34539.429688] ufs_mount+0x15/0x30 [ufs]
[34539.429711] legacy_get_tree+0x28/0x60
[34539.429714] vfs_get_tree+0x27/0x100
[34539.429716] do_new_mount+0x1a0/0x340
[34539.429718] path_mount+0x1e0/0x830
[34539.429719] ? putname+0x5b/0x80
[34539.429721] __x64_sys_mount+0x127/0x160
[34539.429723] x64_sys_call+0x1e57/0x25a0
[34539.429725] do_syscall_64+0x7f/0x180
[34539.429728] ? put_fs_context+0xff/0x1c0
[34539.429730] ? do_new_mount+0x10d/0x340
[34539.429731] ? rseq_get_rseq_cs+0x22/0x280
[34539.429753] ? rseq_ip_fixup+0x90/0x1f0
[34539.429755] ? syscall_exit_to_user_mode+0x86/0x260
[34539.429757] ? do_syscall_64+0x8c/0x180
[34539.429758] ? do_faccessat+0x1c2/0x2f0
[34539.429780] ? syscall_exit_to_user_mode+0x86/0x260
[34539.429782] ? do_syscall_64+0x8c/0x180
[34539.429783] ? __do_sys_newfstatat+0x53/0x90
[34539.429786] ? syscall_exit_to_user_mode+0x86/0x260
[34539.429787] ? do_syscall_64+0x8c/0x180
[34539.429807] ? syscall_exit_to_user_mode+0x86/0x260
[34539.429809] ? do_syscall_64+0x8c/0x180
[34539.429810] ? irqentry_exit_to_user_mode+0x7b/0x260
[34539.429812] ? irqentry_exit+0x43/0x50
[34539.429813] ? clear_bhb_loop+0x15/0x70
[34539.429815] ? clear_bhb_loop+0x15/0x70
[34539.429816] ? clear_bhb_loop+0x15/0x70
[34539.429817] entry_SYSCALL_64_after_hwframe+0x78/0x80
[34539.429819] RIP: 0033:0x7689eff2af0e
[34539.429838] Code: 48 8b 0d 0d 7f 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d da 7e 0d 00 f7 d8 64 89 01 48
[34539.429839] RSP: 002b:00007ffd8f391668 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
[34539.429841] RAX: ffffffffffffffda RBX: 0000575a9b52abe0 RCX: 00007689eff2af0e
[34539.429842] RDX: 0000575a9b52b070 RSI: 0000575a9b52b0b0 RDI: 0000575a9b52b090
[34539.429843] RBP: 00007ffd8f3916d0 R08: 0000575a9b52be30 R09: 0000000000000007
[34539.429844] R10: 0000000000000001 R11: 0000000000000246 R12: 0000575a9b52b090
[34539.429845] R13: 0000575a9b52b0b0 R14: 0000575a9b52b070 R15: 0000575a9b52ad40
[34539.429846] </TASK>
[34539.429847] ---[ end trace ]---
[35018.100057] ufs: error (device sdc2): ufs_check_page: bad entry in directory #19957332: rec_len is smaller than minimal - offset=512, rec_len=0, name_len=0
[35018.100082] ufs: error (device sdc2): ufs_readdir: bad page in #19957332

Revision history for this message
Agathe Porte (gagath) wrote :

Hello Marietto, you need to enable "proposed" and install the proposed kernel linux/6.8.0-53.55 as explained by the bot. The issue still happens because you are running 6.8.0-51-generic instead of the kernel that has the fix.

Can you install the proposed kernel and check that the error is gone?

Thanks.

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-intel/6.11.0-1007.7 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-oracular-linux-intel' to 'verification-done-oracular-linux-intel'. If the problem still exists, change the tag 'verification-needed-oracular-linux-intel' to 'verification-failed-oracular-linux-intel'.

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-oracular-linux-intel-v2 verification-needed-oracular-linux-intel
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (73.0 KiB)

This bug was fixed in the package linux - 6.8.0-53.55

---------------
linux (6.8.0-53.55) noble; urgency=medium

  * noble/linux: 6.8.0-53.55 -proposed tracker (LP: #2093677)

  * Packaging resync (LP: #1786013)
    - [Packaging] debian.master/dkms-versions -- update from kernel-versions
      (main/2025.01.13)

  * generate and ship vmlinux.h to allow packages to build BPF CO-RE
    (LP: #2050083)
    - [Packaging] add linux-bpf-dev package
    - [Packaging] do not attempt to generate BTF header on armhf

  * Unable to boot as a guest on VMware ESX (LP: #2091941)
    - ptp/vmware: Use VMware hypercall API
    - input/vmmouse: Use VMware hypercall API
    - drm/vmwgfx: Use VMware hypercall API
    - x86/vmware: Use VMware hypercall API
    - x86/vmware: Correct macro names
    - x86/vmware: Remove legacy VMWARE_HYPERCALL* macros

  * When /dev/vmbus/hv_kvp is not present, disable hv-kvp-daemon (LP: #2091744)
    - [Packaging] disable hv-kvp-daemon if needed

  * Backport "netkit: Add option for scrubbing skb meta data" to 6.8
    (LP: #2091184)
    - netkit: Add option for scrubbing skb meta data

  * KVM: Cache CPUID at KVM.ko module init to reduce latency of VM-Enter and VM-
    Exit (LP: #2093146)
    - KVM: x86: Cache CPUID.0xD XSTATE offsets+sizes during module init

  * [SRU] add support of QCA BT 0489:e0fc (LP: #2085406)
    - Bluetooth: btusb: add Foxconn 0xe0fc for Qualcomm WCN785x

  * ice driver RTNL assertion failed warning on shutdown/reboot (LP: #2091107)
    - ice: Remove and readd netdev during devlink reload

  * vfio_pci soft lockup on VM start while using PCIe passthrough (LP: #2089306)
    - SAUCE: Revert "vfio/pci: Insert full vma on mmap'd MMIO fault"
    - SAUCE: Revert "vfio/pci: Use unmap_mapping_range()"

  * [SRU] Fix error of resume on rtl8168fp (LP: #2087507)
    - r8169: avoid unsolicited interrupts

  * [SRU] power: intel_pstate: HWP interrupt support for maximum ratio changed
    (LP: #2090852)
    - x86/cpufeatures: Add HWP highest perf change feature flag
    - cpufreq: intel_pstate: Support highest performance change interrupt

  * Noble update: upstream stable patchset 2024-11-29 (LP: #2089884)
    - static_call: Handle module init failure correctly in
      static_call_del_module()
    - static_call: Replace pointless WARN_ON() in static_call_module_notify()
    - jump_label: Simplify and clarify static_key_fast_inc_cpus_locked()
    - jump_label: Fix static_key_slow_dec() yet again
    - scsi: st: Fix input/output error on empty drive reset
    - scsi: pm8001: Do not overwrite PCI queue mapping
    - drm/amdgpu: Fix get each xcp macro
    - mailbox: rockchip: fix a typo in module autoloading
    - mailbox: bcm2835: Fix timeout during suspend mode
    - ceph: remove the incorrect Fw reference check when dirtying pages
    - ieee802154: Fix build error
    - net: sparx5: Fix invalid timestamps
    - net/mlx5: Fix error path in multi-packet WQE transmit
    - net/mlx5: Added cond_resched() to crdump collection
    - net/mlx5e: Fix NULL deref in mlx5e_tir_builder_alloc()
    - net/mlx5e: Fix crash caused by calling __xfrm_state_delete() twice
    - netfilter: uapi: NFTA_FLOWTABLE_HOOK is NLA_NESTED
    - net...

Changed in linux (Ubuntu Noble):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (254.6 KiB)

This bug was fixed in the package linux - 6.11.0-18.18

---------------
linux (6.11.0-18.18) oracular; urgency=medium

  * CVE-2025-0927
    - SAUCE: fs: hfs/hfsplus: add key_len boundary check to hfs_bnode_read_key

linux (6.11.0-17.17) oracular; urgency=medium

  * oracular/linux: 6.11.0-17.17 -proposed tracker (LP: #2093643)

  * Packaging resync (LP: #1786013)
    - [Packaging] debian.master/dkms-versions -- update from kernel-versions
      (main/2025.01.13)

  * When /dev/vmbus/hv_kvp is not present, disable hv-kvp-daemon (LP: #2091744)
    - [Packaging] disable hv-kvp-daemon if needed

  * Backport "netkit: Add option for scrubbing skb meta data" to 6.8
    (LP: #2091184)
    - netkit: Add option for scrubbing skb meta data

  * KVM: Cache CPUID at KVM.ko module init to reduce latency of VM-Enter and VM-
    Exit (LP: #2093146)
    - KVM: x86: Cache CPUID.0xD XSTATE offsets+sizes during module init

  * [SRU] add support of QCA BT 0489:e0fc (LP: #2085406)
    - Bluetooth: btusb: add Foxconn 0xe0fc for Qualcomm WCN785x

  * oracular: ubuntu_boot lib/dynamic_queue_limits.c:99! (LP: #2089684)
    - virtio_net: correct netdev_tx_reset_queue() invocation point
    - virtio_ring: add a func argument 'recycle_done' to virtqueue_resize()
    - virtio_net: ensure netdev_tx_reset_queue is called on tx ring resize

  * Failed to probe for OVTI02C1: chip id mismatch: 560243!=0 (LP: #2090932)
    - SAUCE: ACPI: scan: Update HID for new platform

  * Bluetooth[8086:a876] crash with "hci0: Failed to read MSFT supported
    features (-110)" (LP: #2085485)
    - Bluetooth: btintel_pcie: Add recovery mechanism

  * Poor bluetooth performance on Lenovo X13s (LP: #2089357)
    - SAUCE: Bluetooth: qca: Support downloading board ID specific NVM for WCN6855

  * vfio_pci soft lockup on VM start while using PCIe passthrough (LP: #2089306)
    - SAUCE: Revert "mm: use rwsem assertion macros for mmap_lock"
    - SAUCE: Revert "vfio/pci: Insert full vma on mmap'd MMIO fault"
    - SAUCE: Revert "vfio/pci: Use unmap_mapping_range()"

  * Oracular update: v6.11.11 upstream stable release (LP: #2091655)
    - wifi: mac80211: Fix setting txpower with emulate_chanctx
    - wifi: cfg80211: Add wiphy_delayed_work_pending()
    - wifi: mac80211: Convert color collision detection to wiphy work
    - wifi: radiotap: Avoid -Wflex-array-member-not-at-end warnings
    - spi: stm32: fix missing device mode capability in stm32mp25
    - ASoC: codecs: rt5640: Always disable IRQs from rt5640_cancel_work()
    - ASoC: Intel: bytcr_rt5640: Add support for non ACPI instantiated codec
    - ASoC: Intel: bytcr_rt5640: Add DMI quirk for Vexia Edu Atla 10 tablet
    - ASoC: Intel: sst: Support LPE0F28 ACPI HID
    - wifi: iwlwifi: mvm: Use the sync timepoint API in suspend
    - wifi: iwlwifi: mvm: SAR table alignment
    - mac80211: fix user-power when emulating chanctx
    - usb: add support for new USB device ID 0x17EF:0x3098 for the r8152 driver
    - usb: typec: use cleanup facility for 'altmodes_node'
    - selftests/watchdog-test: Fix system accidentally reset after watchdog-test
    - ALSA: hda/realtek: Add subwoofer quirk for Infinix ZERO BOOK 13
    - ASoC: codecs: wcd937x: ...

Changed in linux (Ubuntu Oracular):
status: Fix Committed → Fix Released
Revision history for this message
Timo Aaltonen (tjaalton) wrote : Update Released

The verification of the Stable Release Update for linux has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (30.0 KiB)

This bug was fixed in the package linux - 5.15.0-133.144

---------------
linux (5.15.0-133.144) jammy; urgency=medium

  * CVE-2025-0927
    - SAUCE: fs: hfs/hfsplus: add key_len boundary check to hfs_bnode_read_key

linux (5.15.0-132.143) jammy; urgency=medium

  * jammy/linux: 5.15.0-132.143 -proposed tracker (LP: #2093735)

  * Packaging resync (LP: #1786013)
    - [Packaging] debian.master/dkms-versions -- update from kernel-versions
      (main/2025.01.13)

  * KVM: Cache CPUID at KVM.ko module init to reduce latency of VM-Enter and VM-
    Exit (LP: #2093146)
    - kvm: x86: Fix xstate_required_size() to follow XSTATE alignment rule
    - KVM: x86: Cache CPUID.0xD XSTATE offsets+sizes during module init

  * Jammy update: v5.15.173 upstream stable release (LP: #2089541)
    - 9p: Avoid creating multiple slab caches with the same name
    - irqchip/ocelot: Fix trigger register address
    - block: Fix elevator_get_default() checking for NULL q->tag_set
    - HID: multitouch: Add support for B2402FVA track point
    - HID: multitouch: Add quirk for HONOR MagicBook Art 14 touchpad
    - bpf: use kvzmalloc to allocate BPF verifier environment
    - crypto: marvell/cesa - Disable hash algorithms
    - sound: Make CONFIG_SND depend on INDIRECT_IOMEM instead of UML
    - drm/vmwgfx: Limit display layout ioctl array size to
      VMWGFX_NUM_DISPLAY_UNITS
    - powerpc/powernv: Free name on error in opal_event_init()
    - vDPA/ifcvf: Fix pci_read_config_byte() return code handling
    - fs: Fix uninitialized value issue in from_kuid and from_kgid
    - HID: multitouch: Add quirk for Logitech Bolt receiver w/ Casa touchpad
    - HID: lenovo: Add support for Thinkpad X1 Tablet Gen 3 keyboard
    - net: usb: qmi_wwan: add Fibocom FG132 0x0112 composition
    - md/raid10: improve code of mrdev in raid10_sync_request
    - mm/memory: add non-anonymous page check in the copy_present_page()
    - udf: Allocate name buffer in directory iterator on heap
    - udf: Avoid directory type conversion failure due to ENOMEM
    - 9p: fix slab cache name creation for real
    - Linux 5.15.173

  * Jammy update: v5.15.173 upstream stable release (LP: #2089541) //
    CVE-2024-41080
    - io_uring: fix possible deadlock in io_register_iowq_max_workers()

  * Jammy update: v5.15.172 upstream stable release (LP: #2089533)
    - arm64: dts: rockchip: Fix rt5651 compatible value on rk3399-sapphire-
      excavator
    - arm64: dts: rockchip: Remove hdmi's 2nd interrupt on rk3328
    - arm64: dts: rockchip: Fix bluetooth properties on Rock960 boards
    - arm64: dts: rockchip: Remove #cooling-cells from fan on Theobroma lion
    - arm64: dts: rockchip: Fix LED triggers on rk3308-roc-cc
    - arm64: dts: imx8mp: correct sdhc ipg clk
    - ARM: dts: rockchip: fix rk3036 acodec node
    - ARM: dts: rockchip: drop grf reference from rk3036 hdmi
    - ARM: dts: rockchip: Fix the spi controller on rk3036
    - ARM: dts: rockchip: Fix the realtek audio codec on rk3036-kylin
    - NFSv3: only use NFS timeout for MOUNT when protocols are compatible
    - NFS: Add a tracepoint to show the results of nfs_set_cache_invalid()
    - NFSv3: handle out-of-order write replies.
    - ...

Changed in linux (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-nvidia-tegra/6.8.0-1003.3 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
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-nvidia-tegra-pvw/6.8.0-1004.4 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-pvw' to 'verification-done-noble-linux-nvidia-tegra-pvw'. If the problem still exists, change the tag 'verification-needed-noble-linux-nvidia-tegra-pvw' to 'verification-failed-noble-linux-nvidia-tegra-pvw'.

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-pvw-v2 verification-needed-noble-linux-nvidia-tegra-pvw
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-gcp-6.11/6.11.0-1011.11~24.04.1 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-gcp-6.11' to 'verification-done-noble-linux-gcp-6.11'. If the problem still exists, change the tag 'verification-needed-noble-linux-gcp-6.11' to 'verification-failed-noble-linux-gcp-6.11'.

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-gcp-6.11-v2 verification-needed-noble-linux-gcp-6.11
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-azure/6.8.0-1025.30 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-azure' to 'verification-done-noble-linux-azure'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure' to 'verification-failed-noble-linux-azure'.

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-azure-v2 verification-needed-noble-linux-azure
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-nvidia-6.11/6.11.0-1004.4 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-6.11' to 'verification-done-noble-linux-nvidia-6.11'. If the problem still exists, change the tag 'verification-needed-noble-linux-nvidia-6.11' to 'verification-failed-noble-linux-nvidia-6.11'.

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-6.11-v2 verification-needed-noble-linux-nvidia-6.11
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-azure-6.11/6.11.0-1012.12~24.04.1 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-azure-6.11' to 'verification-done-noble-linux-azure-6.11'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure-6.11' to 'verification-failed-noble-linux-azure-6.11'.

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-azure-6.11-v2 verification-needed-noble-linux-azure-6.11
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-nvidia-tegra/5.15.0-1033.33 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-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-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-jammy-linux-nvidia-tegra-v2 verification-needed-jammy-linux-nvidia-tegra
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-nvidia-tegra-igx/5.15.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-jammy-linux-nvidia-tegra-igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.

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-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-azure-nvidia/6.8.0-1014.15 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-azure-nvidia' to 'verification-done-noble-linux-azure-nvidia'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-failed-noble-linux-azure-nvidia'.

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-azure-nvidia-v2 verification-needed-noble-linux-azure-nvidia
Juerg Haefliger (juergh)
tags: added: kernel-daily-bug
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-aws-6.11/6.11.0-1013.14~24.04.1 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-aws-6.11' to 'verification-done-noble-linux-aws-6.11'. If the problem still exists, change the tag 'verification-needed-noble-linux-aws-6.11' to 'verification-failed-noble-linux-aws-6.11'.

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-aws-6.11-v2 verification-needed-noble-linux-aws-6.11
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-mtk/5.15.0-1039.47 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-jammy-linux-mtk' to 'verification-done-jammy-linux-mtk'. If the problem still exists, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'.

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-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-nvidia-tegra-5.15/5.15.0-1039.39~20.04.1 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-focal-linux-nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia-tegra-5.15'.

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-focal-linux-nvidia-tegra-5.15-v2 verification-needed-focal-linux-nvidia-tegra-5.15
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-fips/6.8.0-72.72+fips1 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-fips' to 'verification-done-noble-linux-fips'. If the problem still exists, change the tag 'verification-needed-noble-linux-fips' to 'verification-failed-noble-linux-fips'.

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-fips-v2 verification-needed-noble-linux-fips
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-aws-fips/6.8.0-1034.36+fips1 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-aws-fips' to 'verification-done-noble-linux-aws-fips'. If the problem still exists, change the tag 'verification-needed-noble-linux-aws-fips' to 'verification-failed-noble-linux-aws-fips'.

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-aws-fips-v2 verification-needed-noble-linux-aws-fips
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-gcp-fips/6.8.0-1035.37+fips1 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-gcp-fips' to 'verification-done-noble-linux-gcp-fips'. If the problem still exists, change the tag 'verification-needed-noble-linux-gcp-fips' to 'verification-failed-noble-linux-gcp-fips'.

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-gcp-fips-v2 verification-needed-noble-linux-gcp-fips
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-xilinx/6.8.0-1017.18 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-xilinx' to 'verification-done-noble-linux-xilinx'. If the problem still exists, change the tag 'verification-needed-noble-linux-xilinx' to 'verification-failed-noble-linux-xilinx'.

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-xilinx-v2 verification-needed-noble-linux-xilinx
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-azure-fips/6.8.0-1034.39+fips1 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-azure-fips' to 'verification-done-noble-linux-azure-fips'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure-fips' to 'verification-failed-noble-linux-azure-fips'.

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-azure-fips-v2 verification-needed-noble-linux-azure-fips
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.