BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-53265High confidence

dm cache policy smq: check allocation under invalidate lock

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 21 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.12% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 21 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 21 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.13-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.13-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-53265 · CSAF 2.0 · revision 15 · interimSUSE Product Security TeamCVE-2026-53265
17 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SUSE Linux Micro Extras 6.2:kernel-obs-build
  • SUSE Linux Micro Extras 6.2:kernel-syms
  • SLES 15 SP1 CHOST Images for Amazon EC2
  • SLES 15 SP2 CHOST Images for Amazon EC2
  • SLES 15 SP3 CHOST Images for Amazon EC2
  • SLES 15 SP4 CHOST Images for Amazon EC2
  • SLES 15 SP5 CHOST Images for Amazon EC2
  • SLES 15 SP1 CHOST Images for Google
  • SLES 15 SP2 CHOST Images for Google
  • SLES 15 SP3 CHOST Images for Google
  • SLES 15 SP4 CHOST Images for Google
  • SLES 15 SP5 CHOST Images for Google
Summary
In the Linux kernel, the following vulnerability has been resolved: dm cache policy smq: check allocation under invalidate lock commit 2d1f7b65f5de ("dm cache policy smq: fix missing locks in invalidating cache blocks") added mq->lock around the destructive part of smq_invalidate_mapping(), but left the e->allocated check outside the critical section. That leaves a check-then-act race. Two concurrent invalidators can both observe e->allocated as true before either of them takes mq->lock. The first invalidator that acquires the lock removes the entry from the queues and hash table and then calls free_entry(), which clears e->allocated and puts the entry back on the free list. The second invalidator can then acquire mq->lock and continue with the stale result of the unlocked check. This can corrupt the SMQ queues or hash table by deleting an entry that is no longer on those structures. It can also hit the allocation check in free_entry() when the same entry is freed again. Move the allocation check under mq->lock so the predicate and the destructive operations are serialized by the same lock.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-39216

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 21 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: dm cache policy smq: check allocation under invalidate lock commit 2d1f7b65f5de ("dm cache policy smq: fix missing locks in invalidating cache blocks") added mq->lock around the destructive part of smq_invalidate_mapping(), but left the e->allocated check outside the critical section. That leaves a check-then-act race. Two concurrent invalidators can both observe e->allocated as true before either of them takes mq->lock. The first invalidator that acquires the lock removes the entry from the queues and hash table and then calls free_entry(), which clears e->allocated and puts the entry back on the free list. The second invalidator can then acquire mq->lock and continue with the stale result of the unlocked check. This can corrupt the SMQ queues or hash table by deleting an entry that is no longer on those structures. It can also hit the allocation check in free_entry() when the same entry is freed again. Move the allocation check under mq->lock so the predicate and the destructive operations are serialized by the same lock.

What

In the Linux kernel, the following vulnerability has been resolved: dm cache policy smq: check allocation under invalidate lock commit 2d1f7b65f5de ("dm cache policy smq: fix missing locks in invalidating cache blocks") added mq->lock around the destructive part of smq_invalidate_mapping(), but left the e->allocated check outside the critical section. That leaves a check-then-act race. Two concurrent invalidators can both observe e->allocated as true before either of them takes mq->lock. The first invalidator that acquires the lock removes the entry from the queues and hash table and then calls free_entry(), which clears e->allocated and puts the entry back on the free list. The second invalidator can then acquire mq->lock and continue with the stale result of the unlocked check. This can corrupt the SMQ queues or hash table by deleting an entry that is no longer on those structures. It can also hit the allocation check in free_entry() when the same entry is freed again. Move the allocation check under mq->lock so the predicate and the destructive operations are serialized by the same lock.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: dm cache policy smq: check allocation under invalidate lock commit 2d1f7b65f5de ("dm cache policy smq: fix missing locks in invalidating cache blocks") added mq->lock around the destructive part of smq_invalidate_mapping(), but left the e->allocated check outside the critical section. That leaves a check-then-act race. Two concurrent invalidators can both observe e->allocated as true before either of them takes mq->lock. The first invalidator that acquires the lock removes the entry from the queues and hash table and then calls free_entry(), which clears e->allocated and puts the entry back on the free list. The second invalidator can then acquire mq->lock and continue with the stale result of the unlocked check. This can corrupt the SMQ queues or hash table by deleting an entry that is no longer on those structures. It can also hit the allocation check in free_entry() when the same entry is freed again. Move the allocation check under mq->lock so the predicate and the destructive operations are serialized by the same lock.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-2077Linux Kernel: Mehrere Schwachstellen

Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260701Security Bulletin 1 July 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 1 July 2026, published on 1 July 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1231Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-53149 Référence CVE CVE-2026-53163 https://www.cve.org/CVERecord?id=CVE-2026-53163 Référence CVE CVE-2026-53219 https://www.cve.org/CVERecord?id=CVE-2026-53219 Référence CVE CVE-2026-53220 https://www.cve.org/CVERecord?id=CVE-2026-53220 Référence CVE CVE-2026-53223 https://www.cve.org/CVERecord?id=CVE-2026-53223 Référence CVE CVE-2026-53228 https://www.cve.org/CVERecord?id=CVE-2026-53228 Référence CVE CVE-2026-53238 https://www.cve.org/CVERecord?id=CVE-2026-53238 Référence CVE CVE-2026-53260 https://www.cve.org/CVERecord?id=CVE-2026-53260 Référence CVE CVE-2026-53264 https://www.cve.org/CVERecord?id=CVE-2026-53264 Référence CVE CVE-2026-53265 https://www.cve.org/CVERecord?id=CVE-2026-53265 Référence CVE CVE-2026-53309 https://www.cve.org/CVERecord?id=CVE-2026-53309 Référence CVE CVE-2026-53360 https://www.cve.org/CVERecord?id=CVE-2026-53360 Référence CVE CVE-2026-53374 https://www.cve.org/CVERecord?id=CVE-2026-53374 Référence CVE CVE-2026-53381 https://www.cve.org/CVERecord?id=CVE-2026-53381 Référence CVE CVE-2026-53388 https://www.cve.org/CVERecord?id=CVE-2026-53388 Référence CVE CVE-2026-53403 https://www.cve.org/CVERecord?id=CVE-2026-53403 Référence CVE CVE-2026-63801 https://www.cve.org/CVERecord?id=CVE-2026-63801 Référence CVE CVE-2026-63810 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53256 Référence CVE CVE-2026-53257 https://www.cve.org/CVERecord?id=CVE-2026-53257 Référence CVE CVE-2026-53258 https://www.cve.org/CVERecord?id=CVE-2026-53258 Référence CVE CVE-2026-53259 https://www.cve.org/CVERecord?id=CVE-2026-53259 Référence CVE CVE-2026-53260 https://www.cve.org/CVERecord?id=CVE-2026-53260 Référence CVE CVE-2026-53261 https://www.cve.org/CVERecord?id=CVE-2026-53261 Référence CVE CVE-2026-53262 https://www.cve.org/CVERecord?id=CVE-2026-53262 Référence CVE CVE-2026-53263 https://www.cve.org/CVERecord?id=CVE-2026-53263 Référence CVE CVE-2026-53264 https://www.cve.org/CVERecord?id=CVE-2026-53264 Référence CVE CVE-2026-53265 https://www.cve.org/CVERecord?id=CVE-2026-53265 Référence CVE CVE-2026-53266 https://www.cve.org/CVERecord?id=CVE-2026-53266 Référence CVE CVE-2026-53267 https://www.cve.org/CVERecord?id=CVE-2026-53267 Référence CVE CVE-2026-53268 https://www.cve.org/CVERecord?id=CVE-2026-53268 Référence CVE CVE-2026-53269 https://www.cve.org/CVERecord?id=CVE-2026-53269 Référence CVE CVE-2026-53270 https://www.cve.org/CVERecord?id=CVE-2026-53270 Référence CVE CVE-2026-53271 https://www.cve.org/CVERecord?id=CVE-2026-53271 Référence CVE CVE-2026-53272 https://www.cve.org/CVERecord?id=CVE-2026-53272 Référence CVE CVE-2026-53273 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1203Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53255 Référence CVE CVE-2026-53256 https://www.cve.org/CVERecord?id=CVE-2026-53256 Référence CVE CVE-2026-53257 https://www.cve.org/CVERecord?id=CVE-2026-53257 Référence CVE CVE-2026-53258 https://www.cve.org/CVERecord?id=CVE-2026-53258 Référence CVE CVE-2026-53259 https://www.cve.org/CVERecord?id=CVE-2026-53259 Référence CVE CVE-2026-53261 https://www.cve.org/CVERecord?id=CVE-2026-53261 Référence CVE CVE-2026-53262 https://www.cve.org/CVERecord?id=CVE-2026-53262 Référence CVE CVE-2026-53263 https://www.cve.org/CVERecord?id=CVE-2026-53263 Référence CVE CVE-2026-53264 https://www.cve.org/CVERecord?id=CVE-2026-53264 Référence CVE CVE-2026-53265 https://www.cve.org/CVERecord?id=CVE-2026-53265 Référence CVE CVE-2026-53266 https://www.cve.org/CVERecord?id=CVE-2026-53266 Référence CVE CVE-2026-53267 https://www.cve.org/CVERecord?id=CVE-2026-53267 Référence CVE CVE-2026-53268 https://www.cve.org/CVERecord?id=CVE-2026-53268 Référence CVE CVE-2026-53269 https://www.cve.org/CVERecord?id=CVE-2026-53269 Référence CVE CVE-2026-53270 https://www.cve.org/CVERecord?id=CVE-2026-53270 Référence CVE CVE-2026-53271 https://www.cve.org/CVERecord?id=CVE-2026-53271 Référence CVE CVE-2026-53272 https://www.cve.org/CVERecord?id=CVE-2026-53272 Référence CVE CVE-2026-53273 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1162Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53256 Référence CVE CVE-2026-53257 https://www.cve.org/CVERecord?id=CVE-2026-53257 Référence CVE CVE-2026-53258 https://www.cve.org/CVERecord?id=CVE-2026-53258 Référence CVE CVE-2026-53259 https://www.cve.org/CVERecord?id=CVE-2026-53259 Référence CVE CVE-2026-53260 https://www.cve.org/CVERecord?id=CVE-2026-53260 Référence CVE CVE-2026-53261 https://www.cve.org/CVERecord?id=CVE-2026-53261 Référence CVE CVE-2026-53262 https://www.cve.org/CVERecord?id=CVE-2026-53262 Référence CVE CVE-2026-53263 https://www.cve.org/CVERecord?id=CVE-2026-53263 Référence CVE CVE-2026-53264 https://www.cve.org/CVERecord?id=CVE-2026-53264 Référence CVE CVE-2026-53265 https://www.cve.org/CVERecord?id=CVE-2026-53265 Référence CVE CVE-2026-53266 https://www.cve.org/CVERecord?id=CVE-2026-53266 Référence CVE CVE-2026-53267 https://www.cve.org/CVERecord?id=CVE-2026-53267 Référence CVE CVE-2026-53268 https://www.cve.org/CVERecord?id=CVE-2026-53268 Référence CVE CVE-2026-53269 https://www.cve.org/CVERecord?id=CVE-2026-53269 Référence CVE CVE-2026-53270 https://www.cve.org/CVERecord?id=CVE-2026-53270 Référence CVE CVE-2026-53271 https://www.cve.org/CVERecord?id=CVE-2026-53271 Référence CVE CVE-2026-53272 https://www.cve.org/CVERecord?id=CVE-2026-53272 Référence CVE CVE-2026-53273 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1091Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-53221 Référence CVE CVE-2026-53224 https://www.cve.org/CVERecord?id=CVE-2026-53224 Référence CVE CVE-2026-53230 https://www.cve.org/CVERecord?id=CVE-2026-53230 Référence CVE CVE-2026-53236 https://www.cve.org/CVERecord?id=CVE-2026-53236 Référence CVE CVE-2026-53246 https://www.cve.org/CVERecord?id=CVE-2026-53246 Référence CVE CVE-2026-53250 https://www.cve.org/CVERecord?id=CVE-2026-53250 Référence CVE CVE-2026-53252 https://www.cve.org/CVERecord?id=CVE-2026-53252 Référence CVE CVE-2026-53256 https://www.cve.org/CVERecord?id=CVE-2026-53256 Référence CVE CVE-2026-53262 https://www.cve.org/CVERecord?id=CVE-2026-53262 Référence CVE CVE-2026-53265 https://www.cve.org/CVERecord?id=CVE-2026-53265 Référence CVE CVE-2026-53267 https://www.cve.org/CVERecord?id=CVE-2026-53267 Référence CVE CVE-2026-53270 https://www.cve.org/CVERecord?id=CVE-2026-53270 Référence CVE CVE-2026-53275 https://www.cve.org/CVERecord?id=CVE-2026-53275 Référence CVE CVE-2026-53289 https://www.cve.org/CVERecord?id=CVE-2026-53289 Référence CVE CVE-2026-53291 https://www.cve.org/CVERecord?id=CVE-2026-53291 Référence CVE CVE-2026-53297 https://www.cve.org/CVERecord?id=CVE-2026-53297 Référence CVE CVE-2026-53321 https://www.cve.org/CVERecord?id=CVE-2026-53321 Référence CVE CVE-2026-53324 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1064Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-53247 Référence CVE CVE-2026-53250 https://www.cve.org/CVERecord?id=CVE-2026-53250 Référence CVE CVE-2026-53251 https://www.cve.org/CVERecord?id=CVE-2026-53251 Référence CVE CVE-2026-53252 https://www.cve.org/CVERecord?id=CVE-2026-53252 Référence CVE CVE-2026-53253 https://www.cve.org/CVERecord?id=CVE-2026-53253 Référence CVE CVE-2026-53254 https://www.cve.org/CVERecord?id=CVE-2026-53254 Référence CVE CVE-2026-53255 https://www.cve.org/CVERecord?id=CVE-2026-53255 Référence CVE CVE-2026-53256 https://www.cve.org/CVERecord?id=CVE-2026-53256 Référence CVE CVE-2026-53260 https://www.cve.org/CVERecord?id=CVE-2026-53260 Référence CVE CVE-2026-53265 https://www.cve.org/CVERecord?id=CVE-2026-53265 Référence CVE CVE-2026-53267 https://www.cve.org/CVERecord?id=CVE-2026-53267 Référence CVE CVE-2026-53268 https://www.cve.org/CVERecord?id=CVE-2026-53268 Référence CVE CVE-2026-53270 https://www.cve.org/CVERecord?id=CVE-2026-53270 Référence CVE CVE-2026-53273 https://www.cve.org/CVERecord?id=CVE-2026-53273 Référence CVE CVE-2026-53275 https://www.cve.org/CVERecord?id=CVE-2026-53275 Référence CVE CVE-2026-53277 https://www.cve.org/CVERecord?id=CVE-2026-53277 Référence CVE CVE-2026-53279 https://www.cve.org/CVERecord?id=CVE-2026-53279 Référence CVE CVE-2026-53289 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0812Multiples vulnérabilités dans Microsoft Azure Linux

ulletin de sécurité Microsoft CVE-2026-53242 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53245 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53247 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53249 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53252 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53253 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53254 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53255 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53263 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53264 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53265 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53266 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53267 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53268 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53270 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53274 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53275 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-55200 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-9675 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-9697 du 27 juin 2026 Une gestion de version détaillée se trouve à la fin de ce document. Risque No

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-022876LinuxのLinux Kernelにおける不特定の脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。dmキャッシュポリシーsmqでは、無効化ロック下での割り当てチェックに問題がありました。コミット2d1f7b65f5de（"dm cache policy smq: 無効化キャッシュブロックのロック漏れ修正"）では、smq_invalidate_mapping()の破壊的な部分の周りにmq-＞lockを追加しましたが、e-＞allocatedのチェックがクリティカルセクションの外に残されていました。このため、チェック・アクションの競合状態が発生していました。2つの同時に動作する無効化処理が、どちらもmq-＞lockを取得する前にe-＞allocatedをtrueと判断する場合があります。最初にロックを取得した無効化処理は、キューやハッシュテーブルからエントリを削除し、free_entry()を呼び出してe-＞allocatedをクリアし、エントリをフリーリストに戻します。2番目の無効化処理は、その後mq-＞lockを取得し、ロックなしでの古いチェック結果を使って処理を続けてしまいます。これにより、SMQのキューやハッシュテーブルが既に存在しないエントリを削除しようとして破損する可能性があります。また、同じエントリが再度解放される際にfree_entry()の割り当てチェックで問題が発生することもあります。割り当てチェックをmq-＞lockの下に移動し、述語の評価と破壊的操作が同じロックによって直列化されるように修正しました。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 25 Jun 2026 · Last source change 5 Aug 2026, 12:34 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-39216
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD enriched

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-39216↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-53265 · cve.blacktree.nl