...
This noncompliant code example illustrates Xen Security Advisory CVE-2015-8550 / XSA-155 In this example, the following code is vulnerable to a data race where the integer referenced by ps could be modified by a second thread that ran between the two reads of the variable.
...
| Tool | Version | Checker | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Astrée |
| read_data_race write_data_race | Supported by sound analysis (data race alarm) | ||||||||
| CodeSonar |
| CONCURRENCY.DATARACE CONCURRENCY.MAA | Data race Multiple Accesses of Atomic | ||||||||
| Coverity |
| MISSING_LOCK (partial) | Implemented | ||||||||
| Helix QAC |
| C1765, C1766, C1770, C1771 C++1765, C++1766, C++1770, C++1771 | |||||||||
| Parasoft C/C++test |
| CERT_C-CON43-aUsage of functions prone to race is not allowed | Do not use global variable with different locks set | ||||||||
| PC-lint Plus |
| 457 | Partially supported: access is detected at the object level (not at the field level) | ||||||||
| Polyspace Bug Finder |
| CERT C: Rule CON43-C | Checks for data race (rule fully covered) | ||||||||
| V1088 | Data race | Multiple tasks perform unprotected non-atomic operations on shared variables |
Related Vulnerabilities
Search for vulnerabilities resulting from the violation of this rule on the CERT website.
...