# btrfs: fix race when detecting delalloc ranges during fiemap

CVE record · `CVE-2024-27080`

- **Identifiers:** `CVE-2024-27080`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 1 May 2024
- **Updated:** 30 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 1 May 2024, 13:05 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `ded566b4637f1b6b4c9ba74e7d0b8493e93f19cf to before 49d640d2946c35a17b051d54171a032dd95b0f50` (git)
  - affected: `b0ad381fa7690244802aed119b478b4bdafc31dd to before ced63fffd63072c0ca55d5a451010d71bf08c0b3` (git)
  - affected: `b0ad381fa7690244802aed119b478b4bdafc31dd to before 978b63f7464abcfd364a6c95f734282c50f3decf` (git)
  - affected: `06d3879bb51be205a04b3da752cfd121a3367fb1` (git)
  - affected: `89bca7fe6382d61e88c67a0b0e7bce315986fb8b` (git)
  - affected: `6.6.24 to before 6.6.26` (semver)
  - affected: `6.1.191 to before 6.2` (semver)
  - affected: `6.7.12 to before 6.8` (semver)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.8`
  - unaffected: `before 6.8` (semver)
  - unaffected: `6.6.26 to 6.6.*, inclusive` (semver)
  - unaffected: `6.8.2 to 6.8.*, inclusive` (semver)
  - unaffected: `6.9 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel btrfs code is affected from 6.6.24 before 6.6.26, and in 6.8 before 6.8.2. A race in fiemap can cause delalloc data in a file hole to go unreported, so tools such as cp may skip that data and lose it. The source does not say what access an attacker needs. Upgrade to 6.6.26, 6.8.2, or 6.9 or later.

Written 13 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0019, the 8th percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 1 May 2024. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2024-27080](https://www.cve.org/CVERecord?id=CVE-2024-27080)
- [NVD: CVE-2024-27080](https://nvd.nist.gov/vuln/detail/CVE-2024-27080)

### References from the CNA

- <https://git.kernel.org/stable/c/49d640d2946c35a17b051d54171a032dd95b0f50>
- <https://git.kernel.org/stable/c/ced63fffd63072c0ca55d5a451010d71bf08c0b3>
- <https://git.kernel.org/stable/c/978b63f7464abcfd364a6c95f734282c50f3decf>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2024-27080>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2024-27080/>. Everything for agents: <https://agentprime.io/llms.txt>.
