Description: clocksource/drivers/arm_arch_timer: Avoid infinite recursion when ftrace is enabled References: Notes: bwh> I'm not convinced this is really a security issue. Anyway, the bwh> vulnerable code path was introduced in 4.12 by commit 6acc71ccac71 bwh> "arm64: arch_timer: Allows a CPU-specific erratum to only affect a bwh> subset of CPUs". Bugs: upstream: released (4.13-rc6) [adb4f11e0a8f4e29900adb2b7af28b6bbd5c1fa4] 4.9-upstream-stable: N/A "Vulnerable code not present" 3.16-upstream-stable: N/A "Vulnerable code not present" 3.2-upstream-stable: N/A "Vulnerable code not present" sid: released (4.13.4-1) 4.9-stretch-security: N/A "Vulnerable code not present" 3.16-jessie-security: N/A "Vulnerable code not present" 3.2-wheezy-security: N/A "Vulnerable code not present"