Kernel crash via zero framebuffer pixel clock
Published Jun 18, 2025 · Updated May 11, 2026
Divide-by-zero in the Linux kernel pm2fb driver allows local users to crash the kernel through a crafted framebuffer ioctl. pm2fb_check_var passes the user-controlled var->pixclock value to the PICOS2KHZ reciprocal calculation without first rejecting zero. Access to the pm2 framebuffer device and FBIOPUT_VSCREENINFO path is required, and a successful trigger interrupts host availability through a kernel crash.
Summary
What happened
Divide-by-zero in the Linux kernel pm2fb driver allows local users to crash the kernel through a crafted framebuffer ioctl. pm2fb_check_var passes the user-controlled var->pixclock value to the PICOS2KHZ reciprocal calculation without first rejecting zero. Access to the pm2 framebuffer device and FBIOPUT_VSCREENINFO path is required, and a successful trigger interrupts host availability through a kernel crash.
The record
- CVE
- CVE-2022-49978
- Published
- Jun 18, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-369, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0f1174f4972ea9fad6becf8881d71adca8e9ca91
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <19f953e7435644b81332dd632ba1b2d80b1e37af
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <34c3dea1189525cd533071ed5c176fc4ea8d982b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3ec326a6a0d4667585ca595f438c7293e5ced7c4
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7d9591b32a9092fc6391a316b56e8016c6181c3d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7f88cdfea8d7f4dbaf423d808241403b2bb945e4
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8fc778ee2fb2853f7a3531fa7273349640d8e4e9
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <cb4bb011a683532841344ca7f281b5e04389b4f8
- Affected versionversion=2.6.12
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