The issue is related to a lack of validation for the reply size of an AudioFlinger effect command in the mediaserver's services/audioflinger/Effects.cpp file. This could allow a local attacker to elevate their privileges using a specially crafted application.