medium
5.4
CWE
200
Advisory Published
CVE Published
Updated

CVE-2010-0003: Infoleak

First published: Tue Jan 12 2010(Updated: )

Description of problem: When print-fatal-signals is enabled it's possible to dump any memory reachable by the kernel to the log by simply jumping to that address from user space. Or crash the system if there's some hardware with read side effects. The fatal signals handler will dump 16 bytes at the execution address, which is fully controlled by ring 3. In addition when something jumps to a unmapped address there will be up to 16 additional useless page faults, which might be potentially slow (and at least is not very efficient) Fortunately this option is off by default and only there on i386. But fix it by checking for kernel addresses and also stopping when there's a page fault. References: <a href="http://patchwork.kernel.org/patch/69752/">http://patchwork.kernel.org/patch/69752/</a> <a href="http://git.kernel.org/linus/b45c6e76bc2c72f6426c14bed64fdcbc9bf37cb0">http://git.kernel.org/linus/b45c6e76bc2c72f6426c14bed64fdcbc9bf37cb0</a>

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
Linux Kernel<2.6.32.4
Debian Linux=5.0
Debian Linux=4.0
<2.6.32.4
=4.0
=5.0

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2010-0003?

    CVE-2010-0003 has a high severity level due to the potential to dump sensitive kernel memory and cause system crashes.

  • How do I fix CVE-2010-0003?

    To fix CVE-2010-0003, users should upgrade the Linux kernel to a version higher than 2.6.32.4 or apply patches provided by their distribution.

  • Which systems are affected by CVE-2010-0003?

    CVE-2010-0003 affects Linux Kernel versions up to 2.6.32.4 and specific versions of Debian GNU/Linux, namely 4.0 and 5.0.

  • What are the risks of CVE-2010-0003?

    The risks of CVE-2010-0003 include unauthorized access to sensitive data and potential system instability or crashes.

  • Is CVE-2010-0003 remotely exploitable?

    CVE-2010-0003 is not considered remotely exploitable as it requires local user access to trigger the vulnerability.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203