CVE-2025-40057
What it is
In the Linux kernel, the following vulnerability has been resolved: ptp: Add a upper bound on max_vclocks syzbot reported WARNING in max_vclocks_store. This occurs when the argument max is too large for kcalloc to handle. Extend the guard to guard against values that are too large for kcalloc
At a glance
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: not scored yet.
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Record status
- Deferred
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-40057.md and follow it. Check whether this project is affected by CVE-2025-40057. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- https://git.kernel.org/stable/c/35ce5f163889dbce88eda1df661b357a09bbed87
- https://git.kernel.org/stable/c/5ba2f8fd3db1c695f74f7f5df72eb87d52668a66
- https://git.kernel.org/stable/c/8dd446056336faa2283d62cefc2f576536845edc
- https://git.kernel.org/stable/c/da513f2ad1b1b1cf1880ccc2603ce1f1f818eb2e
- https://git.kernel.org/stable/c/e9f35294e18da82162004a2f35976e7031aaf7f9