CVE-2026-99121 json
ipv4: avoid divide by zero in fib_rebalance
published 14d ago modified 12d ago also EUVD-2026-112021
- 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 8%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
ipv4: avoid divide by zero in fib_rebalance
fib_rebalance() computes the total eligible nexthop weight in one pass and programs upper bounds in a second pass. A concurrent change to ignore_routes_with_linkdown can make the first pass return zero while the second pass sees an eligible nexthop, resulting in division by zero.
If the first pass reports a zero total, set each nexthop upper bound to -1 and skip the division. This matches the IPv6 fix in commit d2c26c2911dd ("ipv6: avoid divide by zero in rt6_multipath_rebalance") and preserves the lock-free rebalance path.
Patch / fix
- Linux Linux 7.3
- linux Debian 13 6.12.115-2
- linux Debian 14 7.2.13-1
debian advisories DEBIAN-CVE-2026-99121
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-111221
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
- git.kernel.org/stable/c/baf3a767b2845eb8e68f056ee4aa5b41b151e990 commit
- git.kernel.org/stable/c/f655a26490e705ec76a79db7f412847fda342b39 commit
- git.kernel.org/stable/c/7c68f4de5090b17b63b9a0a3b01b3807e01a296a commit
- git.kernel.org/stable/c/226a974054acbd892560bfa67f0ae8ffe271a736 commit
- git.kernel.org/stable/c/0800c92ca5d1983df6843a5435299978901d1d02 commit
- git.kernel.org/stable/c/5dac5c7ba8f5f3fb4bf29f2a2c3cb552f5b83c8f commit
- git.kernel.org/stable/c/d5520e815c4b1427104ce1428ee23821f2aa824d commit
- git.kernel.org/stable/c/5046d2880fec7d49ebed2fd2866747ee1d06ad71 commit
Is CVE-2026-99121 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 FencerVendor 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-99121 updated cvss 5.5
kernel: kernel: Denial of Service via division by zero during IPv4 route rebalancing
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: 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-9affected: 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.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/baf3a767b2845eb8e68f056ee4aa5b41b151e990
- git.kernel.org /stable/c/f655a26490e705ec76a79db7f412847fda342b39
- git.kernel.org /stable/c/7c68f4de5090b17b63b9a0a3b01b3807e01a296a
- git.kernel.org /stable/c/226a974054acbd892560bfa67f0ae8ffe271a736
- git.kernel.org /stable/c/0800c92ca5d1983df6843a5435299978901d1d02
- git.kernel.org /stable/c/5dac5c7ba8f5f3fb4bf29f2a2c3cb552f5b83c8f
- git.kernel.org /stable/c/d5520e815c4b1427104ce1428ee23821f2aa824d
- git.kernel.org /stable/c/5046d2880fec7d49ebed2fd2866747ee1d06ad71
Sources
- CVE List CVE-2026-99121
- NVD CVE-2026-99121
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.