Approved changes feed: RSS · Atom

cpe:2.3:o:ti:real-time_operating_system:-:*:*:*:*:*:*:*

part: o version: - update: *

VendorTi (2c4e43a5-e08a-542d-a02a-38c51c91aad1)
ProductReal Time Operating System (404bbe7b-aa12-5dd6-be21-909c70b5354a)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2021-27502 vulnerable 2026-06-03 14:44:16.150580 Texas Instruments TI-RTOS Integer Overflow or Wraparound
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 'HeapMem_allocUnprotected' and result in code execution.
Published: 2023-11-21T17:41:08.040Z
Updated: 2024-08-03T21:26:09.047Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2021-27429 vulnerable 2026-06-03 14:44:15.858872 Texas Instruments TI-RTOS Integer Overflow or Wraparound
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 'HeapTrack_alloc' and result in code execution.
Published: 2023-11-20T19:00:19.757Z
Updated: 2024-08-03T20:48:17.195Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2021-22636 vulnerable 2026-06-03 14:43:53.259147 Texas Instruments TI-RTOS Integer Overflow or Wraparound
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 'HeapMem_allocUnprotected' and result in code execution.
Published: 2023-11-20T19:02:30.434Z
Updated: 2024-08-03T18:44:13.779Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2020-16630 vulnerable 2026-06-03 14:41:47.757718 Details available
TI’s BLE stack caches and reuses the LTK’s property for a bonded mobile. A LTK can be an unauthenticated-and-no-MITM-protection key created by Just Works or an authenticated-and-MITM-protection key created by Passkey Entry, Numeric Comparison or OOB. Assume that a victim mobile uses secure pairing to pair with a victim BLE device based on TI chips and generate an authenticated-and-MITM-protection LTK. If a fake mobile with the victim mobile’s MAC address uses Just Works and pairs with the victim device, the generated LTK still has the property of authenticated-and-MITM-protection. Therefore, the fake mobile can access attributes with the authenticated read/write permission.
Published: 2021-09-20T19:20:50.000Z
Updated: 2024-08-04T13:45:33.225Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.