# CVE-2026-40225: Privilege escalation in systemd

> Local attackers can achieve root execution via malicious hardware devices and unsanitized kernel output in systemd udev.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Apr 2026
- **Updated:** 14 Apr 2026
- **Also known as:** AZL-84590, DEBIAN-CVE-2026-40225, ECHO-5372-36f1-2a63, GHSA-396h-m3pm-fpm5, GHSA-vpfq-8p5f-jcqx, OESA-2026-2548, UBUNTU-CVE-2026-40225, USN-8119-2

## What is CVE-2026-40225?

CVE-2026-40225 is a medium-severity vulnerability in Systemd Project Systemd, published on 10 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In udev in systemd before 260, local root execution can occur via malicious hardware devices and unsanitized kernel output.

Weakness: CWE-669 (Incorrect Resource Transfer Between Spheres)

## Which versions are affected by CVE-2026-40225?

It affects 1 product.


Products: Systemd Project Systemd.

## How do I fix CVE-2026-40225?

Upgrade to a fixed version.

## Is CVE-2026-40225 being exploited?

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

## Other vulnerabilities in Systemd Project Systemd

- [CVE-2015-7510](https://insights.sbomify.com/CVE-2015-7510/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-1000082](https://insights.sbomify.com/CVE-2017-1000082/): Privilege escalation in n/a (critical 9.8)
- [CVE-2016-10156](https://insights.sbomify.com/CVE-2016-10156/): Privilege escalation in n/a (high 7.8)
- [CVE-2017-9445](https://insights.sbomify.com/CVE-2017-9445/): Memory corruption in n/a (high 7.5)
- [CVE-2017-9217](https://insights.sbomify.com/CVE-2017-9217/): Null dereference in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-40225 and fix it if it is affected.

What it is: CVE-2026-40225 is a medium-severity vulnerability in Systemd Project Systemd, published on 10 Apr 2026. 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-2026-40225 in the wild and no public exploit code.

Affected product: Systemd Project Systemd. 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-2026-40225/ (Markdown: https://insights.sbomify.com/CVE-2026-40225/index.md)
```

## Sources

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

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