Skip to content

AXP-OS/cve_checker

Repository files navigation

Kernel CVE Patcher

A tool for downloading, checking, and applying (CVE) patches to a (kernel) repository.

This is a fork of the original patched made by: Divested Computing Group.

A prebuilt release can be downloaded here / or always-latest

Notes on CVE Patching

  • Patches applied may not be relevant to a device's architecture or hardware
  • Patches can make issues worse, or create new issues
  • Backported patches do not receive much review
  • Patches may not completely mitigate the issue they intend to
  • There are many security patches that do not receive CVEs
  • Linux has many known security issues that go unresolved for years
  • This is not a long-term solution
  • We need more rigorous support lifecycles from upstreams
  • This project is solely made to attempt to improve the security and by extension the lifespan of unsupported devices

Real World Use

  • This project was considered viable by end of 2017 and has been in use since then for DivestOS.
  • The corresponding CVE database is likely one of the largest with support for older kernels.
  • It is often near impossible to provide viable mainline support for many vendor altered kernel trees. We believe this project at the very least improves their situation. To ignore this is to be a defeatist. Not everyone can afford the latest shiny thing.
  • Production examples: 20.0, 19.1, 18.1, 17.1, 16.0, 15.1, 14.1

Patch Database

License

  • AGPL-3.0-or-later

Credits

Quick Start

  • Clone this repo, cd into it, and compile the tool: gradle jar
  • Put the resulting jar into your .bashrc: $DOS_BINARY_PATCHER
  • Clone the patches repo, put it into your .bashrc: $DOS_PATCHES_LINUX_CVES

Adding Patches

CVEs are sourced from the sources listed at the top of Kernel_CVE_Patch_List.txt

Automatic

  1. Not everything can be automated! Most of all the check&test of a patch set cannot be automated and so require manual interaction always.
  2. Not all steps are automated. A full list of sources which are to be checked is here Kernel_CVE_Patch_List.header
  3. You have to ensure to test the results properly before applying them for production use
  4. The whole process is currently (2025-02) a WIP, so expect issues

A real-world example using Ansible can be found here role, play while this can be adapted to any CI/CD process.

Manual

Importing CIP Patches

  • Run: ./CIP.sh $PATH_TO_CIP_REPO
  • Run: git diff CIP.txt
  • Manually import the new patches into Kernel_CVE_Patch_List.txt

Importing Linux incremental diffs

  • Open kernel.org in a browser
  • Run: cd 0001-LinuxIncrementals/4.4
  • Run: java -jar $DOS_BINARY_PATCHER linuxIncrDownload 4.x 4.4. 238 > download.sh
  • Run: git diff download.sh
  • Manually run the commands shown in the diff to download the new ones

Importing Linux incremental patches

an alternative approach to "Importing Linux incremental diffs" but diffs apply faster.

  • Open kernel.org in a browser
  • Run: cd 0001-LinuxIncrementals/4.4
  • Run: java -jar $DOS_BINARY_PATCHER linuxIncrGen 4.4 238 > generate.sh
  • Run: cd $somewhereElse && git clone https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git && git fetch
  • Run: export incrPath="$PATH_TO/0001-LinuxIncrementals"
  • Run: sh $PATH_TO/generate.sh

Downloading Patches

  • If updating an existing patchset, rm -rf it first (e.g. rm -r CVE-XXXX)
  • To ensure you get only recent patches (i.e. not from X years ago): set export CVE_PATCHER_NOT_OLDER_THAN_DATE="2024-10-01"
  • Pointing $DOS_PATCHER_INCLUSIVE_KERNEL to a combined kernel repo will generate patches locally if possible (REQUIRED for CVE_PATCHER_NOT_OLDER_THAN_DATE)
  • Run: java -jar patcher.jar download $DOS_PATCHES_LINUX_CVES/Kernel_CVE_Patch_List.txt

Downloading Entire Repository

  • This easily takes hours
  • You will likely be rate-limited
  • Some patches will be missing as the links may no longer be valid
  • There are a handful of patches that have been added by hand (eg. compressed, or manually backported)
  • Pointing $DOS_PATCHER_INCLUSIVE_KERNEL to a (CIP) combined kernel repo will generate patches locally when possible

Patching

environment vars:

export DOS_PATCHER_LOOSE_VERSIONS=true  # enable loose patching
export DOS_PATCHER_LOOSE_VERSIONS_EXTREME=true  # try as hard as possible to find matching patches
  • Key: $outputDir is where script will be saved, $repoPath is the kernel to be checked, $repoName is vanity name of kernel
  • To patch a kernel directly: java -jar $DOS_BINARY_PATCHER patch direct $DOS_PATCHES_LINUX_CVES $outputDir/ $repoPath/:repoName...
  • To patch a kernel in an AOSP workspace: java -jar $DOS_BINARY_PATCHER patch workspace $workspace/ $DOS_PATCHES_LINUX_CVES $outputDir/ $repoName...

Using the Resulting Scripts

  • This part is entirely up to you
  • They are intended to be run during build time
  • The results of them shouldn't be committed to a tree due to the automated nature

Identifying Failed Patches

  • During compile-time there is an obvious chance it will fail
  • Take the error
  • Run: cd $DOS_PATCHES_LINUX_CVES
  • Run: rg -l $snippet_of_error
  • Check to see if any of those patches were applied
  • Then look at each applied patch to narrow it down
  • Once you find it, you'll want to mark that somewhere. DivestOS has a Fix_CVE_Patchers.sh for tracking/disabling them
  • Generally if it compiles, it boots. However there are patches that can compile and absolutely break boot, see: CVE-2017-13218/4.4/0027.patch

Patch Version Matrix


Version Default Loose Extreme Reverse
3.0 3.0 3.4 3.10, 3.18, 4.4 x
3.4 3.4 3.10 3.18, 4.4 x
3.10 3.10 3.18 4.4 3.4
3.18 3.18 4.4 4.9 x
4.4 4.4 4.9 x x
4.9 4.9 4.14 4.19 x
4.14 4.14 4.19 x x

Relevant Links

Implementation Discussions

Examples