<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: magicos</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2024-47150: Some Honor products are affected by information leak vulnerability, successful exploitation could cause the in</title><link>https://patchthecve.com/cve/CVE-2024-47150.html</link><guid>https://patchthecve.com/cve/CVE-2024-47150.html</guid><pubDate>Wed, 17 Jun 2026 07:56:37 +0000</pubDate><description>LOW 3.3: Some Honor products are affected by information leak vulnerability, successful exploitation could cause the information leak.</description></item><item><title>CVE-2024-47149: Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation coul</title><link>https://patchthecve.com/cve/CVE-2024-47149.html</link><guid>https://patchthecve.com/cve/CVE-2024-47149.html</guid><pubDate>Wed, 17 Jun 2026 07:56:37 +0000</pubDate><description>LOW 3.3: Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation could cause device service exceptions.</description></item><item><title>CVE-2024-8994: Some Honor products are affected by information leak vulnerability, successful exploitation could cause the in</title><link>https://patchthecve.com/cve/CVE-2024-8994.html</link><guid>https://patchthecve.com/cve/CVE-2024-8994.html</guid><pubDate>Wed, 17 Jun 2026 08:23:45 +0000</pubDate><description>MEDIUM 6.2: Some Honor products are affected by information leak vulnerability, successful exploitation could cause the information leak.</description></item><item><title>CVE-2024-8993: Some Honor products are affected by information leak vulnerability, successful exploitation could cause the in</title><link>https://patchthecve.com/cve/CVE-2024-8993.html</link><guid>https://patchthecve.com/cve/CVE-2024-8993.html</guid><pubDate>Wed, 17 Jun 2026 08:23:45 +0000</pubDate><description>MEDIUM 6.2: Some Honor products are affected by information leak vulnerability, successful exploitation could cause the information leak.</description></item><item><title>CVE-2024-8992: Some Honor products are affected by information leak vulnerability, successful exploitation could cause the in</title><link>https://patchthecve.com/cve/CVE-2024-8992.html</link><guid>https://patchthecve.com/cve/CVE-2024-8992.html</guid><pubDate>Wed, 17 Jun 2026 08:23:45 +0000</pubDate><description>MEDIUM 4.0: Some Honor products are affected by information leak vulnerability, successful exploitation could cause the information leak.</description></item><item><title>CVE-2024-47157: Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation coul</title><link>https://patchthecve.com/cve/CVE-2024-47157.html</link><guid>https://patchthecve.com/cve/CVE-2024-47157.html</guid><pubDate>Wed, 17 Jun 2026 07:56:38 +0000</pubDate><description>LOW 2.9: Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation could cause device service exceptions.</description></item><item><title>CVE-2024-47155: Some Honor products are affected by information leak vulnerability, successful exploitation could cause the in</title><link>https://patchthecve.com/cve/CVE-2024-47155.html</link><guid>https://patchthecve.com/cve/CVE-2024-47155.html</guid><pubDate>Wed, 17 Jun 2026 07:56:38 +0000</pubDate><description>MEDIUM 5.5: Some Honor products are affected by information leak vulnerability, successful exploitation could cause the information leak.</description></item><item><title>CVE-2024-47154: Some Honor products are affected by information leak vulnerability, successful exploitation could cause the in</title><link>https://patchthecve.com/cve/CVE-2024-47154.html</link><guid>https://patchthecve.com/cve/CVE-2024-47154.html</guid><pubDate>Wed, 17 Jun 2026 07:56:38 +0000</pubDate><description>MEDIUM 5.5: Some Honor products are affected by information leak vulnerability, successful exploitation could cause the information leak.</description></item><item><title>CVE-2024-47153: Some Honor products are affected by information leak vulnerability, successful exploitation could cause the in</title><link>https://patchthecve.com/cve/CVE-2024-47153.html</link><guid>https://patchthecve.com/cve/CVE-2024-47153.html</guid><pubDate>Wed, 17 Jun 2026 07:56:38 +0000</pubDate><description>MEDIUM 6.2: Some Honor products are affected by information leak vulnerability, successful exploitation could cause the information leak.</description></item><item><title>CVE-2024-47148: Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation coul</title><link>https://patchthecve.com/cve/CVE-2024-47148.html</link><guid>https://patchthecve.com/cve/CVE-2024-47148.html</guid><pubDate>Wed, 17 Jun 2026 07:56:37 +0000</pubDate><description>MEDIUM 4.0: Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation could cause device service exceptions.</description></item><item><title>CVE-2024-47156: Some Honor products are affected by information leak vulnerability, successful exploitation could cause the in</title><link>https://patchthecve.com/cve/CVE-2024-47156.html</link><guid>https://patchthecve.com/cve/CVE-2024-47156.html</guid><pubDate>Wed, 17 Jun 2026 07:56:38 +0000</pubDate><description>LOW 3.3: Some Honor products are affected by information leak vulnerability, successful exploitation could cause the information leak.</description></item><item><title>CVE-2024-47151: Some Honor products are affected by file writing vulnerability, successful exploitation could cause code execu</title><link>https://patchthecve.com/cve/CVE-2024-47151.html</link><guid>https://patchthecve.com/cve/CVE-2024-47151.html</guid><pubDate>Wed, 17 Jun 2026 07:56:38 +0000</pubDate><description>MEDIUM 6.3: Some Honor products are affected by file writing vulnerability, successful exploitation could cause code execution</description></item></channel></rss>