CVSS: -EPSS: 0%CPEs: 5EXPL: 0CVE-2024-49850 – bpf: correctly handle malformed BPF_CORE_TYPE_ID_LOCAL relos
https://notcve.org/view.php?id=CVE-2024-49850
In the Linux kernel, the following vulnerability has been resolved: bpf: correctly handle malformed BPF_CORE_TYPE_ID_LOCAL relos In case of malformed relocation record of kind BPF_CORE_TYPE_ID_LOCAL referencing a non-existing BTF type, function bpf_core_calc_relo_insn would cause a null pointer deference. Fix this by adding a proper check upper in call stack, as malformed relocation records could be passed from user space. Simplest reproducer is a program: r0 = 0 exit With a single relocation record: .insn_off = 0, /* patch first instruction */ .type_id = 100500, /* this type id does not exist */ .access_str_off = 6, /* offset of string "0" */ .kind = BPF_CORE_TYPE_ID_LOCAL, See the link for original reproducer or next commit for a test case. • https://git.kernel.org/stable/c/74753e1462e77349525daf9eb60ea21ed92d3a97 https://git.kernel.org/stable/c/dc7ce14f00bcd50641f2110b7a32aa6552e0780f https://git.kernel.org/stable/c/2288b54b96dcb55bedebcef3572bb8821fc5e708 https://git.kernel.org/stable/c/584cd3ff792e1edbea20b2a7df55897159b0be3e https://git.kernel.org/stable/c/e7e9c5b2dda29067332df2a85b0141a92b41f218 https://git.kernel.org/stable/c/3d2786d65aaa954ebd3fcc033ada433e10da21c4 •
CVSS: -EPSS: 0%CPEs: 9EXPL: 0CVE-2024-47757 – nilfs2: fix potential oob read in nilfs_btree_check_delete()
https://notcve.org/view.php?id=CVE-2024-47757
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential oob read in nilfs_btree_check_delete() The function nilfs_btree_check_delete(), which checks whether degeneration to direct mapping occurs before deleting a b-tree entry, causes memory access outside the block buffer when retrieving the maximum key if the root node has no entries. This does not usually happen because b-tree mappings with 0 child nodes are never created by mkfs.nilfs2 or nilfs2 itself. However, it can happen if the b-tree root node read from a device is configured that way, so fix this potential issue by adding a check for that case. • https://git.kernel.org/stable/c/17c76b0104e4a6513983777e1a17e0297a12b0c4 https://git.kernel.org/stable/c/f3a9859767c7aea758976f5523903d247e585129 https://git.kernel.org/stable/c/ed76d381dae125b81d09934e365391a656249da8 https://git.kernel.org/stable/c/d20674f31626e0596ae4c1d9401dfb6739b81b58 https://git.kernel.org/stable/c/c4f8554996e8ada3be872dfb8f60e93bcf15fb27 https://git.kernel.org/stable/c/a8abfda768b9f33630cfbc4af6c4214f1e5681b0 https://git.kernel.org/stable/c/257f9e5185eb6de83377caea686c306e22e871f2 https://git.kernel.org/stable/c/a33e967b681e088a125b979975c93e345 •
CVSS: -EPSS: 0%CPEs: 8EXPL: 0CVE-2024-47756 – PCI: keystone: Fix if-statement expression in ks_pcie_quirk()
https://notcve.org/view.php?id=CVE-2024-47756
In the Linux kernel, the following vulnerability has been resolved: PCI: keystone: Fix if-statement expression in ks_pcie_quirk() This code accidentally uses && where || was intended. It potentially results in a NULL dereference. Thus, fix the if-statement expression to use the correct condition. [kwilczynski: commit log] • https://git.kernel.org/stable/c/cfb006e185f64edbbdf7869eac352442bc76b8f6 https://git.kernel.org/stable/c/ebbdbbc580c1695dec283d0ba6448729dc993246 https://git.kernel.org/stable/c/135843c351c08df72bdd4b4ebea53c8052a76881 https://git.kernel.org/stable/c/af218c803fe298ddf00abef331aa526b20d7ea61 https://git.kernel.org/stable/c/576d0fb6f8d4bd4695e70eee173a1b9c7bae9572 https://git.kernel.org/stable/c/dd47051c76c8acd8cb983f01b4d1265da29cb66a https://git.kernel.org/stable/c/86f271f22bbb6391410a07e08d6ca3757fda01fa https://git.kernel.org/stable/c/9c9afc3e75069fcfb067727973242cfbf •
CVSS: -EPSS: 0%CPEs: 4EXPL: 0CVE-2024-47752 – media: mediatek: vcodec: Fix H264 stateless decoder smatch warning
https://notcve.org/view.php?id=CVE-2024-47752
In the Linux kernel, the following vulnerability has been resolved: media: mediatek: vcodec: Fix H264 stateless decoder smatch warning Fix a smatch static checker warning on vdec_h264_req_if.c. Which leads to a kernel crash when fb is NULL. • https://git.kernel.org/stable/c/06fa5f757dc5a5687e1cdd13097c3265735f60bf https://git.kernel.org/stable/c/c6b9f971b43980de8893610f606d751131fb5d86 https://git.kernel.org/stable/c/18181b0c1c5bd43846e5e0ae3d61a4a1adceab03 https://git.kernel.org/stable/c/790d1848fac5ac3b1c474f66162598ab07a20c21 https://git.kernel.org/stable/c/7878d3a385efab560dce793b595447867fb163f2 •
CVSS: -EPSS: 0%CPEs: 5EXPL: 0CVE-2024-47751 – PCI: kirin: Fix buffer overflow in kirin_pcie_parse_port()
https://notcve.org/view.php?id=CVE-2024-47751
In the Linux kernel, the following vulnerability has been resolved: PCI: kirin: Fix buffer overflow in kirin_pcie_parse_port() Within kirin_pcie_parse_port(), the pcie->num_slots is compared to pcie->gpio_id_reset size (MAX_PCI_SLOTS) which is correct and would lead to an overflow. Thus, fix condition to pcie->num_slots + 1 >= MAX_PCI_SLOTS and move pcie->num_slots increment below the if-statement to avoid out-of-bounds array access. Found by Linux Verification Center (linuxtesting.org) with SVACE. [kwilczynski: commit log] • https://git.kernel.org/stable/c/b22dbbb24571c052364f476381dbac110bdca4d5 https://git.kernel.org/stable/c/a5f795f9412854df28e66679c5e6b68b0b79c229 https://git.kernel.org/stable/c/95248d7497bcbfe7deed4805469c6ff6ddd7f9d1 https://git.kernel.org/stable/c/6dcc5b49d6607a741a14122bf3105f3ac50d259e https://git.kernel.org/stable/c/aeb0335971806e15ac91e838ca471936c8e7efd5 https://git.kernel.org/stable/c/c500a86693a126c9393e602741e348f80f1b0fc5 •