kernelCTF submission form
Please make sure that you read the rules before filling out the form - even if you are familiar with the rules, the submission process may have been changed since the last time you read the page.
Email *
Is this a 0-day or 1-day submission? *
Flags *
In the format: kernelCTF{<version>:<environment>:<unix-timestamp>:<signature>}, one flag per line.

Please do not edit this field after the original submission. If you pwned another target since then, make a new submission (as eligibility depends on the original submission time, so the flags and the exploit hash cannot be modified after the initial submission).

Check the public spreadsheet and make sure that your LTS/COS slots are not taken - the 'environment' value(s) from the flag(s) should NOT be listed in the LTS/COS slot columns, otherwise your submission will be a dupe.
Exploit hash *
SHA256 hash of the exploit (as a .tar.gz file) which captured the flag(s).

Keep the exploit small, leave out large, publicly available files (vmlinux, bzImage, etc).

If you are submitting multiple exploits for different targets, then put your exploits into separate folders, compress the folders and submit the hash of the compressed .tar.gz file.

Please do not edit this field after the original submission. If you pwned another target since then, make a new submission (as eligibility depends on the original submission time, so the flags and the exploit hash cannot be modified after the initial submission).

In hex format: [0-9a-f]{64}
Notes
Any additional notes regarding the submission which cannot be added to the other fields.

This will only be read by the kernelCTF team and won't be published publicly.
Next
Clear form
Never submit passwords through Google Forms.
This form was created inside of Google.com. Privacy & Terms
Google Forms