Kernel level driver: Difference between revisions
m Drakeula moved page Kernel Level Drivers to Kernel level driver: Misspelled title: Not in sentence case |
m →Consumer impact summary: oops, missed this one |
||
| (One intermediate revision by the same user not shown) | |||
| Line 5: | Line 5: | ||
There are even lower level processors and programs, which typically operate beyond the control of an operating system. Examples include the UEFI or BIOS, the Intel management engine (and similar processors from other manufacturers), the microcode, and the controllers on various devices (like the storage controller on a solid state drive). These are typically proprietary, less well documented and less well understood than the kernel. They can pose similar risks to kernel drivers. | There are even lower level processors and programs, which typically operate beyond the control of an operating system. Examples include the UEFI or BIOS, the Intel management engine (and similar processors from other manufacturers), the microcode, and the controllers on various devices (like the storage controller on a solid state drive). These are typically proprietary, less well documented and less well understood than the kernel. They can pose similar risks to kernel drivers. | ||
==Consumer | ==Consumer impact summary== | ||
Code running in the kernel presents numerous privacy and security concerns. Code running in the kernel can read and write the memory of any running process, including apps and websites used for banking, passwords, and other highly sensitive actions. Additionally, it has full control over all hardware, including the capability to permanently damage or disable hardware components. | Code running in the kernel presents numerous privacy and security concerns. Code running in the kernel can read and write the memory of any running process, including apps and websites used for banking, passwords, and other highly sensitive actions. Additionally, it has full control over all hardware, including the capability to permanently damage or disable hardware components. | ||
Many companies now require the use of proprietary drivers in order to use applications that would work fine in user space, like [[ | Many companies now require the use of proprietary drivers in order to use applications that would work fine in user space, like [[kernel level anti-cheats]]. This gives these companies unrestricted access to a consumer's system, allowing for unmoderated data collection and control. | ||
==Examples== | ==Examples== | ||
*{{Wplink|CrowdStrike}} | |||
* | *{{Wplink|Cheating in online games#Anti-cheating methods and limitations|Anti-cheats}}, like Easy Anti Cheat and EA Anti Cheat | ||
* | |||
==Incidents== | ==Incidents== | ||
*{{Wplink|2024 CrowdStrike-related IT outages}} | |||
==See also== | |||
*[[Kernel level anti-cheats]] | |||
==See | *[[Trusted computing]] | ||
*[[Kernel | |||
*[[Trusted | |||
==References== | ==References== | ||
{{ | {{Reflist}} | ||
[[Category:Common terms]] | [[Category:Common terms]] | ||