# CVE-2026-98673: iio: adc: pac1934: check ACPI label duplication

> A null pointer dereference in the PAC1934 ADC driver can cause a kernel crash when handling duplicate ACPI labels.

- **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:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-98673, DEBIAN-CVE-2026-98673, GHSA-256p-6hqh-vvmc, UBUNTU-CVE-2026-98673

## What is CVE-2026-98673?

CVE-2026-98673 is a vulnerability in Linux, published on 18 Oct 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: adc: pac1934: check ACPI label duplication

A label duplication failure currently reaches the terminating-byte
write. Release the ACPI result and abort before accessing the missing
label; earlier labels are managed by devres.

Detected by static analysis and reviewed with AI-assisted source auditing.

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


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

Apply the vendor's patch.

## Is CVE-2026-98673 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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