CVE-2024-27079: iommu/vt-d: Fix NULL domain on device release
First published: Wed May 01 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix NULL domain on device release In the kdump kernel, the IOMMU operates in deferred_attach mode. In this mode, info->domain may not yet be assigned by the time the release_device function is called. It leads to the following crash in the crash kernel: BUG: kernel NULL pointer dereference, address: 000000000000003c ... RIP: 0010:do_raw_spin_lock+0xa/0xa0 ... _raw_spin_lock_irqsave+0x1b/0x30 intel_iommu_release_device+0x96/0x170 iommu_deinit_device+0x39/0xf0 __iommu_group_remove_device+0xa0/0xd0 iommu_bus_notifier+0x55/0xb0 notifier_call_chain+0x5a/0xd0 blocking_notifier_call_chain+0x41/0x60 bus_notify+0x34/0x50 device_del+0x269/0x3d0 pci_remove_bus_device+0x77/0x100 p2sb_bar+0xae/0x1d0 ... i801_probe+0x423/0x740 Use the release_domain mechanism to fix it. The scalable mode context entry which is not part of release domain should be cleared in release_device().
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat/kernel | <6.8.2 | 6.8.2 |
| redhat/kernel | <6.9 | 6.9 |
| Linux Kernel | >=5.18<6.8.2 | |
| debian/linux | <=6.1.129-1<=6.1.135-1 | 5.10.223-1 5.10.234-1 6.12.25-1 6.12.27-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/333fe86968482ca701c609af590003bcea450e8f
- https://git.kernel.org/stable/c/81e921fd321614c2ad8ac333b041aae1da7a1c6d
- https://launchpad.net/bugs/cve/CVE-2024-27079
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-27079
- https://nvd.nist.gov/vuln/detail/CVE-2024-27079
- https://security-tracker.debian.org/tracker/CVE-2024-27079
- https://ubuntu.com/security/CVE-2024-27079
- https://git.kernel.org/linus/81e921fd321614c2ad8ac333b041aae1da7a1c6d
- https://access.redhat.com/security/cve/CVE-2024-27079
- https://lore.kernel.org/linux-cve-announce/2024050134-CVE-2024-27079-f478@gregkh/T
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2278493
- https://access.redhat.com/errata/RHSA-2024:9315
- https://bugzilla.redhat.com/show_bug.cgi?id=2278492
Frequently Asked Questions
What is the severity of CVE-2024-27079?
CVE-2024-27079 has a high severity rating due to its impact on the Linux kernel's IOMMU functionality.
How do I fix CVE-2024-27079?
To fix CVE-2024-27079, update the kernel package to version 6.8.2, 6.9, or the specified versions for Debian distributions.
What systems are affected by CVE-2024-27079?
CVE-2024-27079 affects specific versions of the Red Hat kernel and Debian Linux packages related to the IOMMU.
What are the implications of CVE-2024-27079?
CVE-2024-27079 can lead to unauthorized access or system instability by improperly handling device releases in the IOMMU.
Is there a workaround for CVE-2024-27079 before applying the fix?
There are no known effective workarounds for CVE-2024-27079, and applying the kernel update is recommended.
- agent/title
- agent/weakness
- agent/type
- agent/first-publish-date
- collector/launchpad-cve
- source/Launchpad
- agent/author
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2024-27079
- agent/software-canonical-lookup
- agent/references
- collector/mitre-cve
- source/MITRE
- agent/trending
- agent/source
- agent/remedy
- agent/severity
- agent/tags
- collector/usn-cve
- source/Ubuntu
- agent/description
- collector/nvd-api
- source/NVD
- agent/last-modified-date
- agent/event
- collector/nvd-cve
- agent/softwarecombine
- collector/security-tracker-debian
- source/Debian
- package-manager/redhat
- vendor/linux
- canonical/linux kernel
- version/linux kernel/5.18
- package-manager/debian