VulnerabilityPublished 1 May 2024Updated 30 Oct 2026

CVE-2024-27080: Linux kernel · btrfs: fix race when detecting delalloc ranges during fiemap

Affects Linux kernelSource GCVE Database

Compare

Not known to be exploited.

Data as of 30 Oct 2026, 16:33 UTC

Severity

High

Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation evidence

Disclosed: evidence found.
CVE published 1 May 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Linux Linux	Affected =6.6.24 =6.1.191 =6.7.12	Fixed in–

AI-suggested

A fix for this race condition has been implemented in the Linux kernel. Users should update to a Linux kernel version that includes the fix, such as versions 6.6.24, 6.1.191, or 6.7.12. No additional mitigation is required once the kernel is updated. Users of coreutils should also ensure they use version 9.0 or later to avoid relying on the vulnerable fiemap behavior.

Description

CVE-2024-27080 is a race condition vulnerability in the Linux kernel's btrfs filesystem related to detecting delayed allocation (delalloc) ranges during the fiemap operation. The issue arises because fiemap no longer locks the entire target extent range, which can cause it to miss delalloc ranges that are currently holes, misleading user space applications about the presence of data. This can lead to data loss in scenarios such as when the cp utility uses fiemap to preserve sparse files, potentially resulting in missing data in the destination file. The vulnerability was introduced by a recent change to avoid deadlocks but was fixed by restoring correct detection of delalloc ranges.

Impact

The impact of this vulnerability is potential data loss when user space applications rely on fiemap to detect file holes and data extents. For example, the cp utility before version 9.0 uses fiemap to copy only data regions and preserve holes in sparse files. If fiemap misses delalloc ranges due to this race, cp may omit copying some data, resulting in incomplete destination files. This is a correctness and data integrity issue rather than a security breach or privilege escalation. There is no indication of active exploitation in the wild.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 16:33 UTC

Technical details

References

Community reviews

Related threats