Workaround CVE-2026-31431

[chilcano]

Adds a kernel module blacklist step as the first step in every job as a workaround for CVE-2026-31431.

[github-actions]

Consolidated Tests Results 2026-04-30 - 17:29:46

Test Results

12 passed

Details

12 tests
not captured
junit-to-ctrf
build-and-test test-reporter #1827
Workaround CVE-2026-31431 #563

test-reporter: Run #1827

Tests 📝	Passed ✅	Failed ❌	Skipped ⏭️	Pending ⏳	Other ❓	Flaky 🍂	Duration ⏱️
12	12	0	0	0	0	0	not captured

🎉 All tests passed!

Tests

View All Tests

Test Name	Status	Flaky	Duration
k8s_test_crs_uniqueness	✅		32.4s
k8s_test_insecure_keygen_encrypt_and_public_decrypt	✅		2m 7s
k8s_test_insecure_keygen_encrypt_multiple_types	✅		2m 21s
k8s_test_keygen_and_crs	✅		2m 3s
k8s_test_keygen_uniqueness	✅		5m 20s
k8s_test_crs_uniqueness	✅		34.1s
k8s_test_insecure_keygen_encrypt_and_public_decrypt	✅		2m 12s
k8s_test_insecure_keygen_encrypt_multiple_types	✅		2m 26s
k8s_test_keygen_and_crs	✅		2m 7s
k8s_test_keygen_uniqueness	✅		5m 31s
k8s_test_centralized_insecure	✅		1m 2s
nightly_full_gen_tests_default_k8s_centralized_sequential_crs	✅		1.9s

_{🍂 No flaky tests in this run.}

Github Test Reporter by CTRF 💚

[dvdplm]

@chilcano The diff seems to contain a lot of extraneous white space changes that will cause messy merge conflicts. Do you mind backing out any changes that are not specifically tied to CVE-2026-31431?

[chilcano]

@chilcano The diff seems to contain a lot of extraneous white space changes that will cause messy merge conflicts. Do you mind backing out any changes that are not specifically tied to CVE-2026-3143

You are right @dvdplm , those changes were not intended to be done.
I tried to add only 1 github step in the top of github job, but it seems something happened in the script.
Let me check it out.
I'll keep in the loop.

[chilcano]

@dvdplm I'm going to close this PR and raise a new one to address this CVE.