dbcve.org
Linux KernelOperating system · Linux

CVE-2024-23307

HIGH · 7.8 CVSS v3.1 Published 2024-01-25
Fix available
A fix is available. Upgrade to 6.1.84 / 6.6.24 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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
Integer Overflow or Wraparound vulnerability in Linux Linux kernel kernel on Linux, x86, ARM (md, raid, raid5 modules) allows Forced Integer Overflow.

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 · moderate confidence

Integer overflow vulnerability in the Linux kernel's MD (multi-device) software RAID subsystem (md, raid, raid5 modules) on x86 and ARM architectures. The 'forced integer overflow' suggests attacker-controlled integer manipulation in arithmetic operations within the RAID metadata or data processing path, potentially leading to memory corruption or incorrect buffer allocations.

MitigationApply the upstream Linux kernel security patch for CVE-2024-23307; until patched, monitor for suspicious RAID operations and restrict untrusted users from configuring RAID devices.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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.1, < 6.1.84>= 6.2, < 6.6.24>= 6.7, < 6.7.12>= 6.8, < 6.8.3

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
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify kernel version
    Run 'uname -r' or check /proc/version to get the running kernel version
    Affected if The kernel version falls within any of these ranges: >= 4.1 and < 6.1.84, >= 6.2 and < 6.6.24, >= 6.7 and < 6.7.12, or >= 6.8 and < 6.8.3
  2. Verify MD subsystem is in use
    Check /proc/mdstat for any active RAID arrays, or run 'lsmod | grep -E "^md|^raid"' to see if md, raid1, raid5, raid6, or raid10 modules are loaded
    Affected if The system actively uses software RAID (md devices are assembled or the md/raid modules are loaded)
  3. Confirm architecture
    Run 'uname -m' to identify the system architecture
    Affected if The system runs on x86 (i386, i686, x86_64) or ARM (armv7l, aarch64) architectures, as the vulnerability is specific to these
  4. Check for untrusted RAID users
    Review /etc/mdadm.conf or active RAID configurations and user permissions using 'mdadm --detail /dev/md*' for any arrays
    Affected if Untrusted or non-privileged users have access to configure or manipulate RAID devices, which would be the attack vector

The system is affected if the running kernel version is in the affected range AND the MD software RAID subsystem is actively used on an x86 or ARM architecture.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 6.1.84 / 6.6.24 / 6.7.12 or later
Fixed in 6.1.846.6.246.7.12
Interim mitigation

Apply the upstream Linux kernel security patch for CVE-2024-23307; until patched, monitor for suspicious RAID operations and restrict untrusted users from configuring RAID devices.

Recommended fix High confidence

Upgrade to kernel 6.1.84+, 6.6.24+, 6.7.12+, or 6.8.3+ depending on which branch you are on

  1. 1. Identify the currently running Linux kernel version using 'uname -r'
  2. 2. Based on the current version, determine the minimum fixed release needed: if running 6.1.x upgrade to 6.1.84+, if running 6.2.x-6.5.x upgrade to 6.6.24+, if running 6.7.x upgrade to 6.7.12+, if running 6.8.x upgrade to 6.8.3+
  3. 3. Update package repositories and install the new kernel version using the distribution's package manager (e.g., apt-get update && apt-get install linux-image-<version> for Debian/Ubuntu, or yum/dnf for RHEL-based systems)
  4. 4. Reboot the system to load the new kernel
  5. 5. Verify the system is running the patched kernel using 'uname -r'
Caveat Kernel upgrades may require rebuild of third-party kernel modules; ensure compatibility with system-critical modules before reboot

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

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23307 — 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-23307 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