# CVE-2026-74491: of/address: Fix NULL bus dereference in of_pci_range_parser_one()

> A NULL pointer dereference in the Linux kernel's PCI range parser can cause a system crash, requiring a kernel patch to fix.

- **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:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-74491, DEBIAN-CVE-2026-74491, GHSA-wjhg-hxg5-8vjp, UBUNTU-CVE-2026-74491

## What is CVE-2026-74491?

CVE-2026-74491 is a vulnerability in Linux, published on 15 Aug 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:

of/address: Fix NULL bus dereference in of_pci_range_parser_one()

The bus matching rework made of_match_bus() return NULL for nodes with
ranges/dma-ranges but no local #address-cells. parser_init() stored that
NULL bus, and the range iterator later dereferenced it.

Reject such nodes in parser_init(), leaving an explicit empty
iterator for callers that ignore the init return, and make
of_dma_get_max_cpu_address() honour the init failure so a rejected node
cannot clamp the DMA limit.

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


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

Apply the vendor's patch.

## Is CVE-2026-74491 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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