CVE-2026-68245: drm/amdgpu: fix lifetime issue of amdgpu_vm_get_task_info_pasid()
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.13% (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 04cc4aa3617b0ed67e859f91f09de5d896a46f3a, 1173190412fb9d12e7efce76734118d9712ff970, 5d5fb9124a2bba96a7807086d8fe0f7ce810d546.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 04cc4aa3617b0ed67e859f91f09de5d896a46f3a, 1173190412fb9d12e7efce76734118d9712ff970, 5d5fb9124a2bba96a7807086d8fe0f7ce810d546 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: drm/amdgpu: fix lifetime issue of amdgpu_vm_get_task_info_pasid() The vm pointer returned from amdgpu_vm_get_vm_from_pasid() is only valid while the lock is still being held. Once xa_unlock_irqrestore is called and returned, the pointer is no longer under lock and is subject to modification. Since, the caller still dereferences vm->task_info in amdgpu_vm_get_task_info_vm() after the lock is removed, this causes a use after unlock problem. Remove the lifetime issue present in amdgpu_vm_get_task_info_pasid() through removing the amdgpu_vm_get_vm_from_pasid() function from amdgpu_vm.c and making the relevant code inline to hold the lock while it is still in use. (cherry picked from commit 9d01579f3f868b333acc901815972685989092c7)
- Published
- Aug 10, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-362
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
- aa22d6c58505d239814b5ef8fa7da4ce43e9212b, 251840f22eff35c25de531a3fcb523df94c128c0, 6.9affected
- b8f67b9ddf4f8fe6dd536590712b5912ad78f99c and later · before fe16a7e5336ae888751984e30c451fbf7cfa5df7affected · git
- b8f67b9ddf4f8fe6dd536590712b5912ad78f99c and later · before 1173190412fb9d12e7efce76734118d9712ff970affected · git
- b8f67b9ddf4f8fe6dd536590712b5912ad78f99c and later · before 5d5fb9124a2bba96a7807086d8fe0f7ce810d546affected · git
- b8f67b9ddf4f8fe6dd536590712b5912ad78f99c and later · before 04cc4aa3617b0ed67e859f91f09de5d896a46f3aaffected · git
- 6.1.191 and later · before 6.2affected · semver
- 6.6.160 and later · before 6.7affected · semver
- before 6.9not affected · semver
- 6.12.101 and later · up to and including 6.12.*not affected · semver
- 6.18.42 and later · up to and including 6.18.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
+96
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-68243Aug 10, 2026 · drm/i915/gem: Fix NULL deref in I915_CONTEXT_PARAM_SSEU0Monitor
- ← EarlierCVE-2026-68244Aug 10, 2026 · drm/i915/gem: Do not leak siblings[] on proto context error0Monitor
- Later →CVE-2026-68247Aug 10, 2026 · drm/i915/bios: range check LFP Data Block panel_type20Monitor
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 | 04cc4aa3617b0ed67e859f91f09de5d896a46f3a | Vendor (CNA) |
| Linux Linux | 1173190412fb9d12e7efce76734118d9712ff970 | Vendor (CNA) |
| Linux Linux | 5d5fb9124a2bba96a7807086d8fe0f7ce810d546 | Vendor (CNA) |
| Linux Linux | 6.2 | Vendor (CNA) |
| Linux Linux | 6.7 | Vendor (CNA) |
| Linux Linux | fe16a7e5336ae888751984e30c451fbf7cfa5df7 | Vendor (CNA) |
| almalinux:kernel | 5.14.0-687.57.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-687.57.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-687.57.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-687.57.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-687.57.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-687.57.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-687.57.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-687.57.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-modules | 5.14.0-687.57.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-modules-core | 5.14.0-687.57.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-modules-extra | 5.14.0-687.57.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 5.14.0-687.57.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.12.101-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-687.57.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-687.57.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-687.57.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-687.57.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-687.57.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-687.57.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-687.57.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-687.57.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-687.57.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-687.57.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
+3
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-720645 days apartnet: mana: Sync page pool RX frags for CPU39Monitor
- CVE-2026-6397822 days apartnet/handshake: Drain pending requests at net namespace exit39Monitor
- CVE-2026-683290 days apartiommu/amd: Wait for completion instead of returning early in iommu_completion_wait()35Monitor
- CVE-2026-645616 days apartKVM: x86: Check for invalid/obsolete root *after* making MMU pages available35Monitor
- CVE-2026-681380 days apartnet/sched: serialize qdisc_rtab_list against concurrent get/put31Monitor
- CVE-2026-682000 days apartALSA: timer: don't re-enter an instance callback that is still running31Monitor
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-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.