CVE-2023-53093

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-05-02. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

tracing: Do not let histogram values have some modifiers

Histogram values can not be strings, stacktraces, graphs, symbols, syscalls, or grouped in buckets or log. Give an error if a value is set to do so.

Note, the histogram code was not prepared to handle these modifiers for histograms and caused a bug.

Mark Rutland reported:

# echo 'p:copy_to_user __arch_copy_to_user n=$arg2' >> /sys/kernel/tracing/kprobe_events # echo 'hist:keys=n:vals=hitcount.buckets=8:sort=hitcount' > /sys/kernel/tracing/events/kprobes/copy_to_user/trigger # cat /sys/kernel/tracing/events/kprobes/copy_to_user/hist [ 143.694628] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 [ 143.695190] Mem abort info: [ 143.695362] ESR = 0x0000000096000004 [ 143.695604] EC = 0x25: DABT (current EL), IL = 32 bits [ 143.695889] SET = 0, FnV = 0 [ 143.696077] EA = 0, S1PTW = 0 [ 143.696302] FSC = 0x04: level 0 translation fault [ 143.702381] Data abort info: [ 143.702614] ISV = 0, ISS = 0x00000004 [ 143.702832] CM = 0, WnR = 0 [ 143.703087] user pgtable: 4k pages, 48-bit VAs, pgdp=00000000448f9000 [ 143.703407] [0000000000000000] pgd=0000000000000000, p4d=0000000000000000 [ 143.704137] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP [ 143.704714] Modules linked in: [ 143.705273] CPU: 0 PID: 133 Comm: cat Not tainted 6.2.0-00003-g6fc512c10a7c #3 [ 143.706138] Hardware name: linux,dummy-virt (DT) [ 143.706723] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 143.707120] pc : hist_field_name.part.0+0x14/0x140 [ 143.707504] lr : hist_field_name.part.0+0x104/0x140 [ 143.707774] sp : ffff800008333a30 [ 143.707952] x29: ffff800008333a30 x28: 0000000000000001 x27: 0000000000400cc0 [ 143.708429] x26: ffffd7a653b20260 x25: 0000000000000000 x24: ffff10d303ee5800 [ 143.708776] x23: ffffd7a6539b27b0 x22: ffff10d303fb8c00 x21: 0000000000000001 [ 143.709127] x20: ffff10d303ec2000 x19: 0000000000000000 x18: 0000000000000000 [ 143.709478] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000 [ 143.709824] x14: 0000000000000000 x13: 203a6f666e692072 x12: 6567676972742023 [ 143.710179] x11: 0a230a6d6172676f x10: 000000000000002c x9 : ffffd7a6521e018c [ 143.710584] x8 : 000000000000002c x7 : 7f7f7f7f7f7f7f7f x6 : 000000000000002c [ 143.710915] x5 : ffff10d303b0103e x4 : ffffd7a653b20261 x3 : 000000000000003d [ 143.711239] x2 : 0000000000020001 x1 : 0000000000000001 x0 : 0000000000000000 [ 143.711746] Call trace: [ 143.712115] hist_field_name.part.0+0x14/0x140 [ 143.712642] hist_field_name.part.0+0x104/0x140 [ 143.712925] hist_field_print+0x28/0x140 [ 143.713125] event_hist_trigger_print+0x174/0x4d0 [ 143.713348] hist_show+0xf8/0x980 [ 143.713521] seq_read_iter+0x1bc/0x4b0 [ 143.713711] seq_read+0x8c/0xc4 [ 143.713876] vfs_read+0xc8/0x2a4 [ 143.714043] ksys_read+0x70/0xfc [ 143.714218] __arm64_sys_read+0x24/0x30 [ 143.714400] invoke_syscall+0x50/0x120 [ 143.714587] el0_svc_common.constprop.0+0x4c/0x100 [ 143.714807] do_el0_svc+0x44/0xd0 [ 143.714970] el0_svc+0x2c/0x84 [ 143.715134] el0t_64_sync_handler+0xbc/0x140 [ 143.715334] el0t_64_sync+0x190/0x194 [ 143.715742] Code: a9bd7bfd 910003fd a90153f3 aa0003f3 (f9400000) [ 143.716510] ---[ end trace 0000000000000000 ]--- Segmentation fault

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

May 2, 2025

Last Modified

November 12, 2025

References (3)

Vendor Advisories for CVE-2023-53093(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.1.23—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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2023-53093?
CVE-2023-53093 is a medium vulnerability published on May 2, 2025. In the Linux kernel, the following vulnerability has been resolved: tracing: Do not let histogram values have some modifiers Histogram values can not be strings, stacktraces, graphs, symbols, syscalls, or grouped in buckets or log. Give an error if a value is set to do so. Note, the histogram code…
When was CVE-2023-53093 disclosed?
CVE-2023-53093 was first published in the National Vulnerability Database on May 2, 2025, with the most recent update on November 12, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-53093 actively exploited?
CVE-2023-53093 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.9% of all scored CVEs.
What is the CVSS score of CVE-2023-53093?
CVE-2023-53093 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-53093?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-53093, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-53093

Explore →

Is Your Infrastructure Affected by CVE-2023-53093?

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

Start Free Scan →Browse All CVEs