Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 44 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-26778, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.25% · top 83% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 224453de8505aede1890f007be973925a3edf6a1
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 84dce0f6a4cc5b7bfd7242ef9290db8ac1dd77ff
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 512ee6d6041e007ef5bf200c6e388e172a2c5b24
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 8c54acf33e5adaad6374bf3ec1e3aff0591cc8e1
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 070398d32c5f3ab0e890374904ad94551c76aec4
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < bc3c2e58d73b28b9a8789fca84778ee165a72d13
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < a9ca4e80d23474f90841251f4ac0d941fa337a01
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 04e5eac8f3ab2ff52fa191c187a46d4fdbc1e288
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 4.19.308 – ≤ 4.19.*
    • unaffected 5.4.270 – ≤ 5.4.*
    • unaffected 5.10.211 – ≤ 5.10.*
    • unaffected 5.15.150 – ≤ 5.15.*
    • unaffected 6.1.80 – ≤ 6.1.*
    • unaffected 6.6.19 – ≤ 6.6.*
    • unaffected 6.7.7 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-26778 badge
[![CVE-2024-26778](https://cveledger.app/badge/CVE-2024-26778.svg)](https://cveledger.app/cve/CVE-2024-26778)

Record last updated .