CVE-2024-36884

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.2% (12th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2024-36236 (ENISA EUVD)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:

iommu/arm-smmu: Use the correct type in nvidia_smmu_context_fault()

This was missed because of the function pointer indirection.

nvidia_smmu_context_fault() is also installed as a irq function, and the 'void *' was changed to a struct arm_smmu_domain. Since the iommu_domain is embedded at a non-zero offset this causes nvidia_smmu_context_fault() to miscompute the offset. Fixup the types.

Unable to handle kernel NULL pointer dereference at virtual address 0000000000000120 Mem abort info: ESR = 0x0000000096000004 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x04: level 0 translation fault Data abort info: ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000 CM = 0, WnR = 0, TnD = 0, TagAccess = 0 GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 user pgtable: 4k pages, 48-bit VAs, pgdp=0000000107c9f000 [0000000000000120] pgd=0000000000000000, p4d=0000000000000000 Internal error: Oops: 0000000096000004 [#1] SMP Modules linked in: CPU: 1 PID: 47 Comm: kworker/u25:0 Not tainted 6.9.0-0.rc7.58.eln136.aarch64 #1 Hardware name: Unknown NVIDIA Jetson Orin NX/NVIDIA Jetson Orin NX, BIOS 3.1-32827747 03/19/2023 Workqueue: events_unbound deferred_probe_work_func pstate: 604000c9 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : nvidia_smmu_context_fault+0x1c/0x158 lr : __free_irq+0x1d4/0x2e8 sp : ffff80008044b6f0 x29: ffff80008044b6f0 x28: ffff000080a60b18 x27: ffffd32b5172e970 x26: 0000000000000000 x25: ffff0000802f5aac x24: ffff0000802f5a30 x23: ffff0000802f5b60 x22: 0000000000000057 x21: 0000000000000000 x20: ffff0000802f5a00 x19: ffff000087d4cd80 x18: ffffffffffffffff x17: 6234362066666666 x16: 6630303078302d30 x15: ffff00008156d888 x14: 0000000000000000 x13: ffff0000801db910 x12: ffff00008156d6d0 x11: 0000000000000003 x10: ffff0000801db918 x9 : ffffd32b50f94d9c x8 : 1fffe0001032fda1 x7 : ffff00008197ed00 x6 : 000000000000000f x5 : 000000000000010e x4 : 000000000000010e x3 : 0000000000000000 x2 : ffffd32b51720cd8 x1 : ffff000087e6f700 x0 : 0000000000000057 Call trace: nvidia_smmu_context_fault+0x1c/0x158 __free_irq+0x1d4/0x2e8 free_irq+0x3c/0x80 devm_free_irq+0x64/0xa8 arm_smmu_domain_free+0xc4/0x158 iommu_domain_free+0x44/0xa0 iommu_deinit_device+0xd0/0xf8 __iommu_group_remove_device+0xcc/0xe0 iommu_bus_notifier+0x64/0xa8 notifier_call_chain+0x78/0x148 blocking_notifier_call_chain+0x4c/0x90 bus_notify+0x44/0x70 device_del+0x264/0x3e8 pci_remove_bus_device+0x84/0x120 pci_remove_root_bus+0x5c/0xc0 dw_pcie_host_deinit+0x38/0xe0 tegra_pcie_config_rp+0xc0/0x1f0 tegra_pcie_dw_probe+0x34c/0x700 platform_probe+0x70/0xe8 really_probe+0xc8/0x3a0 __driver_probe_device+0x84/0x160 driver_probe_device+0x44/0x130 __device_attach_driver+0xc4/0x170 bus_for_each_drv+0x90/0x100 __device_attach+0xa8/0x1c8 device_initial_probe+0x1c/0x30 bus_probe_device+0xb0/0xc0 deferred_probe_work_func+0xbc/0x120 process_one_work+0x194/0x490 worker_thread+0x284/0x3b0 kthread+0xf4/0x108 ret_from_fork+0x10/0x20 Code: a9b97bfd 910003fd a9025bf5 f85a0035 (b94122a1)

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
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 (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.NVD CVSS v3 · CVSS v3.0 or v3.1
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

May 30, 2024

Last Modified

August 5, 2026

References (2)

Vendor Advisories for CVE-2024-36884(1)

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

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oem-24.04a (6.8.0-1010.10) @ noble2026-10-24ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1010.10) @ noble2026-10-24ubuntu
ubuntulinux-tools-raspi (6.8.0-1009.10) @ noble2026-10-24ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-40.40) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure (6.8.0-1012.14) @ noble2026-10-24ubuntu
redhatkernel-0:5.14.0-503.11.1.el9_52024-11-12redhat
linuxKernel @ 6.8.10 (fixes >=6.8.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.8.11-1: fixed in 6.8.11-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.11-1: fixed in 6.8.11-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(5)

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 7× in last 7d / 36× 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 96 of 213 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 117 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-36884?
CVE-2024-36884 is a medium-severity vulnerability; its CVE record was published on May 30, 2024. In the Linux kernel, the following vulnerability has been resolved: iommu/arm-smmu: Use the correct type in nvidia_smmu_context_fault() This was missed because of the function pointer indirection. nvidia_smmu_context_fault() is also installed as a irq function, and the 'void *' was changed to a…
When was the CVE record for CVE-2024-36884 published?
The CVE record for CVE-2024-36884 was published on May 30, 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2024-36884 actively exploited?
CVE-2024-36884 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-36884?
CVE-2024-36884 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-36884?
A fix for CVE-2024-36884 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-36884 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-36884?

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

Book a Demo →Browse All CVEs