CVE-2023-53067

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
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:

LoongArch: Only call get_timer_irq() once in constant_clockevent_init()

Under CONFIG_DEBUG_ATOMIC_SLEEP=y and CONFIG_DEBUG_PREEMPT=y, we can see the following messages on LoongArch, this is because using might_sleep() in preemption disable context.

[ 0.001127] smp: Bringing up secondary CPUs ... [ 0.001222] Booting CPU#1... [ 0.001244] 64-bit Loongson Processor probed (LA464 Core) [ 0.001247] CPU1 revision is: 0014c012 (Loongson-64bit) [ 0.001250] FPU1 revision is: 00000000 [ 0.001252] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:283 [ 0.001255] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 0, name: swapper/1 [ 0.001257] preempt_count: 1, expected: 0 [ 0.001258] RCU nest depth: 0, expected: 0 [ 0.001259] Preemption disabled at: [ 0.001261] [<9000000000223800>] arch_dup_task_struct+0x20/0x110 [ 0.001272] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 6.2.0-rc7+ #43 [ 0.001275] Hardware name: Loongson Loongson-3A5000-7A1000-1w-A2101/Loongson-LS3A5000-7A1000-1w-A2101, BIOS vUDK2018-LoongArch-V4.0.05132-beta10 12/13/202 [ 0.001277] Stack : 0072617764726148 0000000000000000 9000000000222f1c 90000001001e0000 [ 0.001286] 90000001001e3be0 90000001001e3be8 0000000000000000 0000000000000000 [ 0.001292] 90000001001e3be8 0000000000000040 90000001001e3cb8 90000001001e3a50 [ 0.001297] 9000000001642000 90000001001e3be8 be694d10ce4139dd 9000000100174500 [ 0.001303] 0000000000000001 0000000000000001 00000000ffffe0a2 0000000000000020 [ 0.001309] 000000000000002f 9000000001354116 00000000056b0000 ffffffffffffffff [ 0.001314] 0000000000000000 0000000000000000 90000000014f6e90 9000000001642000 [ 0.001320] 900000000022b69c 0000000000000001 0000000000000000 9000000001736a90 [ 0.001325] 9000000100038000 0000000000000000 9000000000222f34 0000000000000000 [ 0.001331] 00000000000000b0 0000000000000004 0000000000000000 0000000000070000 [ 0.001337] ... [ 0.001339] Call Trace: [ 0.001342] [<9000000000222f34>] show_stack+0x5c/0x180 [ 0.001346] [<90000000010bdd80>] dump_stack_lvl+0x60/0x88 [ 0.001352] [<9000000000266418>] __might_resched+0x180/0x1cc [ 0.001356] [<90000000010c742c>] mutex_lock+0x20/0x64 [ 0.001359] [<90000000002a8ccc>] irq_find_matching_fwspec+0x48/0x124 [ 0.001364] [<90000000002259c4>] constant_clockevent_init+0x68/0x204 [ 0.001368] [<900000000022acf4>] start_secondary+0x40/0xa8 [ 0.001371] [<90000000010c0124>] smpboot_entry+0x60/0x64

Here are the complete call chains:

smpboot_entry() start_secondary() constant_clockevent_init() get_timer_irq() irq_find_matching_fwnode() irq_find_matching_fwspec() mutex_lock() might_sleep() __might_sleep() __might_resched()

In order to avoid the above issue, we should break the call chains, using timer_irq_installed variable as check condition to only call get_timer_irq() once in constant_clockevent_init() is a simple and proper way.

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
8%
KEV
Not listed

Published

May 2, 2025

Last Modified

November 12, 2025

References (3)

Patch Availability(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 37× 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.

Showing the most recent 100 of 104 total refreshes for this CVE.

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

Related CVEs(same product)

Frequently asked(5)

What is CVE-2023-53067?
CVE-2023-53067 is a medium vulnerability published on May 2, 2025. In the Linux kernel, the following vulnerability has been resolved: LoongArch: Only call gettimerirq() once in constantclockeventinit() Under CONFIGDEBUGATOMICSLEEP=y and CONFIGDEBUG_PREEMPT=y, we can see the following messages on LoongArch, this is because using might_sleep() in preemption disable…
When was CVE-2023-53067 disclosed?
CVE-2023-53067 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-53067 actively exploited?
CVE-2023-53067 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 91.6% of all scored CVEs.
What is the CVSS score of CVE-2023-53067?
CVE-2023-53067 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-53067?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-53067, 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-53067

Explore →

Is Your Infrastructure Affected by CVE-2023-53067?

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

Start Free Scan →Browse All CVEs