netfilter: nft_fib: reject fib expression on the netdev egress hook
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 42df6e1d221dddc0f2acf2be37e68d553ad65f96 · < d07955dd34ecae17d35d8c7d0a273a3fba653a8c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nft_fib: reject fib expression on the netdev egress hook
A fib expression in a netdev egress base chain dereferences nft_in(pkt), NULL on the transmit path, causing a NULL pointer dereference at eval. nft_fib_validate() masks the hook with NF_INET_* values, but netdev hook numbers are a separate enum that aliases them (NF_NETDEV_EGRESS == NF_INET_LOCAL_IN), so an egress chain passes validation and then faults.
Add nft_fib_netdev_validate() that limits each result/flag to the netdev hook where the device it reads exists: the input-device cases (OIF, OIFNAME, ADDRTYPE with F_IIF) to ingress, the output-device case (ADDRTYPE with F_OIF) to egress, ADDRTYPE with no device flag to both. Also restrict nft_fib_validate() to NFPROTO_IPV4/IPV6/INET so its NF_INET_* masks are not applied to another family's hooks.
From the CVE record · Linux
A fib expression in a netdev egress base chain can pass validation and dereference a NULL input-device pointer during evaluation, causing a kernel fault. This occurs on the transmit path; the input does not specify whether an attacker needs network access, authentication, or user interaction to trigger it.
Engineers running the Linux kernel should check their vendor’s advisory for affected versions; none are listed in the input.