selinux-policy: Restore excluded policy.kern.

[pebenito]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

Fix this issue:

$ sudo semanage fcontext -a -e /var /mnt/overlays/var/upper
libsemanage.semanage_read_policydb: Could not open kernel policy /var/lib/selinux/targeted/active/policy.kern for reading. (No such file or directory).
FileNotFoundError: No such file or directory

Change Log

• Restore policy.kern to fix semanage error.

Does this affect the toolchain?

NO

Test Methodology

• Pipeline build id: 903051

[CBL-Mariner-Bot]

✅ PR Check Passed

No critical issues detected in spec file changes.

🤖 AI Analysis Summary:

Brief Analysis:
The changes update the package release number and tighten file verification for policy.kern, with an associated changelog entry explaining the new inclusion. No new CVE-related patches are referenced.

Critical Issues Found:
• No ERROR/CRITICAL issues detected regarding missing CVE patches or misapplied patch directives.

Recommended Actions:
• Verify that any future CVE fixes use the mandated "Patch: CVE-YYYY-XXXXX.patch" naming scheme.
• Continue using %verify to avoid file mismatches and ensure policy file integrity.
• Maintain clear changelog entries for security fixes as done in this update.

---

📋 For detailed analysis and recommendations, check the Azure DevOps pipeline logs.