Linux Kernel: elan Driver Potential Double Free in elan_input_configured
CVE-2022-49508 Published on February 26, 2025
HID: elan: Fix potential double free in elan_input_configured
In the Linux kernel, the following vulnerability has been resolved:
HID: elan: Fix potential double free in elan_input_configured
'input' is a managed resource allocated with devm_input_allocate_device(),
so there is no need to call input_free_device() explicitly or
there will be a double free.
According to the doc of devm_input_allocate_device():
* Managed input devices do not need to be explicitly unregistered or
* freed as it will be done automatically when owner device unbinds from
* its driver (or binding fails).
Vulnerability Analysis
CVE-2022-49508 is exploitable with local system access, and requires small amount of user privileges. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to be very high.
Weakness Type
What is a Double-free Vulnerability?
The product calls free() twice on the same memory address, potentially leading to modification of unexpected memory locations. When a program calls free() twice with the same argument, the program's memory management data structures become corrupted. This corruption can cause the program to crash or, in some circumstances, cause two later calls to malloc() to return the same pointer. If malloc() returns the same value twice and the program later gives the attacker control over the data that is written into this doubly-allocated memory, the program becomes vulnerable to a buffer overflow attack.
CVE-2022-49508 has been classified to as a Double-free vulnerability or weakness.
Products Associated with CVE-2022-49508
stack.watch emails you whenever new vulnerabilities are published in Linux Kernel or Linux Kernel. Just hit a watch button to start following.
Affected Versions
Linux:- Version 9a6a4193d65b853020ef0e66cecdf9e64a863883 and below c92ec22a991778a096342cf1a917ae36c5c86a90 is affected.
- Version 9a6a4193d65b853020ef0e66cecdf9e64a863883 and below f1d4f19a796551edc6679a681ea1756b8c578c08 is affected.
- Version 9a6a4193d65b853020ef0e66cecdf9e64a863883 and below 6d0726725c7c560495f5ff364862a2cefea542e3 is affected.
- Version 9a6a4193d65b853020ef0e66cecdf9e64a863883 and below 24f9dfdaece9bd75bb8dbfdba83eddeefdf7dc47 is affected.
- Version 9a6a4193d65b853020ef0e66cecdf9e64a863883 and below 5291451851feeb66fd4bf0826710f482f3b1ab38 is affected.
- Version 9a6a4193d65b853020ef0e66cecdf9e64a863883 and below 8bb1716507ebf12d50bbf181764481de3b6bc7fd is affected.
- Version 9a6a4193d65b853020ef0e66cecdf9e64a863883 and below 1af20714fedad238362571620be0bd690ded05b6 is affected.
- Version 4.17 is affected.
- Before 4.17 is unaffected.
- Version 4.19.247, <= 4.19.* is unaffected.
- Version 5.4.198, <= 5.4.* is unaffected.
- Version 5.10.121, <= 5.10.* is unaffected.
- Version 5.15.46, <= 5.15.* is unaffected.
- Version 5.17.14, <= 5.17.* is unaffected.
- Version 5.18.3, <= 5.18.* is unaffected.
- Version 5.19, <= * is unaffected.
Exploit Probability
EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.