Skip to content

kernelCTF: add CVE-2024-26582_mitigation_2 - #424

Open
federico-zanca wants to merge 1 commit into
google:masterfrom
federico-zanca:exp795-cve-2024-26582-mitigation-2
Open

kernelCTF: add CVE-2024-26582_mitigation_2#424
federico-zanca wants to merge 1 commit into
google:masterfrom
federico-zanca:exp795-cve-2024-26582-mitigation-2

Conversation

@federico-zanca

Copy link
Copy Markdown

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.md proposes the main techniques and variants.

Bug Hunters issue: https://issuetracker.google.com/issues/553474550

@google-cla

google-cla Bot commented Aug 27, 2026

Copy link
Copy Markdown

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.

@federico-zanca

Copy link
Copy Markdown
Author

I think the structure_check failure is caused by the legacy spreadsheet row for novelty-only submission exp795 having an empty CVE field.

This PR uses CVE-2024-26582_mitigation_2. The exp795 row already contains the corresponding upstream fix commit.

Could the spreadsheet entry for exp795 please be updated so that the structure check can be rerun?

  • CVE: CVE-2024-26582
  • Patch commit title: net: tls: fix use-after-free with partial reads and async decrypt

@federico-zanca

federico-zanca commented Sep 1, 2026

Copy link
Copy Markdown
Author

The only check that is not passed is vuln_verify, it seems that the github actions script fails to find the commit patch for my exploit row in the spreadsheet. The reason is that I got the flag and submitted the form before the redesign of the spreadsheet, while the pull request was made a couple hours after this redesign. The script tries to fetch it only from the default tab of the spreadsheet, the one with gid=855892526, while my exploit (exp795) is in the "kernelCTF (old)" tab, that has gid=2095368189

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 32b55c5ff9103b8508c1e04bfa5a08c64e7a925f

Could some moderator please fix this?

Edit:
Full commit patch link (as reported in the spreadsheet) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id%3D32b55c5ff9103b8508c1e04bfa5a08c64e7a925f

koczkatamas pushed a commit that referenced this pull request Sep 1, 2026
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.
@matrizzo matrizzo added the recheck Triggers kernelCTF PR verification again label Sep 1, 2026
@federico-zanca

Copy link
Copy Markdown
Author

Thanks!

@matrizzo matrizzo added kCTF: vuln OK The submission exploits the claims vulnerability (passed manual verification) and removed recheck Triggers kernelCTF PR verification again labels Sep 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kCTF: vuln OK The submission exploits the claims vulnerability (passed manual verification)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants