Nixpkgs security tracker

Login with GitHub

Suggestion detail

Dismissed
(max. allowed matches exceeded)
Permalink CVE-2026-63992
9.1 CRITICAL
  • 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): High (H)
  • 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): High (H)
  • Modified Scope (MS): Unchanged (U)
  • Modified Integrity (MI): None (N)
  • Modified Availability (MA): High (H)
created 6 days, 9 hours ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
tunnels: do not assume transport header in iptunnel_pmtud_check_icmp()

In the Linux kernel, the following vulnerability has been resolved: tunnels: do not assume transport header in iptunnel_pmtud_check_icmp() In some cases, iptunnel_pmtud_check_icmp() can be called while skb transport header is not set. This triggers an out-of-bound access, because (typeof(skb->transport_header))~0U is 65535. Access the icmp header based on IPv4 network header, after making sure icmp->type is present in skb linear part. Note that iptunnel_pmtud_check_icmpv6()) is fine.

Affected products

Linux
  • <a096b6e34f602950af9a2b0856cd93a5f4c276d7
  • <5a92cb45e34749865d03daf8d3500f77b5f6644c
  • =<6.18.*
  • <cb549df9ce4ee15c9d5b19ddab12cf2128e4313c
  • =<7.0.*
  • <7f4f7efe7f30edd29c4988de01728bf2398217e4
  • =<5.15.*
  • =<6.12.*
  • <5.9
  • =<6.1.*
  • =<*
  • <43368636c663cff6e59dde93cf4b8e43ac28eb93
  • =<6.6.*
  • ==5.9
  • <e917d0c69f01af2bb4fbea2b66d560a53b3ac7ec
  • <c7b7ec3e69e673c0d6b57f74d21da50c485c598e
  • <509323077ef79a26ba0c60bb556e45c12c398b2d
  • =<5.10.*