Review reviewHigh

CVE-2026-53062

Linux Linux, linux kernel

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 at...

CVSS
7.8
EPSS
0.10%
0.88% percentile
CISA KEV
Not listed
Published
2026.06.25
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.10%
Technical severityCVSS 7.8

Vulnerability overview

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 at...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= b29d4986d0da1a27cd35917cdb433672f5c95d7f < 4991b5a08751e2e82488fb93ae08849b6aea10d9, >= b29d4986d0da1a27cd35917cdb433672f5c95d7f < 1b2bec4a7dcf5f00b7a1cbeeec8997841d783513, >= b29d4986d0da1a27cd35917cdb433672f5c95d7f < 9a5fdfb9e57ec3a8ad2b8fce5e5ffa42d53b130e, >= b29d4986d0da1a27cd35917cdb433672f5c95d7f < ac5ee99443891bdb161f5539606a66a1b5e72542, >= b29d4986d0da1a27cd35917cdb433672f5c95d7f < 93627a29d4b66d4a2def938dfb8610cc80ae454b, >= b29d4986d0da1a27cd35917cdb433672f5c95d7f < c348ae47d8e65f06429fa41adce9ad986b696766, >= b29d4986d0da1a27cd35917cdb433672f5c95d7f < 2b62d0611c9af14a16bddf22df2612b4f40eb5a1, >= b29d4986d0da1a27cd35917cdb433672f5c95d7f < 2d1f7b65f5deedd2e6b09fdc6ea27f8375f24b45, >= 4.12, >= 4.12 < 5.10.258, >= 5.11 < 5.15.209, >= 5.16 < 6.1.175, >= 6.2 < 6.6.141, >= 6.7 < 6.12.91, >= 6.13 < 6.18.33, >= 6.19 < 7.0.10
Fixed versions
5.10.258, 5.15.209, 6.1.175, 6.6.141, 6.12.91, 6.18.33, 7.0.10

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-667
CVE-2026-53062 — Linux Linux, linux kernel | SECUFOCUS NOW