# btrfs: don't drop extent_map for free space inode on write error

CVE record · `CVE-2024-26726`

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

Published by the CVE Program (CNA: Linux) at 3 Apr 2024, 14:55 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: `77cef2ec5484564eca6bd12a2b4a1e88fd766fbc to before 143842584c1237ebc248b2547c29d16bbe400a92` (git)
  - affected: `77cef2ec5484564eca6bd12a2b4a1e88fd766fbc to before 02f2b95b00bf57d20320ee168b30fb7f3db8e555` (git)
  - affected: `77cef2ec5484564eca6bd12a2b4a1e88fd766fbc to before 7bddf18f474f166c19f91b2baf67bf7c5eda03f7` (git)
  - affected: `77cef2ec5484564eca6bd12a2b4a1e88fd766fbc to before a4b7741c8302e28073bfc6dd1c2e73598e5e535e` (git)
  - affected: `77cef2ec5484564eca6bd12a2b4a1e88fd766fbc to before 5571e41ec6e56e35f34ae9f5b3a335ef510e0ade` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `3.12`
  - unaffected: `before 3.12` (semver)
  - unaffected: `5.15.187 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.79 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.18 to 6.6.*, inclusive` (semver)
  - unaffected: `6.7.6 to 6.7.*, inclusive` (semver)
  - unaffected: `6.8 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## 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.0026, the 17th 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 3 Apr 2024. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/143842584c1237ebc248b2547c29d16bbe400a92>
- <https://git.kernel.org/stable/c/02f2b95b00bf57d20320ee168b30fb7f3db8e555>
- <https://git.kernel.org/stable/c/7bddf18f474f166c19f91b2baf67bf7c5eda03f7>
- <https://git.kernel.org/stable/c/a4b7741c8302e28073bfc6dd1c2e73598e5e535e>
- <https://git.kernel.org/stable/c/5571e41ec6e56e35f34ae9f5b3a335ef510e0ade>

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-26726>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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