dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-14605

HIGH · 7.8 CVSS v3.1 Published 2026-07-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click 7 weeks old

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 · unedited
A vulnerability was identified in RT-Thread up to 5.0.2. Affected by this vulnerability is the function recvmsg in the library bsp/loongson/ls1cdev/libraries/ls1c_can.h of the component ls1c CAN Handler. Such manipulation leads to stack-based buffer overflow. Local access is required to approach this attack. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

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 confidence

Stack-based buffer overflow in the recvmsg function of the ls1c CAN Handler library (ls1c_can.h) in RT-Thread up to v5.0.2 allows local attackers to overflow a stack buffer, potentially achieving code execution. The vulnerability exists in the CAN message receive path for Loongson LS1C embedded hardware.

MitigationSince the vendor did not respond, obtain the source code and add explicit bounds checking on message length fields before copying to stack buffers in recvmsg. Verify no newer RT-Thread version exists with patched code, or consider compensating controls such as restricting local access to the device.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check RT-Thread version
    Run 'version' command in RT-Thread finsh shell, or check the version define in rtthread.h (typically at include/rtconfig.h or in the build system)
    Affected if Version is v5.0.2 or earlier (the vulnerability affects up to v5.0.2)
  2. Identify if ls1c CAN driver is present
    Search for ls1c_can.h in the project source tree, typically under drivers/ or bsp/loongson/ directory, or list loaded CAN drivers via 'list_device' command in finsh shell
    Affected if The ls1c CAN handler source file (ls1c_can.h) exists in the build and is being compiled
  3. Confirm hardware platform is Loongson LS1C
    Check the BSP (Board Support Package) in use - look for ls1c reference in board configuration files (often in bsp/loongson/ls1c/ or similar path), or run 'board_info' command if available
    Affected if The system is built for Loongson LS1C embedded hardware
  4. Verify CAN interface is enabled and active
    Run 'list_device' in RT-Thread finsh shell to see if a CAN device is registered, or check rtconfig.h for RT_USING_CAN macro defined, or check if CAN device appears in '/dev' if using device filesystem
    Affected if A CAN device interface (can0, can1, etc.) is present and initialized

A user is affected if they are running RT-Thread v5.0.2 or earlier on Loongson LS1C hardware with the ls1c CAN driver enabled and an active CAN interface.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the vendor did not respond, obtain the source code and add explicit bounds checking on message length fields before copying to stack buffers in recvmsg. Verify no newer RT-Thread version exists with patched code, or consider compensating controls such as restricting local access to the device.

Recommended fix Moderate confidence

RT-Thread 5.0.3 or later

  1. 1. Identify all RT-Thread deployments in your environment using version 5.0.2 or earlier
  2. 2. Download RT-Thread version 5.0.3 or later from the official repository at https://github.com/RT-Thread/rt-thread
  3. 3. Review the ls1c CAN driver component (bsp/loongson/ls1cdev/libraries/ls1c_can.h) in the new version to confirm the recvmsg function buffer overflow has been addressed
  4. 4. Rebuild firmware images with the updated RT-Thread version
  5. 5. Test the CAN functionality thoroughly, especially the recvmsg path, to verify no regressions were introduced
  6. 6. Deploy the updated firmware to affected devices
  7. 7. If upgrade is not immediately possible, implement input validation on CAN receive paths to limit buffer sizes and enable compiler stack protection flags (-fstack-protector-strong)

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14605 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-14605 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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