{ "dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": { "cveId": "CVE-2024-57999", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2025-02-27T02:04:28.915Z", "datePublished": "2025-02-27T02:07:18.570Z", "dateUpdated": "2026-08-05T11:47:19.135Z" }, "containers": { "cna": { "providerMetadata": { "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-08-05T11:47:19.135Z" }, "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\npowerpc/pseries/iommu: IOMMU incorrectly marks MMIO range in DDW\n\nPower Hypervisor can possibily allocate MMIO window intersecting with\nDynamic DMA Window (DDW) range, which is over 32-bit addressing.\n\nThese MMIO pages needs to be marked as reserved so that IOMMU doesn't map\nDMA buffers in this range.\n\nThe current code is not marking these pages correctly which is resulting\nin LPAR to OOPS while booting. The stack is at below\n\nBUG: Unable to handle kernel data access on read at 0xc00800005cd40000\nFaulting instruction address: 0xc00000000005cdac\nOops: Kernel access of bad area, sig: 11 [#1]\nLE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries\nModules linked in: af_packet rfkill ibmveth(X) lpfc(+) nvmet_fc nvmet nvme_keyring crct10dif_vpmsum nvme_fc nvme_fabrics nvme_core be2net(+) nvme_auth rtc_generic nfsd auth_rpcgss nfs_acl lockd grace sunrpc fuse configfs ip_tables x_tables xfs libcrc32c dm_service_time ibmvfc(X) scsi_transport_fc vmx_crypto gf128mul crc32c_vpmsum dm_mirror dm_region_hash dm_log dm_multipath dm_mod sd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua t10_pi crc64_rocksoft_generic crc64_rocksoft sg crc64 scsi_mod\nSupported: Yes, External\nCPU: 8 PID: 241 Comm: kworker/8:1 Kdump: loaded Not tainted 6.4.0-150600.23.14-default #1 SLE15-SP6 b44ee71c81261b9e4bab5e0cde1f2ed891d5359b\nHardware name: IBM,9080-M9S POWER9 (raw) 0x4e2103 0xf000005 of:IBM,FW950.B0 (VH950_149) hv:phyp pSeries\nWorkqueue: events work_for_cpu_fn\nNIP: c00000000005cdac LR: c00000000005e830 CTR: 0000000000000000\nREGS: c00001400c9ff770 TRAP: 0300 Not tainted (6.4.0-150600.23.14-default)\nMSR: 800000000280b033 CR: 24228448 XER: 00000001\nCFAR: c00000000005cdd4 DAR: c00800005cd40000 DSISR: 40000000 IRQMASK: 0\nGPR00: c00000000005e830 c00001400c9ffa10 c000000001987d00 c00001400c4fe800\nGPR04: 0000080000000000 0000000000000001 0000000004000000 0000000000800000\nGPR08: 0000000004000000 0000000000000001 c00800005cd40000 ffffffffffffffff\nGPR12: 0000000084228882 c00000000a4c4f00 0000000000000010 0000080000000000\nGPR16: c00001400c4fe800 0000000004000000 0800000000000000 c00000006088b800\nGPR20: c00001401a7be980 c00001400eff3800 c000000002a2da68 000000000000002b\nGPR24: c0000000026793a8 c000000002679368 000000000000002a c0000000026793c8\nGPR28: 000008007effffff 0000080000000000 0000000000800000 c00001400c4fe800\nNIP [c00000000005cdac] iommu_table_reserve_pages+0xac/0x100\nLR [c00000000005e830] iommu_init_table+0x80/0x1e0\nCall Trace:\n[c00001400c9ffa10] [c00000000005e810] iommu_init_table+0x60/0x1e0 (unreliable)\n[c00001400c9ffa90] [c00000000010356c] iommu_bypass_supported_pSeriesLP+0x9cc/0xe40\n[c00001400c9ffc30] [c00000000005c300] dma_iommu_dma_supported+0xf0/0x230\n[c00001400c9ffcb0] [c00000000024b0c4] dma_supported+0x44/0x90\n[c00001400c9ffcd0] [c00000000024b14c] dma_set_mask+0x3c/0x80\n[c00001400c9ffd00] [c0080000555b715c] be_probe+0xc4/0xb90 [be2net]\n[c00001400c9ffdc0] [c000000000986f3c] local_pci_probe+0x6c/0x110\n[c00001400c9ffe40] [c000000000188f28] work_for_cpu_fn+0x38/0x60\n[c00001400c9ffe70] [c00000000018e454] process_one_work+0x314/0x620\n[c00001400c9fff10] [c00000000018f280] worker_thread+0x2b0/0x620\n[c00001400c9fff90] [c00000000019bb18] kthread+0x148/0x150\n[c00001400c9fffe0] [c00000000000ded8] start_kernel_thread+0x14/0x18\n\nThere are 2 issues in the code\n\n1. The index is \"int\" while the address is \"unsigned long\". This results in\n negative value when setting the bitmap.\n\n2. The DMA offset is page shifted but the MMIO range is used as-is (64-bit\n address). MMIO address needs to be page shifted as well." } ], "metrics": [ { "cvssV3_1": { "version": "3.1", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H", "baseScore": 8.8, "baseSeverity": "HIGH" }, "scenarios": [ { "lang": "en", "value": "AV:L - The vulnerable code is powerpc/pseries platform IOMMU setup, reached either at local PCI driver probe (dma_set_mask → enable_ddw) or via the local VFIO SPAPR TCE container ioctl VFIO_IOMMU_SPAPR_TCE_CREATE. There is no network-facing path to iommu_init_table().\nAC:L - Via the VFIO path the attacker directly supplies page_shift and window_size, which set it_offset = win_addr >> page_shift and it_size — the exact terms in the overlap test that decides whether the corrupt loop executes — and can enumerate the hypervisor-supported page sizes to force the overlap. On a given machine the DDW and MMIO32 base addresses are deterministic, so the trigger is repeatable.\nPR:L - Exploitation requires only local access to a VFIO container and group fd, which is exactly what unprivileged device-passthrough processes (QEMU, userspace drivers) are granted by administrators; no root in the init namespace is needed. The boot/probe manifestation requires no attacker privileges at all.\nUI:N - The ioctl sequence is issued entirely by the attacker's own process, and the probe-path manifestation occurs autonomously during device initialization. No victim action is involved.\nS:C - The reserved-page mechanism exists specifically to stop the IOMMU from mapping DMA buffers over hypervisor-allocated MMIO ranges, so the mis-marking is a failure of the DMA/IOMMU isolation boundary itself, allowing device DMA to reach MMIO registers. On the VFIO path the corruption is driven from a guest/passthrough domain into host kernel state, crossing the VM boundary.\nC:H - The truncated index makes set_bit() perform an out-of-bounds atomic read-modify-write far outside the vmalloc'd bitmap, and the poisoned it_reserved_start later drives find_next_bit() past the bitmap end in iommu_table_in_use(); combined with DMA/MMIO aliasing exposing hardware register contents, this is an unbounded out-of-bounds read.\nI:H - set_bit() at index 0xfffff80000000000 is an out-of-bounds write, attempted ~0x800000 times over an attacker-influenced range, giving an atomic bit-set primitive at wild kernel offsets. Additionally, DMA buffers mapped over the unreserved MMIO range write attacker-influenced data directly into hardware registers.\nA:H - The reported and confirmed outcome is a kernel oops (\"Kernel access of bad area, sig: 11\") in iommu_table_reserve_pages() that kills the LPAR during boot or device probe. The VFIO path lets this be triggered on demand against a running host." } ] } ], "affected": [ { "product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": [ "arch/powerpc/kernel/iommu.c", "arch/powerpc/platforms/pseries/iommu.c" ], "versions": [ { "version": "3c33066a21903076722a2881556a92aa3cd7d359", "lessThan": "7043d58ecd1381674f5b2c894deb6986a1a4896b", "status": "affected", "versionType": "git" }, { "version": "3c33066a21903076722a2881556a92aa3cd7d359", "lessThan": "d8cc20a8cceb3b5e8ad2e11365e3100ba36a27e9", "status": "affected", "versionType": "git" }, { "version": "3c33066a21903076722a2881556a92aa3cd7d359", "lessThan": "8f70caad82e9c088ed93b4fea48d941ab6441886", "status": "affected", "versionType": "git" } ] }, { "product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": [ "arch/powerpc/kernel/iommu.c", "arch/powerpc/platforms/pseries/iommu.c" ], "versions": [ { "version": "5.15", "status": "affected" }, { "version": "0", "lessThan": "5.15", "status": "unaffected", "versionType": "semver" }, { "version": "6.12.13", "lessThanOrEqual": "6.12.*", "status": "unaffected", "versionType": "semver" }, { "version": "6.13.2", "lessThanOrEqual": "6.13.*", "status": "unaffected", "versionType": "semver" }, { "version": "6.14", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix" } ] } ], "cpeApplicability": [ { "nodes": [ { "operator": "OR", "negate": false, "cpeMatch": [ { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "5.15", "versionEndExcluding": "6.12.13" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "5.15", "versionEndExcluding": "6.13.2" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "5.15", "versionEndExcluding": "6.14" } ] } ] } ], "references": [ { "url": "https://git.kernel.org/stable/c/7043d58ecd1381674f5b2c894deb6986a1a4896b" }, { "url": "https://git.kernel.org/stable/c/d8cc20a8cceb3b5e8ad2e11365e3100ba36a27e9" }, { "url": "https://git.kernel.org/stable/c/8f70caad82e9c088ed93b4fea48d941ab6441886" } ], "title": "powerpc/pseries/iommu: IOMMU incorrectly marks MMIO range in DDW", "x_generator": { "engine": "bippy-1.2.0" } } } }