# CVE-2026-93051: misc: ad525x_dpot: use driver core groups for sysfs files

> Refactors sysfs file creation in the ad525x_dpot driver to prevent potential resource management issues during probe and remove operations.

- **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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-101948, BELL-CVE-2026-93051, DEBIAN-CVE-2026-93051, GHSA-5r45-m6rw-4qwh, UBUNTU-CVE-2026-93051

## What is CVE-2026-93051?

CVE-2026-93051 is a vulnerability in Linux, published on 17 Sep 2026. 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:

misc: ad525x_dpot: use driver core groups for sysfs files

ad_dpot_probe() creates per-RDAC sysfs files manually and then
optionally creates the command sysfs group. This leaves probe responsible
for rolling back partial sysfs state and makes remove responsible for
matching every file that probe created.

Move the device attributes into driver core dev_groups for the I2C and
SPI drivers and use an is_visible() callback to expose only the
attributes supported by the probed device. With this shape, the driver
core creates the sysfs files only after probe succeeds and removes them
before the remove callback frees the driver data.

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


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

Apply the vendor's patch.

## Is CVE-2026-93051 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93051 is a vulnerability in Linux, published on 17 Sep 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-93051 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-2026-93051/ (Markdown: https://insights.sbomify.com/CVE-2026-93051/index.md)
```

## Sources

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

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