Add kernelCTF CVE-2023-3611 LTS #52
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
liona24
force-pushed
the
CVE-2023-3611
branch
from
a9e520b to
37ed654
Compare
|
Thanks for kaslr leak update. Just FYI, it appears that the KASLR leak is provided to the exploit regardless of the "requires_separate_kaslr_leak" flag (see lts logs). Not sure if this is intended. |
|
Hey! Thanks for noticing the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey.
This is the LTS part of the submission. Since PR #34 hasn't really progressed, I think there is no point in adding the mitigation part right now, because they are pretty much the same. When the other PR is done - and the mitigation exploit for this submission is still relevant - I can open another PR.
Edit: Oh well, the structure check is preventing it. Added the mitigation part anyway now..