In file selectmodule.c

our static code scanner has reported the following case, function set2list is liable to return NULL (if PyTuple_New failed),  would any chance the NULL pointer be dereferenced (Py_DECREF(fdlist) after set2list) or it would just raise python exception to handle PyTuple_New error ?

static PyObject *
select_select(PyObject *self, PyObject *args)
{
    ......
    if (n < 0) {
        PyErr_SetFromErrno(SelectError);
    }
#endif
    else {
        /* any of these three calls can raise an exception.  it's more
           convenient to test for this after all three calls... but
           is that acceptable?
        */
        ifdlist = set2list(&ifdset, rfd2obj);          //   || <=====
        ofdlist = set2list(&ofdset, wfd2obj);          //   ||
        efdlist = set2list(&efdset, efd2obj);          //   ||
        if (PyErr_Occurred())
            ret = NULL;
        else
            ret = PyTuple_Pack(3, ifdlist, ofdlist, efdlist);

        Py_DECREF(ifdlist);
        Py_DECREF(ofdlist);
        Py_DECREF(efdlist);

This has been fixed for 3.x in #18408 but not backported to 2.7.

New changeset e6a55dd8391651a7d3a97b6215e70e48e628d3d7 by Xiang Zhang in branch '2.7':
bpo-29874: fix INCREF for possible NULL values in select_select() (GH-758)
https://github.com/python/cpython/commit/e6a55dd8391651a7d3a97b6215e70e48e628d3d7