netfilter: xt_multiport: validate range encoding in checkentry
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a89ecb6a2ef732d04058d87801e2b6bd7e5c7089 · < 8368ce8eb01f0b91111d814703696e780d0ef12f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
netfilter: xt_multiport: validate range encoding in checkentry
ports_match_v1() treats any non-zero pflags entry as the start of a port range and unconditionally consumes the next ports[] element as the range end.
The checkentry path currently validates protocol, flags and count, but it does not validate the range encoding itself. As a result, malformed rules can mark the last slot as a range start or place two range starts back to back, leaving ports_match_v1() to step past the last valid ports[] element while interpreting the rule.
Reject malformed multiport v1 rules in checkentry by validating that each range start has a following element and that the following element is not itself marked as another range start.
From the CVE record · Linux
The Linux kernel’s netfilter xt_multiport checkentry path does not validate how multiport v1 rules encode port ranges. When a malformed rule is interpreted, ports_match_v1() can step past the last valid ports[] element. The input does not specify how an attacker could install such a rule.
Engineers running Linux kernels with netfilter xt_multiport should check their exposure; affected versions are not specified.