Skip to content
Fencer Intel
no cvss —

CVE-2026-98347 json

IB/IPoIB: Avoid restoring OPER_UP after multicast flush

published last mo. modified 23d ago also EUVD-2026-93332

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 7%
public exploits
0
none known

Summary

In the Linux kernel, the following vulnerability has been resolved:

IB/IPoIB: Avoid restoring OPER_UP after multicast flush

ipoib_ib_dev_flush_light() temporarily clears IPOIB_FLAG_OPER_UP to prevent multicast joins while ipoib_mcast_dev_flush() is running, and restores the flag afterwards if it was previously set.

This restore races with ipoib_ib_dev_down(). If the interface is brought down while the flush is in progress, ipoib_ib_dev_down() clears IPOIB_FLAG_OPER_UP, but the flush path may set it again after the device has already gone down.

Since commit 894021a75291 ("IB/ipoib: Make the carrier_on_task race aware"), ipoib_mcast_carrier_on_task() relies on IPOIB_FLAG_OPER_UP being cleared to terminate its rtnl_trylock() retry loop. If the flag is left set after shutdown, the workqueue retries forever, causing teardown to deadlock when ipoib_ndo_uninit() waits in destroy_workqueue() while holding RTNL.

Instead of overloading IPOIB_FLAG_OPER_UP to block multicast joins during a light flush, introduce a dedicated IPOIB_FLAG_MCAST_FLUSH flag. Use it together with IPOIB_FLAG_OPER_UP to determine whether multicast joins are allowed, avoiding the race with device shutdown.

Patch / fix

  • Linux Linux 3.3, 3.11, 3.13, 3.17, 4.5, 4.8, 7.3
  • linux Debian 12 6.1.190-1
  • linux Debian 13 6.12.113-1
  • linux Debian 14 7.2.8-1
  • linux-6.12 Debian 12 6.12.113-1~deb12u1

debian advisories DEBIAN-CVE-2026-98347

  • linux Ubuntu 22.04 LTS 5.15.0-202.212
  • linux Ubuntu 24.04 LTS 6.8.0-149.149
  • linux Ubuntu 26.04 LTS 7.0.0-42.42
  • linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
  • linux-aws Ubuntu 24.04 LTS 6.8.0-1069.74
  • linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
  • linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
  • linux-gcp Ubuntu 24.04 LTS 6.8.0-1073.81

ubuntu advisories UBUNTU-CVE-2026-98347

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-rt Real Time Module 15 SP7 6.4.0-150700.7.81.1
  • kernel-syms-rt Real Time Module 15 SP7 6.4.0-150700.7.81.1
  • kernel-source-rt Real Time Module 15 SP7 6.4.0-150700.7.81.1
  • kernel-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.87.3
  • kernel-syms SLE Module for Development Tools 15 SP7 6.4.0-150700.53.87.1
  • kernel-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.53.87.3
  • kernel-source SLE Module for Development Tools 15 SP7, SLE Module for Basesystem 15 SP7 6.4.0-150700.53.87.3
  • kernel-default SLE Workstation Extension 15 SP7, SLE Module for Legacy 15 SP7, SLE Module for Basesystem 15 SP7 +2 more 6.4.0-150700.53.87.3

suse advisories SUSE-SU-2026:4940-1SUSE-SU-2026:4935-1SUSE-SU-2026:24473-1SUSE-SU-2026:24553-1SUSE-SU-2026:24422-1SUSE-SU-2026:24446-1

  • kernel-rt openSUSE Leap 16.0 6.12.0-160000.40.1
  • dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.40.1
  • kernel-64kb openSUSE Leap 16.0 6.12.0-160000.40.1
  • kernel-syms openSUSE Leap 16.0 6.12.0-160000.40.1
  • kernel-azure openSUSE Leap 16.0 6.12.0-160000.40.1
  • kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.40.1
  • kernel-source openSUSE Leap 16.0 6.12.0-160000.40.1
  • kernel-default openSUSE Leap 16.0 6.12.0-160000.40.1

opensuse advisories openSUSE-SU-2026:22167-1openSUSE-SU-2026:12131-1

  • kernel Azure Linux 3.0 6.6.158.1-1

azure linux advisories AZL-106446

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2026-98347 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-98347 updated cvss 7.0

kernel: IB/IPoIB: Avoid restoring OPER_UP after multicast flush

  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9
    affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).

Affected products

  • Linux Linux

Classification

Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.