CVSS: -EPSS: 0%CPEs: 5EXPL: 0CVE-2024-56727 – octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_flows.c
https://notcve.org/view.php?id=CVE-2024-56727
In the Linux kernel, the following vulnerability has been resolved: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_flows.c Adding error pointer check after calling otx2_mbox_get_rsp(). • https://git.kernel.org/stable/c/f0a1913f8a6f947531c3042f9d6524946e661b57 https://git.kernel.org/stable/c/8c9f8b35dc3d4ad8053a72bc0c5a7843591f6b75 https://git.kernel.org/stable/c/c4eae7bac880edd88aaed6a8ec2997fa85e259c7 https://git.kernel.org/stable/c/a479b3d7586e6f77f8337bbcac980eaf2d0a4029 https://git.kernel.org/stable/c/e5e60f17d2462ef5c13db4d1a54eef5778fd2295 https://git.kernel.org/stable/c/bd3110bc102ab6292656b8118be819faa0de8dd0 •
CVSS: -EPSS: 0%CPEs: 6EXPL: 0CVE-2024-56726 – octeontx2-pf: handle otx2_mbox_get_rsp errors in cn10k.c
https://notcve.org/view.php?id=CVE-2024-56726
In the Linux kernel, the following vulnerability has been resolved: octeontx2-pf: handle otx2_mbox_get_rsp errors in cn10k.c Add error pointer check after calling otx2_mbox_get_rsp(). • https://git.kernel.org/stable/c/2ca89a2c37527221edc549ffd3b65c6f8d9d4088 https://git.kernel.org/stable/c/a374e7e79fbdd7574bd89344447b0d4b91ba9801 https://git.kernel.org/stable/c/856ad633e11869729be698df2287ecfe6ec31f27 https://git.kernel.org/stable/c/c5a6c5af434671aea739a5a41c849819144f02c9 https://git.kernel.org/stable/c/41f39f4c67253f802809310be6846ff408c3c758 https://git.kernel.org/stable/c/54abcec092616a4d01195355eb5d6036fb8fe363 https://git.kernel.org/stable/c/ac9183023b6a9c09467516abd8aab04f9a2f9564 •
CVSS: -EPSS: 0%CPEs: 5EXPL: 0CVE-2024-56725 – octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_dcbnl.c
https://notcve.org/view.php?id=CVE-2024-56725
In the Linux kernel, the following vulnerability has been resolved: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_dcbnl.c Add error pointer check after calling otx2_mbox_get_rsp(). • https://git.kernel.org/stable/c/8e67558177f8f55dcffa47273c2af0a6f2ab9418 https://git.kernel.org/stable/c/b94052830e3cd3be7141789a5ce6e62cf9f620a4 https://git.kernel.org/stable/c/b99db02209ca4c2e2f53b82049ea3cbc82b54895 https://git.kernel.org/stable/c/54e8b501b3ea9371e4a9aa639c75b681fa5680f0 https://git.kernel.org/stable/c/6ee6cf42dc5230425cfce1ffefa5a8d8a99e6fce https://git.kernel.org/stable/c/69297b0d3369488af259e3a7cf53d69157938ea1 •
CVSS: -EPSS: 0%CPEs: 8EXPL: 0CVE-2024-56724 – mfd: intel_soc_pmic_bxtwc: Use IRQ domain for TMU device
https://notcve.org/view.php?id=CVE-2024-56724
In the Linux kernel, the following vulnerability has been resolved: mfd: intel_soc_pmic_bxtwc: Use IRQ domain for TMU device While design wise the idea of converting the driver to use the hierarchy of the IRQ chips is correct, the implementation has (inherited) flaws. This was unveiled when platform_get_irq() had started WARN() on IRQ 0 that is supposed to be a Linux IRQ number (also known as vIRQ). Rework the driver to respect IRQ domain when creating each MFD device separately, as the domain is not the same for all of them. • https://git.kernel.org/stable/c/957ae5098185e763b5c06be6c3b4b6e98c048712 https://git.kernel.org/stable/c/b7c7c400de85d915e0da7c2c363553a801c47349 https://git.kernel.org/stable/c/c472b55cc0bc3df805db6a14f50a084884cf18ee https://git.kernel.org/stable/c/da498e02c92e6d82df8001438dd583b90c570815 https://git.kernel.org/stable/c/56acf415772ee7e10e448b371f52b249aa2d0f7b https://git.kernel.org/stable/c/1b734ad0e33648c3988c6a37c2ac16c2d63eda06 https://git.kernel.org/stable/c/2310f5336f32eac9ada2d59b965d578efe25c4bf https://git.kernel.org/stable/c/5bc6d0da4a32fe34a9960de577e0b7de3 •
CVSS: -EPSS: 0%CPEs: 8EXPL: 0CVE-2024-56723 – mfd: intel_soc_pmic_bxtwc: Use IRQ domain for PMIC devices
https://notcve.org/view.php?id=CVE-2024-56723
In the Linux kernel, the following vulnerability has been resolved: mfd: intel_soc_pmic_bxtwc: Use IRQ domain for PMIC devices While design wise the idea of converting the driver to use the hierarchy of the IRQ chips is correct, the implementation has (inherited) flaws. This was unveiled when platform_get_irq() had started WARN() on IRQ 0 that is supposed to be a Linux IRQ number (also known as vIRQ). Rework the driver to respect IRQ domain when creating each MFD device separately, as the domain is not the same for all of them. • https://git.kernel.org/stable/c/57129044f5044dcd73c22d91491906104bd331fd https://git.kernel.org/stable/c/6ea17c03edc7ed0aabb1431eb26e2f94849af68a https://git.kernel.org/stable/c/61d590d7076b50b6ebdea1f3b83bb041c01fc482 https://git.kernel.org/stable/c/bb6642d4b3136359b5b620049f76515876e6127e https://git.kernel.org/stable/c/7ba45b8bc62e64da524d45532107ae93eb33c93c https://git.kernel.org/stable/c/d4cc78bd6a25accb7ae2ac9fc445d1e1deda4a62 https://git.kernel.org/stable/c/897713c9d24f6ec394585abfcf259a6e5cad22c8 https://git.kernel.org/stable/c/b3d45c19bcffb9a9a821df759f60be39d •