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 •
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
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 https://git.kernel.org/stable/c/31c6fe9b79ed42440094f2367897aea0c0ce96ec https://git.kernel.org/stable/c/b4ba31e5aaffbda9b22d9a35c40b16dc39e475a6 https://git.kernel.org/stable/c/a0e4c78770faa0d56d47391476fe1d827e72eded https://git.kernel.org/stable/c/e2e64f9c42c717beb459ab209ec1c4baa73d3760 https://git.kernel.org/stable/c/323275ac2ff15b2b7b3eac391ae5d8c5a3c3a999 •
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
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 https://git.kernel.org/stable/c/82d6b82cf89d950982ac240ba068c3a7e1f23b0a https://git.kernel.org/stable/c/ccfee14f08b8699132b87bc6d78e0fa75bf094dd https://git.kernel.org/stable/c/ff6cdc407f4179748f4673c39b0921503199a0ad •
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
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 https://git.kernel.org/stable/c/d3f5763b3062514a234114e97bbde74d8d702449 https://git.kernel.org/stable/c/d26d977633d1d0b8bf9407278189bd0a8d973323 https://git.kernel.org/stable/c/e1f54c61c4c9a5244eb8159dce60d248f7d97b32 https://git.kernel.org/stable/c/f58d3aa457e77a3d9b3df2ab081dcf9950f6029f https://git.kernel.org/stable/c/98c7ea7d11f2588e8197db042e0291e4ac8f8346 https://git.kernel.org/stable/c/785180bed9879680d8e5c5e1b54c8ae8d948f4c8 https://git.kernel.org/stable/c/275a9f3ef8fabb0cb282a62b9e164dedb •
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
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 from dma_map_single(). However, by moving the assignment later, this is not the case when priv->dma_cap.addr64 > 32 as "des" is offset by proto_hdr_len. This causes problems such as: dwc-eth-dwmac 2490000.ethernet eth0: Tx DMA map failed and with DMA_API_DEBUG enabled: DMA-API: dwc-eth-dwmac 2490000.ethernet: device driver tries to +free DMA memory it has not allocated [device address=0x000000ffffcf65c0] [size=66 bytes] Fix this by maintaining "des" as the original DMA cookie, and use tso_des to pass the offset DMA cookie to stmmac_tso_allocator(). Full details of the crashes can be found at: https://lore.kernel.org/all/d8112193-0386-4e14-b516-37c2d838171a@nvidia.com/ https://lore.kernel.org/all/klkzp5yn5kq5efgtrow6wbvnc46bcqfxs65nz3qy77ujr5turc@bwwhelz2l4dw/ • https://git.kernel.org/stable/c/07c9c26e37542486e34d767505e842f48f29c3f6 https://git.kernel.org/stable/c/66600fac7a984dea4ae095411f644770b2561ede https://git.kernel.org/stable/c/ece593fc9c00741b682869d3f3dc584d37b7c9df https://git.kernel.org/stable/c/a3ff23f7c3f0e13f718900803e090fd3997d6bc9 https://git.kernel.org/stable/c/58d23d835eb498336716cca55b5714191a309286 https://git.kernel.org/stable/c/db3667c9bbfbbf5de98e6c9542f7e03fb5243286 https://git.kernel.org/stable/c/9d5dd7ccea1b46a9a7c6b3c2b9e5ed8864e185e2 https://git.kernel.org/stable/c/4c49f38e20a57f8abaebdf95b369295b1 •