# dm thin metadata: fix metadata snapshot consistency on commit failure

CVE record · `CVE-2026-72108`

- **Identifiers:** `CVE-2026-72108`
- **State:** Confirmed
- **Severity:** CVSS 7.8 High
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-672](https://cwe.mitre.org/data/definitions/672.html)
- **Tags:** [CWE-672](https://agentprime.io/advisories/tag/cwe-672.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 15 Aug 2026
- **Updated:** 19 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 15 Aug 2026, 05:52 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: `991d9fa02da0dd1f843dc011376965e0c8c6c9b5 to before 4af993468193cf4cd32ba5748786e7801945f7d2` (git)
  - affected: `991d9fa02da0dd1f843dc011376965e0c8c6c9b5 to before abf2fae92cbe68945028987d498cc72f8f0e23a8` (git)
  - affected: `991d9fa02da0dd1f843dc011376965e0c8c6c9b5 to before 5efb1a7734ed4035fa4fdc3716bdb84621f27cf6` (git)
  - affected: `991d9fa02da0dd1f843dc011376965e0c8c6c9b5 to before 3dc9ae1029320d77472c44965e572f176949cd63` (git)
  - affected: `991d9fa02da0dd1f843dc011376965e0c8c6c9b5 to before b5f9a31c51cbb374a1713c3494f8660ab070f035` (git)
  - affected: `991d9fa02da0dd1f843dc011376965e0c8c6c9b5 to before 7f76245960a332f39b08cc556e675d1765dc5bbb` (git)
  - affected: `991d9fa02da0dd1f843dc011376965e0c8c6c9b5 to before 9f1a0d27586ceab055e6b050e3731ce3c6b2c4f0` (git)
  - affected: `991d9fa02da0dd1f843dc011376965e0c8c6c9b5 to before 5bcd4d3058ebaf46ad2e163829d87dd4870c7a45` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `3.2`
  - unaffected: `before 3.2` (semver)
  - unaffected: `5.10.261 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.212 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.178 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.145 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.97 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.40 to 6.18.*, inclusive` (semver)
  - unaffected: `7.1.5 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

- 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.0026, the 17th percentile, on 6 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 15 Aug 2026. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/4af993468193cf4cd32ba5748786e7801945f7d2>
- <https://git.kernel.org/stable/c/abf2fae92cbe68945028987d498cc72f8f0e23a8>
- <https://git.kernel.org/stable/c/5efb1a7734ed4035fa4fdc3716bdb84621f27cf6>
- <https://git.kernel.org/stable/c/3dc9ae1029320d77472c44965e572f176949cd63>
- <https://git.kernel.org/stable/c/b5f9a31c51cbb374a1713c3494f8660ab070f035>
- <https://git.kernel.org/stable/c/7f76245960a332f39b08cc556e675d1765dc5bbb>
- <https://git.kernel.org/stable/c/9f1a0d27586ceab055e6b050e3731ce3c6b2c4f0>
- <https://git.kernel.org/stable/c/5bcd4d3058ebaf46ad2e163829d87dd4870c7a45>

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

---

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