Local kernel crash via framebuffer read
Published Jul 13, 2022 · Updated Apr 23, 2025
Out-of-bounds memory access in the Linux kernel before 5.18-rc1 allows local users to crash the kernel through a framebuffer read. In smtcfb_read(), open-coded endian fixup logic applies a pointer post-decrement inside fb_readl(), so a three-byte read advances outside the mapped framebuffer. The flaw is reachable when the SM712 framebuffer driver is in use and a local user can read its framebuffer device; exploitation causes a kernel page fault and service interruption.
Summary
What happened
Out-of-bounds memory access in the Linux kernel before 5.18-rc1 allows local users to crash the kernel through a framebuffer read. In smtcfb_read(), open-coded endian fixup logic applies a pointer post-decrement inside fb_readl(), so a three-byte read advances outside the mapped framebuffer. The flaw is reachable when the SM712 framebuffer driver is in use and a local user can read its framebuffer device; exploitation causes a kernel page fault and service interruption.
The record
- CVE
- CVE-2022-2380
- Published
- Jul 13, 2022
- Updated
- Apr 23, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-125, CWE-787
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 13, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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=Linux kernel 5.18-rc1
What conditions does exploitation require?
What is affected?
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