# loop: Avoid updating block size under exclusive owner

CVE record · `CVE-2025-38709`

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

Published by the CVE Program (CNA: Linux) at 4 Sept 2025, 15:32 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: `89e4fdecb51cf5535867026274bc97de9480ade5 to before 46034518cae95db4abfde990c9ca1a0751855072` (git)
  - affected: `89e4fdecb51cf5535867026274bc97de9480ade5 to before 457d2c5e112fd08dc1039b1ae39a83ec1782360d` (git)
  - affected: `89e4fdecb51cf5535867026274bc97de9480ade5 to before 139a000d20f2f38ce34296feddd641d730fe1c08` (git)
  - affected: `89e4fdecb51cf5535867026274bc97de9480ade5 to before b928438cc87c0bf7ae078e4b7b6e14261e84c5c5` (git)
  - affected: `89e4fdecb51cf5535867026274bc97de9480ade5 to before 5d67b30aefeb7a949040bbb1b4e3b84c5d29a624` (git)
  - affected: `89e4fdecb51cf5535867026274bc97de9480ade5 to before 7e49538288e523427beedd26993d446afef1a6fb` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.14`
  - unaffected: `before 4.14` (semver)
  - unaffected: `6.1.191 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.109 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.43 to 6.12.*, inclusive` (semver)
  - unaffected: `6.15.11 to 6.15.*, inclusive` (semver)
  - unaffected: `6.16.2 to 6.16.*, inclusive` (semver)
  - unaffected: `6.17 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 loop device driver: the block size of a loop device could be changed while a mounted filesystem held it, causing a mismatch with the block size recorded in the superblock. The source gives few details on the attack requirements or impact. The fix makes block size changes take exclusive ownership of the loop device, so the change fails if another exclusive owner such as a filesystem already holds it. No fixed version is listed in the source's version ranges for the fixed commits beyond the listed stable releases; upgrade to a kernel release that includes these fixes.

Written 13 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.0021, the 10th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 4 Sept 2025, 15:32 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2025-38709)
- 4 Sept 2025, 16:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2025-38709)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/46034518cae95db4abfde990c9ca1a0751855072>
- <https://git.kernel.org/stable/c/457d2c5e112fd08dc1039b1ae39a83ec1782360d>
- <https://git.kernel.org/stable/c/139a000d20f2f38ce34296feddd641d730fe1c08>
- <https://git.kernel.org/stable/c/b928438cc87c0bf7ae078e4b7b6e14261e84c5c5>
- <https://git.kernel.org/stable/c/5d67b30aefeb7a949040bbb1b4e3b84c5d29a624>
- <https://git.kernel.org/stable/c/7e49538288e523427beedd26993d446afef1a6fb>

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

---

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