Kernel panic via unlocked CRTC event access
Published Feb 5, 2024 · Updated Aug 1, 2024
A race condition in the Linux kernel before 6.6-rc1 allows local users to trigger a kernel panic through Exynos DRM display teardown. exynos_drm_crtc_atomic_disable() tests crtc->state->event without event_lock, allowing another thread to clear it before drm_crtc_send_vblank_event() dereferences it. Low-privileged local access and an enabled Exynos DRM driver are required; successful exploitation interrupts the host without reported data disclosure or modification.
Summary
What happened
A race condition in the Linux kernel before 6.6-rc1 allows local users to trigger a kernel panic through Exynos DRM display teardown. exynos_drm_crtc_atomic_disable() tests crtc->state->event without event_lock, allowing another thread to clear it before drm_crtc_send_vblank_event() dereferences it. Low-privileged local access and an enabled Exynos DRM driver are required; successful exploitation interrupts the host without reported data disclosure or modification.
The record
- CVE
- CVE-2024-22386
- Published
- Feb 5, 2024
- Updated
- Aug 1, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-362, CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 5, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 2024Record 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=v4.11-rc1 <v6.6-rc1
What conditions does exploitation require?
What is affected?
Published CVSS scores
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