Skip to main content
VulnerabilityPublished Updated

CVE-2025-38312: Linux kernel · fbdev: core: fbcvt: avoid division by 0 in fb_cvt_hperiod()

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in b235393b9f43ff86a38ca2bde6372312ea215dc5 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:19 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in b235393b9f43ff86a38ca2bde6372312ea215dc5, ab91647acdf43b984824776559a452212eaeb21a, 54947530663edcbaaee1314c01fdd8c72861b124 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 96fe6a2109db29cd15b90a093c16e6cb4b19371a, < b235393b9f43ff86a38ca2bde6372312ea215dc5
Fixed in
  • b235393b9f43ff86a38ca2bde6372312ea215dc5
LinuxLinuxAffected
  • ≥ 96fe6a2109db29cd15b90a093c16e6cb4b19371a, < ab91647acdf43b984824776559a452212eaeb21a
Fixed in
  • ab91647acdf43b984824776559a452212eaeb21a
LinuxLinuxAffected
  • ≥ 96fe6a2109db29cd15b90a093c16e6cb4b19371a, < 54947530663edcbaaee1314c01fdd8c72861b124
Fixed in
  • 54947530663edcbaaee1314c01fdd8c72861b124
LinuxLinuxAffected
  • ≥ 96fe6a2109db29cd15b90a093c16e6cb4b19371a, < 53784073cbad18f75583fd3da9ffdfc4d1f05405
Fixed in
  • 53784073cbad18f75583fd3da9ffdfc4d1f05405
LinuxLinuxAffected
  • ≥ 96fe6a2109db29cd15b90a093c16e6cb4b19371a, < 9027ce4c037b566b658b8939a76326b7125e3627
Fixed in
  • 9027ce4c037b566b658b8939a76326b7125e3627
LinuxLinuxAffected
  • ≥ 96fe6a2109db29cd15b90a093c16e6cb4b19371a, < 610f247f2772e4f92b63442125a1b7ade79898d8
Fixed in
  • 610f247f2772e4f92b63442125a1b7ade79898d8

Description

In the Linux kernel, the following vulnerability has been resolved: fbdev: core: fbcvt: avoid division by 0 in fb_cvt_hperiod() In fb_find_mode_cvt(), iff mode->refresh somehow happens to be 0x80000000, cvt.f_refresh will become 0 when multiplying it by 2 due to overflow. It's then passed to fb_cvt_hperiod(), where it's used as a divider -- division by 0 will result in kernel oops. Add a sanity check for cvt.f_refresh to avoid such overflow... Found by Linux Verification Center (linuxtesting.org) with the Svace static analysis tool.

References

Community reviews

Loading reviews…