# btrfs: fix missing last_unlink_trans update when removing a directory

CVE record · `CVE-2026-46160`

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

Published by the CVE Program (CNA: Linux) at 28 May 2026, 09:36 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 af467162290f5fe79d6a361b7c84302e45b1fd9f` (git)
  - affected: `12fcfd22fe5bf4fe74710232098bc101af497995 to before 2525998ac956476bded26b9f34c4164dc890b87a` (git)
  - affected: `12fcfd22fe5bf4fe74710232098bc101af497995 to before 6acbb2f6dff23c9bb9761fb98b516525b9cf1ce9` (git)
  - affected: `12fcfd22fe5bf4fe74710232098bc101af497995 to before cc3c0a0f965754ce230d93ba44ee5b34fbe6138a` (git)
  - affected: `12fcfd22fe5bf4fe74710232098bc101af497995 to before aa9c3ecaf7337df3a689318584f879b5339ede0f` (git)
  - affected: `12fcfd22fe5bf4fe74710232098bc101af497995 to before fb388eb58c1ba047ccabc33901839acfecadcf49` (git)
  - affected: `12fcfd22fe5bf4fe74710232098bc101af497995 to before 36fcc2c7517f8a86379154c9793f867592aa8b7e` (git)
  - affected: `12fcfd22fe5bf4fe74710232098bc101af497995 to before 999757231c49376cd1a37308d2c8c4c9932571e1` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `2.6.30`
  - unaffected: `before 2.6.30` (semver)
  - unaffected: `5.10.259 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.210 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.176 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.141 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.91 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.30 to 6.18.*, inclusive` (semver)
  - unaffected: `7.0.7 to 7.0.*, inclusive` (semver)
  - unaffected: `7.1 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.

> Linux kernel btrfs is vulnerable in versions from commit 12fcfd22fe5bf4fe74710232098bc101af497995 before the listed fixed commits, and affects 2.6.30 onward; the fixed stable branches are 5.10.259, 5.15.210, 6.1.176 and 6.6.141. The source gives few details beyond a bug where removing a directory does not update its last_unlink_trans field, which can cause incorrect fsync behaviour and a failed log replay after a power failure. Upgrade to a fixed kernel version; 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.0013, the 2nd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 28 May 2026, 09:36 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-46160)
- 28 May 2026, 10:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-46160)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/af467162290f5fe79d6a361b7c84302e45b1fd9f>
- <https://git.kernel.org/stable/c/2525998ac956476bded26b9f34c4164dc890b87a>
- <https://git.kernel.org/stable/c/6acbb2f6dff23c9bb9761fb98b516525b9cf1ce9>
- <https://git.kernel.org/stable/c/cc3c0a0f965754ce230d93ba44ee5b34fbe6138a>
- <https://git.kernel.org/stable/c/aa9c3ecaf7337df3a689318584f879b5339ede0f>
- <https://git.kernel.org/stable/c/fb388eb58c1ba047ccabc33901839acfecadcf49>
- <https://git.kernel.org/stable/c/36fcc2c7517f8a86379154c9793f867592aa8b7e>
- <https://git.kernel.org/stable/c/999757231c49376cd1a37308d2c8c4c9932571e1>

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

---

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