# CVE-2014-0974: Memory corruption in n/a

> Attackers can write to arbitrary memory locations via the Little Kernel bootloader, potentially leading to code execution or privilege escalation on Qualcomm devices.

- **Severity:** Low 1.9 (`AV:L/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2014
- **Updated:** 6 Aug 2024
- **Also known as:** CVE-2014-9797, GHSA-g2h3-9497-7mxh

## What is CVE-2014-0974?

CVE-2014-0974 is a low-severity memory corruption vulnerability in n/a, published on 25 Aug 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The boot_linux_from_mmc function in app/aboot/aboot.c in the Little Kernel (LK) bootloader, as distributed with Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, does not properly validate a certain address value, which allows attackers to write data to a controllable memory location by leveraging the ability to initiate an attempted boot of an arbitrary image.

Weakness: CWE-264

## Which versions are affected by CVE-2014-0974?

It affects 1 product.


Products: Little Kernel Project Little Kernel Bootloader.

## How do I fix CVE-2014-0974?

No fix has been published for CVE-2014-0974 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-0974 being exploited?

There is no known exploitation of CVE-2014-0974 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2014-0973](https://insights.sbomify.com/CVE-2014-0973/): Auth bypass in n/a (high 7.2)
- [CVE-2014-4325](https://insights.sbomify.com/CVE-2014-4325/): Security feature bypass in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-0974 and fix it if it is affected.

What it is: CVE-2014-0974 is a low-severity memory corruption vulnerability in n/a, published on 25 Aug 2014. 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-2014-0974 in the wild and no public exploit code.

Affected product: n/a. 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-2014-0974/ (Markdown: https://insights.sbomify.com/CVE-2014-0974/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-0974
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-0974
- OSV: https://osv.dev/vulnerability/CVE-2014-0974

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-0974/
Summaries are generated and may contain mistakes; the official description above is the record.