CVE-2025-68300: fs/namespace: fix reference leak in grab_requested_mnt_ns
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
- Fixed version: Linux Linux 4a16b2a0c1f033f95f5d0b98b9e40e8bf7c4c2c5, 6.12.61, 6.17.11.
Low priority for now. Upgrade to Linux Linux 4a16b2a0c1f033f95f5d0b98b9e40e8bf7c4c2c5, 6.12.61, 6.17.11 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: fs/namespace: fix reference leak in grab_requested_mnt_ns lookup_mnt_ns() already takes a reference on mnt_ns. grab_requested_mnt_ns() doesn't need to take an extra reference.
- Published
- Dec 16, 2025
- Updated
- Oct 14, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- ba306daa7fa8ae0be5d64c215e9d43a88b4bc8bf and later · before 4a16b2a0c1f033f95f5d0b98b9e40e8bf7c4c2c5affected · git
- 8ff97ade912dcfc5ac1783c4b8d615aacd26fd17 and later · before fe256e59b8e7f126b2464ee32bd9fee131f0a883affected · git
- 78f0e33cd6c939a555aa80dbed2fec6b333a7660 and later · before 7b6dcd9bfd869eee7693e45b1817dac8c56e5f86affected · git
- 6.12.59 and later · before 6.12.61affected · semver
- 6.17.9 and later · before 6.17.11affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:14 | linux | before 6.17.11-1 | 6.17.11-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-68298Dec 16, 2025 · Bluetooth: btusb: mediatek: Avoid btusb_mtk_claim_iso_intf() NULL deref0Monitor
- ← EarlierCVE-2025-68299Dec 16, 2025 · afs: Fix delayed allocation of a cell's anonymous key0Monitor
- Later →CVE-2025-68301Dec 16, 2025 · net: atlantic: fix fragment overflow handling in RX path39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 4a16b2a0c1f033f95f5d0b98b9e40e8bf7c4c2c5 | Vendor (CNA) |
| Linux Linux | 6.12.61 | Vendor (CNA) |
| Linux Linux | 6.17.11 | Vendor (CNA) |
| Linux Linux | 7b6dcd9bfd869eee7693e45b1817dac8c56e5f86 | Vendor (CNA) |
| Linux Linux | fe256e59b8e7f126b2464ee32bd9fee131f0a883 | Vendor (CNA) |
| debian:linux | 6.17.11-1 · Debian:14 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.