VulnSocial

CVE-2022-21744(mediatek / lr11)

LOWCVSS 9.8 · CRITICAL

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

In Modem 2G RR, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution when decoding GPRS Packet Neighbour Cell Data (PNCD) improper neighbouring cell size with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: MOLY00810064; Issue ID: ALPS06641626.

mediatek CVEsBack to dashboard
0.5/ 10 priority

Sources & remediation

Vendor / third-party advisories
Weakness type (CWE)
CWE-787

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • lr11
  • lr12
  • lr12a
  • lr13

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • 1 total mentions across 1 day

Affected systems

Vendors
mediatek
Products
lr11lr12lr12alr13lr9mt2731mt2735mt6297mt6725mt6735

1 version affected across 73 products

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-09-17: 109-17
Full discourse1 post
  • Sad HAM Society@Sad_HAMs_

    @TheManDocSmurf @4nt1p4tt3rn 'k. Guess all those other modem RCE pivots didn't exist, then, huh? Someone notify Mobile Pwn2Own, Huawei / Mediatek, the authors of CVE-2022-21744, TAZSK, and the Unisoc folks.

    20000338
    5.8K followersView on X
CPE platform detail73 entries

73 of 73 entries

PartVendorProductVersionTarget SWTarget HW
OSmediateklr11---
OSmediateklr12---
OSmediateklr12a---
OSmediateklr13---
OSmediateklr9---
HWmediatekmt2731---
HWmediatekmt2735---
HWmediatekmt6297---
HWmediatekmt6725---
HWmediatekmt6735---
HWmediatekmt6737---
HWmediatekmt6739---
HWmediatekmt6750---
HWmediatekmt6750s---
HWmediatekmt6755---
HWmediatekmt6757---
HWmediatekmt6757p---
HWmediatekmt6758---
HWmediatekmt6761---
HWmediatekmt6762---
HWmediatekmt6762d---
HWmediatekmt6762m---
HWmediatekmt6763---
HWmediatekmt6765---
HWmediatekmt6765t---
HWmediatekmt6767---
HWmediatekmt6768---
HWmediatekmt6769---
HWmediatekmt6769t---
HWmediatekmt6769z---
HWmediatekmt6771---
HWmediatekmt6775---
HWmediatekmt6779---
HWmediatekmt6781---
HWmediatekmt6783---
HWmediatekmt6785---
HWmediatekmt6785t---
HWmediatekmt6789---
HWmediatekmt6797---
HWmediatekmt6799---
HWmediatekmt6833---
HWmediatekmt6853---
HWmediatekmt6855---
HWmediatekmt6873---
HWmediatekmt6875---
HWmediatekmt6877---
HWmediatekmt6879---
HWmediatekmt6880---
HWmediatekmt6883---
HWmediatekmt6885---
HWmediatekmt6889---
HWmediatekmt6890---
HWmediatekmt6891---
HWmediatekmt6893---
HWmediatekmt6895---
HWmediatekmt6983---
HWmediatekmt8666---
HWmediatekmt8667---
HWmediatekmt8675---
HWmediatekmt8735a---
HWmediatekmt8735b---
HWmediatekmt8765---
HWmediatekmt8766---
HWmediatekmt8768---
HWmediatekmt8771---
HWmediatekmt8781---
HWmediatekmt8786---
HWmediatekmt8788---
HWmediatekmt8789---
HWmediatekmt8791---
HWmediatekmt8797---
OSmediateknr15---
OSmediateknr16---

Explore more

Back to dashboardmediatek CVEslr11 vulnerabilities