Skip to content

Incorrect stack adjustment on an indirect call despite the call of the call is provided #7326

@xusheng6

Description

@xusheng6

For the following call to LocalAlloc

Image

we can see from LLIL that the stack adjustment is wrong (it should be 0x8 instead of 0xd8):

Image

The 0xd8 is initially calculated when the type info of LocalAlloc is missing, but even after I manually applied that info, it is still wrong. It is worth pointing out that, even without providing the type info, the analysis correctly realizes that the call should have two parameters.

Database: lily leaf spreads greatly

Metadata

Metadata

Assignees

No one assigned

    Labels

    Component: CoreIssue needs changes to the coreEffort: LowIssue should take < 1 weekImpact: LowIssue is a papercut or has a good, supported workaroundWorkload: malwareIssues that are relevant to malware analysis workload

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions