Update content/en/ebpf.md

Co-authored-by: Maryam Tavakkoli <maryam_tavakkoli@hotmail.com>
Signed-off-by: Catherine Paganini <74001907+CathPag@users.noreply.github.com>
Signed-off-by: MaryamTavakkoli <maryam_tavakkoli@hotmail.com>

content/en/ebpf.md

@@ -21,7 +21,8 @@ However, since kernel modules operate within the kernel space, this approach int
 Normally, applications run in user space, and if the application requires some privileges from the kernel (exp. to access some hardware), then it needs to send a call referred to as a “system call” and ask for that request from the kernel. 
 This might be good enough for many scenarios, however, there are cases, in which developers require more flexibility for hardware accessibility. Observability, security, and networking features are some of the ideal examples to be implemented within the kernel space. 
 One of the possibilities to reach such a goal is to use Linux kernel modules, which allow extending the kernel base without adding directly to the kernel source code. 
-While using Linux kernel modules bring the mentioned benefits, it adds to the security risks since they can make the kernel crash.
+While using Linux kernel modules bring the mentioned benefits, it adds to the security risks because they operate within the kernel space and can make the kernel crash. 
+Kernel modules have elevated privileges and direct access to system resources, making them a potential target for attackers.
 
 ## How it helps