CVE-2023-53702

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week

Also known asEUVD-2023-60026 (ENISA EUVD) · GHSA-28rv-6x7m-q268 (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

s390/crypto: use vector instructions only if available for ChaCha20

Commit 349d03ffd5f6 ("crypto: s390 - add crypto library interface for ChaCha20") added a library interface to the s390 specific ChaCha20 implementation. However no check was added to verify if the required facilities are installed before branching into the assembler code.

If compiled into the kernel, this will lead to the following crash, if vector instructions are not available:

data exception: 0007 ilc:3 [#1] SMP Modules linked in: CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.3.0-rc7+ #11 Hardware name: IBM 3931 A01 704 (KVM/Linux) Krnl PSW : 0704e00180000000 000000001857277a (chacha20_vx+0x32/0x818) R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 Krnl GPRS: 0000037f0000000a ffffffffffffff60 000000008184b000 0000000019f5c8e6 0000000000000109 0000037fffb13c58 0000037fffb13c78 0000000019bb1780 0000037fffb13c58 0000000019f5c8e6 000000008184b000 0000000000000109 00000000802d8000 0000000000000109 0000000018571ebc 0000037fffb13718 Krnl Code: 000000001857276a: c07000b1f80b larl %r7,0000000019bb1780 0000000018572770: a708000a lhi %r0,10 #0000000018572774: e78950000c36 vlm %v24,%v25,0(%r5),0 >000000001857277a: e7a060000806 vl %v26,0(%r6),0 0000000018572780: e7bf70004c36 vlm %v27,%v31,0(%r7),4 0000000018572786: e70b00000456 vlr %v0,%v27 000000001857278c: e71800000456 vlr %v1,%v24 0000000018572792: e74b00000456 vlr %v4,%v27 Call Trace: [<000000001857277a>] chacha20_vx+0x32/0x818 Last Breaking-Event-Address: [<0000000018571eb6>] chacha20_crypt_s390.constprop.0+0x6e/0xd8 ---[ end trace 0000000000000000 ]--- Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

Fix this by adding a missing MACHINE_HAS_VX check.

[agordeev@linux.ibm.com: remove duplicates in commit message]

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
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)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). 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
No SSVC decision: EchelonGraph has not assessed this CVECISA 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 BOD 26-04 block below.

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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

October 22, 2025

Last Modified

October 28, 2026

References (3)

Vendor Advisories for CVE-2023-53702(1)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-503.11.1.el9_52024-11-12redhat
linuxKernel @ 6.1.30 (fixes >=5.19.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
  • every version up to 6.1.37-1: fixed in 6.1.37-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.3.7-1: fixed in 6.3.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.3.7-1: fixed in 6.3.7-1
—

Data Freshness Timeline

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

Related CVEs(same vendor)

Frequently asked(4)

What is CVE-2023-53702?
CVE-2023-53702 is a vulnerability whose severity is not yet rated; its CVE record was published on October 22, 2025. In the Linux kernel, the following vulnerability has been resolved: s390/crypto: use vector instructions only if available for ChaCha20 Commit 349d03ffd5f6 ("crypto: s390 - add crypto library interface for ChaCha20") added a library interface to the s390 specific ChaCha20 implementation. However no…
When was the CVE record for CVE-2023-53702 published?
The CVE record for CVE-2023-53702 was published on October 22, 2025. 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 28, 2026; the record at its source may have been updated since.
Is CVE-2023-53702 actively exploited?
CVE-2023-53702 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).
How do I remediate CVE-2023-53702?
A fix for CVE-2023-53702 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-53702 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-2023-53702

Explore →

Is Your Infrastructure Affected by CVE-2023-53702?

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

Book a Demo →Browse All CVEs