Kernel crash via unchecked CRTC state error
Published Jan 8, 2025 · Updated May 11, 2026
Improper error handling in the DRM/STI cursor code allows local users to crash Linux through a failed atomic CRTC state lookup. The sti_cursor_atomic_check function dereferences an error pointer returned by drm_atomic_get_crtc_state instead of testing it with IS_ERR. Exploitation requires local low-privileged access to a system using the DRM/STI cursor path; confidentiality and integrity are unaffected.
Summary
What happened
Improper error handling in the DRM/STI cursor code allows local users to crash Linux through a failed atomic CRTC state lookup. The sti_cursor_atomic_check function dereferences an error pointer returned by drm_atomic_get_crtc_state instead of testing it with IS_ERR. Exploitation requires local low-privileged access to a system using the DRM/STI cursor path; confidentiality and integrity are unaffected.
The record
- CVE
- CVE-2024-56776
- Published
- Jan 8, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-754, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 8, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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=4.6
- Affected versionversion=dd86dc2f9ae1102f46115be1f1422265c15540f1 <40725c5fabee804fecce41d4d5c5bae80c45e1c4
- Affected versionversion=dd86dc2f9ae1102f46115be1f1422265c15540f1 <831214f77037de02afc287eae93ce97f218d8c04
- Affected versionversion=dd86dc2f9ae1102f46115be1f1422265c15540f1 <8ab73ac97c0fa528f66eeccd9bb53eb6eb7d20dc
- Affected versionversion=dd86dc2f9ae1102f46115be1f1422265c15540f1 <e98ff67f5a68114804607de549c2350d27628fc7
- Affected versionversion=dd86dc2f9ae1102f46115be1f1422265c15540f1 <f67786293193cf01ebcc6fdbcbd1587b24f52679
What conditions does exploitation require?
What is affected?
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