
Wazuh SCA policy that audits host-level interim mitigations for CVE-2026-98432, checking nftables/iptables IP-option drop rules and TCP migration and MPTCP sysctls.
This policy checks host-level interim controls for CVE-2026-98432. It does not detect the vulnerability and does not prove that the running kernel is patched. Pair it with Wazuh Vulnerability Detection and a reboot check.
| ID | Check | Passes when | Limits |
|---|---|---|---|
| 990100 | nftables drops inbound IPv4 packets carrying options | nft list ruleset has a line with ip hdrlength != 5 or ip hdrlength > 5 and drop | Rule text only. The rule may sit in the wrong chain, after an accept rule, or not persist across reboot. Not applicable when nft is unavailable. |
| 990101 | iptables drops inbound IPv4 packets carrying options | iptables-save has a line with u32, the IHL match, and -j DROP | Rule text only. The rule may sit in the wrong chain, after an accept rule, or not persist across reboot. Not applicable when iptables-save is unavailable. |
| 990102 | TCP request socket migration is disabled | /proc/sys/net/ipv4/tcp_migrate_req is 0 | Runtime value only. Does not verify persistence or cover a BPF reuseport migration program. Not applicable when the sysctl is absent. |
| 990103 | MPTCP is disabled | /proc/sys/net/mptcp/enabled is 0 | Runtime value only. Does not verify persistence. Removes one exploitation route, not the use-after-free. MPTCP may be required by applications. Not applicable when MPTCP is absent. |
nft list ruleset prints gt as >. Check 990100 matches both forms. iptables-save normalizes the u32 expression to hex. Check 990101 matches the normalized form and the decimal form.
If MPTCP is required, remove check 990103. The remaining checks still cover the IP option drop and the migration path.
A pass means the named control was present at scan time. It does not guarantee that the control persists or that the kernel is fixed. A fail means the control was absent or did not match. Not applicable means SCA could not evaluate the target; it is not a pass.
The policy includes a Linux requirement, so it does not run on non-Linux agents. Wazuh excludes not-applicable checks from the policy score. Read the individual results. A host with no firewall tooling can show a high score while both firewall checks are not applicable.
SCA reads command output in chunks. On hosts with very large nftables or iptables rulesets, the line-based firewall match can be unreliable near the chunk boundary. Verify those hosts manually.
GODEBUG=multipathtcp=0, whether exploitation was attempted or succeeded, and whether a host is immune.If a command runs but exits non-zero, the SCA engine evaluates its output. That case is reported as failed when no pattern matches, not as not applicable. Check the agent log if a firewall check fails unexpectedly.
Create a temporary agent group from hosts that Vulnerability Detection or the vendor tracker flagged as running an affected kernel. Do not add this policy to a permanent baseline.
install -m 0640 cve_2026_98432_mitigation.yml /var/ossec/etc/shared/<group>/
chown wazuh:wazuh /var/ossec/etc/shared/<group>/cve_2026_98432_mitigation.yml
/var/ossec/etc/shared/<group>/agent.conf:<agent_config>
<sca>
<policies>
<policy>etc/shared/cve_2026_98432_mitigation.yml</policy>
</policies>
</sca>
</agent_config>
echo "sca.remote_commands=1" >> /var/ossec/etc/local_internal_options.conf
That setting lets the manager run commands on the endpoint. Restrict manager access before enabling it.
systemctl restart wazuh-agent
/var/ossec/logs/ossec.log for policy errors. The command checks need nft or iptables-save in the agent PATH and permission to read the ruleset; the Linux agent normally runs as root. A containerized agent may see a different network namespace.Check IDs 990100 to 990103 must be unique across all policy files. Change them if they collide with an existing policy.
python3 validate_policy.py
The validator requires PyYAML. It checks YAML structure, policy fields, requirements, rule syntax, unique check IDs, compliance and reference shape, and 32 fixture cases plus three requirements assertions.
The fixtures cover:
!= 5, real > 5 output, and the older gt 5 formu32 rules in normalized hex, leading-zero hex, and decimal forms, including a lower-case verdictDROP comment, which must failu32 matcher, which must failtcp_migrate_req values 0, 1, and absentmptcp.enabled values 0, 1, and absentThis is not a Wazuh runtime test. The fixtures use Python re, while Wazuh uses OSRegex by default. The policy patterns avoid advanced regex constructs, so expected results should match, but run one lab agent before rolling out.
A kernel release string is not a reliable patch indicator. Distribution backports, ABI suffixes, livepatches, and a pending reboot all break version matching. See SCA-ASSESSMENT.md for the reasoning and the alternatives.
After the fleet runs a fixed kernel, remove the policy from agent.conf, delete the file from the group directory, and restart the agents. A mitigation policy that outlives the patch produces false failures and score noise.