CVE-2026-68427: gpu: host1x: Fix use-after-free in host1x_bo_clear_cached_mappings
Noroxi assessment
Priority: Monitor (action score 31/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.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 266cddf7bd0f6c79b6c0633aef742a22bf70265b, 5b7e5f84d3d4cea10c3764d2da274810a7934228, 5f4de3c717d34a24d555af581947742980778c02.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 266cddf7bd0f6c79b6c0633aef742a22bf70265b, 5b7e5f84d3d4cea10c3764d2da274810a7934228, 5f4de3c717d34a24d555af581947742980778c02 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: Fix use-after-free in host1x_bo_clear_cached_mappings __host1x_bo_unpin() drops the last reference to the mapping and frees it, so we can't dereference mapping afterwards. The cache itself outlives the mapping, so use the cache local variable instead.
- Published
- Aug 10, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-416
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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
- af755456299d44e4ed6af3b7c70a7f03ea37fdf1 and later · before 86a9bd8c8f422d5f3079da31e151868902fcc702affected · git
- 71c017b3f83ff72638f2a1b1d6d4e7bc61d30231 and later · before abeff53233b984571b87582bb588b4b38ef4ea50affected · git
- 0e9dd7cfb9986b78cc81eca126ccfbf57f4c0602 and later · before 5b7e5f84d3d4cea10c3764d2da274810a7934228affected · git
- 8c0d3cf0d5108c96317e0eca92b60dd368867cef and later · before 5f4de3c717d34a24d555af581947742980778c02affected · git
- df63c76f9c8d881ca7bce1aecfba512328d0527d and later · before b773faa32b0a98c3eb2b50d96de631681e5d1157affected · git
- 3cbf5e3c46e66d9b3b6b91099bb720c6cb1be3bc and later · before 266cddf7bd0f6c79b6c0633aef742a22bf70265baffected · git
- 6.1.178 and later · before 6.1.183affected · semver
- 6.6.145 and later · before 6.6.148affected · semver
- 6.12.97 and later · before 6.12.101affected · semver
- 6.18.40 and later · before 6.18.42affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.101-1~deb12u1 | 6.12.101-1~deb12u1 |
| Debian:13 | linux | before 6.12.101-1 | 6.12.101-1 |
| Debian:14 | linux | before 7.1.6-1 | 7.1.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-68425Aug 10, 2026 · IB/mad: Drop unmatched RMPP responses before reassembly28Monitor
- ← EarlierCVE-2026-68426Aug 10, 2026 · xfrm: fix stale skb->prev after async crypto steals a GSO segment39Monitor
- Later →CVE-2026-68429Aug 11, 2026 · drm/dp_mst: Handle torn-down topology gracefully in drm_dp_mst_topology_queue_probe()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 / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 266cddf7bd0f6c79b6c0633aef742a22bf70265b | Vendor (CNA) |
| Linux Linux | 5b7e5f84d3d4cea10c3764d2da274810a7934228 | Vendor (CNA) |
| Linux Linux | 5f4de3c717d34a24d555af581947742980778c02 | Vendor (CNA) |
| Linux Linux | 6.1.183 | Vendor (CNA) |
| Linux Linux | 6.12.101 | Vendor (CNA) |
| Linux Linux | 6.18.42 | Vendor (CNA) |
| Linux Linux | 6.6.148 | Vendor (CNA) |
| Linux Linux | 7.1.6 | Vendor (CNA) |
| Linux Linux | 86a9bd8c8f422d5f3079da31e151868902fcc702 | Vendor (CNA) |
| Linux Linux | abeff53233b984571b87582bb588b4b38ef4ea50 | Vendor (CNA) |
| Linux Linux | b773faa32b0a98c3eb2b50d96de631681e5d1157 | Vendor (CNA) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · Debian:12 | Package 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.
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.
Credits
All researchersFinders, 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.
- CVE-2026-681170 days aparttipc: clear sock->sk on the failed-insert path in tipc_sk_create()39Monitor
- CVE-2026-681270 days apartila: reload IPv6 header after pskb_may_pull in checksum adjust39Monitor
- CVE-2026-681440 days apartphonet: pep: fix use-after-free in pep_get_sb()39Monitor
- CVE-2026-681560 days apartlibceph: refresh auth->authorizer_buf{,_len} after authorizer update39Monitor
- CVE-2026-683810 days apartksmbd: pin conn during async oplock break notification39Monitor
- CVE-2026-684260 days apartxfrm: fix stale skb->prev after async crypto steals a GSO segment39Monitor
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/5b7e5f84d3d4cea10c3764d2da274810a7934228
- git.kernel.org/stable/c/5f4de3c717d34a24d555af581947742980778c02
- git.kernel.org/stable/c/86a9bd8c8f422d5f3079da31e151868902fcc702
- git.kernel.org/stable/c/abeff53233b984571b87582bb588b4b38ef4ea50
- git.kernel.org/stable/c/b773faa32b0a98c3eb2b50d96de631681e5d1157
Vendor advisories and official records. Exploit/PoC links are deliberately left out.