LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26778: fbdev: savage: Error out if pixclock equals zero

In the Linux kernel, the following vulnerability has been resolved: fbdev: savage: Error out if pixclock equals zero The userspace program could pass any values to the driver through ioctl() interface. If the driver doesn't check the value of pixclock, it may cause divide-by-zero error. Although pixclock is checked in savagefb_decode_var(), but it is not checked properly in savagefb_probe(). Fix this by checking whether pixclock is zero in the function savagefb_check_var() before info->var.pixclock is used as the divisor. This is similar to CVE-2022-3061 in i740fb which was fixed by commit 15cf0b8.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-26778 is a Linux kernel bug in the Savage framebuffer driver. A local userspace program could provide a zero pixel-clock value through an ioctl path, leading the kernel driver to divide by zero. The public sources describe a kernel stability issue, not a confirmed remote compromise path.

Executive priority

Treat this as routine but real kernel maintenance. Prioritize systems with local multi-user access or legacy framebuffer hardware support. It is not KEV-listed and no active exploitation is cited in the supplied sources.

Technical view

The issue is in fbdev savage handling of pixclock. The driver checked pixclock in one path, but not properly before info->var.pixclock was used as a divisor in savagefb_probe/check handling. Stable Linux commits add a zero check in savagefb_check_var().

Likely exposure

Exposure is likely limited to Linux systems running affected kernels where the savage framebuffer driver is present and reachable by local users through framebuffer ioctl interfaces. The source bundle does not show cloud, network, container, or browser-facing exposure.

Exploitation context

The CVE source says a userspace program could pass arbitrary values through ioctl and trigger divide-by-zero. KEV is false, and the supplied sources do not report active exploitation or public weaponization.

Researcher notes

Evidence supports a local ioctl-triggered divide-by-zero in the Linux savage fbdev driver. Impact details beyond kernel fault or denial-of-service are not established in the supplied bundle. No CVSS, CWE, exploit status, or complete product-specific package matrix is provided.

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable commits.
  • Use Debian LTS kernel updates where the Debian advisories apply.
  • Check your distribution vendor advisory for exact fixed package versions.
  • If not needed, follow vendor guidance to avoid loading the savage framebuffer driver.

Validation and detection

  • Inventory kernels against the affected Linux version data in the CVE record.
  • Check whether the savage framebuffer driver is built, installed, or loaded.
  • Confirm updated kernels include one of the referenced stable fixes.
  • Review Debian LTS advisory applicability for Debian-managed systems.
Prepared
Confidence
high
Sources
12

Public sources used

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-26778 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
2ADP providers
11Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2unaffected
LinuxLinux2.6.12, 0, 4.19.308, 5.4.270, 5.10.211, 5.15.150, 6.1.80, 6.6.19, 6.7.7, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.