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-39475fbdev: savage: Handle err return when savagefb_check_var failed

Description

In the Linux kernel, the following vulnerability has been resolved: fbdev: savage: Handle err return when savagefb_check_var failed The commit 04e5eac8f3ab("fbdev: savage: Error out if pixclock equals zero") checks the value of pixclock to avoid divide-by-zero error. However the function savagefb_probe doesn't handle the error return of savagefb_check_var. When pixclock is 0, it will cause divide-by-zero error.

Timeline

  1. ID reserved

    By Linux

  2. · 10 days later

    Published

  3. · 23 months 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-39475, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.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.23% · top 86% of all CVEs (16 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 224453de8505aede1890f007be973925a3edf6a1 – < be754cbd77eaf2932408a4e18532e4945274a5c7
    • affected 84dce0f6a4cc5b7bfd7242ef9290db8ac1dd77ff – < 86435f39c18967cdd937d7a49ba539cdea7fb547
    • affected 512ee6d6041e007ef5bf200c6e388e172a2c5b24 – < 32f92b0078ebf79dbe4827288e0acb50d89d3d5b
    • affected 8c54acf33e5adaad6374bf3ec1e3aff0591cc8e1 – < 4b2c67e30b4e1d2ae19dba8b8e8f3b5fd3cf8089
    • affected 070398d32c5f3ab0e890374904ad94551c76aec4 – < edaa57480b876e8203b51df7c3d14a51ea6b09e3
    • affected bc3c2e58d73b28b9a8789fca84778ee165a72d13 – < b8385ff814ca4cb7e63789841e6ec2a14c73e1e8
    • affected 04e5eac8f3ab2ff52fa191c187a46d4fdbc1e288 – < 5f446859bfa46df0ffb34149499f48a2c2d8cd95
    • affected 04e5eac8f3ab2ff52fa191c187a46d4fdbc1e288 – < 6ad959b6703e2c4c5d7af03b4cfd5ff608036339
    • affected a9ca4e80d23474f90841251f4ac0d941fa337a01
    • affected 4.19.308 – < 4.19.316
    • affected 5.4.270 – < 5.4.278
    • affected 5.10.211 – < 5.10.219
    • affected 5.15.150 – < 5.15.161
    • affected 6.1.80 – < 6.1.94
    • affected 6.6.19 – < 6.6.34
    • affected 6.7.7 – < 6.8
  • Linux · Linux

    • affected 6.8
    • unaffected < 6.8
    • unaffected 4.19.316 – ≤ 4.19.*
    • unaffected 5.4.278 – ≤ 5.4.*
    • unaffected 5.10.219 – ≤ 5.10.*
    • unaffected 5.15.161 – ≤ 5.15.*
    • unaffected 6.1.94 – ≤ 6.1.*
    • unaffected 6.6.34 – ≤ 6.6.*
    • unaffected 6.9.5 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .