PAGES
← all tools
◆ Code Security

syzkaller

open-source

Free plan: not checked yet · Open source: yes

syzkaller is an unsupervised coverage-guided kernel fuzzer

What you can do now

Checking Plays…

Summary

syzkaller is an Apache-2.0 open-source command-line kernel fuzzer that uses unsupervised, coverage-guided testing to discover vulnerabilities across Linux and other operating-system kernels. It is self-hosted rather than a SaaSSaaSSoftware delivered over the internet and billed by subscription, hosted and operated by the vendor so the buyer skips installation and infrastructure management. service, aimed at kernel developers, vulnerability researchers, and security-testing teams who can build and run kernel targets. It sits in the kernel-fuzzing and appsec testing space, with documentation covering Linux, FreeBSD, Fuchsia, NetBSD, OpenBSD, Windows, and other systems. The project has issued 34 releases in the tracked period, with its latest release this week.

syzkaller is an unsupervised coverage-guided kernel fuzzer

How syzkaller helps

What system calls in the kernel are likely to have bugs?

fuzzes system calls across multiple operating systems, generating inputs to find undefined behavior

Which operating system kernel interface should I test?

supports generating test cases for Linux, FreeBSD, Fuchsia, gVisor, NetBSD, OpenBSD, and Windows

What specific system calls are being exercised during a test run?

covers system calls through its kernel fuzzer mechanism

How can I check for potential bugs in my custom kernel module or driver?

can be used to test and discover vulnerabilities in kernel interfaces

What are the known vulnerabilities found in various OS kernels?

maintains documentation listing bugs found in Linux, FreeBSD, NetBSD, OpenBSD, and Windows

Which OS kernels does the fuzzer support for testing?

supports fuzzing for Linux, FreeBSD, Fuchsia, gVisor, NetBSD, OpenBSD, and Windows

all 32 features, with the evidence for each →

Languages

Chinese (Simplified) Documentation: Chinese (Simplified)

Features

32 capabilities

Built from syzkaller's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date.

Compare with peers →

All capabilities 32 capabilities
LLM backend and agent configuration Manages model routing, context limits, multi-key distribution, and custom agent skills for automated analysis pipelines. 11 releases · first seen Oct 2026
Test environment configuration Detects host hardware capabilities, configures virtual machines and sandboxes, and verifies required system dependencies for execution. 8 releases · first seen Oct 2026
Kernel syscall descriptions Maintains and updates system call definitions and kernel API descriptions across supported operating systems. 7 releases · first seen Oct 2026
Unsupervised kernel fuzzing Provides unsupervised, coverage-guided fuzzing capabilities for the Linux kernel. 2 releases · 1 other source · first seen Oct 2026
LoongArch64 guest support Extends KVM fuzzing and tooling to loong64 guests, including KVM register state assertion via a dedicated pseudo-syscall, exit-test descriptions, and check-syzos.sh build toolchain support for the loongarch64 architecture. 3 releases · first seen Nov 2026
AI-assisted patch planning Integrates reasoning models and planning agents into the code modification pipeline to generate patch strategies before edits. 3 releases · first seen Oct 2026
AI-assisted bisection Uses AI to identify the commits that introduced or fixed a kernel bug by analysing crash reports, reproducers, and optional root-cause analysis via bisect-cause and bisect-fix workflows in the aflow subsystem. 2 releases · first seen Nov 2026
AI security assessment bug routing Adds a route label to the dashboard that AI security assessments use to tag bugs with a routing destination, propagating the label to external bug reportings so downstream consumers receive it. 2 releases · first seen Nov 2026
Manager public HTTP endpoint Exposes the syz-manager dashboard at a configurable public-facing URL so that external dashboards and CI systems can link directly to it. 1 release · 1 other source · first seen Oct 2026
Dashboard subsystem configuration Manages dashboard configuration entries and subsystem extraction rules for supported kernel versions, including enabling hardware subsystem profiles such as UFS. 2 releases · first seen Oct 2026
Differential kernel fuzzing Orchestrates fuzzing sessions that compare base and patched kernel binaries, skipping runs when the binaries are identical, via a reusable syz-cluster package. 2 releases · first seen Oct 2026
Cluster fuzz target scoping Allows syz-cluster fuzz targets to include static seeds and exclude specific paths via regexp filters, controlling the scope of fuzzing runs. 2 releases · first seen Oct 2026
RDMA network fuzzing Configures RDMA hardware interfaces and network focus profiles to extend coverage to RDMA subsystems. 2 releases · first seen Oct 2026
Automated task execution Orchestrates parallel execution of fuzzing tasks, manages per-task logs, and persists executed seeds and results into a corpus database. 2 releases · first seen Oct 2026
vhost vsock fuzzing Provides executor helpers for setting up and sending data over vhost vsock interfaces to extend fuzzing coverage to that subsystem. 1 release · first seen Nov 2026
Multi-architecture target support Extends syz-agent to support additional CPU architectures, including riscv64 and arm64 compat targets, with configurable target VM architecture selection. 1 release · first seen Nov 2026
Patch recipient management Supports To/Cc recipient additions and removals during patch iteration within the aflow patching workflow, allowing reviewers to request email address changes alongside tag updates. 1 release · first seen Nov 2026
Per-bug embargo management Allows the dashboard to assign and track individual embargo durations on a per-bug basis. 1 release · first seen Nov 2026
Impact and root cause analysis separation Separates impact analysis from root cause analysis within the aflow package to allow each concern to be handled independently. 1 release · first seen Nov 2026
Lint enforcement Enforces code style rules on syzkaller source files, including requiring raw string literals for multi-line strings. 1 release · first seen Oct 2026
Source file linkification Converts source file references in bug reports and other text into hyperlinks anchored to a specified kernel repository and commit, available in both HTML and Markdown output formats. 1 release · first seen Oct 2026
Infra-error retry limiting Caps the number of infrastructure-error retries in CollectRuns via a configurable MaxRetries field, returning a distinct error when the limit is exceeded. 1 release · first seen Oct 2026
AI-assisted bug report summarisation Generates and includes AI-produced root cause analysis summaries in dashboard bug report emails. 1 release · first seen Oct 2026
Cluster boot testing Provides reusable smoke boot test logic as a standalone package for verifying kernel boot behaviour across syz-cluster components. 1 release · first seen Oct 2026
Cluster kernel build management Provides shared kernel build logic as a reusable package for use across syz-cluster components. 1 release · first seen Oct 2026
Cluster symbol verification Checks data symbols in both directions within syz-cluster to validate kernel patch correctness. 1 release · first seen Oct 2026
Stable backport recognition Recognises AUTOSEL tags and version-range stable backport annotations when processing patch metadata in syz-cluster workflows. 1 release · first seen Oct 2026
Cluster network and protocol focus configurations Provides preconfigured fuzzing focus modes in syz-cluster for specific protocol areas, including Bluetooth and USB, with expanded enabled syscall sets for each. 1 release · first seen Oct 2026
Corpus triage Optimizes patch testing workflows by automatically capping deflake runs and streamlining regression validation. 1 release · first seen Oct 2026
Memory safety execution Controls executor-level memory safety flags and optimization settings across supported architectures. 1 release · first seen Oct 2026
Code search Enables batched repository searches and per-file result counting for targeted code analysis. 1 release · first seen Oct 2026
Crash report parsing Extracts structured fault information and titles from kernel crash outputs for automated analysis. 1 release · first seen Oct 2026

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for syzkaller, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail syzkaller puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Coverage

Missing something? Tell us

What syzkaller connects to, runs on and detects, read from its release notes and docs. So far: 5 new detections, 3 updated detections, 2 new supported platforms, 1 updated supported platform.

Show
When

11 changes, tracked since Oct 13, 2026.

  • Nov 22026

    new Binder generic netlink report descriptions

    With binder generic netlink reports

    sys/linux: describe binder generic netlink reports

    commits-2026-10-30 Source ↗

  • Nov 22026

    updated Binder and binderfs syscall descriptions

    sys/linux: fix and extend binder and binderfs descriptions

    commits-2026-10-30 Source ↗

  • Oct 302026

    new VMX MSR load/store list syscall descriptions for x86 SYZOS

    With VMX MSR load/store lists

    executor, sys/linux: add VMX MSR load/store lists to x86 SYZOS

    commits-2026-10-28 Source ↗

  • Oct 302026

    updated AF_VSOCK syscall descriptions for Linux

    With sys/linux

    sys/linux: fix and extend AF_VSOCK descriptions

    commits-2026-10-28 Source ↗

  • Oct 222026

    updated Linux subsystem extraction rules updated for v7.3

    pkg/subsystem/linux: update subsystem extraction rules for v7.3

    commits-2026-10-22 Source ↗

  • Oct 192026

    new Nested KVM state pages mutation for x86

    Covers 7: SYZOS_API_NESTED_SET_STATE_PAGES, NESTED_PAGE_APIC_ACCESS, NESTED_PAGE_VAPIC, NESTED_PAGE_MSRPM, NESTED_PAGE_IOPM, NESTED_PAGE_POSTED_INTR and 1 more

    executor, sys/linux: add nested state pages mutation for x86

    commits-2026-10-16 Source ↗

Changes per month New Updated Retired
2026-109
2026-112
How we count

Read from 13 of 22 release notes and docs updates we hold for syzkaller. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through syzkaller's life, so an old integration can show a recent first-seen date.

Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.

Releases

Show
Coverage in all entries

22 entries

  1. November 202610
  2. October 202612
    Show
    Coverage in all entries

    22 entries

    Project health

    Issue, contributor and maintainer activity in google/syzkaller, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors not measured distinct committers, last 12 months
    2. Maintainers not measured core set, last 12 months
    3. Bus factor not measured committers behind half the commits
    4. Community-filed 16% of issues opened, last 12 months
    5. Median time to close 8.1 days first maintainer reply 20 hours
    6. Open backlog 522 of 1,432 issues ever filed
    1. Issues opened / month 2 · 5 communitymaintainers
    2. Open backlog 522
    3. Contributors / month not measured
    4. Commits / month not measured
    5. Stars not measured
    Issue themes, last 12 months
    • bugs 36%
    • features 55%
    • other 9%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    We can only check tools that publish GitHub releases.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    Saved in this browser. Sign in to sync your tools.