Dirty Frag Vulnerability Made Public Early: Root Privilege On All Distributions

[Condobloke]

This, AI assisted.

how to check for dirty-frag-vulnerability at DuckDuckGo

DuckDuckGo. Privacy, Simplified.

duckduckgo.com

 

[Condobloke]

The response on my pc is as below:

condobloke@brian-desktop:~$ lsmod | grep -E "esp4|esp6|ipcomp4|ipcomp6|rxrpc"
condobloke@brian-desktop:~$

Zero response therefore zero bugs

 

[The Duck]

Here's mine and same result so I guess I'm good to go also.

 

[CaffeineAddict]

Is it already fixed in debian?

There is no fix for any of distros, only partial kernel fixes, with the 2nd half still in the works.

Loading...

Loading...

 

[Trml]

condobloke@brian-desktop:~$ lsmod | grep -E "esp4|esp6|ipcomp4|ipcomp6|rxrpc"
condobloke@brian-desktop:~$

Zero response therefore zero bugs

An issue remains if something can trigger the kernel to load the vulnerable modules. A mitigation for that is to disallow the loading of further modules on the running system:

sudo sysctl -w kernel.modules_disabled=1

Yes, this can lead to failures if you suddenly do something that requires a new kernel module. But in general it is no issue, since the system already boots with modules required for its hardware and you don't plug in a PCIe-device while the system is running.

 

[kc1di]

zero response here also