Kernel warning via failed re-pin count increment
Published Oct 18, 2026 · Updated Oct 18, 2026
Pin-count corruption in the Linux kernel's Nouveau driver allows local users to trigger a kernel warning via incompatible re-pin requests. nouveau_bo_pin_locked() calls ttm_bo_pin() despite returning -EBUSY, leaving an unmatched pin that triggers a warning in ttm_bo_release(). Triggering requires access to the Nouveau driver; the published trace demonstrates a warning, not a crash or privilege escalation.
Summary
What happened
Pin-count corruption in the Linux kernel's Nouveau driver allows local users to trigger a kernel warning via incompatible re-pin requests. nouveau_bo_pin_locked() calls ttm_bo_pin() despite returning -EBUSY, leaving an unmatched pin that triggers a warning in ttm_bo_release(). Triggering requires access to the Nouveau driver; the published trace demonstrates a warning, not a crash or privilege escalation.
The record
- CVE
- CVE-2026-98511
- Published
- Oct 18, 2026
- Updated
- Oct 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 18, 2026CVE publishedPublication date reported by the CVE source.
- Oct 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.19
- Affected versionversion=ad76b3f7c7a0836e74ac0e316e03988ef3c43564 <189ffc7b6cad6390c0695031cb6c7c63472981e8
- Affected versionversion=ad76b3f7c7a0836e74ac0e316e03988ef3c43564 <19f5a5839b308697824ff46e6213a2b4cb677771
- Affected versionversion=ad76b3f7c7a0836e74ac0e316e03988ef3c43564 <5cb7109f0f5f1b47b172e2d5b868d4ce3ae687f8
- Affected versionversion=ad76b3f7c7a0836e74ac0e316e03988ef3c43564 <6a6870d3077faa501ca97760057ddca22b68418d
- Affected versionversion=ad76b3f7c7a0836e74ac0e316e03988ef3c43564 <73c7093e6cc1e6b181a79e16eccc4b8d4f34d8ee
- Affected versionversion=ad76b3f7c7a0836e74ac0e316e03988ef3c43564 <9924c1d64405be8d10b906368dfb1cfe0d0c6bf0
- Affected versionversion=ad76b3f7c7a0836e74ac0e316e03988ef3c43564 <a6e755acf85793a7b4d29ba27b5421af1087263f
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started