Call only asynchronous-safe functions within signal handlers. For strictly conforming programs, only the C standard library functions
signal() can be safely called from within a signal handler.
...the signal handler calls any function in the standard library other than the
quick_exitfunction, or the
signalfunction with the first argument equal to the signal number corresponding to the signal that caused the invocation of the handler.
Implementations may define a list of additional asynchronous-safe functions. These functions can also be called within a signal handler. This restriction applies to library functions as well as application-defined functions.
According to the C Rationale, 18.104.22.168 [C99 Rationale 2003],
When a signal occurs, the normal flow of control of a program is interrupted. If a signal occurs that is being trapped by a signal handler, that handler is invoked. When it is finished, execution continues at the point at which the signal occurred. This arrangement can cause problems if the signal handler invokes a library function that was being executed at the time of the signal.
In general, it is not safe to invoke I/O functions from within signal handlers. Programmers should ensure a function is included in the list of an implementation's asynchronous-safe functions for all implementations the code will run on before using them in signal handlers.
Noncompliant Code Example
In this noncompliant example, the C standard library functions
free() are called from the signal handler via the function
log_message(). Neither function is asynchronous-safe.
Signal handlers should be as concise as possible—ideally by unconditionally setting a flag and returning. This compliant solution sets a flag of type
volatile sig_atomic_t and returns; the
free() functions are called directly from
Noncompliant Code Example (
longjmp() function from within a signal handler can lead to undefined behavior if it results in the invocation of any non-asynchronous-safe functions. Consequently, neither
longjmp() nor the POSIX
siglongjmp() functions should ever be called from within a signal handler.
This noncompliant code example is similar to a vulnerability in an old version of Sendmail [VU #834865]. The intent is to execute code in a
main() loop, which also logs some data. Upon receiving a
SIGINT, the program transfers out of the loop, logs the error, and terminates.
However, an attacker can exploit this noncompliant code example by generating a
SIGINT just before the second
if statement in
log_message(). The result is that
longjmp() transfers control back to
log_message() is called again. However, the first
if statement would not be executed this time (because
buf is not set to
NULL as a result of the interrupt), and the program would write to the invalid memory location referenced by
In this compliant solution, the call to
longjmp() is removed; the signal handler sets an error flag instead:
Noncompliant Code Example (
In this noncompliant code example, the
int_handler() function is used to carry out tasks specific to
SIGINT and then raises
SIGTERM. However, there is a nested call to the
raise() function, which is undefined behavior.
In this compliant solution,
term_handler() instead of raising
The following table from the POSIX standard [IEEE Std 1003.1:2013] defines a set of functions that are asynchronous-signal-safe. Applications may invoke these functions, without restriction, from a signal handler.
All functions not listed in this table are considered to be unsafe with respect to signals. In the presence of signals, all POSIX functions behave as defined when called from or interrupted by a signal handler, with a single exception: when a signal interrupts an unsafe function and the signal handler calls an unsafe function, the behavior is undefined.
The C Standard, 22.214.171.124, paragraph 4 [ISO/IEC 9899:2011], states
If the signal occurs as the result of calling the abort or raise function, the signal handler shall not call the raise function.
However, in the description of
signal(), POSIX [IEEE Std 1003.1:2013] states
This restriction does not apply to POSIX applications, as POSIX.1-2008 requires
raise()to be async-signal-safe.
See also undefined behavior 131.
signal() manual page lists a few additional functions that are asynchronous-safe in OpenBSD but "probably not on other systems" [OpenBSD], including
syslog_r() but only when the
syslog_data struct is initialized as a local variable.
|Axivion Bauhaus Suite|
|Compass/ROSE||Can detect violations of the rule for single-file programs|
|LDRA tool suite|
88 D, 89 D
Properly define signal handlers
Checks for function called from signal handler not asynchronous-safe (rule fully covered)
For an overview of software vulnerabilities resulting from improper signal handling, see Michal Zalewski's paper "Delivering Signals for Fun and Profit" [Zalewski 2001].
CERT Vulnerability Note VU #834865, "Sendmail signal I/O race condition," describes a vulnerability resulting from a violation of this rule. Another notable case where using the
longjmp() function in a signal handler caused a serious vulnerability is wu-ftpd 2.4 [Greenman 1997]. The effective user ID is set to 0 in one signal handler. If a second signal interrupts the first, a call is made to
longjmp(), returning the program to the main thread but without lowering the user's privileges. These escalated privileges can be used for further exploitation.
Key here (explains table format and definitions)
|ISO/IEC TS 17961:2013||Calling functions in the C Standard Library other than ||Prior to 2018-01-12: CERT: Unspecified Relationship|
|CWE 2.11||CWE-479, Signal Handler Use of a Non-reentrant Function||2017-07-10: CERT: Exact|
|[C99 Rationale 2003]||Subclause 5.2.3, "Signals and Interrupts"|
Subclause 126.96.36.199, "The
|[Dowd 2006]||Chapter 13, "Synchronization and State"|
|[IEEE Std 1003.1:2013]||XSH, System Interfaces, |
XSH, System Interfaces,
|[ISO/IEC 9899:2011]||188.8.131.52, "The |
|[Zalewski 2001]||"Delivering Signals for Fun and Profit"|
adjust column widths