Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-68273: drm/amdgpu: Fix context pstate override handling

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.10% (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 23a8726e1d7597fe7c9a59d5dc42ba8b7d345b8a, 3531910845165dcf1a213267199ccc97e03cd58a, 6.1; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 23a8726e1d7597fe7c9a59d5dc42ba8b7d345b8a, 3531910845165dcf1a213267199ccc97e03cd58a, 6.1; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes 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 context pstate override handling There are several problems in the context pstate handling code. The most serious ones are potential use-after-free and NULL pointer dereferences at context initialization time. Both are due amdgpu_ctx_init() not holding the adev->pm.stable_pstate_ctx_lock, which is otherwise used from both sysfs and the context code itself for modifying and clearing the stored context pointer. Second issue is that context fini can trample over the pstate configuration set via sysfs. This is due the restore state (ctx->stable_pstate) being saved at context init time, and not if, or when the context actually changes the pstate. As the context exits it will therefore incorrectly restore to what was set before the sysfs override was requested. The simplest fix is to drastically simplify how the state is tracked, by clearly defining the points at which pstate ownership is taken and released, and to handle all transitions under the correct lock. Instead of at context init time, the previous state is saved only at the point the context overrides the current state, and is restored on context exit only if the context is still the owner of the current override state. (cherry picked from commit 1b5e413713c0a93bc1818394d0ce49aaad21bd27)

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Aug 10, 2026
Updated
Oct 30, 2026
EPSS
0.1% · 1th percentile

Report tools

JSON

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.

Follow CVE-2026-68273

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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

    • 6607901fce79959130db485e7549dacaaeef034e, 6.1affected
    • 79610d3041338dc1ef554d6fd8b3b3e23be527f5 and later · before ebed6179c993f07da24d0a454816e7da790377afaffected · git
    • 79610d3041338dc1ef554d6fd8b3b3e23be527f5 and later · before 3531910845165dcf1a213267199ccc97e03cd58aaffected · git
    • 79610d3041338dc1ef554d6fd8b3b3e23be527f5 and later · before 23a8726e1d7597fe7c9a59d5dc42ba8b7d345b8aaffected · git
    • 79610d3041338dc1ef554d6fd8b3b3e23be527f5 and later · before e06c39cc1c48dca68a5ffd971c23025a52d46634affected · git
    • 79610d3041338dc1ef554d6fd8b3b3e23be527f5 and later · before 9f9c88eb298c54348be3ca4087f4f4c615065b87affected · git
    • 79610d3041338dc1ef554d6fd8b3b3e23be527f5 and later · before c1dc4ccb82c9e56325d8e7514ca4c90bd1efb351affected · git
    • 6.0.7 and later · before 6.1affected · semver
    • before 6.1not affected · semver
    • 6.1.191 and later · up to and including 6.1.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2

+96

Same product

linux: all records

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-68265Aug 10, 2026 · drm/xe/vm: Fix BO prefetch with CONSULT_MEM_ADVISE_PREF_LOC
    29Monitor
  • ← EarlierCVE-2026-68266Aug 10, 2026 · drm/xe: Hold a dma-buf reference for imported BOs
    31Monitor
  • Later →CVE-2026-68274Aug 10, 2026 · drm/xe/guc: Fix buffer overflow in steered register list allocation
    31Monitor

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 Linux23a8726e1d7597fe7c9a59d5dc42ba8b7d345b8aVendor (CNA)
Linux Linux3531910845165dcf1a213267199ccc97e03cd58aVendor (CNA)
Linux Linux6.1Vendor (CNA)
Linux Linux9f9c88eb298c54348be3ca4087f4f4c615065b87Vendor (CNA)
Linux Linuxc1dc4ccb82c9e56325d8e7514ca4c90bd1efb351Vendor (CNA)
Linux Linuxe06c39cc1c48dca68a5ffd971c23025a52d46634Vendor (CNA)
Linux Linuxebed6179c993f07da24d0a454816e7da790377afVendor (CNA)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
almalinux:kernel5.14.0-687.52.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel6.12.0-211.60.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k5.14.0-687.52.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k6.12.0-211.60.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.52.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.60.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.52.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.60.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.52.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.60.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-687.52.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.60.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-687.52.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.60.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.52.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.60.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.52.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.60.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.52.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.60.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-687.52.1.el9_8 · AlmaLinux:9Package registry (OSV)

+19

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.

Credits

All researchers

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.

  • CVE-2026-720645 days apartnet: mana: Sync page pool RX frags for CPU
    39Monitor
  • CVE-2026-6397822 days apartnet/handshake: Drain pending requests at net namespace exit
    39Monitor
  • 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 available
    35Monitor
  • CVE-2026-681380 days apartnet/sched: serialize qdisc_rtab_list against concurrent get/put
    31Monitor
  • CVE-2026-684170 days apartRDMA/siw: publish QP after initialization
    31Monitor

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.

All national notices →

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.

ATT&CK techniques

—

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

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

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records