Local information disclosure via dangling device-name pointer
Published Apr 1, 2026 · Updated Apr 1, 2026
Use-after-free in libinput 1.30.0 through 1.30.2 and 1.31.0 allows local users to cause indirect process-memory disclosure through system logs. A Lua plugin's __gc() callback leaves a dangling device-name pointer, so later logging reads that pointer after its storage is reused. Exploitation requires placing a plugin in a loaded plugin directory and having Lua plugins enabled or loaded by the compositor.
Summary
What happened
Use-after-free in libinput 1.30.0 through 1.30.2 and 1.31.0 allows local users to cause indirect process-memory disclosure through system logs. A Lua plugin's __gc() callback leaves a dangling device-name pointer, so later logging reads that pointer after its storage is reused. Exploitation requires placing a plugin in a loaded plugin directory and having Lua plugins enabled or loaded by the compositor.
The record
- CVE
- CVE-2026-35094
- Published
- Apr 1, 2026
- Updated
- Apr 1, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux 10
- Classifications
- CWE-825, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 1, 2026CVE publishedPublication date reported by the CVE source.
- Apr 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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