Skip to main content
Vulnerability Database/CVE-2024-28115

CVE-2024-28115: FreeRTOS Privilege Escalation Vulnerability

CVE-2024-28115 is a privilege escalation vulnerability in FreeRTOS Kernel affecting ARMv7-M and ARMv8-M MPU ports. Attackers can exploit ROP techniques to gain elevated privileges. This article covers technical details, affected versions, security impact, and available patches.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2024-28115 Overview

CVE-2024-28115 affects the FreeRTOS Kernel, a real-time operating system widely deployed on microcontrollers. Versions through 10.6.1 do not sufficiently protect against local privilege escalation using Return Oriented Programming (ROP) techniques when a secondary code injection vulnerability is present. The issue impacts ARMv7-M Memory Protection Unit (MPU) ports and ARMv8-M ports with MPU support enabled via configENABLE_MPU set to 1. Amazon shipped a new MPU wrapper in FreeRTOS Kernel version 10.6.2 to address the weakness. The flaw is classified under [CWE-284: Improper Access Control].

Critical Impact

An attacker with local, low-privileged code execution on an affected ARMv7-M or ARMv8-M device can elevate privileges to kernel mode and compromise confidentiality, integrity, and availability of the embedded system.

Affected Products

  • FreeRTOS Kernel versions through 10.6.1 on ARMv7-M MPU ports
  • FreeRTOS Kernel versions through 10.6.1 on ARMv8-M ports with configENABLE_MPU=1
  • Amazon FreeRTOS distributions bundling the affected kernel versions

Discovery Timeline

  • 2024-03-07 - CVE-2024-28115 published to the National Vulnerability Database
  • 2026-06-17 - Last updated in the NVD database

Technical Details for CVE-2024-28115

Vulnerability Analysis

The FreeRTOS Kernel supports privilege separation on ARM Cortex-M microcontrollers using the Memory Protection Unit. Unprivileged tasks are expected to transition to privileged mode only through controlled system call entry points provided by the MPU wrapper. The pre-10.6.2 wrapper does not fully validate call sites or constrain the privileged execution path. An attacker who already has a code injection or arbitrary write primitive in an unprivileged task can chain gadgets within the privileged kernel to escape MPU restrictions. This defeats the isolation boundary that the MPU is intended to provide.

The weakness is tracked as [CWE-284] and requires local access, low privileges, and no user interaction. Exploitation is a secondary stage: it does not grant initial access but amplifies the impact of any other code execution flaw present on the device.

Root Cause

The root cause is insufficient hardening of the MPU wrapper that mediates system calls between unprivileged tasks and the FreeRTOS kernel. The wrapper did not pin the privileged execution path, allowing attacker-controlled gadgets in privileged memory to be reached using Return Oriented Programming. Version 10.6.2 introduces a reworked MPU wrapper that constrains entry conditions and the privileged return path.

Attack Vector

Exploitation requires an attacker to already run code inside an unprivileged FreeRTOS task on the target microcontroller. The attacker chains ROP gadgets through the MPU wrapper to reach privileged kernel execution. From there, the attacker can disable MPU regions, access secure peripherals, modify kernel structures, or persist on the device. See the GitHub Security Advisory GHSA-xcv7-v92w-gq6r for the full technical description.

Detection Methods for CVE-2024-28115

Indicators of Compromise

  • Unexpected modification of MPU region configuration registers at runtime on ARMv7-M or ARMv8-M targets
  • Firmware images containing FreeRTOS Kernel builds reporting a version string at or below 10.6.1 with MPU support enabled
  • Anomalous task transitions into privileged mode outside documented system call entry points

Detection Strategies

  • Inventory firmware builds and extract FreeRTOS Kernel version metadata to flag any image using 10.6.1 or earlier with configENABLE_MPU=1
  • Review build configurations in CI pipelines for the configENABLE_MPU setting and the kernel version pinned in FreeRTOSConfig.h
  • Correlate device telemetry with the vendor advisory listed in the FreeRTOS-Kernel release notes for V10.6.2

Monitoring Recommendations

  • Instrument device fault handlers to log MemManage, BusFault, and UsageFault events that may indicate ROP chain execution failures
  • Monitor supply chain and software bill of materials (SBOM) feeds for FreeRTOS Kernel component versions across embedded product lines
  • Track upstream FreeRTOS advisories and GitHub security notifications for the FreeRTOS-Kernel repository

How to Mitigate CVE-2024-28115

Immediate Actions Required

  • Upgrade the FreeRTOS Kernel to version 10.6.2 or later, which ships the new MPU wrapper that remediates CVE-2024-28115
  • Rebuild and reflash all affected embedded devices with the patched kernel and validate that configENABLE_MPU behavior remains as expected
  • Audit application tasks for secondary code injection vulnerabilities that would be required to reach this escalation path

Patch Information

Amazon addressed CVE-2024-28115 in FreeRTOS Kernel release V10.6.2. The release introduces a redesigned MPU wrapper that hardens the privileged execution path and mitigates ROP-based privilege escalation. Full release details are available in the FreeRTOS Kernel Release V10.6.2 notes and the GitHub Security Advisory GHSA-xcv7-v92w-gq6r.

Workarounds

  • If immediate upgrade is not feasible, enforce strict code signing and secure boot to reduce the likelihood of a prerequisite code injection flaw being introduced
  • Disable MPU support (configENABLE_MPU=0) only if the deployment model does not rely on privilege separation; note that this removes isolation and is not a true fix
  • Apply compiler mitigations such as stack canaries and W^X memory layouts in application tasks to raise the bar for the initial code injection step
bash
# Pin FreeRTOS Kernel to the patched version in a git submodule
cd FreeRTOS-Kernel
git fetch --tags
git checkout V10.6.2
# Verify MPU wrapper source present
ls portable/Common/mpu_wrappers_v2.c

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.