CVE-2025-38210
configfs-tsm-report: Fix NULL dereference of tsm_ops
Reported by linux · Published July 4, 2025
In the Linux kernel, the following vulnerability has been resolved: configfs-tsm-report: Fix NULL dereference of tsm_ops Unlike sysfs, the lifetime of configfs objects is controlled by userspace. There is no mechanism for the kernel to find and delete all created config-items. Instead, the configfs-tsm-report mechanism has an expectation that tsm_unregister() can happen at any time and cause established config-item access to start failing. That expectation is not fully satisfied. While tsm_report_read(), tsm_report_{is,is_bin}_visible(), and tsm_report_make_item() safely fail if tsm_ops have been unregistered, tsm_report_privlevel_store() tsm_report_provider_show() fail to check for ops registration. Add the missing checks for tsm_ops having been removed. Now, in supporting the ability for tsm_unregister() to always succeed, it leaves the problem of what to do with lingering config-items. The expectation is that the admin that arranges for the ->remove() (unbind) of the ${tsm_arch}-guest driver is also responsible for deletion of all open config-items. Until that deletion happens, ->probe() (reload / bind) of the ${tsm_arch}-guest driver fails. This allows for emergency shutdown / revocation of attestation interfaces, and requires coordinated restart.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel6.12 | Amazon Linux | 6.12.35-55.103.amzn2023 |
| linux_kernel | linux | 6.15.4, 6.12.35 |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 70e6f7e2b98575621019aa40ac616be58ff984e0, 70e6f7e2b98575621019aa40ac616be58ff984e0, 70e6f7e2b98575621019aa40ac616be58ff984e0 |
| Linux | Linux | 6.7, 0, 6.12.35 |
| amazon:2023 | kernel6.12 | 0 |
| linux | linux_kernel | 6.7, 6.7, 6.7 |
| amazon:2023 | kernel-tools | 0 |
| amazon:2023 | perf6.12 | 0 |
| amazon:2023 | python3-perf6.12 | 0 |
| amazon:2023 | bpftool | 0 |
| amazon:2023 | kernel-tools-devel | 0 |
| Linux | Linux | 6.7, 6.16, 6.15.4 |
| amazon:2023 | kernel-libbpf-static | 0 |
| amazon:2023 | kernel-headers | 0 |
| amazon:2023 | kernel-libbpf | 0 |
| amazon:2023 | kernel-livepatch-6.12.35-55.103 | 0 |
| amazon:2023 | kernel6.12-modules-extra | 0 |
| amazon:2023 | kernel-devel | 0 |
| amazon:2023 | kernel-libbpf-devel | 0 |
| amazon:2023 | kernel-modules-extra-common | 0 |
Timeline
- Jul 4, 2025 CVE Published
- Jul 5, 2025 EPSS Score (30 in total, the first dated here)
- Oct 12, 2025 PoC Published (8 in total, the first dated here)
- Mar 29, 2026 Distribution Patch (223 in total, the first dated here)
- Mar 29, 2026 Security Advisory (273 in total, the first dated here)
- Jun 9, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-38210
vulnetix vdb fixes CVE-2025-38210
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-38210/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart