CVE-2026-74630

ipv6: prevent in6_dev_get() from resurrecting inet6_dev

HIGH
7.8
CVSS Score
Published: August 22, 2026 at 03:32 PM UTC
Updated: October 16, 2026 at 08:17 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
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: ipv6: prevent in6_dev_get() from resurrecting inet6_dev in6_dev_get() reads dev->ip6_ptr under RCU and then unconditionally increments its refcount. Device teardown can clear the pointer and drop the last reference between these operations. The increment then resurrects an object whose RCU free has already been queued, so callers can use it after it is freed. Use refcount_inc_not_zero() and return NULL when the object has already reached zero. RCU keeps the memory accessible through the attempted reference acquisition, and a successful increment pins the object for the caller. An independent run on the exact unpatched 6f5156d7a31a (v7.2-rc3) kernel reproduced the invalid reference acquisition as UID 1000: refcount_t: addition on 0; use-after-free. ip6_mc_source+0xef4/0x17e0 It was followed by the corresponding reference underflow in ip6_mc_source(). The supplied trace from the same unpatched revision additionally shows the access after the RCU read-side section ends: BUG: KASAN: slab-use-after-free in mutex_lock+0x76/0xe0 Write of size 8 at addr ffff888015b50240 by task poc/1219 Bug found and triaged by OpenAI Security Research and validated by Trail of Bits.

Affected

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

2.6.198814c4b533817df825485ff32ce6ac406c3a54d1
Vendor states this is fixed in 0e243671bc7b8eaf00f83dd2f4367436dc0cff98 (fixed)
Vendor states this is fixed in 145812b678de9f3b59780173be3c0d22ed60dd93 (fixed)
Vendor states this is fixed in 14e812ab41df0cac033479da835ec9a5de633404 (fixed)
Vendor states this is fixed in 1c206d461c680c3151daa3c89fc26eaf5bf98a7f (fixed)
Vendor states this is fixed in 680fbd7942185448eadb990a3d10a53eb946b702 (fixed)
Vendor states this is fixed in 785d908f8d21c8bc78b6fb2c2932ab662bf6918a (fixed)
Vendor states this is fixed in aedcfefdb5b7ed7f8a6196a3e68a25bdbe51d2f8 (fixed)
Vendor states this is fixed in cc5bd568f9b7683e60841b6fd02c10d64535bd6e (fixed)
Vendor states this is fixed in 2.6.19 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (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.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

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