xamxte/cve-to-cwe huggingface dataset:
CVE-2022-49211: In the Linux kernel, the following vulnerability has been resolved:  mips: cdmm: Fix refcount leak in mips_cdmm_phys_base  The of_find_compatible_node() function returns a node pointer with refcount incremented, We should use of_node_put() on it when done Add the missing of_node_put() to release the refcount.
CVE-2022-49212: In the Linux kernel, the following vulnerability has been resolved:  mtd: rawnand: atmel: fix refcount issue in atmel_nand_controller_init  The reference counting issue happens in several error handling paths on a refcounted object "nc->dmac". In these paths, the function simply returns the error code, forgetting to balance the reference count of "nc->dmac", increased earlier by dma_request_channel(), which may cause refcount leaks.  Fix it by decrementing the refcount of specific object in those error paths.
CVE-2022-49213: In the Linux kernel, the following vulnerability has been resolved:  ath10k: Fix error handling in ath10k_setup_msa_resources  The device_node pointer is returned by of_parse_phandle() with refcount incremented. We should use of_node_put() on it when done.  This function only calls of_node_put() in the regular path. And it will cause refcount leak in error path.
CVE-2022-49216: In the Linux kernel, the following vulnerability has been resolved:  drm/tegra: Fix reference leak in tegra_dsi_ganged_probe  The reference taken by 'of_find_device_by_node()' must be released when not needed anymore. Add put_device() call to fix this.
CVE-2022-49229: In the Linux kernel, the following vulnerability has been resolved:  ptp: unregister virtual clocks when unregistering physical clock.  When unregistering a physical clock which has some virtual clocks, unregister the virtual clocks with it.  This fixes the following oops, which can be triggered by unloading a driver providing a PTP clock when it has enabled virtual clocks:  BUG: unable to handle page fault for address: ffffffffc04fc4d8 Oops: 0000 [#1] PREEMPT SMP NOPTI RIP: 0010:ptp_vclock_read+0x31/0xb0 Call Trace:  timecounter_read+0xf/0x50  ptp_vclock_refresh+0x2c/0x50  ? ptp_clock_release+0x40/0x40  ptp_aux_kworker+0x17/0x30  kthread_worker_fn+0x9b/0x240  ? kthread_should_park+0x30/0x30  kthread+0xe2/0x110  ? kthread_complete_and_exit+0x20/0x20  ret_from_fork+0x22/0x30
CVE-2022-49237: In the Linux kernel, the following vulnerability has been resolved:  ath11k: add missing of_node_put() to avoid leak  The node pointer is returned by of_find_node_by_type() or of_parse_phandle() with refcount incremented. Calling of_node_put() to aovid the refcount leak.
CVE-2022-49239: In the Linux kernel, the following vulnerability has been resolved:  ASoC: codecs: wcd934x: Add missing of_node_put() in wcd934x_codec_parse_data  The device_node pointer is returned by of_parse_phandle()  with refcount incremented. We should use of_node_put() on it when done. This is similar to commit 64b92de9603f ("ASoC: wcd9335: fix a leaked reference by adding missing of_node_put")
CVE-2022-49240: In the Linux kernel, the following vulnerability has been resolved:  ASoC: mediatek: mt8195: Fix error handling in mt8195_mt6359_rt1019_rt5682_dev_probe  The device_node pointer is returned by of_parse_phandle()  with refcount incremented. We should use of_node_put() on it when done.  This function only calls of_node_put() in the regular path. And it will cause refcount leak in error path.
CVE-2022-49241: In the Linux kernel, the following vulnerability has been resolved:  ASoC: atmel: Fix error handling in sam9x5_wm8731_driver_probe  The device_node pointer is returned by of_parse_phandle()  with refcount incremented. We should use of_node_put() on it when done.  This function only calls of_node_put() in the regular path. And it will cause refcount leak in error path.
CVE-2022-49242: In the Linux kernel, the following vulnerability has been resolved:  ASoC: mxs: Fix error handling in mxs_sgtl5000_probe  This function only calls of_node_put() in the regular path. And it will cause refcount leak in error paths. For example, when codec_np is NULL, saif_np[0] and saif_np[1] are not NULL, it will cause leaks.  of_node_put() will check if the node pointer is NULL, so we can call it directly to release the refcount of regular pointers.
CVE-2022-49243: In the Linux kernel, the following vulnerability has been resolved:  ASoC: atmel: Add missing of_node_put() in at91sam9g20ek_audio_probe  This node pointer is returned by of_parse_phandle() with refcount incremented in this function. Calling of_node_put() to avoid the refcount leak.
CVE-2022-49244: In the Linux kernel, the following vulnerability has been resolved:  ASoC: mediatek: mt8192-mt6359: Fix error handling in mt8192_mt6359_dev_probe  The device_node pointer is returned by of_parse_phandle()  with refcount incremented. We should use of_node_put() on it when done.  This function only calls of_node_put() in the regular path. And it will cause refcount leak in error paths. Fix this by calling of_node_put() in error handling too.
CVE-2022-49245: In the Linux kernel, the following vulnerability has been resolved:  ASoC: rockchip: Fix PM usage reference of rockchip_i2s_tdm_resume  pm_runtime_get_sync will increment pm usage counter even it failed. Forgetting to putting operation will result in reference leak here. We fix it by replacing it with pm_runtime_resume_and_get to keep usage counter balanced.
CVE-2022-49246: In the Linux kernel, the following vulnerability has been resolved:  ASoC: atmel: Fix error handling in snd_proto_probe  The device_node pointer is returned by of_parse_phandle()  with refcount incremented. We should use of_node_put() on it when done.  This function only calls of_node_put() in the regular path. And it will cause refcount leak in error paths. Fix this by calling of_node_put() in error handling too.
CVE-2022-49265: In the Linux kernel, the following vulnerability has been resolved:  PM: domains: Fix sleep-in-atomic bug caused by genpd_debug_remove()  When a genpd with GENPD_FLAG_IRQ_SAFE gets removed, the following sleep-in-atomic bug will be seen, as genpd_debug_remove() will be called with a spinlock being held.  [    0.029183] BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:1460 [    0.029204] in_atomic(): 1, irqs_disabled(): 128, non_block: 0, pid: 1, name: swapper/0 [    0.029219] preempt_count: 1, expected: 0 [    0.029230] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.17.0-rc4+ #489 [    0.029245] Hardware name: Thundercomm TurboX CM2290 (DT) [    0.029256] Call trace: [    0.029265]  dump_backtrace.part.0+0xbc/0xd0 [    0.029285]  show_stack+0x3c/0xa0 [    0.029298]  dump_stack_lvl+0x7c/0xa0 [    0.029311]  dump_stack+0x18/0x34 [    0.029323]  __might_resched+0x10c/0x13c [    0.029338]  __might_sleep+0x4c/0x80 [    0.029351]  down_read+0x24/0xd0 [    0.029363]  lookup_one_len_unlocked+0x9c/0xcc [    0.029379]  lookup_positive_unlocked+0x10/0x50 [    0.029392]  debugfs_lookup+0x68/0xac [    0.029406]  genpd_remove.part.0+0x12c/0x1b4 [    0.029419]  of_genpd_remove_last+0xa8/0xd4 [    0.029434]  psci_cpuidle_domain_probe+0x174/0x53c [    0.029449]  platform_probe+0x68/0xe0 [    0.029462]  really_probe+0x190/0x430 [    0.029473]  __driver_probe_device+0x90/0x18c [    0.029485]  driver_probe_device+0x40/0xe0 [    0.029497]  __driver_attach+0xf4/0x1d0 [    0.029508]  bus_for_each_dev+0x70/0xd0 [    0.029523]  driver_attach+0x24/0x30 [    0.029534]  bus_add_driver+0x164/0x22c [    0.029545]  driver_register+0x78/0x130 [    0.029556]  __platform_driver_register+0x28/0x34 [    0.029569]  psci_idle_init_domains+0x1c/0x28 [    0.029583]  do_one_initcall+0x50/0x1b0 [    0.029595]  kernel_init_freeable+0x214/0x280 [    0.029609]  kernel_init+0x2c/0x13c [    0.029622]  ret_from_fork+0x10/0x20  It doesn't seem necessary to call genpd_debug_remove() with the lock, so move it out from locking to fix the problem.
CVE-2022-49269: In the Linux kernel, the following vulnerability has been resolved:  can: isotp: sanitize CAN ID checks in isotp_bind()  Syzbot created an environment that lead to a state machine status that can not be reached with a compliant CAN ID address configuration. The provided address information consisted of CAN ID 0x6000001 and 0xC28001 which both boil down to 11 bit CAN IDs 0x001 in sending and receiving.  Sanitize the SFF/EFF CAN ID values before performing the address checks.
CVE-2022-49293: In the Linux kernel, the following vulnerability has been resolved:  netfilter: nf_tables: initialize registers in nft_do_chain()  Initialize registers to avoid stack leak into userspace.
CVE-2022-49308: In the Linux kernel, the following vulnerability has been resolved:  extcon: Modify extcon device to be created after driver data is set  Currently, someone can invoke the sysfs such as state_show() intermittently before dev_set_drvdata() is done. And it can be a cause of kernel Oops because of edev is Null at that time. So modified the driver registration to after setting drviver data.  - Oops's backtrace.  Backtrace: [<c067865c>] (state_show) from [<c05222e8>] (dev_attr_show) [<c05222c0>] (dev_attr_show) from [<c02c66e0>] (sysfs_kf_seq_show) [<c02c6648>] (sysfs_kf_seq_show) from [<c02c496c>] (kernfs_seq_show) [<c02c4938>] (kernfs_seq_show) from [<c025e2a0>] (seq_read) [<c025e11c>] (seq_read) from [<c02c50a0>] (kernfs_fop_read) [<c02c5064>] (kernfs_fop_read) from [<c0231cac>] (__vfs_read) [<c0231c5c>] (__vfs_read) from [<c0231ee0>] (vfs_read) [<c0231e34>] (vfs_read) from [<c0232464>] (ksys_read) [<c02323f0>] (ksys_read) from [<c02324fc>] (sys_read) [<c02324e4>] (sys_read) from [<c00091d0>] (__sys_trace_return)
CVE-2022-49310: In the Linux kernel, the following vulnerability has been resolved:  char: xillybus: fix a refcount leak in cleanup_dev()  usb_get_dev is called in xillyusb_probe. So it is better to call usb_put_dev before xdev is released.
CVE-2022-49314: In the Linux kernel, the following vulnerability has been resolved:  tty: Fix a possible resource leak in icom_probe  When pci_read_config_dword failed, call pci_release_regions() and pci_disable_device() to recycle the resource previously allocated.
CVE-2022-49318: In the Linux kernel, the following vulnerability has been resolved:  f2fs: remove WARN_ON in f2fs_is_valid_blkaddr  Syzbot triggers two WARNs in f2fs_is_valid_blkaddr and __is_bitmap_valid. For example, in f2fs_is_valid_blkaddr, if type is DATA_GENERIC_ENHANCE or DATA_GENERIC_ENHANCE_READ, it invokes WARN_ON if blkaddr is not in the right range. The call trace is as follows:   f2fs_get_node_info+0x45f/0x1070  read_node_page+0x577/0x1190  __get_node_page.part.0+0x9e/0x10e0  __get_node_page  f2fs_get_node_page+0x109/0x180  do_read_inode  f2fs_iget+0x2a5/0x58b0  f2fs_fill_super+0x3b39/0x7ca0  Fix these two WARNs by replacing WARN_ON with dump_stack.
CVE-2022-49324: In the Linux kernel, the following vulnerability has been resolved:  mips: cpc: Fix refcount leak in mips_cpc_default_phys_base  Add the missing of_node_put() to release the refcount incremented by of_find_compatible_node().
CVE-2022-49336: In the Linux kernel, the following vulnerability has been resolved:  drm/etnaviv: check for reaped mapping in etnaviv_iommu_unmap_gem  When the mapping is already reaped the unmap must be a no-op, as we would otherwise try to remove the mapping twice, corrupting the involved data structures.
CVE-2022-49342: In the Linux kernel, the following vulnerability has been resolved:  net: ethernet: bgmac: Fix refcount leak in bcma_mdio_mii_register  of_get_child_by_name() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak.
CVE-2022-49343: In the Linux kernel, the following vulnerability has been resolved:  ext4: avoid cycles in directory h-tree  A maliciously corrupted filesystem can contain cycles in the h-tree stored inside a directory. That can easily lead to the kernel corrupting tree nodes that were already verified under its hands while doing a node split and consequently accessing unallocated memory. Fix the problem by verifying traversed block numbers are unique.
CVE-2022-49346: In the Linux kernel, the following vulnerability has been resolved:  net: dsa: lantiq_gswip: Fix refcount leak in gswip_gphy_fw_list  Every iteration of for_each_available_child_of_node() decrements the reference count of the previous node. when breaking early from a for_each_available_child_of_node() loop, we need to explicitly call of_node_put() on the gphy_fw_np. Add missing of_node_put() to avoid refcount leak.
CVE-2022-49348: In the Linux kernel, the following vulnerability has been resolved:  ext4: filter out EXT4_FC_REPLAY from on-disk superblock field s_state  The EXT4_FC_REPLAY bit in sbi->s_mount_state is used to indicate that we are in the middle of replay the fast commit journal.  This was actually a mistake, since the sbi->s_mount_info is initialized from es->s_state.  Arguably s_mount_state is misleadingly named, but the name is historical --- s_mount_state and s_state dates back to ext2.  What should have been used is the ext4_{set,clear,test}_mount_flag() inline functions, which sets EXT4_MF_* bits in sbi->s_mount_flags.  The problem with using EXT4_FC_REPLAY is that a maliciously corrupted superblock could result in EXT4_FC_REPLAY getting set in s_mount_state.  This bypasses some sanity checks, and this can trigger a BUG() in ext4_es_cache_extent().  As a easy-to-backport-fix, filter out the EXT4_FC_REPLAY bit for now.  We should eventually transition away from EXT4_FC_REPLAY to something like EXT4_MF_REPLAY.
CVE-2022-49351: In the Linux kernel, the following vulnerability has been resolved:  net: altera: Fix refcount leak in altera_tse_mdio_create  Every iteration of for_each_child_of_node() decrements the reference count of the previous node. When break from a for_each_child_of_node() loop, we need to explicitly call of_node_put() on the child node when not need anymore. Add missing of_node_put() to avoid refcount leak.
CVE-2022-49354: In the Linux kernel, the following vulnerability has been resolved:  ata: pata_octeon_cf: Fix refcount leak in octeon_cf_probe  of_find_device_by_node() takes reference, we should use put_device() to release it when not need anymore. Add missing put_device() to avoid refcount leak.
CVE-2022-49361: In the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to do sanity check for inline inode  Yanming reported a kernel bug in Bugzilla kernel [1], which can be reproduced. The bug message is:  The kernel message is shown below:  kernel BUG at fs/inode.c:611! Call Trace:  evict+0x282/0x4e0  __dentry_kill+0x2b2/0x4d0  dput+0x2dd/0x720  do_renameat2+0x596/0x970  __x64_sys_rename+0x78/0x90  do_syscall_64+0x3b/0x90  [1] https://bugzilla.kernel.org/show_bug.cgi?id=215895  The bug is due to fuzzed inode has both inline_data and encrypted flags. During f2fs_evict_inode(), as the inode was deleted by rename(), it will cause inline data conversion due to conflicting flags. The page cache will be polluted and the panic will be triggered in clear_inode().  Try fixing the bug by doing more sanity checks for inline data inode in sanity_check_inode().
CVE-2022-49363: In the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to do sanity check on block address in f2fs_do_zero_range()  As Yanming reported in bugzilla:  https://bugzilla.kernel.org/show_bug.cgi?id=215894  I have encountered a bug in F2FS file system in kernel v5.17.  I have uploaded the system call sequence as case.c, and a fuzzed image can be found in google net disk  The kernel should enable CONFIG_KASAN=y and CONFIG_KASAN_INLINE=y. You can reproduce the bug by running the following commands:  kernel BUG at fs/f2fs/segment.c:2291! Call Trace:  f2fs_invalidate_blocks+0x193/0x2d0  f2fs_fallocate+0x2593/0x4a70  vfs_fallocate+0x2a5/0xac0  ksys_fallocate+0x35/0x70  __x64_sys_fallocate+0x8e/0xf0  do_syscall_64+0x3b/0x90  entry_SYSCALL_64_after_hwframe+0x44/0xae  The root cause is, after image was fuzzed, block mapping info in inode will be inconsistent with SIT table, so in f2fs_fallocate(), it will cause panic when updating SIT with invalid blkaddr.  Let's fix the issue by adding sanity check on block address before updating SIT table with it.
CVE-2022-49366: In the Linux kernel, the following vulnerability has been resolved:  ksmbd: fix reference count leak in smb_check_perm_dacl()  The issue happens in a specific path in smb_check_perm_dacl(). When "id" and "uid" have the same value, the function simply jumps out of the loop without decrementing the reference count of the object "posix_acls", which is increased by get_acl() earlier. This may result in memory leaks.  Fix it by decreasing the reference count of "posix_acls" before jumping to label "check_access_bits".
CVE-2022-49367: In the Linux kernel, the following vulnerability has been resolved:  net: dsa: mv88e6xxx: Fix refcount leak in mv88e6xxx_mdios_register  of_get_child_by_name() returns a node pointer with refcount incremented, we should use of_node_put() on it when done.  mv88e6xxx_mdio_register() pass the device node to of_mdiobus_register(). We don't need the device node after it.  Add missing of_node_put() to avoid refcount leak.
CVE-2022-49373: In the Linux kernel, the following vulnerability has been resolved:  watchdog: ts4800_wdt: Fix refcount leak in ts4800_wdt_probe  of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. Add  missing of_node_put() in some error paths.
CVE-2022-49382: In the Linux kernel, the following vulnerability has been resolved:  soc: rockchip: Fix refcount leak in rockchip_grf_init  of_find_matching_node_and_match returns a node pointer with refcount incremented, we should use of_node_put() on it when done. Add missing of_node_put() to avoid refcount leak.
CVE-2022-49386: In the Linux kernel, the following vulnerability has been resolved:  net: ethernet: ti: am65-cpsw-nuss: Fix some refcount leaks  of_get_child_by_name() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. am65_cpsw_init_cpts() and am65_cpsw_nuss_probe() don't release the refcount in error case. Add missing of_node_put() to avoid refcount leak.
CVE-2022-49389: In the Linux kernel, the following vulnerability has been resolved:  usb: usbip: fix a refcount leak in stub_probe()  usb_get_dev() is called in stub_device_alloc(). When stub_probe() fails after that, usb_put_dev() needs to be called to release the reference.  Fix this by moving usb_put_dev() to sdev_free error path handling.  Find this by code review.
CVE-2022-49398: In the Linux kernel, the following vulnerability has been resolved:  usb: dwc3: gadget: Replace list_for_each_entry_safe() if using giveback  The list_for_each_entry_safe() macro saves the current item (n) and the item after (n+1), so that n can be safely removed without corrupting the list.  However, when traversing the list and removing items using gadget giveback, the DWC3 lock is briefly released, allowing other routines to execute.  There is a situation where, while items are being removed from the cancelled_list using dwc3_gadget_ep_cleanup_cancelled_requests(), the pullup disable routine is running in parallel (due to UDC unbind).  As the cleanup routine removes n, and the pullup disable removes n+1, once the cleanup retakes the DWC3 lock, it references a request who was already removed/handled.  With list debug enabled, this leads to a panic. Ensure all instances of the macro are replaced where gadget giveback is used.  Example call stack:  Thread#1: __dwc3_gadget_ep_set_halt() - CLEAR HALT   -> dwc3_gadget_ep_cleanup_cancelled_requests()     ->list_for_each_entry_safe()     ->dwc3_gadget_giveback(n)       ->dwc3_gadget_del_and_unmap_request()- n deleted[cancelled_list]       ->spin_unlock       ->Thread#2 executes       ...     ->dwc3_gadget_giveback(n+1)       ->Already removed!  Thread#2: dwc3_gadget_pullup()   ->waiting for dwc3 spin_lock   ...   ->Thread#1 released lock   ->dwc3_stop_active_transfers()     ->dwc3_remove_requests()       ->fetches n+1 item from cancelled_list (n removed by Thread#1)       ->dwc3_gadget_giveback()         ->dwc3_gadget_del_and_unmap_request()- n+1 deleted[cancelled_list]         ->spin_unlock
CVE-2022-49399: In the Linux kernel, the following vulnerability has been resolved:  tty: goldfish: Use tty_port_destroy() to destroy port  In goldfish_tty_probe(), the port initialized through tty_port_init() should be destroyed in error paths.In goldfish_tty_remove(), qtty->port also should be destroyed or else might leak resources.  Fix the above by calling tty_port_destroy().
CVE-2022-49405: In the Linux kernel, the following vulnerability has been resolved:  staging: r8188eu: prevent ->Ssid overflow in rtw_wx_set_scan()  This code has a check to prevent read overflow but it needs another check to prevent writing beyond the end of the ->Ssid[] array.
CVE-2022-49415: In the Linux kernel, the following vulnerability has been resolved:  ipmi:ipmb: Fix refcount leak in ipmi_ipmb_probe  of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. Add missing of_node_put() to avoid refcount leak.
CVE-2022-49420: In the Linux kernel, the following vulnerability has been resolved:  net: annotate races around sk->sk_bound_dev_if  UDP sendmsg() is lockless, and reads sk->sk_bound_dev_if while this field can be changed by another thread.  Adds minimal annotations to avoid KCSAN splats for UDP. Following patches will add more annotations to potential lockless readers.  BUG: KCSAN: data-race in __ip6_datagram_connect / udpv6_sendmsg  write to 0xffff888136d47a94 of 4 bytes by task 7681 on cpu 0:  __ip6_datagram_connect+0x6e2/0x930 net/ipv6/datagram.c:221  ip6_datagram_connect+0x2a/0x40 net/ipv6/datagram.c:272  inet_dgram_connect+0x107/0x190 net/ipv4/af_inet.c:576  __sys_connect_file net/socket.c:1900 [inline]  __sys_connect+0x197/0x1b0 net/socket.c:1917  __do_sys_connect net/socket.c:1927 [inline]  __se_sys_connect net/socket.c:1924 [inline]  __x64_sys_connect+0x3d/0x50 net/socket.c:1924  do_syscall_x64 arch/x86/entry/common.c:50 [inline]  do_syscall_64+0x2b/0x50 arch/x86/entry/common.c:80  entry_SYSCALL_64_after_hwframe+0x44/0xae  read to 0xffff888136d47a94 of 4 bytes by task 7670 on cpu 1:  udpv6_sendmsg+0xc60/0x16e0 net/ipv6/udp.c:1436  inet6_sendmsg+0x5f/0x80 net/ipv6/af_inet6.c:652  sock_sendmsg_nosec net/socket.c:705 [inline]  sock_sendmsg net/socket.c:725 [inline]  ____sys_sendmsg+0x39a/0x510 net/socket.c:2413  ___sys_sendmsg net/socket.c:2467 [inline]  __sys_sendmmsg+0x267/0x4c0 net/socket.c:2553  __do_sys_sendmmsg net/socket.c:2582 [inline]  __se_sys_sendmmsg net/socket.c:2579 [inline]  __x64_sys_sendmmsg+0x53/0x60 net/socket.c:2579  do_syscall_x64 arch/x86/entry/common.c:50 [inline]  do_syscall_64+0x2b/0x50 arch/x86/entry/common.c:80  entry_SYSCALL_64_after_hwframe+0x44/0xae  value changed: 0x00000000 -> 0xffffff9b  Reported by Kernel Concurrency Sanitizer on: CPU: 1 PID: 7670 Comm: syz-executor.3 Tainted: G        W         5.18.0-rc1-syzkaller-dirty #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011  I chose to not add Fixes: tag because race has minor consequences and stable teams busy enough.
CVE-2022-49421: In the Linux kernel, the following vulnerability has been resolved:  video: fbdev: clcdfb: Fix refcount leak in clcdfb_of_vram_setup  of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore.  Add missing of_node_put() to avoid refcount leak.
CVE-2022-49422: In the Linux kernel, the following vulnerability has been resolved:  dmaengine: idxd: Fix the error handling path in idxd_cdev_register()  If a call to alloc_chrdev_region() fails, the already allocated resources are leaking.  Add the needed error handling path to fix the leak.
CVE-2022-49431: In the Linux kernel, the following vulnerability has been resolved:  powerpc/iommu: Add missing of_node_put in iommu_init_early_dart  The device_node pointer is returned by of_find_compatible_node with refcount incremented. We should use of_node_put() to avoid the refcount leak.