CVE-2024-26957

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-05-01. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 5 sources updated this week

Also known asEUVD-2024-24219 (ENISA EUVD) · GHSA-7x33-7jjx-2gmh (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

s390/zcrypt: fix reference counting on zcrypt card objects

Tests with hot-plugging crytpo cards on KVM guests with debug kernel build revealed an use after free for the load field of the struct zcrypt_card. The reason was an incorrect reference handling of the zcrypt card object which could lead to a free of the zcrypt card object while it was still in use.

This is an example of the slab message:

kernel: 0x00000000885a7512-0x00000000885a7513 @offset=1298. First byte 0x68 instead of 0x6b kernel: Allocated in zcrypt_card_alloc+0x36/0x70 [zcrypt] age=18046 cpu=3 pid=43 kernel: kmalloc_trace+0x3f2/0x470 kernel: zcrypt_card_alloc+0x36/0x70 [zcrypt] kernel: zcrypt_cex4_card_probe+0x26/0x380 [zcrypt_cex4] kernel: ap_device_probe+0x15c/0x290 kernel: really_probe+0xd2/0x468 kernel: driver_probe_device+0x40/0xf0 kernel: __device_attach_driver+0xc0/0x140 kernel: bus_for_each_drv+0x8c/0xd0 kernel: __device_attach+0x114/0x198 kernel: bus_probe_device+0xb4/0xc8 kernel: device_add+0x4d2/0x6e0 kernel: ap_scan_adapter+0x3d0/0x7c0 kernel: ap_scan_bus+0x5a/0x3b0 kernel: ap_scan_bus_wq_callback+0x40/0x60 kernel: process_one_work+0x26e/0x620 kernel: worker_thread+0x21c/0x440 kernel: Freed in zcrypt_card_put+0x54/0x80 [zcrypt] age=9024 cpu=3 pid=43 kernel: kfree+0x37e/0x418 kernel: zcrypt_card_put+0x54/0x80 [zcrypt] kernel: ap_device_remove+0x4c/0xe0 kernel: device_release_driver_internal+0x1c4/0x270 kernel: bus_remove_device+0x100/0x188 kernel: device_del+0x164/0x3c0 kernel: device_unregister+0x30/0x90 kernel: ap_scan_adapter+0xc8/0x7c0 kernel: ap_scan_bus+0x5a/0x3b0 kernel: ap_scan_bus_wq_callback+0x40/0x60 kernel: process_one_work+0x26e/0x620 kernel: worker_thread+0x21c/0x440 kernel: kthread+0x150/0x168 kernel: __ret_from_fork+0x3c/0x58 kernel: ret_from_fork+0xa/0x30 kernel: Slab 0x00000372022169c0 objects=20 used=18 fp=0x00000000885a7c88 flags=0x3ffff00000000a00(workingset|slab|node=0|zone=1|lastcpupid=0x1ffff) kernel: Object 0x00000000885a74b8 @offset=1208 fp=0x00000000885a7c88 kernel: Redzone 00000000885a74b0: bb bb bb bb bb bb bb bb ........ kernel: Object 00000000885a74b8: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk kernel: Object 00000000885a74c8: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk kernel: Object 00000000885a74d8: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk kernel: Object 00000000885a74e8: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk kernel: Object 00000000885a74f8: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk kernel: Object 00000000885a7508: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 68 4b 6b 6b 6b a5 kkkkkkkkkkhKkkk. kernel: Redzone 00000000885a7518: bb bb bb bb bb bb bb bb ........ kernel: Padding 00000000885a756c: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a ZZZZZZZZZZZZ kernel: CPU: 0 PID: 387 Comm: systemd-udevd Not tainted 6.8.0-HF #2 kernel: Hardware name: IBM 3931 A01 704 (KVM/Linux) kernel: Call Trace: kernel: [<00000000ca5ab5b8>] dump_stack_lvl+0x90/0x120 kernel: [<00000000c99d78bc>] check_bytes_and_report+0x114/0x140 kernel: [<00000000c99d53cc>] check_object+0x334/0x3f8 kernel: [<00000000c99d820c>] alloc_debug_processing+0xc4/0x1f8 kernel: [<00000000c99d852e>] get_partial_node.part.0+0x1ee/0x3e0 kernel: [<00000000c99d94ec>] ___slab_alloc+0xaf4/0x13c8 kernel: [<00000000c99d9e38>] __slab_alloc.constprop.0+0x78/0xb8 kernel: [<00000000c99dc8dc>] __kmalloc+0x434/0x590 kernel: [<00000000c9b4c0ce>] ext4_htree_store_dirent+0x4e/0x1c0 kernel: [<00000000c9b908a2>] htree_dirblock_to_tree+0x17a/0x3f0 kernel: ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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
15th
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 (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-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-29). 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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 1, 2024

Last Modified

October 15, 2026

Advisory Details (9)

Auto-updated Aug 4, 2026
Patch available.
Web page

s390/zcrypt: fix reference counting on zcrypt card objects - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/394b6d8bbdf9ddee6d5bcf3e1f3e9f23eecd6484
Web page

s390/zcrypt: fix reference counting on zcrypt card objects - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/befb7f889594d23e1b475720cf93efd2f77df000
Web page

s390/zcrypt: fix reference counting on zcrypt card objects - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b7f6c3630eb3f103115ab0d7613588064f665d0d
Web page

s390/zcrypt: fix reference counting on zcrypt card objects - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a64ab862e84e3e698cd351a87cdb504c7fc575ca
Web page

s390/zcrypt: fix reference counting on zcrypt card objects - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a55677878b93e9ebc31f66d0e2fb93be5e7836a6
Web page

s390/zcrypt: fix reference counting on zcrypt card objects - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9daddee03de3f231012014dab8ab2b277a116a55
Web page

s390/zcrypt: fix reference counting on zcrypt card objects - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7e500849fa558879a1cde43f80c7c048c2437058
Web page

s390/zcrypt: fix reference counting on zcrypt card objects - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6470078ab3d8f222115e11c4ec67351f3031b3dd
Web page

s390/zcrypt: fix reference counting on zcrypt card objects - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/50ed48c80fecbe17218afed4f8bed005c802976c

Vendor Advisories for CVE-2024-26957(1)

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

Patch Availability(19)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.116.116) @ jammy2026-10-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-35.35) @ noble2026-10-30ubuntu
ubuntulinux-tools-gcp (6.8.0-1008.9) @ noble2026-10-30ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1006.6+1) @ noble2026-10-30ubuntu
ubuntulinux-tools-gke (6.8.0-1004.7) @ noble2026-10-30ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1006.6) @ noble2026-10-30ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.189.187) @ focal2026-10-30ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.189.209~18.04.1) @ bionic2026-10-30ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.116.106) @ jammy2026-10-30ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1047 (5.4.0-1047.51) @ focal2026-10-30ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.116.126~20.04.1) @ focal2026-10-30ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1112.142) @ focal2026-10-30ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1068.66) @ jammy2026-10-30ubuntu
ubuntulinux-tools-iot (5.4.0.1040.38) @ focal2026-10-30ubuntu
ubuntulinux-tools-aws-edge (5.15.0.1065.71~20.04.1) @ focal2026-10-30ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1065.73~20.04.1) @ focal2026-10-30ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1058.56) @ jammy2026-10-30ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1035.39) @ jammy2026-10-30ubuntu
linuxKernel @ 4.19.312 (fixes >=4.10.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

(5 across 5 ecosystems)
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
linux-5.105.10.136-1~deb10u1 ... 5.10.209-2~deb10u1 (13 versions)
  • every version up to 5.10.216-1~deb10u1: fixed in 5.10.216-1~deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (39 versions)
  • every version up to 5.10.216-1: fixed in 5.10.216-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.82-1 (19 versions)
  • every version up to 6.1.85-1: fixed in 6.1.85-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.12-1: fixed in 6.7.12-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.12-1: fixed in 6.7.12-1
—

Weakness Classification(1)

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

All Vendor Advisories

(18)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 11× in last 7d / 45× 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 98 of 225 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 127 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% · 15th percentile
  2. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.2% · 15th 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-30 01:32 UTCEG score recompute
  6. 2026-10-30 01:32 UTCVendor advisory
  7. 2026-10-30 01:32 UTCGHSA enrichmentGHSA-7x33-7jjx-2gmh · GitHub severity HIGH · GitHub CVSS 7.8
  8. 2026-10-30 00:55 UTCOSV refresh
  9. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  10. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  11. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  12. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  13. 2026-10-25 17:15 UTCEG score recompute
  14. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  15. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  16. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  17. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  18. 2026-10-22 13:41 UTCEG score recompute
  19. 2026-10-22 13:41 UTCVendor advisory
  20. 2026-10-22 13:41 UTCGHSA enrichmentGHSA-7x33-7jjx-2gmh · GitHub severity HIGH · GitHub CVSS 7.8
  21. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  22. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  23. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  24. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  25. 2026-10-18 07:22 UTCEG score recompute
Show 73 more
  1. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  2. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  3. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  4. 2026-10-15 01:47 UTCGHSA enrichmentGHSA-7x33-7jjx-2gmh · GitHub severity HIGH · GitHub CVSS 7.8
  5. 2026-10-15 01:10 UTCEG score recompute
  6. 2026-10-15 01:10 UTCGHSA enrichmentGHSA-7x33-7jjx-2gmh · GitHub severity HIGH · GitHub CVSS 7.8
  7. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  8. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  9. 2026-10-12 17:59 UTCEG score recompute
  10. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  11. 2026-10-11 21:23 UTCEG score recompute
  12. 2026-10-11 16:17 UTCEG score recompute
  13. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  14. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  15. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  16. 2026-10-08 17:07 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  17. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  18. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  19. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  20. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  21. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  22. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  23. 2026-09-30 17:00 UTCEG score recompute
  24. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  25. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  26. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  27. 2026-09-27 01:42 UTCOSV refresh
  28. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  29. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  30. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  31. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  32. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  33. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  34. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  35. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  36. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  37. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  38. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  39. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  40. 2026-09-07 10:47 UTCOSV refresh
  41. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  42. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  43. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  44. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  45. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  46. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  47. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  48. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  49. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  50. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  51. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  52. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  53. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  54. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  55. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  56. 2026-08-20 19:31 UTCOSV refresh
  57. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  58. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  59. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  60. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  61. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  62. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  63. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  64. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  65. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  66. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  67. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  68. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  69. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  70. 2026-08-05 12:19 UTCEG score recompute
  71. 2026-08-05 12:19 UTCVendor advisory
  72. 2026-08-05 12:19 UTCGHSA enrichmentGHSA-7x33-7jjx-2gmh · GitHub severity HIGH · GitHub CVSS 7.8
  73. 2026-08-04 15:08 UTCEPSS rescoreEPSS 0.2% · 15th percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-26957?
CVE-2024-26957 is a high-severity vulnerability; its CVE record was published on May 1, 2024. In the Linux kernel, the following vulnerability has been resolved: s390/zcrypt: fix reference counting on zcrypt card objects Tests with hot-plugging crytpo cards on KVM guests with debug kernel build revealed an use after free for the load field of the struct zcrypt_card. The reason was an…
When was the CVE record for CVE-2024-26957 published?
The CVE record for CVE-2024-26957 was published on May 1, 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 15, 2026; the record at its source may have been updated since.
Is CVE-2024-26957 actively exploited?
CVE-2024-26957 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-26957?
CVE-2024-26957 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-26957?
A fix for CVE-2024-26957 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-26957 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-26957

Explore →

Is Your Infrastructure Affected by CVE-2024-26957?

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

Book a Demo →Browse All CVEs