This bug was fixed in the package linux-oem-6.5 - 6.5.0-1006.6 --------------- linux-oem-6.5 (6.5.0-1006.6) jammy; urgency=medium
* jammy/linux-oem-6.5: 6.5.0-1006.6 -proposed tracker (LP: #2039056) * No external output when hotplugging to a DP monitor after the monitor went to sleep for AMD 6300 GPU (LP: #2038981) - drm/amd: Fix detection of _PR3 on the PCIe root port - SAUCE: usb: typec: ucsi: Use GET_CAPABILITY attributes data to set power supply scope * drm/i915/gsc: define gsc fw (LP: #2038641) - drm/i915/gsc: define gsc fw * Add SoF topology support on Intel RaptorLake DELL SKU 0C11 (LP: #2038263) - SAUCE: ASoC: Intel: soc-acpi-intel-rpl-match: add rt711-l0-rt1316-l12 support * Fix ADL: System enabled AHCI can't get into s0ix when attached ODD (LP: #2037493) - SAUCE: ata: ahci: Add Intel Alder Lake-P AHCI controller to low power chipsets list * Realtek 8852CE WiFi 6E country code udpates (LP: #2037273) - wifi: rtw89: regd: update regulatory map to R64-R43 * Fix RCU warning on AMD laptops (LP: #2036377) - power: supply: core: Use blocking_notifier_call_chain to avoid RCU complaint [ Ubuntu: 6.5.0-9.9 ] * mantic/linux: 6.5.0-9.9 -proposed tracker (LP: #2038687) * update apparmor and LSM stacking patch set (LP: #2028253) - re-apply apparmor 4.0.0 * Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature (LP: #2038567) - SAUCE: apparmor: Make apparmor_restrict_unprivileged_unconfined opt-in [ Ubuntu: 6.5.0-8.8 ] * mantic/linux: 6.5.0-8.8 -proposed tracker (LP: #2038577) * update apparmor and LSM stacking patch set (LP: #2028253) - SAUCE: apparmor3.2.0 [02/60]: rename SK_CTX() to aa_sock and make it an inline fn - SAUCE: apparmor3.2.0 [05/60]: Add sysctls for additional controls of unpriv userns restrictions - SAUCE: apparmor3.2.0 [08/60]: Stacking v38: LSM: Identify modules by more than name - SAUCE: apparmor3.2.0 [09/60]: Stacking v38: LSM: Add an LSM identifier for external use - SAUCE: apparmor3.2.0 [10/60]: Stacking v38: LSM: Identify the process attributes for each module - SAUCE: apparmor3.2.0 [11/60]: Stacking v38: LSM: Maintain a table of LSM attribute data - SAUCE: apparmor3.2.0 [12/60]: Stacking v38: proc: Use lsmids instead of lsm names for attrs - SAUCE: apparmor3.2.0 [13/60]: Stacking v38: integrity: disassociate ima_filter_rule from security_audit_rule - SAUCE: apparmor3.2.0 [14/60]: Stacking v38: LSM: Infrastructure management of the sock security - SAUCE: apparmor3.2.0 [15/60]: Stacking v38: LSM: Add the lsmblob data structure. - SAUCE: apparmor3.2.0 [16/60]: Stacking v38: LSM: provide lsm name and id slot mappings - SAUCE: apparmor3.2.0 [17/60]: Stacking v38: IMA: avoid label collisions with stacked LSMs - SAUCE: apparmor3.2.0 [18/60]: Stacking v38: LSM: Use lsmblob in security_audit_rule_match - SAUCE: apparmor3.2.0 [19/60]: Stacking v38: LSM: Use lsmblob in security_kernel_act_as - SAUCE: apparmor3.2.0 [20/60]: Stacking v38: LSM: Use lsmblob in security_secctx_to_secid - SAUCE: apparmor3.2.0 [21/60]: Stacking v38: LSM: Use lsmblob in security_secid_to_secctx - SAUCE: apparmor3.2.0 [22/60]: Stacking v38: LSM: Use lsmblob in security_ipc_getsecid - SAUCE: apparmor3.2.0 [23/60]: Stacking v38: LSM: Use lsmblob in security_current_getsecid - SAUCE: apparmor3.2.0 [24/60]: Stacking v38: LSM: Use lsmblob in security_inode_getsecid - SAUCE: apparmor3.2.0 [25/60]: Stacking v38: LSM: Use lsmblob in security_cred_getsecid - SAUCE: apparmor3.2.0 [26/60]: Stacking v38: LSM: Specify which LSM to display - SAUCE: apparmor3.2.0 [28/60]: Stacking v38: LSM: Ensure the correct LSM context releaser - SAUCE: apparmor3.2.0 [29/60]: Stacking v38: LSM: Use lsmcontext in security_secid_to_secctx - SAUCE: apparmor3.2.0 [30/60]: Stacking v38: LSM: Use lsmcontext in security_inode_getsecctx - SAUCE: apparmor3.2.0 [31/60]: Stacking v38: Use lsmcontext in security_dentry_init_security - SAUCE: apparmor3.2.0 [32/60]: Stacking v38: LSM: security_secid_to_secctx in netlink netfilter - SAUCE: apparmor3.2.0 [33/60]: Stacking v38: NET: Store LSM netlabel data in a lsmblob - SAUCE: apparmor3.2.0 [34/60]: Stacking v38: binder: Pass LSM identifier for confirmation - SAUCE: apparmor3.2.0 [35/60]: Stacking v38: LSM: security_secid_to_secctx module selection - SAUCE: apparmor3.2.0 [36/60]: Stacking v38: Audit: Keep multiple LSM data in audit_names - SAUCE: apparmor3.2.0 [37/60]: Stacking v38: Audit: Create audit_stamp structure - SAUCE: apparmor3.2.0 [38/60]: Stacking v38: LSM: Add a function to report multiple LSMs - SAUCE: apparmor3.2.0 [39/60]: Stacking v38: Audit: Allow multiple records in an audit_buffer - SAUCE: apparmor3.2.0 [40/60]: Stacking v38: Audit: Add record for multiple task security contexts - SAUCE: apparmor3.2.0 [41/60]: Stacking v38: audit: multiple subject lsm values for netlabel - SAUCE: apparmor3.2.0 [42/60]: Stacking v38: Audit: Add record for multiple object contexts - SAUCE: apparmor3.2.0 [43/60]: Stacking v38: netlabel: Use a struct lsmblob in audit data - SAUCE: apparmor3.2.0 [44/60]: Stacking v38: LSM: Removed scaffolding function lsmcontext_init - SAUCE: apparmor3.2.0 [45/60]: Stacking v38: AppArmor: Remove the exclusive flag - SAUCE: apparmor3.2.0 [46/60]: combine common_audit_data and apparmor_audit_data - SAUCE: apparmor3.2.0 [47/60]: setup slab cache for audit data - SAUCE: apparmor3.2.0 [48/60]: rename audit_data->label to audit_data->subj_label - SAUCE: apparmor3.2.0 [49/60]: pass cred through to audit info. - SAUCE: apparmor3.2.0 [50/60]: Improve debug print infrastructure - SAUCE: apparmor3.2.0 [51/60]: add the ability for profiles to have a learning cache - SAUCE: apparmor3.2.0 [52/60]: enable userspace upcall for mediation - SAUCE: apparmor3.2.0 [53/60]: cache buffers on percpu list if there is lock contention - SAUCE: apparmor3.2.0 [55/60]: advertise availability of exended perms - SAUCE: apparmor3.2.0 [60/60]: [Config] enable CONFIG_SECURITY_APPARMOR_RESTRICT_USERNS * LSM stacking and AppArmor for 6.2: additional fixes (LP: #2017903) // update apparmor and LSM stacking patch set (LP: #2028253) - SAUCE: apparmor3.2.0 [57/60]: fix profile verification and enable it * udev fails to make prctl() syscall with apparmor=0 (as used by maas by default) (LP: #2016908) // update apparmor and LSM stacking patch set (LP: #2028253) - SAUCE: apparmor3.2.0 [27/60]: Stacking v38: Fix prctl() syscall with apparmor=0 * kinetic: apply new apparmor and LSM stacking patch set (LP: #1989983) // update apparmor and LSM stacking patch set (LP: #2028253) - SAUCE: apparmor3.2.0 [01/60]: add/use fns to print hash string hex value - SAUCE: apparmor3.2.0 [03/60]: patch to provide compatibility with v2.x net rules - SAUCE: apparmor3.2.0 [04/60]: add user namespace creation mediation - SAUCE: apparmor3.2.0 [06/60]: af_unix mediation - SAUCE: apparmor3.2.0 [07/60]: Add fine grained mediation of posix mqueues [ Ubuntu: 6.5.0-7.7 ] * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611) * kexec enable to load/kdump zstd compressed zimg (LP: #2037398) - [Packaging] Revert arm64 image format to Image.gz * Mantic minimized/minimal cloud images do not receive IP address during provisioning (LP: #2036968) - [Config] Enable virtio-net as built-in to avoid race * Miscellaneous Ubuntu changes - SAUCE: Add mdev_set_iommu_device() kABI - [Config] update gcc version in annotations -- Timo Aaltonen <timo.aalto...@canonical.com> Wed, 11 Oct 2023 18:54:54 +0300 ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2037273 Title: Realtek 8852CE WiFi 6E country code udpates Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] [Impact] Missing WiFi 6G band for interested countries. [Fix] Upstream v6.6-rc1 commit f585f4ab0b99 ("wifi: rtw89: regd: update regulatory map to R64-R43"). [Test Case] Use `iw list` to check if 6G bands are then enabled. [Where problems could occur] This enables corresponding 6G bands for rtw89 driven devices. There should be no other side effects. [Other Info] Nominated for oem-6.5 and mantic. Since this is in v6.6-rc1, Unstable is skipped. ========= original bug report ========== Proposed fix: https://patchwork.kernel.org/project/linux-wireless/patch/20230815120253.9901-1-pks...@realtek.com/ Accepted in wireless-next as commit f585f4ab0b99 ("wifi: rtw89: regd: update regulatory map to R64-R43") and is in v6.6-rc1 now. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037273/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp