CVE-2023-53709

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week

Also known asEUVD-2023-60019 (ENISA EUVD) · GHSA-2v5h-c6vh-95p9 (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ring-buffer: Handle race between rb_move_tail and rb_check_pages

It seems a data race between ring_buffer writing and integrity check. That is, RB_FLAG of head_page is been updating, while at same time RB_FLAG was cleared when doing integrity check rb_check_pages():

rb_check_pages() rb_handle_head_page(): -------- -------- rb_head_page_deactivate() rb_head_page_set_normal() rb_head_page_activate()

We do intergrity test of the list to check if the list is corrupted and it is still worth doing it. So, let's refactor rb_check_pages() such that we no longer clear and set flag during the list sanity checking.

[1] and [2] are the test to reproduce and the crash report respectively.

1: `` read_trace.sh while true; do # the "trace" file is closed after read head -1 /sys/kernel/tracing/trace > /dev/null done

repro.sh sysctl -w kernel.panic_on_warn=1 # function tracer will writing enough data into ring_buffer echo function > /sys/kernel/tracing/current_tracer ./read_trace.sh & ./read_trace.sh & ./read_trace.sh & ./read_trace.sh & ./read_trace.sh & ./read_trace.sh & ./read_trace.sh & ./read_trace.sh & ``

2: ------------[ cut here ]------------ WARNING: CPU: 9 PID: 62 at kernel/trace/ring_buffer.c:2653 rb_move_tail+0x450/0x470 Modules linked in: CPU: 9 PID: 62 Comm: ksoftirqd/9 Tainted: G W 6.2.0-rc6+ Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014 RIP: 0010:rb_move_tail+0x450/0x470 Code: ff ff 4c 89 c8 f0 4d 0f b1 02 48 89 c2 48 83 e2 fc 49 39 d0 75 24 83 e0 03 83 f8 02 0f 84 e1 fb ff ff 48 8b 57 10 f0 ff 42 08 <0f> 0b 83 f8 02 0f 84 ce fb ff ff e9 db RSP: 0018:ffffb5564089bd00 EFLAGS: 00000203 RAX: 0000000000000000 RBX: ffff9db385a2bf81 RCX: ffffb5564089bd18 RDX: ffff9db281110100 RSI: 0000000000000fe4 RDI: ffff9db380145400 RBP: ffff9db385a2bf80 R08: ffff9db385a2bfc0 R09: ffff9db385a2bfc2 R10: ffff9db385a6c000 R11: ffff9db385a2bf80 R12: 0000000000000000 R13: 00000000000003e8 R14: ffff9db281110100 R15: ffffffffbb006108 FS: 0000000000000000(0000) GS:ffff9db3bdcc0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005602323024c8 CR3: 0000000022e0c000 CR4: 00000000000006e0 Call Trace: ring_buffer_lock_reserve+0x136/0x360 ? __do_softirq+0x287/0x2df ? __pfx_rcu_softirq_qs+0x10/0x10 trace_function+0x21/0x110 ? __pfx_rcu_softirq_qs+0x10/0x10 ? __do_softirq+0x287/0x2df function_trace_call+0xf6/0x120 0xffffffffc038f097 ? rcu_softirq_qs+0x5/0x140 rcu_softirq_qs+0x5/0x140 __do_softirq+0x287/0x2df run_ksoftirqd+0x2a/0x30 smpboot_thread_fn+0x188/0x220 ? __pfx_smpboot_thread_fn+0x10/0x10 kthread+0xe7/0x110 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x2c/0x50 ---[ end trace 0000000000000000 ]---

[ crash report and test reproducer credit goes to Zheng Yejian]

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
9th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). 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
No SSVC decision: EchelonGraph has not assessed this CVECISA 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 BOD 26-04 block below.

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

October 22, 2025

Last Modified

October 28, 2026

Vendor Advisories for CVE-2023-53709(1)

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 @ 5.10.173 (fixes >=5.7.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.20-1: fixed in 6.1.20-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.20-1: fixed in 6.1.20-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.20-1: fixed in 6.1.20-1
—

Data Freshness Timeline

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

Frequently asked(4)

What is CVE-2023-53709?
CVE-2023-53709 is a vulnerability whose severity is not yet rated; its CVE record was published on October 22, 2025. In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Handle race between rb_move_tail and rb_check_pages It seems a data race between ring_buffer writing and integrity check. That is, RB_FLAG of head_page is been updating, while at same time RB_FLAG was cleared when…
When was the CVE record for CVE-2023-53709 published?
The CVE record for CVE-2023-53709 was published on October 22, 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 28, 2026; the record at its source may have been updated since.
Is CVE-2023-53709 actively exploited?
CVE-2023-53709 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
How do I remediate CVE-2023-53709?
A fix for CVE-2023-53709 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-53709 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-53709

Explore →

Is Your Infrastructure Affected by CVE-2023-53709?

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