CVE-2026-74381

gpu: host1x: Allow entries in BO caches to be freed

N/A
Published: August 15, 2026 at 05:58 AM UTC
Updated: August 17, 2026 at 06:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: gpu: host1x: Allow entries in BO caches to be freed When a buffer object is pinned via host1x_bo_pin() with a cache, the resulting mapping is kept in the cache so it can be reused on subsequent pins. Each mapping held a reference to the underlying host1x_bo (taken in tegra_bo_pin / gather_bo_pin), so as long as a mapping was cached, the bo itself could not be freed. However, the only way to remove the cached mapping was through the free path of the buffer object. This meant that if a bo got cached, it could never get freed again. Resolve the circularity by holding a weak reference to the bo from the cache side. This is done by having the .pin callbacks not bump the bo's refcount -- instead the common Host1x bo code does so, except for the cache reference. Also move the remove-cache-mapping-on-free code into a common function inside Host1x code. This is only called from the TegraDRM GEM buffers since those are the only ones that can be cached at the moment.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.17 ≤ v < 6.1.1785.17 ≤ v < 6.12.975.17 ≤ v < 6.18.405.17 ≤ v < 6.6.1455.17 ≤ v < 7.1.55.17 ≤ v < 7.21f39b1dfa53c84b56d7ad37fed44afda7004959d5.17
Vendor states this is fixed in 0e9dd7cfb9986b78cc81eca126ccfbf57f4c0602 (fixed)
Vendor states this is fixed in 3cbf5e3c46e66d9b3b6b91099bb720c6cb1be3bc (fixed)
Vendor states this is fixed in 71c017b3f83ff72638f2a1b1d6d4e7bc61d30231 (fixed)
Vendor states this is fixed in 8c0d3cf0d5108c96317e0eca92b60dd368867cef (fixed)
Vendor states this is fixed in af755456299d44e4ed6af3b7c70a7f03ea37fdf1 (fixed)
Vendor states this is fixed in df63c76f9c8d881ca7bce1aecfba512328d0527d (fixed)
Vendor states this is fixed in 5.17 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card