{"id":"CVE-2026-90244","title":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu/dma: Restore locking around msi_page_list\n\nUnlike a group's default domain, which is always freshly allocated\nand privately owned (iommu_group_alloc_default_domai…","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu/dma: Restore locking around msi_page_list\n\nUnlike a group's default domain, which is always freshly allocated\nand privately owned (iommu_group_alloc_default_domai…","severity":"high","cvss":7.8,"cvssVector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","vendor":"Linux","product":"Linux","affected":["Linux >= 288683c92b1abc32277c83819bea287af614d239 < e3c53e9173a47d5ce1fae020f2c6b1fb3c1123c2","Linux >= 288683c92b1abc32277c83819bea287af614d239 < 2af1e99ec14d226d66ceb9f16c663ee2568e6676","Linux >= 288683c92b1abc32277c83819bea287af614d239 < 5a9e89ea34e0e34ac5d7e949042d665533549e40","Linux 6.15"],"published":"2026-09-17","updated":"2026-09-18","sourceUpdated":"2026-09-18T18:17:50.720","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-90244","references":[{"url":"https://git.kernel.org/stable/c/2af1e99ec14d226d66ceb9f16c663ee2568e6676","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/5a9e89ea34e0e34ac5d7e949042d665533549e40","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/e3c53e9173a47d5ce1fae020f2c6b1fb3c1123c2","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}],"tags":["nvd","cve.org"],"epss":0.00161,"epssPercentile":0.05766,"ingestedAt":"2026-09-17T16:21:47.846Z","slug":"CVE-2026-90244","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/dma: Restore locking around msi_page_list\n\nUnlike a group's default domain, which is always freshly allocated\nand privately owned (iommu_group_alloc_default_domain()), VFIO type1's\nlegacy container merges any newly attached group into an existing\ndomain whenever their iommu_ops and cache-coherency enforcement match.\n\niommu_dma_get_msi_page() only asserts the caller's own group mutex is\nheld (iommu_group_mutex_assert()). On an IOMMU that publishes\nIOMMU_RESV_SW_MSI, e.g. ARM SMMU, a VM with two such devices assigned\nthrough the legacy container can have their guest drivers probe and\nallocate MSIs in parallel; each host-side VFIO_DEVICE_SET_IRQS lands\non a different device fd and group mutex, but both devices' domains\nare the same merged domain, so both can enter\niommu_dma_get_msi_page() concurrently and corrupt msi_page_list.\n\ncommit 288683c92b1a (\"iommu: Make iommu_dma_prepare_msi() into a\ngeneric operation\") dropped the prior msi_prepare_lock on the\nreasoning that \"each iommu_domain is unique to a group,\" which holds\nfor default domains but not this VFIO type1 case. Restore the static\nlock, since it's only guarding a corner case and will likely never\nbe contended.\n\niommufd avoids the equivalent problem by having its own callers\n(iommufd_sw_map_msi()) take a ctx-wide sw_msi_lock before ever\nreaching the shared list. VFIO type1 can't mirror that since it\ndispatches to iommu_dma_sw_msi() which is outside VFIO's jurisdiction.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"twilight","depthScore":43,"depthScoreParts":{"impact":42.9,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[{"seq":207213,"id":"CVE-2026-90244","ts":1789757339627,"field":"cvss","old":null,"new":"7.8"},{"seq":207212,"id":"CVE-2026-90244","ts":1789757339627,"field":"severity","old":"none","new":"high"}]}