# CVE-2009-2849: Null dereference in n/a > Local attackers can cause a denial of service via NULL pointer dereference in the Linux kernel md driver if sysfs is writable. - **Severity:** Medium 4.7 (`AV:L/AC:M/Au:N/C:N/I:N/A:C`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 18 Aug 2009 - **Updated:** 7 Aug 2024 - **Also known as:** GHSA-xc37-2m2p-wghm, RHSA-2009:1455 ## What is CVE-2009-2849? CVE-2009-2849 is a medium-severity vulnerability in Linux kernel, published on 18 Aug 2009. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description The md driver (drivers/md/md.c) in the Linux kernel before 2.6.30.2 might allow local users to cause a denial of service (NULL pointer dereference) via vectors related to "suspend_* sysfs attributes" and the (1) suspend_lo_store or (2) suspend_hi_store functions. NOTE: this is only a vulnerability when sysfs is writable by an attacker. ## Which versions are affected by CVE-2009-2849? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `kernel` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-PAE` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-PAE-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-PAE-devel` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-debug` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-debug-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-debug-devel` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-debuginfo-common` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-devel` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-doc` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-headers` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-xen` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-xen-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-xen-devel` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-164.2.1.el5 | | `kernel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-PAE` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-PAE-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-PAE-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-debug` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-debug-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-debug-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-debuginfo-common` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-doc` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-headers` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-kdump` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-kdump-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-kdump-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-xen` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-xen-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-164.2.1.el5 | | `kernel-xen-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-164.2.1.el5 | Products: Linux kernel. ## How do I fix CVE-2009-2849? Upgrade to a fixed version. ## Is CVE-2009-2849 being exploited? There is no known exploitation of CVE-2009-2849 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-2009-2849 and fix it if it is affected. What it is: CVE-2009-2849 is a medium-severity vulnerability in Linux kernel, published on 18 Aug 2009. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2009-2849 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-2009-2849/ (Markdown: https://insights.sbomify.com/CVE-2009-2849/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2009-2849 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2009-2849 - OSV: https://osv.dev/vulnerability/CVE-2009-2849 --- From sbomify Insights: https://insights.sbomify.com/CVE-2009-2849/ Summaries are generated and may contain mistakes; the official description above is the record.