Skip to content
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

Report unsoundness in cortex-m #2178

Closed
wants to merge 1 commit into from
Closed

Conversation

shinmao
Copy link
Contributor

@shinmao shinmao commented Dec 23, 2024

The issue has been patched in Nov 2023 but it is still not released in the latest version (0.7.7). We can ask whether the maintainer plan to release it first.

@Shnatsel
Copy link
Member

Normally users would already get the latest version of the dependency crate. Publishing this advisory as-is would result in false positives even if the latest version did patch it, but right now the advisory seems entirely non-actionable.

Since the issue only manifests given a combination of versions between cortex-m and volatile_register, which we cannot encode in the database format right now, and that it is only unsoundness and not a pressing security issue, I'm inclined not to publish an advisory for it.

@shinmao
Copy link
Contributor Author

shinmao commented Dec 23, 2024

Yes. It makes sense. Thanks for pointing it out.

@Shnatsel Shnatsel closed this Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants