CVE-2024-38601

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 2024-06-19. 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.2%CVSS: 4.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ring-buffer: Fix a race between readers and resize checks

The reader code in rb_get_reader_page() swaps a new reader page into the ring buffer by doing cmpxchg on old->list.prev->next to point it to the new page. Following that, if the operation is successful, old->list.next->prev gets updated too. This means the underlying doubly-linked list is temporarily inconsistent, page->prev->next or page->next->prev might not be equal back to page for some page in the ring buffer.

The resize operation in ring_buffer_resize() can be invoked in parallel. It calls rb_check_pages() which can detect the described inconsistency and stop further tracing:

[ 190.271762] ------------[ cut here ]------------ [ 190.271771] WARNING: CPU: 1 PID: 6186 at kernel/trace/ring_buffer.c:1467 rb_check_pages.isra.0+0x6a/0xa0 [ 190.271789] Modules linked in: [...] [ 190.271991] Unloaded tainted modules: intel_uncore_frequency(E):1 skx_edac(E):1 [ 190.272002] CPU: 1 PID: 6186 Comm: cmd.sh Kdump: loaded Tainted: G E 6.9.0-rc6-default #5 158d3e1e6d0b091c34c3b96bfd99a1c58306d79f [ 190.272011] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552c-rebuilt.opensuse.org 04/01/2014 [ 190.272015] RIP: 0010:rb_check_pages.isra.0+0x6a/0xa0 [ 190.272023] Code: [...] [ 190.272028] RSP: 0018:ffff9c37463abb70 EFLAGS: 00010206 [ 190.272034] RAX: ffff8eba04b6cb80 RBX: 0000000000000007 RCX: ffff8eba01f13d80 [ 190.272038] RDX: ffff8eba01f130c0 RSI: ffff8eba04b6cd00 RDI: ffff8eba0004c700 [ 190.272042] RBP: ffff8eba0004c700 R08: 0000000000010002 R09: 0000000000000000 [ 190.272045] R10: 00000000ffff7f52 R11: ffff8eba7f600000 R12: ffff8eba0004c720 [ 190.272049] R13: ffff8eba00223a00 R14: 0000000000000008 R15: ffff8eba067a8000 [ 190.272053] FS: 00007f1bd64752c0(0000) GS:ffff8eba7f680000(0000) knlGS:0000000000000000 [ 190.272057] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 190.272061] CR2: 00007f1bd6662590 CR3: 000000010291e001 CR4: 0000000000370ef0 [ 190.272070] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 190.272073] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 190.272077] Call Trace: [ 190.272098] [ 190.272189] ring_buffer_resize+0x2ab/0x460 [ 190.272199] __tracing_resize_ring_buffer.part.0+0x23/0xa0 [ 190.272206] tracing_resize_ring_buffer+0x65/0x90 [ 190.272216] tracing_entries_write+0x74/0xc0 [ 190.272225] vfs_write+0xf5/0x420 [ 190.272248] ksys_write+0x67/0xe0 [ 190.272256] do_syscall_64+0x82/0x170 [ 190.272363] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 190.272373] RIP: 0033:0x7f1bd657d263 [ 190.272381] Code: [...] [ 190.272385] RSP: 002b:00007ffe72b643f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [ 190.272391] RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007f1bd657d263 [ 190.272395] RDX: 0000000000000002 RSI: 0000555a6eb538e0 RDI: 0000000000000001 [ 190.272398] RBP: 0000555a6eb538e0 R08: 000000000000000a R09: 0000000000000000 [ 190.272401] R10: 0000555a6eb55190 R11: 0000000000000246 R12: 00007f1bd6662500 [ 190.272404] R13: 0000000000000002 R14: 00007f1bd6667c00 R15: 0000000000000002 [ 190.272412] [ 190.272414] ---[ end trace 0000000000000000 ]---

Note that ring_buffer_resize() calls rb_check_pages() only if the parent trace_buffer has recording disabled. Recent commit d78ab792705c ("tracing: Stop current tracer when resizing buffer") causes that it is now always the case which makes it more likely to experience this issue.

The window to hit this race is nonetheless very small. To help reproducing it, one can add a delay loop in rb_get_reader_page():

ret = rb_head_page_replace(reader, cpu_buffer->reader_page); if (!ret) goto spin; for (unsigned i = 0; i < 1U << 26; i++) /* inserted delay loop */ __asm__ __volatile__ ("" : : : "memory"); rb_list_head(reader->list.next)->prev = &cpu_buffer->reader_page->list;

.. ---truncated---

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.2% × 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.2%
EPSS %ILE
6th
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.2% 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 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: 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.

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

June 19, 2024

Last Modified

November 4, 2025

Vendor Advisories for CVE-2024-38601(1)

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

Patch Availability(18)

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

(5 across 5 ecosystems)
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
linux4.19.118-1 ... 4.19.98-1~bpo9+1 (46 versions)
  • every version up to 4.19.316-1: fixed in 4.19.316-1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (41 versions)
  • every version up to 5.10.221-1: fixed in 5.10.221-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.94-1~bpo11+1 (23 versions)
  • every version up to 6.1.94-1: fixed in 6.1.94-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.12-1: fixed in 6.8.12-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.12-1: fixed in 6.8.12-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(16)

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2024-38601?
CVE-2024-38601 is a medium-severity vulnerability; its CVE record was published on June 19, 2024. In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Fix a race between readers and resize checks The reader code in rbgetreader_page() swaps a new reader page into the ring buffer by doing cmpxchg on old->list.prev->next to point it to the new page. Following that, if…
When was the CVE record for CVE-2024-38601 published?
The CVE record for CVE-2024-38601 was published on June 19, 2024. 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 November 4, 2025; the record at its source may have been updated since.
Is CVE-2024-38601 actively exploited?
CVE-2024-38601 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-38601?
CVE-2024-38601 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2024-38601?
A fix for CVE-2024-38601 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-38601 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-2024-38601

Explore →

Is Your Infrastructure Affected by CVE-2024-38601?

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