What risks may arise when passing a lambda from…

Implicit type conversion: Java methods expect functional interfaces, whereas Kotlin lambdas have their own internal type. Although the Kotlin compiler usually performs the conversion, errors can occur in complex cases.
null safety: Kotlin lambdas can capture null values, but Java code may not be prepared to handle them, leading to NullPointerException.
Exception checking: Kotlin does not require explicit handling of checked exceptions, while Java methods may throw them. A lambda passed to Java can trigger an unchecked exception on the Java side.
Performance: Creating anonymous classes (which compile from lambdas) can have minor overhead, especially in loops or frequent creation scenarios.
Java version compatibility: Kotlin is compiled for a specific Java bytecode level. If Java code uses APIs unavailable in the target version, compatibility issues may arise.
Variable capture: Accessing mutable variables from an external scope within a lambda in Java code can be unintuitive and potentially unsafe if synchronization is not considered.
Debugging: Debugging code where Kotlin and Java lambdas interact can be more complex due to differences in stack traces and class naming.

What risks may arise when passing a lambda from Kotlin to a Java method?