Nixpkgs security tracker

Login with GitHub

Suggestion detail

Dismissed
(max. allowed matches exceeded)
Permalink CVE-2026-64116
7.5 HIGH
  • CVSS version (CVSS): 3.1
  • Attack Vector (AV): Network (N)
  • Attack Complexity (AC): Low (L)
  • Privileges Required (PR): None (N)
  • User Interaction (UI): None (N)
  • Scope (S): Unchanged (U)
  • Confidentiality (C): None (N)
  • Integrity (I): None (N)
  • Availability (A): High (H)
  • Modified Attack Vector (MAV): Network (N)
  • Modified Attack Complexity (MAC): Low (L)
  • Modified Privileges Required (MPR): None (N)
  • Modified User Interaction (MUI): None (N)
  • Modified Confidentiality (MC): None (N)
  • Modified Scope (MS): Unchanged (U)
  • Modified Integrity (MI): None (N)
  • Modified Availability (MA): High (H)
created 6 days, 5 hours ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
ipv6: ioam: add NULL check for idev in ipv6_hop_ioam()

In the Linux kernel, the following vulnerability has been resolved: ipv6: ioam: add NULL check for idev in ipv6_hop_ioam() Reported by Sashiko: The function ipv6_hop_ioam() accesses __in6_dev_get(skb->dev)->cnf.ioam6_enabled without validating the returned idev pointer. Because addrconf_ifdown() can concurrently clear dev->ip6_ptr via RCU, __in6_dev_get() can return NULL during interface teardown, which could cause a NULL pointer dereference when processing an IOAM Hop-by-Hop option. Let's add a check and use SKB_DROP_REASON_IPV6DISABLED accordingly.

Affected products

Linux
  • <cf75eb6617042c8cff6112daeed7791809fc9dd2
  • =<6.18.*
  • <902daac307eb7e1955ce05b071950f3cba88c963
  • <5.15
  • =<7.0.*
  • =<6.12.*
  • <d4ea0dfd75011b78cebf3808f98ac4c4f51a6fb9
  • ==5.15
  • =<*
  • =<6.1.*
  • <c7e8971abd70e9d022f1c251ba2508f8dc7f2db8
  • <abdd03229414b5a52943b65a60f34b84cea5ac59
  • =<5.15.*
  • <1dca7e491f070ac49b3d934f16ee953a53b37f38
  • =<6.6.*
  • <09cbfd4b81ae90963dadb1de99b63b702e73290a