CVE-2026-31618: fbdev: tdfxfb: avoid divide-by-zero on FBIOPUT_VSCREENINFO
Published Apr 24, 2026
·Updated
fbdev: tdfxfb: avoid divide-by-zero on FBIOPUTVSCREENINFO
Affected Software
13 affected componentsFixes available
Linux Linux kernel
Microsoft azl3 kernel 6.6.134.1-2
Linux Linux kernel>=2.6.12.1<6.6.136
Linux Linux kernel>=6.7<6.12.83
Linux Linux kernel>=6.13<6.18.24
Linux Linux kernel>=6.19<6.19.14
Linux Linux kernel>=7.0<7.0.1
Linux Linux kernel=2.6.12
Linux Linux kernel=2.6.12-rc2
Linux Linux kernel=2.6.12-rc3
Linux Linux kernel=2.6.12-rc4
Linux Linux kernel=2.6.12-rc5
Microsoft azl3 kernel 6.6.134.1-2<6.6.137.1-1
6.6.137.1-1
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.137.1-1
Event History
Apr 24, 2026
CVE Published
via MITRE·02:42 PM
Data Sourced
via MITRE·02:42 PM
Description
Data Sourced
via NVD·03:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Apr 26, 2026
Data Sourced
via Microsoft·08:02 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:02 AM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2026-31618?
The severity of CVE-2026-31618 is classified as medium with a CVSS score of 5.5.
2
How do I fix CVE-2026-31618?
To fix CVE-2026-31618, ensure that you update to the latest version of the Linux kernel that includes the patch for this vulnerability.
3
What kind of vulnerability is CVE-2026-31618?
CVE-2026-31618 is a divide by zero vulnerability that can cause a denial of service.
4
Which software is affected by CVE-2026-31618?
CVE-2026-31618 affects the Linux kernel and Microsoft azl3 kernel 6.6.134.1-2.
5
What is the potential impact of CVE-2026-31618?
The potential impact of CVE-2026-31618 includes a denial of service condition caused by a divide by zero error.