CVE-2024-26738

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

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

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

Also known asEUVD-2024-24000 (ENISA EUVD) · GHSA-m5hg-cjq4-86mq (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
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: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

powerpc/pseries/iommu: DLPAR add doesn't completely initialize pci_controller

When a PCI device is dynamically added, the kernel oopses with a NULL pointer dereference:

BUG: Kernel NULL pointer dereference on read at 0x00000030 Faulting instruction address: 0xc0000000006bbe5c Oops: Kernel access of bad area, sig: 11 [#1] LE PAGE_SIZE=64K MMU=Radix SMP NR_CPUS=2048 NUMA pSeries Modules linked in: rpadlpar_io rpaphp rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache netfs xsk_diag bonding nft_compat nf_tables nfnetlink rfkill binfmt_misc dm_multipath rpcrdma sunrpc rdma_ucm ib_srpt ib_isert iscsi_target_mod target_core_mod ib_umad ib_iser libiscsi scsi_transport_iscsi ib_ipoib rdma_cm iw_cm ib_cm mlx5_ib ib_uverbs ib_core pseries_rng drm drm_panel_orientation_quirks xfs libcrc32c mlx5_core mlxfw sd_mod t10_pi sg tls ibmvscsi ibmveth scsi_transport_srp vmx_crypto pseries_wdt psample dm_mirror dm_region_hash dm_log dm_mod fuse CPU: 17 PID: 2685 Comm: drmgr Not tainted 6.7.0-203405+ #66 Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1060.00 (NH1060_008) hv:phyp pSeries NIP: c0000000006bbe5c LR: c000000000a13e68 CTR: c0000000000579f8 REGS: c00000009924f240 TRAP: 0300 Not tainted (6.7.0-203405+) MSR: 8000000000009033 CR: 24002220 XER: 20040006 CFAR: c000000000a13e64 DAR: 0000000000000030 DSISR: 40000000 IRQMASK: 0 ... NIP sysfs_add_link_to_group+0x34/0x94 LR iommu_device_link+0x5c/0x118 Call Trace: iommu_init_device+0x26c/0x318 (unreliable) iommu_device_link+0x5c/0x118 iommu_init_device+0xa8/0x318 iommu_probe_device+0xc0/0x134 iommu_bus_notifier+0x44/0x104 notifier_call_chain+0xb8/0x19c blocking_notifier_call_chain+0x64/0x98 bus_notify+0x50/0x7c device_add+0x640/0x918 pci_device_add+0x23c/0x298 of_create_pci_dev+0x400/0x884 of_scan_pci_dev+0x124/0x1b0 __of_scan_bus+0x78/0x18c pcibios_scan_phb+0x2a4/0x3b0 init_phb_dynamic+0xb8/0x110 dlpar_add_slot+0x170/0x3b8 [rpadlpar_io] add_slot_store.part.0+0xb4/0x130 [rpadlpar_io] kobj_attr_store+0x2c/0x48 sysfs_kf_write+0x64/0x78 kernfs_fop_write_iter+0x1b0/0x290 vfs_write+0x350/0x4a0 ksys_write+0x84/0x140 system_call_exception+0x124/0x330 system_call_vectored_common+0x15c/0x2ec

Commit a940904443e4 ("powerpc/iommu: Add iommu_ops to report capabilities and allow blocking domains") broke DLPAR add of PCI devices.

The above added iommu_device structure to pci_controller. During system boot, PCI devices are discovered and this newly added iommu_device structure is initialized by a call to iommu_device_register().

During DLPAR add of a PCI device, a new pci_controller structure is allocated but there are no calls made to iommu_device_register() interface.

Fix is to register the iommu device during DLPAR add as well.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 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
14th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 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 3, 2024

Last Modified

January 7, 2025

References (3)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 6.6.19 (fixes >=6.4.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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.7-1: fixed in 6.7.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.7-1: fixed in 6.7.7-1
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-26738?
CVE-2024-26738 is a medium-severity vulnerability; its CVE record was published on April 3, 2024. In the Linux kernel, the following vulnerability has been resolved: powerpc/pseries/iommu: DLPAR add doesn't completely initialize pci_controller When a PCI device is dynamically added, the kernel oopses with a NULL pointer dereference: BUG: Kernel NULL pointer dereference on read at 0x00000030…
When was the CVE record for CVE-2024-26738 published?
The CVE record for CVE-2024-26738 was published on April 3, 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 January 7, 2025; the record at its source may have been updated since.
Is CVE-2024-26738 actively exploited?
CVE-2024-26738 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-26738?
CVE-2024-26738 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-26738?
A fix for CVE-2024-26738 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-26738

Explore →

Is Your Infrastructure Affected by CVE-2024-26738?

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

Book a Demo →Browse All CVEs