fix(kernel): resolve CIS unused module findings - #18697
Conversation
There was a problem hiding this comment.
🟡 Changes recommended
The post-rebase 1.3 build inputs require fresh build and smoke/CIS validation.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
Removes unused kernel modules to reduce attack surface and satisfy CIS requirements.
Changes:
- Disables CRAMFS, freevxfs, HFS/HFS+, FireWire, and NOSY.
- Bumps the kernel release to
6.18.45-1.3. - Refreshes rendered configs and lock fingerprint.
File summaries
| File | Description |
|---|---|
base/comps/kernel/kernel.spec |
Bumps release and changelog. |
base/comps/kernel/6.18-x86_64-azl.config |
Disables targeted x86_64 modules. |
base/comps/kernel/6.18-aarch64-azl.config |
Disables targeted aarch64 modules. |
specs/k/kernel/kernel.spec |
Updates rendered kernel spec. |
specs/k/kernel/6.18-x86_64-azl.config |
Updates rendered x86_64 config. |
specs/k/kernel/6.18-aarch64-azl.config |
Updates rendered aarch64 config. |
locks/kernel.lock |
Refreshes the input fingerprint. |
Review details
- Files reviewed: 6/7 changed files
- Comments generated: 1
- Review effort level: Balanced
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
/azp run |
|
Azure Pipelines: 2 pipeline(s) were filtered out due to trigger conditions. |
b5fb3e1 to
40d6f71
Compare
There was a problem hiding this comment.
🟡 Changes recommended
The aarch64 output lacks the mandatory installation and smoke-test validation.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Review details
- Files reviewed: 7/8 changed files
- Comments generated: 1
- Review effort level: Balanced
Disable unsupported kernel modules on x86_64 and aarch64 to resolve these CIS Level 1 findings: - Ensure cramfs kernel module is not available (AB#22846) - Ensure freevxfs kernel module is not available (AB#22847) - Ensure hfs kernel module is not available (AB#22848) - Ensure hfsplus kernel module is not available (AB#22849) - Ensure firewire-core kernel module is not available (AB#22850) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
40d6f71 to
daa8c0c
Compare
There was a problem hiding this comment.
🟢 Approval recommended
The policy entries match both architecture configs, and the release, lock, rendered outputs, and validation are consistent.
Review details
- Files reviewed: 7/8 changed files
- Comments generated: 0 new
- Review effort level: Balanced
|
/azp run |
|
Azure Pipelines: 2 pipeline(s) were filtered out due to trigger conditions. |
Summary
Rationale
These modules are not part of the expected Azure Linux server workload surface, and compiling them out removes unused kernel attack surface while satisfying the CIS requirement that they not be available. Unlike a modprobe deny-list, this also prevents privileged software from bypassing policy by loading the module file directly.
The existing distribution evidence supports removal:
This also eliminates an x86_64 CIS-CAT applicability trap: AZL4 previously disabled
CONFIG_FIREWIREbut retainedCONFIG_FIREWIRE_NOSY=m. CIS-CAT treatednosy.kounderdrivers/firewireas evidence that the unrelated FireWire core module was available.Validation
After incorporating the latest 4.0 kernel changes, the kernel was rebuilt successfully for x86_64 and aarch64. Both shipped kernel configs were inspected, and the x86_64 build was installed on AZL4 nightly
vm-base4.0.2026082802and tested:Related work items