CVE-2023-53135

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2025-05-02. NVD baseline CVSS 7.1; sources differ by 0.0.

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

Also known asEUVD-2025-13129 (ENISA EUVD) · GHSA-2c79-g4hv-82qp (GitHub Security Advisories)Source: ENISA EUVD

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

A fix is available — apply it.

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

riscv: Use READ_ONCE_NOCHECK in imprecise unwinding stack mode

When CONFIG_FRAME_POINTER is unset, the stack unwinding function walk_stackframe randomly reads the stack and then, when KASAN is enabled, it can lead to the following backtrace:

[ 0.000000] ================================================================== [ 0.000000] BUG: KASAN: stack-out-of-bounds in walk_stackframe+0xa6/0x11a [ 0.000000] Read of size 8 at addr ffffffff81807c40 by task swapper/0 [ 0.000000] [ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 6.2.0-12919-g24203e6db61f #43 [ 0.000000] Hardware name: riscv-virtio,qemu (DT) [ 0.000000] Call Trace: [ 0.000000] [] walk_stackframe+0x0/0x11a [ 0.000000] [] init_param_lock+0x26/0x2a [ 0.000000] [] walk_stackframe+0xa2/0x11a [ 0.000000] [] dump_stack_lvl+0x22/0x36 [ 0.000000] [] print_report+0x198/0x4a8 [ 0.000000] [] init_param_lock+0x26/0x2a [ 0.000000] [] walk_stackframe+0xa2/0x11a [ 0.000000] [] kasan_report+0x9a/0xc8 [ 0.000000] [] walk_stackframe+0xa2/0x11a [ 0.000000] [] walk_stackframe+0xa2/0x11a [ 0.000000] [] desc_make_final+0x80/0x84 [ 0.000000] [] stack_trace_save+0x88/0xa6 [ 0.000000] [] filter_irq_stacks+0x72/0x76 [ 0.000000] [] devkmsg_read+0x32a/0x32e [ 0.000000] [] kasan_save_stack+0x28/0x52 [ 0.000000] [] desc_make_final+0x7c/0x84 [ 0.000000] [] stack_trace_save+0x84/0xa6 [ 0.000000] [] kasan_set_track+0x12/0x20 [ 0.000000] [] __kasan_slab_alloc+0x58/0x5e [ 0.000000] [] __kmem_cache_create+0x21e/0x39a [ 0.000000] [] create_boot_cache+0x70/0x9c [ 0.000000] [] kmem_cache_init+0x6c/0x11e [ 0.000000] [] mm_init+0xd8/0xfe [ 0.000000] [] start_kernel+0x190/0x3ca [ 0.000000] [ 0.000000] The buggy address belongs to stack of task swapper/0 [ 0.000000] and is located at offset 0 in frame: [ 0.000000] stack_trace_save+0x0/0xa6 [ 0.000000] [ 0.000000] This frame has 1 object: [ 0.000000] [32, 56) 'c' [ 0.000000] [ 0.000000] The buggy address belongs to the physical page: [ 0.000000] page:(____ptrval____) refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x81a07 [ 0.000000] flags: 0x1000(reserved|zone=0) [ 0.000000] raw: 0000000000001000 ff600003f1e3d150 ff600003f1e3d150 0000000000000000 [ 0.000000] raw: 0000000000000000 0000000000000000 00000001ffffffff [ 0.000000] page dumped because: kasan: bad access detected [ 0.000000] [ 0.000000] Memory state around the buggy address: [ 0.000000] ffffffff81807b00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 0.000000] ffffffff81807b80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 0.000000] >ffffffff81807c00: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 00 00 f3 [ 0.000000] ^ [ 0.000000] ffffffff81807c80: f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00 [ 0.000000] ffffffff81807d00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 0.000000] ==================================================================

Fix that by using READ_ONCE_NOCHECK when reading the stack in imprecise mode.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 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 BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
9th
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.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 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-27). 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 (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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'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

May 2, 2025

Last Modified

November 10, 2025

References (6)

Patch Availability(1)

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (25 versions)
  • every version up to 5.10.178-1: fixed in 5.10.178-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.20-1: fixed in 6.1.20-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.20-1: fixed in 6.1.20-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.20-1: fixed in 6.1.20-1
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-53135?
CVE-2023-53135 is a high-severity vulnerability; its CVE record was published on May 2, 2025. In the Linux kernel, the following vulnerability has been resolved: riscv: Use READ_ONCE_NOCHECK in imprecise unwinding stack mode When CONFIG_FRAME_POINTER is unset, the stack unwinding function walk_stackframe randomly reads the stack and then, when KASAN is enabled, it can lead to the following…
When was the CVE record for CVE-2023-53135 published?
The CVE record for CVE-2023-53135 was published on May 2, 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 November 10, 2025; the record at its source may have been updated since.
Is CVE-2023-53135 actively exploited?
CVE-2023-53135 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53135?
CVE-2023-53135 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2023-53135?
A fix for CVE-2023-53135 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-2023-53135

Explore →

Is Your Infrastructure Affected by CVE-2023-53135?

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

Book a Demo →Browse All CVEs