CVE-2025-68233

What it actually does

Missing put_pid() call after get_task_pid() in host1x_memory_context_alloc() within the Tegra DRM driver causes an unreleased PID reference, resulting in a kernel resource leak.

Why it matters to the business

Prolonged operation on affected systems may lead to gradual kernel memory consumption, potentially impacting stability and performance in environments using compatible Tegra hardware or dependent packages.

How an attack unfolds

A local user triggers repeated memory context allocations in the DRM subsystem to exhaust PID references over time; the low EPSS score and lack of known exploitation indicate this is primarily a stability issue rather than a targeted attack vector.

How to fix it

Upgrade the Linux kernel to commit 6b572e5154af08ee13f8d2673e86f83bc5ff86cd or later; update gobump (Chainguard) and gobump (Wolfi) to version 0.9.0-r2.

How to confirm the fix worked

Inspect the host1x_memory_context_alloc() function for the presence of the put_pid() call and confirm the running kernel or package version matches a fixed release.

Typical attack path

1. Obtain local user access on an affected Linux system
2. Repeatedly invoke operations that allocate host1x memory contexts
3. Monitor for increasing kernel memory usage attributable to PID structures

How to detect it

Examine kernel logs and memory usage statistics for patterns of unreleased PID references in the DRM subsystem; profile allocations in the host1x driver path.

What your security team should do

• Apply the listed kernel and package updates at the earliest maintenance window
• Review systems using Tegra DRM for signs of unexpected memory growth
• Prioritize updates on high-uptime or multi-user systems