SEI CERT C Coding Standard

Space shortcuts

Page tree

Versions Compared

Old Version 27

changes.mady.by.user Anirban Gangopadhyay

Saved on

compared with

New Version Current

changes.mady.by.user David Svoboda

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: REM Cost Reform

...

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

4971, 4972, 4981, 4982

Tool

Version

Checker

Description

CodeSonar
Include Page
CodeSonar_V
CodeSonar_V

CONCURRENCY.DU

Double Unlock

Helix QAC

Include Page
Helix QAC_V
Helix QAC_V

C4971DF4971, C4972DF4972, C4981DF4981, C4982

C++4971, C++4972, C++4981, C++4982

DF4982


Parasoft C/C++test

Include Page
Parasoft_V
Parasoft_V

CERT_C-POS48-a
CERT_C-POS48-b

Do not destroy another thread's mutex
Do not release a lock that has not been acquired

Polyspace Bug Finder

Include Page
Polyspace Bug Finder_V
Polyspace Bug Finder_V

CERT C: Rule POS48-CChecks for destruction of locked mutex (rule fully covered)PRQA QA-C
Include Page
PRQA QA-C_vPRQA QA-C_v

Related Vulnerabilities

Search for vulnerabilities resulting from the violation of this rule on the CERT website.

...