CVE & CISA-KEV Catalog

CVE-2026-53062

CRITICAL
9.8
CVSS v3
NVD

Description

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"

How to fix

Remediation Available
linuxDebian
Fixed in:5.10.259-1CVE-2026-53062
Fixed in:6.1.176-1CVE-2026-53062
Fixed in:6.12.94-1CVE-2026-53062
Fixed in:7.0.10-1CVE-2026-53062
linuxUbuntu
Fixed in:5.15.0-186.196USN-8575-1
Fixed in:6.8.0-136.136USN-8567-1
linux-awsUbuntu
Fixed in:5.15.0-1112.119USN-8575-2
Fixed in:6.8.0-1061.64USN-8595-2
linux-aws-5.15Ubuntu
Fixed in:5.15.0-1112.119~20.04.1USN-8575-2
linux-aws-6.8Ubuntu
Fixed in:6.8.0-1061.64~22.04.1USN-8595-3
linux-aws-fipsUbuntu
Fixed in:5.15.0-1112.119+fips1USN-8575-2
Fixed in:6.8.0-1061.64+fips1USN-8595-3
linux-azureUbuntu
Fixed in:5.15.0-1117.126USN-8575-3
Fixed in:6.8.0-1063.71USN-8606-1
linux-azure-5.15Ubuntu
Fixed in:5.15.0-1117.126~20.04.1USN-8620-1
linux-azure-6.8Ubuntu
Fixed in:6.8.0-1063.71~22.04.1USN-8606-1
linux-azure-fdeUbuntu
Fixed in:5.15.0-1117.126USN-8610-1
Fixed in:6.8.0-1062.69USN-8607-1
linux-azure-fde-5.15Ubuntu
Fixed in:5.15.0-1117.126~20.04.2USN-8620-1
linux-azure-fde-6.8Ubuntu
Fixed in:6.8.0-1062.69~22.04.1USN-8609-1
linux-azure-fipsUbuntu
Fixed in:5.15.0-1117.126+fips1USN-8620-2
Fixed in:6.8.0-1063.71+fips2USN-8608-1
linux-fipsUbuntu
Fixed in:5.15.0-186.196+fips1USN-8575-2
Fixed in:6.8.0-136.136+fips2USN-8574-2
linux-gcpUbuntu
Fixed in:5.15.0-1112.122USN-8575-1
Fixed in:6.8.0-1064.72USN-8567-1
linux-gcp-5.15Ubuntu
Fixed in:5.15.0-1112.122~20.04.1USN-8668-1
linux-gcp-6.8Ubuntu
Fixed in:6.8.0-1064.72~22.04.1USN-8567-1
linux-gcp-fipsUbuntu
Fixed in:5.15.0-1112.122+fips1USN-8575-1
Fixed in:6.8.0-1064.72+fips1USN-8574-1
linux-gkeUbuntu
Fixed in:5.15.0-1108.114USN-8575-1
Fixed in:6.8.0-1059.67USN-8567-1
linux-gkeopUbuntu
Fixed in:5.15.0-1095.103USN-8575-1
Fixed in:6.8.0-1046.50USN-8567-1
linux-hwe-5.15Ubuntu
Fixed in:5.15.0-186.196~20.04.1USN-8575-1
linux-hwe-6.8Ubuntu
Fixed in:6.8.0-136.136~22.04.1USN-8619-1
linux-hwe-7.0Ubuntu
Fixed in:7.0.0-28.28~24.04.1USN-8569-1
linux-ibmUbuntu
Fixed in:5.15.0-1106.110USN-8575-2
Fixed in:6.8.0-1061.62USN-8574-3
linux-ibm-6.8Ubuntu
Fixed in:6.8.0-1061.62~22.04.1USN-8574-3
linux-image-5.15.0-1053-nvidia-tegra-igxUbuntu
Fixed in:5.15.0-1053.53USN-8576-2
linux-image-5.15.0-1053-nvidia-tegra-igx-rtUbuntu
Fixed in:5.15.0-1053.53USN-8576-2
linux-image-5.15.0-1064-nvidia-tegraUbuntu
Fixed in:5.15.0-1064.66~20.04.1USN-8576-1
Fixed in:5.15.0-1064.66USN-8576-2
linux-image-5.15.0-1064-nvidia-tegra-rtUbuntu
Fixed in:5.15.0-1064.66~20.04.1USN-8576-1
Fixed in:5.15.0-1064.66USN-8576-2
linux-image-5.15.0-1075-xilinx-zynqmpUbuntu
Fixed in:5.15.0-1075.79USN-8575-1

This vulnerability affects an unusually large number of packages. The highest-confidence fixes are shown above; the full list is longer. Check the referenced advisories for complete coverage.

TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works

Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.

CVSS v3 Vector

Exploitability

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U

Exploit Intelligence

0.10%probability of exploitation in 30 days
1stpercentile

Low risk: more likely to be exploited than 1% of all known CVEs.

References

Related Vulnerabilities

Other CWE-667 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2019-10072High7.573%-Fix
CVE-2002-1850High7.517%-Fix
CVE-2009-2699High7.514%-Fix
CVE-2004-0174High7.512%--
CVE-2009-4272High7.511%--
CVE-2020-24606High8.65.2%-Fix

Common questions

How do I fix CVE-2026-53062?

Published advisories record a fix for 260 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.

Is CVE-2026-53062 being actively exploited?

Not that we know of. CVE-2026-53062 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.10% is the estimated probability that it will be exploited in the next 30 days. That is higher than 1% of all scored CVEs.

How severe is CVE-2026-53062?

CVE-2026-53062 has a CVSS v3 base score of 9.8, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

What does CVE-2026-53062 affect?

Published advisories record a fix for linux (Debian), linux (Ubuntu), linux-aws (Ubuntu), linux-aws-5.15 (Ubuntu), and 256 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.

Embed a live status badge for CVE-2026-53062
CVE-2026-53062 severity badge

Markdown

[![CVE-2026-53062](https://tridentstack.com/cve/badge/CVE-2026-53062.svg)](https://tridentstack.com/cve/CVE-2026-53062)

HTML

<a href="https://tridentstack.com/cve/CVE-2026-53062"><img src="https://tridentstack.com/cve/badge/CVE-2026-53062.svg" alt="CVE-2026-53062"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

See how it worksStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-07-21.