# CVE-2012-2744: Null dereference in n/a > Remote attackers can crash the Linux kernel via fragmented IPv6 packets if the nf_conntrack_ipv6 module is enabled. - **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 9 Aug 2012 - **Updated:** 6 Aug 2024 - **Also known as:** DEBIAN-CVE-2012-2744, GHSA-rf7q-2943-h3jp, RHSA-2012:1114, RHSA-2012:1148 ## What is CVE-2012-2744? CVE-2012-2744 is a high-severity vulnerability in Linux kernel, published on 9 Aug 2012. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description net/ipv6/netfilter/nf_conntrack_reasm.c in the Linux kernel before 2.6.34, when the nf_conntrack_ipv6 module is enabled, allows remote attackers to cause a denial of service (NULL pointer dereference and system crash) via certain types of fragmented IPv6 packets. ## Which versions are affected by CVE-2012-2744? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `kernel` | Red Hat:rhel_eus:6.0 | All versions | 0:2.6.32-71.40.1.el6 | | `kernel-bootwrapper` | Red Hat:rhel_eus:6.0 | All versions | 0:2.6.32-71.40.1.el6 | | `kernel-debug` | Red Hat:rhel_eus:6.0 | All versions | 0:2.6.32-71.40.1.el6 | | `kernel-debug-debuginfo` | Red Hat:rhel_eus:6.0 | All versions | 0:2.6.32-71.40.1.el6 | | `kernel-debug-devel` | Red Hat:rhel_eus:6.0 | All versions | 0:2.6.32-71.40.1.el6 | | `kernel-debuginfo` | Red Hat:rhel_eus:6.0 | All versions | 0:2.6.32-71.40.1.el6 | | `kernel-debuginfo-common-i686` | Red Hat:rhel_eus:6.0 | All versions | 0:2.6.32-71.40.1.el6 | | `kernel-debuginfo-common-ppc64` | Red Hat:rhel_eus:6.0 | All versions | 0:2.6.32-71.40.1.el6 | | `kernel-debuginfo-common-s390x` | Red Hat:rhel_eus:6.0 | All versions | 0:2.6.32-71.40.1.el6 | | `kernel-debuginfo-common-x86_64` | Red Hat:rhel_eus:6.0 | All versions | 0:2.6.32-71.40.1.el6 | | `kernel-devel` | Red Hat:rhel_eus:6.0 | All versions | 0:2.6.32-71.40.1.el6 | | `kernel-doc` | Red Hat:rhel_eus:6.0 | All versions | 0:2.6.32-71.40.1.el6 | | `kernel-firmware` | Red Hat:rhel_eus:6.0 | All versions | 0:2.6.32-71.40.1.el6 | | `kernel-headers` | Red Hat:rhel_eus:6.0 | All versions | 0:2.6.32-71.40.1.el6 | | `kernel-kdump` | Red Hat:rhel_eus:6.0 | All versions | 0:2.6.32-71.40.1.el6 | | `kernel-kdump-debuginfo` | Red Hat:rhel_eus:6.0 | All versions | 0:2.6.32-71.40.1.el6 | | `kernel-kdump-devel` | Red Hat:rhel_eus:6.0 | All versions | 0:2.6.32-71.40.1.el6 | | `perf` | Red Hat:rhel_eus:6.0 | All versions | 0:2.6.32-71.40.1.el6 | | `kernel` | Red Hat:rhel_eus:6.1 | All versions | 0:2.6.32-131.30.1.el6 | | `kernel-bootwrapper` | Red Hat:rhel_eus:6.1 | All versions | 0:2.6.32-131.30.1.el6 | | `kernel-debug` | Red Hat:rhel_eus:6.1 | All versions | 0:2.6.32-131.30.1.el6 | | `kernel-debug-debuginfo` | Red Hat:rhel_eus:6.1 | All versions | 0:2.6.32-131.30.1.el6 | | `kernel-debug-devel` | Red Hat:rhel_eus:6.1 | All versions | 0:2.6.32-131.30.1.el6 | | `kernel-debuginfo` | Red Hat:rhel_eus:6.1 | All versions | 0:2.6.32-131.30.1.el6 | | `kernel-debuginfo-common-i686` | Red Hat:rhel_eus:6.1 | All versions | 0:2.6.32-131.30.1.el6 | | `kernel-debuginfo-common-ppc64` | Red Hat:rhel_eus:6.1 | All versions | 0:2.6.32-131.30.1.el6 | | `kernel-debuginfo-common-s390x` | Red Hat:rhel_eus:6.1 | All versions | 0:2.6.32-131.30.1.el6 | | `kernel-debuginfo-common-x86_64` | Red Hat:rhel_eus:6.1 | All versions | 0:2.6.32-131.30.1.el6 | | `kernel-devel` | Red Hat:rhel_eus:6.1 | All versions | 0:2.6.32-131.30.1.el6 | | `kernel-doc` | Red Hat:rhel_eus:6.1 | All versions | 0:2.6.32-131.30.1.el6 | | `kernel-firmware` | Red Hat:rhel_eus:6.1 | All versions | 0:2.6.32-131.30.1.el6 | | `kernel-headers` | Red Hat:rhel_eus:6.1 | All versions | 0:2.6.32-131.30.1.el6 | | `kernel-kdump` | Red Hat:rhel_eus:6.1 | All versions | 0:2.6.32-131.30.1.el6 | | `kernel-kdump-debuginfo` | Red Hat:rhel_eus:6.1 | All versions | 0:2.6.32-131.30.1.el6 | | `kernel-kdump-devel` | Red Hat:rhel_eus:6.1 | All versions | 0:2.6.32-131.30.1.el6 | | `perf` | Red Hat:rhel_eus:6.1 | All versions | 0:2.6.32-131.30.1.el6 | | `perf-debuginfo` | Red Hat:rhel_eus:6.1 | All versions | 0:2.6.32-131.30.1.el6 | Products: Linux kernel. ## How do I fix CVE-2012-2744? Apply the vendor's patch. ## Is CVE-2012-2744 being exploited? There is no known exploitation of CVE-2012-2744 in the wild and no public exploit code. ## Other vulnerabilities in Linux kernel - [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild) - [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild) - [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild) - [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild) - [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2012-2744 and fix it if it is affected. What it is: CVE-2012-2744 is a high-severity vulnerability in Linux kernel, published on 9 Aug 2012. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2012-2744 in the wild and no public exploit code. Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2012-2744/ (Markdown: https://insights.sbomify.com/CVE-2012-2744/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2012-2744 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-2744 - OSV: https://osv.dev/vulnerability/CVE-2012-2744 --- From sbomify Insights: https://insights.sbomify.com/CVE-2012-2744/ Summaries are generated and may contain mistakes; the official description above is the record.