Weakness ID: 911
Abstraction: Base Status: Incomplete
The software uses a reference count to manage a
resource, but it does not update or incorrectly updates the reference count.
Reference counts can be used when tracking how many objects contain a reference to a particular
resource, such as in memory management or garbage collection. When the reference count reaches zero, the resource can be de-allocated or reused because there are no more objects that use it. If the reference count accidentally reaches zero, then the resource might be released too soon, even though it is still in use. If all objects no longer use the resource, but the reference count is not zero, then the resource might not ever be released.
Time of Introduction
Likelihood of Exploit
chain: reference count is not decremented, leading
to memory leak in OS by sending ICMP packets.
Reference count for shared memory not decremented
when a function fails, potentially allowing unprivileged users to read
chain: improper reference count tracking leads to
file descriptor consumption
chain: integer overflow in reference counter
causes the same variable to be destroyed twice.
Incorrect reference count calculation leads to
improper object destruction and code
chain: incorrect update of reference count leads
to memory leak.
chain/composite: use of incorrect data type for a
reference counter allows an overflow of the counter, leading to a free of
memory that is still in use.
Improper reference counting leads to failure of
chain: improper reference counting in a garbage
collection routine leads to use-after-free
chain: reference count not correctly maintained
when client disconnects during a large operation, leading to a
Reference count not always incremented, leading to
crash or code execution.
improper reference counting leads to expired
OS kernel increments reference count twice but
only decrements once, leading to resource consumption and
OS kernel driver allows code
improper reference counting leads to exhaustion of
Race condition causes reference counter to be
decremented prematurely, leading to the destruction of still-active object
and an invalid pointer dereference.
improper reference counting leads to
the weakness exists independent of other weaknesses)
Submissions Submission Date Submitter Organization Source 2012-12-21 MITRE Internal CWE Team
More information is available — Please select a different filter.