CVE-2026-98522

Kernel crash via discarded GPU mapping errors

Published Oct 18, 2026 · Updated Oct 18, 2026

Error handling in Linux's PowerVR driver allows local users to crash the kernel via failed GPU virtual-memory mappings. In pvr_mmu_map_sgl(), cleanup overwrites the original mapping error with its own return value, letting pvr_mmu_map() continue into a NULL-pointer dereference. Reaching this path requires access to the affected GPU driver and a mapping failure; the published trace establishes a kernel crash, not code execution.

CVSS severityUnavailable
Unscored
EPSS probability0.21%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Error handling in Linux's PowerVR driver allows local users to crash the kernel via failed GPU virtual-memory mappings. In pvr_mmu_map_sgl(), cleanup overwrites the original mapping error with its own return value, letting pvr_mmu_map() continue into a NULL-pointer dereference. Reaching this path requires access to the affected GPU driver and a mapping failure; the published trace establishes a kernel crash, not code execution.

The record

CVE
CVE-2026-98522
Published
Oct 18, 2026
Updated
Oct 18, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1499.004
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Oct 18, 2026CVE publishedPublication date reported by the CVE source.
  2. 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.

  1. Affected versionversion=6.8
  2. Affected versionversion=ff5f643de0bf27874c4033cd57a0bd034b5c7d11 <13c7ae1d92ceea18d55612fa9431ca5ac77025f5
  3. Affected versionversion=ff5f643de0bf27874c4033cd57a0bd034b5c7d11 <7b824c293a6b56de8285a97984c507cba56bc4c4
  4. Affected versionversion=ff5f643de0bf27874c4033cd57a0bd034b5c7d11 <afe5b4d66d45b278ecd0e3d6889fb208ce2e5339
  5. Affected versionversion=ff5f643de0bf27874c4033cd57a0bd034b5c7d11 <d30ea2747164992f5e720f6f53695d422bdc0346

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=6.8; version=ff5f643de0bf27874c4033cd57a0bd034b5c7d11 <13c7ae1d92ceea18d55612fa9431ca5ac77025f5; version=ff5f643de0bf27874c4033cd57a0bd034b5c7d11 <7b824c293a6b56de8285a97984c507cba56bc4c4; version=ff5f643de0bf27874c4033cd57a0bd034b5c7d11 <afe5b4d66d45b278ecd0e3d6889fb208ce2e5339; version=ff5f643de0bf27874c4033cd57a0bd034b5c7d11 <d30ea2747164992f5e720f6f53695d422bdc0346

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1499.004Application or System Exploitation

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