xamxte/cve-to-cwe huggingface dataset:
CVE-2022-50120: In the Linux kernel, the following vulnerability has been resolved:  remoteproc: imx_rproc: Fix refcount leak in imx_rproc_addr_init  of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not needed anymore. This function has two paths missing of_node_put().
CVE-2022-50121: In the Linux kernel, the following vulnerability has been resolved:  remoteproc: k3-r5: Fix refcount leak in k3_r5_cluster_of_init  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 child node. Add missing of_node_put() to avoid refcount leak.
CVE-2022-50122: In the Linux kernel, the following vulnerability has been resolved:  ASoC: mediatek: mt8173-rt5650: Fix refcount leak in mt8173_rt5650_dev_probe  of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Fix refcount leak in some error paths.
CVE-2022-50123: In the Linux kernel, the following vulnerability has been resolved:  ASoC: mediatek: mt8173: Fix refcount leak in mt8173_rt5650_rt5676_dev_probe  of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Fix missing of_node_put() in error paths.
CVE-2022-50124: In the Linux kernel, the following vulnerability has been resolved:  ASoC: mt6797-mt6351: Fix refcount leak in mt6797_mt6351_dev_probe  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-50125: In the Linux kernel, the following vulnerability has been resolved:  ASoC: cros_ec_codec: Fix refcount leak in cros_ec_codec_platform_probe  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-50139: In the Linux kernel, the following vulnerability has been resolved:  usb: aspeed-vhub: Fix refcount leak bug in ast_vhub_init_desc()  We should call of_node_put() for the reference returned by of_get_child_by_name() which has increased the refcount.
CVE-2022-50141: In the Linux kernel, the following vulnerability has been resolved:  mmc: sdhci-of-esdhc: Fix refcount leak in esdhc_signal_voltage_switch  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-50152: In the Linux kernel, the following vulnerability has been resolved:  usb: ohci-nxp: Fix refcount leak in ohci_hcd_nxp_probe  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-50153: In the Linux kernel, the following vulnerability has been resolved:  usb: host: Fix refcount leak in ehci_hcd_ppc_of_probe  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-50154: In the Linux kernel, the following vulnerability has been resolved:  PCI: mediatek-gen3: Fix refcount leak in mtk_pcie_init_irq_domains()  of_get_child_by_name() returns a node pointer with refcount incremented, so we should use of_node_put() on it when we don't need it anymore.  Add missing of_node_put() to avoid refcount leak.
CVE-2022-50155: In the Linux kernel, the following vulnerability has been resolved:  mtd: parsers: ofpart: Fix refcount leak in bcm4908_partitions_fw_offset  of_find_node_by_path() 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-50157: In the Linux kernel, the following vulnerability has been resolved:  PCI: microchip: Fix refcount leak in mc_pcie_init_irq_domains()  of_get_next_child() returns a node pointer with refcount incremented, so we should use of_node_put() on it when we don't need it anymore.  mc_pcie_init_irq_domains() only calls of_node_put() in the normal path, missing it in some error paths.  Add missing of_node_put() to avoid refcount leak.
CVE-2022-50158: In the Linux kernel, the following vulnerability has been resolved:  mtd: partitions: Fix refcount leak in parse_redboot_of  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-50160: In the Linux kernel, the following vulnerability has been resolved:  mtd: maps: Fix refcount leak in ap_flash_init  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.
CVE-2022-50161: In the Linux kernel, the following vulnerability has been resolved:  mtd: maps: Fix refcount leak in of_flash_probe_versatile  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-50162: In the Linux kernel, the following vulnerability has been resolved:  wifi: libertas: Fix possible refcount leak in if_usb_probe()  usb_get_dev will be called before lbs_get_firmware_async which means that usb_put_dev need to be called when lbs_get_firmware_async fails.
CVE-2022-50171: In the Linux kernel, the following vulnerability has been resolved:  crypto: hisilicon/sec - don't sleep when in softirq  When kunpeng920 encryption driver is used to deencrypt and decrypt packets during the softirq, it is not allowed to use mutex lock. The kernel will report the following error:  BUG: scheduling while atomic: swapper/57/0/0x00000300 Call trace: dump_backtrace+0x0/0x1e4 show_stack+0x20/0x2c dump_stack+0xd8/0x140 __schedule_bug+0x68/0x80 __schedule+0x728/0x840 schedule+0x50/0xe0 schedule_preempt_disabled+0x18/0x24 __mutex_lock.constprop.0+0x594/0x5dc __mutex_lock_slowpath+0x1c/0x30 mutex_lock+0x50/0x60 sec_request_init+0x8c/0x1a0 [hisi_sec2] sec_process+0x28/0x1ac [hisi_sec2] sec_skcipher_crypto+0xf4/0x1d4 [hisi_sec2] sec_skcipher_encrypt+0x1c/0x30 [hisi_sec2] crypto_skcipher_encrypt+0x2c/0x40 crypto_authenc_encrypt+0xc8/0xfc [authenc] crypto_aead_encrypt+0x2c/0x40 echainiv_encrypt+0x144/0x1a0 [echainiv] crypto_aead_encrypt+0x2c/0x40 esp_output_tail+0x348/0x5c0 [esp4] esp_output+0x120/0x19c [esp4] xfrm_output_one+0x25c/0x4d4 xfrm_output_resume+0x6c/0x1fc xfrm_output+0xac/0x3c0 xfrm4_output+0x64/0x130 ip_build_and_send_pkt+0x158/0x20c tcp_v4_send_synack+0xdc/0x1f0 tcp_conn_request+0x7d0/0x994 tcp_v4_conn_request+0x58/0x6c tcp_v6_conn_request+0xf0/0x100 tcp_rcv_state_process+0x1cc/0xd60 tcp_v4_do_rcv+0x10c/0x250 tcp_v4_rcv+0xfc4/0x10a4 ip_protocol_deliver_rcu+0xf4/0x200 ip_local_deliver_finish+0x58/0x70 ip_local_deliver+0x68/0x120 ip_sublist_rcv_finish+0x70/0x94 ip_list_rcv_finish.constprop.0+0x17c/0x1d0 ip_sublist_rcv+0x40/0xb0 ip_list_rcv+0x140/0x1dc __netif_receive_skb_list_core+0x154/0x28c __netif_receive_skb_list+0x120/0x1a0 netif_receive_skb_list_internal+0xe4/0x1f0 napi_complete_done+0x70/0x1f0 gro_cell_poll+0x9c/0xb0 napi_poll+0xcc/0x264 net_rx_action+0xd4/0x21c __do_softirq+0x130/0x358 irq_exit+0x11c/0x13c __handle_domain_irq+0x88/0xf0 gic_handle_irq+0x78/0x2c0 el1_irq+0xb8/0x140 arch_cpu_idle+0x18/0x40 default_idle_call+0x5c/0x1c0 cpuidle_idle_call+0x174/0x1b0 do_idle+0xc8/0x160 cpu_startup_entry+0x30/0x11c secondary_start_kernel+0x158/0x1e4 softirq: huh, entered softirq 3 NET_RX 0000000093774ee4 with preempt_count 00000100, exited with fffffe00?
CVE-2022-50176: In the Linux kernel, the following vulnerability has been resolved:  drm/mcde: Fix refcount leak in mcde_dsi_bind  Every iteration of for_each_available_child_of_node() decrements the reference counter of the previous node. There is no decrement when break out from the loop and results in refcount leak. Add missing of_node_put() to fix this.
CVE-2022-50183: In the Linux kernel, the following vulnerability has been resolved:  drm/meson: encoder_cvbs: Fix refcount leak in meson_encoder_cvbs_init  of_graph_get_remote_node() returns remote device nodepointer with refcount incremented, we should use of_node_put() on it when done. Add missing of_node_put() to avoid refcount leak.
CVE-2022-50184: In the Linux kernel, the following vulnerability has been resolved:  drm/meson: encoder_hdmi: Fix refcount leak in meson_encoder_hdmi_init  of_graph_get_remote_node() returns remote device nodepointer with refcount incremented, we should use of_node_put() on it when done. Add missing of_node_put() to avoid refcount leak.
CVE-2022-50188: In the Linux kernel, the following vulnerability has been resolved:  drm/meson: Fix refcount leak in meson_encoder_hdmi_init  of_find_device_by_node() takes reference, we should use put_device() to release it when not need anymore. Add missing put_device() in error path to avoid refcount leak.
CVE-2022-50191: In the Linux kernel, the following vulnerability has been resolved:  regulator: of: Fix refcount leak bug in of_get_regulation_constraints()  We should call the of_node_put() for the reference returned by of_get_child_by_name() which has increased the refcount.
CVE-2022-50194: In the Linux kernel, the following vulnerability has been resolved:  soc: qcom: aoss: Fix refcount leak in qmp_cooling_devices_register  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 child node. Add missing of_node_put() to avoid refcount leak.
CVE-2022-50196: In the Linux kernel, the following vulnerability has been resolved:  soc: qcom: ocmem: Fix refcount leak in of_get_ocmem  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. of_node_put() will check NULL pointer.
CVE-2022-50197: In the Linux kernel, the following vulnerability has been resolved:  cpufreq: zynq: Fix refcount leak in zynq_get_revision  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-50198: In the Linux kernel, the following vulnerability has been resolved:  ARM: OMAP2+: Fix refcount leak in omap3xxx_prm_late_init  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.
CVE-2022-50199: In the Linux kernel, the following vulnerability has been resolved:  ARM: OMAP2+: Fix refcount leak in omapdss_init_of  omapdss_find_dss_of_node() calls of_find_compatible_node() to get device node. 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() in later error path and normal path.
CVE-2022-50203: In the Linux kernel, the following vulnerability has been resolved:  ARM: OMAP2+: display: Fix refcount leak bug  In omapdss_init_fbdev(), of_find_node_by_name() will return a node pointer with refcount incremented. We should use of_node_put() when it is not used anymore.
CVE-2022-50204: In the Linux kernel, the following vulnerability has been resolved:  ARM: OMAP2+: pdata-quirks: Fix refcount leak bug  In pdata_quirks_init_clocks(), the loop contains of_find_node_by_name() but without corresponding of_node_put().
CVE-2022-50205: In the Linux kernel, the following vulnerability has been resolved:  ext2: Add more validity checks for inode counts  Add checks verifying number of inodes stored in the superblock matches the number computed from number of inodes per group. Also verify we have at least one block worth of inodes per group. This prevents crashes on corrupted filesystems.
CVE-2022-50207: In the Linux kernel, the following vulnerability has been resolved:  ARM: bcm: Fix refcount leak in bcm_kona_smc_init  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.
CVE-2022-50208: In the Linux kernel, the following vulnerability has been resolved:  soc: amlogic: Fix refcount leak in meson-secure-pwrc.c  In meson_secure_pwrc_probe(), there is a refcount leak in one fail path.
CVE-2022-50209: In the Linux kernel, the following vulnerability has been resolved:  meson-mx-socinfo: Fix refcount leak in meson_mx_socinfo_init  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.
CVE-2022-50222: In the Linux kernel, the following vulnerability has been resolved:  tty: vt: initialize unicode screen buffer  syzbot reports kernel infoleak at vcs_read() [1], for buffer can be read immediately after resize operation. Initialize buffer using kzalloc().    ----------   #include <fcntl.h>   #include <unistd.h>   #include <sys/ioctl.h>   #include <linux/fb.h>    int main(int argc, char *argv[])   {     struct fb_var_screeninfo var = { };     const int fb_fd = open("/dev/fb0", 3);     ioctl(fb_fd, FBIOGET_VSCREENINFO, &var);     var.yres = 0x21;     ioctl(fb_fd, FBIOPUT_VSCREENINFO, &var);     return read(open("/dev/vcsu", O_RDONLY), &var, sizeof(var)) == -1;   }   ----------
CVE-2022-50227: In the Linux kernel, the following vulnerability has been resolved:  KVM: x86/xen: Initialize Xen timer only once  Add a check for existing xen timers before initializing a new one.  Currently kvm_xen_init_timer() is called on every KVM_XEN_VCPU_ATTR_TYPE_TIMER, which is causing the following ODEBUG crash when vcpu->arch.xen.timer is already set.  ODEBUG: init active (active state 0) object type: hrtimer hint: xen_timer_callbac0 RIP: 0010:debug_print_object+0x16e/0x250 lib/debugobjects.c:502 Call Trace: __debug_object_init debug_hrtimer_init debug_init hrtimer_init kvm_xen_init_timer kvm_xen_vcpu_set_attr kvm_arch_vcpu_ioctl kvm_vcpu_ioctl vfs_ioctl
CVE-2022-50228: In the Linux kernel, the following vulnerability has been resolved:  KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0  Don't BUG/WARN on interrupt injection due to GIF being cleared, since it's trivial for userspace to force the situation via KVM_SET_VCPU_EVENTS (even if having at least a WARN there would be correct for KVM internally generated injections).    kernel BUG at arch/x86/kvm/svm/svm.c:3386!   invalid opcode: 0000 [#1] SMP   CPU: 15 PID: 926 Comm: smm_test Not tainted 5.17.0-rc3+ #264   Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015   RIP: 0010:svm_inject_irq+0xab/0xb0 [kvm_amd]   Code: <0f> 0b 0f 1f 00 0f 1f 44 00 00 80 3d ac b3 01 00 00 55 48 89 f5 53   RSP: 0018:ffffc90000b37d88 EFLAGS: 00010246   RAX: 0000000000000000 RBX: ffff88810a234ac0 RCX: 0000000000000006   RDX: 0000000000000000 RSI: ffffc90000b37df7 RDI: ffff88810a234ac0   RBP: ffffc90000b37df7 R08: ffff88810a1fa410 R09: 0000000000000000   R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000   R13: ffff888109571000 R14: ffff88810a234ac0 R15: 0000000000000000   FS:  0000000001821380(0000) GS:ffff88846fdc0000(0000) knlGS:0000000000000000   CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033   CR2: 00007f74fc550008 CR3: 000000010a6fe000 CR4: 0000000000350ea0   Call Trace:    <TASK>    inject_pending_event+0x2f7/0x4c0 [kvm]    kvm_arch_vcpu_ioctl_run+0x791/0x17a0 [kvm]    kvm_vcpu_ioctl+0x26d/0x650 [kvm]    __x64_sys_ioctl+0x82/0xb0    do_syscall_64+0x3b/0xc0    entry_SYSCALL_64_after_hwframe+0x44/0xae    </TASK>
CVE-2025-5526: The BuddyPress Docs WordPress plugin before 2.2.5 lacks proper access controls and allows a logged in user to view and download files belonging to another user
CVE-2025-45851: An issue in Hikvision DS-2CD1321-I V5.7.21 build 230819 allows attackers to cause a Denial of Service (DoS) via sending a crafted POST request to the endpoint /ISAPI/Security/challenge. The vendor has stated that upgrading to V5.7.23_SP2 fixes the issue.
CVE-2025-38084: In the Linux kernel, the following vulnerability has been resolved:  mm/hugetlb: unshare page tables during VMA split, not before  Currently, __split_vma() triggers hugetlb page table unsharing through vm_ops->may_split().  This happens before the VMA lock and rmap locks are taken - which is too early, it allows racing VMA-locked page faults in our process and racing rmap walks from other processes to cause page tables to be shared again before we actually perform the split.  Fix it by explicitly calling into the hugetlb unshare logic from __split_vma() in the same place where THP splitting also happens.  At that point, both the VMA and the rmap(s) are write-locked.  An annoying detail is that we can now call into the helper hugetlb_unshare_pmds() from two different locking contexts:  1. from hugetlb_split(), holding:     - mmap lock (exclusively)     - VMA lock     - file rmap lock (exclusively) 2. hugetlb_unshare_all_pmds(), which I think is designed to be able to    call us with only the mmap lock held (in shared mode), but currently    only runs while holding mmap lock (exclusively) and VMA lock  Backporting note: This commit fixes a racy protection that was introduced in commit b30c14cd6102 ("hugetlb: unshare some PMDs when splitting VMAs"); that commit claimed to fix an issue introduced in 5.13, but it should actually also go all the way back.  [jannh@google.com: v2]
CVE-2025-38090: In the Linux kernel, the following vulnerability has been resolved:  drivers/rapidio/rio_cm.c: prevent possible heap overwrite  In  riocm_cdev_ioctl(RIO_CM_CHAN_SEND)    -> cm_chan_msg_send()       -> riocm_ch_send()  cm_chan_msg_send() checks that userspace didn't send too much data but riocm_ch_send() failed to check that userspace sent sufficient data.  The result is that riocm_ch_send() can write to fields in the rio_ch_chan_hdr which were outside the bounds of the space which cm_chan_msg_send() allocated.  Address this by teaching riocm_ch_send() to check that the entire rio_ch_chan_hdr was copied in from userspace.
CVE-2025-38097: In the Linux kernel, the following vulnerability has been resolved:  espintcp: remove encap socket caching to avoid reference leak  The current scheme for caching the encap socket can lead to reference leaks when we try to delete the netns.  The reference chain is: xfrm_state -> enacp_sk -> netns  Since the encap socket is a userspace socket, it holds a reference on the netns. If we delete the espintcp state (through flush or individual delete) before removing the netns, the reference on the socket is dropped and the netns is correctly deleted. Otherwise, the netns may not be reachable anymore (if all processes within the ns have terminated), so we cannot delete the xfrm state to drop its reference on the socket.  This patch results in a small (~2% in my tests) performance regression.  A GC-type mechanism could be added for the socket cache, to clear references if the state hasn't been used "recently", but it's a lot more complex than just not caching the socket.
CVE-2025-38105: In the Linux kernel, the following vulnerability has been resolved:  ALSA: usb-audio: Kill timer properly at removal  The USB-audio MIDI code initializes the timer, but in a rare case, the driver might be freed without the disconnect call.  This leaves the timer in an active state while the assigned object is released via snd_usbmidi_free(), which ends up with a kernel warning when the debug configuration is enabled, as spotted by fuzzer.  For avoiding the problem, put timer_shutdown_sync() at snd_usbmidi_free(), so that the timer can be killed properly. While we're at it, replace the existing timer_delete_sync() at the disconnect callback with timer_shutdown_sync(), too.
CVE-2025-38119: In the Linux kernel, the following vulnerability has been resolved:  scsi: core: ufs: Fix a hang in the error handler  ufshcd_err_handling_prepare() calls ufshcd_rpm_get_sync(). The latter function can only succeed if UFSHCD_EH_IN_PROGRESS is not set because resuming involves submitting a SCSI command and ufshcd_queuecommand() returns SCSI_MLQUEUE_HOST_BUSY if UFSHCD_EH_IN_PROGRESS is set. Fix this hang by setting UFSHCD_EH_IN_PROGRESS after ufshcd_rpm_get_sync() has been called instead of before.  Backtrace: __switch_to+0x174/0x338 __schedule+0x600/0x9e4 schedule+0x7c/0xe8 schedule_timeout+0xa4/0x1c8 io_schedule_timeout+0x48/0x70 wait_for_common_io+0xa8/0x160 //waiting on START_STOP wait_for_completion_io_timeout+0x10/0x20 blk_execute_rq+0xe4/0x1e4 scsi_execute_cmd+0x108/0x244 ufshcd_set_dev_pwr_mode+0xe8/0x250 __ufshcd_wl_resume+0x94/0x354 ufshcd_wl_runtime_resume+0x3c/0x174 scsi_runtime_resume+0x64/0xa4 rpm_resume+0x15c/0xa1c __pm_runtime_resume+0x4c/0x90 // Runtime resume ongoing ufshcd_err_handler+0x1a0/0xd08 process_one_work+0x174/0x808 worker_thread+0x15c/0x490 kthread+0xf4/0x1ec ret_from_fork+0x10/0x20  [ bvanassche: rewrote patch description ]
CVE-2025-38125: In the Linux kernel, the following vulnerability has been resolved:  net: stmmac: make sure that ptp_rate is not 0 before configuring EST  If the ptp_rate recorded earlier in the driver happens to be 0, this bogus value will propagate up to EST configuration, where it will trigger a division by 0.  Prevent this division by 0 by adding the corresponding check and error code.
CVE-2025-38128: In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: MGMT: reject malformed HCI_CMD_SYNC commands  In 'mgmt_hci_cmd_sync()', check whether the size of parameters passed in 'struct mgmt_cp_hci_cmd_sync' matches the total size of the data (i.e. 'sizeof(struct mgmt_cp_hci_cmd_sync)' plus trailing bytes). Otherwise, large invalid 'params_len' will cause 'hci_cmd_sync_alloc()' to do 'skb_put_data()' from an area beyond the one actually passed to 'mgmt_hci_cmd_sync()'.
CVE-2025-38132: In the Linux kernel, the following vulnerability has been resolved:  coresight: holding cscfg_csdev_lock while removing cscfg from csdev  There'll be possible race scenario for coresight config:  CPU0                                          CPU1 (perf enable)                                 load module                                               cscfg_load_config_sets()                                               activate config. // sysfs                                               (sys_active_cnt == 1) ... cscfg_csdev_enable_active_config()   lock(csdev->cscfg_csdev_lock)                                               deactivate config // sysfs                                               (sys_activec_cnt == 0)                                               cscfg_unload_config_sets()   <iterating config_csdev_list>               cscfg_remove_owned_csdev_configs()   // here load config activate by CPU1   unlock(csdev->cscfg_csdev_lock)  iterating config_csdev_list could be raced with config_csdev_list's entry delete.  To resolve this race , hold csdev->cscfg_csdev_lock() while cscfg_remove_owned_csdev_configs()
CVE-2025-38162: In the Linux kernel, the following vulnerability has been resolved:  netfilter: nft_set_pipapo: prevent overflow in lookup table allocation  When calculating the lookup table size, ensure the following multiplication does not overflow:  - desc->field_len[] maximum value is U8_MAX multiplied by   NFT_PIPAPO_GROUPS_PER_BYTE(f) that can be 2, worst case. - NFT_PIPAPO_BUCKETS(f->bb) is 2^8, worst case. - sizeof(unsigned long), from sizeof(*f->lt), lt in   struct nft_pipapo_field.  Then, use check_mul_overflow() to multiply by bucket size and then use check_add_overflow() to the alignment for avx2 (if needed). Finally, add lt_size_check_overflow() helper and use it to consolidate this.  While at it, replace leftover allocation using the GFP_KERNEL to GFP_KERNEL_ACCOUNT for consistency, in pipapo_resize().