CVE-2026-80733

net: remove WARN_ON_ONCE() from sk_mc_loop()

N/A
Published: September 3, 2026 at 08:21 AM UTC
Updated: September 3, 2026 at 01:34 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
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: net: remove WARN_ON_ONCE() from sk_mc_loop() sk_mc_loop() can be called for sockets that are neither AF_INET nor AF_INET6 (e.g. AF_PACKET sockets when sending packets via raw/packet socket over virtual devices such as VRF or ipvlan). In such cases, sk_family is not AF_INET/AF_INET6 and sk_mc_loop() falls through the switch statement and triggers WARN_ON_ONCE(1). Non-INET sockets do not support IP_MULTICAST_LOOP or IPV6_MULTICAST_LOOP options, so loopback should default to true without generating a warning.

Affected

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

v ≥ 3.14.40v ≥ 3.18.13v ≥ 3.19.63.14.40 ≤ v < 3.153.18.13 ≤ v < 3.193.19.6 ≤ v < 3.204.0 ≤ v < 5.10.2654.0 ≤ v < 5.15.2164.0 ≤ v < 6.1.1834.0 ≤ v < 6.12.1044.0 ≤ v < 6.18.454.0 ≤ v < 6.6.1524.0 ≤ v < 7.1.94.0 ≤ v < 7.23.14.403.18.133.19.63fe207e4637a2e792c46a08666aa722f77d7f8f74.0c8c30b2b17f2133e953850c547e3902c3a3d80e2c91f81773cd4bbebfe744e9ab30a7ce093f9b930f60e5990d9c1424af9dbca60a23ba2a1c7c1ce90
Vendor states this is fixed in 0d75f2c1d0764efa756ad9c1e078d8c09ea8fc1f (fixed)
Vendor states this is fixed in 97133c4d42654578fab95abe47359ebe784dde18 (fixed)
Vendor states this is fixed in ad7dbb1d14b1b4406eca8ef9478e8de312ba0cfe (fixed)
Vendor states this is fixed in ad7fa2f411cb30f63d6725f111be134064cdb718 (fixed)
Vendor states this is fixed in b8a39a09ae4eaae04309e1e38ed6a1101d967496 (fixed)
Vendor states this is fixed in c8f256dc849205ccb2bd78bd99a3497b972b44e0 (fixed)
Vendor states this is fixed in d2adc4e80b29e58b5162ae09f0f657a215806c8c (fixed)
Vendor states this is fixed in f625c742b33dc137c209dd13d1c5f12b1c18d71c (fixed)
Affected range stops below 3.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.19, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.0 (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.

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