In the Linux kernel, the following vulnerability has been resolved:
drm: Fix use-after-free read in drm_getunique()
There is a time-of-check-to-time-of-use error in drmgetunique() due to retrieving filepriv->master prior to locking the device's master mutex.
An example can be seen in the crash report of the use-after-free error found by Syzbot: https://syzkaller.appspot.com/bug?id=148d2f1dfac64af52ffd27b661981a540724f803
In the report, the master pointer was used after being freed. This is because another process had acquired the device's master mutex in drmsetmasterioctl(), then overwrote fpriv->master in drmnewset_master(). The old value of fpriv->master was subsequently freed before the mutex was unlocked.
To fix this, we lock the device's master mutex before retrieving the pointer from from fpriv->master. This patch passes the Syzbot reproducer test.
[
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.14.237"
}
]
},
{
"events": [
{
"introduced": "4.15"
},
{
"fixed": "4.19.195"
}
]
},
{
"events": [
{
"introduced": "4.20"
},
{
"fixed": "5.4.126"
}
]
},
{
"events": [
{
"introduced": "5.5"
},
{
"fixed": "5.10.44"
}
]
},
{
"events": [
{
"introduced": "5.11"
},
{
"fixed": "5.12.11"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "5.13-rc1"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "5.13-rc2"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "5.13-rc3"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "5.13-rc4"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "5.13-rc5"
}
]
}
]
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2021-47280.json"