# f2fs: read COW data with the original inode during atomic write

CVE record · `CVE-2026-63811`

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

Published by the CVE Program (CNA: Linux) at 19 Jul 2026, 12:02 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: `591fc34e1f98b0d7eef4aa3440bfdff3c5a1cadd to before bcc9df992f3cbc43f2ecfe0b22e428e50f326e72` (git)
  - affected: `591fc34e1f98b0d7eef4aa3440bfdff3c5a1cadd to before 655d55c5740d37ffdf6233ff5fe21cea879407f1` (git)
  - affected: `591fc34e1f98b0d7eef4aa3440bfdff3c5a1cadd to before 7e4ab3907f44dc243d026048d7f5d477dae9267b` (git)
  - affected: `591fc34e1f98b0d7eef4aa3440bfdff3c5a1cadd to before a92332f32a8d31a7eee47b1dc1d751cb3319908f` (git)
  - affected: `591fc34e1f98b0d7eef4aa3440bfdff3c5a1cadd to before a41075acde0124d2f8a5f563068a5d63e8ffd57b` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.4`
  - unaffected: `before 6.4` (semver)
  - unaffected: `6.6.160 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.114 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.57 to 6.18.*, inclusive` (semver)
  - unaffected: `7.1.3 to 7.1.*, inclusive` (semver)
  - unaffected: `7.2 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.0009, the 1st percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 19 Jul 2026, 12:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-63811)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/bcc9df992f3cbc43f2ecfe0b22e428e50f326e72>
- <https://git.kernel.org/stable/c/655d55c5740d37ffdf6233ff5fe21cea879407f1>
- <https://git.kernel.org/stable/c/7e4ab3907f44dc243d026048d7f5d477dae9267b>
- <https://git.kernel.org/stable/c/a92332f32a8d31a7eee47b1dc1d751cb3319908f>
- <https://git.kernel.org/stable/c/a41075acde0124d2f8a5f563068a5d63e8ffd57b>

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

---

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