dbcve.org
Linux KernelOperating system · Linux

CVE-2024-35815

MEDIUM · 5.5 CVSS v3.1 Published 2024-05-17
Fix available
A fix is available. Upgrade to 4.19.312 / 5.4.274 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: fs/aio: Check IOCB_AIO_RW before the struct aio_kiocb conversion The first kiocb_set_cancel_fn() argument may point at a struct kiocb that is not embedded inside struct aio_kiocb. With the current code, depending on the compiler, the req->ki_ctx read happens either before the IOCB_AIO_RW test or after that test. Move the req->ki_ctx read such that it is guaranteed that the IOCB_AIO_RW test happens first.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 4.19.308, < 4.19.312>= 5.4.270, < 5.4.274>= 5.10.211, < 5.10.215>= 5.15.150, < 5.15.154>= 6.1.80, < 6.1.84>= 6.6.19, < 6.6.24>= 6.7.7, < 6.7.12= 6.8
Debian LinuxOperating system
Affected:= 10.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.19.312 / 5.4.274 / 5.10.215 or later
Fixed in 4.19.3125.4.2745.10.215
Vendor patch git.kernel.org →
Recommended fix High confidence

Linux kernel 4.19.312+ / 5.4.274+ / 5.10.215+ / 5.15.154+ (depending on which branch is in use)

  1. Identify the current kernel version using `uname -r` or `cat /proc/version`
  2. Determine which kernel branch is in use (e.g., 4.19.x, 5.4.x, 5.10.x, or 5.15.x)
  3. Use the system's package manager to upgrade to a fixed kernel version: For Debian/Ubuntu: `apt-get update && apt-get install linux-image-<version>`; For RHEL/CentOS: `yum update kernel`; For other distros, use their standard kernel update mechanism
  4. Update bootloader configuration if necessary (e.g., update-grub for GRUB)
  5. Schedule a system reboot to load the new kernel
  6. After reboot, verify the kernel has been upgraded to a fixed version (>= 4.19.312, >= 5.4.274, >= 5.10.215, or >= 5.15.154) using `uname -r`
Caveat Kernel upgrades require system reboot and may require recompiling third-party kernel modules; ensure compatibility with installed kernel modules before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-35815 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-35815 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data