LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26764: fs/aio: Restrict kiocb_set_cancel_fn() to I/O submitted via libaio

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-26764 is a Linux kernel flaw involving asynchronous I/O cancellation handling. The public record describes a kernel warning when an io_uring path reaches logic intended for libaio. Business impact is not fully stated in the sources, so urgency should be tied to kernel update hygiene rather than assumed compromise.

Executive priority

Treat this as a routine kernel maintenance item unless your environment has additional evidence of impact. There is no sourced active exploitation or severity score, but kernel flaws should still be patched through standard vulnerability windows.

Technical view

The fix restricts kiocb_set_cancel_fn() behavior to I/O submitted through libaio by setting IOCB_AIO_RW for libaio read and write I/O. The reported warning occurs in fs/aio.c when I/O submitted via io_uring reaches this code path. Sources provide stable kernel commits but no CVSS, CWE, or detailed impact statement.

Likely exposure

Exposure is likely limited to systems running affected Linux kernel versions listed in the CVE record, including several stable series before the referenced fixes. Debian LTS advisories are cited, so Debian-managed kernels should be checked against those updates.

Exploitation context

The CVE is not listed as CISA KEV in the source bundle, and no cited source states active exploitation. The public description shows a reproducible kernel warning path, but does not establish exploitability, privilege requirements, or practical attacker impact.

Researcher notes

The evidence supports a narrow fs/aio and io_uring interaction fixed in upstream stable commits. The source bundle does not provide exploitability analysis, CVSS, CWE mapping, or a workaround beyond applying kernel fixes and distribution updates.

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable fixes.
  • Use distribution advisories, including Debian LTS notices, to identify fixed packages.
  • Reboot systems after kernel updates to load the corrected kernel.
  • If no package is available, monitor vendor guidance for supported backports.

Validation and detection

  • Inventory running kernel versions across Linux hosts.
  • Compare deployed kernels with vendor fixed versions or referenced stable commits.
  • Review kernel logs for the cited kiocb_set_cancel_fn warning pattern.
  • Confirm updated hosts booted into the patched kernel after maintenance.
Prepared
Confidence
medium
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-26764 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
11Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux04b2fa9f8f36ec6fb6fd1c9dc9df6fff0cd27323, 04b2fa9f8f36ec6fb6fd1c9dc9df6fff0cd27323, 04b2fa9f8f36ec6fb6fd1c9dc9df6fff0cd27323, 04b2fa9f8f36ec6fb6fd1c9dc9df6fff0cd27323, 04b2fa9f8f36ec6fb6fd1c9dc9df6fff0cd27323, 04b2fa9f8f36ec6fb6fd1c9dc9df6fff0cd27323, 04b2fa9f8f36ec6fb6fd1c9dc9df6fff0cd27323, 04b2fa9f8f36ec6fb6fd1c9dc9df6fff0cd27323unaffected
LinuxLinux4.1, 0, 4.19.308, 5.4.270, 5.10.211, 5.15.150, 6.1.80, 6.6.19, 6.7.7, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.