Skip to content

fix(detector): detect factory closure replay#195

Closed
prasannakotyal wants to merge 1 commit into
gpu-mode:mainfrom
prasannakotyal:kg-blue-167-factory-closure-replay
Closed

fix(detector): detect factory closure replay#195
prasannakotyal wants to merge 1 commit into
gpu-mode:mainfrom
prasannakotyal:kg-blue-167-factory-closure-replay

Conversation

@prasannakotyal

Copy link
Copy Markdown

KernelGuard-Red-Submission: 167

Detects factory-returned entrypoints that replay from mutated closure state.

The pass requires:

  • module-level custom_kernel = factory()
  • factory returns an inner function
  • inner fast path has no real compute and does not depend on live input
  • fast-path return from closure state by subscript or attribute
  • mutation of that same closure state inside the inner function

Local validation:

  • uv run python -m py_compile kernelguard.py
  • uv run python /home/nino/repos/paradigma/kernelguard_bypasses/eval_blue_patch.py /home/nino/repos/paradigma/competition_state/kernelguard_mirror/kernelguard.py

Target red fixture: red_49_closure_list_replay.py

@prasannakotyal
prasannakotyal temporarily deployed to kernelguard-api-control-plane May 2, 2026 14:39 — with GitHub Actions Inactive
@github-actions

github-actions Bot commented May 2, 2026

Copy link
Copy Markdown

KernelGuard Blue Evaluation

@SinatrasC

Copy link
Copy Markdown
Collaborator

Thanks for the KernelGuard Flywheel Campaign contribution. This PR is now superseded by the consolidated rule-family implementation in #273, which folds this detector coverage together with the related passing-eval variants.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants