xamxte/cve-to-cwe huggingface dataset:
CVE-2022-50862: In the Linux kernel, the following vulnerability has been resolved:  bpf: prevent decl_tag from being referenced in func_proto  Syzkaller was able to hit the following issue:  ------------[ cut here ]------------ WARNING: CPU: 0 PID: 3609 at kernel/bpf/btf.c:1946 btf_type_id_size+0x2d5/0x9d0 kernel/bpf/btf.c:1946 Modules linked in: CPU: 0 PID: 3609 Comm: syz-executor361 Not tainted 6.0.0-syzkaller-02734-g0326074ff465 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022 RIP: 0010:btf_type_id_size+0x2d5/0x9d0 kernel/bpf/btf.c:1946 Code: ef e8 7f 8e e4 ff 41 83 ff 0b 77 28 f6 44 24 10 18 75 3f e8 6d 91 e4 ff 44 89 fe bf 0e 00 00 00 e8 20 8e e4 ff e8 5b 91 e4 ff <0f> 0b 45 31 f6 e9 98 02 00 00 41 83 ff 12 74 18 e8 46 91 e4 ff 44 RSP: 0018:ffffc90003cefb40 EFLAGS: 00010293 RAX: 0000000000000000 RBX: 0000000000000002 RCX: 0000000000000000 RDX: ffff8880259c0000 RSI: ffffffff81968415 RDI: 0000000000000005 RBP: ffff88801270ca00 R08: 0000000000000005 R09: 000000000000000e R10: 0000000000000011 R11: 0000000000000000 R12: 0000000000000000 R13: 0000000000000011 R14: ffff888026ee6424 R15: 0000000000000011 FS:  000055555641b300(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000f2e258 CR3: 000000007110e000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:  <TASK>  btf_func_proto_check kernel/bpf/btf.c:4447 [inline]  btf_check_all_types kernel/bpf/btf.c:4723 [inline]  btf_parse_type_sec kernel/bpf/btf.c:4752 [inline]  btf_parse kernel/bpf/btf.c:5026 [inline]  btf_new_fd+0x1926/0x1e70 kernel/bpf/btf.c:6892  bpf_btf_load kernel/bpf/syscall.c:4324 [inline]  __sys_bpf+0xb7d/0x4cf0 kernel/bpf/syscall.c:5010  __do_sys_bpf kernel/bpf/syscall.c:5069 [inline]  __se_sys_bpf kernel/bpf/syscall.c:5067 [inline]  __x64_sys_bpf+0x75/0xb0 kernel/bpf/syscall.c:5067  do_syscall_x64 arch/x86/entry/common.c:50 [inline]  do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80  entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f0fbae41c69 Code: 28 c3 e8 2a 14 00 00 66 2e 0f 1f 84 00 00 00 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffc8aeb6228 EFLAGS: 00000246 ORIG_RAX: 0000000000000141 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f0fbae41c69 RDX: 0000000000000020 RSI: 0000000020000140 RDI: 0000000000000012 RBP: 00007f0fbae05e10 R08: 0000000000000000 R09: 0000000000000000 R10: 00000000ffffffff R11: 0000000000000246 R12: 00007f0fbae05ea0 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000  </TASK>  Looks like it tries to create a func_proto which return type is decl_tag. For the details, see Martin's spot on analysis in [0].  0: https://lore.kernel.org/bpf/CAKH8qBuQDLva_hHxxBuZzyAcYNO4ejhovz6TQeVSk8HY-2SO6g@mail.gmail.com/T/#mea6524b3fcd6298347432226e81b1e6155efc62c
CVE-2022-50863: In the Linux kernel, the following vulnerability has been resolved:  wifi: rtw89: free unused skb to prevent memory leak  This avoid potential memory leak under power saving mode.
CVE-2022-50864: In the Linux kernel, the following vulnerability has been resolved:  nilfs2: fix shift-out-of-bounds due to too large exponent of block size  If field s_log_block_size of superblock data is corrupted and too large, init_nilfs() and load_nilfs() still can trigger a shift-out-of-bounds warning followed by a kernel panic (if panic_on_warn is set):   shift exponent 38973 is too large for 32-bit type 'int'  Call Trace:   <TASK>   dump_stack_lvl+0xcd/0x134   ubsan_epilogue+0xb/0x50   __ubsan_handle_shift_out_of_bounds.cold.12+0x17b/0x1f5   init_nilfs.cold.11+0x18/0x1d [nilfs2]   nilfs_mount+0x9b5/0x12b0 [nilfs2]   ...  This fixes the issue by adding and using a new helper function for getting block size with sanity check.
CVE-2022-50865: In the Linux kernel, the following vulnerability has been resolved:  tcp: fix a signed-integer-overflow bug in tcp_add_backlog()  The type of sk_rcvbuf and sk_sndbuf in struct sock is int, and in tcp_add_backlog(), the variable limit is caculated by adding sk_rcvbuf, sk_sndbuf and 64 * 1024, it may exceed the max value of int and overflow. This patch reduces the limit budget by halving the sndbuf to solve this issue since ACK packets are much smaller than the payload.
CVE-2022-50866: In the Linux kernel, the following vulnerability has been resolved:  ASoC: pxa: fix null-pointer dereference in filter()  kasprintf() would return NULL pointer when kmalloc() fail to allocate. Need to check the return pointer before calling strcmp().
CVE-2022-50868: In the Linux kernel, the following vulnerability has been resolved:  hwrng: amd - Fix PCI device refcount leak  for_each_pci_dev() is implemented by pci_get_device(). The comment of pci_get_device() says that it will increase the reference count for the returned pci_dev and also decrease the reference count for the input pci_dev @from if it is not NULL.  If we break for_each_pci_dev() loop with pdev not NULL, we need to call pci_dev_put() to decrease the reference count. Add the missing pci_dev_put() for the normal and error path.
CVE-2022-50869: In the Linux kernel, the following vulnerability has been resolved:  fs/ntfs3: Fix slab-out-of-bounds in r_page  When PAGE_SIZE is 64K, if read_log_page is called by log_read_rst for the first time, the size of *buffer would be equal to DefaultLogPageSize(4K).But for *buffer operations like memcpy, if the memory area size(n) which being assigned to buffer is larger than 4K (log->page_size(64K) or bytes(64K-page_off)), it will cause an out of boundary error.  Call trace:   [...]   kasan_report+0x44/0x130   check_memory_region+0xf8/0x1a0   memcpy+0xc8/0x100   ntfs_read_run_nb+0x20c/0x460   read_log_page+0xd0/0x1f4   log_read_rst+0x110/0x75c   log_replay+0x1e8/0x4aa0   ntfs_loadlog_and_replay+0x290/0x2d0   ntfs_fill_super+0x508/0xec0   get_tree_bdev+0x1fc/0x34c   [...]  Fix this by setting variable r_page to NULL in log_read_rst.
CVE-2022-50872: In the Linux kernel, the following vulnerability has been resolved:  ARM: OMAP2+: Fix memory leak in realtime_counter_init()  The "sys_clk" resource is malloced by clk_get(), it is not released when the function return.
CVE-2022-50873: In the Linux kernel, the following vulnerability has been resolved:  vdpa/vp_vdpa: fix kfree a wrong pointer in vp_vdpa_remove  In vp_vdpa_remove(), the code kfree(&vp_vdpa_mgtdev->mgtdev.id_table) uses a reference of pointer as the argument of kfree, which is the wrong pointer and then may hit crash like this:  Unable to handle kernel paging request at virtual address 00ffff003363e30c Internal error: Oops: 96000004 [#1] SMP Call trace:  rb_next+0x20/0x5c  ext4_readdir+0x494/0x5c4 [ext4]  iterate_dir+0x168/0x1b4  __se_sys_getdents64+0x68/0x170  __arm64_sys_getdents64+0x24/0x30  el0_svc_common.constprop.0+0x7c/0x1bc  do_el0_svc+0x2c/0x94  el0_svc+0x20/0x30  el0_sync_handler+0xb0/0xb4  el0_sync+0x160/0x180 Code: 54000220 f9400441 b4000161 aa0103e0 (f9400821) SMP: stopping secondary CPUs Starting crashdump kernel...
CVE-2022-50874: In the Linux kernel, the following vulnerability has been resolved:  RDMA/erdma: Fix refcount leak in erdma_mmap  rdma_user_mmap_entry_get() take reference, we should release it when not need anymore, add the missing rdma_user_mmap_entry_put() in the error path to fix it.
CVE-2022-50875: In the Linux kernel, the following vulnerability has been resolved:  of: overlay: fix null pointer dereferencing in find_dup_cset_node_entry() and find_dup_cset_prop()  When kmalloc() fail to allocate memory in kasprintf(), fn_1 or fn_2 will be NULL, and strcmp() will cause null pointer dereference.
CVE-2022-50876: In the Linux kernel, the following vulnerability has been resolved:  usb: musb: Fix musb_gadget.c rxstate overflow bug  The usb function device call musb_gadget_queue() adds the passed request to musb_ep::req_list,If the (request->length > musb_ep->packet_sz) and (is_buffer_mapped(req) return false),the rxstate() will copy all data in fifo to request->buf which may cause request->buf out of bounds.  Fix it by add the length check : fifocnt = min_t(unsigned, request->length - request->actual, fifocnt);
CVE-2022-50877: In the Linux kernel, the following vulnerability has been resolved:  net: broadcom: bcm4908_enet: update TX stats after actual transmission  Queueing packets doesn't guarantee their transmission. Update TX stats after hardware confirms consuming submitted data.  This also fixes a possible race and NULL dereference. bcm4908_enet_start_xmit() could try to access skb after freeing it in the bcm4908_enet_poll_tx().
CVE-2022-50878: In the Linux kernel, the following vulnerability has been resolved:  gpu: lontium-lt9611: Fix NULL pointer dereference in lt9611_connector_init()  A NULL check for bridge->encoder shows that it may be NULL, but it already been dereferenced on all paths leading to the check. 812 if (!bridge->encoder) {  Dereference the pointer bridge->encoder. 810 drm_connector_attach_encoder(&lt9611->connector, bridge->encoder);
CVE-2022-50879: In the Linux kernel, the following vulnerability has been resolved:  objtool: Fix SEGFAULT  find_insn() will return NULL in case of failure. Check insn in order to avoid a kernel Oops for NULL pointer dereference.
CVE-2022-50882: In the Linux kernel, the following vulnerability has been resolved:  media: uvcvideo: Fix memory leak in uvc_gpio_parse  Previously the unit buffer was allocated before checking the IRQ for privacy GPIO. In case of error, the unit buffer was leaked.  Allocate the unit buffer after the IRQ to avoid it.  Addresses-Coverity-ID: 1474639 ("Resource leak")
CVE-2022-50884: In the Linux kernel, the following vulnerability has been resolved:  drm: Prevent drm_copy_field() to attempt copying a NULL pointer  There are some struct drm_driver fields that are required by drivers since drm_copy_field() attempts to copy them to user-space via DRM_IOCTL_VERSION.  But it can be possible that a driver has a bug and did not set some of the fields, which leads to drm_copy_field() attempting to copy a NULL pointer:  [ +10.395966] Unable to handle kernel access to user memory outside uaccess routines at virtual address 0000000000000000 [  +0.010955] Mem abort info: [  +0.002835]   ESR = 0x0000000096000004 [  +0.003872]   EC = 0x25: DABT (current EL), IL = 32 bits [  +0.005395]   SET = 0, FnV = 0 [  +0.003113]   EA = 0, S1PTW = 0 [  +0.003182]   FSC = 0x04: level 0 translation fault [  +0.004964] Data abort info: [  +0.002919]   ISV = 0, ISS = 0x00000004 [  +0.003886]   CM = 0, WnR = 0 [  +0.003040] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000115dad000 [  +0.006536] [0000000000000000] pgd=0000000000000000, p4d=0000000000000000 [  +0.006925] Internal error: Oops: 96000004 [#1] SMP ... [  +0.011113] pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [  +0.007061] pc : __pi_strlen+0x14/0x150 [  +0.003895] lr : drm_copy_field+0x30/0x1a4 [  +0.004156] sp : ffff8000094b3a50 [  +0.003355] x29: ffff8000094b3a50 x28: ffff8000094b3b70 x27: 0000000000000040 [  +0.007242] x26: ffff443743c2ba00 x25: 0000000000000000 x24: 0000000000000040 [  +0.007243] x23: ffff443743c2ba00 x22: ffff8000094b3b70 x21: 0000000000000000 [  +0.007241] x20: 0000000000000000 x19: ffff8000094b3b90 x18: 0000000000000000 [  +0.007241] x17: 0000000000000000 x16: 0000000000000000 x15: 0000aaab14b9af40 [  +0.007241] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000 [  +0.007239] x11: 0000000000000000 x10: 0000000000000000 x9 : ffffa524ad67d4d8 [  +0.007242] x8 : 0101010101010101 x7 : 7f7f7f7f7f7f7f7f x6 : 6c6e6263606e7141 [  +0.007239] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000 [  +0.007241] x2 : 0000000000000000 x1 : ffff8000094b3b90 x0 : 0000000000000000 [  +0.007240] Call trace: [  +0.002475]  __pi_strlen+0x14/0x150 [  +0.003537]  drm_version+0x84/0xac [  +0.003448]  drm_ioctl_kernel+0xa8/0x16c [  +0.003975]  drm_ioctl+0x270/0x580 [  +0.003448]  __arm64_sys_ioctl+0xb8/0xfc [  +0.003978]  invoke_syscall+0x78/0x100 [  +0.003799]  el0_svc_common.constprop.0+0x4c/0xf4 [  +0.004767]  do_el0_svc+0x38/0x4c [  +0.003357]  el0_svc+0x34/0x100 [  +0.003185]  el0t_64_sync_handler+0x11c/0x150 [  +0.004418]  el0t_64_sync+0x190/0x194 [  +0.003716] Code: 92402c04 b200c3e8 f13fc09f 5400088c (a9400c02) [  +0.006180] ---[ end trace 0000000000000000 ]---
CVE-2022-50885: In the Linux kernel, the following vulnerability has been resolved:  RDMA/rxe: Fix NULL-ptr-deref in rxe_qp_do_cleanup() when socket create failed  There is a null-ptr-deref when mount.cifs over rdma:    BUG: KASAN: null-ptr-deref in rxe_qp_do_cleanup+0x2f3/0x360 [rdma_rxe]   Read of size 8 at addr 0000000000000018 by task mount.cifs/3046    CPU: 2 PID: 3046 Comm: mount.cifs Not tainted 6.1.0-rc5+ #62   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-1.fc3   Call Trace:    <TASK>    dump_stack_lvl+0x34/0x44    kasan_report+0xad/0x130    rxe_qp_do_cleanup+0x2f3/0x360 [rdma_rxe]    execute_in_process_context+0x25/0x90    __rxe_cleanup+0x101/0x1d0 [rdma_rxe]    rxe_create_qp+0x16a/0x180 [rdma_rxe]    create_qp.part.0+0x27d/0x340    ib_create_qp_kernel+0x73/0x160    rdma_create_qp+0x100/0x230    _smbd_get_connection+0x752/0x20f0    smbd_get_connection+0x21/0x40    cifs_get_tcp_session+0x8ef/0xda0    mount_get_conns+0x60/0x750    cifs_mount+0x103/0xd00    cifs_smb3_do_mount+0x1dd/0xcb0    smb3_get_tree+0x1d5/0x300    vfs_get_tree+0x41/0xf0    path_mount+0x9b3/0xdd0    __x64_sys_mount+0x190/0x1d0    do_syscall_64+0x35/0x80    entry_SYSCALL_64_after_hwframe+0x46/0xb0  The root cause of the issue is the socket create failed in rxe_qp_init_req().  So move the reset rxe_qp_do_cleanup() after the NULL ptr check.
CVE-2022-50886: In the Linux kernel, the following vulnerability has been resolved:  mmc: toshsd: fix return value check of mmc_add_host()  mmc_add_host() may return error, if we ignore its return value, the memory that allocated in mmc_alloc_host() will be leaked and it will lead a kernel crash because of deleting not added device in the remove path.  So fix this by checking the return value and goto error path which will call mmc_free_host(), besides, free_irq() also needs be called.
CVE-2022-50887: In the Linux kernel, the following vulnerability has been resolved:  regulator: core: fix unbalanced of node refcount in regulator_dev_lookup()  I got the the following report:    OF: ERROR: memory leak, expected refcount 1 instead of 2,   of_node_get()/of_node_put() unbalanced - destroy cset entry:   attach overlay node /i2c/pmic@62/regulators/exten  In of_get_regulator(), the node is returned from of_parse_phandle() with refcount incremented, after using it, of_node_put() need be called.
CVE-2022-50888: In the Linux kernel, the following vulnerability has been resolved:  remoteproc: qcom: q6v5: Fix potential null-ptr-deref in q6v5_wcss_init_mmio()  q6v5_wcss_init_mmio() will call platform_get_resource_byname() that may fail and return NULL. devm_ioremap() will use res->start as input, which may causes null-ptr-deref. Check the ret value of platform_get_resource_byname() to avoid the null-ptr-deref.
CVE-2022-50889: In the Linux kernel, the following vulnerability has been resolved:  dm integrity: Fix UAF in dm_integrity_dtr()  Dm_integrity also has the same UAF problem when dm_resume() and dm_destroy() are concurrent.  Therefore, cancelling timer again in dm_integrity_dtr().
CVE-2023-54168: In the Linux kernel, the following vulnerability has been resolved:  RDMA/mlx4: Prevent shift wrapping in set_user_sq_size()  The ucmd->log_sq_bb_count variable is controlled by the user so this shift can wrap.  Fix it by using check_shl_overflow() in the same way that it was done in commit 515f60004ed9 ("RDMA/hns: Prevent undefined behavior in hns_roce_set_user_sq_size()").
CVE-2023-54169: In the Linux kernel, the following vulnerability has been resolved:  net/mlx5e: fix memory leak in mlx5e_ptp_open  When kvzalloc_node or kvzalloc failed in mlx5e_ptp_open, the memory pointed by "c" or "cparams" is not freed, which can lead to a memory leak. Fix by freeing the array in the error path.
CVE-2023-54171: In the Linux kernel, the following vulnerability has been resolved:  tracing: Fix memory leak of iter->temp when reading trace_pipe  kmemleak reports:   unreferenced object 0xffff88814d14e200 (size 256):     comm "cat", pid 336, jiffies 4294871818 (age 779.490s)     hex dump (first 32 bytes):       04 00 01 03 00 00 00 00 08 00 00 00 00 00 00 00  ................       0c d8 c8 9b ff ff ff ff 04 5a ca 9b ff ff ff ff  .........Z......     backtrace:       [<ffffffff9bdff18f>] __kmalloc+0x4f/0x140       [<ffffffff9bc9238b>] trace_find_next_entry+0xbb/0x1d0       [<ffffffff9bc9caef>] trace_print_lat_context+0xaf/0x4e0       [<ffffffff9bc94490>] print_trace_line+0x3e0/0x950       [<ffffffff9bc95499>] tracing_read_pipe+0x2d9/0x5a0       [<ffffffff9bf03a43>] vfs_read+0x143/0x520       [<ffffffff9bf04c2d>] ksys_read+0xbd/0x160       [<ffffffff9d0f0edf>] do_syscall_64+0x3f/0x90       [<ffffffff9d2000aa>] entry_SYSCALL_64_after_hwframe+0x6e/0xd8  when reading file 'trace_pipe', 'iter->temp' is allocated or relocated in trace_find_next_entry() but not freed before 'trace_pipe' is closed.  To fix it, free 'iter->temp' in tracing_release_pipe().
CVE-2023-54173: In the Linux kernel, the following vulnerability has been resolved:  bpf: Disable preemption in bpf_event_output  We received report [1] of kernel crash, which is caused by using nesting protection without disabled preemption.  The bpf_event_output can be called by programs executed by bpf_prog_run_array_cg function that disabled migration but keeps preemption enabled.  This can cause task to be preempted by another one inside the nesting protection and lead eventually to two tasks using same perf_sample_data buffer and cause crashes like:    BUG: kernel NULL pointer dereference, address: 0000000000000001   #PF: supervisor instruction fetch in kernel mode   #PF: error_code(0x0010) - not-present page   ...   ? perf_output_sample+0x12a/0x9a0   ? finish_task_switch.isra.0+0x81/0x280   ? perf_event_output+0x66/0xa0   ? bpf_event_output+0x13a/0x190   ? bpf_event_output_data+0x22/0x40   ? bpf_prog_dfc84bbde731b257_cil_sock4_connect+0x40a/0xacb   ? xa_load+0x87/0xe0   ? __cgroup_bpf_run_filter_sock_addr+0xc1/0x1a0   ? release_sock+0x3e/0x90   ? sk_setsockopt+0x1a1/0x12f0   ? udp_pre_connect+0x36/0x50   ? inet_dgram_connect+0x93/0xa0   ? __sys_connect+0xb4/0xe0   ? udp_setsockopt+0x27/0x40   ? __pfx_udp_push_pending_frames+0x10/0x10   ? __sys_setsockopt+0xdf/0x1a0   ? __x64_sys_connect+0xf/0x20   ? do_syscall_64+0x3a/0x90   ? entry_SYSCALL_64_after_hwframe+0x72/0xdc  Fixing this by disabling preemption in bpf_event_output.  [1] https://github.com/cilium/cilium/issues/26756
CVE-2023-54174: In the Linux kernel, the following vulnerability has been resolved:  vfio: Fix NULL pointer dereference caused by uninitialized group->iommufd  group->iommufd is not initialized for the iommufd_ctx_put()  [20018.331541] BUG: kernel NULL pointer dereference, address: 0000000000000000 [20018.377508] RIP: 0010:iommufd_ctx_put+0x5/0x10 [iommufd] ... [20018.476483] Call Trace: [20018.479214]  <TASK> [20018.481555]  vfio_group_fops_unl_ioctl+0x506/0x690 [vfio] [20018.487586]  __x64_sys_ioctl+0x6a/0xb0 [20018.491773]  ? trace_hardirqs_on+0xc5/0xe0 [20018.496347]  do_syscall_64+0x67/0x90 [20018.500340]  entry_SYSCALL_64_after_hwframe+0x4b/0xb5
CVE-2023-54175: In the Linux kernel, the following vulnerability has been resolved:  i2c: xiic: xiic_xfer(): Fix runtime PM leak on error path  The xiic_xfer() function gets a runtime PM reference when the function is entered. This reference is released when the function is exited. There is currently one error path where the function exits directly, which leads to a leak of the runtime PM reference.  Make sure that this error path also releases the runtime PM reference.
CVE-2023-54178: In the Linux kernel, the following vulnerability has been resolved:  of: unittest: fix null pointer dereferencing in of_unittest_find_node_by_name()  when kmalloc() fail to allocate memory in kasprintf(), name or full_name will be NULL, strcmp() will cause null pointer dereference.
CVE-2023-54179: In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Array index may go out of bound  Klocwork reports array 'vha->host_str' of size 16 may use index value(s) 16..19.  Use snprintf() instead of sprintf().
CVE-2023-54183: In the Linux kernel, the following vulnerability has been resolved:  media: v4l2-core: Fix a potential resource leak in v4l2_fwnode_parse_link()  If fwnode_graph_get_remote_endpoint() fails, 'fwnode' is known to be NULL, so fwnode_handle_put() is a no-op.  Release the reference taken from a previous fwnode_graph_get_port_parent() call instead.  Also handle fwnode_graph_get_port_parent() failures.  In order to fix these issues, add an error handling path to the function and the needed gotos.
CVE-2023-54184: In the Linux kernel, the following vulnerability has been resolved:  scsi: target: iscsit: Free cmds before session free  Commands from recovery entries are freed after session has been closed. That leads to use-after-free at command free or NPE with such call trace:  Time2Retain timer expired for SID: 1, cleaning up iSCSI session. BUG: kernel NULL pointer dereference, address: 0000000000000140 RIP: 0010:sbitmap_queue_clear+0x3a/0xa0 Call Trace:  target_release_cmd_kref+0xd1/0x1f0 [target_core_mod]  transport_generic_free_cmd+0xd1/0x180 [target_core_mod]  iscsit_free_cmd+0x53/0xd0 [iscsi_target_mod]  iscsit_free_connection_recovery_entries+0x29d/0x320 [iscsi_target_mod]  iscsit_close_session+0x13a/0x140 [iscsi_target_mod]  iscsit_check_post_dataout+0x440/0x440 [iscsi_target_mod]  call_timer_fn+0x24/0x140  Move cleanup of recovery enrties to before session freeing.
CVE-2023-54186: In the Linux kernel, the following vulnerability has been resolved:  usb: typec: altmodes/displayport: fix pin_assignment_show  This patch fixes negative indexing of buf array in pin_assignment_show when get_current_pin_assignments returns 0 i.e. no compatible pin assignments are found.  BUG: KASAN: use-after-free in pin_assignment_show+0x26c/0x33c ... Call trace: dump_backtrace+0x110/0x204 dump_stack_lvl+0x84/0xbc print_report+0x358/0x974 kasan_report+0x9c/0xfc __do_kernel_fault+0xd4/0x2d4 do_bad_area+0x48/0x168 do_tag_check_fault+0x24/0x38 do_mem_abort+0x6c/0x14c el1_abort+0x44/0x68 el1h_64_sync_handler+0x64/0xa4 el1h_64_sync+0x78/0x7c pin_assignment_show+0x26c/0x33c dev_attr_show+0x50/0xc0
CVE-2023-54188: In the Linux kernel, the following vulnerability has been resolved:  dmaengine: apple-admac: Fix 'current_tx' not getting freed  In terminate_all we should queue up all submitted descriptors to be freed. We do that for the content of the 'issued' and 'submitted' lists, but the 'current_tx' descriptor falls through the cracks as it's removed from the 'issued' list once it gets assigned to be the current descriptor. Explicitly queue up freeing of the 'current_tx' descriptor to address a memory leak that is otherwise present.
CVE-2023-54189: In the Linux kernel, the following vulnerability has been resolved:  pstore/ram: Add check for kstrdup  Add check for the return value of kstrdup() and return the error if it fails in order to avoid NULL pointer dereference.
CVE-2023-54190: In the Linux kernel, the following vulnerability has been resolved:  leds: led-core: Fix refcount leak in of_led_get()  class_find_device_by_of_node() calls class_find_device(), it will take the reference, use the put_device() to drop the reference when not need anymore.
CVE-2023-54191: In the Linux kernel, the following vulnerability has been resolved:  wifi: mt76: mt7996: fix memory leak in mt7996_mcu_exit  Always purge mcu skb queues in mt7996_mcu_exit routine even if mt7996_firmware_state fails.