gpu: host1x: Allow entries in BO caches to be freed
Summary
| CVE | CVE-2026-74381 |
|---|
| State | PUBLISHED |
|---|
| Assigner | Linux |
|---|
| Source Priority | CVE Program / NVD first with legacy fallback |
|---|
| Published | 2026-08-15 06:22:39 UTC |
|---|
| Updated | 2026-08-15 06:22:39 UTC |
|---|
| 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. |
|---|
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 1f39b1dfa53c84b56d7ad37fed44afda7004959d af755456299d44e4ed6af3b7c70a7f03ea37fdf1 git |
Not specified |
| CNA |
Linux |
Linux |
affected 1f39b1dfa53c84b56d7ad37fed44afda7004959d 71c017b3f83ff72638f2a1b1d6d4e7bc61d30231 git |
Not specified |
| CNA |
Linux |
Linux |
affected 1f39b1dfa53c84b56d7ad37fed44afda7004959d 0e9dd7cfb9986b78cc81eca126ccfbf57f4c0602 git |
Not specified |
| CNA |
Linux |
Linux |
affected 1f39b1dfa53c84b56d7ad37fed44afda7004959d 8c0d3cf0d5108c96317e0eca92b60dd368867cef git |
Not specified |
| CNA |
Linux |
Linux |
affected 1f39b1dfa53c84b56d7ad37fed44afda7004959d df63c76f9c8d881ca7bce1aecfba512328d0527d git |
Not specified |
| CNA |
Linux |
Linux |
affected 1f39b1dfa53c84b56d7ad37fed44afda7004959d 3cbf5e3c46e66d9b3b6b91099bb720c6cb1be3bc git |
Not specified |
| CNA |
Linux |
Linux |
affected 5.17 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.17 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.178 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.145 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.97 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.40 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1.5 7.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/0e9dd7cfb9986b78cc81eca126ccfbf57f4c0602 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/71c017b3f83ff72638f2a1b1d6d4e7bc61d30231 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/df63c76f9c8d881ca7bce1aecfba512328d0527d |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/3cbf5e3c46e66d9b3b6b91099bb720c6cb1be3bc |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/8c0d3cf0d5108c96317e0eca92b60dd368867cef |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/af755456299d44e4ed6af3b7c70a7f03ea37fdf1 |
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.