milliways-infosec/dirtyfrag
5
0
Fork 0
mirror of https://github.com/V4bel/dirtyfrag.git synced 2026-05-16 10:50:10 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update README: clarify page cache cleanup after exploit

Browse source
This commit is contained in:
Nate River 2026-05-08 11:58:36 +08:00 • committed by GitHub
parent 892d9a31d3
commit f2796739b2
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 8 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

8
README.md
View file

@ -26,6 +26,14 @@ git clone https://github.com/V4bel/dirtyfrag.git && cd dirtyfrag && gcc -O0 -Wal
This PoC is provided as accurate information following consultation with linux-distros. Do not use it on systems that you are not authorized to test. This PoC is provided as accurate information following consultation with linux-distros. Do not use it on systems that you are not authorized to test.
> ⚠️ **Important:** After running this exploit, the page cache is contaminated. To clear the polluted page cache and ensure system stability, either run:
>
> ```bash
> echo 3 > /proc/sys/vm/drop_caches
> ```
>
> or reboot the system.
# Affected Versions # Affected Versions
The xfrm-ESP Page-Cache Write vulnerability is in scope from cac2661c53f3 (2017-01-17) up to upstream, and the RxRPC Page-Cache Write vulnerability is in scope from 2dc334f1a63a (2023-06) up to upstream. The xfrm-ESP Page-Cache Write vulnerability is in scope from cac2661c53f3 (2017-01-17) up to upstream, and the RxRPC Page-Cache Write vulnerability is in scope from 2dc334f1a63a (2023-06) up to upstream.