netfilter: xt_policy: fix strict mode inbound policy matching
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c4b885139203d37f76662c37ae645fe8e0f4e4e5 · < 938867e870fb5471bb16f442aeac81326e05bf65| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
netfilter: xt_policy: fix strict mode inbound policy matching
match_policy_in() walks sec_path entries from the last transform to the first one, but strict policy matching needs to consume info->pol[] in the same forward order as the rule layout.
Derive the strict-match policy position from the number of transforms already consumed so that multi-element inbound rules are matched consistently.
From the CVE record · Linux
The Linux kernel’s netfilter xt_policy component can match multi-element inbound rules incorrectly in strict mode because it checks policy entries in the wrong order. The input does not specify what an attacker could achieve or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels that use netfilter xt_policy should check their versions; affected versions are not specified.