medium
5.4
CWE
NVD-CWE-Other
Advisory Published
CVE Published
Updated

CVE-2011-1767

First published: Thu May 05 2011(Updated: )

Description: 1) <a href="https://access.redhat.com/security/cve/CVE-2011-1767">CVE-2011-1767</a> gre: fix netns vs proto registration ordering GRE protocol receive hook can be called right after protocol addition is done. If netns stuff is not yet initialized, we're going to oops in net_generic(). This is remotely oopsable if ip_gre is compiled as module and packet comes at unfortunate moment of module loading. Upstream commit: <a href="http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=c2892f02">http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=c2892f02</a> References: <a href="http://www.openwall.com/lists/oss-security/2010/02/18/3">http://www.openwall.com/lists/oss-security/2010/02/18/3</a> <a href="http://patchwork.ozlabs.org/patch/45553/">http://patchwork.ozlabs.org/patch/45553/</a> 2) <a href="https://access.redhat.com/security/cve/CVE-2011-1768">CVE-2011-1768</a> tunnels: fix netns vs proto registration ordering Same stuff as in ip_gre patch: receive hook can be called before netns setup is done, oopsing in net_generic(). Upstream commit: <a href="http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=d5aa407f">http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=d5aa407f</a> References: <a href="http://www.openwall.com/lists/oss-security/2010/02/18/3">http://www.openwall.com/lists/oss-security/2010/02/18/3</a> <a href="http://patchwork.ozlabs.org/patch/45554/">http://patchwork.ozlabs.org/patch/45554/</a>

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
debian/linux-2.6
Linux kernel=2.6.33.7
Linux kernel=2.6.33.9
Linux kernel=2.6.33.18
Linux kernel=2.6.33.14
Linux kernel=2.6.33.19
Linux kernel=2.6.33.2
Linux kernel=2.6.33.6
Linux kernel=2.6.33.17
Linux kernel=2.6.33.1
Linux kernel=2.6.33.4
Linux kernel=2.6.33
Linux kernel=2.6.33.12
Linux kernel=2.6.33.3
Linux kernel=2.6.33.13
Linux kernel=2.6.33.11
Linux kernel=2.6.33.15
Linux kernel=2.6.33.16
Linux kernel<=2.6.33.20
Linux kernel=2.6.33.8
Linux kernel=2.6.33.5
Linux kernel=2.6.33.10
Linux Kernel<=2.6.33.20
Linux Kernel=2.6.33
Linux Kernel=2.6.33.1
Linux Kernel=2.6.33.2
Linux Kernel=2.6.33.3
Linux Kernel=2.6.33.4
Linux Kernel=2.6.33.5
Linux Kernel=2.6.33.6
Linux Kernel=2.6.33.7
Linux Kernel=2.6.33.8
Linux Kernel=2.6.33.9
Linux Kernel=2.6.33.10
Linux Kernel=2.6.33.11
Linux Kernel=2.6.33.12
Linux Kernel=2.6.33.13
Linux Kernel=2.6.33.14
Linux Kernel=2.6.33.15
Linux Kernel=2.6.33.16
Linux Kernel=2.6.33.17
Linux Kernel=2.6.33.18
Linux Kernel=2.6.33.19
<=2.6.33.20
=2.6.33
=2.6.33.1
=2.6.33.2
=2.6.33.3
=2.6.33.4
=2.6.33.5
=2.6.33.6
=2.6.33.7
=2.6.33.8
=2.6.33.9
=2.6.33.10
=2.6.33.11
=2.6.33.12
=2.6.33.13
=2.6.33.14
=2.6.33.15
=2.6.33.16
=2.6.33.17
=2.6.33.18
=2.6.33.19

Remedy

https://github.com/torvalds/linux/commit/c2892f02712e9516d72841d5c019ed6916329794

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-2011-1767?

    CVE-2011-1767 is rated as important due to potential system instability and kernel crashes.

  • How do I fix CVE-2011-1767?

    To mitigate CVE-2011-1767, update the Linux kernel to version 2.6.33.20 or later.

  • What systems are affected by CVE-2011-1767?

    CVE-2011-1767 affects multiple versions of the Linux kernel, specifically those earlier than 2.6.33.20.

  • What kind of vulnerability is CVE-2011-1767?

    CVE-2011-1767 is a vulnerability that stems from improper initialization during network protocol registration.

  • Can CVE-2011-1767 cause denial of service?

    Yes, CVE-2011-1767 can lead to denial of service if the kernel encounters instability or crashes.

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