kernel-cve-analysis
/kernel-cve-analysis
Query the Android/AOSP kernel CVE database to look up a specific CVE, find CVEs affecting a kernel version or build date, find unpatched CVEs in a branch, or identify exploitable vulnerabilities. Use this skill when the user asks about Android kernel CVEs, AOSP kernel vulnerabilities, which CVEs affect a kernel version/branch/build, whether a kernel is patched, or which vulnerabilities are exploitable. Trigger for phrases like "CVEs in kernel 5.10", "is android13-5.15 patched", "exploitable CVEs in <branch>", or "look up CVE-2024-XXXXX".
- Author
- DeepBitsTechnology ↗
- Repository
- claude-plugins ↗
- Licence
- Apache-2.0
- Last repository change
- 12.07.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.07.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Query the Android/AOSP kernel CVE database to look up a specific CVE, find CVEs affecting a kernel version or build date, find unpatched CVEs in a branch, or identify exploitable vulnerabilities. Use this skill when the user asks about Android kernel CVEs, AOSP kernel vulnerabilities, which CVEs affect a kernel version/branch/build, whether a kernel is patched, or which vulnerabilities are exploitable. Trigger for phrases like "CVEs in kernel 5.10", "is android13-5.15 patched", "exploitable CVEs in <branch>", or "look up CVE-2024-XXXXX".
Triggers from the description
Original author description
Query the Android/AOSP kernel CVE database to look up a specific CVE, find CVEs affecting a kernel version or build date, find unpatched CVEs in a branch, or identify exploitable vulnerabilities. Use this skill when the user asks about Android kernel CVEs, AOSP kernel vulnerabilities, which CVEs affect a kernel version/branch/build, whether a kernel is patched, or which vulnerabilities are exploitable. Trigger for phrases like "CVEs in kernel 5.10", "is android13-5.15 patched", "exploitable CVEs in <branch>", or "look up CVE-2024-XXXXX".
How it works
- When to Use This Skill
- Available Tools (remote MCP)
- Workflow
- Output Format
SKILL.md preview
--- name: kernel-cve-analysis description: Query the Android/AOSP kernel CVE database to look up a specific CVE, find CVEs affecting a kernel version or build date, find unpatched CVEs in a branch, or identify exploitable vulnerabilities. Use this skill when the user asks about Android kernel CVEs, AOSP kernel vulnerabilities, which CVEs affect a kernel version/branch/build, whether a kernel is patched, or which vulnerabilities are exploitable. Trigger for phrases like "CVEs in kernel 5.10", "is android13-5.15 patched", "exploitable CVEs in <branch>", or "look up CVE-2024-XXXXX". --- # Android Kernel CVE Analysis This skill queries the remote Dr. Binary MCP server's Android/AOSP kernel CVE database. It helps determine which kernel vulnerabilities affect a given version, build date, or branch — and which are actually exploitable (bug-inducing code present *and* fix absent). ## When to Use This Skill Use this skill when the user wants to: - Look up details for a specific CVE (affected versions, fix, bug-inducing commit, branches) - Enumerate CVEs affecting a specific AOSP kernel version - Find CVEs affecting a kernel built at a specific date - Find unpatched CVEs in a specific branch - Identify exploitable CVEs for a branch at a point in time - Browse the CVE database ## Available Tools (remote MCP) | Tool | Use it when… | Arguments | | --- | --- | --- | | `get_cve_info` | The user names a specific CVE | `cve_id` (e.g. `"CVE-2024-12345"`) | | `query_cves_by_version` | "Which CVEs affect kernel `<version>`?" | `aosp_version`, `limit?` (default 100) | | `query_cves_by_date` | "Which CVEs affect a kernel built on `<date>`?" | `commit_date`, `limit?` (default 100) | | `query_cves_by_branch` | "Which CVEs are unpatched in `<branch>`?" | `branch`, `limit?` (default 100) | | `find_exploitable_cves` | "Which CVEs are exploitable in `<branch>` as of `<date>`?" | `commit_date`, `branch`, `limit?` (default 50) | | `list_all_cves` | "Show me the CVEs in the database" | `limit?` (default 100) | ### Notes on each tool - **`get_cve_info`** — returns a formatted report with type, severity, subcomponent, fixed-in version, affected version ranges, fix commits, and bug-inducing commits. - **`query_cves_by_version`** — all CVEs affecting a specific AOSP kernel version (e.g. `5.10`, `5.15`). - **`query_cves_by_date`** — CVEs affecting a kernel built at a specific commit date. - **`query_cves_by_branch`** — unpatched CVEs in a branch (fixes not yet present in that branch). - **`find_exploitable_cves`** — the flagship query: vulnerabilities present in a branch at a specific time where both the bug-inducing code exists *and* the fix is absent. Requires **both** `commit_date` and `branch`. - **`list_all_cves`** — enumerate the database with basic info. ## Workflow 1. **Pick the right tool** from the table above based on what the user gives you (a CVE id, a version, a date, a branch, or a branch+date pair). 2. **For exploitability questions**, you need both a branch and a date. If the user supplied only one, ask for the other before calling `find_exploitable_cves`. 3. **Call the tool** and summarize results: highlight severity, affected ranges, and patch status. 4. **Drill down** into individual CVEs with `get_cve_info` when the user wants details on a specific result. ## Output Format When reporting results, prefer a concise table (CVE id, severity, subcomponent, affected range / patch status) followed by a short narrative for the most important findings, and call out any exploitable CVEs explicitly.
Versions
The database has no other skills named kernel-cve-analysis.
Database snapshot: 13.11.2026 · package version f75f48ebdebd (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100triage-fixed-cves
Triage Go stdlib CVEs against an OpenShift release image to determine which CVEs are fixed by the Go version each component was built with. Use when the user asks to triage Go stdlib CVEs against an OpenShift release image, check which Go CVEs are fixed in a release, or… - 100oci-cve-checker
Use this skill to compare CVE vulnerabilities between two OCI container images and generate reports showing fixed and new CVEs. - 90cve-research
Use when checking a specific dependency or package version for known CVEs and security advisories. - 98cve-remediation
Scan dependency manifests against known CVEs and remediate by upgrading vulnerable dependencies to patched versions, then rebuild and re-scan to confirm. Self-contained scan→fix→verify loop for any project with a dependency manifest. Use when: a cve-remediation task is… - 90cve-review
Read-only review of known and likely vulnerabilities (CVEs) in your dependencies, runtimes, container images and cloud versions, with a ranked findings report. Use for "CVE scan", "vulnerable dependencies", "known vulnerabilities", "am I affected by", "outdated packages with… - 95cve-fix
Automatically fix CVE vulnerabilities in Python dependencies for downstream projects. Queries Jira for unresolved CVEs, filters already-fixed issues, updates Pipfile and Pipfile.lock using container-based pipenv lock, creates MRs, and updates Jira. Use when the user mentions…