<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: performancetest</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2020-15481: An issue was discovered in PassMark BurnInTest v9.1 Build 1008, OSForensics v7.1 Build 1012, and PerformanceTe</title><link>https://patchthecve.com/cve/CVE-2020-15481.html</link><guid>https://patchthecve.com/cve/CVE-2020-15481.html</guid><pubDate>Wed, 17 Jun 2026 02:56:43 +0000</pubDate><description>HIGH 7.8: An issue was discovered in PassMark BurnInTest v9.1 Build 1008, OSForensics v7.1 Build 1012, and PerformanceTest v10.0 Build 1008. The kernel driver exposes IOCTL functionality that allows low-privilege users to map arbitrary physical memory into the address space of the calling process. This could </description></item><item><title>CVE-2020-15480: An issue was discovered in PassMark BurnInTest through 9.1, OSForensics through 7.1, and PerformanceTest throu</title><link>https://patchthecve.com/cve/CVE-2020-15480.html</link><guid>https://patchthecve.com/cve/CVE-2020-15480.html</guid><pubDate>Wed, 17 Jun 2026 02:56:42 +0000</pubDate><description>HIGH 8.8: An issue was discovered in PassMark BurnInTest through 9.1, OSForensics through 7.1, and PerformanceTest through 10. The kernel driver exposes IOCTL functionality that allows low-privilege users to read and write to arbitrary Model Specific Registers (MSRs). This could lead to arbitrary Ring-0 code </description></item><item><title>CVE-2020-15479: An issue was discovered in PassMark BurnInTest through 9.1, OSForensics through 7.1, and PerformanceTest throu</title><link>https://patchthecve.com/cve/CVE-2020-15479.html</link><guid>https://patchthecve.com/cve/CVE-2020-15479.html</guid><pubDate>Wed, 17 Jun 2026 02:56:42 +0000</pubDate><description>HIGH 8.8: An issue was discovered in PassMark BurnInTest through 9.1, OSForensics through 7.1, and PerformanceTest through 10. The driver&#x27;s IOCTL request handler attempts to copy the input buffer onto the stack without checking its size and can cause a buffer overflow. This could lead to arbitrary Ring-0 code</description></item></channel></rss>