CVE-2026-74656ipv4: fix use-after-free in fib_nhc_update_mtu()
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: ipv4: fix use-after-free in fib_nhc_update_mtu() fib_nhc_update_mtu() walks the nexthop exception table under RTNL, but RTNL does not serialize this walk with PMTU exception updates. The walk uses rcu_dereference_protected() with a constant true condition without holding fnhe_lock. The following interleaving can therefore occur: CPU 0 CPU 1 fib_nhc_update_mtu() update_or_create_fnhe() load fnhe spin_lock_bh(&fnhe_lock) fnhe_remove_oldest() unlink fnhe kfree_rcu(fnhe, rcu) <quiescent state> access fnhe after grace period KASAN reported: BUG: KASAN: slab-use-after-free in fib_nhc_update_mtu+0x3df/0x410 Read of size 8 at addr ffff888107d49000 by task poc/90 Call Trace: fib_nhc_update_mtu+0x3df/0x410 fib_sync_mtu+0x7a/0xd0 fib_netdev_event+0x229/0x3f0 netif_set_mtu_ext+0x33a/0x570 dev_set_mtu+0x88/0x120 The same walk updates fnhe_pmtu and fnhe_mtu_locked. These fields form a pair and other writers serialize them with fnhe_lock. RCU alone prevents reclamation, but would still allow concurrent writers to leave a mixed pair. Walk the table under RCU and acquire fnhe_lock only while updating each exception. RCU keeps the current entry alive while the short critical section serializes its paired PMTU fields. This avoids holding the global lock while scanning all 2048 buckets for every nexthop.
- CVSS
- 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from af7d6cce53694a88d6a1bb60c9a239a6a5144459 before fd39e711866498ae94fcf9acf6f422a4f045b681; from af7d6cce53694a88d6a1bb60c9a239a6a5144459 before e1e602d6b22d5cb1641c4459c487eb18bf569e0a; from af7d6cce53694a88d6a1bb60c9a239a6a5144459 before e00f7d2b5f2540a3415a229c982af7a25ff6362e; from af7d6cce53694a88d6a1bb60c9a239a6a5144459 before dfe388da13aa784851e5ebbea90afbb099075761; from af7d6cce53694a88d6a1bb60c9a239a6a5144459 before 5a28a4b22dde92f9d293b94236314b8d6181dc4a; from af7d6cce53694a88d6a1bb60c9a239a6a5144459 before 63996ffc594d128ccec8fc0983f91effd2d3adc4; from af7d6cce53694a88d6a1bb60c9a239a6a5144459 before ed503eaad62f20cdd5122d7c3078a648a99c8f16; from af7d6cce53694a88d6a1bb60c9a239a6a5144459 before bc5bde9ce3cc36502839dfe98e068f7303a50982; and 10 more ranges | CNA record |
References
- https://git.kernel.org/stable/c/fd39e711866498ae94fcf9acf6f422a4f045b681
- https://git.kernel.org/stable/c/e1e602d6b22d5cb1641c4459c487eb18bf569e0a
- https://git.kernel.org/stable/c/e00f7d2b5f2540a3415a229c982af7a25ff6362e
- https://git.kernel.org/stable/c/dfe388da13aa784851e5ebbea90afbb099075761
- https://git.kernel.org/stable/c/5a28a4b22dde92f9d293b94236314b8d6181dc4a
- https://git.kernel.org/stable/c/63996ffc594d128ccec8fc0983f91effd2d3adc4
- https://git.kernel.org/stable/c/ed503eaad62f20cdd5122d7c3078a648a99c8f16
- https://git.kernel.org/stable/c/bc5bde9ce3cc36502839dfe98e068f7303a50982
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.