CVE-2024-45005

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-09-04. 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-41575 (ENISA EUVD) · GHSA-cj8h-mjwg-43cc (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:

KVM: s390: fix validity interception issue when gisa is switched off

We might run into a SIE validity if gisa has been disabled either via using kernel parameter "kvm.use_gisa=0" or by setting the related sysfs attribute to N (echo N >/sys/module/kvm/parameters/use_gisa).

The validity is caused by an invalid value in the SIE control block's gisa designation. That happens because we pass the uninitialized gisa origin to virt_to_phys() before writing it to the gisa designation.

To fix this we return 0 in kvm_s390_get_gisa_desc() if the origin is 0. kvm_s390_get_gisa_desc() is used to determine which gisa designation to set in the SIE control block. A value of 0 in the gisa designation disables gisa usage.

The issue surfaces in the host kernel with the following kernel message as soon a new kvm guest start is attemted.

kvm: unhandled validity intercept 0x1011 WARNING: CPU: 0 PID: 781237 at arch/s390/kvm/intercept.c:101 kvm_handle_sie_intercept+0x42e/0x4d0 [kvm] Modules linked in: vhost_net tap tun xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT xt_tcpudp nft_compat x_tables nf_nat_tftp nf_conntrack_tftp vfio_pci_core irqbypass vhost_vsock vmw_vsock_virtio_transport_common vsock vhost vhost_iotlb kvm nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables sunrpc mlx5_ib ib_uverbs ib_core mlx5_core uvdevice s390_trng eadm_sch vfio_ccw zcrypt_cex4 mdev vfio_iommu_type1 vfio sch_fq_codel drm i2c_core loop drm_panel_orientation_quirks configfs nfnetlink lcs ctcm fsm dm_service_time ghash_s390 prng chacha_s390 libchacha aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common dm_mirror dm_region_hash dm_log zfcp scsi_transport_fc scsi_dh_rdac scsi_dh_emc scsi_dh_alua pkey zcrypt dm_multipath rng_core autofs4 [last unloaded: vfio_pci] CPU: 0 PID: 781237 Comm: CPU 0/KVM Not tainted 6.10.0-08682-gcad9f11498ea #6 Hardware name: IBM 3931 A01 701 (LPAR) Krnl PSW : 0704c00180000000 000003d93deb0122 (kvm_handle_sie_intercept+0x432/0x4d0 [kvm]) R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 Krnl GPRS: 000003d900000027 000003d900000023 0000000000000028 000002cd00000000 000002d063a00900 00000359c6daf708 00000000000bebb5 0000000000001eff 000002cfd82e9000 000002cfd80bc000 0000000000001011 000003d93deda412 000003ff8962df98 000003d93de77ce0 000003d93deb011e 00000359c6daf960 Krnl Code: 000003d93deb0112: c020fffe7259 larl %r2,000003d93de7e5c4 000003d93deb0118: c0e53fa8beac brasl %r14,000003d9bd3c7e70 #000003d93deb011e: af000000 mc 0,0 >000003d93deb0122: a728ffea lhi %r2,-22 000003d93deb0126: a7f4fe24 brc 15,000003d93deafd6e 000003d93deb012a: 9101f0b0 tm 176(%r15),1 000003d93deb012e: a774fe48 brc 7,000003d93deafdbe 000003d93deb0132: 40a0f0ae sth %r10,174(%r15) Call Trace: [<000003d93deb0122>] kvm_handle_sie_intercept+0x432/0x4d0 [kvm] ([<000003d93deb011e>] kvm_handle_sie_intercept+0x42e/0x4d0 [kvm]) [<000003d93deacc10>] vcpu_post_run+0x1d0/0x3b0 [kvm] [<000003d93deaceda>] __vcpu_run+0xea/0x2d0 [kvm] [<000003d93dead9da>] kvm_arch_vcpu_ioctl_run+0x16a/0x430 [kvm] [<000003d93de93ee0>] kvm_vcpu_ioctl+0x190/0x7c0 [kvm] [<000003d9bd728b4e>] vfs_ioctl+0x2e/0x70 [<000003d9bd72a092>] __s390x_sys_ioctl+0xc2/0xd0 [<000003d9be0e9222>] __do_syscall+0x1f2/0x2e0 [<000003d9be0f9a90>] system_call+0x70/0x98 Last Breaking-Event-Address: [<000003d9bd3c7f58>] __warn_printk+0xe8/0xf0

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
11th
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

September 4, 2024

Last Modified

October 9, 2024

References (3)

Vendor Advisories for CVE-2024-45005(2)

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-nvidia-lowlatency-64k (6.8.0-1019.21.1) @ noble2026-10-24ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-50.51~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-virtual-hwe-24.04 (6.8.0-50.51) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure (6.8.0-1020.23) @ noble2026-10-24ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1002.4) @ noble2026-10-24ubuntu
redhatkernel-0:5.14.0-503.11.1.el9_52024-11-12redhat
linuxKernel @ 6.6.48 (fixes >=6.2.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.10.7-1: fixed in 6.10.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.10.7-1: fixed in 6.10.7-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 / 39× 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 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. 4 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-01 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  2. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  3. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  4. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  5. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  6. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  7. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  8. 2026-10-25 17:02 UTCEG score recompute
  9. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  10. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-10-24 05:12 UTCEG score recompute
  12. 2026-10-24 05:12 UTCVendor advisory
  13. 2026-10-24 05:12 UTCGHSA enrichmentGHSA-cj8h-mjwg-43cc · GitHub CVSS 5.5
  14. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  17. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-10-18 07:00 UTCEG score recompute
  21. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  22. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  23. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  24. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  25. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
Show 71 more
  1. 2026-10-12 17:45 UTCEG score recompute
  2. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-10-11 21:11 UTCEG score recompute
  4. 2026-10-11 16:03 UTCEG score recompute
  5. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-10-10 00:33 UTCOSV refresh
  8. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  13. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-09-30 19:53 UTCEG score recompute
  17. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-09-26 15:57 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% · 11th percentile
  24. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  25. 2026-09-21 20:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  26. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  27. 2026-09-20 08:43 UTCOSV refresh
  28. 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  29. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  30. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  31. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  32. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  33. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  34. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  35. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  36. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  37. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  38. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  39. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  40. 2026-09-05 15:27 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  41. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  42. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  43. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  44. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  45. 2026-09-01 11:36 UTCOSV refresh
  46. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  47. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  48. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  49. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  50. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  51. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  52. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  53. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  54. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  55. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  56. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  57. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  58. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  59. 2026-08-15 11:07 UTCOSV refresh
  60. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  61. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  62. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  63. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  64. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  65. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  66. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  67. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  68. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  69. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  70. 2026-08-04 15:08 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  71. 2026-08-04 10:36 UTCEPSS rescoreEPSS 0.2% · 11th percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-45005?
CVE-2024-45005 is a medium-severity vulnerability; its CVE record was published on September 4, 2024. In the Linux kernel, the following vulnerability has been resolved: KVM: s390: fix validity interception issue when gisa is switched off We might run into a SIE validity if gisa has been disabled either via using kernel parameter "kvm.use_gisa=0" or by setting the related sysfs attribute to N (echo…
When was the CVE record for CVE-2024-45005 published?
The CVE record for CVE-2024-45005 was published on September 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 October 9, 2024; the record at its source may have been updated since.
Is CVE-2024-45005 actively exploited?
CVE-2024-45005 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-45005?
CVE-2024-45005 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-45005?
A fix for CVE-2024-45005 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-45005 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-45005

Explore →

Is Your Infrastructure Affected by CVE-2024-45005?

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

Book a Demo →Browse All CVEs