CVE-2026-43132

dm-verity: correctly handle dm_bufio_client_create() failure

MEDIUM

5.5

CVSS Score

Published: May 6, 2026 at 11:27 AM UTC

Updated: June 17, 2026 at 10:48 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

MEDIUM5.5

Exploit prediction

EPSS 0.1%

Description

In the Linux kernel, the following vulnerability has been resolved: dm-verity: correctly handle dm_bufio_client_create() failure If either of the calls to dm_bufio_client_create() in verity_fec_ctr() fails, then dm_bufio_client_destroy() is later called with an ERR_PTR() argument. That causes a crash. Fix this.

Affected

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

Linux Kernel · Linux

95%

4.5 ≤ v < 5.10.2524.5 ≤ v < 5.15.2024.5 ≤ v < 6.1.1654.5 ≤ v < 6.12.754.5 ≤ v < 6.18.164.5 ≤ v < 6.19.64.5 ≤ v < 6.6.1284.5 ≤ v < 7.05.11 ≤ v < 5.15.2025.16 ≤ v < 6.1.1656.13 ≤ v < 6.18.166.19 ≤ v < 6.19.66.2 ≤ v < 6.6.1286.7 ≤ v < 6.12.754.5a739ff3f543afbb4a041c16cd0182c8e8d366e70

Vendor states this is fixed in 031f2adc1499b112a39ac316bbab3c80bba16cf2 (fixed)

Vendor states this is fixed in 119f4f04186fa4f33ee6bd39af145cdaff1ff17f (fixed)

Vendor states this is fixed in 451cc650e40e8c3222d37877a9e4be0fcaacb9c8 (fixed)

Vendor states this is fixed in 5c2217ddb3b7e7ac25f4ebe9061258fc8f1c9167 (fixed)

Vendor states this is fixed in 6283e49af87a9c121bb01e5a64a7fe5706c210bc (fixed)

Vendor states this is fixed in 9b8dc1d327e2928f3da59ced0595d850d31c0936 (fixed)

Vendor states this is fixed in b154a868a3856fb5216c4f82981d8a503832e095 (fixed)

Vendor states this is fixed in d3e1f1adc8a0289efe2d2cdc90edb8c6ffe0b5ef (fixed)

Vendor states this is fixed in 4.5 (unaffected)

Vendor states this is fixed in 5.10.252 (unaffected)

Vendor states this is fixed in 5.15.202 (unaffected)

Vendor states this is fixed in 6.1.165 (unaffected)