# CVE-2019-25160: netlabel: fix out-of-bounds memory accesses

> Out-of-bounds memory accesses in the Linux kernel netlabel subsystem allow attackers to cause denial of service or potentially execute code.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Feb 2024
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-39908, DEBIAN-CVE-2019-25160, GHSA-gj7p-vqfr-xgjw, UBUNTU-CVE-2019-25160

## What is CVE-2019-25160?

CVE-2019-25160 is a critical memory corruption vulnerability in Linux kernel, published on 26 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

netlabel: fix out-of-bounds memory accesses

There are two array out-of-bounds memory accesses, one in
cipso_v4_map_lvl_valid(), the other in netlbl_bitmap_walk().  Both
errors are embarassingly simple, and the fixes are straightforward.

As a FYI for anyone backporting this patch to kernels prior to v4.8,
you'll want to apply the netlbl_bitmap_walk() patch to
cipso_v4_bitmap_walk() as netlbl_bitmap_walk() doesn't exist before
Linux v4.8.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2019-25160?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2019-25160?

Apply the vendor's patch.

## Is CVE-2019-25160 being exploited?

There is no known exploitation of CVE-2019-25160 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-2019-25160 and fix it if it is affected.

What it is: CVE-2019-25160 is a critical memory corruption vulnerability in Linux kernel, published on 26 Feb 2024. 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-2019-25160 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-2019-25160/ (Markdown: https://insights.sbomify.com/CVE-2019-25160/index.md)
```

## Sources

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

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