...
The risks of ignoring mutex ownership are similar to the risk of not using mutexes at all, which can result in a violation of data integrity.
Rule | Severity | Likelihood | Detectable | RepairableRemediation Cost | Priority | Level |
|---|---|---|---|---|---|---|
POS48-C | Medium | Probable | No | NoHigh | P4 | L3 |
Automated Detection
Tool | Version | Checker | Description | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CodeSonar |
| CONCURRENCY.DU | Double Unlock | |||||||||||||
| Helix QAC |
| DF4971, DF4972, DF4981, DF4982 | ||||||||||||||
| Parasoft C/C++test |
| BD CERT_C- TRS-DSTRLOCK, BD-TRS-REVLOCKPOS48-a | Do not destroy another thread's mutex | |||||||||||||
| R2016b | Destruction of locked mutex |
| CERT C: Rule POS48-C | Checks for destruction of locked mutex (rule fully covered)Task tries to destroy a mutex in the locked state |
Related Vulnerabilities
Search for vulnerabilities resulting from the violation of this rule on the CERT website.
...