# CVE-2022-25265: Security feature bypass in n/a

> The Linux kernel may incorrectly mark old binary files as executable, allowing attackers to execute code in non-executable memory regions.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 16 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** AZL-8641, DEBIAN-CVE-2022-25265, GHSA-jgc5-xgwj-77vf, ROOT-OS-DEBIAN-11-CVE-2022-25265, ROOT-OS-DEBIAN-12-CVE-2022-25265, ROOT-OS-DEBIAN-13-CVE-2022-25265, UBUNTU-CVE-2022-25265

## What is CVE-2022-25265?

CVE-2022-25265 is a high-severity vulnerability in Linux kernel, published on 16 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel through 5.16.10, certain binary files may have the exec-all attribute if they were built in approximately 2003 (e.g., with GCC 3.2.2 and Linux kernel 2.4.20). This can cause execution of bytes located in supposedly non-executable regions of a file.

Weakness: CWE-913 (Improper Control of Dynamically-Managed Code Resources)

## Which versions are affected by CVE-2022-25265?

It affects 9 products.


Products: Linux kernel, Netapp Baseboard Management Controller Firmware, Netapp H300e Firmware, Netapp H300s Firmware, Netapp H410s Firmware, Netapp H500e Firmware, Netapp H500s Firmware, Netapp H700e Firmware, Netapp H700s Firmware.

## How do I fix CVE-2022-25265?

Apply the vendor's patch.

## Is CVE-2022-25265 being exploited?

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

Public exploit code:

- Bypassing Linux Executable Space Protection using 20+ years old tools (CVE-2022-25265). (github_poc): https://github.com/x0reaxeax/exec-prot-bypass

## 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-2022-25265 and fix it if it is affected.

What it is: CVE-2022-25265 is a high-severity vulnerability in Linux kernel, published on 16 Feb 2022. 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-2022-25265 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-2022-25265/ (Markdown: https://insights.sbomify.com/CVE-2022-25265/index.md)
```

## Sources

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

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