<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: ti</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2021-27504: Texas Instruments devices running FREERTOS, malloc returns a valid 
pointer to a small buffer on extremely lar</title><link>https://patchthecve.com/cve/CVE-2021-27504.html</link><guid>https://patchthecve.com/cve/CVE-2021-27504.html</guid><pubDate>Wed, 17 Jun 2026 03:44:59 +0000</pubDate><description>HIGH 7.4: Texas Instruments devices running FREERTOS, malloc returns a valid 
pointer to a small buffer on extremely large values, which can trigger 
an integer overflow vulnerability in &#x27;malloc&#x27; for FreeRTOS, resulting in
 code execution.</description></item><item><title>CVE-2021-27502: Texas Instruments TI-RTOS, when configured to use HeapMem heap(default),
 malloc returns a valid pointer to a </title><link>https://patchthecve.com/cve/CVE-2021-27502.html</link><guid>https://patchthecve.com/cve/CVE-2021-27502.html</guid><pubDate>Wed, 17 Jun 2026 03:44:59 +0000</pubDate><description>HIGH 7.4: Texas Instruments TI-RTOS, when configured to use HeapMem heap(default),
 malloc returns a valid pointer to a small buffer on extremely large 
values, which can trigger an integer overflow vulnerability in 
&#x27;HeapMem_allocUnprotected&#x27; and result in code execution.</description></item><item><title>CVE-2021-27429: 
Texas Instruments TI-RTOS returns a valid pointer to a small buffer on extremely large values</title><link>https://patchthecve.com/cve/CVE-2021-27429.html</link><guid>https://patchthecve.com/cve/CVE-2021-27429.html</guid><pubDate>Wed, 17 Jun 2026 03:44:50 +0000</pubDate><description>HIGH 7.4: 
Texas Instruments TI-RTOS returns a valid pointer to a small buffer on extremely large values. This can trigger an integer overflow vulnerability in &#x27;HeapTrack_alloc&#x27; and result in code execution. 

</description></item><item><title>CVE-2021-22636: 






Texas Instruments TI-RTOS, when configured to use HeapMem heap(default), malloc returns a valid pointer</title><link>https://patchthecve.com/cve/CVE-2021-22636.html</link><guid>https://patchthecve.com/cve/CVE-2021-22636.html</guid><pubDate>Wed, 17 Jun 2026 03:37:27 +0000</pubDate><description>HIGH 7.4: 






Texas Instruments TI-RTOS, when configured to use HeapMem heap(default), malloc returns a valid pointer to a small buffer on extremely large values, which can trigger an integer overflow vulnerability in &#x27;HeapMem_allocUnprotected&#x27; and result in code execution. 







</description></item><item><title>CVE-2022-25334: The Texas Instruments OMAP L138 (secure variants) trusted execution environment (TEE) lacks a bounds check on </title><link>https://patchthecve.com/cve/CVE-2022-25334.html</link><guid>https://patchthecve.com/cve/CVE-2022-25334.html</guid><pubDate>Wed, 17 Jun 2026 04:33:24 +0000</pubDate><description>HIGH 8.2: The Texas Instruments OMAP L138 (secure variants) trusted execution environment (TEE) lacks a bounds check on the signature size field in the SK_LOAD module loading routine, present in mask ROM. A module with a sufficiently large signature field causes a stack overflow, affecting secure kernel data </description></item><item><title>CVE-2022-25333: The Texas Instruments OMAP L138 (secure variants) trusted execution environment (TEE) performs an RSA check im</title><link>https://patchthecve.com/cve/CVE-2022-25333.html</link><guid>https://patchthecve.com/cve/CVE-2022-25333.html</guid><pubDate>Wed, 17 Jun 2026 04:33:24 +0000</pubDate><description>HIGH 8.2: The Texas Instruments OMAP L138 (secure variants) trusted execution environment (TEE) performs an RSA check implemented in mask ROM when loading a module through the SK_LOAD routine. However, only the module header authenticity is validated. An adversary can re-use any correctly signed header and ap</description></item><item><title>CVE-2022-25332: The AES implementation in the Texas Instruments OMAP L138 (secure variants), present in mask ROM, suffers from</title><link>https://patchthecve.com/cve/CVE-2022-25332.html</link><guid>https://patchthecve.com/cve/CVE-2022-25332.html</guid><pubDate>Wed, 17 Jun 2026 04:33:24 +0000</pubDate><description>MEDIUM 4.4: The AES implementation in the Texas Instruments OMAP L138 (secure variants), present in mask ROM, suffers from a timing side channel which can be exploited by an adversary with non-secure supervisor privileges by managing cache contents and collecting timing information for different ciphertext inpu</description></item><item><title>CVE-2023-29468: The Texas Instruments (TI) WiLink WL18xx MCP driver does not limit the number of information elements (IEs) of</title><link>https://patchthecve.com/cve/CVE-2023-29468.html</link><guid>https://patchthecve.com/cve/CVE-2023-29468.html</guid><pubDate>Wed, 17 Jun 2026 05:50:07 +0000</pubDate><description>CRITICAL 9.8: The Texas Instruments (TI) WiLink WL18xx MCP driver does not limit the number of information elements (IEs) of type XCC_EXT_1_IE_ID or XCC_EXT_2_IE_ID that can be parsed in a management frame. Using a specially crafted frame, a buffer overflow can be triggered that can potentially lead to remote cod</description></item></channel></rss>