CVE-2024-35922: fbmon: prevent division by zero in fb_videomode_from_videomode()
In the Linux kernel, the following vulnerability has been resolved:
fbmon: prevent division by zero in fb_videomode_from_videomode()
The expression htotal * vtotal can have a zero value on
overflow. It is necessary to prevent division by zero like in
fb_var_to_videomode().
Found by Linux Verification Center (linuxtesting.org) with Svace.
Security readout for executives and security teams
Plain-English summary
CVE-2024-35922 is a Linux kernel bug in framebuffer monitor video-mode conversion. Certain display mode calculations can produce zero and trigger a division by zero. The sources do not provide CVSS, confirmed exploitation, or detailed impact beyond kernel stability risk, so urgency depends on whether affected kernels are deployed.
Executive priority
Track this as a kernel maintenance item, not an emergency based on current evidence. Patch affected systems through normal security update processes, with faster handling for critical Linux infrastructure or vendor appliances where kernel updates lag.
Technical view
The issue is in fb_videomode_from_videomode() in fbmon. The CVE record says htotal * vtotal may become zero on overflow, so later division must be guarded, matching existing handling in fb_var_to_videomode(). Stable kernel commits backport the fix across maintained branches.
Likely exposure
Exposure is likely limited to systems running affected Linux kernel versions with framebuffer video-mode handling reachable in their workload. The bundle lists Linux kernel versions from 3.9 through fixed stable releases as affected, but does not identify specific distributions beyond Debian LTS advisories or Siemens product context.
Exploitation context
The bundle marks KEV as false and provides no cited evidence of active exploitation or public exploit use. The bug was found by Linux Verification Center with Svace, suggesting a discovered code flaw rather than reported exploitation.
Researcher notes
Key uncertainty is impact. The record describes a division-by-zero prevention fix but provides no CVSS, CWE, crash path, privilege context, or attacker control details. Avoid assuming remote exploitability; validate by kernel version, downstream vendor advisory, and presence of the relevant fbmon fix.
Mitigation direction
Update affected Linux kernels to vendor-provided fixed stable releases.
Check Debian LTS advisories if using Debian-based long-term support systems.
Review Siemens guidance where Siemens products or appliances are in scope.
Prioritize internet-facing or high-availability Linux systems if affected.
If no vendor package is available, monitor vendor kernel advisories.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and embedded systems.
Confirm whether deployed kernels include one of the referenced stable commits.
Check distribution security advisories for patched package versions.
Validate that Debian LTS systems received the relevant kernel updates.
Record unsupported or custom kernels for separate remediation tracking.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-35922 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.