From 35c33df16f5764f6938b7f3c7236357d66a1e3f1 Mon Sep 17 00:00:00 2001 From: KaraZajac Date: Mon, 1 Jun 2026 11:05:05 -0400 Subject: [PATCH] fragnesia: add 5.10.257 kernel_range entry (Debian bullseye backport) Weekly drift-check (build.yml schedule cron) went red 2026-06-01: Debian's security tracker now lists CVE-2026-46300 as fixed on the 5.10 branch (bullseye 5.10.257), a branch fragnesia's kernel_patched_from table didn't model. detect() would false-positive VULNERABLE on a patched bullseye 5.10.257+ host. Adding {5,10,257} clears the only MISSING finding; refresh-kernel-ranges.py now exits 0. The 10 remaining drifted modules are INFO-only 'more permissive' entries the check tolerates. --- modules/fragnesia_cve_2026_46300/skeletonkey_modules.c | 1 + 1 file changed, 1 insertion(+) diff --git a/modules/fragnesia_cve_2026_46300/skeletonkey_modules.c b/modules/fragnesia_cve_2026_46300/skeletonkey_modules.c index a288e92..ee3efd5 100644 --- a/modules/fragnesia_cve_2026_46300/skeletonkey_modules.c +++ b/modules/fragnesia_cve_2026_46300/skeletonkey_modules.c @@ -916,6 +916,7 @@ static int fg_active_probe(void) * 7.1-rcN: still vulnerable (rc1..rc4 at time of writing) */ static const struct kernel_patched_from fragnesia_patched_branches[] = { + {5, 10, 257}, /* 5.10-LTS backport (Debian bullseye ships .257 with fix) */ {5, 15, 208}, /* 5.15-LTS backport */ {6, 1, 174}, /* 6.1-LTS backport */ {6, 6, 141}, /* 6.6-LTS backport */