Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Fixed version: Linux Linux 0e9dd7cfb9986b78cc81eca126ccfbf57f4c0602, 3cbf5e3c46e66d9b3b6b91099bb720c6cb1be3bc, 71c017b3f83ff72638f2a1b1d6d4e7bc61d30231.

Low priority for now. Upgrade to Linux Linux 0e9dd7cfb9986b78cc81eca126ccfbf57f4c0602, 3cbf5e3c46e66d9b3b6b91099bb720c6cb1be3bc, 71c017b3f83ff72638f2a1b1d6d4e7bc61d30231 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Aug 15, 2026
Updated
Aug 17, 2026
EPSS
0.2% · 11th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-74381

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.17affected
    • 1f39b1dfa53c84b56d7ad37fed44afda7004959d and later · before af755456299d44e4ed6af3b7c70a7f03ea37fdf1affected · git
    • 1f39b1dfa53c84b56d7ad37fed44afda7004959d and later · before 71c017b3f83ff72638f2a1b1d6d4e7bc61d30231affected · git
    • 1f39b1dfa53c84b56d7ad37fed44afda7004959d and later · before 0e9dd7cfb9986b78cc81eca126ccfbf57f4c0602affected · git
    • 1f39b1dfa53c84b56d7ad37fed44afda7004959d and later · before 8c0d3cf0d5108c96317e0eca92b60dd368867cefaffected · git
    • 1f39b1dfa53c84b56d7ad37fed44afda7004959d and later · before df63c76f9c8d881ca7bce1aecfba512328d0527daffected · git
    • 1f39b1dfa53c84b56d7ad37fed44afda7004959d and later · before 3cbf5e3c46e66d9b3b6b91099bb720c6cb1be3bcaffected · git
    • before 5.17not affected · semver
    • 6.1.178 and later · up to and including 6.1.*not affected · semver
    • 6.6.145 and later · up to and including 6.6.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.5-17.1.5-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-74372Aug 15, 2026 · raid1: fix nr_pending leak in REQ_ATOMIC bad-block error path
    0Monitor
  • ← EarlierCVE-2026-74379Aug 15, 2026 · dax/kmem: account for partial discontiguous resource upon removal
    0Monitor
  • Later →CVE-2026-74382Aug 15, 2026 · net/sched: cls_bpf: prevent unbounded recursion in offload rollback
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0e9dd7cfb9986b78cc81eca126ccfbf57f4c0602Vendor (CNA)
Linux Linux3cbf5e3c46e66d9b3b6b91099bb720c6cb1be3bcVendor (CNA)
Linux Linux71c017b3f83ff72638f2a1b1d6d4e7bc61d30231Vendor (CNA)
Linux Linux8c0d3cf0d5108c96317e0eca92b60dd368867cefVendor (CNA)
Linux Linuxaf755456299d44e4ed6af3b7c70a7f03ea37fdf1Vendor (CNA)
Linux Linuxdf63c76f9c8d881ca7bce1aecfba512328d0527dVendor (CNA)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records