CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2022-49865 – ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network
https://notcve.org/view.php?id=CVE-2022-49865
01 May 2025 — In the Linux kernel, the following vulnerability has been resolved: ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network When copying a `struct ifaddrlblmsg` to the network, __ifal_reserved remained uninitialized, resulting in a 1-byte infoleak: BUG: KMSAN: kernel-network-infoleak in __netdev_start_xmit ./include/linux/netdevice.h:4841 __netdev_start_xmit ./include/linux/netdevice.h:4841 netdev_start_xmit ./include/linux/netdevice.h:4857 xmit_one net/core/dev.c:3590 dev_hard_start_xmit+... • https://git.kernel.org/stable/c/2a8cc6c89039e0530a3335954253b76ed0f9339a •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2022-49864 – drm/amdkfd: Fix NULL pointer dereference in svm_migrate_to_ram()
https://notcve.org/view.php?id=CVE-2022-49864
01 May 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Fix NULL pointer dereference in svm_migrate_to_ram() ./drivers/gpu/drm/amd/amdkfd/kfd_migrate.c:985:58-62: ERROR: p is NULL but dereferenced. • https://git.kernel.org/stable/c/3c1bb6187e566143f15dbf0367ae671584aead5b •
CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2022-49863 – can: af_can: fix NULL pointer dereference in can_rx_register()
https://notcve.org/view.php?id=CVE-2022-49863
01 May 2025 — In the Linux kernel, the following vulnerability has been resolved: can: af_can: fix NULL pointer dereference in can_rx_register() It causes NULL pointer dereference when testing as following: (a) use syscall(__NR_socket, 0x10ul, 3ul, 0) to create netlink socket. (b) use syscall(__NR_sendmsg, ...) to create bond link device and vxcan link device, and bind vxcan device to bond device (can also use ifenslave command to bind vxcan device to bond device). (c) use syscall(__NR_socket, 0x1dul, 3ul, 1) to create C... • https://git.kernel.org/stable/c/4ac1feff6ea6495cbfd336f4438a6c6d140544a6 •
CVSS: 5.5EPSS: 0%CPEs: 10EXPL: 0CVE-2022-49862 – tipc: fix the msg->req tlv len check in tipc_nl_compat_name_table_dump_header
https://notcve.org/view.php?id=CVE-2022-49862
01 May 2025 — In the Linux kernel, the following vulnerability has been resolved: tipc: fix the msg->req tlv len check in tipc_nl_compat_name_table_dump_header This is a follow-up for commit 974cb0e3e7c9 ("tipc: fix uninit-value in tipc_nl_compat_name_table_dump") where it should have type casted sizeof(..) to int to work when TLV_GET_DATA_LEN() returns a negative value. syzbot reported a call trace because of it: BUG: KMSAN: uninit-value in ... tipc_nl_compat_name_table_dump+0x841/0xea0 net/tipc/netlink_compat.c:934 __t... • https://git.kernel.org/stable/c/4c559fb7e111077b56f62ccf833a52d8169cde19 •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2022-49861 – dmaengine: mv_xor_v2: Fix a resource leak in mv_xor_v2_remove()
https://notcve.org/view.php?id=CVE-2022-49861
01 May 2025 — In the Linux kernel, the following vulnerability has been resolved: dmaengine: mv_xor_v2: Fix a resource leak in mv_xor_v2_remove() A clk_prepare_enable() call in the probe is not balanced by a corresponding clk_disable_unprepare() in the remove function. Add the missing call. In the Linux kernel, the following vulnerability has been resolved: dmaengine: mv_xor_v2: Fix a resource leak in mv_xor_v2_remove() A clk_prepare_enable() call in the probe is not balanced by a corresponding clk_disable_unprepare() in... • https://git.kernel.org/stable/c/3bdcced41936b054470639c6a76ae033df1074e3 •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2022-49860 – dmaengine: ti: k3-udma-glue: fix memory leak when register device fail
https://notcve.org/view.php?id=CVE-2022-49860
01 May 2025 — In the Linux kernel, the following vulnerability has been resolved: dmaengine: ti: k3-udma-glue: fix memory leak when register device fail If device_register() fails, it should call put_device() to give up reference, the name allocated in dev_set_name() can be freed in callback function kobject_cleanup(). In the Linux kernel, the following vulnerability has been resolved: dmaengine: ti: k3-udma-glue: fix memory leak when register device fail If device_register() fails, it should call put_device() to give up... • https://git.kernel.org/stable/c/5b65781d06ea90ef2f8e51a13352c43c3daa8cdc •
CVSS: 7.8EPSS: 0%CPEs: 3EXPL: 0CVE-2022-49859 – net: lapbether: fix issue of invalid opcode in lapbeth_open()
https://notcve.org/view.php?id=CVE-2022-49859
01 May 2025 — In the Linux kernel, the following vulnerability has been resolved: net: lapbether: fix issue of invalid opcode in lapbeth_open() If lapb_register() failed when lapb device goes to up for the first time, the NAPI is not disabled. As a result, the invalid opcode issue is reported when the lapb device goes to up for the second time. The stack info is as follows: [ 1958.311422][T11356] kernel BUG at net/core/dev.c:6442! [ 1958.312206][T11356] invalid opcode: 0000 [#1] PREEMPT SMP KASAN [ 1958.315979][T11356] R... • https://git.kernel.org/stable/c/514e1150da9cd8d7978d990a353636cf1a7a87c2 •
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2022-49858 – octeontx2-pf: Fix SQE threshold checking
https://notcve.org/view.php?id=CVE-2022-49858
01 May 2025 — In the Linux kernel, the following vulnerability has been resolved: octeontx2-pf: Fix SQE threshold checking Current way of checking available SQE count which is based on HW updated SQB count could result in driver submitting an SQE even before CQE for the previously transmitted SQE at the same index is processed in NAPI resulting losing SKB pointers, hence a leak. Fix this by checking a consumer index which is updated once CQE is processed. In the Linux kernel, the following vulnerability has been resolved... • https://git.kernel.org/stable/c/3ca6c4c882a7f34085b170d93cf0d0e843aa00e6 •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2022-49857 – net: marvell: prestera: fix memory leak in prestera_rxtx_switch_init()
https://notcve.org/view.php?id=CVE-2022-49857
01 May 2025 — In the Linux kernel, the following vulnerability has been resolved: net: marvell: prestera: fix memory leak in prestera_rxtx_switch_init() When prestera_sdma_switch_init() failed, the memory pointed to by sw->rxtx isn't released. Fix it. Only be compiled, not be tested. In the Linux kernel, the following vulnerability has been resolved: net: marvell: prestera: fix memory leak in prestera_rxtx_switch_init() When prestera_sdma_switch_init() failed, the memory pointed to by sw->rxtx isn't released. Fix it. • https://git.kernel.org/stable/c/501ef3066c89d7f9045315e1be58749cf9e6814d •
CVSS: 7.1EPSS: 0%CPEs: 1EXPL: 0CVE-2022-49856 – net: tun: call napi_schedule_prep() to ensure we own a napi
https://notcve.org/view.php?id=CVE-2022-49856
01 May 2025 — In the Linux kernel, the following vulnerability has been resolved: net: tun: call napi_schedule_prep() to ensure we own a napi A recent patch exposed another issue in napi_get_frags() caught by syzbot [1] Before feeding packets to GRO, and calling napi_complete() we must first grab NAPI_STATE_SCHED. [1] WARNING: CPU: 0 PID: 3612 at net/core/dev.c:6076 napi_complete_done+0x45b/0x880 net/core/dev.c:6076 Modules linked in: CPU: 0 PID: 3612 Comm: syz-executor408 Not tainted 6.1.0-rc3-syzkaller-00175-g1118b2049... • https://git.kernel.org/stable/c/07d120aa33cc9d9115753d159f64d20c94458781 •