dbcve.org
FreertosOperating system · Amazon

CVE-2024-28115

HIGH · 7.8 CVSS v3.1 Published 2024-03-07
Fix available
A fix is available. Upgrade to 10.6.2 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
FreeRTOS is a real-time operating system for microcontrollers. FreeRTOS Kernel versions through 10.6.1 do not sufficiently protect against local privilege escalation via Return Oriented Programming techniques should a vulnerability exist that allows code injection and execution. These issues affect ARMv7-M MPU ports, and ARMv8-M ports with Memory Protected Unit (MPU) support enabled (i.e. `configENABLE_MPU` set to 1). These issues are fixed in version 10.6.2 with a new MPU wrapper.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

FreeRTOS Kernel versions through 10.6.1 have insufficient Memory Protection Unit (MPU) implementation on ARMv7-M and ARMv8-M ports that fails to prevent Return Oriented Programming (ROP) techniques, allowing local privilege escalation when code injection vulnerabilities exist.

MitigationUpgrade FreeRTOS Kernel to version 10.6.2 or later which implements a new MPU wrapper with proper ROP protection. For systems that cannot upgrade immediately, verify MPU configuration restricts execution to authorized code regions only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FreertosOperating system
Affected:< 10.6.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the FreeRTOS Kernel version
    Check the FreeRTOS version.h or version.c file in your kernel source, typically located in FreeRTOS/Source/include or examine the build artifacts for the version string
    Affected if The version is 10.6.1 or earlier (any version < 10.6.2)
  2. Confirm ARM architecture
    Identify the target MCU architecture from your hardware documentation, linker script, or build configuration files. Look for ARM Cortex-M3/M4 (ARMv7-M) or ARM Cortex-M33/M23 (ARMv8-M)
    Affected if The device uses an ARMv7-M or ARMv8-M processor core
  3. Verify MPU is enabled in FreeRTOS configuration
    Check the FreeRTOSConfig.h file for configincludeMPUWRAPPERS and confirm MPU support is compiled in. Look for MPU-related compilation flags or the presence of mpu_*.c files in your build
    Affected if MPU wrappers are included in the build (the vulnerability only applies when MPU is used)
  4. Inspect MPU region configuration
    Examine the MPU setup code in port.c or the platform-specific MPU configuration. Check if the MPU is configured to prevent execution from RAM or data regions
    Affected if The MPU allows execution permission in data/heap regions or does not enforce strict code execution boundaries

You are affected if you are running FreeRTOS Kernel versions before 10.6.2 on an ARMv7-M or ARMv8-M device with MPU enabled, and the MPU configuration does not block execution from non-code regions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.6.2 or later
Fixed in 10.6.2
Interim mitigation

Upgrade FreeRTOS Kernel to version 10.6.2 or later which implements a new MPU wrapper with proper ROP protection. For systems that cannot upgrade immediately, verify MPU configuration restricts execution to authorized code regions only.

Recommended fix High confidence

FreeRTOS Kernel 10.6.2

  1. Upgrade FreeRTOS Kernel to version 10.6.2 or later
  2. If using ARMv7-M MPU ports or ARMv8-M ports with MPU enabled (configENABLE_MPU=1), verify the new MPU wrapper is properly integrated
  3. Recompile and redeploy the firmware to all affected microcontrollers

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Freertos Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-28115 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-28115 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data