1. 9
  1. 3

    I used to run Coverity on large projects at a previous job, and I believe it would have found this issue since it is a simple unprotected variable in a struct. However, Coverity currently reports over 6000 issues in the kernel, and I don’t think there is a systematic effort to fix all of them (and many are probably not exploitable). The scan reports are public but I can’t figure out how to find old results, and this problem was fixed in the version they are currently scanning so it does not appear currently.