CVE-2026-37232
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in OpenAirInterface5G 2.4.0 (nr-softmodem) in the E2SM-KPM RAN Function's PRB utilization metric calculation. The functions fill_RRU_PrbTotDl() and fill_RRU_PrbTotUl() in openair2/E2AP/RAN_FUNCTION/O-RAN/ran_func_kpm_subs.c (lines 182 and 197) compute PRB usage percentages by dividing by the difference of two consecutive total_prb_aggregate samples without checking for zero. When a malicious xApp sends a high volume of E42_RIC_SUBSCRIPTION_REQUESTs via the FlexRIC iApp (port 36422/SCTP), the E2 Agent generates KPM Indication reports at high frequency. If two consecutive sampling intervals yield identical PRB aggregate values, the divisor becomes zero, triggering SIGFPE and crashing the entire 5G base station process (nr-softmodem). This results in complete 5G cell service interruption for all connected UEs. No authentication is required.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpenAirInterface5G 2.4.0 nr-softmodem contains a division by zero vulnerability in the E2SM-KPM RAN Function's PRB utilization calculation. Functions fill_RRU_PrbTotDl() and fill_RRU_PrbTotUl() compute PRB percentages by dividing by the difference of consecutive total_prb_aggregate samples without validating the divisor is non-zero. An unauthenticated malicious xApp sending rapid E42_RIC_SUBSCRIPTION_REQUESTs can trigger identical consecutive PRB samples, causing SIGFPE and crashing the entire 5G base station process.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.4.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify OpenAirInterface5G versionRun 'git log' or check version metadata in the OpenAirInterface5G installation directory to confirm the installed version is 2.4.0Affected if Version is exactly 2.4.0
-
Confirm E2SM-KPM module is enabledInspect the E2SM-KPM configuration files or runtime settings for the nr-softmodem to determine if the E2SM-KPM RAN Function is loaded and activeAffected if E2SM-KPM RAN Function is enabled and processing PRB metrics
-
Verify nr-softmodem process is runningRun 'ps aux | grep nr-softmodem' or check process list to confirm the nr-softmodem process is activeAffected if nr-softmodem process is running with E2SM-KPM support
-
Check for presence of vulnerable functionsSearch the source code for fill_RRU_PrbTotDl() and fill_RRU_PrbTotUl() functions in the E2SM-KPM implementation filesAffected if These functions exist without zero-check validation on the divisor
-
Monitor for SIGFPE crashesCheck system logs or dmesg for SIGFPE signals affecting nr-softmodem, or monitor for unexpected nr-softmodem restartsAffected if SIGFPE crashes of nr-softmodem are occurring
Running OpenAirInterface5G version 2.4.0 with the E2SM-KPM RAN Function enabled allows a malicious xApp to trigger a division by zero and crash nr-softmodem.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataAdd input validation to ensure the PRB sample difference (divisor) is non-zero before performing division in both fill_RRU_PrbTotDl() and fill_RRU_PrbTotUl(); additionally implement rate limiting on E2AP subscription requests to mitigate high-frequency sample generation.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-37232 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-37232 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data