Kernel crash via unsynchronized DisplayPort partner removal
Published May 29, 2025 · Updated May 11, 2026
A NULL pointer dereference in affected Linux kernels allows local users to crash the kernel during UCSI DisplayPort partner removal. ucsi_displayport_remove_partner clears partner state without synchronously canceling dp->work, allowing queued work to access the removed partner. Triggering requires high local privileges and UCSI DisplayPort-capable hardware during partner teardown; the bounded impact is a kernel crash.
Summary
What happened
A NULL pointer dereference in affected Linux kernels allows local users to crash the kernel during UCSI DisplayPort partner removal. ucsi_displayport_remove_partner clears partner state without synchronously canceling dp->work, allowing queued work to access the removed partner. Triggering requires high local privileges and UCSI DisplayPort-capable hardware during partner teardown; the bounded impact is a kernel crash.
The record
- CVE
- CVE-2025-37994
- Published
- May 29, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 29, 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=5.2
- Affected versionversion=af8622f6a585d8d82b11cd7987e082861fd0edd3 <076ab0631ed4928905736f1701e25f1e722bc086
- Affected versionversion=af8622f6a585d8d82b11cd7987e082861fd0edd3 <14f298c52188c34acde9760bf5abc669c5c36fdb
- Affected versionversion=af8622f6a585d8d82b11cd7987e082861fd0edd3 <312d79669e71283d05c05cc49a1a31e59e3d9e0e
- Affected versionversion=af8622f6a585d8d82b11cd7987e082861fd0edd3 <5ad298d6d4aebe1229adba6427e417e89a5208d8
- Affected versionversion=af8622f6a585d8d82b11cd7987e082861fd0edd3 <7804c4d63edfdd5105926cc291e806e8f4ce01b5
- Affected versionversion=af8622f6a585d8d82b11cd7987e082861fd0edd3 <9dda1e2a666a8a32ce0f153b5dee05c7351f1020
- Affected versionversion=af8622f6a585d8d82b11cd7987e082861fd0edd3 <a9931f1b52b2d0bf3952e003fd5901ea7eb851ed
- Affected versionversion=af8622f6a585d8d82b11cd7987e082861fd0edd3 <e9b63faf5c97deb43fc39a52edbc39d626cc14bf
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