CVE-2023-53022

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2023-59698 (ENISA EUVD) · GHSA-9933-f4m5-7v96 (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

net: enetc: avoid deadlock in enetc_tx_onestep_tstamp()

This lockdep splat says it better than I could:

================================ WARNING: inconsistent lock state 6.2.0-rc2-07010-ga9b9500ffaac-dirty #967 Not tainted -------------------------------- inconsistent {IN-SOFTIRQ-W} -> {SOFTIRQ-ON-W} usage. kworker/1:3/179 [HC0[0]:SC0[0]:HE1:SE1] takes: ffff3ec4036ce098 (_xmit_ETHER#2){+.?.}-{3:3}, at: netif_freeze_queues+0x5c/0xc0 {IN-SOFTIRQ-W} state was registered at: _raw_spin_lock+0x5c/0xc0 sch_direct_xmit+0x148/0x37c __dev_queue_xmit+0x528/0x111c ip6_finish_output2+0x5ec/0xb7c ip6_finish_output+0x240/0x3f0 ip6_output+0x78/0x360 ndisc_send_skb+0x33c/0x85c ndisc_send_rs+0x54/0x12c addrconf_rs_timer+0x154/0x260 call_timer_fn+0xb8/0x3a0 __run_timers.part.0+0x214/0x26c run_timer_softirq+0x3c/0x74 __do_softirq+0x14c/0x5d8 ____do_softirq+0x10/0x20 call_on_irq_stack+0x2c/0x5c do_softirq_own_stack+0x1c/0x30 __irq_exit_rcu+0x168/0x1a0 irq_exit_rcu+0x10/0x40 el1_interrupt+0x38/0x64 irq event stamp: 7825 hardirqs last enabled at (7825): [] exit_to_kernel_mode+0x34/0x130 hardirqs last disabled at (7823): [] __do_softirq+0x550/0x5d8 softirqs last enabled at (7824): [] __do_softirq+0x46c/0x5d8 softirqs last disabled at (7811): [] ____do_softirq+0x10/0x20

other info that might help us debug this: Possible unsafe locking scenario:

CPU0 ---- lock(_xmit_ETHER#2); lock(_xmit_ETHER#2);

* DEADLOCK *

3 locks held by kworker/1:3/179: #0: ffff3ec400004748 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x1f4/0x6c0 #1: ffff80000a0bbdc8 ((work_completion)(&priv->tx_onestep_tstamp)){+.+.}-{0:0}, at: process_one_work+0x1f4/0x6c0 #2: ffff3ec4036cd438 (&dev->tx_global_lock){+.+.}-{3:3}, at: netif_tx_lock+0x1c/0x34

Workqueue: events enetc_tx_onestep_tstamp Call trace: print_usage_bug.part.0+0x208/0x22c mark_lock+0x7f0/0x8b0 __lock_acquire+0x7c4/0x1ce0 lock_acquire.part.0+0xe0/0x220 lock_acquire+0x68/0x84 _raw_spin_lock+0x5c/0xc0 netif_freeze_queues+0x5c/0xc0 netif_tx_lock+0x24/0x34 enetc_tx_onestep_tstamp+0x20/0x100 process_one_work+0x28c/0x6c0 worker_thread+0x74/0x450 kthread+0x118/0x11c

but I'll say it anyway: the enetc_tx_onestep_tstamp() work item runs in process context, therefore with softirqs enabled (i.o.w., it can be interrupted by a softirq). If we hold the netif_tx_lock() when there is an interrupt, and the NET_TX softirq then gets scheduled, this will take the netif_tx_lock() a second time and deadlock the kernel.

To solve this, use netif_tx_lock_bh(), which blocks softirqs from running.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.1%
EPSS %ILE
4th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

March 27, 2025

Last Modified

October 1, 2025

References (3)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 5.15.91 (fixes >=5.13.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
linux—
  • every version up to 6.1.11-1: fixed in 6.1.11-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.11-1: fixed in 6.1.11-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.11-1: fixed in 6.1.11-1
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-53022?
CVE-2023-53022 is a medium-severity vulnerability; its CVE record was published on March 27, 2025. In the Linux kernel, the following vulnerability has been resolved: net: enetc: avoid deadlock in enetc_tx_onestep_tstamp() This lockdep splat says it better than I could: ================================ WARNING: inconsistent lock state 6.2.0-rc2-07010-ga9b9500ffaac-dirty #967 Not tainted…
When was the CVE record for CVE-2023-53022 published?
The CVE record for CVE-2023-53022 was published on March 27, 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 1, 2025; the record at its source may have been updated since.
Is CVE-2023-53022 actively exploited?
CVE-2023-53022 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53022?
CVE-2023-53022 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-53022?
A fix for CVE-2023-53022 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-53022

Explore →

Is Your Infrastructure Affected by CVE-2023-53022?

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

Book a Demo →Browse All CVEs