CVE-2026-74657

ipv4: Fix fib_nlmsg_size() for RTA_VIA nexthops

N/A
Published: August 22, 2026 at 03:32 PM UTC
Updated: October 14, 2026 at 01:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix fib_nlmsg_size() for RTA_VIA nexthops fib_nlmsg_size() still estimates nexthop space as if every gateway is encoded as an IPv4 RTA_GATEWAY attribute. IPv4 routes can also carry an IPv6 gateway, which fib_nexthop_info() dumps as RTA_VIA. As a result, route notifications can allocate an skb that is too small. fib_dump_info() then fails with -EMSGSIZE and rtmsg_fib() hits the WARN_ON() that marks such failures as a fib_nlmsg_size() bug. With panic_on_warn set, this becomes a kernel panic. Mirror the actual nexthop dump layout in fib_nlmsg_size(): account for IPv6 nexthop gateways dumped as RTA_VIA, for the no-header rtnexthop layout used inside RTA_MULTIPATH, and for RTA_FLOW only when it is actually present.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.2d15662682db232da77136cd348f4c9df312ca6f9
Vendor states this is fixed in 0f0ca602941d0a81ae9514943ca06c55159c6385 (fixed)
Vendor states this is fixed in 4a5dfbae5179f6574695012a980476254df2d295 (fixed)
Vendor states this is fixed in 4ff9548d84945d2cbf9e4c207288063a200ea397 (fixed)
Vendor states this is fixed in 5307a53599fa762c06e475ee4a375252074fd324 (fixed)
Vendor states this is fixed in 57195f0ab5cfbb5ee0864e5aff15ceb48f5a5e28 (fixed)
Vendor states this is fixed in 7f80ad373ce4a7af5367ff273cea0f16e91387f3 (fixed)
Vendor states this is fixed in 9b22f13524fa0de0d963bbd3002df6c28bae3395 (fixed)
Vendor states this is fixed in a59edda6eda1252340354322d8ab318b2e9052fb (fixed)
Vendor states this is fixed in 5.10.267 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 5.2 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.104 (unaffected)
Vendor states this is fixed in 6.18.45 (unaffected)
Vendor states this is fixed in 6.6.152 (unaffected)
Vendor states this is fixed in 7.1.9 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card