CVE-2017-16995: Add assembly for BPF object files #6
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
luisgerhorst
force-pushed
the
cve-2017-16995-bpf-o
branch
from
5a51727 to
e32eade
Compare
luisgerhorst
force-pushed
the
cve-2017-16995-bpf-o
branch
from
e32eade to
7c5fe8e
Compare
|
Hi, thanks for this addition! |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Figured this would be a good addition to the PoC DB. In addition to the usecase from the README, the BPF object files can also be tested with the kernel using
bpftoolin case thepoc.cdoes not compile / work for some reason.The assembly files are pretty messy, unfortunately. But I found it to be simply impossible to write valid BTF by hand.