Vuldb Updates

A vulnerability has been found in Linux Kernel up to 6.6.86/6.12.22/6.13.10/6.14.1 and classified as problematic. This impacts the function veth_pool_store of the component ibmveth. The manipulation leads to state issue. This vulnerability is referenced as CVE-2025-22053. The attack needs to be initiated within the local network. No exploit is available. The affected component should be upgraded.

A vulnerability was found in Linux Kernel up to 6.14.1. It has been declared as problematic. This issue affects the function rx_complete of the component usbnet. Executing manipulation can lead to race condition. This vulnerability is tracked as CVE-2025-22050. The attack is only possible within the local network. No exploit exists. It is recommended to upgrade the affected component.

A vulnerability was found in Linux Kernel up to 6.1.133/6.6.86/6.12.22/6.13.10/6.14.1 and classified as problematic. Affected by this vulnerability is the function kmalloc of the component LoongArch. Such manipulation leads to allocation of resources. This vulnerability is uniquely identified as CVE-2025-22049. The attack can only be initiated within the local network. No exploit exists. It is suggested to upgrade the affected component.

A vulnerability, which was classified as critical, was found in Linux Kernel up to 6.13.10/6.14.1. This vulnerability affects the function usb_dev of the component gpib. Such manipulation leads to null pointer dereference. This vulnerability is uniquely identified as CVE-2025-22051. The attack can only be initiated within the local network. No exploit exists. You should upgrade the affected component.

A vulnerability categorized as problematic has been discovered in Linux Kernel up to 6.6.86/6.12.22/6.13.10/6.14.1. The affected element is an unknown function of the component LoongArch. The manipulation results in unchecked return value. This vulnerability is cataloged as CVE-2025-22048. The attack must originate from the local network. There is no exploit available. It is advisable to upgrade the affected component.

A vulnerability has been found in Linux Kernel up to 6.6.86/6.12.22/6.13.10/6.14.1 and classified as problematic. Affected is the function __apply_microcode_amd. This manipulation causes unchecked return value. This vulnerability is handled as CVE-2025-22047. The attack can only be done within the local network. There is not any exploit available. The affected component should be upgraded.

A vulnerability marked as problematic has been reported in Netty. This issue affects some unknown processing of the component HTTP2 Handler. This manipulation causes allocation of resources. The identification of this vulnerability is CVE-2025-55163. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to upgrade the affected component.

A vulnerability was found in Eclipse Jetty up to 9.4.57/10.0.25/11.0.25/12.0.21/12.1.0.alpha2. It has been declared as problematic. This affects an unknown part. Executing manipulation can lead to resource consumption. This vulnerability is tracked as CVE-2025-5115. The attack can be launched remotely. No exploit exists.

A vulnerability was found in activerecord Gem on Rails. It has been declared as problematic. The impacted element is an unknown function of the component ANSI Handler. Executing manipulation can lead to improper neutralization of escape, meta, or control sequences. The identification of this vulnerability is CVE-2025-55193. The attack may be launched remotely. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability categorized as problematic has been discovered in Apache Tomcat up to 8.5.100/9.0.107/10.1.43/11.0.9. The affected element is an unknown function of the component HTTP2 Handler. The manipulation results in denial of service. This vulnerability only affects products that are no longer supported by the maintainer. This vulnerability was named CVE-2025-48989. The attack may be performed from remote. There is no available exploit. It is advisable to upgrade the affected component.

A vulnerability has been found in PyTorch up to 2.5.x and classified as critical. This affects an unknown function. This manipulation causes deserialization. This vulnerability is registered as CVE-2025-32434. Remote exploitation of the attack is possible. No exploit is available. The affected component should be upgraded.

A vulnerability labeled as critical has been found in activestorage Gem on Ruby. Affected by this vulnerability is an unknown functionality. Such manipulation leads to command injection. This vulnerability is listed as CVE-2025-24293. The attack may be performed from remote. There is no available exploit. The affected component should be upgraded.

A vulnerability labeled as critical has been found in Linux Kernel up to 6.12.25/6.14.4. Affected is the function me_swapcache_dirty of the component vmscan. The manipulation results in improper update of reference count. This vulnerability is known as CVE-2025-37834. 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 6.6.88/6.12.25/6.14.4/6.15-rc3 and classified as critical. Affected by this vulnerability is the function apple_soc_cpufreq_get_rate of the component cpufreq. Performing manipulation results in null pointer dereference. This vulnerability is cataloged as CVE-2025-37831. The attack must originate from the local network. There is no exploit available. The affected component should be upgraded.

A vulnerability marked as critical has been reported in Linux Kernel. Affected by this vulnerability is the function niu_try_msix. This manipulation causes denial of service. This vulnerability is handled as CVE-2025-37833. The attack can only be done within the local network. There is not any exploit available. It is suggested to upgrade the affected component.

This appears to be a false positive. Please validate the mentioned sources and consider excluding this entry altogether.

A vulnerability has been found in Tomofun Furbo 360 and Furbo Mini and classified as problematic. This impacts an unknown function of the component Trial Restriction Handler. This manipulation causes improper access controls. This vulnerability is handled as CVE-2025-11641. It is feasible to perform the attack on the physical device. There is not any exploit available. The firmware versions determined to be affected are Furbo 360 up to FB0035_FW_036 and Furbo Mini up to MC0020_FW_074. The vendor was contacted early about this disclosure but did not respond in any way.

A vulnerability was found in Tomofun Furbo 360 and Furbo Mini and classified as problematic. Affected is an unknown function of the component Registration Handler. Such manipulation leads to denial of service. This vulnerability is uniquely identified as CVE-2025-11642. The attack can be executed directly on the physical device. No exploit exists. The firmware versions determined to be affected are Furbo 360 up to FB0035_FW_036 and Furbo Mini up to MC0020_FW_074. The vendor was contacted early about this disclosure but did not respond in any way.

A vulnerability was found in Tomofun Furbo 360 and Furbo Mini. It has been classified as problematic. Affected by this vulnerability is an unknown functionality of the file /squashfs-root/furbo_img of the component MQTT Client Certificate. Performing manipulation results in hard-coded credentials. This vulnerability was named CVE-2025-11643. The attack may be initiated remotely. There is no available exploit. The firmware versions determined to be affected are Furbo 360 up to FB0035_FW_036 and Furbo Mini up to MC0020_FW_074. The vendor was contacted early about this disclosure but did not respond in any way.

A vulnerability was found in Tomofun Furbo 360 and Furbo Mini. It has been declared as problematic. Affected by this issue is some unknown functionality of the component UART Interface. Executing manipulation can lead to insecure storage of sensitive information. The identification of this vulnerability is CVE-2025-11644. The physical device can be targeted for the attack. Furthermore, there is an exploit available. The firmware versions determined to be affected are Furbo 360 up to FB0035_FW_036 and Furbo Mini up to MC0020_FW_074. The vendor was contacted early about this disclosure but did not respond in any way.