# CVE-2026-46282: iio: frequency: admv1013: fix NULL pointer dereference on str

> A NULL pointer dereference in the Linux kernel ADMV1013 driver allows local attackers to cause 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:** 8 Jun 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-89616, BELL-CVE-2026-46282, DEBIAN-CVE-2026-46282, GHSA-qrv5-4j39-f7c6, ROOT-OS-DEBIAN-12-CVE-2026-46282, UBUNTU-CVE-2026-46282

## What is CVE-2026-46282?

CVE-2026-46282 is a medium-severity vulnerability in Linux kernel, published on 8 Jun 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:

iio: frequency: admv1013: fix NULL pointer dereference on str

When device_property_read_string() fails, str is left uninitialized
but the code falls through to strcmp(str, ...), dereferencing a garbage
pointer. Replace manual read/strcmp with
device_property_match_property_string() and consolidate the SE mode
enums into a single sequential enum, mapping to hardware register
values via a switch consistent with other bitfields in the driver.

Several cleanup patches have been applied to this driver recently so
this will need a manual backport.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2026-46282 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46282 is a medium-severity vulnerability in Linux kernel, published on 8 Jun 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-46282 in the wild and no public exploit code.

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

## Sources

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

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