CVE-2024-26745

MEDIUMNVD 4.44.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 4.4 from GitHub Security Advisory published 2024-04-04. NVD baseline CVSS 4.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2024-24007 (ENISA EUVD) · GHSA-44wr-9xpq-76v2 (GitHub Security Advisories)Source: ENISA EUVD

4.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

powerpc/pseries/iommu: IOMMU table is not initialized for kdump over SR-IOV

When kdump kernel tries to copy dump data over SR-IOV, LPAR panics due to NULL pointer exception:

Kernel attempted to read user page (0) - exploit attempt? (uid: 0) BUG: Kernel NULL pointer dereference on read at 0x00000000 Faulting instruction address: 0xc000000020847ad4 Oops: Kernel access of bad area, sig: 11 [#1] LE PAGE_SIZE=64K MMU=Radix SMP NR_CPUS=2048 NUMA pSeries Modules linked in: mlx5_core(+) vmx_crypto pseries_wdt papr_scm libnvdimm mlxfw tls psample sunrpc fuse overlay squashfs loop CPU: 12 PID: 315 Comm: systemd-udevd Not tainted 6.4.0-Test102+ #12 Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1060.00 (NH1060_008) hv:phyp pSeries NIP: c000000020847ad4 LR: c00000002083b2dc CTR: 00000000006cd18c REGS: c000000029162ca0 TRAP: 0300 Not tainted (6.4.0-Test102+) MSR: 800000000280b033 CR: 48288244 XER: 00000008 CFAR: c00000002083b2d8 DAR: 0000000000000000 DSISR: 40000000 IRQMASK: 1 ... NIP _find_next_zero_bit+0x24/0x110 LR bitmap_find_next_zero_area_off+0x5c/0xe0 Call Trace: dev_printk_emit+0x38/0x48 (unreliable) iommu_area_alloc+0xc4/0x180 iommu_range_alloc+0x1e8/0x580 iommu_alloc+0x60/0x130 iommu_alloc_coherent+0x158/0x2b0 dma_iommu_alloc_coherent+0x3c/0x50 dma_alloc_attrs+0x170/0x1f0 mlx5_cmd_init+0xc0/0x760 [mlx5_core] mlx5_function_setup+0xf0/0x510 [mlx5_core] mlx5_init_one+0x84/0x210 [mlx5_core] probe_one+0x118/0x2c0 [mlx5_core] local_pci_probe+0x68/0x110 pci_call_probe+0x68/0x200 pci_device_probe+0xbc/0x1a0 really_probe+0x104/0x540 __driver_probe_device+0xb4/0x230 driver_probe_device+0x54/0x130 __driver_attach+0x158/0x2b0 bus_for_each_dev+0xa8/0x130 driver_attach+0x34/0x50 bus_add_driver+0x16c/0x300 driver_register+0xa4/0x1b0 __pci_register_driver+0x68/0x80 mlx5_init+0xb8/0x100 [mlx5_core] do_one_initcall+0x60/0x300 do_init_module+0x7c/0x2b0

At the time of LPAR dump, before kexec hands over control to kdump kernel, DDWs (Dynamic DMA Windows) are scanned and added to the FDT. For the SR-IOV case, default DMA window "ibm,dma-window" is removed from the FDT and DDW added, for the device.

Now, kexec hands over control to the kdump kernel.

When the kdump kernel initializes, PCI busses are scanned and IOMMU group/tables created, in pci_dma_bus_setup_pSeriesLP(). For the SR-IOV case, there is no "ibm,dma-window". The original commit: b1fc44eaa9ba, fixes the path where memory is pre-mapped (direct mapped) to the DDW. When TCEs are direct mapped, there is no need to initialize IOMMU tables.

iommu_table_setparms_lpar() only considers "ibm,dma-window" property when initiallizing IOMMU table. In the scenario where TCEs are dynamically allocated for SR-IOV, newly created IOMMU table is not initialized. Later, when the device driver tries to enter TCEs for the SR-IOV device, NULL pointer execption is thrown from iommu_area_alloc().

The fix is to initialize the IOMMU table with DDW property stored in the FDT. There are 2 points to remember:

  • For the dedicated adapter, kdump kernel would encounter both
default and DDW in FDT. In this case, DDW property is used to initialize the IOMMU table.
  • A DDW could be direct or dynamic mapped. kdump kernel would
initialize IOMMU table and mark the existing DDW as "dynamic". This works fine since, at the time of table initialization, iommu_table_clear() makes some space in the DDW, for some predefined number of TCEs which are needed for kdump to succeed.

CVSS v3
4.4
EG Score
4.4MEDIUMmedium confidence
EG Risk
20
EG Risk 20/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity44% × 45%
Impact severity (EG Severity): CVSS 4.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
12th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.4): severity, escalated by confirmed exploitation. This CVE's 4.4 is its impact severity (EG Severity), not escalated.

EG Severity
4.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 4, 2024

Last Modified

April 4, 2025

References (4)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 6.1.81 (fixes >=6.0.0)—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 rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.76-1~bpo11+1 (18 versions)
  • every version up to 6.1.82-1: fixed in 6.1.82-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.9-1: fixed in 6.7.9-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.9-1: fixed in 6.7.9-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 97 of 208 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 111 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-26745?
CVE-2024-26745 is a medium-severity vulnerability; its CVE record was published on April 4, 2024. In the Linux kernel, the following vulnerability has been resolved: powerpc/pseries/iommu: IOMMU table is not initialized for kdump over SR-IOV When kdump kernel tries to copy dump data over SR-IOV, LPAR panics due to NULL pointer exception: Kernel attempted to read user page (0) - exploit attempt?…
When was the CVE record for CVE-2024-26745 published?
The CVE record for CVE-2024-26745 was published on April 4, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 4, 2025; the record at its source may have been updated since.
Is CVE-2024-26745 actively exploited?
CVE-2024-26745 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-26745?
CVE-2024-26745 has a CVSS v3 base score of 4.4 (NVD).
How do I remediate CVE-2024-26745?
A fix for CVE-2024-26745 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-26745?

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

Book a Demo →Browse All CVEs