# CVE-2018-14853: Null dereference in n/a

> An attacker with code execution on the Wi-Fi chip can trigger a null pointer dereference in the bcmdhd4358 driver, causing the Samsung Galaxy S6 to reboot.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **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:** 17 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pjxr-6c7r-hpjf

## What is CVE-2018-14853?

CVE-2018-14853 is a medium-severity vulnerability in n/a, published on 17 Dec 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A NULL pointer dereference in dhd_prot_txdata_write_flush in drivers/net/wireless/bcmdhd4358/dhd_msgbuf.c in the bcmdhd4358 Wi-Fi driver on the Samsung Galaxy S6 SM-G920F G920FXXU5EQH7 allows an attacker (who has obtained code execution on the Wi-Fi chip) to cause the device to reboot. The Samsung ID is SVE-2018-11783.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2018-14853?

It affects 1 product.


Products: Samsung Galaxy S6 Firmware.

## How do I fix CVE-2018-14853?

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

## Is CVE-2018-14853 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-2566](https://insights.sbomify.com/CVE-2016-2566/): SQL injection in n/a (critical 9.8)
- [CVE-2018-14745](https://insights.sbomify.com/CVE-2018-14745/): Memory corruption in n/a (high 8.8)
- [CVE-2018-14852](https://insights.sbomify.com/CVE-2018-14852/): Memory corruption in n/a (medium 6.3)
- [CVE-2018-14854](https://insights.sbomify.com/CVE-2018-14854/): Memory corruption in n/a (medium 6.3)
- [CVE-2018-14855](https://insights.sbomify.com/CVE-2018-14855/): Memory corruption in n/a (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-14853 and fix it if it is affected.

What it is: CVE-2018-14853 is a medium-severity vulnerability in n/a, published on 17 Dec 2018. 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-2018-14853 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-2018-14853/ (Markdown: https://insights.sbomify.com/CVE-2018-14853/index.md)
```

## Sources

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

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