cve.bz

CVE-2026-74734 linux linux

no score yetEPSS 0.2%Fix available

linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 6.6.160
  • Linux Linux: fixed in 6.12.114
  • Linux Linux: fixed in 6.18.46
  • Linux Linux: fixed in 7.1.10
  • Linux Linux: fixed in 7.2
  • Debian, Ubuntu, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-74734 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-74734?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-74734?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-74734 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.5 and later

Fixed in

ProductRelease lineFixed in
Linux6.66.6.160
Linux6.126.12.114
Linux6.186.18.46
Linux7.17.1.10
Linuxlater releases7.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux-6.126.12.115-2~deb12u1DEBIAN-CVE-2026-74734
Debian13linux6.12.115-2DEBIAN-CVE-2026-74734
Debian14linux7.1.10-1DEBIAN-CVE-2026-74734
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-74734
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-74734
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-74734
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 40 moreno fix listedUBUNTU-CVE-2026-74734
Ubuntu24.04:LTSlinux, linux-aws, linux-gcp and 44 moreno fix listedUBUNTU-CVE-2026-74734
Ubuntu24.04:LTSlinux-aws-7.07.0.0-1017.18~24.04.1UBUNTU-CVE-2026-74734 USN-9020-1
Ubuntu24.04:LTSlinux-azure-fde-7.07.0.0-1019.19~24.04.1UBUNTU-CVE-2026-74734 USN-9020-1
Ubuntu24.04:LTSlinux-gcp-7.07.0.0-1017.19~24.04.1UBUNTU-CVE-2026-74734 USN-9020-1
Ubuntu24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-74734 USN-8959-1
Ubuntu24.04:LTSlinux-oracle-7.07.0.0-1016.18~24.04.1UBUNTU-CVE-2026-74734 USN-9020-1
Ubuntu24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-74734
Ubuntu26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-74734 USN-8959-1
15 more for Ubuntu in the JSON and on Ubuntu's page.
Azure Linux3kernel6.6.161.1-1AZL-97832
Alpaquita25linux-lts6.12.115-r0BELL-CVE-2026-74734
Alpaquitastreamlinux-lts6.18.46-r0BELL-CVE-2026-74734

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Low.

Red Hat's statement

Red Hat Product Security has rated this issue as having Low security impact. A NULL pointer dereference flaw was found in the Linux kernel's FireWire (IEEE 1394) Open Host Controller Interface (OHCI) driver. If the driver's PCI probe function fails early (for example, when pcim_enable_device() or MMIO mapping fails), the device resource (devres) cleanup path invokes release_ohci(), which unconditionally calls ar_context_release(). When the asynchronous receive context was never initialized, ctx->ohci remains NULL, and ar_context_release() dereferences it before checking whether the context was initialized. A local attacker able to trigger the driver's probe error path under specific hardware conditions could use this flaw to crash the kernel, resulting in a denial of service. The flaw affects only system availability; there is no impact on confidentiality or integrity.

Red Hat Enterprise Linux and Red Hat In-Vehicle OS kernels shipped in currently supported streams are not affected by this flaw because the vulnerable code is not present in those kernels. Red Hat Enterprise Linux 6 Extended Lifecycle Support is out of support scope, so this flaw will not be addressed for that stream.

Red Hat's Low impact rating reflects that, although the CVSS:3.1 base score of 5.5 (Moderate) captures the high availability impact, exploitation requires local privileged access to trigger PCI device probing, depends on specific hardware conditions, and the sole consequence is a system crash (denial of service).

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelNot affected
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-74734.

References

Check your stackJSON