Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-74381gpu: host1x: Allow entries in BO caches to be freed

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 1f39b1dfa53c84b56d7ad37fed44afda7004959d – < af755456299d44e4ed6af3b7c70a7f03ea37fdf1
    • affected 1f39b1dfa53c84b56d7ad37fed44afda7004959d – < 71c017b3f83ff72638f2a1b1d6d4e7bc61d30231
    • affected 1f39b1dfa53c84b56d7ad37fed44afda7004959d – < 0e9dd7cfb9986b78cc81eca126ccfbf57f4c0602
    • affected 1f39b1dfa53c84b56d7ad37fed44afda7004959d – < 8c0d3cf0d5108c96317e0eca92b60dd368867cef
    • affected 1f39b1dfa53c84b56d7ad37fed44afda7004959d – < df63c76f9c8d881ca7bce1aecfba512328d0527d
    • affected 1f39b1dfa53c84b56d7ad37fed44afda7004959d – < 3cbf5e3c46e66d9b3b6b91099bb720c6cb1be3bc
  • Linux · Linux

    • affected 5.17
    • unaffected < 5.17
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-74381 badge
[![CVE-2026-74381](https://cveledger.app/badge/CVE-2026-74381.svg)](https://cveledger.app/cve/CVE-2026-74381)

Record last updated .