kernelCTF: add CVE-2024-26582_mitigation_2 - #424
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
|
I think the This PR uses Could the spreadsheet entry for exp795 please be updated so that the structure check can be rerun?
|
|
The only check that is not passed is This is the responsible part of the script commit_hash = hash_from_url(
public_csv[first_exp_id]["Patch commit"]
)The commit patch is present in the row of exp795, I believe it's just a github actions problem This is the commit patch ID Could some moderator please fix this? Edit: |
vuln-verify searches for the patch commit of a submission in the public spreadsheet. That spreadsheet only used to contain a list of all submissions, but with the switch to the new rules we created new sheets and now the first sheet is for the winners. This makes vuln-verify fail because it can't find the patch commit anymore. Make it look at the correct sheet instead. This will break vuln-verify for the submissions under the new rules so we will need to fix that in the future but this should be ok for now. See #424 for an example of where this broke.
|
Thanks! |
Novelty-only kernelCTF submission exp795 for mitigation-v4-6.6.
This submission targets an already exploited vulnerability and claims only the novel techniques documented in
docs/novel-techniques.md.The submitted exploit demonstrates DirtyBPF, a technique to corrupt a BPF filter with a UAF.
docs/novel-techniques.mdproposes the main techniques and variants.Bug Hunters issue: https://issuetracker.google.com/issues/553474550