🛡️ UBUNTU-CVE-2024-53232
⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

In the Linux kernel, the following vulnerability has been resolved: iommu/s390: Implement blocking domain This fixes a crash when surprise hot-unplugging a PCI device. This crash happens because during hot-unplug __iommu_group_set_domain_nofail() attaching the default domain fails when the platform no longer recognizes the device as it has already been removed and we end up with a NULL domain pointer and UAF. This is exactly the case referred to in the second comment in __iommu_device_set_domain() and just as stated there if we can instead attach the blocking domain the UAF is prevented as this can handle the already removed device. Implement the blocking domain to use this handling. With this change, the crash is fixed but we still hit a warning attempting to change DMA ownership on a blocked device.

Details

Severity Unknown
CVSS Score N/A
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2024-12-27
Updated 2026-06-15
Modified 2026-04-22
Fix URL N/A

Affected Packages

Software From version Fixed in
linux 6.8.0-58.60
linux-allwinner-5.19
linux-aws 6.8.0-1027.29
linux-aws-5.0
linux-aws-5.11
linux-aws-5.13
linux-aws-5.19
linux-aws-5.3
linux-aws-5.8
linux-aws-6.2
linux-aws-6.5
linux-aws-6.8 6.8.0-1027.29~22.04.1
linux-azure 6.8.0-1027.32
linux-azure-5.11
linux-azure-5.13
linux-azure-5.19
linux-azure-5.3
linux-azure-5.8
linux-azure-6.11 6.11.0-1012.12~24.04.1
linux-azure-6.2
linux-azure-6.5
linux-azure-6.8 6.8.0-1027.32~22.04.1
linux-azure-edge
linux-azure-fde
linux-azure-fde-5.19
linux-azure-fde-6.2
linux-azure-nvidia 6.8.0-1014.15
linux-fips 6.8.0-78.78+fips1
linux-gcp 6.8.0-1028.30
linux-gcp-5.11
linux-gcp-5.13
linux-gcp-5.19
linux-gcp-5.3
linux-gcp-5.8
linux-gcp-6.11 6.11.0-1011.11~24.04.1
linux-gcp-6.2
linux-gcp-6.5
linux-gcp-6.8 6.8.0-1028.30~22.04.1
linux-gke 6.8.0-1023.27
linux-gke-4.15
linux-gke-5.15
linux-gke-5.4
linux-gkeop 6.8.0-1010.12
linux-gkeop-5.15
linux-gkeop-5.4
linux-hwe
linux-hwe-5.11
linux-hwe-5.13
linux-hwe-5.19
linux-hwe-5.8
linux-hwe-6.2
linux-hwe-6.5
linux-hwe-6.8 6.8.0-58.60~22.04.1
linux-hwe-edge
linux-ibm 6.8.0-1024.24
linux-ibm-6.8 6.8.0-1024.24~22.04.1
linux-intel-5.13
linux-intel-iot-realtime
linux-lowlatency 6.8.0-58.60.1
linux-lowlatency-hwe-5.19
linux-lowlatency-hwe-6.2
linux-lowlatency-hwe-6.5
linux-lowlatency-hwe-6.8 6.8.0-58.60.1~22.04.1
linux-nvidia 6.8.0-1026.29
linux-nvidia-6.11 6.11.0-1007.7
linux-nvidia-6.2
linux-nvidia-6.5
linux-nvidia-6.8 6.8.0-1026.29~22.04.1
linux-nvidia-lowlatency 6.8.0-1026.29.1
linux-nvidia-tegra 6.8.0-1008.8
linux-oem
linux-oem-5.10
linux-oem-5.13
linux-oem-5.14
linux-oem-5.17
linux-oem-5.6
linux-oem-6.0
linux-oem-6.1
linux-oem-6.11 6.11.0-1015.15
linux-oem-6.5
linux-oem-6.8 6.8.0-1026.26
linux-oracle 6.8.0-1024.25
linux-oracle-5.0
linux-oracle-5.11
linux-oracle-5.13
linux-oracle-5.3
linux-oracle-5.8
linux-oracle-6.5
linux-oracle-6.8 6.8.0-1024.25~22.04.1
linux-raspi 6.8.0-1028.32
linux-raspi-realtime 6.8.0-2023.24
linux-raspi2
linux-realtime 6.8.1-1020.21
linux-realtime-6.8 6.8.1-1020.21~22.04.1
linux-riscv 6.8.0-58.60.1
linux-riscv-5.11
linux-riscv-5.19
linux-riscv-5.8
linux-riscv-6.5
linux-riscv-6.8 6.8.0-58.60.1~22.04.1
linux-starfive-5.19
linux-starfive-6.2
linux-starfive-6.5
linux-xilinx 6.8.0-1017.18

References

Similar Threats

Vulnerability Monitoring

Stay informed about vulnerabilities in your stack

BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.