107 matches found
CVE-2025-35963: Insufficient Control Flow Management
Insufficient control flow management for some IntelR PROSet/Wireless WiFi Software for Windows before version 23.160 within Ring 2: Device Drivers may allow a denial of service. Unprivileged software adversary with an unauthenticated user combined with a low complexity attack may enable denial of...
CVE-2025-24512: Improper Input Validation
Improper input validation for some IntelR PROSet/Wireless WiFi Software for Windows before version 23.160 within Ring 2: Device Drivers may allow a denial of service. Authorized adversary with an authenticated user combined with a high complexity attack may enable denial of service. This result m...
CVE-2025-33029: Out-of-bounds Write
Out-of-bounds write for some IntelR PROSet/Wireless WiFi Software for Windows before version 23.160 within Ring 2: Device Drivers may allow a denial of service. Unprivileged software adversary with an unauthenticated user combined with a low complexity attack may enable denial of service. This...
PT-2022-19249
Name of the Vulnerable Software and Affected Versions Fujitsu LIEFBOOK devices A3510, U9310, U7511/U7411/U7311, U9311, E5510/E5410, U7510/U7410/U7310, E459/E449 versions prior to v1.09 A3510, v2.17 U9310, v2.30 U7511/U7411/U7311, v2.33 U9311, v2.23 E5510, v2.19 U7510/U7410, v2.13 U7310, and v1.09...
CVE-2020-5953: Undefined Security Weakness
A vulnerability exists in System Management Interrupt SWSMI handler of InsydeH2O UEFI Firmware code located in SWSMI handler that dereferences gRT EFIRUNTIMESERVICES pointer to call a GetVariable service, which is located outside of SMRAM. This can result in code execution in SMM escalating...
PT-2022-9047
Name of the Vulnerable Software and Affected Versions InsydeH2O UEFI Firmware affected versions not specified Description A vulnerability exists in the System Management Interrupt SWSMI handler of InsydeH2O UEFI Firmware code. The SWSMI handler dereferences the gRT EFI RUNTIME SERVICES pointer to...
CVE-2013-4554
Xen 3.0.3 through 4.1.x possibly 4.1.6.1, 4.2.x possibly 4.2.3, and 4.3.x possibly 4.3.1 does not properly prevent access to hypercalls, which allows local guest users to gain privileges via a crafted application running in ring 1 or 2...