mirror of https://github.com/V4bel/dirtyfrag.git synced 2026-05-16 10:50:10 +00:00

History

Clem 44af5b1a14 Add Kubernetes mitigation manifest Adds a self-contained DaemonSet manifest under k8s/ that applies the mitigation from the README (modprobe blacklist of esp4/esp6/rxrpc + page-cache flush) to every Linux node in a Kubernetes cluster, and re-applies it automatically on any new node that joins the cluster (autoscaling, node-image upgrade, scale-set rolling update). - k8s/dirtyfrag-mitigation.yaml — single-file manifest applyable with kubectl apply -f. Uses an init container that nsenter's into PID 1 to write /etc/modprobe.d/disable-dirtyfrag.conf, modprobe -r each module that has refcnt=0, and echo 3 > /proc/sys/vm/drop_caches. For any module that remains loaded with refcnt > 0, emits a single aggregated Warning Kubernetes Event on the Node (no auto-cordon). A long-running pause container keeps the pod Running so the init container is only re-executed on pod recreation. - k8s/README.md — apply / verify / revert instructions and compatibility notes (esp4/esp6 = IPsec, rxrpc = AFS). - README.md — short Kubernetes section in Mitigation pointing to k8s/. Tested on AKS (Azure) running Kubernetes 1.30, in a production environment across staging and production clusters.	2026-05-08 10:41:03 +02:00
..
dirtyfrag-mitigation.yaml	Add Kubernetes mitigation manifest	2026-05-08 10:41:03 +02:00
README.md	Add Kubernetes mitigation manifest	2026-05-08 10:41:03 +02:00

Adds a self-contained DaemonSet manifest under k8s/ that applies the
mitigation from the README (modprobe blacklist of esp4/esp6/rxrpc +
page-cache flush) to every Linux node in a Kubernetes cluster, and
re-applies it automatically on any new node that joins the cluster
(autoscaling, node-image upgrade, scale-set rolling update).

  - k8s/dirtyfrag-mitigation.yaml — single-file manifest applyable with
    kubectl apply -f. Uses an init container that nsenter's into PID 1
    to write /etc/modprobe.d/disable-dirtyfrag.conf, modprobe -r each
    module that has refcnt=0, and echo 3 > /proc/sys/vm/drop_caches.
    For any module that remains loaded with refcnt > 0, emits a single
    aggregated Warning Kubernetes Event on the Node (no auto-cordon).
    A long-running pause container keeps the pod Running so the init
    container is only re-executed on pod recreation.
  - k8s/README.md — apply / verify / revert instructions and
    compatibility notes (esp4/esp6 = IPsec, rxrpc = AFS).
  - README.md — short Kubernetes section in Mitigation pointing to k8s/.

Tested on AKS (Azure) running Kubernetes 1.30, in a production
environment across staging and production clusters.

2026-05-08 10:41:03 +02:00

dirtyfrag-mitigation.yaml

Add Kubernetes mitigation manifest

2026-05-08 10:41:03 +02:00

README.md

Add Kubernetes mitigation manifest

2026-05-08 10:41:03 +02:00

README.md

Kubernetes mitigation

A self-contained Kubernetes manifest that applies the Dirty Frag mitigation to every Linux node in a cluster.

What it does

Deploys a DaemonSet (dirtyfrag-mitigation in kube-system) whose init container — running on every Linux node, including system pools — performs the steps from the disclosure README inside the host's namespaces via nsenter:

Writes /etc/modprobe.d/disable-dirtyfrag.conf blacklisting esp4, esp6 and rxrpc so they cannot be loaded on demand.
For each of these modules currently loaded with refcnt=0, runs modprobe -r to unload it from the live kernel.
Runs sync; echo 3 > /proc/sys/vm/drop_caches to clear any contaminated cached pages.
If any of these modules is loaded with refcnt > 0 (in active use), emits a single aggregated Warning Kubernetes Event (reason=DirtyFragModulesInUse) on the affected Node listing the in-use modules, so operators can drain and reboot/replace the node. No auto-cordon.

A long-running pause container keeps the pod in Running state so the init container is only re-executed on pod recreation — i.e. on each new node that joins the cluster (autoscaling, node-image upgrade, scale-set rolling update).

Apply

kubectl apply -f https://raw.githubusercontent.com/V4bel/dirtyfrag/master/k8s/dirtyfrag-mitigation.yaml
kubectl -n kube-system rollout status ds/dirtyfrag-mitigation

Check for nodes that need a drain+reboot to complete the mitigation (modules that were already in use):

kubectl -n default get events --field-selector reason=DirtyFragModulesInUse

Compatibility

esp4 and esp6 provide IPsec ESP transforms; rxrpc provides the RxRPC socket family used by AFS. None of these are required by a typical workload-only Kubernetes cluster.

If your cluster does require one of these modules (e.g. a node-level IPsec tunnel, an AFS client running on the host or in a privileged pod), edit the MODULES env var in the manifest and remove the affected module(s) before applying — or label-exclude the affected node pool.

Revert (once upstream kernel patches roll out)

The modprobe drop-in persists for the lifetime of each node. To clean it up from live nodes before deleting the DaemonSet:

# 1. Flip the init container into cleanup mode and roll the fleet
kubectl -n kube-system set env ds/dirtyfrag-mitigation CLEANUP_MODE=true
kubectl -n kube-system rollout restart ds/dirtyfrag-mitigation
kubectl -n kube-system rollout status  ds/dirtyfrag-mitigation

# 2. Delete the DaemonSet, ServiceAccount and ClusterRole/Binding
kubectl delete -f https://raw.githubusercontent.com/V4bel/dirtyfrag/master/k8s/dirtyfrag-mitigation.yaml

If you skip step 1, the /etc/modprobe.d/disable-dirtyfrag.conf drop-in remains on existing nodes until each is recycled (node-image upgrade, scale-down, or manual kubectl drain && kubectl delete node).

Tested with

Kubernetes 1.30 on AKS (Azure), in a production environment across staging and production clusters
Linux nodes only (the DaemonSet has nodeSelector: kubernetes.io/os: linux so Windows nodes are skipped automatically)