dm cache policy smq: check allocation under invalidate lock_CVE-2026-53265

{
    "lastseen": "",
    "description": "In the Linux kernel, the following vulnerability has been resolved:\n\ndm cache policy smq: check allocation under invalidate lock\n\ncommit 2d1f7b65f5de (\"dm cache policy smq: fix missing locks in\ninvalidating cache blocks\") added mq->lock around the destructive part of\nsmq_invalidate_mapping(), but left the e->allocated check outside the\ncritical section.\n\nThat leaves a check-then-act race. Two concurrent invalidators can both\nobserve e->allocated as true before either of them takes mq->lock. The\nfirst invalidator that acquires the lock removes the entry from the\nqueues and hash table and then calls free_entry(), which clears\ne->allocated and puts the entry back on the free list. The second\ninvalidator can then acquire mq->lock and continue with the stale result\nof the unlocked check.\n\nThis can corrupt the SMQ queues or hash table by deleting an entry that\nis no longer on those structures. It can also hit the allocation check in\nfree_entry() when the same entry is freed again.\n\nMove the allocation check under mq->lock so the predicate and the\ndestructive operations are serialized by the same lock.",
    "published": "2026-06-25T08:39:52.543Z",
    "modified": "2026-06-28T06:41:08.232Z",
    "type": "cve",
    "title": "dm cache policy smq: check allocation under invalidate lock",
    "source": "Linux",
    "references": "https://git.kernel.org/stable/c/c242c7af2aecf0b538b8623bdb86b8b441da38d9\nhttps://git.kernel.org/stable/c/13da856c86fb8c2ccab95034fd77da1bb2c2a17c\nhttps://git.kernel.org/stable/c/d886945fcb0f8c9dc6b39928d7a96c95c587346c\nhttps://git.kernel.org/stable/c/b4892561552d671bd8c4da5ebb70e9fbb1ec446e\nhttps://git.kernel.org/stable/c/03ffe1112ed88bb3a9bd0b971549bf4d64bfc59a\nhttps://git.kernel.org/stable/c/42ff6774ecd9d7f70d599cb71ff64373a1da4948\nhttps://git.kernel.org/stable/c/c57570fba24016ec25ec046ab44db39143fb7a64\nhttps://git.kernel.org/stable/c/d3f0a606b9f278ece8a0df626ded9c4044071235",
    "id": "CVE-2026-53265",
    "bulletinFamily": "",
    "cwe": null,
    "cvelist": null,
    "sourceData": "Linux Linux 4991b5a08751e2e82488fb93ae08849b6aea10d9\nLinux Linux 1b2bec4a7dcf5f00b7a1cbeeec8997841d783513\nLinux Linux 9a5fdfb9e57ec3a8ad2b8fce5e5ffa42d53b130e\nLinux Linux ac5ee99443891bdb161f5539606a66a1b5e72542\nLinux Linux 93627a29d4b66d4a2def938dfb8610cc80ae454b\nLinux Linux c348ae47d8e65f06429fa41adce9ad986b696766\nLinux Linux 2b62d0611c9af14a16bddf22df2612b4f40eb5a1\nLinux Linux 2d1f7b65f5deedd2e6b09fdc6ea27f8375f24b45\nLinux Linux 5.10.258\nLinux Linux 5.15.209\nLinux Linux 6.1.175\nLinux Linux 6.6.141\nLinux Linux 6.12.91\nLinux Linux 6.18.33\nLinux Linux 7.0.10",
    "sourceHref": "",
    "cvss": {
        "score": 7.8,
        "severity": "HIGH",
        "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
        "version": "3.1"
    },
    "cvss2": [],
    "cvss3": {
        "version": "",
        "vectorString": "",
        "baseScore": 0,
        "baseSeverity": "",
        "attackVector": "",
        "attackComplexity": "",
        "privilegesRequired": "",
        "userInteraction": "",
        "scope": "",
        "confidentialityImpact": "",
        "integrityImpact": "",
        "availabilityImpact": "",
        "cvssV3": {
            "version": "",
            "vectorString": "",
            "baseScore": 0,
            "baseSeverity": "",
            "attackVector": "",
            "attackComplexity": "",
            "privilegesRequired": "",
            "userInteraction": "",
            "scope": "",
            "confidentialityImpact": "",
            "integrityImpact": "",
            "availabilityImpact": ""
        }
    },
    "href": "",
    "category_name": "CVE",
    "post_link": "",
    "product": "Linux",
    "version": "4991b5a08751e2e82488fb93ae08849b6aea10d9",
    "vendor": "Linux",
    "ai_description": "",
    "ai_severity": "",
    "ai_vendor": "",
    "ai_product": "",
    "ai_version": "",
    "ai_score": 0
}