CVSS: 5.1EPSS: 0%CPEs: 3EXPL: 0CVE-2024-40997 – cpufreq: amd-pstate: fix memory leak on CPU EPP exit
https://notcve.org/view.php?id=CVE-2024-40997
In the Linux kernel, the following vulnerability has been resolved: cpufreq: amd-pstate: fix memory leak on CPU EPP exit The cpudata memory from kzalloc() in amd_pstate_epp_cpu_init() is not freed in the analogous exit function, so fix that. [ rjw: Subject and changelog edits ] • https://git.kernel.org/stable/c/448efb7ea0bfa2c4e27c5a2eb5684fd225cd12cd https://git.kernel.org/stable/c/8015c17fe11a8608cc3eb83d0ab831e1845a9582 https://git.kernel.org/stable/c/cea04f3d9aeebda9d9c063c0dfa71e739c322c81 https://access.redhat.com/security/cve/CVE-2024-40997 https://bugzilla.redhat.com/show_bug.cgi?id=2297581 • CWE-402: Transmission of Private Resources into a New Sphere ('Resource Leak') •
CVSS: 4.7EPSS: 0%CPEs: 8EXPL: 0CVE-2024-40988 – drm/radeon: fix UBSAN warning in kv_dpm.c
https://notcve.org/view.php?id=CVE-2024-40988
In the Linux kernel, the following vulnerability has been resolved: drm/radeon: fix UBSAN warning in kv_dpm.c Adds bounds check for sumo_vid_mapping_entry. • https://git.kernel.org/stable/c/07e8f15fa16695cf4c90e89854e59af4a760055b https://git.kernel.org/stable/c/a8c6df9fe5bc390645d1e96eff14ffe414951aad https://git.kernel.org/stable/c/febe794b83693257f21a23d2e03ea695a62449c8 https://git.kernel.org/stable/c/cf1cc8fcfe517e108794fb711f7faabfca0dc855 https://git.kernel.org/stable/c/f803532bc3825384100dfc58873e035d77248447 https://git.kernel.org/stable/c/9e57611182a817824a17b1c3dd300ee74a174b42 https://git.kernel.org/stable/c/468a50fd46a09bba7ba18a11054ae64b6479ecdc https://git.kernel.org/stable/c/a498df5421fd737d11bfd152428ba6b1c • CWE-787: Out-of-bounds Write •
CVSS: -EPSS: 0%CPEs: 8EXPL: 0CVE-2024-40987 – drm/amdgpu: fix UBSAN warning in kv_dpm.c
https://notcve.org/view.php?id=CVE-2024-40987
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix UBSAN warning in kv_dpm.c Adds bounds check for sumo_vid_mapping_entry. • https://git.kernel.org/stable/c/4ad7d49059358ceadd352b4e2511425bdb68f400 https://git.kernel.org/stable/c/1c44f7759a5650acf8f13d3e0a184d09e03be9e4 https://git.kernel.org/stable/c/d8a04a6bfa75251ba7bcc3651ed211e82f13f388 https://git.kernel.org/stable/c/4d020c1dbd2b2304f44d003e6de956ae570049dc https://git.kernel.org/stable/c/fc5cb952e6723c5c55e47b8cf94a891bd4af1a86 https://git.kernel.org/stable/c/b065d79ed06a0bb4377bc6dcc2ff0cb1f55a798f https://git.kernel.org/stable/c/b0d612619ed70cab476c77b19e00d13aa414e14f https://git.kernel.org/stable/c/f0d576f840153392d04b2d52cf3adab8f •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2024-40984 – ACPICA: Revert "ACPICA: avoid Info: mapping multiple BARs. Your kernel is fine."
https://notcve.org/view.php?id=CVE-2024-40984
In the Linux kernel, the following vulnerability has been resolved: ACPICA: Revert "ACPICA: avoid Info: mapping multiple BARs. Your kernel is fine." Undo the modifications made in commit d410ee5109a1 ("ACPICA: avoid "Info: mapping multiple BARs. Your kernel is fine.""). The initial purpose of this commit was to stop memory mappings for operation regions from overlapping page boundaries, as it can trigger warnings if different page attributes are present. However, it was found that when this situation arises, mapping continues until the boundary's end, but there is still an attempt to read/write the entire length of the map, leading to a NULL pointer deference. • https://git.kernel.org/stable/c/d410ee5109a1633a686a5663c6743a92e1181f9b https://git.kernel.org/stable/c/435ecc978c3d5d0c4e172ec5b956dc1904061d98 https://git.kernel.org/stable/c/ae465109d82f4fb03c5adbe85f2d6a6a3d59124c https://git.kernel.org/stable/c/6eca23100e9030725f69c1babacd58803f29ec8d https://git.kernel.org/stable/c/dc5017c57f5eee80020c73ff8b67ba7f9fd08b1f https://git.kernel.org/stable/c/ddc1f5f124479360a1fd43f73be950781d172239 https://git.kernel.org/stable/c/434c6b924e1f4c219aab2d9e05fe79c5364e37d3 https://git.kernel.org/stable/c/e21a4c9129c72fa54dd00f5ebf71219b4 • CWE-476: NULL Pointer Dereference •
CVSS: -EPSS: 0%CPEs: 3EXPL: 0CVE-2024-40982 – ssb: Fix potential NULL pointer dereference in ssb_device_uevent()
https://notcve.org/view.php?id=CVE-2024-40982
In the Linux kernel, the following vulnerability has been resolved: ssb: Fix potential NULL pointer dereference in ssb_device_uevent() The ssb_device_uevent() function first attempts to convert the 'dev' pointer to 'struct ssb_device *'. However, it mistakenly dereferences 'dev' before performing the NULL check, potentially leading to a NULL pointer dereference if 'dev' is NULL. To fix this issue, move the NULL check before dereferencing the 'dev' pointer, ensuring that the pointer is valid before attempting to use it. Found by Linux Verification Center (linuxtesting.org) with SVACE. • https://git.kernel.org/stable/c/c5dc2d8eb3981bae261ea7d1060a80868e886813 https://git.kernel.org/stable/c/7d43c8377c6fc846b1812f8df360425c9323dc56 https://git.kernel.org/stable/c/789c17185fb0f39560496c2beab9b57ce1d0cbe7 •