System crash via random MMIO address read
Published May 28, 2026 · Updated May 28, 2026
Invalid address access in Linux Kernel LoongArch PCI setup allows local users to crash the system during device discovery. loongson_gpu_fixup_dma_hang() derives a device from pdev->devfn plus one, handles only DC2 and DC3, and otherwise passes an unset crtc_reg address to readl(). The panic requires a LoongArch system with the relevant discrete-GPU PCI topology and occurs while the kernel scans devices during startup.
Summary
What happened
Invalid address access in Linux Kernel LoongArch PCI setup allows local users to crash the system during device discovery. loongson_gpu_fixup_dma_hang() derives a device from pdev->devfn plus one, handles only DC2 and DC3, and otherwise passes an unset crtc_reg address to readl(). The panic requires a LoongArch system with the relevant discrete-GPU PCI topology and occurs while the kernel scans devices during startup.
The record
- CVE
- CVE-2026-46156
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-667, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 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=151ba1721ac50765e16d293256389ef14553b46e <2cb19b06c09983727573bbe7d7430cbad480a714
- Affected versionversion=3446dd359ba9a6ce5a1ca389c0d48c434d3cc915
- Affected versionversion=6.1.168 <6.2
- Affected versionversion=6.12.80 <6.12.88
- Affected versionversion=6.18.21 <6.18.30
- Affected versionversion=6.19.11 <6.20
- Affected versionversion=6.6.131 <6.6.140
- Affected versionversion=7.0
- Affected versionversion=70fb63c5d36cc02eaf336b87ac6a82e657f832a4 <9e1aed63a5552958ef2a9bfd699a3f990e52a77f
- Affected versionversion=95db0c9f526d583634cddb2e5914718570fbac87 <81fef1c278436e6bd68ee4ca05a0acb96e256561
- Affected versionversion=95db0c9f526d583634cddb2e5914718570fbac87 <8dfa2f8780e486d05b9a0ffce70b8f5fbd62053e
- Affected versionversion=a31da4d5d1fc29d92d2410c60e1ca298b02a6528
- Affected versionversion=f458dceaa6a35f89180ebd14484983d8e79ecd10 <07d190e4ec689d6478f7f5e36099fb9bf457e7c5
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo