Support Channel

For the purpose of defining maintenance guidelines and policies, IoT Yocto software components are categorized into the following 3 categories:

  1. Binary and non-open source licensed software components

  2. Open source software components used in IoT Yocto

  3. Open source software components that contain derivative works from MediaTek

Binary and non-open source licensed software components

These components are listed in the document IoT Yocto Feature Table, for example, IoT Yocto Feature Table v25.0.

MediaTek updates these components as part of the IoT Yocto life cycle. All issue fixes and security patches are applied to the development mainline. There are no backports for previous point releases.

For example, a security patch included in IoT Yocto v25.0 does not get backported to v24.1, v24.0 or earlier releases.

Security patches for identified CVE issues are periodically announced in the IoT Yocto Product Security Bulletin. MediaTek does not actively notify customers or developers about these patches. Please regularly visit and check for the latest CVE patches.

Examples include:

  • MT7921 (Wi-Fi/BT) Firmware

  • DRAM calibration module for Trusted-Firmware-A

  • Video user space driver (VPUD)

Open source software components used in IoT Yocto

The Yocto project integrates a number of open source software components. IoT Yocto integrates and uses these components in BSP and demonstration board images.

MediaTek adopts a “best-effort” approach to merge patches from the upstream Yocto project.

As of July 2025, IoT Yocto is developed based on the Yocto Scarthgap branch in the rity-scarthgap branch. The rity-kirkstone branch is now in a dormant state, and MediaTek does not actively update these open-source modules from the Yocto Kirkstone branch.

While MediaTek periodically merges patches from corresponding Yocto LTS branches, MediaTek does not maintain nor track issues and CVEs of these components.

These open source software components are maintained by their respective open source projects. The software recipes for these components are maintained by the Yocto project.

Examples include:

  • systemd

  • openssl

  • python3

Open source software components that contain derivative works from MediaTek

IoT Yocto and MediaTek BSP software are derived from several essential open-source projects.

Notable examples include:

  • Linux kernel

  • Trusted-Firmware-A

  • U-Boot

In these software components, MediaTek maintains the device drivers and MediaTek hardware-specific modifications. MediaTek does not maintain nor track CVEs of these open source projects that are not related to MediaTek hardware.

Linux Kernel Maintenance Guideline

IoT Yocto contains a Linux kernel derived from the upstream Linux kernel.

As described in the previous section, Linux kernel CVEs related to MediaTek hardware are periodically announced in the IoT Yocto Product Security Bulletin. MediaTek does not actively notify customers or developers about these patches. All issue fixes and security patches are applied to the development mainline. There are no backports for previous point releases.

For other Linux kernel fixes and CVEs, MediaTek does not actively track them.

Instead, MediaTek adopts a “best-effort” approach to integrate upstream kernel minor version patches into the currently active kernel branch in the IoT Yocto life cycle.

The currently active kernel branch is mtk-v6.6. MediaTek will periodically merge upstream Linux 6.6.y patches on a best-effort basis, until the end-of-life of the mtk-v6.6 branch, or the EOL of the upstream Linux 6.6.y LTS branch.

Support Channels

If you are a direct customer of MediaTek and need confidential assistance from MediaTek support team, please contact your MediaTek sales.

If you are not a direct customer of MediaTek, please visit Genio Developer Center and register a developer account for community development resources and forums.