A vulnerability classified as problematic was found in libinput . This vulnerability affects unknown code. Executing a manipulation can lead to expired pointer dereference. This vulnerability is handled as CVE-2026-35094 . It is possible to launch the attack on the local host. There is not any exploit available.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-354677 · CVE-2026-35094 · GCVE-0-2026-35094
LIBINPUT EXPIRED POINTER DEREFERENCE
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
3.3 $0-$5k 1.09+
Summaryinfo
A vulnerability, which was classified as problematic, has been found in libinput. This issue affects some unknown processing. The manipulation leads to expired pointer dereference. This vulnerability is uniquely identified as CVE-2026-35094. Local access is required to approach this attack. No exploit exists.
Detailsinfo
A vulnerability was found in libinput (affected version unknown) and classified as problematic. This issue affects an unknown functionality. The manipulation with an unknown input leads to a expired pointer dereference vulnerability. Using CWE to declare the problem leads to CWE-825. The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid. Impacted is confidentiality. The summary by CVE is:
A flaw was found in libinput. An attacker capable of deploying a Lua plugin file in specific system directories can exploit a dangling pointer vulnerability. This occurs when a garbage collection cleanup function is called, leaving a pointer that can then be printed to system logs. This could potentially expose sensitive data if the memory location is re-used, leading to information disclosure. For this exploit to work, Lua plugins must be enabled in libinput and loaded by the compositor.
The advisory is shared at access.redhat.com. The identification of this vulnerability is CVE-2026-35094 since 04/01/2026. The exploitation is known to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Productinfo
Name
libinput
CPE 2.3info
🔒
CPE 2.2info
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 3.3
VulDB Meta Temp Score: 3.3
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 3.3
CNA Vector (redhat): 🔒
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Expired pointer dereference
CWE: CWE-825
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: no mitigation known
Status: 🔍
0-Day Time: 🔒
Timelineinfo
04/01/2026 Advisory disclosed
04/01/2026 +0 days CVE reserved
04/01/2026 +0 days VulDB entry created
04/01/2026 +0 days VulDB entry last update
Sourcesinfo
Advisory: access.redhat.com
Status: Not defined
CVE: CVE-2026-35094 (🔒)
GCVE (CVE): GCVE-0-2026-35094
GCVE (VulDB): GCVE-100-354677
Entryinfo
Created: 04/01/2026 17:01
Changes: 04/01/2026 17:01 (58)
Complete: 🔍
Cache ID: 99:9E0:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸