# drm/msm: Fix another leak in the submit error path

CVE record · `CVE-2025-38409`

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

Published by the CVE Program (CNA: Linux) at 25 Jul 2025, 13:20 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: `0cf6c71d70d8aa39b8fd0e39c9009602a0e0d300 to before 00b3401f692082ddf6342500d1be25560bba46d4` (git)
  - affected: `0cf6c71d70d8aa39b8fd0e39c9009602a0e0d300 to before c40ad1c04d306f7fde26337fdcf8a5979657d93f` (git)
  - affected: `0cf6c71d70d8aa39b8fd0e39c9009602a0e0d300 to before 3f6ce8433a9035b0aa810e1f5b708e9dc1c367b0` (git)
  - affected: `0cf6c71d70d8aa39b8fd0e39c9009602a0e0d300 to before 30d3819b0b9173e31b84d662a592af8bad351427` (git)
  - affected: `0cf6c71d70d8aa39b8fd0e39c9009602a0e0d300 to before f681c2aa8676a890eacc84044717ab0fd26e058f` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `3.12`
  - unaffected: `before 3.12` (semver)
  - unaffected: `6.1.144 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.97 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.37 to 6.12.*, inclusive` (semver)
  - unaffected: `6.15.6 to 6.15.*, inclusive` (semver)
  - unaffected: `6.16 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.0019, the 8th percentile, on 20 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 25 Jul 2025. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/00b3401f692082ddf6342500d1be25560bba46d4>
- <https://git.kernel.org/stable/c/c40ad1c04d306f7fde26337fdcf8a5979657d93f>
- <https://git.kernel.org/stable/c/3f6ce8433a9035b0aa810e1f5b708e9dc1c367b0>
- <https://git.kernel.org/stable/c/30d3819b0b9173e31b84d662a592af8bad351427>
- <https://git.kernel.org/stable/c/f681c2aa8676a890eacc84044717ab0fd26e058f>

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

---

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