# btrfs: fix zero size inode with non-zero size after log replay

CVE record · `CVE-2026-43118`

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

Published by the CVE Program (CNA: Linux) at 6 May 2026, 07:40 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: `12fcfd22fe5bf4fe74710232098bc101af497995 to before 126999610eddeb1de3b47680585f4bc9531dc7f4` (git)
  - affected: `12fcfd22fe5bf4fe74710232098bc101af497995 to before c939bfa67d221f75351a5bf2fc912e8125547b7e` (git)
  - affected: `12fcfd22fe5bf4fe74710232098bc101af497995 to before 91990732ec4ce5c09361d498c6d621f5a76ee1f2` (git)
  - affected: `12fcfd22fe5bf4fe74710232098bc101af497995 to before fddb157536e67a055597f00a8b4922d5f5ed0826` (git)
  - affected: `12fcfd22fe5bf4fe74710232098bc101af497995 to before 03e966b63df5b06790310c1faaf3e0cb43adea8b` (git)
  - affected: `12fcfd22fe5bf4fe74710232098bc101af497995 to before 5254d4181add9dfaa5e3519edd71cc8f752b2f85` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `2.6.30`
  - unaffected: `before 2.6.30` (semver)
  - unaffected: `6.1.191 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.160 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.114 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.24 to 6.18.*, inclusive` (semver)
  - unaffected: `6.19.14 to 6.19.*, inclusive` (semver)
  - unaffected: `7.0 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.0016, the 4th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 6 May 2026, 10:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-43118)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/126999610eddeb1de3b47680585f4bc9531dc7f4>
- <https://git.kernel.org/stable/c/c939bfa67d221f75351a5bf2fc912e8125547b7e>
- <https://git.kernel.org/stable/c/91990732ec4ce5c09361d498c6d621f5a76ee1f2>
- <https://git.kernel.org/stable/c/fddb157536e67a055597f00a8b4922d5f5ed0826>
- <https://git.kernel.org/stable/c/03e966b63df5b06790310c1faaf3e0cb43adea8b>
- <https://git.kernel.org/stable/c/5254d4181add9dfaa5e3519edd71cc8f752b2f85>

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

---

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