xamxte/cve-to-cwe huggingface dataset:
CVE-2022-49432: In the Linux kernel, the following vulnerability has been resolved:  powerpc/xics: fix refcount leak in icp_opal_init()  The of_find_compatible_node() function returns a node pointer with refcount incremented, use of_node_put() on it when done.
CVE-2022-49437: In the Linux kernel, the following vulnerability has been resolved:  powerpc/xive: Fix refcount leak in xive_spapr_init  of_find_compatible_node() 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-49438: In the Linux kernel, the following vulnerability has been resolved:  Input: sparcspkr - fix refcount leak in bbc_beep_probe  of_find_node_by_path() calls of_find_node_opts_by_path(), which 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-49439: In the Linux kernel, the following vulnerability has been resolved:  powerpc/fsl_rio: Fix refcount leak in fsl_rio_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-49447: In the Linux kernel, the following vulnerability has been resolved:  ARM: hisi: Add missing of_node_put after of_find_compatible_node  of_find_compatible_node  will increment the refcount of the returned device_node. Calling of_node_put() to avoid the refcount leak
CVE-2022-49454: In the Linux kernel, the following vulnerability has been resolved:  PCI: mediatek: Fix refcount leak in mtk_pcie_subsys_powerup()  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-49457: In the Linux kernel, the following vulnerability has been resolved:  ARM: versatile: Add missing of_node_put in dcscb_init  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.
CVE-2022-49462: In the Linux kernel, the following vulnerability has been resolved:  drm/msm/a6xx: Fix refcount leak in a6xx_gpu_init  of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore.  a6xx_gmu_init() passes the node to of_find_device_by_node() and of_dma_configure(), of_find_device_by_node() will takes its reference, of_dma_configure() doesn't need the node after usage.  Add missing of_node_put() to avoid refcount leak.
CVE-2022-49463: In the Linux kernel, the following vulnerability has been resolved:  thermal/drivers/imx_sc_thermal: Fix refcount leak in imx_sc_thermal_probe  of_find_node_by_name() 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-49466: In the Linux kernel, the following vulnerability has been resolved:  regulator: scmi: Fix refcount leak in scmi_regulator_probe  of_find_node_by_name() 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-49473: In the Linux kernel, the following vulnerability has been resolved:  ASoC: ti: j721e-evm: Fix refcount leak in j721e_soc_probe_*  of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not needed anymore. Add missing of_node_put() to avoid refcount leak.
CVE-2022-49477: In the Linux kernel, the following vulnerability has been resolved:  ASoC: samsung: Fix refcount leak in aries_audio_probe  of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. If extcon_find_edev_by_node() fails, it doesn't call of_node_put() Calling of_node_put() after extcon_find_edev_by_node() to fix this.
CVE-2022-49480: In the Linux kernel, the following vulnerability has been resolved:  ASoC: imx-hdmi: Fix refcount leak in imx_hdmi_probe  of_find_device_by_node() takes reference, we should use put_device() to release it. when devm_kzalloc() fails, it doesn't have a put_device(), it will cause refcount leak. Add missing put_device() to fix this.
CVE-2022-49481: In the Linux kernel, the following vulnerability has been resolved:  regulator: pfuze100: Fix refcount leak in pfuze_parse_regulators_dt  of_node_get() returns a node with refcount incremented. Calling of_node_put() to drop the reference when not needed anymore.
CVE-2022-49482: In the Linux kernel, the following vulnerability has been resolved:  ASoC: mxs-saif: Fix refcount leak in mxs_saif_probe  of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when done.
CVE-2022-49486: In the Linux kernel, the following vulnerability has been resolved:  ASoC: fsl: Fix refcount leak in imx_sgtl5000_probe  of_find_i2c_device_by_node() takes a reference, In error paths, we should call put_device() to drop the reference to aviod refount leak.
CVE-2022-49504: In the Linux kernel, the following vulnerability has been resolved:  scsi: lpfc: Inhibit aborts if external loopback plug is inserted  After running a short external loopback test, when the external loopback is removed and a normal cable inserted that is directly connected to a target device, the system oops in the llpfc_set_rrq_active() routine.  When the loopback was inserted an FLOGI was transmit. As we're looped back, we receive the FLOGI request. The FLOGI is ABTS'd as we recognize the same wppn thus understand it's a loopback. However, as the ABTS sends address information the port is not set to (fffffe), the ABTS is dropped on the wire. A short 1 frame loopback test is run and completes before the ABTS times out. The looback is unplugged and the new cable plugged in, and the an FLOGI to the new device occurs and completes. Due to a mixup in ref counting the completion of the new FLOGI releases the fabric ndlp. Then the original ABTS completes and references the released ndlp generating the oops.  Correct by no-op'ing the ABTS when in loopback mode (it will be dropped anyway). Added a flag to track the mode to recognize when it should be no-op'd.
CVE-2022-49506: In the Linux kernel, the following vulnerability has been resolved:  drm/mediatek: Add vblank register/unregister callback functions  We encountered a kernel panic issue that callback data will be NULL when it's using in ovl irq handler. There is a timing issue between mtk_disp_ovl_irq_handler() and mtk_ovl_disable_vblank().  To resolve this issue, we use the flow to register/unregister vblank cb: - Register callback function and callback data when crtc creates. - Unregister callback function and callback data when crtc destroies.  With this solution, we can assure callback data will not be NULL when vblank is disable.
CVE-2022-49511: In the Linux kernel, the following vulnerability has been resolved:  fbdev: defio: fix the pagelist corruption  Easily hit the below list corruption: == list_add corruption. prev->next should be next (ffffffffc0ceb090), but was ffffec604507edc8. (prev=ffffec604507edc8). WARNING: CPU: 65 PID: 3959 at lib/list_debug.c:26 __list_add_valid+0x53/0x80 CPU: 65 PID: 3959 Comm: fbdev Tainted: G     U RIP: 0010:__list_add_valid+0x53/0x80 Call Trace:  <TASK>  fb_deferred_io_mkwrite+0xea/0x150  do_page_mkwrite+0x57/0xc0  do_wp_page+0x278/0x2f0  __handle_mm_fault+0xdc2/0x1590  handle_mm_fault+0xdd/0x2c0  do_user_addr_fault+0x1d3/0x650  exc_page_fault+0x77/0x180  ? asm_exc_page_fault+0x8/0x30  asm_exc_page_fault+0x1e/0x30 RIP: 0033:0x7fd98fc8fad1 ==  Figure out the race happens when one process is adding &page->lru into the pagelist tail in fb_deferred_io_mkwrite(), another process is re-initializing the same &page->lru in fb_deferred_io_fault(), which is not protected by the lock.  This fix is to init all the page lists one time during initialization, it not only fixes the list corruption, but also avoids INIT_LIST_HEAD() redundantly.  V2: change "int i" to "unsigned int i" (Geert Uytterhoeven)
CVE-2022-49512: In the Linux kernel, the following vulnerability has been resolved:  mtd: rawnand: denali: Use managed device resources  All of the resources used by this driver has managed interfaces, so use them. Otherwise we will get the following splat:  [    4.472703] denali-nand-pci 0000:00:05.0: timeout while waiting for irq 0x1000 [    4.474071] denali-nand-pci: probe of 0000:00:05.0 failed with error -5 [    4.473538] nand: No NAND device found [    4.474068] BUG: unable to handle page fault for address: ffffc90005000410 [    4.475169] #PF: supervisor write access in kernel mode [    4.475579] #PF: error_code(0x0002) - not-present page [    4.478362] RIP: 0010:iowrite32+0x9/0x50 [    4.486068] Call Trace: [    4.486269]  <IRQ> [    4.486443]  denali_isr+0x15b/0x300 [denali] [    4.486788]  ? denali_direct_write+0x50/0x50 [denali] [    4.487189]  __handle_irq_event_percpu+0x161/0x3b0 [    4.487571]  handle_irq_event+0x7d/0x1b0 [    4.487884]  handle_fasteoi_irq+0x2b0/0x770 [    4.488219]  __common_interrupt+0xc8/0x1b0 [    4.488549]  common_interrupt+0x9a/0xc0
CVE-2022-49513: In the Linux kernel, the following vulnerability has been resolved:  cpufreq: governor: Use kobject release() method to free dbs_data  The struct dbs_data embeds a struct gov_attr_set and the struct gov_attr_set embeds a kobject. Since every kobject must have a release() method and we can't use kfree() to free it directly, so introduce cpufreq_dbs_data_release() to release the dbs_data via the kobject::release() method. This fixes the calltrace like below:    ODEBUG: free active (active state 0) object type: timer_list hint: delayed_work_timer_fn+0x0/0x34   WARNING: CPU: 12 PID: 810 at lib/debugobjects.c:505 debug_print_object+0xb8/0x100   Modules linked in:   CPU: 12 PID: 810 Comm: sh Not tainted 5.16.0-next-20220120-yocto-standard+ #536   Hardware name: Marvell OcteonTX CN96XX board (DT)   pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)   pc : debug_print_object+0xb8/0x100   lr : debug_print_object+0xb8/0x100   sp : ffff80001dfcf9a0   x29: ffff80001dfcf9a0 x28: 0000000000000001 x27: ffff0001464f0000   x26: 0000000000000000 x25: ffff8000090e3f00 x24: ffff80000af60210   x23: ffff8000094dfb78 x22: ffff8000090e3f00 x21: ffff0001080b7118   x20: ffff80000aeb2430 x19: ffff800009e8f5e0 x18: 0000000000000000   x17: 0000000000000002 x16: 00004d62e58be040 x15: 013590470523aff8   x14: ffff8000090e1828 x13: 0000000001359047 x12: 00000000f5257d14   x11: 0000000000040591 x10: 0000000066c1ffea x9 : ffff8000080d15e0   x8 : ffff80000a1765a8 x7 : 0000000000000000 x6 : 0000000000000001   x5 : ffff800009e8c000 x4 : ffff800009e8c760 x3 : 0000000000000000   x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff0001474ed040   Call trace:    debug_print_object+0xb8/0x100    __debug_check_no_obj_freed+0x1d0/0x25c    debug_check_no_obj_freed+0x24/0xa0    kfree+0x11c/0x440    cpufreq_dbs_governor_exit+0xa8/0xac    cpufreq_exit_governor+0x44/0x90    cpufreq_set_policy+0x29c/0x570    store_scaling_governor+0x110/0x154    store+0xb0/0xe0    sysfs_kf_write+0x58/0x84    kernfs_fop_write_iter+0x12c/0x1c0    new_sync_write+0xf0/0x18c    vfs_write+0x1cc/0x220    ksys_write+0x74/0x100    __arm64_sys_write+0x28/0x3c    invoke_syscall.constprop.0+0x58/0xf0    do_el0_svc+0x70/0x170    el0_svc+0x54/0x190    el0t_64_sync_handler+0xa4/0x130    el0t_64_sync+0x1a0/0x1a4   irq event stamp: 189006   hardirqs last  enabled at (189005): [<ffff8000080849d0>] finish_task_switch.isra.0+0xe0/0x2c0   hardirqs last disabled at (189006): [<ffff8000090667a4>] el1_dbg+0x24/0xa0   softirqs last  enabled at (188966): [<ffff8000080106d0>] __do_softirq+0x4b0/0x6a0   softirqs last disabled at (188957): [<ffff80000804a618>] __irq_exit_rcu+0x108/0x1a4  [ rjw: Because can be freed by the gov_attr_set_put() in   cpufreq_dbs_governor_exit() now, it is also necessary to put the   invocation of the governor ->exit() callback into the new   cpufreq_dbs_data_release() function. ]
CVE-2022-49517: In the Linux kernel, the following vulnerability has been resolved:  ASoC: mediatek: Fix missing of_node_put in mt2701_wm8960_machine_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-49533: In the Linux kernel, the following vulnerability has been resolved:  ath11k: Change max no of active probe SSID and BSSID to fw capability  The maximum number of SSIDs in a for active probe requests is currently reported as 16 (WLAN_SCAN_PARAMS_MAX_SSID) when registering the driver. The scan_req_params structure only has the capacity to hold 10 SSIDs. This leads to a buffer overflow which can be triggered from wpa_supplicant in userspace. When copying the SSIDs into the scan_req_params structure in the ath11k_mac_op_hw_scan route, it can overwrite the extraie pointer.  Firmware supports 16 ssid * 4 bssid, for each ssid 4 bssid combo probe request will be sent, so totally 64 probe requests supported. So set both max ssid and bssid to 16 and 4 respectively. Remove the redundant macros of ssid and bssid.  Tested-on: IPQ8074 hw2.0 AHB WLAN.HK.2.7.0.1-01300-QCAHKSWPL_SILICONZ-1
CVE-2022-49556: In the Linux kernel, the following vulnerability has been resolved:  KVM: SVM: Use kzalloc for sev ioctl interfaces to prevent kernel data leak  For some sev ioctl interfaces, the length parameter that is passed maybe less than or equal to SEV_FW_BLOB_MAX_SIZE, but larger than the data that PSP firmware returns. In this case, kmalloc will allocate memory that is the size of the input rather than the size of the data. Since PSP firmware doesn't fully overwrite the allocated buffer, these sev ioctl interface may return uninitialized kernel slab memory.
CVE-2022-49558: In the Linux kernel, the following vulnerability has been resolved:  netfilter: nf_tables: double hook unregistration in netns path  __nft_release_hooks() is called from pre_netns exit path which unregisters the hooks, then the NETDEV_UNREGISTER event is triggered which unregisters the hooks again.  [  565.221461] WARNING: CPU: 18 PID: 193 at net/netfilter/core.c:495 __nf_unregister_net_hook+0x247/0x270 [...] [  565.246890] CPU: 18 PID: 193 Comm: kworker/u64:1 Tainted: G            E     5.18.0-rc7+ #27 [  565.253682] Workqueue: netns cleanup_net [  565.257059] RIP: 0010:__nf_unregister_net_hook+0x247/0x270 [...] [  565.297120] Call Trace: [  565.300900]  <TASK> [  565.304683]  nf_tables_flowtable_event+0x16a/0x220 [nf_tables] [  565.308518]  raw_notifier_call_chain+0x63/0x80 [  565.312386]  unregister_netdevice_many+0x54f/0xb50  Unregister and destroy netdev hook from netns pre_exit via kfree_rcu so the NETDEV_UNREGISTER path see unregistered hooks.
CVE-2022-49559: In the Linux kernel, the following vulnerability has been resolved:  KVM: x86: Drop WARNs that assert a triple fault never "escapes" from L2  Remove WARNs that sanity check that KVM never lets a triple fault for L2 escape and incorrectly end up in L1.  In normal operation, the sanity check is perfectly valid, but it incorrectly assumes that it's impossible for userspace to induce KVM_REQ_TRIPLE_FAULT without bouncing through KVM_RUN (which guarantees kvm_check_nested_state() will see and handle the triple fault).  The WARN can currently be triggered if userspace injects a machine check while L2 is active and CR4.MCE=0.  And a future fix to allow save/restore of KVM_REQ_TRIPLE_FAULT, e.g. so that a synthesized triple fault isn't lost on migration, will make it trivially easy for userspace to trigger the WARN.  Clearing KVM_REQ_TRIPLE_FAULT when forcibly leaving guest mode is tempting, but wrong, especially if/when the request is saved/restored, e.g. if userspace restores events (including a triple fault) and then restores nested state (which may forcibly leave guest mode).  Ignoring the fact that KVM doesn't currently provide the necessary APIs, it's userspace's responsibility to manage pending events during save/restore.    ------------[ cut here ]------------   WARNING: CPU: 7 PID: 1399 at arch/x86/kvm/vmx/nested.c:4522 nested_vmx_vmexit+0x7fe/0xd90 [kvm_intel]   Modules linked in: kvm_intel kvm irqbypass   CPU: 7 PID: 1399 Comm: state_test Not tainted 5.17.0-rc3+ #808   Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015   RIP: 0010:nested_vmx_vmexit+0x7fe/0xd90 [kvm_intel]   Call Trace:    <TASK>    vmx_leave_nested+0x30/0x40 [kvm_intel]    vmx_set_nested_state+0xca/0x3e0 [kvm_intel]    kvm_arch_vcpu_ioctl+0xf49/0x13e0 [kvm]    kvm_vcpu_ioctl+0x4b9/0x660 [kvm]    __x64_sys_ioctl+0x83/0xb0    do_syscall_64+0x3b/0xc0    entry_SYSCALL_64_after_hwframe+0x44/0xae    </TASK>   ---[ end trace 0000000000000000 ]---
CVE-2022-49561: In the Linux kernel, the following vulnerability has been resolved:  netfilter: conntrack: re-fetch conntrack after insertion  In case the conntrack is clashing, insertion can free skb->_nfct and set skb->_nfct to the already-confirmed entry.  This wasn't found before because the conntrack entry and the extension space used to free'd after an rcu grace period, plus the race needs events enabled to trigger.
CVE-2022-49591: In the Linux kernel, the following vulnerability has been resolved:  net: dsa: microchip: ksz_common: Fix refcount leak bug  In ksz_switch_register(), we should call of_node_put() for the reference returned by of_get_child_by_name() which has increased the refcount.
CVE-2022-49609: In the Linux kernel, the following vulnerability has been resolved:  power/reset: arm-versatile: Fix refcount leak in versatile_reboot_probe  of_find_matching_node_and_match() 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-49620: In the Linux kernel, the following vulnerability has been resolved:  net: tipc: fix possible refcount leak in tipc_sk_create()  Free sk in case tipc_sk_insert() fails.
CVE-2022-49621: In the Linux kernel, the following vulnerability has been resolved:  cpufreq: pmac32-cpufreq: Fix refcount leak bug  In pmac_cpufreq_init_MacRISC3(), we need to add corresponding of_node_put() for the three node pointers whose refcount have been incremented by of_find_node_by_name().
CVE-2022-49644: In the Linux kernel, the following vulnerability has been resolved:  drm/i915: fix a possible refcount leak in intel_dp_add_mst_connector()  If drm_connector_init fails, intel_connector_free will be called to take care of proper free. So it is necessary to drop the refcount of port before intel_connector_free.  (cherry picked from commit cea9ed611e85d36a05db52b6457bf584b7d969e2)
CVE-2022-49652: In the Linux kernel, the following vulnerability has been resolved:  dmaengine: ti: Fix refcount leak in ti_dra7_xbar_route_allocate  of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not needed anymore.  Add missing of_node_put() in to fix this.
CVE-2022-49656: In the Linux kernel, the following vulnerability has been resolved:  ARM: meson: Fix refcount leak in meson_smp_prepare_cpus  of_find_compatible_node() 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-49662: In the Linux kernel, the following vulnerability has been resolved:  ipv6: fix lockdep splat in in6_dump_addrs()  As reported by syzbot, we should not use rcu_dereference() when rcu_read_lock() is not held.  WARNING: suspicious RCU usage 5.19.0-rc2-syzkaller #0 Not tainted  net/ipv6/addrconf.c:5175 suspicious rcu_dereference_check() usage!  other info that might help us debug this:  rcu_scheduler_active = 2, debug_locks = 1 1 lock held by syz-executor326/3617:  #0: ffffffff8d5848e8 (rtnl_mutex){+.+.}-{3:3}, at: netlink_dump+0xae/0xc20 net/netlink/af_netlink.c:2223  stack backtrace: CPU: 0 PID: 3617 Comm: syz-executor326 Not tainted 5.19.0-rc2-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace:  <TASK>  __dump_stack lib/dump_stack.c:88 [inline]  dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106  in6_dump_addrs+0x12d1/0x1790 net/ipv6/addrconf.c:5175  inet6_dump_addr+0x9c1/0xb50 net/ipv6/addrconf.c:5300  netlink_dump+0x541/0xc20 net/netlink/af_netlink.c:2275  __netlink_dump_start+0x647/0x900 net/netlink/af_netlink.c:2380  netlink_dump_start include/linux/netlink.h:245 [inline]  rtnetlink_rcv_msg+0x73e/0xc90 net/core/rtnetlink.c:6046  netlink_rcv_skb+0x153/0x420 net/netlink/af_netlink.c:2501  netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline]  netlink_unicast+0x543/0x7f0 net/netlink/af_netlink.c:1345  netlink_sendmsg+0x917/0xe10 net/netlink/af_netlink.c:1921  sock_sendmsg_nosec net/socket.c:714 [inline]  sock_sendmsg+0xcf/0x120 net/socket.c:734  ____sys_sendmsg+0x6eb/0x810 net/socket.c:2492  ___sys_sendmsg+0xf3/0x170 net/socket.c:2546  __sys_sendmsg net/socket.c:2575 [inline]  __do_sys_sendmsg net/socket.c:2584 [inline]  __se_sys_sendmsg net/socket.c:2582 [inline]  __x64_sys_sendmsg+0x132/0x220 net/socket.c:2582  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+0x46/0xb0
CVE-2022-49668: In the Linux kernel, the following vulnerability has been resolved:  PM / devfreq: exynos-ppmu: Fix refcount leak in of_get_devfreq_events  of_get_child_by_name() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. This function only calls of_node_put() in normal path, missing it in error paths. Add missing of_node_put() to avoid refcount leak.
CVE-2022-49672: In the Linux kernel, the following vulnerability has been resolved:  net: tun: unlink NAPI from device on destruction  Syzbot found a race between tun file and device destruction. NAPIs live in struct tun_file which can get destroyed before the netdev so we have to del them explicitly. The current code is missing deleting the NAPI if the queue was detached first.
CVE-2022-49676: In the Linux kernel, the following vulnerability has been resolved:  memory: samsung: exynos5422-dmc: Fix refcount leak in of_get_dram_timings  of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. This function doesn't call of_node_put() in some error paths. To unify the structure, Add put_node label and goto it on errors.
CVE-2022-49677: In the Linux kernel, the following vulnerability has been resolved:  ARM: cns3xxx: Fix refcount leak in cns3xxx_init  of_find_compatible_node() 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-49678: In the Linux kernel, the following vulnerability has been resolved:  soc: bcm: brcmstb: pm: pm-arm: Fix refcount leak in brcmstb_pm_probe  of_find_matching_node() 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.  In brcmstb_init_sram, it pass dn to of_address_to_resource(), of_address_to_resource() will call of_find_device_by_node() to take reference, so we should release the reference returned by of_find_matching_node().
CVE-2022-49679: In the Linux kernel, the following vulnerability has been resolved:  ARM: Fix refcount leak in axxia_boot_secondary  of_find_compatible_node() 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-49680: In the Linux kernel, the following vulnerability has been resolved:  ARM: exynos: Fix refcount leak in exynos_map_pmu  of_find_matching_node() 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. of_node_put() checks null pointer.
CVE-2022-49681: In the Linux kernel, the following vulnerability has been resolved:  xtensa: xtfpga: Fix refcount leak bug in setup  In machine_setup(), of_find_compatible_node() will return a node pointer with refcount incremented. We should use of_node_put() when it is not used anymore.