{"uuid": "8abfca58-46af-40d0-82e3-e756685ac447", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-42073", "type": "seen", "source": "https://t.me/cvedetector/1879", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42073 - Mellanox Linux mlxsw Spectrum-4 Memory Corruption Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-42073 \nPublished : July 29, 2024, 4:15 p.m. | 26\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nmlxsw: spectrum_buffers: Fix memory corruptions on Spectrum-4 systems  \n  \nThe following two shared buffer operations make use of the Shared Buffer  \nStatus Register (SBSR):  \n  \n # devlink sb occupancy snapshot pci/0000:01:00.0  \n # devlink sb occupancy clearmax pci/0000:01:00.0  \n  \nThe register has two masks of 256 bits to denote on which ingress /  \negress ports the register should operate on. Spectrum-4 has more than  \n256 ports, so the register was extended by cited commit with a new  \n'port_page' field.  \n  \nHowever, when filling the register's payload, the driver specifies the  \nports as absolute numbers and not relative to the first port of the port  \npage, resulting in memory corruptions [1].  \n  \nFix by specifying the ports relative to the first port of the port page.  \n  \n[1]  \nBUG: KASAN: slab-use-after-free in mlxsw_sp_sb_occ_snapshot+0xb6d/0xbc0  \nRead of size 1 at addr ffff8881068cb00f by task devlink/1566  \n[...]  \nCall Trace:  \n   \n dump_stack_lvl+0xc6/0x120  \n print_report+0xce/0x670  \n kasan_report+0xd7/0x110  \n mlxsw_sp_sb_occ_snapshot+0xb6d/0xbc0  \n mlxsw_devlink_sb_occ_snapshot+0x75/0xb0  \n devlink_nl_sb_occ_snapshot_doit+0x1f9/0x2a0  \n genl_family_rcv_msg_doit+0x20c/0x300  \n genl_rcv_msg+0x567/0x800  \n netlink_rcv_skb+0x170/0x450  \n genl_rcv+0x2d/0x40  \n netlink_unicast+0x547/0x830  \n netlink_sendmsg+0x8d4/0xdb0  \n __sys_sendto+0x49b/0x510  \n __x64_sys_sendto+0xe5/0x1c0  \n do_syscall_64+0xc1/0x1d0  \n entry_SYSCALL_64_after_hwframe+0x77/0x7f  \n[...]  \nAllocated by task 1:  \n kasan_save_stack+0x33/0x60  \n kasan_save_track+0x14/0x30  \n __kasan_kmalloc+0x8f/0xa0  \n copy_verifier_state+0xbc2/0xfb0  \n do_check_common+0x2c51/0xc7e0  \n bpf_check+0x5107/0x9960  \n bpf_prog_load+0xf0e/0x2690  \n __sys_bpf+0x1a61/0x49d0  \n __x64_sys_bpf+0x7d/0xc0  \n do_syscall_64+0xc1/0x1d0  \n entry_SYSCALL_64_after_hwframe+0x77/0x7f  \n  \nFreed by task 1:  \n kasan_save_stack+0x33/0x60  \n kasan_save_track+0x14/0x30  \n kasan_save_free_info+0x3b/0x60  \n poison_slab_object+0x109/0x170  \n __kasan_slab_free+0x14/0x30  \n kfree+0xca/0x2b0  \n free_verifier_state+0xce/0x270  \n do_check_common+0x4828/0xc7e0  \n bpf_check+0x5107/0x9960  \n bpf_prog_load+0xf0e/0x2690  \n __sys_bpf+0x1a61/0x49d0  \n __x64_sys_bpf+0x7d/0xc0  \n do_syscall_64+0xc1/0x1d0  \n entry_SYSCALL_64_after_hwframe+0x77/0x7f \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-29T18:48:31.000000Z"}