CVSS: 6.3EPSS: 0%CPEs: 8EXPL: 0CVE-2024-42228 – drm/amdgpu: Using uninitialized value *size when calling amdgpu_vce_cs_reloc
https://notcve.org/view.php?id=CVE-2024-42228
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Using uninitialized value *size when calling amdgpu_vce_cs_reloc Initialize the size before calling amdgpu_vce_cs_reloc, such as case 0x03000001. V2: To really improve the handling we would actually need to have a separate value of 0xffffffff.(Christian) A vulnerability was found in the Linux kernel's amdgpu driver in the amdgpu_vce_ring_parse_cs() function where the size variable is initialized with a pointer that may not be properly set before use. This issue could lead to unpredictable behavior in the system. • https://git.kernel.org/stable/c/d35cf41c8eb5d9fe95b21ae6ee2910f9ba4878e8 https://git.kernel.org/stable/c/3b505759447637dcccb50cbd98ec6f8d2a04fc46 https://git.kernel.org/stable/c/df02642c21c984303fe34c3f7d72965792fb1a15 https://git.kernel.org/stable/c/da6a85d197888067e8d38b5d22c986b5b5cab712 https://git.kernel.org/stable/c/9ee1534ecdd5b4c013064663502d7fde824d2144 https://git.kernel.org/stable/c/855ae72c20310e5402b2317fc537d911e87537ef https://git.kernel.org/stable/c/f8f120b3de48b8b6bdf8988a9b334c2d61c17440 https://git.kernel.org/stable/c/88a9a467c548d0b3c7761b4fd54a68e70 • CWE-457: Use of Uninitialized Variable •
CVSS: -EPSS: 0%CPEs: 2EXPL: 0CVE-2024-42227 – drm/amd/display: Fix overlapping copy within dml_core_mode_programming
https://notcve.org/view.php?id=CVE-2024-42227
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix overlapping copy within dml_core_mode_programming [WHY] &mode_lib->mp.Watermark and &locals->Watermark are the same address. memcpy may lead to unexpected behavior. [HOW] memmove should be used. • https://git.kernel.org/stable/c/9342da15f2491d8600eca89c8e0da08876fb969b https://git.kernel.org/stable/c/f1fd8a0a54e6d23a6d16ee29159f247862460fd1 •
CVSS: 4.8EPSS: 0%CPEs: 5EXPL: 0CVE-2024-42225 – wifi: mt76: replace skb_put with skb_put_zero
https://notcve.org/view.php?id=CVE-2024-42225
In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: replace skb_put with skb_put_zero Avoid potentially reusing uninitialized data A potential flaw was found in the Linux kernel’s MediaTek WiFi, where it was reusing uninitialized data. This flaw allows a local user to gain unauthorized access to some data potentially. • https://git.kernel.org/stable/c/dc7f14d00d0c4c21898f3504607f4a31079065a2 https://git.kernel.org/stable/c/22ea2a7f0b64d323625950414a4496520fb33657 https://git.kernel.org/stable/c/ff6b26be13032c5fbd6b6a0b24358f8eaac4f3af https://git.kernel.org/stable/c/64f86337ccfe77fe3be5a9356b0dabde23fbb074 https://git.kernel.org/stable/c/7f819a2f4fbc510e088b49c79addcf1734503578 https://access.redhat.com/security/cve/CVE-2024-42225 https://bugzilla.redhat.com/show_bug.cgi?id=2301543 • CWE-457: Use of Uninitialized Variable •
CVSS: -EPSS: 0%CPEs: 8EXPL: 0CVE-2024-42224 – net: dsa: mv88e6xxx: Correct check for empty list
https://notcve.org/view.php?id=CVE-2024-42224
In the Linux kernel, the following vulnerability has been resolved: net: dsa: mv88e6xxx: Correct check for empty list Since commit a3c53be55c95 ("net: dsa: mv88e6xxx: Support multiple MDIO busses") mv88e6xxx_default_mdio_bus() has checked that the return value of list_first_entry() is non-NULL. This appears to be intended to guard against the list chip->mdios being empty. However, it is not the correct check as the implementation of list_first_entry is not designed to return NULL for empty lists. Instead, use list_first_entry_or_null() which does return NULL if the list is empty. Flagged by Smatch. Compile tested only. • https://git.kernel.org/stable/c/47d28dde172696031c880c5778633cdca30394ee https://git.kernel.org/stable/c/3bf8d70e1455f87856640c3433b3660a31001618 https://git.kernel.org/stable/c/2a2fe25a103cef73cde356e6d09da10f607e93f5 https://git.kernel.org/stable/c/8c2c3cca816d074c75a2801d1ca0dea7b0148114 https://git.kernel.org/stable/c/aa03f591ef31ba603a4a99d05d25a0f21ab1cd89 https://git.kernel.org/stable/c/3f25b5f1635449036692a44b771f39f772190c1d https://git.kernel.org/stable/c/f75625db838ade28f032dacd0f0c8baca42ecde4 https://git.kernel.org/stable/c/4c7f3950a9fd53a62b156c0fe7c3a2c43 •
CVSS: -EPSS: 0%CPEs: 8EXPL: 0CVE-2024-42223 – media: dvb-frontends: tda10048: Fix integer overflow
https://notcve.org/view.php?id=CVE-2024-42223
In the Linux kernel, the following vulnerability has been resolved: media: dvb-frontends: tda10048: Fix integer overflow state->xtal_hz can be up to 16M, so it can overflow a 32 bit integer when multiplied by pll_mfactor. Create a new 64 bit variable to hold the calculations. • https://git.kernel.org/stable/c/8167e4d7dc086d4f7ca7897dcff3827e4d22c99a https://git.kernel.org/stable/c/5c72587d024f087aecec0221eaff2fe850d856ce https://git.kernel.org/stable/c/e1ba22618758e95e09c9fd30c69ccce38edf94c0 https://git.kernel.org/stable/c/bd5620439959a7e02012588c724c6ff5143b80af https://git.kernel.org/stable/c/1663e2474e4d777187d749a5c90ae83232db32bd https://git.kernel.org/stable/c/8ac224e9371dc3c4eb666033e6b42d05cf5184a1 https://git.kernel.org/stable/c/1121d8a5c6ed6b8fad492e43b63b386cb6a3a9d8 https://git.kernel.org/stable/c/1aa1329a67cc214c3b7bd2a14d1301a79 •