CVE-2022-49508: 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).
Security readout for executives and security teams
Plain-English summary
This Linux kernel flaw is a double-free bug in the ELAN HID input driver path. A local, low-privileged user could potentially trigger memory corruption with high confidentiality, integrity, and availability impact. No provided source shows active exploitation.
Executive priority
Treat as high priority for Linux patch management, but not an emergency solely from the provided evidence. The risk is local privilege-based kernel impact, so prioritize exposed multi-user and endpoint fleets first.
Technical view
CVE-2022-49508 fixes an unnecessary input_free_device() call after devm_input_allocate_device() allocated a managed input device. The managed resource is automatically freed during driver unbind or binding failure, so explicit freeing can cause CWE-415 double free in elan_input_configured.
Likely exposure
Exposure is most likely on Linux systems running the affected kernel versions or commit lineage listed in the CVE, especially where the HID ELAN driver path is present. Distribution backports may change apparent version status, so validate against vendor kernel advisories and referenced stable commits.
Exploitation context
The CVSS vector is local, low complexity, low privileges, and no user interaction. The provided bundle marks KEV false and gives no evidence of exploitation in the wild, exploit tooling, or remote attack paths.
Researcher notes
The source evidence identifies the bug class, affected Linux kernel entries, CVSS 7.8, and stable kernel references. It does not provide proof-of-concept details, exploitation telemetry, indicators of compromise, or distro-specific fixed package versions.
Mitigation direction
Update to a distribution kernel containing the referenced upstream stable fix or vendor backport.
Prioritize shared workstations, developer endpoints, kiosks, and multi-user Linux systems.
Check Linux distribution advisories before assuming upstream version numbers map directly to exposure.
If immediate patching is blocked, reduce local user access on affected systems.
Validation and detection
Inventory Linux kernel versions across endpoints, servers, and appliances.
Confirm whether kernels include one of the referenced stable commits or an equivalent vendor backport.
Identify systems where HID ELAN driver support is enabled or relevant hardware is present.
Track remediation through normal vulnerability management evidence, including package version and reboot status.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-415: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
8Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.