high CVSS 7.8

CVE-2019-25162·Kernel vulnerability

In the Linux kernel, the following vulnerability has been resolved: i2c: Fix a potential use after free Free the adap structure only after we are done using it. This patch just moves the put_device() down a bit to avoid the use after free. [wsa: added comment to the code, added Fixes tag]

Severity
high
Software
Kernel
Fixed in
5.19.2
Published
2024-02-26

Affected versions

From: 5.19.0

Until: 5.19.2

Fixed in: 5.19.2

How to fix this CVE

Update your Linux kernel to version 5.19.2 or later to resolve a use-after-free vulnerability in the i2c subsystem that could allow local privilege escalation. The i2c adapter structure was being freed prematurely while still in use, creating a window for memory corruption. Apply the kernel update immediately on all affected systems.

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 the affected range 5.19.0-5.19.2
  2. Step 2: Verify i2c device exposure by running `lsmod | grep i2c` to confirm the i2c modules are loaded on your system
  3. Step 3: Search kernel logs for i2c-related crashes or memory faults using `sudo dmesg | grep -i 'i2c\|use.after.free\|UAF'`
  4. Step 4: After patching, reboot the system with `sudo reboot` and confirm the new kernel version with `uname -r` to ensure 5.19.2 or later is running

FAQ

What is CVE-2019-25162?

This is a use-after-free vulnerability in the Linux kernel's i2c (Inter-Integrated Circuit) bus driver where the adapter device structure was being freed while still being referenced by other code paths, potentially allowing local attackers with low privileges to cause a denial of service or gain elevated privileges.

Is CVE-2019-25162 being actively exploited?

No, according to CISA's Known Exploited Vulnerabilities catalog, this vulnerability is not currently being actively exploited in the wild, though the high CVSS score warrants prompt patching.

What versions of Kernel are affected by CVE-2019-25162?

Linux kernel versions 5.19.0, 5.19.1, and 5.19.2-rc versions are affected. The vulnerability was patched in 5.19.2 release.

How do I check if my server is vulnerable to CVE-2019-25162?

Run `uname -r` to display your kernel version. If the output shows 5.19.0 or 5.19.1, your system is vulnerable and requires an immediate kernel update to 5.19.2 or newer.

Does Defensia detect CVE-2019-25162?

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-2019-25162 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-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-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-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.
CVE-2022-48716CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ASoC: codecs: wcd938x: fix incorrect used of portid Mixer controls have the channel id in mixer->reg, which is not same as port id. port id should be derived from chan_info array. So fix this. Without this, its possible that we could corrupt struct wcd938x_sdw_priv by accessing port_map array out of range with channel id instead of port id.

References

Track CVEs across your fleet automatically

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

Get started free