Page 83 of 2833 results (0.007 seconds)

CVSS: 7.3EPSS: 0%CPEs: 4EXPL: 0

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: 0

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 •

CVSS: -EPSS: 0%CPEs: 8EXPL: 0

In the Linux kernel, the following vulnerability has been resolved: s390/pkey: Wipe sensitive data on failure Wipe sensitive data from stack also if the copy_to_user() fails. • https://git.kernel.org/stable/c/6e2e374403bf73140d0efc9541cb1b3bea55ac02 https://git.kernel.org/stable/c/b5eb9176ebd4697bc248bf8d145e66d782cf5250 https://git.kernel.org/stable/c/93c034c4314bc4c4450a3869cd5da298502346ad https://git.kernel.org/stable/c/4889f117755b2f18c23045a0f57977f3ec130581 https://git.kernel.org/stable/c/c51795885c801b6b7e976717e0d6d45b1e5be0f0 https://git.kernel.org/stable/c/90a01aefb84b09ccb6024d75d85bb8f620bd3487 https://git.kernel.org/stable/c/c44a2151e5d21c66b070a056c26471f30719b575 https://git.kernel.org/stable/c/1d8c270de5eb74245d72325d285894a57 •

CVSS: -EPSS: 0%CPEs: 2EXPL: 0

In the Linux kernel, the following vulnerability has been resolved: s390/pkey: Wipe copies of clear-key structures on failure Wipe all sensitive data from stack for all IOCTLs, which convert a clear-key into a protected- or secure-key. • https://git.kernel.org/stable/c/7f6243edd901b75aaece326c90a1cc0dcb60cc3d https://git.kernel.org/stable/c/d65d76a44ffe74c73298ada25b0f578680576073 •

CVSS: -EPSS: 0%CPEs: 2EXPL: 0

In the Linux kernel, the following vulnerability has been resolved: s390/pkey: Wipe copies of protected- and secure-keys Although the clear-key of neither protected- nor secure-keys is accessible, this key material should only be visible to the calling process. So wipe all copies of protected- or secure-keys from stack, even in case of an error. • https://git.kernel.org/stable/c/c746f7ced4ad88ee48d0b6c92710e4674403185b https://git.kernel.org/stable/c/f2ebdadd85af4f4d0cae1e5d009c70eccc78c207 •