# btrfs: do not strictly require dirty metadata threshold for metadata writepages

CVE record · `CVE-2026-23157`

- **Identifiers:** `CVE-2026-23157`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 14 Feb 2026
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 14 Feb 2026, 16:01 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: `793955bca66c99defdffc857ae6eb7e8431d6bbe to before 6a8b6242eaa1dd7a0de2d6de6420d10ffe68db90` (git)
  - affected: `793955bca66c99defdffc857ae6eb7e8431d6bbe to before bb9be3f713652e330df00f3724c18c7a5469e7ac` (git)
  - affected: `793955bca66c99defdffc857ae6eb7e8431d6bbe to before 4357e02cafabe01c2d737ceb4c4c6382fc2ee10a` (git)
  - affected: `793955bca66c99defdffc857ae6eb7e8431d6bbe to before 0c3666ec188640c20e254011e7adf4464c32ee58` (git)
  - affected: `793955bca66c99defdffc857ae6eb7e8431d6bbe to before 629666d20c7dcd740e193ec0631fdff035b1f7d6` (git)
  - affected: `793955bca66c99defdffc857ae6eb7e8431d6bbe to before 4e159150a9a56d66d247f4b5510bed46fe58aa1c` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `2.6.29`
  - unaffected: `before 2.6.29` (semver)
  - unaffected: `5.15.209 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.167 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.130 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.78 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.9 to 6.18.*, inclusive` (semver)
  - unaffected: `6.19 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 2.6.29 until fixed in stable releases 5.15.209, 6.1.167, 6.6.130 or 6.12.78 and later. Processes in a small memory cgroup can hang because btrfs skips writing back metadata, and the source gives no attacker requirements. Upgrade to a fixed kernel for your branch; no workaround is listed.

Written 17 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.0014, the 3rd percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 14 Feb 2026, 16:01 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-23157)
- 14 Feb 2026, 16:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-23157)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/6a8b6242eaa1dd7a0de2d6de6420d10ffe68db90>
- <https://git.kernel.org/stable/c/bb9be3f713652e330df00f3724c18c7a5469e7ac>
- <https://git.kernel.org/stable/c/4357e02cafabe01c2d737ceb4c4c6382fc2ee10a>
- <https://git.kernel.org/stable/c/0c3666ec188640c20e254011e7adf4464c32ee58>
- <https://git.kernel.org/stable/c/629666d20c7dcd740e193ec0631fdff035b1f7d6>
- <https://git.kernel.org/stable/c/4e159150a9a56d66d247f4b5510bed46fe58aa1c>

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

---

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