# CVE-2026-14629: RT-Thread Parameter lwp_syscall.c sys_ioctl divide by zero

> A divide-by-zero flaw in RT-Thread's syscall handler allows remote attackers to cause a denial of service.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** GHSA-jp84-4rqr-29c5

## What is CVE-2026-14629?

CVE-2026-14629 is a medium-severity denial of service vulnerability in RT-Thread, published on 4 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw has been found in RT-Thread up to 5.2.2. Affected is the function read/write/sys_ioctl of the file components/lwp/lwp_syscall.c of the component Parameter Handler. Executing a manipulation can lead to divide by zero. The attack may be launched remotely. The exploit has been published and may be used. The pull request to fix this issue awaits acceptance.

Weakness: CWE-404 (Improper Resource Shutdown or Release), CWE-369 (Divide By Zero)

## Which versions are affected by CVE-2026-14629?


## How do I fix CVE-2026-14629?

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

## Is CVE-2026-14629 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14629 and fix it if it is affected.

What it is: CVE-2026-14629 is a medium-severity denial of service vulnerability in RT-Thread, published on 4 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-14629 exists.

Affected product: RT-Thread. 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-2026-14629/ (Markdown: https://insights.sbomify.com/CVE-2026-14629/index.md)
```

## Sources

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

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