high CVSS 7.8

CVE-2024-38569·Kernel vulnerability

In the Linux kernel, the following vulnerability has been resolved: drivers/perf: hisi_pcie: Fix out-of-bound access when valid event group The perf tool allows users to create event groups through following cmd [1], but the driver does not check whether the array index is out of bounds when writing data to the event_group array. If the number of events in an event_group is greater than HISI_PCIE_MAX_COUNTERS, the memory write overflow of event_group array occurs. Add array index check to fix the possible array out of bounds violation, and return directly when write new events are written to array bounds. There are 9 different events in an event_group. [1] perf stat -e '{pmu/event1/, ... ,pmu/event9/}'

Severity
high
Software
Kernel
Fixed in
6.9.3
Published
2024-06-19

Affected versions

From: 6.9

Until: 6.9.3

Fixed in: 6.9.3

How to fix this CVE

Update your Linux kernel to version 6.9.3 or later to address an array bounds checking vulnerability in the HiSilicon PCIe performance monitoring driver. This flaw allows local users with sufficient privileges to trigger memory write overflow when configuring performance event groups with more than the maximum supported counters, potentially leading to kernel memory corruption. Patch your systems promptly, especially in production environments running vulnerable kernel versions 6.9 through 6.9.2.

sudo dnf update kernel kernel-devel

Defensia detects this vulnerability

How to check if you are affected

  1. Run 'uname -r' to identify your current kernel version and confirm if it falls within the 6.9.0 to 6.9.2 range
  2. Check if the HiSilicon PCIe PMU driver is loaded by running 'lsmod | grep hisi_pcie' or 'dmesg | grep -i hisi'
  3. Review kernel logs for any memory access violations or oops messages related to perf or event_group: 'sudo dmesg | grep -i "out of bounds\|array\|event_group"'
  4. After updating, verify the new kernel version with 'uname -r' and confirm it is 6.9.3 or later, then reboot and re-run the version check

FAQ

What is CVE-2024-38569?

This vulnerability exists in the Linux kernel's HiSilicon PCIe performance monitoring driver, where insufficient bounds checking on performance event group arrays allows local users to write beyond allocated memory when configuring more than the maximum number of performance counters, potentially corrupting kernel memory.

Is CVE-2024-38569 being actively exploited?

No, according to CISA's Known Exploited Vulnerabilities database, this CVE is not currently being actively exploited in the wild, and no public exploits are available.

What versions of Kernel are affected by CVE-2024-38569?

Linux kernel versions 6.9.0 through 6.9.2 are affected; version 6.9.3 and later contain the fix.

How do I check if my server is vulnerable to CVE-2024-38569?

Run 'uname -r' to check your kernel version; if it shows 6.9.0, 6.9.1, or 6.9.2, your system is vulnerable. Additionally verify with 'cat /boot/config-$(uname -r) | grep HISI_PCIE' to confirm the affected driver is enabled.

Does Defensia detect CVE-2024-38569?

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-2024-38569 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-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-2024-38569. Free for 1 server.

Get started free