Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
cve-2026-31431-check — Check local Linux mitigation/exposure status for CVE-2026-31431 "Copy Fail" | Kitploit
Tools/GitHubGitHub/forensicfoundry/cve-2026-31431-check
Privilege EscalationVulnerability ScannersVulnerability AnalysisConfiguration AuditingIncident Response
GitHubforensicfoundry/cve-2026-31431-check

cve-2026-31431-check

Check local Linux mitigation/exposure status for CVE-2026-31431 "Copy Fail"

View Repository

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share
74 months agoNot yet reviewed

cve-2026-31431-check

cve-2026-31431-check is a small Bash triage script for checking local Linux exposure and mitigation indicators for CVE-2026-31431, also known as "Copy Fail."

The script targets Debian, Ubuntu, and Debian-family derivatives (including Linux Mint, Pop!_OS, and similar dpkg/APT-based systems). It exits with code 3 on non-Debian-family hosts or without dpkg-query. It does not rely on kernel version alone, because vendor backports and mitigation packages can make version-only checks misleading.

In containers, chroots, or environments where /proc boot time, module state, or /var/lib/dpkg does not reflect the real host, reboot and package timestamps may be misleading—treat those signals accordingly.

What it checks

The script reports:

  • running OS, kernel, kmod, and kernel package details
  • whether algif_aead is loaded, built in, loadable, blocked, or absent
  • whether the running kernel package changelog references the CVE or relevant fix
  • whether the system has rebooted since the running kernel package was last installed or upgraded (compared to last boot time), so disk-side changelog evidence is not treated as “clean” while an older kernel may still be running

Important limitation

This script does not determine whether a host was previously exploited.

It checks current local exposure indicators and whether the booted kernel is consistent with the installed running-kernel package timestamps and mitigation state. If the running kernel package changelog references the fix but the host has not rebooted since that package was installed, the script treats that as action required (exit code 1): the in-memory kernel may still predate the on-disk fix until you reboot into the installed image.

Usage

root@kitploit:~
chmod +x cve-2026-31431-check
./cve-2026-31431-check

Show help:

root@kitploit:~
./cve-2026-31431-check --help

Show version:

root@kitploit:~
./cve-2026-31431-check --version

Exit codes

CodeMeaning
0Patched, mitigated, or likely not exposed based on local checks
1Vulnerable or exposed indicator found, reboot required after a fix is present on disk

License

GPL-3.0-only

Download Tool
or
2Unknown; manual review needed
3Script error, unsupported OS (non-Debian-family), or missing dpkg-query