CVE-2024-57999

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-02-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

powerpc/pseries/iommu: IOMMU incorrectly marks MMIO range in DDW

Power Hypervisor can possibily allocate MMIO window intersecting with Dynamic DMA Window (DDW) range, which is over 32-bit addressing.

These MMIO pages needs to be marked as reserved so that IOMMU doesn't map DMA buffers in this range.

The current code is not marking these pages correctly which is resulting in LPAR to OOPS while booting. The stack is at below

BUG: Unable to handle kernel data access on read at 0xc00800005cd40000 Faulting instruction address: 0xc00000000005cdac Oops: Kernel access of bad area, sig: 11 [#1] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries Modules 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 Supported: Yes, External CPU: 8 PID: 241 Comm: kworker/8:1 Kdump: loaded Not tainted 6.4.0-150600.23.14-default #1 SLE15-SP6 b44ee71c81261b9e4bab5e0cde1f2ed891d5359b Hardware name: IBM,9080-M9S POWER9 (raw) 0x4e2103 0xf000005 of:IBM,FW950.B0 (VH950_149) hv:phyp pSeries Workqueue: events work_for_cpu_fn NIP: c00000000005cdac LR: c00000000005e830 CTR: 0000000000000000 REGS: c00001400c9ff770 TRAP: 0300 Not tainted (6.4.0-150600.23.14-default) MSR: 800000000280b033 CR: 24228448 XER: 00000001 CFAR: c00000000005cdd4 DAR: c00800005cd40000 DSISR: 40000000 IRQMASK: 0 GPR00: c00000000005e830 c00001400c9ffa10 c000000001987d00 c00001400c4fe800 GPR04: 0000080000000000 0000000000000001 0000000004000000 0000000000800000 GPR08: 0000000004000000 0000000000000001 c00800005cd40000 ffffffffffffffff GPR12: 0000000084228882 c00000000a4c4f00 0000000000000010 0000080000000000 GPR16: c00001400c4fe800 0000000004000000 0800000000000000 c00000006088b800 GPR20: c00001401a7be980 c00001400eff3800 c000000002a2da68 000000000000002b GPR24: c0000000026793a8 c000000002679368 000000000000002a c0000000026793c8 GPR28: 000008007effffff 0000080000000000 0000000000800000 c00001400c4fe800 NIP [c00000000005cdac] iommu_table_reserve_pages+0xac/0x100 LR [c00000000005e830] iommu_init_table+0x80/0x1e0 Call Trace: [c00001400c9ffa10] [c00000000005e810] iommu_init_table+0x60/0x1e0 (unreliable) [c00001400c9ffa90] [c00000000010356c] iommu_bypass_supported_pSeriesLP+0x9cc/0xe40 [c00001400c9ffc30] [c00000000005c300] dma_iommu_dma_supported+0xf0/0x230 [c00001400c9ffcb0] [c00000000024b0c4] dma_supported+0x44/0x90 [c00001400c9ffcd0] [c00000000024b14c] dma_set_mask+0x3c/0x80 [c00001400c9ffd00] [c0080000555b715c] be_probe+0xc4/0xb90 [be2net] [c00001400c9ffdc0] [c000000000986f3c] local_pci_probe+0x6c/0x110 [c00001400c9ffe40] [c000000000188f28] work_for_cpu_fn+0x38/0x60 [c00001400c9ffe70] [c00000000018e454] process_one_work+0x314/0x620 [c00001400c9fff10] [c00000000018f280] worker_thread+0x2b0/0x620 [c00001400c9fff90] [c00000000019bb18] kthread+0x148/0x150 [c00001400c9fffe0] [c00000000000ded8] start_kernel_thread+0x14/0x18

There are 2 issues in the code

  • The index is "int" while the address is "unsigned long". This results in
negative value when setting the bitmap.
  • The DMA offset is page shifted but the MMIO range is used as-is (64-bit
address). MMIO address needs to be page shifted as well.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

February 27, 2025

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

powerpc/pseries/iommu: IOMMU incorrectly marks MMIO range in DDW - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8f70caad82e9c088ed93b4fea48d941ab6441886
generic

powerpc/pseries/iommu: IOMMU incorrectly marks MMIO range in DDW - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d8cc20a8cceb3b5e8ad2e11365e3100ba36a27e9
generic

powerpc/pseries/iommu: IOMMU incorrectly marks MMIO range in DDW - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7043d58ecd1381674f5b2c894deb6986a1a4896b

Vendor Advisories for CVE-2024-57999(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-26.26~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-aws (6.11.0-1014.15) @ oracular2026-05-30ubuntu
ubuntulinux-virtual-6.8 (6.8.0-64.67) @ noble2026-05-30ubuntu
ubuntulinux-tools-lowlatency-hwe-24.04-edge (6.11.0-1014.15~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1025.26) @ noble2026-05-30ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2026.27) @ noble2026-05-30ubuntu
ubuntulinux-tools-gcp-lts-24.04 (6.8.0-1033.35) @ noble2026-05-30ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-64.67~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-64.67.1~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1029.30) @ noble2026-05-30ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1031.35) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-nvidia-lts-24.04 (6.8.0-1022.23) @ noble2026-05-30ubuntu
linuxKernel @ 6.12.13—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.12.13-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.12.13-1—

Additional Vendor Advisories

(12)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 158 total refreshes for this CVE.

  1. 2026-09-20 20:14 UTCEPSS rescore
  2. 2026-09-20 20:14 UTCEPSS rescore
  3. 2026-09-18 19:26 UTCEPSS rescore
  4. 2026-09-16 14:06 UTCEPSS rescore
  5. 2026-09-16 14:06 UTCEPSS rescore
  6. 2026-09-16 05:12 UTCEPSS rescore
  7. 2026-09-15 03:08 UTCEPSS rescore
  8. 2026-09-13 16:45 UTCEPSS rescore
  9. 2026-09-12 14:59 UTCEPSS rescore
  10. 2026-09-11 14:51 UTCEPSS rescore
  11. 2026-09-11 09:35 UTCEPSS rescore
  12. 2026-09-10 09:33 UTCEPSS rescore
  13. 2026-09-08 21:59 UTCEPSS rescore
  14. 2026-09-07 13:17 UTCOSV refresh
  15. 2026-09-06 13:46 UTCEPSS rescore
  16. 2026-09-04 13:59 UTCEPSS rescore
  17. 2026-09-04 05:05 UTCEPSS rescore
  18. 2026-09-02 14:10 UTCEPSS rescore
  19. 2026-09-01 13:52 UTCEPSS rescore
  20. 2026-08-30 19:16 UTCEPSS rescore
  21. 2026-08-30 19:16 UTCEPSS rescore
  22. 2026-08-28 21:39 UTCEPSS rescore
  23. 2026-08-27 14:24 UTCEPSS rescore
  24. 2026-08-26 14:44 UTCEPSS rescore
  25. 2026-08-25 13:47 UTCEPSS rescore
Show 75 more
  1. 2026-08-24 14:15 UTCEPSS rescore
  2. 2026-08-21 23:47 UTCEPSS rescore
  3. 2026-08-20 22:54 UTCEPSS rescore
  4. 2026-08-20 22:31 UTCOSV refresh
  5. 2026-08-19 17:02 UTCEPSS rescore
  6. 2026-08-18 13:47 UTCEPSS rescore
  7. 2026-08-17 13:45 UTCEPSS rescore
  8. 2026-08-16 14:55 UTCEPSS rescore
  9. 2026-08-16 02:13 UTCEPSS rescore
  10. 2026-08-15 01:29 UTCEPSS rescore
  11. 2026-08-13 21:59 UTCEPSS rescore
  12. 2026-08-12 13:49 UTCEPSS rescore
  13. 2026-08-11 13:41 UTCEPSS rescore
  14. 2026-08-10 23:58 UTCEPSS rescore
  15. 2026-08-09 13:45 UTCEPSS rescore
  16. 2026-08-08 16:35 UTCEPSS rescore
  17. 2026-08-07 16:26 UTCEPSS rescore
  18. 2026-08-06 13:45 UTCEPSS rescore
  19. 2026-08-05 19:16 UTCEPSS rescore
  20. 2026-08-05 14:04 UTCEG score recompute
  21. 2026-08-05 14:04 UTCVendor advisory
  22. 2026-08-05 14:04 UTCGHSA enrichment
  23. 2026-08-04 15:08 UTCEPSS rescore
  24. 2026-08-04 11:24 UTCVendor advisory
  25. 2026-08-04 11:24 UTCGHSA enrichment
  26. 2026-08-04 11:06 UTCEG score recompute
  27. 2026-08-04 11:06 UTCVendor advisory
  28. 2026-08-04 11:06 UTCGHSA enrichment
  29. 2026-08-03 10:35 UTCEPSS rescore
  30. 2026-08-02 02:25 UTCEPSS rescore
  31. 2026-08-02 02:25 UTCEPSS rescore
  32. 2026-08-01 04:14 UTCEPSS rescore
  33. 2026-07-30 16:26 UTCEPSS rescore
  34. 2026-07-30 16:26 UTCEPSS rescore
  35. 2026-07-30 01:29 UTCEPSS rescore
  36. 2026-07-28 15:35 UTCEPSS rescore
  37. 2026-07-26 14:53 UTCEPSS rescore
  38. 2026-07-25 14:17 UTCEPSS rescore
  39. 2026-07-25 14:17 UTCEPSS rescore
  40. 2026-07-24 14:16 UTCEPSS rescore
  41. 2026-07-24 13:41 UTCOSV refresh
  42. 2026-07-23 14:17 UTCEPSS rescore
  43. 2026-07-23 14:17 UTCEPSS rescore
  44. 2026-07-23 02:45 UTCEG score recompute
  45. 2026-07-22 14:07 UTCEPSS rescore
  46. 2026-07-21 15:23 UTCEPSS rescore
  47. 2026-07-20 17:07 UTCEPSS rescore
  48. 2026-07-19 14:30 UTCEPSS rescore
  49. 2026-07-19 14:30 UTCEPSS rescore
  50. 2026-07-19 02:28 UTCEPSS rescore
  51. 2026-07-19 02:28 UTCEPSS rescore
  52. 2026-07-18 10:03 UTCEPSS rescore
  53. 2026-07-16 17:02 UTCEPSS rescore
  54. 2026-07-15 16:57 UTCEPSS rescore
  55. 2026-07-15 01:59 UTCEPSS rescore
  56. 2026-07-15 01:59 UTCEPSS rescore
  57. 2026-07-13 22:29 UTCEPSS rescore
  58. 2026-07-13 06:12 UTCEPSS rescore
  59. 2026-07-12 05:45 UTCEPSS rescore
  60. 2026-07-11 08:26 UTCEPSS rescore
  61. 2026-07-09 19:09 UTCEPSS rescore
  62. 2026-07-09 19:09 UTCEPSS rescore
  63. 2026-07-08 15:14 UTCEPSS rescore
  64. 2026-07-07 13:45 UTCEPSS rescore
  65. 2026-07-07 13:45 UTCEPSS rescore
  66. 2026-07-07 09:21 UTCOSV refresh
  67. 2026-07-06 16:26 UTCEPSS rescore
  68. 2026-07-06 16:26 UTCEPSS rescore
  69. 2026-07-06 02:22 UTCEPSS rescore
  70. 2026-07-05 02:29 UTCEPSS rescore
  71. 2026-07-04 06:30 UTCEPSS rescore
  72. 2026-07-04 06:30 UTCEPSS rescore
  73. 2026-07-01 15:06 UTCEPSS rescore
  74. 2026-06-30 23:21 UTCEPSS rescore
  75. 2026-06-30 23:21 UTCEPSS rescore

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2024-57999?
CVE-2024-57999 is a medium vulnerability published on February 27, 2025. In the Linux kernel, the following vulnerability has been resolved: powerpc/pseries/iommu: IOMMU incorrectly marks MMIO range in DDW Power Hypervisor can possibily allocate MMIO window intersecting with Dynamic DMA Window (DDW) range, which is over 32-bit addressing. These MMIO pages needs to be…
When was CVE-2024-57999 disclosed?
CVE-2024-57999 was first published in the National Vulnerability Database on February 27, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-57999 actively exploited?
CVE-2024-57999 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 86.4% of all scored CVEs.
What is the CVSS score of CVE-2024-57999?
CVE-2024-57999 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-57999?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-57999, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-57999

Explore →

Is Your Infrastructure Affected by CVE-2024-57999?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs