Bug 2520980 (CVE-2026-74581) - CVE-2026-74581 kernel: net: ipv6: use-after-free in fib6_rule_suppress due to stale res->rt6 pointer
Summary: CVE-2026-74581 kernel: net: ipv6: use-after-free in fib6_rule_suppress due to...
Keywords:
Status: NEW
Alias: CVE-2026-74581
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-21 12:57 UTC by OSIDB Bzimport
Modified: 2026-08-22 04:42 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-08-21 12:57:57 UTC
A use-after-free vulnerability was found in the Linux kernel's IPv6 FIB rule lookup path. In fib6_rule_suppress(), when a route is suppressed and released via ip6_rt_put_flags(), the res->rt6 pointer is not cleared. If no later rule supplies a replacement route, fib6_rule_lookup() returns the stale (freed) rt6_info to its caller. The subsequent dst_release() then operates on freed memory, hitting rcuref_put_slowpath(). A local attacker who can configure IPv6 routing/FIB rules could trigger this to cause a denial of service (kernel crash) or potentially escalate privileges.

Comment 3 Mauro Matteo Cascella 2026-08-21 17:39:23 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026082100-CVE-2026-74581-47ca@gregkh/T/#u

Comment 4 Akiyoshi Kurita 2026-08-22 04:42:04 UTC
The proposed mitigation does not appear to be applicable to the affected RHEL kernels because IPv6 is built directly into the kernel (`CONFIG_IPV6=y`), rather than provided as a loadable kernel module.

Therefore, the following configuration cannot prevent the IPv6 subsystem from being loaded:


install ipv6 /bin/true
blacklist ipv6


Since there is no `ipv6.ko` module to blacklist when `CONFIG_IPV6=y`, this mitigation would not disable the vulnerable IPv6 code path.

A kernel command-line parameter such as:


ipv6.disable=1


would appear to be a more appropriate mitigation for completely disabling IPv6 on these kernels.

Could you please confirm whether the current mitigation guidance is correct for RHEL kernels built with `CONFIG_IPV6=y`?


Note You need to log in before you can comment on or make changes to this bug.