Vuldb Updates

A vulnerability labeled as problematic has been found in Linux Kernel up to 5.18.2. Affected by this issue is the function bug_on of the file fs/ext4/inode.c of the component ext4. The manipulation results in allocation of resources. This vulnerability is known as CVE-2022-49347. Access to the local network is required for this attack. No exploit is available. The affected component should be upgraded.

A vulnerability has been found in Linux Kernel up to 5.18.3 and classified as problematic. Affected is the function tcp_mtu_probe. This manipulation causes information disclosure. This vulnerability is registered as CVE-2022-49330. The attack requires access to the local network. No exploit is available. The affected component should be upgraded.

A vulnerability was found in Linux Kernel up to 5.15.46/5.17.14/5.18.3. It has been declared as problematic. Impacted is an unknown function of the component TCP. The manipulation results in information disclosure. This vulnerability is reported as CVE-2022-49325. The attacker must have access to the local network to execute the attack. No exploit exists. It is recommended to upgrade the affected component.

A vulnerability has been found in Linux Kernel up to 5.4.197/5.10.121/5.15.46/5.17.14/5.18.3 and classified as critical. This affects the function zynqmp_dma_alloc/free_chan_resources of the component zynqmp_dma. Performing a manipulation results in buffer overflow. This vulnerability is cataloged as CVE-2022-49320. The attack must originate from the local network. There is no exploit available. The affected component should be upgraded.

A vulnerability was found in Linux Kernel up to 5.15.31/5.16.17/5.17.0. It has been rated as problematic. Impacted is the function access_ok. This manipulation of the argument size causes integer overflow. This vulnerability is tracked as CVE-2022-49289. The attack is only possible within the local network. No exploit exists. Upgrading the affected component is advised.

A vulnerability was found in Linux Kernel up to 5.4.187/5.10.108/5.15.31/5.16.17/5.17.0. It has been classified as problematic. This vulnerability affects the function try_get_ops of the file tpm-space.c. The manipulation of the argument tpm_mutex leads to null pointer dereference. This vulnerability is referenced as CVE-2022-49286. The attack needs to be initiated within the local network. No exploit is available. Upgrading the affected component is recommended.

A vulnerability has been found in Linux Kernel up to 5.17.0 and classified as problematic. The impacted element is the function vmalloc. This manipulation causes allocation of resources. This vulnerability is handled as CVE-2022-49292. The attack can only be done within the local network. There is not any exploit available. The affected component should be upgraded.

A vulnerability, which was classified as critical, has been found in Linux Kernel up to 5.10.109/5.15.32/5.16.18/5.17.1. Affected is the function rproc_coredump_write. This manipulation causes integer underflow. This vulnerability is handled as CVE-2022-49278. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.

A vulnerability was found in Linux Kernel up to 5.15.53/5.17.1 and classified as problematic. This affects the function to_i2c_client. Executing a manipulation can lead to null pointer dereference. The identification of this vulnerability is CVE-2022-49285. The attack needs to be done within the local network. There is no exploit available. It is suggested to upgrade the affected component.

A vulnerability marked as critical has been reported in Linux Kernel up to 5.15.32/5.16.18/5.17.1. Affected by this issue is some unknown functionality of the component sysfb_create_simplefb. This manipulation causes memory leak. This vulnerability is registered as CVE-2022-49283. The attack requires access to the local network. No exploit is available. It is suggested to upgrade the affected component.

A vulnerability, which was classified as problematic, was found in Linux Kernel up to 5.15.32/5.16.18/5.17.1. The affected element is the function dqi_gqlock of the component ocfs2. The manipulation results in uninitialized pointer. This vulnerability is known as CVE-2022-49274. Access to the local network is required for this attack. No exploit is available. You should upgrade the affected component.

A vulnerability, which was classified as critical, was found in Linux Kernel up to 5.4.188/5.10.109/5.15.32/5.16.18/5.17.1. This affects the function snd_dma_free_pages. The manipulation results in null pointer dereference. This vulnerability was named CVE-2022-49268. The attack needs to be approached within the local network. There is no available exploit. You should upgrade the affected component.

A vulnerability was found in Linux Kernel up to 5.10.109/5.15.32/5.16.18/5.17.1 and classified as critical. Affected is the function smb2_ioctl_query_info. Such manipulation of the argument argv[] leads to memory corruption. This vulnerability is referenced as CVE-2022-49271. The attack needs to be initiated within the local network. No exploit is available. It is suggested to upgrade the affected component.

A vulnerability was found in Linux Kernel up to 5.10.109/5.15.32/5.16.18/5.17.1. It has been rated as critical. This affects the function to_user. The manipulation leads to improper update of reference count. This vulnerability is listed as CVE-2022-49272. The attack must be carried out from within the local network. There is no available exploit. Upgrading the affected component is advised.

A vulnerability has been found in Linux Kernel up to 5.4.188/5.10.109/5.15.32/5.16.18/5.17.1 and classified as critical. This issue affects the function brcmf_pcie_setup. The manipulation leads to memory leak. This vulnerability is uniquely identified as CVE-2022-49263. The attack can only be initiated within the local network. No exploit exists. The affected component should be upgraded.

A vulnerability was found in Free5GC up to 4.1.0 and classified as problematic. This affects an unknown function of the component PFCP UDP Endpoint. Such manipulation leads to denial of service. This vulnerability is uniquely identified as CVE-2026-2525. The attack can be launched remotely. Moreover, an exploit is present.

A vulnerability was found in Wavlink WL-WN579A3 up to 20210219. It has been classified as critical. This impacts the function multi_ssid of the file /cgi-bin/wireless.cgi. Performing a manipulation of the argument SSID2G2 results in command injection. This vulnerability was named CVE-2026-2526. The attack may be initiated remotely. In addition, an exploit is available. The vendor was contacted early about this disclosure but did not respond in any way.

A vulnerability was found in Wavlink WL-WN579A3 up to 20210219. It has been declared as critical. Affected is an unknown function of the file /cgi-bin/login.cgi. Executing a manipulation of the argument key can lead to command injection. The identification of this vulnerability is CVE-2026-2527. The attack may be launched remotely. Furthermore, there is an exploit available. The vendor was contacted early about this disclosure but did not respond in any way.

A vulnerability was found in Wavlink WL-WN579A3 up to 20210219. It has been rated as critical. Affected by this vulnerability is the function Delete_Mac_list of the file /cgi-bin/wireless.cgi. The manipulation of the argument delete_list leads to command injection. This vulnerability is referenced as CVE-2026-2528. Remote exploitation of the attack is possible. Furthermore, an exploit is available. The vendor was contacted early about this disclosure but did not respond in any way.

A vulnerability categorized as critical has been discovered in Wavlink WL-WN579A3 up to 20210219. Affected by this issue is the function DeleteMac of the file /cgi-bin/wireless.cgi. The manipulation of the argument delete_list results in command injection. This vulnerability is identified as CVE-2026-2529. The attack can be executed remotely. There is not any exploit available. The vendor was contacted early about this disclosure but did not respond in any way.