summaryrefslogtreecommitdiff
path: root/crypto
diff options
context:
space:
mode:
authorliqiong <liqiong@nfschina.com>2021-10-09 18:38:21 +0800
committerMimi Zohar <zohar@linux.ibm.com>2021-10-09 22:17:52 -0400
commiteb0782bbdfd0d7c4786216659277c3fd585afc0e (patch)
treee5ca30f7b9a1e46f7e5ba770397ac4e12eb537fe /crypto
parent6880fa6c56601bb8ed59df6c30fd390cc5f6dd8f (diff)
ima: fix deadlock when traversing "ima_default_rules".
The current IMA ruleset is identified by the variable "ima_rules" that default to "&ima_default_rules". When loading a custom policy for the first time, the variable is updated to "&ima_policy_rules" instead. That update isn't RCU-safe, and deadlocks are possible. Indeed, some functions like ima_match_policy() may loop indefinitely when traversing "ima_default_rules" with list_for_each_entry_rcu(). When iterating over the default ruleset back to head, if the list head is "ima_default_rules", and "ima_rules" have been updated to "&ima_policy_rules", the loop condition (&entry->list != ima_rules) stays always true, traversing won't terminate, causing a soft lockup and RCU stalls. Introduce a temporary value for "ima_rules" when iterating over the ruleset to avoid the deadlocks. Signed-off-by: liqiong <liqiong@nfschina.com> Reviewed-by: THOBY Simon <Simon.THOBY@viveris.fr> Fixes: 38d859f991f3 ("IMA: policy can now be updated multiple times") Reported-by: kernel test robot <lkp@intel.com> (Fix sparse: incompatible types in comparison expression.) Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions