Kernel resource leak via unreleased PID reference
Published Dec 16, 2025 · Updated Dec 16, 2025
Resource leak in Linux kernel 6.0 and affected later branches allows local users to retain PID references through Tegra DRM operations. The drm/tegra allocation path calls get_task_pid(), then passes that reference to host1x_memory_context_alloc(), which does not assume ownership, without a matching put_pid(). Reachability requires Tegra host1x memory contexts with IOMMU support; repeated allocations retain PID references and consume kernel resources.
Summary
What happened
Resource leak in Linux kernel 6.0 and affected later branches allows local users to retain PID references through Tegra DRM operations. The drm/tegra allocation path calls get_task_pid(), then passes that reference to host1x_memory_context_alloc(), which does not assume ownership, without a matching put_pid(). Reachability requires Tegra host1x memory contexts with IOMMU support; repeated allocations retain PID references and consume kernel resources.
The record
- CVE
- CVE-2025-68233
- Published
- Dec 16, 2025
- Updated
- Dec 16, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 16, 2025CVE publishedPublication date reported by the CVE source.
- Dec 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.0
- Affected versionversion=e09db97889ec647ad373f7a7422c83099c6120c5 <27ea5c2c75c3419a9a019240ca44b9256f628df1
- Affected versionversion=e09db97889ec647ad373f7a7422c83099c6120c5 <2e78580e6e7deac6556236ef96db5bbf7b46857e
- Affected versionversion=e09db97889ec647ad373f7a7422c83099c6120c5 <6b572e5154af08ee13f8d2673e86f83bc5ff86cd
- Affected versionversion=e09db97889ec647ad373f7a7422c83099c6120c5 <6cbab9f0da72b4dc3c3f9161197aa3b9daa1fa3a
- Affected versionversion=e09db97889ec647ad373f7a7422c83099c6120c5 <cbf2cbdb0733d7974dab296ffba0e7ae9b6524e5
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo