cve.bz

CVE-2026-98425 linux linux

no score yetEPSS 0.2%Fix available

linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: don't warn when an IBSS has no channel to scan ieee80211_request_ibss_scan() warns when regulatory leaves no allowed channel, but that can happen as the regdomain can change while IBSS is operating, and it can continue to operate briefly during the 60s grace period until it's shut down. Just remove the warning in this case.
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 11th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 6.12.112
  • Linux Linux: fixed in 6.18.54
  • Linux Linux: fixed in 7.2.8
  • Linux Linux: fixed in 7.3
  • Debian, Ubuntu, SUSE, openSUSE, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-98425 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-98425?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-98425?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-98425 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-98425

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-98425](https://cve.bz/cve/badge/CVE-2026-98425.svg)](https://cve.bz/cve/CVE-2026-98425)

HTML:

<a href="https://cve.bz/cve/CVE-2026-98425"><img src="https://cve.bz/cve/badge/CVE-2026-98425.svg" alt="CVE-2026-98425"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linuxfrom 3.4.26 before 3.5
Linuxfrom 3.7.3 before 3.8
Linux3.8 and later

Fixed in

ProductRelease lineFixed in
Linux6.126.12.112
Linux6.186.18.54
Linux7.27.2.8
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linuxno fix listedDEBIAN-CVE-2026-98425
Debian12linux-6.126.12.113-1~deb12u1DEBIAN-CVE-2026-98425
Debian13linux6.12.113-1DEBIAN-CVE-2026-98425
Debian14linux7.2.8-1DEBIAN-CVE-2026-98425
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-98425
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-98425
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-98425
Ubuntu22.04:LTSlinux, linux-aws, linux-gcp and 48 moreno fix listedUBUNTU-CVE-2026-98425
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1069.74~22.04.1UBUNTU-CVE-2026-98425 USN-9024-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1073.82~22.04.1UBUNTU-CVE-2026-98425 USN-9026-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1071.78~22.04.1UBUNTU-CVE-2026-98425 USN-9026-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1073.81~22.04.1UBUNTU-CVE-2026-98425 USN-9024-1
Ubuntu22.04:LTSlinux-hwe-6.86.8.0-149.149~22.04.1UBUNTU-CVE-2026-98425 USN-9066-1
Ubuntu22.04:LTSlinux-ibm-6.86.8.0-1069.70~22.04.1UBUNTU-CVE-2026-98425 USN-9024-1
Ubuntu22.04:LTSlinux-lowlatency-hwe-6.86.8.0-149.149.1~22.04.1UBUNTU-CVE-2026-98425 USN-9024-1
Ubuntu22.04:LTSlinux-oracle-6.86.8.0-1067.71~22.04.1UBUNTU-CVE-2026-98425 USN-9025-1
50 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise Server for NVIDIA 16.1kernel-nvidia64kb, kernel-source-nvidia6.12.0-160100.6.1SUSE-SU-2026:24691-1
openSUSELeap 16.1kernel-default-base6.12.0-160100.9.1.160100.3.14openSUSE-SU-2026:22309-1
openSUSELeap 16.1kernel-nvidia64kb, kernel-syms-nvidia, kernel-source-nvidia6.12.0-160100.6.1openSUSE-SU-2026:22313-1
openSUSELeap 16.1kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160100.9.1openSUSE-SU-2026:22309-1
openSUSETumbleweedkernel-source7.2.11-1.1openSUSE-SU-2026:12165-1
Azure Linux3kernelno fix listedAZL-108096
Alpaquita23linux-ltsno fix listedBELL-CVE-2026-98425
Alpaquita25linux-lts6.12.112-r0BELL-CVE-2026-98425
Alpaquitastreamlinux-lts6.18.55-r0BELL-CVE-2026-98425

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Low.

Red Hat's statement

A low impact flaw was found in the Linux kernel's mac80211 wireless subsystem. When the regulatory domain changes while an ad-hoc (IBSS) network is operating, the ieee80211_request_ibss_scan() function can trigger a WARN_ON_ONCE() warning when no permitted channels remain available, because an IBSS interface may continue to operate briefly during the 60-second grace period before it is shut down. A local user with the privileges needed to configure wireless interfaces (CAP_NET_ADMIN) who triggers an IBSS scan during this window can cause this warning. In default kernel configurations the impact is limited to a warning message in the kernel log and the scan request failing with -EINVAL; there is no impact on confidentiality, integrity, or memory safety. Only systems configured with the non-default panic_on_warn option could experience a kernel panic (local denial of service) as a result of this warning, which is why Red Hat assesses the impact of this flaw as Low even though the worst-case CVSS 3.1 availability metric reflects the panic_on_warn scenario. The affected Red Hat Enterprise Linux kernel and kernel-rt streams, Red Hat In-Vehicle OS, and OpenShift RHCOS components are affected, and the fix, which simply removes the unnecessary warning, is deferred to a future update given the low security risk; the residual risk is limited to non-default panic_on_warn configurations where a privileged local user could trigger a panic. The Red Hat Enterprise Linux 6 Extended Lifecycle Support stream is out of support scope for this flaw.

Red Hat's mitigation

The only security consequence of this flaw occurs on systems running with the non-default kernel option panic_on_warn enabled, where the warning causes a kernel panic. On such systems the impact can be mitigated by disabling panic-on-warn, for example by running 'sysctl kernel.panic_on_warn=0' and persisting 'kernel.panic_on_warn = 0' in a file under /etc/sysctl.d/. On systems using default kernel settings, the flaw results only in a warning message in the kernel log and no specific mitigation is required.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelFix deferred
Red Hat Enterprise Linux 7kernel-rtFix deferred
Red Hat Enterprise Linux 8kernelFix deferred
Red Hat Enterprise Linux 8kernel-rtFix deferred
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Fix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Fix deferred
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-98425.

References

Check your stackJSON