diff --git a/pocs/linux/kernelctf/CVE-2024-50264_lts_cos/docs/exploit.md b/pocs/linux/kernelctf/CVE-2024-50264_lts_cos/docs/exploit.md
index a88fc569..c87d2155 100755
--- a/pocs/linux/kernelctf/CVE-2024-50264_lts_cos/docs/exploit.md
+++ b/pocs/linux/kernelctf/CVE-2024-50264_lts_cos/docs/exploit.md
@@ -1,5 +1,4 @@
 # Vulnerability
----
 This vulnerability occurs because the vsk->trans pointer in virtio_transport_destruct() is not initialized to NULL after being freed, resulting in a dangling pointer.
 ```cpp
 void virtio_transport_destruct(struct vsock_sock *vsk)
@@ -38,9 +37,8 @@ static bool virtio_transport_space_update(struct sock *sk,
 ```
 
 # Race Condition Scenario
----
 This vulnerability is a race condition that must be triggered by precisely controlling the `vsock_loopback_work()` worker used for loopback communication. The full scenario is as follows and can be divided into three main flows.
-```cpp
+```text
                      cpu0                                                      cpu1
     
                                                                socket(A)    // [1.1]
@@ -693,4 +691,4 @@ int main(int argc, void *argv[])
 
     [...]
 }
-```
\ No newline at end of file
+```