CVE-2026-50719: n/a
Description
The Ingenic T41 SoC boot ROM, and likely the T32, T40, and A1 variants, contain a vulnerability in their boot process. The boot ROM parses and executes an attacker-controlled init table from the SPL header before verifying secure boot state or signature. This init table parser allows 32-bit writes to SRAM, enabling an attacker with physical write access to boot media to disable secure boot checks. This leads to acceptance of unsigned or modified first-stage boot code, bypassing secure boot protections. The issue has been hardware-validated on the T41 and confirmed by ROM analysis on related SoCs.
CVSS v3.1
Score 6.8medium
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-50719 describes a vulnerability in Ingenic SoC boot ROMs (T41 confirmed, T32, T40, and A1 likely affected) where the boot ROM executes an attacker-controlled init table from the SPL header before checking secure boot state or signature verification. The init table parser supports full 32-bit writes to SRAM, allowing modification of secure boot state prior to verification. An attacker with physical write access to boot media can inject an init-table entry that disables secure boot checks, causing the ROM to accept unsigned or tampered first-stage boot code. This undermines the secure boot mechanism, allowing potential unauthorized code execution early in the boot process. The vulnerability has been hardware-validated on a secureboot-enabled T41 device and ROM analysis confirms similar behavior on other SoCs.
Potential Impact
An attacker with physical write access to the boot media can bypass secure boot protections by injecting malicious init-table entries that disable secure boot checks. This allows execution of unsigned or modified first-stage boot code, compromising the device's trusted boot process. The vulnerability impacts the integrity and authenticity guarantees provided by secure boot, potentially enabling persistent low-level compromise.
Mitigation Recommendations
No official patch or remediation is currently documented. Since the vulnerability requires physical write access to boot media, mitigation may involve physical security controls to prevent unauthorized access. Monitor vendor advisories for any future firmware or hardware mitigations. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mitre
- Date Reserved
- 2026-06-05T00:00:00.000Z
- State
- PUBLISHED
Threat ID: 6a85b8baacd9273b492ae41f
Added to database: 08/19/2026, 14:07:54 UTC
Last enriched: 09/11/2026, 09:04:09 UTC
Last updated: 10/04/2026, 10:02:28 UTC
Views: 64
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.