CVE-2007-6716: Medium severity Linux Linux kernel vulnerability
Description of problem: To avoid exposing ourselves to the risk of finding another field like .mapbh.bstate where we rely on zeroing but don't enforce it in the code. The fix uses kzalloc to zero all the struct dio rather than manually trying to track which fields we rely on being zero.
Reference: http://lkml.org/lkml/2007/7/26/88
Other sources
fs/direct-io.c in the dio subsystem in the Linux kernel before 2.6.23 does not properly zero out the dio struct, which allows local users to cause a denial of service (OOPS), as demonstrated by a certain fio test.
— MITRE
Affected Software
Remediation
Patch Available
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2007-6716?
CVE-2007-6716 is classified as a high severity vulnerability due to its potential to lead to memory corruption.
How do I fix CVE-2007-6716?
To fix CVE-2007-6716, you should upgrade to a patched version of the Linux kernel or the affected distribution.
Which systems are affected by CVE-2007-6716?
CVE-2007-6716 affects various versions of Linux kernel, Ubuntu, Debian, Novell, and openSUSE systems.
What kind of vulnerability is CVE-2007-6716?
CVE-2007-6716 is a memory corruption vulnerability that occurs due to improper handling of structure initialization.
Is CVE-2007-6716 exploitable remotely?
CVE-2007-6716 can potentially be exploited locally but has implications that could allow for remote exploitation.