Kernel memory corruption via unlocked MST state reset
Published Jan 11, 2025 · Updated May 23, 2026
Memory corruption in the Linux kernel's DisplayPort MST code allows local users to corrupt kernel memory during topology removal. The parser reads shared up_req_recv or down_rep_recv reception state without holding the topology-manager lock while another thread can reset that state. Reachability requires local low-privileged access and DisplayPort Multi-Stream Transport activity timed with topology removal; the bounded result is corruption in the kernel-side message parser.
Summary
What happened
Memory corruption in the Linux kernel's DisplayPort MST code allows local users to corrupt kernel memory during topology removal. The parser reads shared up_req_recv or down_rep_recv reception state without holding the topology-manager lock while another thread can reset that state. Reachability requires local low-privileged access and DisplayPort Multi-Stream Transport activity timed with topology removal; the bounded result is corruption in the kernel-side message parser.
The record
- CVE
- CVE-2024-57876
- Published
- Jan 11, 2025
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-787, CWE-362
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 11, 2025CVE 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=1d082618bbf3b6755b8cc68c0a8122af2842d593 <a6fa67d26de385c3c7a23c1e109a0e23bfda4ec7
- Affected versionversion=1d082618bbf3b6755b8cc68c0a8122af2842d593 <be826b4451fd187a7c0b04be4f8243d5df6e0450
- Affected versionversion=1d082618bbf3b6755b8cc68c0a8122af2842d593 <d834d20d2e86c52ed5cab41763fa61e6071680ef
- Affected versionversion=5.10.173 <5.11
- Affected versionversion=5.15.100 <5.16
- Affected versionversion=6.1.18 <6.1.120
- Affected versionversion=6.2.5 <6.3
- Affected versionversion=6.3
- Affected versionversion=a579ed4613b5a64074963988ad481e43cf3b917b
- Affected versionversion=b30fcedeba643ca16eaa6212c1245598b7cd830d <94b33b2d7640e807869451384eb88321dd0ffbd4
- Affected versionversion=db35e49413a4d03ea0c003598803e49956f59324
- Affected versionversion=ee4a4282d78d96e07e714c28ca54679713fa2157
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