# ptp: Add a upper bound on max_vclocks

CVE record · `CVE-2025-40057`

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

Published by the CVE Program (CNA: Linux) at 28 Oct 2025, 11:48 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: `73f37068d540eba5f93ba3a0019bf479d35ebd76 to before 5ba2f8fd3db1c695f74f7f5df72eb87d52668a66` (git)
  - affected: `73f37068d540eba5f93ba3a0019bf479d35ebd76 to before da513f2ad1b1b1cf1880ccc2603ce1f1f818eb2e` (git)
  - affected: `73f37068d540eba5f93ba3a0019bf479d35ebd76 to before 8dd446056336faa2283d62cefc2f576536845edc` (git)
  - affected: `73f37068d540eba5f93ba3a0019bf479d35ebd76 to before 35ce5f163889dbce88eda1df661b357a09bbed87` (git)
  - affected: `73f37068d540eba5f93ba3a0019bf479d35ebd76 to before e9f35294e18da82162004a2f35976e7031aaf7f9` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.14`
  - unaffected: `before 5.14` (semver)
  - unaffected: `6.1.191 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.160 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.53 to 6.12.*, inclusive` (semver)
  - unaffected: `6.17.3 to 6.17.*, inclusive` (semver)
  - unaffected: `6.18 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.0025, the 16th percentile, on 19 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 28 Oct 2025. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/5ba2f8fd3db1c695f74f7f5df72eb87d52668a66>
- <https://git.kernel.org/stable/c/da513f2ad1b1b1cf1880ccc2603ce1f1f818eb2e>
- <https://git.kernel.org/stable/c/8dd446056336faa2283d62cefc2f576536845edc>
- <https://git.kernel.org/stable/c/35ce5f163889dbce88eda1df661b357a09bbed87>
- <https://git.kernel.org/stable/c/e9f35294e18da82162004a2f35976e7031aaf7f9>

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

---

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