# btrfs: fix race between direct IO write and fsync when using same fd

CVE record · `CVE-2024-46734`

- **Identifiers:** `CVE-2024-46734`
- **State:** Confirmed
- **Severity:** CVSS 7.8 High
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 18 Sept 2024
- **Updated:** 5 Aug 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 18 Sept 2024, 07:11 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: `4e17707035a65f6e5b2a4d987a308cf8ed8c5ad1 to before d116a0b0e02f395cedfb8c725bd67480aa7c428c` (git)
  - affected: `6cae8d04d8b3d1ecfadcaa989e673f6f73349ed5 to before cd3087582e4fa36e89be4e6f859e75a4400292b4` (git)
  - affected: `0a108bde616a7017653385b5a12111015051a294 to before 7b5595f33c3c273613b590892a578d78186bb400` (git)
  - affected: `3831170f740685fddc8f6aa57a83ad0fef4711bf to before 01681aa609b5f110502f56c4e3b2938efcf4a5bc` (git)
  - affected: `939b656bc8ab203fdbde26ccac22bcb7f0985be5 to before cd9253c23aedd61eb5ff11f37a36247cd46faf86` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.15.165 to before 5.15.167` (semver)
  - affected: `6.1.105 to before 6.1.110` (semver)
  - affected: `6.6.46 to before 6.6.51` (semver)
  - affected: `6.10.5 to before 6.10.10` (semver)
  - Other versions: unaffected

## 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

- 7.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (Linux)

- **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 18 Sept 2024. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/d116a0b0e02f395cedfb8c725bd67480aa7c428c>
- <https://git.kernel.org/stable/c/cd3087582e4fa36e89be4e6f859e75a4400292b4>
- <https://git.kernel.org/stable/c/7b5595f33c3c273613b590892a578d78186bb400>
- <https://git.kernel.org/stable/c/01681aa609b5f110502f56c4e3b2938efcf4a5bc>
- <https://git.kernel.org/stable/c/cd9253c23aedd61eb5ff11f37a36247cd46faf86>

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

---

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