dbcve.org
Linux KernelOperating system · Linux

CVE-2026-31462

MEDIUM · 5.5 CVSS v3.1 Published 2026-04-22
Fix available
A fix is available. Upgrade to 6.12.80 / 6.18.21 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: prevent immediate PASID reuse case PASID resue could cause interrupt issue when process immediately runs into hw state left by previous process exited with the same PASID, it's possible that page faults are still pending in the IH ring buffer when the process exits and frees up its PASID. To prevent the case, it uses idr cyclic allocator same as kernel pid's. (cherry picked from commit 8f1de51f49be692de137c8525106e0fce2d1912d)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 4.15, < 6.12.80>= 6.13, < 6.18.21>= 6.19, < 6.19.11= 7.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.12.80 / 6.18.21 / 6.19.11 or later
Fixed in 6.12.806.18.216.19.11
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to Linux kernel 6.12.80+ (for 4.15-6.12.x users), 6.18.21+ (for 6.13-6.18.x users), 6.19.11+ (for 6.19.x users), or 7.1+ (for 7.0 users)

  1. 1. Identify the current running kernel version using 'uname -r'
  2. 2. Determine which version range your current kernel falls into from: >= 4.15 and < 6.12.80, >= 6.13 and < 6.18.21, >= 6.19 and < 6.19.11, or = 7.0
  3. 3. For kernels < 6.12.80: upgrade to kernel version 6.12.80 or later (6.12.x stable)
  4. 4. For kernels >= 6.13 and < 6.18.21: upgrade to kernel version 6.18.21 or later (6.18.x stable)
  5. 5. For kernels >= 6.19 and < 6.19.11: upgrade to kernel version 6.19.11 or later (6.19.x stable)
  6. 6. For kernel 7.0: upgrade to a version beyond 7.0 (such as 7.1 or later stable release)
  7. 7. Verify the fix commit 14b81abe7bdc25f8097906fc2f91276ffedb2d26 is included in the target kernel by checking the kernel release notes or changelog
  8. 8. After upgrade, confirm amdgpu module loads correctly and PASID allocation uses cyclic behavior
Caveat Kernel upgrades may introduce regressions in other drivers or hardware support; ensure compatibility with your system components before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-31462 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-31462 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data