CVE-2024-26764

LOWNVD 3.33.3
EchelonGraph scoreMEDIUM confidence

Score 3.3 from GitHub Security Advisory (severity: LOW) published 2024-04-03. NVD baseline CVSS 3.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
3.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.3Exploit: None knownExposed: 0

A fix is available — apply it.

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

fs/aio: Restrict kiocb_set_cancel_fn() to I/O submitted via libaio

If kiocb_set_cancel_fn() is called for I/O submitted via io_uring, the following kernel warning appears:

WARNING: CPU: 3 PID: 368 at fs/aio.c:598 kiocb_set_cancel_fn+0x9c/0xa8 Call trace: kiocb_set_cancel_fn+0x9c/0xa8 ffs_epfile_read_iter+0x144/0x1d0 io_read+0x19c/0x498 io_issue_sqe+0x118/0x27c io_submit_sqes+0x25c/0x5fc __arm64_sys_io_uring_enter+0x104/0xab0 invoke_syscall+0x58/0x11c el0_svc_common+0xb4/0xf4 do_el0_svc+0x2c/0xb0 el0_svc+0x2c/0xa4 el0t_64_sync_handler+0x68/0xb4 el0t_64_sync+0x1a4/0x1a8

Fix this by setting the IOCB_AIO_RW flag for read and write I/O that is submitted by libaio.

CVSS v3
3.3
EG Score
3.3(medium)
EG Risk
15(Track)
EG Risk 15/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
Severity33% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

April 3, 2024

Last Modified

March 18, 2025

References (18)

Patch Availability(12)

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.

All Vendor Advisories

(11)

Data Freshness Timeline

(refreshed 8× in last 7d / 42× 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 128 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2024-26764?
CVE-2024-26764 is a low vulnerability published on April 3, 2024. In the Linux kernel, the following vulnerability has been resolved: fs/aio: Restrict kiocbsetcancel_fn() to I/O submitted via libaio If kiocbsetcancelfn() is called for I/O submitted via iouring, the following kernel warning appears: WARNING: CPU: 3 PID: 368 at fs/aio.c:598…
When was CVE-2024-26764 disclosed?
CVE-2024-26764 was first published in the National Vulnerability Database on April 3, 2024, with the most recent update on March 18, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-26764 actively exploited?
CVE-2024-26764 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 83.9% of all scored CVEs.
What is the CVSS score of CVE-2024-26764?
CVE-2024-26764 has a CVSS v3 base score of 3.3 (NVD).
How do I remediate CVE-2024-26764?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-26764, 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-2024-26764

Explore →

Is Your Infrastructure Affected by CVE-2024-26764?

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