Why so many, you may ask. Well, because of several reasons, one of them being the recent policy change in CVE assignment for the kernel project, where essentially any commit identified as fixing a potential security issue gets a CVE assigned, even if it’s a minor one or has no known exploit path.
It’s because over the last decade the understanding and tools to take advantage of a bunch of small seemingly insignificant exploits in order to gain privileged access have become widespread.
It’s the flip side of not trusting things written in rust to be effectively more secure just because it prevents someone from sticking their thumb between their fore and middle fingers and declaring they “got your stack”.
i’m pretty sure the kernel itself does that to themselves too. basically there’s so much code in the kernel that if any bug, even if small, could possibly under a specific configuration result in some device out there having its security weakened, they prefer to be on the safe side and assign a cve.
wtf?!!! why?!
i mean it makes sense to me, a vulnerability is a vulnerability regardless of whether it has been exploited or not
It’s because over the last decade the understanding and tools to take advantage of a bunch of small seemingly insignificant exploits in order to gain privileged access have become widespread.
It’s the flip side of not trusting things written in rust to be effectively more secure just because it prevents someone from sticking their thumb between their fore and middle fingers and declaring they “got your stack”.
i’m pretty sure the kernel itself does that to themselves too. basically there’s so much code in the kernel that if any bug, even if small, could possibly under a specific configuration result in some device out there having its security weakened, they prefer to be on the safe side and assign a cve.
Not just that, but any kernel crash could turn off a potentially security related machine
Well more book work, filling the cve database and bureaucracy. That is why. 😳😩