Bug 2492278 (CVE-2026-53062) - CVE-2026-53062 kernel: dm cache policy smq: fix missing locks in invalidating cache blocks
Summary: CVE-2026-53062 kernel: dm cache policy smq: fix missing locks in invalidating...
Keywords:
Status: NEW
Alias: CVE-2026-53062
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-24 18:02 UTC by OSIDB Bzimport
Modified: 2026-11-05 14:13 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:70402 0 None None None 2026-09-22 20:21:07 UTC
Red Hat Product Errata RHSA-2026:70403 0 None None None 2026-09-22 19:30:16 UTC
Red Hat Product Errata RHSA-2026:70459 0 None None None 2026-09-23 20:29:22 UTC
Red Hat Product Errata RHSA-2026:70498 0 None None None 2026-09-23 03:56:11 UTC
Red Hat Product Errata RHSA-2026:77216 0 None None None 2026-10-07 02:49:16 UTC
Red Hat Product Errata RHSA-2026:84793 0 None None None 2026-10-19 10:52:25 UTC
Red Hat Product Errata RHSA-2026:94477 0 None None None 2026-11-03 09:21:50 UTC
Red Hat Product Errata RHSA-2026:94558 0 None None None 2026-11-03 14:04:01 UTC
Red Hat Product Errata RHSA-2026:95556 0 None None None 2026-11-05 14:13:14 UTC

Description OSIDB Bzimport 2026-06-24 18:02:40 UTC
In the Linux kernel, the following vulnerability has been resolved:

dm cache policy smq: fix missing locks in invalidating cache blocks

In passthrough mode, the policy invalidate_mapping operation is called
simultaneously from multiple workers, thus it should be protected by a
lock. Otherwise, we might end up with data races on the allocated blocks
counter, or even use-after-free issues with internal data structures
when doing concurrent writes.

Note that the existing FIXME in smq_invalidate_mapping() doesn't affect
passthrough mode since migration tasks don't exist there, but would need
attention if supporting fast device shrinking via suspend/resume without
target reloading.

Reproduce steps:

1. Create a cache device consisting of 1024 cache entries

dmsetup create cmeta --table "0 8192 linear /dev/sdc 0"
dmsetup create cdata --table "0 131072 linear /dev/sdc 8192"
dmsetup create corig --table "0 262144 linear /dev/sdc 262144"
dd if=/dev/zero of=/dev/mapper/cmeta bs=4k count=1 oflag=direct
dmsetup create cache --table "0 262144 cache /dev/mapper/cmeta \
/dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0"

2. Populate the cache, and record the number of cached blocks

fio --name=populate --filename=/dev/mapper/cache --rw=randwrite --bs=4k \
--size=64m --direct=1
nr_cached=$(dmsetup status cache | awk '{split($7, a, "/"); print a[1]}')

3. Reload the cache into passthrough mode

dmsetup suspend cache
dmsetup reload cache --table "0 262144 cache /dev/mapper/cmeta \
/dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 passthrough smq 0"
dmsetup resume cache

4. Write to the passthrough cache. By setting multiple jobs with I/O
   size equal to the cache block size, cache blocks are invalidated
   concurrently from different workers.

fio --filename=/dev/mapper/cache --name=test --rw=randwrite --bs=64k \
--direct=1 --numjobs=2 --randrepeat=0 --size=64m

5. Check if demoted matches cached block count. These numbers should
   match but may differ due to the data race.

nr_demoted=$(dmsetup status cache | awk '{print $12}')
echo "$nr_cached, $nr_demoted"

Comment 1 Mauro Matteo Cascella 2026-06-25 14:39:36 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026062402-CVE-2026-53062-a727@gregkh/T

Comment 6 Jon Orris 2026-09-22 19:30:16 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:70403 https://access.redhat.com/errata/RHSA-2026:70403

Comment 7 Jon Orris 2026-09-22 20:21:06 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:70402 https://access.redhat.com/errata/RHSA-2026:70402

Comment 8 Jon Orris 2026-09-23 03:56:10 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:70498 https://access.redhat.com/errata/RHSA-2026:70498

Comment 9 Jon Orris 2026-09-23 20:29:21 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:70459 https://access.redhat.com/errata/RHSA-2026:70459

Comment 10 Jon Orris 2026-10-07 02:49:15 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support
  Red Hat Enterprise Linux 8.6 Extended Update Support Long-Life Add-On

Via RHSA-2026:77216 https://access.redhat.com/errata/RHSA-2026:77216

Comment 11 Jon Orris 2026-10-19 10:52:25 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions
  Red Hat Enterprise Linux 8.8 Telecommunications Update Service

Via RHSA-2026:84793 https://access.redhat.com/errata/RHSA-2026:84793

Comment 14 Jon Orris 2026-11-03 09:21:49 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions

Via RHSA-2026:94477 https://access.redhat.com/errata/RHSA-2026:94477

Comment 15 Jon Orris 2026-11-03 14:04:00 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions

Via RHSA-2026:94558 https://access.redhat.com/errata/RHSA-2026:94558

Comment 16 Jon Orris 2026-11-05 14:13:13 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7 Extended Lifecycle Support

Via RHSA-2026:95556 https://access.redhat.com/errata/RHSA-2026:95556


Note You need to log in before you can comment on or make changes to this bug.