# CVE-2025-40188: pwm: berlin: Fix wrong register in suspend/resume

> A bug in the Berlin PWM driver causes a kernel panic during suspend/resume, leading to a local denial of service.

- **Severity:** Not scored
- **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:** 12 Nov 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-40188, DEBIAN-CVE-2025-40188, GHSA-rmrr-hcc6-xrj4, ROOT-OS-DEBIAN-11-CVE-2025-40188, ROOT-OS-DEBIAN-13-CVE-2025-40188, ROOT-OS-UBUNTU-2404-CVE-2025-40188, UBUNTU-CVE-2025-40188

## What is CVE-2025-40188?

CVE-2025-40188 is a denial of service vulnerability in Linux, published on 12 Nov 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:

pwm: berlin: Fix wrong register in suspend/resume

The 'enable' register should be BERLIN_PWM_EN rather than
BERLIN_PWM_ENABLE, otherwise, the driver accesses wrong address, there
will be cpu exception then kernel panic during suspend/resume.

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


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

Apply the vendor's patch.

## Is CVE-2025-40188 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-40188 is a denial of service vulnerability in Linux, published on 12 Nov 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-40188 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-40188/ (Markdown: https://insights.sbomify.com/CVE-2025-40188/index.md)
```

## Sources

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

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