Kernel fault via unchecked framebuffer validation error
Published Jul 5, 2024 · Updated May 23, 2026
Divide-by-zero in the Linux kernel savage framebuffer driver allows attackers to trigger a kernel fault during device probing. savagefb_probe ignores the error returned by savagefb_check_var and continues with a zero pixclock value, which reaches a division operation. The Savage framebuffer driver must probe mode data with pixclock set to zero; the public record does not identify an attacker-controlled path, required privileges, or impact beyond service interruption.
Summary
What happened
Divide-by-zero in the Linux kernel savage framebuffer driver allows attackers to trigger a kernel fault during device probing. savagefb_probe ignores the error returned by savagefb_check_var and continues with a zero pixclock value, which reaches a division operation. The Savage framebuffer driver must probe mode data with pixclock set to zero; the public record does not identify an attacker-controlled path, required privileges, or impact beyond service interruption.
The record
- CVE
- CVE-2024-39475
- Published
- Jul 5, 2024
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-369
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 5, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=04e5eac8f3ab2ff52fa191c187a46d4fdbc1e288 <5f446859bfa46df0ffb34149499f48a2c2d8cd95
- Affected versionversion=04e5eac8f3ab2ff52fa191c187a46d4fdbc1e288 <6ad959b6703e2c4c5d7af03b4cfd5ff608036339
- Affected versionversion=070398d32c5f3ab0e890374904ad94551c76aec4 <edaa57480b876e8203b51df7c3d14a51ea6b09e3
- Affected versionversion=224453de8505aede1890f007be973925a3edf6a1 <be754cbd77eaf2932408a4e18532e4945274a5c7
- Affected versionversion=4.19.308 <4.19.316
- Affected versionversion=5.10.211 <5.10.219
- Affected versionversion=512ee6d6041e007ef5bf200c6e388e172a2c5b24 <32f92b0078ebf79dbe4827288e0acb50d89d3d5b
- Affected versionversion=5.15.150 <5.15.161
- Affected versionversion=5.4.270 <5.4.278
- Affected versionversion=6.1.80 <6.1.94
- Affected versionversion=6.6.19 <6.6.34
- Affected versionversion=6.7.7 <6.8
- Affected versionversion=6.8
- Affected versionversion=84dce0f6a4cc5b7bfd7242ef9290db8ac1dd77ff <86435f39c18967cdd937d7a49ba539cdea7fb547
- Affected versionversion=8c54acf33e5adaad6374bf3ec1e3aff0591cc8e1 <4b2c67e30b4e1d2ae19dba8b8e8f3b5fd3cf8089
- Affected versionversion=a9ca4e80d23474f90841251f4ac0d941fa337a01
- Affected versionversion=bc3c2e58d73b28b9a8789fca84778ee165a72d13 <b8385ff814ca4cb7e63789841e6ec2a14c73e1e8
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo