In gnss, there is a possible out of bounds write due to a missing bounds check.
Affects MediaTek MT2737, MT6813, MT6980D, MT6982, MT6986, MT6988 and MT6990 chipsets through the gnss component. CVSS 5.5 (medium). No fixed version is listed in the checked facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected chipsets include MT2737, MT6813, MT6980D, MT6982, MT6986, MT6988 and MT6990 (gnss subcomponent).
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The vulnerability affects the GNSS (satellite navigation) component of a software platform, which handles location positioning on affected devices. Exploitation could cause a local denial of service, crashing or disrupting that component, and it requires user interaction but no additional privileges.
Read the original description
In gnss, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial of service with no additional execution privileges needed. User interaction is needed for exploitation. Patch ID: ALPS11309305; Issue ID: MSV-10730.
What to do
Check whether your setup matches what the bug needs.
Affected chipsets include MT2737, MT6813, MT6980D, MT6982, MT6986, MT6988 and MT6990 (gnss subcomponent).Workaround: The checked facts do not list a workaround for this issue. Until a fix is available, follow the device vendor's guidance and watch for a firmware update.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- MediaTek, Inc. MediaTek chipset
MT2737, MT6813, MT6980D, MT6982, MT6986, MT6988, MT6990
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-20551
What does this mean?
The advisory describes an out-of-bounds write in the gnss (satellite navigation) component of MediaTek chipsets. The cause is a missing bounds check, which means the code does not verify that a write stays inside its intended memory area.Source: mediatek.com
Am I affected, and how do I check?
The listed affected chipsets are MT2737, MT6813, MT6980D, MT6982, MT6986, MT6988 and MT6990, in the gnss subcomponent. The checked facts give no version ranges, so check the chipset model in the device's hardware specifications and compare it against that list.Source: mediatek.com
What should I do about it?
The checked facts do not name a fixed version or an upgrade target. Check the MediaTek security bulletin or the device vendor's update notes for a patched firmware build.Source: mediatek.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
The checked facts do not list a workaround for this issue. Until a fix is available, follow the device vendor's guidance and watch for a firmware update.Source: mediatek.com