CVE-2026-97507

media: dm1105: fix missing error check for dma_alloc_coherent

N/A

Published: September 24, 2026 at 04:04 PM UTC

Updated: October 3, 2026 at 11:18 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

N/A

Exploit prediction

EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: media: dm1105: fix missing error check for dma_alloc_coherent The return value of dm1105_dma_map(), which handles DMA memory allocation, is ignored in dm1105_hw_init(). If dma_alloc_coherent() fails, the driver will proceed using a NULL pointer for DMA transfers, leading to a kernel oops or invalid hardware access. Fix this by checking the return value and propagating -ENOMEM on failure.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

2.6.28 ≤ v < 5.10.2712.6.28 ≤ v < 5.15.2222.6.28 ≤ v < 6.1.1892.6.28 ≤ v < 6.12.1112.6.28 ≤ v < 6.18.532.6.28 ≤ v < 6.6.1582.6.28 ≤ v < 7.22.6.28a611d0ca006fe76d88b8dd5ac44f4468293b6760

Vendor states this is fixed in 07d6a76a17b550e94ca5cc0060ad6e77952390f2 (fixed)

Vendor states this is fixed in 3eaac9e02d8591d3c790db572ef1c8fa5a841fdb (fixed)

Vendor states this is fixed in 3ff12d5ea9cb0d0fd89c24b69940f0b989bf6d2a (fixed)

Vendor states this is fixed in a2017c80dd7f3c409778ca0898d6e75ccab6d2f2 (fixed)

Vendor states this is fixed in b6327023dcc7482156fc13cda6361ee573721b05 (fixed)

Vendor states this is fixed in e96f91da5c83e4c1f1bebe1c58856d02cea4afd9 (fixed)

Vendor states this is fixed in f3f135c4fac6194933b952e98a15dc05aa420956 (fixed)

Vendor states this is fixed in 2.6.28 (unaffected)

Vendor states this is fixed in 5.10.271 (unaffected)

Vendor states this is fixed in 5.15.222 (unaffected)

Vendor states this is fixed in 6.1.189 (unaffected)

Vendor states this is fixed in 6.12.111 (unaffected)