Vuldb Updates

A vulnerability was found in Linux Kernel up to 6.6.23/6.7.11. It has been classified as problematic. This affects an unknown part of the component rk3288. The manipulation leads to use after free. This vulnerability is uniquely identified as CVE-2024-35792. The attack needs to be approached within the local network. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability classified as problematic has been found in Linux Kernel up to 6.6.23/6.7.11. Affected is the function typec_altmode_set_drvdata of the component displayport. The manipulation leads to null pointer dereference. This vulnerability is traded as CVE-2024-35790. Access to the local network is required for this attack to succeed. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability, which was classified as critical, has been found in Linux Kernel up to 5.10.214/5.15.153/6.1.83/6.6.23/6.7.11. Affected by this issue is some unknown functionality of the component TEE. The manipulation leads to denial of service. This vulnerability is handled as CVE-2024-35785. The attack can only be done within the local network. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability classified as problematic was found in Linux Kernel up to 6.6.23/6.7.11. Affected by this vulnerability is an unknown functionality of the component btrfs. The manipulation leads to excessive iteration. This vulnerability is known as CVE-2024-35784. The attack needs to be approached within the local network. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability, which was classified as critical, was found in Linux Kernel up to 6.6.23/6.7.11. Affected is the function nouveau_gem_ioctl_pushbuf of the component drm. The manipulation leads to deadlock. This vulnerability is traded as CVE-2024-35786. The attack needs to be initiated within the local network. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability classified as problematic has been found in Linux Kernel up to 5.12/6.1.82/6.6.22/6.7.10/6.8.1. This affects an unknown part of the component nvme. The manipulation leads to allocation of resources. This vulnerability is uniquely identified as CVE-2024-27435. The attack needs to be initiated within the local network. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability has been found in Microsoft Windows and classified as critical. This vulnerability affects unknown code of the component StateRepository API Server. The manipulation leads to missing authorization. This vulnerability was named CVE-2025-49723. It is possible to launch the attack on the local host. There is no exploit available. It is recommended to apply a patch to fix this issue.

A vulnerability was found in Microsoft Windows. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the component Notification. The manipulation leads to use after free. This vulnerability is known as CVE-2025-49726. Local access is required to approach this attack. There is no exploit available. It is recommended to apply a patch to fix this issue.

A vulnerability was found in Microsoft Windows and classified as problematic. This issue affects some unknown processing of the component Storage. The manipulation leads to file inclusion. The identification of this vulnerability is CVE-2025-49760. The attack may be initiated remotely. There is no exploit available. It is recommended to apply a patch to fix this issue.

A vulnerability was found in Linux Kernel up to 6.6.23/6.7.11/6.8.2 and classified as critical. This issue affects some unknown processing of the component amdgpu. The manipulation leads to deadlock. The identification of this vulnerability is CVE-2024-35795. The attack needs to be approached within the local network. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability was suspected in Linux Kernel up to 6.7.9. Further investigation has shown that this issues is a false-positive. Please review the sources mentioned and consider not using this entry at all.

A vulnerability was suspected in Linux Kernel up to 6.7.9. Further analysis revealed that this issues is a false-positive. Please take a look at the sources mentioned and consider not using this entry at all.

A vulnerability was suspected in Linux Kernel up to 6.7.9. This issue appears to be a false-positive. Please verify the sources mentioned and consider not using this entry at all.

A vulnerability was suspected in Linux Kernel up to 6.7.9. Further investigation has shown that this issues is a false-positive. Please review the sources mentioned and consider not using this entry at all.

A vulnerability was suspected in Linux Kernel up to 6.7.9. Further analysis revealed that this issues is a false-positive. Please take a look at the sources mentioned and consider not using this entry at all.

A vulnerability was suspected in Linux Kernel up to 6.7.9. This issue was flagged as a false-positive. Please consult the sources mentioned and consider not using this entry at all.

A vulnerability was suspected in Linux Kernel up to 6.7.9. Further analysis revealed that this issues is a false-positive. Please take a look at the sources mentioned and consider not using this entry at all.

A vulnerability was suspected in Linux Kernel up to 6.7.9. This issue was flagged as a false-positive. Please consult the sources mentioned and consider not using this entry at all.

A vulnerability was suspected in Linux Kernel up to 6.7.9. Further investigation has shown that this issues is a false-positive. Please review the sources mentioned and consider not using this entry at all.

A vulnerability was suspected in Linux Kernel up to 6.7.9. This issue was flagged as a false-positive. Please consult the sources mentioned and consider not using this entry at all.