CVE-2023-53623

MEDIUMNVD 4.74.7
EchelonGraph scoreMEDIUM confidence

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

Score 4.7 from GitHub Security Advisory published 2025-10-07. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
4.7EG
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: 4.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

mm/swap: fix swap_info_struct race between swapoff and get_swap_pages()

The si->lock must be held when deleting the si from the available list. Otherwise, another thread can re-add the si to the available list, which can lead to memory corruption. The only place we have found where this happens is in the swapoff path. This case can be described as below:

core 0 core 1 swapoff

del_from_avail_list(si) waiting

try lock si->lock acquire swap_avail_lock and re-add si into swap_avail_head

acquire si->lock but missing si already being added again, and continuing to clear SWP_WRITEOK, etc.

It can be easily found that a massive warning messages can be triggered inside get_swap_pages() by some special cases, for example, we call madvise(MADV_PAGEOUT) on blocks of touched memory concurrently, meanwhile, run much swapon-swapoff operations (e.g. stress-ng-swap).

However, in the worst case, panic can be caused by the above scene. In swapoff(), the memory used by si could be kept in swap_info[] after turning off a swap. This means memory corruption will not be caused immediately until allocated and reset for a new swap in the swapon path. A panic message caused: (with CONFIG_PLIST_DEBUG enabled)

------------[ cut here ]------------ top: 00000000e58a3003, n: 0000000013e75cda, p: 000000008cd4451a prev: 0000000035b1e58a, n: 000000008cd4451a, p: 000000002150ee8d next: 000000008cd4451a, n: 000000008cd4451a, p: 000000008cd4451a WARNING: CPU: 21 PID: 1843 at lib/plist.c:60 plist_check_prev_next_node+0x50/0x70 Modules linked in: rfkill(E) crct10dif_ce(E)... CPU: 21 PID: 1843 Comm: stress-ng Kdump: ... 5.10.134+ Hardware name: Alibaba Cloud ECS, BIOS 0.0.0 02/06/2015 pstate: 60400005 (nZCv daif +PAN -UAO -TCO BTYPE=--) pc : plist_check_prev_next_node+0x50/0x70 lr : plist_check_prev_next_node+0x50/0x70 sp : ffff0018009d3c30 x29: ffff0018009d3c40 x28: ffff800011b32a98 x27: 0000000000000000 x26: ffff001803908000 x25: ffff8000128ea088 x24: ffff800011b32a48 x23: 0000000000000028 x22: ffff001800875c00 x21: ffff800010f9e520 x20: ffff001800875c00 x19: ffff001800fdc6e0 x18: 0000000000000030 x17: 0000000000000000 x16: 0000000000000000 x15: 0736076307640766 x14: 0730073007380731 x13: 0736076307640766 x12: 0730073007380731 x11: 000000000004058d x10: 0000000085a85b76 x9 : ffff8000101436e4 x8 : ffff800011c8ce08 x7 : 0000000000000000 x6 : 0000000000000001 x5 : ffff0017df9ed338 x4 : 0000000000000001 x3 : ffff8017ce62a000 x2 : ffff0017df9ed340 x1 : 0000000000000000 x0 : 0000000000000000 Call trace: plist_check_prev_next_node+0x50/0x70 plist_check_head+0x80/0xf0 plist_add+0x28/0x140 add_to_avail_list+0x9c/0xf0 _enable_swap_info+0x78/0xb4 __do_sys_swapon+0x918/0xa10 __arm64_sys_swapon+0x20/0x30 el0_svc_common+0x8c/0x220 do_el0_svc+0x2c/0x90 el0_svc+0x1c/0x30 el0_sync_handler+0xa8/0xb0 el0_sync+0x148/0x180 irq event stamp: 2082270

Now, si->lock locked before calling 'del_from_avail_list()' to make sure other thread see the si had been deleted and SWP_WRITEOK cleared together, will not reinsert again.

This problem exists in versions after stable 5.10.y.

CVSS v3
4.7
EG Score
4.7MEDIUMmedium confidence
EG Risk
21
EG Risk 21/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)
Severity47% × 45%
Impact severity (EG Severity): CVSS 4.7 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 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.1%
EPSS %ILE
2nd
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 (4.7): severity, escalated by confirmed exploitation. This CVE's 4.7 is its impact severity (EG Severity), not escalated.

EG Severity
4.7 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-17). 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: 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.

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

October 7, 2025

Last Modified

February 5, 2026

References (8)

Vendor Advisories for CVE-2023-53623(2)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:4.18.0-553.el8_102024-05-22redhat
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
linuxKernel @ 4.14.313 (fixes >=4.14.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.25-1: fixed in 6.1.25-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.25-1: fixed in 6.1.25-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.25-1: fixed in 6.1.25-1
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-53623?
CVE-2023-53623 is a medium-severity vulnerability; its CVE record was published on October 7, 2025. In the Linux kernel, the following vulnerability has been resolved: mm/swap: fix swapinfostruct race between swapoff and getswappages() The si->lock must be held when deleting the si from the available list. Otherwise, another thread can re-add the si to the available list, which can lead to memory…
When was the CVE record for CVE-2023-53623 published?
The CVE record for CVE-2023-53623 was published on October 7, 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 February 5, 2026; the record at its source may have been updated since.
Is CVE-2023-53623 actively exploited?
CVE-2023-53623 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53623?
CVE-2023-53623 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2023-53623?
A fix for CVE-2023-53623 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-53623 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-53623

Explore →

Is Your Infrastructure Affected by CVE-2023-53623?

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

Book a Demo →Browse All CVEs