mount: handle NULL values in mnt_ns_release()
Summary
| CVE | CVE-2025-40195 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2025-11-12 22:15:46 UTC |
| Updated | 2026-10-19 21:10:00 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: mount: handle NULL values in mnt_ns_release() When calling in listmount() mnt_ns_release() may be passed a NULL pointer. Handle that case gracefully. |
Risk And Classification
EPSS: 0.001970000 probability, percentile 0.088400000 (date 2026-10-19)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 1901c92497bd90caf608a474f1bf4d8795b372a2 2d68f8a7379d9c61005e982600c61948d4d019bd git | Not specified |
| CNA | Linux | Linux | affected 1901c92497bd90caf608a474f1bf4d8795b372a2 99ae3e70a293834d0274c46a37120c71a24a4995 git | Not specified |
| CNA | Linux | Linux | affected 1901c92497bd90caf608a474f1bf4d8795b372a2 6c7ca6a02f8f9549a438a08a23c6327580ecf3d6 git | Not specified |
| CNA | Linux | Linux | affected 6.11 | Not specified |
| CNA | Linux | Linux | unaffected 6.11 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.54 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.17.4 6.17.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/99ae3e70a293834d0274c46a37120c71a24a4995 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/6c7ca6a02f8f9549a438a08a23c6327580ecf3d6 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/2d68f8a7379d9c61005e982600c61948d4d019bd | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.