VxWorks 7 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 Systems 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 |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Windriver
Windriver vxworks |
|
| Vendors & Products |
Windriver
Windriver vxworks |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In Wind River VxWorks 7 prior to 26.09, specific system call arguments can result in the process management subsystem failing to properly release allocated kernel memory before terminating the calling application. Fixed in Version 26.09 | |
| Title | VxWorks 7 Memory allocation | |
| Weaknesses | CWE-401 | |
| References |
| |
| Metrics |
cvssV3_1
|