CVSS: -EPSS: 0%CPEs: 2EXPL: 0CVE-2024-42162 – gve: Account for stopped queues when reading NIC stats
https://notcve.org/view.php?id=CVE-2024-42162
In the Linux kernel, the following vulnerability has been resolved: gve: Account for stopped queues when reading NIC stats We now account for the fact that the NIC might send us stats for a subset of queues. Without this change, gve_get_ethtool_stats might make an invalid access on the priv->stats_report->stats array. • https://git.kernel.org/stable/c/32675d828c8a392e20d5b42375ed112c407e4b62 https://git.kernel.org/stable/c/af9bcf910b1f86244f39e15e701b2dc564b469a6 •
CVSS: -EPSS: 0%CPEs: 6EXPL: 0CVE-2024-42161 – bpf: Avoid uninitialized value in BPF_CORE_READ_BITFIELD
https://notcve.org/view.php?id=CVE-2024-42161
In the Linux kernel, the following vulnerability has been resolved: bpf: Avoid uninitialized value in BPF_CORE_READ_BITFIELD [Changes from V1: - Use a default branch in the switch statement to initialize `val'.] GCC warns that `val' may be used uninitialized in the BPF_CRE_READ_BITFIELD macro, defined in bpf_core_read.h as: [...] unsigned long long val; \ [...] \ switch (__CORE_RELO(s, field, BYTE_SIZE)) { \ case 1: val = *(const unsigned char *)p; break; \ case 2: val = *(const unsigned short *)p; break; \ case 4: val = *(const unsigned int *)p; break; \ case 8: val = *(const unsigned long long *)p; break; \ } \ [...] val; \ } \ This patch adds a default entry in the switch statement that sets `val' to zero in order to avoid the warning, and random values to be used in case __builtin_preserve_field_info returns unexpected values for BPF_FIELD_BYTE_SIZE. Tested in bpf-next master. No regressions. • https://git.kernel.org/stable/c/b694989bb13ed5f166e633faa1eb0f21c6d261a6 https://git.kernel.org/stable/c/3364c2ed1c241989847f19cf83e3db903ce689e3 https://git.kernel.org/stable/c/a21d76bd0b0d39518e9a4c19f6cf7c042a974aff https://git.kernel.org/stable/c/7e5471b5efebc30dd0bc035cda86693a5c73d45f https://git.kernel.org/stable/c/ff941a8449e712eaf7efca1a13bfb9afd3d99fc2 https://git.kernel.org/stable/c/009367099eb61a4fc2af44d4eb06b6b4de7de6db •
CVSS: -EPSS: 0%CPEs: 4EXPL: 0CVE-2024-42160 – f2fs: check validation of fault attrs in f2fs_build_fault_attr()
https://notcve.org/view.php?id=CVE-2024-42160
In the Linux kernel, the following vulnerability has been resolved: f2fs: check validation of fault attrs in f2fs_build_fault_attr() - It missed to check validation of fault attrs in parse_options(), let's fix to add check condition in f2fs_build_fault_attr(). - Use f2fs_build_fault_attr() in __sbi_store() to clean up code. • https://git.kernel.org/stable/c/bc84dd2c33e0c10fd90d60f0cfc0bfb504d4692d https://git.kernel.org/stable/c/44958ca9e400f57bd0478115519ffc350fcee61e https://git.kernel.org/stable/c/ecb641f424d6d1f055d149a15b892edcc92c504b https://git.kernel.org/stable/c/4ed886b187f47447ad559619c48c086f432d2b77 •
CVSS: 7.3EPSS: 0%CPEs: 4EXPL: 0CVE-2024-42159 – scsi: mpi3mr: Sanitise num_phys
https://notcve.org/view.php?id=CVE-2024-42159
In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Sanitise num_phys Information is stored in mr_sas_port->phy_mask, values larger then size of this field shouldn't be allowed. A vulnerability was found in the Linux kernel's mpi3mr driver in the mpi3mr_sas_port_add() function, where a lack of proper checks could lead to values that are larger than what the defined size of the num_phys field in the mr_sas_node structure being inserted, causing the field to be overwritten and potentially corrupting the structure. This issue could lead to memory corruption or crashes. • https://git.kernel.org/stable/c/b869ec89d2ee923d46608b76e54c006680c9b4df https://git.kernel.org/stable/c/586b41060113ae43032ec6c4a16d518cef5da6e0 https://git.kernel.org/stable/c/c8707901b53a48106d7501bdbd0350cefaefa4cf https://git.kernel.org/stable/c/3668651def2c1622904e58b0280ee93121f2b10b https://access.redhat.com/security/cve/CVE-2024-42159 https://bugzilla.redhat.com/show_bug.cgi?id=2301530 • CWE-787: Out-of-bounds Write •
CVSS: -EPSS: 0%CPEs: 2EXPL: 0CVE-2024-42158 – s390/pkey: Use kfree_sensitive() to fix Coccinelle warnings
https://notcve.org/view.php?id=CVE-2024-42158
In the Linux kernel, the following vulnerability has been resolved: s390/pkey: Use kfree_sensitive() to fix Coccinelle warnings Replace memzero_explicit() and kfree() with kfree_sensitive() to fix warnings reported by Coccinelle: WARNING opportunity for kfree_sensitive/kvfree_sensitive (line 1506) WARNING opportunity for kfree_sensitive/kvfree_sensitive (line 1643) WARNING opportunity for kfree_sensitive/kvfree_sensitive (line 1770) • https://git.kernel.org/stable/c/62151a0acde90823bdfa991d598c85cf4b1d387d https://git.kernel.org/stable/c/22e6824622e8a8889df0f8fc4ed5aea0e702a694 •