Patch Lag Board

See whether your distro and devices actually patched that CVE, and how late

Problem

Community analysis showed the same kernel CVE gets fixed in a median of about 12 days on Debian 13 but 109 days on Ubuntu, and ordinary users have no idea how far behind their own firmware and devices are. Assessing risk means manually cross-checking distro advisories, CVE databases, and device firmware versions.

Solution

Pick your distro, kernel version, and a few device models; the tool aggregates corresponding CVE fix status and lag days, produces a ranked list of known-but-unpatched vulnerabilities, and alerts you when new advisories land.

Users

Homelab and self-hosted server operators, small-team IT, security-conscious developers

MVP

Advisory scraping for major distros like Debian and Ubuntu; CVE matching by kernel version with lag calculation; manual firmware version entry and comparison; a single-page risk dashboard; email or RSS change alerts

Revenue

Free single-device board; subscription unlocks multiple devices, historical trends, and alerts; one-time license for internal fleet versions

Why now

Supply-chain and firmware vulnerabilities keep surfacing, and patch-lag numbers just became a public talking point, making this the moment for a transparent tracker