# CVE-2023-52627: iio: adc: ad7091r: Allow users to configure device events

> A missing callback implementation in the AD7091R ADC driver causes a kernel null pointer dereference, leading to a system crash.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** 26 Mar 2024
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2023-52627, DEBIAN-CVE-2023-52627, GHSA-4v2g-fxcq-4j44, UBUNTU-CVE-2023-52627

## What is CVE-2023-52627?

CVE-2023-52627 is a medium-severity vulnerability in Debian Debian Linux, published on 26 Mar 2024. 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:

iio: adc: ad7091r: Allow users to configure device events

AD7091R-5 devices are supported by the ad7091r-5 driver together with
the ad7091r-base driver. Those drivers declared iio events for notifying
user space when ADC readings fall bellow the thresholds of low limit
registers or above the values set in high limit registers.
However, to configure iio events and their thresholds, a set of callback
functions must be implemented and those were not present until now.
The consequence of trying to configure ad7091r-5 events without the
proper callback functions was a null pointer dereference in the kernel
because the pointers to the callback functions were not set.

Implement event configuration callbacks allowing users to read/write
event thresholds and enable/disable event generation.

Since the event spec structs are generic to AD7091R devices, also move
those from the ad7091r-5 driver the base driver so they can be reused
when support for ad7091r-2/-4/-8 be added.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2023-52627?

It affects 2 products.


Products: Debian Debian Linux, Linux kernel.

## How do I fix CVE-2023-52627?

Apply the vendor's patch.

## Is CVE-2023-52627 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-52627 and fix it if it is affected.

What it is: CVE-2023-52627 is a medium-severity vulnerability in Debian Debian Linux, published on 26 Mar 2024. 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-2023-52627 in the wild and no public exploit code.

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

## Sources

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

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