# media: v4l2-subdev: Fix alloc failure check in v4l2_subdev_call_state_try()

CVE record · `CVE-2025-40207`

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

Published by the CVE Program (CNA: Linux) at 12 Nov 2025, 21:56 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: `982c0487185bd466059ff618f398a8d074ddb654 to before 5b0057459cdc243ffb35617603142dcace09c711` (git)
  - affected: `982c0487185bd466059ff618f398a8d074ddb654 to before ed30811fbed40751deb952bde534aa2632dc0bf7` (git)
  - affected: `982c0487185bd466059ff618f398a8d074ddb654 to before 94e6336dc1f06a06f5b4cd04d4a012bba34f2857` (git)
  - affected: `982c0487185bd466059ff618f398a8d074ddb654 to before a553530b3314a0bdc98cf114cdbe204551a70a00` (git)
  - affected: `982c0487185bd466059ff618f398a8d074ddb654 to before f37df9a0eb5e43fcfe02cbaef076123dc0d79c7e` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.0`
  - unaffected: `before 6.0` (semver)
  - unaffected: `6.1.157 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.113 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.54 to 6.12.*, inclusive` (semver)
  - unaffected: `6.17.4 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.0020, the 10th 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 12 Nov 2025. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/5b0057459cdc243ffb35617603142dcace09c711>
- <https://git.kernel.org/stable/c/ed30811fbed40751deb952bde534aa2632dc0bf7>
- <https://git.kernel.org/stable/c/94e6336dc1f06a06f5b4cd04d4a012bba34f2857>
- <https://git.kernel.org/stable/c/a553530b3314a0bdc98cf114cdbe204551a70a00>
- <https://git.kernel.org/stable/c/f37df9a0eb5e43fcfe02cbaef076123dc0d79c7e>

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

---

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