# CVE-2025-40262: Input: imx_sc_key - fix memory corruption on unload

> A memory corruption vulnerability in the Linux kernel's imx_sc_key driver allows attackers to cause crashes or potentially execute code via improper pointer handling during module unload.

- **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:** 4 Dec 2025
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2025-40262, DEBIAN-CVE-2025-40262, GHSA-2m33-w232-qf59, ROOT-OS-DEBIAN-12-CVE-2025-40262, ROOT-OS-DEBIAN-13-CVE-2025-40262, ROOT-OS-UBUNTU-2204-CVE-2025-40262, ROOT-OS-UBUNTU-2404-CVE-2025-40262, UBUNTU-CVE-2025-40262

## What is CVE-2025-40262?

CVE-2025-40262 is a high-severity memory corruption vulnerability in Linux, published on 4 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

Input: imx_sc_key - fix memory corruption on unload

This is supposed to be "priv" but we accidentally pass "&priv" which is
an address in the stack and so it will lead to memory corruption when
the imx_sc_key_action() function is called.  Remove the &.

## Which versions are affected by CVE-2025-40262?


## How do I fix CVE-2025-40262?

Apply the vendor's patch.

## Is CVE-2025-40262 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-40262 and fix it if it is affected.

What it is: CVE-2025-40262 is a high-severity memory corruption vulnerability in Linux, published on 4 Dec 2025. 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-2025-40262 in the wild and no public exploit code.

Affected product: Linux. 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-2025-40262/ (Markdown: https://insights.sbomify.com/CVE-2025-40262/index.md)
```

## Sources

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

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