Skip to content

extra tests needed for temporal safety #165

@wsong83

Description

@wsong83

Suppose initial double free has been tested, whether double freed pointers can be reallocated and used to access the same object while writing on it?

Furthermore, whether we can free a non-heap object and add it to the free-list of an allocator? Or, we can free an object of a wrong type, especially this pointer is a derived class using a wrong destruction method? Would this cause different react under different defense techniques?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions