# configfs-tsm-report: Fix NULL dereference of tsm_ops

CVE record · `CVE-2025-38210`

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

Published by the CVE Program (CNA: Linux) at 4 Jul 2025, 13:37 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: `70e6f7e2b98575621019aa40ac616be58ff984e0 to before 015f04ac884a454d4d8aaa7b67758f047742b1cf` (git)
  - affected: `70e6f7e2b98575621019aa40ac616be58ff984e0 to before cefbafcbdef011d6ef9414902311afdfba3c33eb` (git)
  - affected: `70e6f7e2b98575621019aa40ac616be58ff984e0 to before fba4ceaa242d2bdf4c04b77bda41d32d02d3925d` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.7`
  - unaffected: `before 6.7` (semver)
  - unaffected: `6.12.35 to 6.12.*, inclusive` (semver)
  - unaffected: `6.15.4 to 6.15.*, inclusive` (semver)
  - unaffected: `6.16 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.

> The Linux kernel configfs-tsm-report facility can be crashed through a NULL pointer dereference of tsm_ops. The privlevel_store and provider_show attributes did not check whether the TSM ops were still registered after tsm_unregister(), so a local user with access to a configfs config-item could trigger the fault. Upgrade to a fixed kernel version: the source lists fixes at commits 015f04ac884a454d4d8aaa7b67758f047742b1cf, cefbafcbdef011d6ef9414902311afdfba3c33eb and fba4ceaa242d2bdf4c04b77bda41d32d02d3925d, and versions 6.12.35, 6.15.4 and 6.16 as unaffected; no workaround is given.

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

## Timeline

- 4 Jul 2025, 13:37 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2025-38210)
- 4 Jul 2025, 14:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2025-38210)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/015f04ac884a454d4d8aaa7b67758f047742b1cf>
- <https://git.kernel.org/stable/c/cefbafcbdef011d6ef9414902311afdfba3c33eb>
- <https://git.kernel.org/stable/c/fba4ceaa242d2bdf4c04b77bda41d32d02d3925d>

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

---

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