VxWorks Memory Allocation
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Wind River Inc | VxWorks 7 | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Windriver | Vxworks |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.098% probability within 30 days)
| Link | Providers |
|---|---|
| https://support2.windriver.com/index.php?page=cve |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Windriver
Windriver vxworks |
|
| Vendors & Products |
Windriver
Windriver vxworks |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Wind River VxWorks 7 24.03 through 26.03, a memory leak occurs under specific, non-default configuration states when processing specific service routines, causing the system to terminate operations before releasing allocated memory pools. Fixed in VxWorks 7 26.09 | |
| Title | VxWorks Memory Allocation | |
| Weaknesses | CWE-401 | |
| References |
| |
| Metrics |
cvssV3_1
|