# CVE-2023-31096: Memory corruption in n/a

> Local attackers can exploit a stack overflow in the Broadcom LSI Soft Modem kernel driver to escalate privileges to SYSTEM and bypass security protections.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Oct 2023
- **Updated:** 19 Sep 2024
- **Also known as:** GHSA-6hxc-fm22-74v5

## What is CVE-2023-31096?

CVE-2023-31096 is a high-severity memory corruption vulnerability in n/a, published on 10 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in Broadcom) LSI PCI-SV92EX Soft Modem Kernel Driver through 2.2.100.1 (aka AGRSM64.sys). There is Local Privilege Escalation to SYSTEM via a Stack Overflow in RTLCopyMemory (IOCTL 0x1b2150). An attacker can exploit this to elevate privileges from a medium-integrity process to SYSTEM. This can also be used to bypass kernel-level protections such as AV or PPL, because exploit code runs with high-integrity privileges and can be used in coordinated BYOVD (bring your own vulnerable driver) ransomware campaigns.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2023-31096?

It affects 1 product.


Products: Broadcom Lsi Pci-Sv92ex Firmware.

## How do I fix CVE-2023-31096?

No fix has been published for CVE-2023-31096 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-31096 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-31096 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-31096 and fix it if it is affected.

What it is: CVE-2023-31096 is a high-severity memory corruption vulnerability in n/a, published on 10 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-31096 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-31096/ (Markdown: https://insights.sbomify.com/CVE-2023-31096/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-31096
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-31096
- OSV: https://osv.dev/vulnerability/CVE-2023-31096

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-31096/
Summaries are generated and may contain mistakes; the official description above is the record.