CVE-2026-45844
published 2026-05-27CVE-2026-45844: In the Linux kernel, the following vulnerability has been resolved: netfilter: arp_tables: fix IEEE1394 ARP payload parsing Weiming Shi says…
medium5.5
In the Linux kernel, the following vulnerability has been resolved:
netfilter: arp_tables: fix IEEE1394 ARP payload parsing
Weiming Shi says:
"arp_packet_match() unconditionally parses the ARP payload assuming two
hardware addresses are present (source and target). However,
IPv4-over-IEEE1394 ARP (RFC 2734) omits the target hardware address
field, and arp_hdr_len() already accounts for this by returning a
shorter length for ARPHRD_IEEE1394 devices.
As a result, on IEEE1394 interfaces arp_packet_match() advances past a
nonexistent target hardware address and reads the wrong bytes for both
the target device address comparison and the target IP address. This
causes arptables rules to match against garbage data, leading to
incorrect filtering decisions: packets that should be accepted may be
dropped and vice versa.
The ARP stack in net/ipv4/arp.c (arp_create and arp_process) already
handles this correctly by skipping the target hardware address for
ARPHRD_IEEE1394. Apply the same pattern to arp_packet_match()."
Mangle the original patch to always return 0 (no match) in case user
matches on the target hardware address which is never present in
IEEE1394.
Note that this returns 0 (no match) for either normal and inverse match
because matching in the target hardware address in ARPHRD_IEEE1394 has
never been supported by arptables. This is intentional, matching on the
target hardware address should never evaluate true for ARPHRD_IEEE1394.
Moreover, adjust arpt_mangle to drop the packet too as AI suggests:
In arpt_mangle, the logic assumes a standard ARP layout. Because
IEEE1394 (FireWire) omits the target hardware address, the linear
pointer arithmetic miscalculates the offset for the target IP address.
This causes mangling operations to write to the wrong location, leading
to packet corruption. To ensure safety, this patch drops packets
(NF_DROP) when mangling is requested for these fields on IEEE1394
devices, as the current implementation cannot correctly map the
Affected
10 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| linux | linux | — | — |
| linux | linux | >= 6752c8db8e0cfedb44ba62806dd15b383ed64000 < 0f23a1457695f1a61f64367e39f0f9cfa29947d1 | 0f23a1457695f1a61f64367e39f0f9cfa29947d1 |
| linux | linux | >= 6752c8db8e0cfedb44ba62806dd15b383ed64000 < 1e285362ef7096eb12733370d59e033f4a1d294a | 1e285362ef7096eb12733370d59e033f4a1d294a |
| linux | linux | >= 6752c8db8e0cfedb44ba62806dd15b383ed64000 < 84e8536c981338d0d8cc6e712cf71a936a93e13f | 84e8536c981338d0d8cc6e712cf71a936a93e13f |
| linux | linux | >= 6752c8db8e0cfedb44ba62806dd15b383ed64000 < ad9973df8e0eeb123d9ec4d18828e05b7d44ff4b | ad9973df8e0eeb123d9ec4d18828e05b7d44ff4b |
| linux | linux | >= 6752c8db8e0cfedb44ba62806dd15b383ed64000 < 03ea11dbefaa55c502735ee551c89ef773fe753b | 03ea11dbefaa55c502735ee551c89ef773fe753b |
| linux | linux | >= 6752c8db8e0cfedb44ba62806dd15b383ed64000 < 1c55053f8ffdc060006df898fd3664e3d1bfac7b | 1c55053f8ffdc060006df898fd3664e3d1bfac7b |
| linux | linux | >= 6752c8db8e0cfedb44ba62806dd15b383ed64000 < ac698d81fd6619c7504cee913f1cab5285fba1b7 | ac698d81fd6619c7504cee913f1cab5285fba1b7 |
| linux | linux | >= 6752c8db8e0cfedb44ba62806dd15b383ed64000 < 1e8e3f449b1e73b73a843257635b9c50f0cc0f0a | 1e8e3f449b1e73b73a843257635b9c50f0cc0f0a |
| linux | linux_kernel | — | — |