Skip to content

Fix use-after-free in EventPipe #81135

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
Jan 28, 2023
Merged

Conversation

jkoritzinsky
Copy link
Member

Read the assembly name host property once and store it in a function-scoped static global. The memory of this name is expected to be managed by this function, and this value will never change in the lifetime of an application.

This was found with AddressSanitizer.

Read the assembly name host property once and store it in a function-scoped static global. The memory of this name is expected to be managed by this function, and this value will never change in the lifetime of an application.
@ghost
Copy link

ghost commented Jan 24, 2023

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

Issue Details

Read the assembly name host property once and store it in a function-scoped static global. The memory of this name is expected to be managed by this function, and this value will never change in the lifetime of an application.

This was found with AddressSanitizer.

Author: jkoritzinsky
Assignees: -
Labels:

EventPipe, area-Diagnostics-coreclr

Milestone: -

Copy link
Member

@elinor-fung elinor-fung left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oof. Thanks.

Co-authored-by: Aaron Robinson <arobins@microsoft.com>
Co-authored-by: Elinor Fung <elfung@microsoft.com>
@jkoritzinsky
Copy link
Member Author

Failures are known, merging.

@jkoritzinsky jkoritzinsky merged commit 844f6ef into dotnet:main Jan 28, 2023
@jkoritzinsky jkoritzinsky deleted the asan-fixes branch January 28, 2023 19:32
@ghost ghost locked as resolved and limited conversation to collaborators Feb 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants