Kernel crash via zero OCC sample counter
Published May 1, 2026 · Updated May 1, 2026
Divide-by-zero in the OCC hwmon driver for Linux Kernel allows local users to crash the kernel by reading an empty power sample set. The occ_show_power_1() case 1 path divides the power accumulator by update_tag without checking whether the sample counter is zero. Exploitation requires an included but not yet updated OCC sensor block, such as during early boot, and causes an availability-only kernel crash.
Summary
What happened
Divide-by-zero in the OCC hwmon driver for Linux Kernel allows local users to crash the kernel by reading an empty power sample set. The occ_show_power_1() case 1 path divides the power accumulator by update_tag without checking whether the sample counter is zero. Exploitation requires an included but not yet updated OCC sensor block, such as during early boot, and causes an availability-only kernel crash.
The record
- CVE
- CVE-2026-31770
- Published
- May 1, 2026
- Updated
- May 1, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-369, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2026CVE publishedPublication date reported by the CVE source.
- May 1, 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=5.0
- Affected versionversion=c10e753d43ebd1d17e1c62bcee20c6124c2c7cca <243d55bd3f08cb15eee9d63f4716d4d4cdd760f5
- Affected versionversion=c10e753d43ebd1d17e1c62bcee20c6124c2c7cca <2502684b9e835de9a992ec47c3e6c6faabe3858d
- Affected versionversion=c10e753d43ebd1d17e1c62bcee20c6124c2c7cca <37ae8fadc74ed68e5bc364ffd17746d88e449ae3
- Affected versionversion=c10e753d43ebd1d17e1c62bcee20c6124c2c7cca <39e2a5bf970402a8530a319cf06122e216ba57b8
- Affected versionversion=c10e753d43ebd1d17e1c62bcee20c6124c2c7cca <53e6175756b8c474b6247bbcea0aad3d68357475
- Affected versionversion=c10e753d43ebd1d17e1c62bcee20c6124c2c7cca <7b89ce0c98bf3015f493ca4285b2d1056cd8c733
- Affected versionversion=c10e753d43ebd1d17e1c62bcee20c6124c2c7cca <bbbefc48f6617cfb738dcff7f44beb50b5dfeb38
- Affected versionversion=c10e753d43ebd1d17e1c62bcee20c6124c2c7cca <c7d3712362c8ab8f82f441b649d9e446e7b9aa9d
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