CVE-2026-31618

Kernel crash via zero framebuffer pixclock

Published Apr 24, 2026 · Updated Apr 24, 2026

Divide by zero in the Linux Kernel tdfxfb driver allows local users to crash the kernel through a crafted FBIOPUT_VSCREENINFO request. tdfxfb_check_var passes a user-controlled zero pixclock value to PICOS2KHZ, whose division by pixclock faults before the mode is rejected. The tdfxfb framebuffer device must be present and accessible; the documented impact is a kernel crash without confidentiality or integrity loss.

CVSS severity5.5
Medium
EPSS probability0.13%
Next 30 days · Sep 16, 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.

Book a demo

Summary

What happened

Divide by zero in the Linux Kernel tdfxfb driver allows local users to crash the kernel through a crafted FBIOPUT_VSCREENINFO request. tdfxfb_check_var passes a user-controlled zero pixclock value to PICOS2KHZ, whose division by pixclock faults before the mode is rejected. The tdfxfb framebuffer device must be present and accessible; the documented impact is a kernel crash without confidentiality or integrity loss.

The record

CVE
CVE-2026-31618
Published
Apr 24, 2026
Updated
Apr 24, 2026
Vendor
The Linux Kernel Organization
Product
Linux Kernel
Classifications
CWE-369, T1499.004
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Apr 24, 2026CVE publishedPublication date reported by the CVE source.
  2. Apr 24, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <53cb4e79a07124d2ebe502983c29800104080b47
  2. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <63dfb0b4741f46d65b667c4275132b3d1966acc8
  3. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6567d3e1aaadfebf44ce7dc9ea2630323cd4c736
  4. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fc386daa6846551a88d338ba9864fc2812cd9030

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linux Kernelversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <53cb4e79a07124d2ebe502983c29800104080b47; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <63dfb0b4741f46d65b667c4275132b3d1966acc8; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6567d3e1aaadfebf44ce7dc9ea2630323cd4c736; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fc386daa6846551a88d338ba9864fc2812cd9030

Published CVSS scores

5.5NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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.

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

No observations available

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

Weakness, pattern, technique

CWE-369Divide By Zero
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

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo