Kernel memory corruption via ULPI double free
Published May 1, 2026 · Updated May 1, 2026
Double free in the Linux kernel ULPI registration path allows local users to corrupt kernel memory when device registration fails. The ulpi_register() failure path invokes put_device(), whose ulpi_dev_release() callback frees the ULPI object, before ulpi_register_interface() calls kfree() on the same object. Reachability requires local low-privileged access and a device_register() failure in the ULPI path; the published record identifies no remote trigger.
Summary
What happened
Double free in the Linux kernel ULPI registration path allows local users to corrupt kernel memory when device registration fails. The ulpi_register() failure path invokes put_device(), whose ulpi_dev_release() callback frees the ULPI object, before ulpi_register_interface() calls kfree() on the same object. Reachability requires local low-privileged access and a device_register() failure in the ULPI path; the published record identifies no remote trigger.
The record
- CVE
- CVE-2026-31759
- Published
- May 1, 2026
- Updated
- May 1, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-415, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2026CVE publishedPublication date reported by the CVE source.
- May 1, 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=289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f <01af542392b5d41fd659d487015a71f627accce3
- Affected versionversion=289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f <272a9b26c336a295e4e209157fed809706c1b1f7
- Affected versionversion=289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f <2f70ba9dae13a190673cc3f9b4aad52179738f60
- Affected versionversion=289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f <38c28fe25611099230f0965c925499bfcf46a795
- Affected versionversion=289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f <8763f8317bb389aded32a32b08f6751cfff657d2
- Affected versionversion=289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f <a6e5461f076c2ef63159f18e5cdbd30b50f0bc15
- Affected versionversion=289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f <aaeae6533d77e6ed4def85baec01e2815ebbef61
- Affected versionversion=289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f <ee248e6e941e4f2e634df2bd43e5f1ef810ab6df
- Affected versionversion=4.2
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.
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