This bug was fixed in the package linux-aws - 5.4.0-1144.154
---------------
linux-aws (5.4.0-1144.154) focal; urgency=medium
* focal/linux-aws: 5.4.0-1144.154 -proposed tracker (LP: #2102590)
* iommu/arm-smmu-v3: Don't reserve implementation defined register space
(LP: #2067864)
- iommu/arm-smmu-v3: Don't reserve implementation defined register space
[ Ubuntu: 5.4.0-214.234 ]
* focal/linux: 5.4.0-214.234 -proposed tracker (LP: #2102635)
* CVE-2024-50256
- netfilter: nf_reject_ipv6: fix potential crash in nf_send_reset6()
* CVE-2025-21702
- pfifo_tail_enqueue: Drop new packet when sch->limit == 0
* CVE-2025-21703
- netem: Update sch->q.qlen before qdisc_tree_reduce_backlog()
* CVE-2024-26915
- drm/amdgpu: Reset IH OVERFLOW_CLEAR bit
* CVE-2025-21700
- net: sched: Disallow replacing of child qdisc from one parent to another
* CVE-2024-46826
- ELF: fix kernel.randomize_va_space double read
* CVE-2024-56651
- can: hi311x: hi3110_can_ist(): fix potential use-after-free
* CVE-2024-53237
- driver core: Introduce device_find_any_child() helper
- Bluetooth: fix use-after-free in device_for_each_child()
* CVE-2024-35958
- net: ena: Fix incorrect descriptor free behavior
* CVE-2024-49974
- NFSD: Limit the number of concurrent async COPY operations
* CVE-2021-47119
- ext4: fix memory leak in ext4_fill_super
* CVE-2024-56658
- net: defer final 'struct net' free in netns dismantle
* CVE-2024-35864
- smb: client: fix potential UAF in smb2_is_valid_lease_break()
* CVE-2024-35864/CVE-2024-26928
- smb: client: fix potential UAF in cifs_debug_files_proc_show()
-- Bethany Jamison <bethany.jami...@canonical.com> Fri, 04 Apr 2025
13:28:19 -0500
** Changed in: linux-aws (Ubuntu Focal)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-47119
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-26915
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-26928
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-35864
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-35958
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-46826
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-49974
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-50256
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-53237
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-56651
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-56658
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2025-21700
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2025-21702
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2025-21703
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2067864
Title:
iommu/arm-smmu-v3: Don't reserve implementation defined register space
Status in linux package in Ubuntu:
New
Status in linux-aws package in Ubuntu:
New
Status in linux source package in Focal:
In Progress
Status in linux-aws source package in Focal:
Fix Released
Bug description:
SRU Justification
[Impact]
In order to solve boot issues with new instance types running the 5.4 kernels,
AWS has requested a backport of upstream commit 52f3fab0067d
("iommu/arm-smmu-v3: Don't reserve implementation defined register space").
[Fix]
There was a conflict when adding arm_smmu_ioremap() due to the current
context missing ab246774713e ("iommu/arm-smmu-v3: Unregister IOMMU and
bus ops on device removal").
[Test]
It's been tested that the new instances can boot successfully with the AWS 5.4
kernels with this patch applied.
[Where problems could occur]
This touches probing of the ARM SMMUv3 driver, which might lead to boot
failures or system instability.
[Other info]
SF #00407928
---------------------------- Original bug report ----------------------------
can ubuntu 20.04 kernel backport this
commit：https://github.com/torvalds/linux/commit/52f3fab0067d6fa9e99c1b7f63265dd48ca76046
to avoid resource reservation conflicts.
we met this problem in aliyun ebmc8y instance type
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2067864/+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
