CVE-2023-53860

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-12-09. The CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 4 sources updated this week

Also known asEUVD-2023-60136 (ENISA EUVD) · GHSA-g5v9-7ppc-vg8p (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:

dm: don't attempt to queue IO under RCU protection

dm looks up the table for IO based on the request type, with an assumption that if the request is marked REQ_NOWAIT, it's fine to attempt to submit that IO while under RCU read lock protection. This is not OK, as REQ_NOWAIT just means that we should not be sleeping waiting on other IO, it does not mean that we can't potentially schedule.

A simple test case demonstrates this quite nicely:

int main(int argc, char *argv[]) { struct iovec iov; int fd;

fd = open("/dev/dm-0", O_RDONLY | O_DIRECT); posix_memalign(&iov.iov_base, 4096, 4096); iov.iov_len = 4096; preadv2(fd, &iov, 1, 0, RWF_NOWAIT); return 0; }

which will instantly spew:

BUG: sleeping function called from invalid context at include/linux/sched/mm.h:306 in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 5580, name: dm-nowait preempt_count: 0, expected: 0 RCU nest depth: 1, expected: 0 INFO: lockdep is turned off. CPU: 7 PID: 5580 Comm: dm-nowait Not tainted 6.6.0-rc1-g39956d2dcd81 #132 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 Call Trace: dump_stack_lvl+0x11d/0x1b0 __might_resched+0x3c3/0x5e0 ? preempt_count_sub+0x150/0x150 mempool_alloc+0x1e2/0x390 ? mempool_resize+0x7d0/0x7d0 ? lock_sync+0x190/0x190 ? lock_release+0x4b7/0x670 ? internal_get_user_pages_fast+0x868/0x2d40 bio_alloc_bioset+0x417/0x8c0 ? bvec_alloc+0x200/0x200 ? internal_get_user_pages_fast+0xb8c/0x2d40 bio_alloc_clone+0x53/0x100 dm_submit_bio+0x27f/0x1a20 ? lock_release+0x4b7/0x670 ? blk_try_enter_queue+0x1a0/0x4d0 ? dm_dax_direct_access+0x260/0x260 ? rcu_is_watching+0x12/0xb0 ? blk_try_enter_queue+0x1cc/0x4d0 __submit_bio+0x239/0x310 ? __bio_queue_enter+0x700/0x700 ? kvm_clock_get_cycles+0x40/0x60 ? ktime_get+0x285/0x470 submit_bio_noacct_nocheck+0x4d9/0xb80 ? should_fail_request+0x80/0x80 ? preempt_count_sub+0x150/0x150 ? lock_release+0x4b7/0x670 ? __bio_add_page+0x143/0x2d0 ? iov_iter_revert+0x27/0x360 submit_bio_noacct+0x53e/0x1b30 submit_bio_wait+0x10a/0x230 ? submit_bio_wait_endio+0x40/0x40 __blkdev_direct_IO_simple+0x4f8/0x780 ? blkdev_bio_end_io+0x4c0/0x4c0 ? stack_trace_save+0x90/0xc0 ? __bio_clone+0x3c0/0x3c0 ? lock_release+0x4b7/0x670 ? lock_sync+0x190/0x190 ? atime_needs_update+0x3bf/0x7e0 ? timestamp_truncate+0x21b/0x2d0 ? inode_owner_or_capable+0x240/0x240 blkdev_direct_IO.part.0+0x84a/0x1810 ? rcu_is_watching+0x12/0xb0 ? lock_release+0x4b7/0x670 ? blkdev_read_iter+0x40d/0x530 ? reacquire_held_locks+0x4e0/0x4e0 ? __blkdev_direct_IO_simple+0x780/0x780 ? rcu_is_watching+0x12/0xb0 ? __mark_inode_dirty+0x297/0xd50 ? preempt_count_add+0x72/0x140 blkdev_read_iter+0x2a4/0x530 do_iter_readv_writev+0x2f2/0x3c0 ? generic_copy_file_range+0x1d0/0x1d0 ? fsnotify_perm.part.0+0x25d/0x630 ? security_file_permission+0xd8/0x100 do_iter_read+0x31b/0x880 ? import_iovec+0x10b/0x140 vfs_readv+0x12d/0x1a0 ? vfs_iter_read+0xb0/0xb0 ? rcu_is_watching+0x12/0xb0 ? rcu_is_watching+0x12/0xb0 ? lock_release+0x4b7/0x670 do_preadv+0x1b3/0x260 ? do_readv+0x370/0x370 __x64_sys_preadv2+0xef/0x150 do_syscall_64+0x39/0xb0 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f5af41ad806 Code: 41 54 41 89 fc 55 44 89 c5 53 48 89 cb 48 83 ec 18 80 3d e4 dd 0d 00 00 74 7a 45 89 c1 49 89 ca 45 31 c0 b8 47 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 be 00 00 00 48 85 c0 79 4a 48 8b 0d da 55 RSP: 002b:00007ffd3145c7f0 EFLAGS: 00000246 ORIG_RAX: 0000000000000147 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f5af41ad806 RDX: 0000000000000001 RSI: 00007ffd3145c850 RDI: 0000000000000003 RBP: 0000000000000008 R08: 0000000000000000 R09: 0000000000000008 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000003 R13: 00007ffd3145c850 R14: 000055f5f0431dd8 R15: 0000000000000001

where in fact it is ---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 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
8th
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-11-02). 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

December 9, 2025

Last Modified

August 5, 2026

Advisory Details (3)

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

dm: don't attempt to queue IO under RCU protection - kernel/git/stable/linux.git - Linux kernel stable tree

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

dm: don't attempt to queue IO under RCU protection - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/699775e9338adcd4eaedea000d32c60250c3114d
Web page

dm: don't attempt to queue IO under RCU protection - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d7b2abd87d1fcdb47811f90090a363e7ca15cb14

Vendor Advisories for CVE-2023-53860(2)

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-427.13.1.el9_42024-04-30redhat
linuxKernel @ 6.1.55 (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 ... 6.1.55-1~bpo11+1 (10 versions)
  • every version up to 6.1.55-1: fixed in 6.1.55-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.5.6-1: fixed in 6.5.6-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.5.6-1: fixed in 6.5.6-1
—

Data Freshness Timeline

(refreshed 10× in last 7d / 43× 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 94 of 241 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. 6 repeat rows among the latest 100 are merged into the row they repeat. The 147 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2023-53860?
CVE-2023-53860 is a high-severity vulnerability; its CVE record was published on December 9, 2025. In the Linux kernel, the following vulnerability has been resolved: dm: don't attempt to queue IO under RCU protection dm looks up the table for IO based on the request type, with an assumption that if the request is marked REQ_NOWAIT, it's fine to attempt to submit that IO while under RCU read…
When was the CVE record for CVE-2023-53860 published?
The CVE record for CVE-2023-53860 was published on December 9, 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2023-53860 actively exploited?
CVE-2023-53860 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53860?
CVE-2023-53860 has a CVSS base score of 7.8 (the CNA's own assessment, by linux; NVD's own analysis pending).
How do I remediate CVE-2023-53860?
A fix for CVE-2023-53860 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-53860 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-53860

Explore →

Is Your Infrastructure Affected by CVE-2023-53860?

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

Book a Demo →Browse All CVEs