high CVSS 7.8

CVE-2022-49508·Kernel vulnerability

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).

Severity
high
Software
Kernel
Fixed in
5.18.3
Published
2025-02-26

Affected versions

From: 5.18

Until: 5.18.3

Fixed in: 5.18.3

How to fix this CVE

Update your Linux kernel to version 5.18.3 or later to resolve a double-free vulnerability in the ELAN HID input device driver. This flaw occurs when the kernel incorrectly attempts to free an input device that is already managed by the kernel's device resource management system, potentially causing system instability or a denial of service. Ensure your system receives the latest kernel updates through your distribution's package manager.

sudo dnf update kernel

Defensia detects this vulnerability

How to check if you are affected

  1. Step 1: Check your current kernel version with `uname -r` and compare against 5.18.3
  2. Step 2: Verify if ELAN HID device is present on your system by running `lsusb | grep -i elan` or `lsmod | grep elan`
  3. Step 3: Search system logs for HID-related errors or double-free warnings: `grep -i 'elan\|hid.*error\|double free' /var/log/kern.log /var/log/messages`
  4. Step 4: After kernel upgrade, reboot and confirm new version with `uname -r` to verify the fix is active

FAQ

What is CVE-2022-49508?

This vulnerability is a double-free memory error in the ELAN HID input device driver within the Linux kernel. When an input device configured by the ELAN driver is released, the kernel attempts to free memory that was already automatically managed by the kernel's device resource manager, leading to memory corruption.

Is CVE-2022-49508 being actively exploited?

No, according to CISA data, this vulnerability is not actively exploited in the wild and no public exploits are currently available. However, it should still be patched promptly as a local privilege escalation vector.

What versions of Kernel are affected by CVE-2022-49508?

Linux kernel versions 5.18 through 5.18.2 are vulnerable. The vulnerability was resolved in kernel version 5.18.3 and later.

How do I check if my server is vulnerable to CVE-2022-49508?

Run `uname -r` to display your kernel version. If it shows 5.18.0, 5.18.1, or 5.18.2, and an ELAN HID device is present (checked via `lsusb | grep -i elan`), your system is vulnerable.

Does Defensia detect CVE-2022-49508?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2022-49508 will appear in your dashboard with remediation steps.

Related Kernel CVEs

CVE-2024-42256CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: cifs: Fix server re-repick on subrequest retry When a subrequest is marked for needing retry, netfs will call cifs_prepare_write() which will make cifs repick the server for the op before renegotiating credits; it then calls cifs_issue_write() which invokes smb2_async_writev() - which re-repicks the server. If a different server is then selected, this causes the increment of server->in_flight to happen against one record and the decrement to happen against another, leading to misaccounting. Fix this by just removing the repick code in smb2_async_writev(). As this is only called from netfslib-driven code, cifs_prepare_write() should always have been called first, and so server should never be NULL and the preparatory step is repeated in the event that we do a retry. The problem manifests as a warning looking something like: WARNING: CPU: 4 PID: 72896 at fs/smb/client/smb2ops.c:97 smb2_add_credits+0x3f0/0x9e0 [cifs] ... RIP: 0010:smb2_add_credits+0x3f0/0x9e0 [cifs] ... smb2_writev_callback+0x334/0x560 [cifs] cifs_demultiplex_thread+0x77a/0x11b0 [cifs] kthread+0x187/0x1d0 ret_from_fork+0x34/0x60 ret_from_fork_asm+0x1a/0x30 Which may be triggered by a number of different xfstests running against an Azure server in multichannel mode. generic/249 seems the most repeatable, but generic/215, generic/249 and generic/308 may also show it.
CVE-2024-36031CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: keys: Fix overwrite of key expiration on instantiation The expiry time of a key is unconditionally overwritten during instantiation, defaulting to turn it permanent. This causes a problem for DNS resolution as the expiration set by user-space is overwritten to TIME64_MAX, disabling further DNS updates. Fix this by restoring the condition that key_set_expiry is only called when the pre-parser sets a specific expiry.
CVE-2024-38612CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ipv6: sr: fix invalid unregister error path The error path of seg6_init() is wrong in case CONFIG_IPV6_SEG6_LWTUNNEL is not defined. In that case if seg6_hmac_init() fails, the genl_unregister_family() isn't called. This issue exist since commit 46738b1317e1 ("ipv6: sr: add option to control lwtunnel support"), and commit 5559cea2d5aa ("ipv6: sr: fix possible use-after-free and null-ptr-deref") replaced unregister_pernet_subsys() with genl_unregister_family() in this error path.
CVE-2024-38623CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Use variable length array instead of fixed size Should fix smatch warning: ntfs_set_label() error: __builtin_memcpy() 'uni->name' too small (20 vs 256)
CVE-2021-47548CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in hns_dsaf_ge_srst_by_port() The if statement: if (port >= DSAF_GE_NUM) return; limits the value of port less than DSAF_GE_NUM (i.e., 8). However, if the value of port is 6 or 7, an array overflow could occur: port_rst_off = dsaf_dev->mac_cb[port]->port_rst_off; because the length of dsaf_dev->mac_cb is DSAF_MAX_PORT_NUM (i.e., 6). To fix this possible array overflow, we first check port and if it is greater than or equal to DSAF_MAX_PORT_NUM, the function returns.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2022-49508. Free for 1 server.

Get started free