CVSS: -EPSS: 0%CPEs: 7EXPL: 0CVE-2024-56728 – octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_ethtool.c
https://notcve.org/view.php?id=CVE-2024-56728
29 Dec 2024 — In the Linux kernel, the following vulnerability has been resolved: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_ethtool.c Add error pointer check after calling otx2_mbox_get_rsp(). • https://git.kernel.org/stable/c/75f36270990c7875c0091afb961ca37f52b6bc55 •
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
29 Dec 2024 — 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 •
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
29 Dec 2024 — 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 •
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
29 Dec 2024 — 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 •
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
29 Dec 2024 — 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... • https://git.kernel.org/stable/c/957ae5098185e763b5c06be6c3b4b6e98c048712 •
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
29 Dec 2024 — 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 t... • https://git.kernel.org/stable/c/57129044f5044dcd73c22d91491906104bd331fd •
CVSS: -EPSS: 0%CPEs: 5EXPL: 0CVE-2024-56722 – RDMA/hns: Fix cpu stuck caused by printings during reset
https://notcve.org/view.php?id=CVE-2024-56722
29 Dec 2024 — In the Linux kernel, the following vulnerability has been resolved: RDMA/hns: Fix cpu stuck caused by printings during reset During reset, cmd to destroy resources such as qp, cq, and mr may fail, and error logs will be printed. When a large number of resources are destroyed, there will be lots of printings, and it may lead to a cpu stuck. Delete some unnecessary printings and replace other printing functions in these paths with the ratelimited version. • https://git.kernel.org/stable/c/9a4435375cd151e07c0c38fa601b00115986091b •
CVSS: -EPSS: 0%CPEs: 3EXPL: 0CVE-2024-56721 – x86/CPU/AMD: Terminate the erratum_1386_microcode array
https://notcve.org/view.php?id=CVE-2024-56721
29 Dec 2024 — In the Linux kernel, the following vulnerability has been resolved: x86/CPU/AMD: Terminate the erratum_1386_microcode array The erratum_1386_microcode array requires an empty entry at the end. Otherwise x86_match_cpu_with_stepping() will continue iterate the array after it ended. Add an empty entry to erratum_1386_microcode to its end. • https://git.kernel.org/stable/c/29ba89f1895285f06c333546882e0c5ae9a6df23 •
CVSS: -EPSS: 0%CPEs: 8EXPL: 0CVE-2024-56720 – bpf, sockmap: Several fixes to bpf_msg_pop_data
https://notcve.org/view.php?id=CVE-2024-56720
29 Dec 2024 — In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Several fixes to bpf_msg_pop_data Several fixes to bpf_msg_pop_data, 1. In sk_msg_shift_left, we should put_page 2. if (len == 0), return early is better 3. pop the entire sk_msg (last == msg->sg.size) should be supported 4. Fix for the value of variable "a" 5. In sk_msg_shift_left, after shifting, i has already pointed to the next element. Addtional sk_msg_iter_var_next may result in BUG. • https://git.kernel.org/stable/c/7246d8ed4dcce23f7509949a77be15fa9f0e3d28 •
CVSS: -EPSS: 0%CPEs: 6EXPL: 0CVE-2024-56719 – net: stmmac: fix TSO DMA API usage causing oops
https://notcve.org/view.php?id=CVE-2024-56719
29 Dec 2024 — In the Linux kernel, the following vulnerability has been resolved: net: stmmac: fix TSO DMA API usage causing oops Commit 66600fac7a98 ("net: stmmac: TSO: Fix unbalanced DMA map/unmap for non-paged SKB data") moved the assignment of tx_skbuff_dma[]'s members to be later in stmmac_tso_xmit(). The buf (dma cookie) and len stored in this structure are passed to dma_unmap_single() by stmmac_tx_clean(). The DMA API requires that the dma cookie passed to dma_unmap_single() is the same as the value returned fr... • https://git.kernel.org/stable/c/07c9c26e37542486e34d767505e842f48f29c3f6 •