How do I install the Kernel Resource Lifecycle skill?

Run npx skillmds@latest add gvago/kernel-resource-lifecycle in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Kernel Resource Lifecycle safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Kernel Resource Lifecycle?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Kernel Resource Lifecycle free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Kernel Resource Lifecycle?

gvago (@gvago) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Kernel Resource Lifecycle by gvago — Agent Skill

Name: Kernel Resource Lifecycle
Author: gvago

Kernel Resource Lifecycle

Use when a Linux kernel PR diff allocates, frees, or hands off objects, tracks lifetimes (Sashiko stage 4): memory leaks on error paths, use-after-free, refcount imbalance, and asymmetric async teardown (missing cancel_work_sync and friends) in the CHANGED code only. Part of the linux-kernel-review suite.

gvago e10cd08 2.5 KB Updated Sep 17, 2026

File contents

kernel-resource-lifecycle

Lens for memory and object lifetime analysis (Sashiko stage 4). Tracks every allocated struct, reference count, and asynchronous handoff in the diff from alloc to free.

How to apply

Track the lifetime of every allocated object and file descriptor: alloc -> init -> use -> cleanup -> free. Flag any unbalanced pair.
Pay special attention to error paths, that is where leaks live.
For every object handed to a background task or registered with a core subsystem, demand teardown symmetry proof.

Rule index

L1. Memory leaks, especially on error/unwind paths.
L2. Use-after-free and double free. Verify refcount logic (kref_get/kref_put); prove objects are not touched after the count can hit zero.
L3. Uninitialized use. list_add and similar APIs must receive fully initialized objects; flag partially-initialized publication.
L4. Async handoff / teardown symmetry (the highest-value rule). If an object is handed to a timer, workqueue, or notifier, or registered to a subsystem, you must find the explicit cancel_work_sync()/ del_timer_sync()/unregister call BEFORE the memory is freed or the queue destroyed. Absence is a finding; do not assume "it probably can't race."
L5. Unbalanced acquisition: get without put, enable without disable, register without unregister, across all paths including errors.

Mapping a finding to the contract

action_level: action_required for UAF, double free, or a leak on a repeating path; remediation_recommended for cold-path leaks.
category: Correctness (Security when the UAF is reachable from untrusted input).
evidence: the allocation site, the handoff or failure path, and the missing release/cancel, all by function and line.

What NOT to flag

Leaks in kselftests or short-lived userspace test programs unless they can crash the system.
Teardown-path release calls whose returns are ignored (teardown must proceed regardless).
Cleanup-attribute code (__free, guard()) that is actually balanced , check kernel-subsystem-guides cleanup.md triggers before flagging.

Sourcing

Stage text adapted from Sashiko (Apache-2.0).

---name: kernel-resource-lifecycledescription: Use when a Linux kernel PR diff allocates, frees, or hands off objects, tracks lifetimes (Sashiko stage 4): memory leaks on error paths, use-after-free, refcount imbalance, and asymmetric async teardown (missing cancel_work_sync and friends) in the CHANGED code only. Part of the linux-kernel-review suite.license: Apache-2.0---# kernel-resource-lifecycleLens for memory and object lifetime analysis (Sashiko stage 4). Tracksevery allocated struct, reference count, and asynchronous handoff in thediff from alloc to free.## How to apply- Track the lifetime of every allocated object and file descriptor: alloc -> init -> use -> cleanup -> free. Flag any unbalanced pair.- Pay special attention to error paths, that is where leaks live.- For every object handed to a background task or registered with a core subsystem, demand teardown symmetry proof.## Rule index- L1. Memory leaks, especially on error/unwind paths.- L2. Use-after-free and double free. Verify refcount logic (kref_get/kref_put); prove objects are not touched after the count can hit zero.- L3. Uninitialized use. list_add and similar APIs must receive fully initialized objects; flag partially-initialized publication.- L4. Async handoff / teardown symmetry (the highest-value rule). If an object is handed to a timer, workqueue, or notifier, or registered to a subsystem, you must find the explicit cancel_work_sync()/ del_timer_sync()/unregister call BEFORE the memory is freed or the queue destroyed. Absence is a finding; do not assume "it probably can't race."- L5. Unbalanced acquisition: get without put, enable without disable, register without unregister, across all paths including errors.## Mapping a finding to the contract- action_level: action_required for UAF, double free, or a leak on a repeating path; remediation_recommended for cold-path leaks.- category: Correctness (Security when the UAF is reachable from untrusted input).- evidence: the allocation site, the handoff or failure path, and the missing release/cancel, all by function and line.## What NOT to flag- Leaks in kselftests or short-lived userspace test programs unless they can crash the system.- Teardown-path release calls whose returns are ignored (teardown must proceed regardless).- Cleanup-attribute code (__free, guard()) that is actually balanced , check kernel-subsystem-guides cleanup.md triggers before flagging.## SourcingStage text adapted from Sashiko (Apache-2.0).

Frequently asked questions