First published: Thu Sep 04 2008(Updated: )
Description of problem: To avoid exposing ourselves to the risk of finding another field like .map_bh.b_state 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: <a href="http://lkml.org/lkml/2007/7/26/88">http://lkml.org/lkml/2007/7/26/88</a>
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | <2.6.23 | |
Ubuntu | =6.06 | |
Ubuntu | =7.10 | |
Ubuntu | =8.04 | |
Debian | =4.0 | |
Novell Linux Desktop | =9 | |
SUSE Linux | =10.3 | |
SUSE Linux Enterprise Desktop | =10-sp2 | |
SUSE Linux Enterprise Server | =10-sp1 | |
SUSE Linux Enterprise Server | =10-sp2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2007-6716 is classified as a high severity vulnerability due to its potential to lead to memory corruption.
To fix CVE-2007-6716, you should upgrade to a patched version of the Linux kernel or the affected distribution.
CVE-2007-6716 affects various versions of Linux kernel, Ubuntu, Debian, Novell, and openSUSE systems.
CVE-2007-6716 is a memory corruption vulnerability that occurs due to improper handling of structure initialization.
CVE-2007-6716 can potentially be exploited locally but has implications that could allow for remote exploitation.