CVE-2024-35874: aio: Fix null ptr deref in aio_complete() wakeup
In the Linux kernel, the following vulnerability has been resolved:
aio: Fix null ptr deref in aio_complete() wakeup
list_del_init_careful() needs to be the last access to the wait queue
entry - it effectively unlocks access.
Previously, finish_wait() would see the empty list head and skip taking
the lock, and then we'd return - but the completion path would still
attempt to do the wakeup after the task_struct pointer had been
overwritten.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux asynchronous I/O completion handling can dereference an invalid pointer during a timing-sensitive wakeup race. The supplied CVSS score is 7.8 because a low-privileged local attacker could potentially affect confidentiality, integrity, and availability. The sources do not establish remote reachability or successful exploitation.
Executive priority
Treat as a high-priority kernel maintenance issue, especially on shared compute, development, hosting, or other systems permitting untrusted local activity. It is not evidenced as an internet-triggered emergency or actively exploited vulnerability. Patch through normal expedited kernel processes after confirming distribution applicability.
Technical view
The completion path accessed a wait-queue entry after list_del_init_careful() had effectively released protected access. Concurrent finish_wait() processing could return while aio_complete() still attempted a wakeup using an overwritten task_struct pointer, causing a null-pointer dereference. Kernel commits referenced by the CVE correct the ordering.
Likely exposure
Exposure is limited to systems running affected Linux kernel versions where a low-privileged local user or workload can reach asynchronous I/O functionality. The bundle identifies versions around Linux 6.8 through 6.9, but its version data is ambiguous; confirm exact affected and fixed releases with kernel or distribution advisories.
Exploitation context
The CVSS vector indicates local access, low complexity, low privileges, and no user interaction. The bundle marks this CVE as absent from KEV, and no supplied source reports active exploitation. The technical description establishes a crash-prone race but does not demonstrate privilege escalation or reliable compromise.
Researcher notes
The core issue is synchronization and access ordering around wait-queue removal and completion wakeup. The cited kernel commits are the strongest remediation evidence. The supplied record has no CWE and unclear version boundaries, so avoid inferring additional affected branches, exploitation primitives, or guaranteed confidentiality and integrity impact from the description alone.
Mitigation direction
Apply the corrected kernel supplied by the system vendor or Linux distribution.
Check vendor guidance for exact fixed versions because the supplied version ranges are ambiguous.
Prioritize multi-user systems and hosts running untrusted or low-trust local workloads.
Restrict unnecessary local access until affected kernels are updated.
Validation and detection
Record each host's running kernel version and distribution package release.
Compare installed packages against the distribution's CVE advisory or fixed-kernel guidance.
Confirm the replacement kernel is running after patching and rebooting.
Review kernel logs for asynchronous-I/O-related null-pointer faults or unexpected crashes.
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-35874 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.