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

dm cache: fix null-deref with concurrent writes in passthrough mode

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 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 severityMediumOperational priority:Low, lowered one band.downgradedsince 24 Jun 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.16% 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: No default targetRemediation target: Normal maintenance

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 20 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 20 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 · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.94-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.176-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.10-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.10-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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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-53064 · CSAF 2.0 · revision 14 · interimSUSE Product Security TeamCVE-2026-53064
295 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: dm cache: fix null-deref with concurrent writes in passthrough mode In passthrough mode, when dm-cache starts to invalidate a cache entry and bio prison cell lock fails due to concurrent write to the same cached block, mg->cell remains NULL. The error path in invalidate_complete() attempts to unlock and free the cell unconditionally, causing a NULL pointer dereference: KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 0 UID: 0 PID: 134 Comm: fio Not tainted 6.19.0-rc7 #3 PREEMPT RIP: 0010:dm_cell_unlock_v2+0x3f/0x210 Call Trace: invalidate_complete+0xef/0x430 map_bio+0x130f/0x1a10 cache_map+0x320/0x6b0 __map_bio+0x458/0x510 dm_submit_bio+0x40e/0x16d0 __submit_bio+0x419/0x870 Reproduce steps: 1. Create a cache device 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. Promote the first data block into cache fio --filename=/dev/mapper/cache --name=populate --rw=write --bs=4k \ --direct=1 --size=64k 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 first cached block concurrently fio --filename=/dev/mapper/cache --name test --rw=randwrite --bs=4k \ --randrepeat=0 --direct=1 --numjobs=2 --size 64k Fix by checking if mg->cell is valid before attempting to unlock it.
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-38932

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 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: fix null-deref with concurrent writes in passthrough mode In passthrough mode, when dm-cache starts to invalidate a cache entry and bio prison cell lock fails due to concurrent write to the same cached block, mg->cell remains NULL. The error path in invalidate_complete() attempts to unlock and free the cell unconditionally, causing a NULL pointer dereference: KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 0 UID: 0 PID: 134 Comm: fio Not tainted 6.19.0-rc7 #3 PREEMPT RIP: 0010:dm_cell_unlock_v2+0x3f/0x210 <snip> Call Trace: invalidate_complete+0xef/0x430 map_bio+0x130f/0x1a10 cache_map+0x320/0x6b0 __map_bio+0x458/0x510 dm_submit_bio+0x40e/0x16d0 __submit_bio+0x419/0x870 <snip> Reproduce steps: 1. Create a cache device 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. Promote the first data block into cache fio --filename=/dev/mapper/cache --name=populate --rw=write --bs=4k \ --direct=1 --size=64k 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 first cached block concurrently fio --filename=/dev/mapper/cache --name test --rw=randwrite --bs=4k \ --randrepeat=0 --direct=1 --numjobs=2 --size 64k Fix by checking if mg->cell is valid before attempting to unlock it.

What

In the Linux kernel, the following vulnerability has been resolved: dm cache: fix null-deref with concurrent writes in passthrough mode In passthrough mode, when dm-cache starts to invalidate a cache entry and bio prison cell lock fails due to concurrent write to the same cached block, mg->cell remains NULL. The error path in invalidate_complete() attempts to unlock and free the cell unconditionally, causing a NULL pointer dereference: KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 0 UID: 0 PID: 134 Comm: fio Not tainted 6.19.0-rc7 #3 PREEMPT RIP: 0010:dm_cell_unlock_v2+0x3f/0x210 <snip> Call Trace: invalidate_complete+0xef/0x430 map_bio+0x130f/0x1a10 cache_map+0x320/0x6b0 __map_bio+0x458/0x510 dm_submit_bio+0x40e/0x16d0 __submit_bio+0x419/0x870 <snip> Reproduce steps: 1. Create a cache device 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. Promote the first data block into cache fio --filename=/dev/mapper/cache --name=populate --rw=write --bs=4k \ --direct=1 --size=64k 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 first cached block concurrently fio --filename=/dev/mapper/cache --name test --rw=randwrite --bs=4k \ --randrepeat=0 --direct=1 --numjobs=2 --size 64k Fix by checking if mg->cell is valid before attempting to unlock it.

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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: fix null-deref with concurrent writes in passthrough mode In passthrough mode, when dm-cache starts to invalidate a cache entry and bio prison cell lock fails due to concurrent write to the same cached block, mg->cell remains NULL. The error path in invalidate_complete() attempts to unlock and free the cell unconditionally, causing a NULL pointer dereference: KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 0 UID: 0 PID: 134 Comm: fio Not tainted 6.19.0-rc7 #3 PREEMPT RIP: 0010:dm_cell_unlock_v2+0x3f/0x210 <snip> Call Trace: invalidate_complete+0xef/0x430 map_bio+0x130f/0x1a10 cache_map+0x320/0x6b0 __map_bio+0x458/0x510 dm_submit_bio+0x40e/0x16d0 __submit_bio+0x419/0x870 <snip> Reproduce steps: 1. Create a cache device 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. Promote the first data block into cache fio --filename=/dev/mapper/cache --name=populate --rw=write --bs=4k \ --direct=1 --size=64k 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 first cached block concurrently fio --filename=/dev/mapper/cache --name test --rw=randwrite --bs=4k \ --randrepeat=0 --direct=1 --numjobs=2 --size 64k Fix by checking if mg->cell is valid before attempting to unlock it.

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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 → NULL Pointer Dereference → 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: a standard category for the underlying weakness.
CWE-476 ↗

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

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:N/I:N/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.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.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.
CWE-476
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-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53055 Référence CVE CVE-2026-53056 https://www.cve.org/CVERecord?id=CVE-2026-53056 Référence CVE CVE-2026-53057 https://www.cve.org/CVERecord?id=CVE-2026-53057 Référence CVE CVE-2026-53058 https://www.cve.org/CVERecord?id=CVE-2026-53058 Référence CVE CVE-2026-53059 https://www.cve.org/CVERecord?id=CVE-2026-53059 Référence CVE CVE-2026-53060 https://www.cve.org/CVERecord?id=CVE-2026-53060 Référence CVE CVE-2026-53061 https://www.cve.org/CVERecord?id=CVE-2026-53061 Référence CVE CVE-2026-53062 https://www.cve.org/CVERecord?id=CVE-2026-53062 Référence CVE CVE-2026-53063 https://www.cve.org/CVERecord?id=CVE-2026-53063 Référence CVE CVE-2026-53064 https://www.cve.org/CVERecord?id=CVE-2026-53064 Référence CVE CVE-2026-53065 https://www.cve.org/CVERecord?id=CVE-2026-53065 Référence CVE CVE-2026-53066 https://www.cve.org/CVERecord?id=CVE-2026-53066 Référence CVE CVE-2026-53067 https://www.cve.org/CVERecord?id=CVE-2026-53067 Référence CVE CVE-2026-53068 https://www.cve.org/CVERecord?id=CVE-2026-53068 Référence CVE CVE-2026-53069 https://www.cve.org/CVERecord?id=CVE-2026-53069 Référence CVE CVE-2026-53070 https://www.cve.org/CVERecord?id=CVE-2026-53070 Référence CVE CVE-2026-53071 https://www.cve.org/CVERecord?id=CVE-2026-53071 Référence CVE CVE-2026-53072 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-53055 Référence CVE CVE-2026-53056 https://www.cve.org/CVERecord?id=CVE-2026-53056 Référence CVE CVE-2026-53057 https://www.cve.org/CVERecord?id=CVE-2026-53057 Référence CVE CVE-2026-53058 https://www.cve.org/CVERecord?id=CVE-2026-53058 Référence CVE CVE-2026-53059 https://www.cve.org/CVERecord?id=CVE-2026-53059 Référence CVE CVE-2026-53060 https://www.cve.org/CVERecord?id=CVE-2026-53060 Référence CVE CVE-2026-53061 https://www.cve.org/CVERecord?id=CVE-2026-53061 Référence CVE CVE-2026-53062 https://www.cve.org/CVERecord?id=CVE-2026-53062 Référence CVE CVE-2026-53063 https://www.cve.org/CVERecord?id=CVE-2026-53063 Référence CVE CVE-2026-53064 https://www.cve.org/CVERecord?id=CVE-2026-53064 Référence CVE CVE-2026-53065 https://www.cve.org/CVERecord?id=CVE-2026-53065 Référence CVE CVE-2026-53066 https://www.cve.org/CVERecord?id=CVE-2026-53066 Référence CVE CVE-2026-53067 https://www.cve.org/CVERecord?id=CVE-2026-53067 Référence CVE CVE-2026-53068 https://www.cve.org/CVERecord?id=CVE-2026-53068 Référence CVE CVE-2026-53069 https://www.cve.org/CVERecord?id=CVE-2026-53069 Référence CVE CVE-2026-53070 https://www.cve.org/CVERecord?id=CVE-2026-53070 Référence CVE CVE-2026-53071 https://www.cve.org/CVERecord?id=CVE-2026-53071 Référence CVE CVE-2026-53072 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-53055 Référence CVE CVE-2026-53056 https://www.cve.org/CVERecord?id=CVE-2026-53056 Référence CVE CVE-2026-53057 https://www.cve.org/CVERecord?id=CVE-2026-53057 Référence CVE CVE-2026-53058 https://www.cve.org/CVERecord?id=CVE-2026-53058 Référence CVE CVE-2026-53059 https://www.cve.org/CVERecord?id=CVE-2026-53059 Référence CVE CVE-2026-53060 https://www.cve.org/CVERecord?id=CVE-2026-53060 Référence CVE CVE-2026-53061 https://www.cve.org/CVERecord?id=CVE-2026-53061 Référence CVE CVE-2026-53062 https://www.cve.org/CVERecord?id=CVE-2026-53062 Référence CVE CVE-2026-53063 https://www.cve.org/CVERecord?id=CVE-2026-53063 Référence CVE CVE-2026-53064 https://www.cve.org/CVERecord?id=CVE-2026-53064 Référence CVE CVE-2026-53065 https://www.cve.org/CVERecord?id=CVE-2026-53065 Référence CVE CVE-2026-53066 https://www.cve.org/CVERecord?id=CVE-2026-53066 Référence CVE CVE-2026-53067 https://www.cve.org/CVERecord?id=CVE-2026-53067 Référence CVE CVE-2026-53068 https://www.cve.org/CVERecord?id=CVE-2026-53068 Référence CVE CVE-2026-53069 https://www.cve.org/CVERecord?id=CVE-2026-53069 Référence CVE CVE-2026-53070 https://www.cve.org/CVERecord?id=CVE-2026-53070 Référence CVE CVE-2026-53071 https://www.cve.org/CVERecord?id=CVE-2026-53071 Référence CVE CVE-2026-53072 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53046 Référence CVE CVE-2026-53047 https://www.cve.org/CVERecord?id=CVE-2026-53047 Référence CVE CVE-2026-53048 https://www.cve.org/CVERecord?id=CVE-2026-53048 Référence CVE CVE-2026-53049 https://www.cve.org/CVERecord?id=CVE-2026-53049 Référence CVE CVE-2026-53050 https://www.cve.org/CVERecord?id=CVE-2026-53050 Référence CVE CVE-2026-53059 https://www.cve.org/CVERecord?id=CVE-2026-53059 Référence CVE CVE-2026-53060 https://www.cve.org/CVERecord?id=CVE-2026-53060 Référence CVE CVE-2026-53061 https://www.cve.org/CVERecord?id=CVE-2026-53061 Référence CVE CVE-2026-53062 https://www.cve.org/CVERecord?id=CVE-2026-53062 Référence CVE CVE-2026-53064 https://www.cve.org/CVERecord?id=CVE-2026-53064 Référence CVE CVE-2026-53065 https://www.cve.org/CVERecord?id=CVE-2026-53065 Référence CVE CVE-2026-53068 https://www.cve.org/CVERecord?id=CVE-2026-53068 Référence CVE CVE-2026-53069 https://www.cve.org/CVERecord?id=CVE-2026-53069 Référence CVE CVE-2026-53071 https://www.cve.org/CVERecord?id=CVE-2026-53071 Référence CVE CVE-2026-53072 https://www.cve.org/CVERecord?id=CVE-2026-53072 Référence CVE CVE-2026-53073 https://www.cve.org/CVERecord?id=CVE-2026-53073 Référence CVE CVE-2026-53074 https://www.cve.org/CVERecord?id=CVE-2026-53074 Référence CVE CVE-2026-53075 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-52999 Référence CVE CVE-2026-53000 https://www.cve.org/CVERecord?id=CVE-2026-53000 Référence CVE CVE-2026-53002 https://www.cve.org/CVERecord?id=CVE-2026-53002 Référence CVE CVE-2026-53006 https://www.cve.org/CVERecord?id=CVE-2026-53006 Référence CVE CVE-2026-53011 https://www.cve.org/CVERecord?id=CVE-2026-53011 Référence CVE CVE-2026-53012 https://www.cve.org/CVERecord?id=CVE-2026-53012 Référence CVE CVE-2026-53032 https://www.cve.org/CVERecord?id=CVE-2026-53032 Référence CVE CVE-2026-53062 https://www.cve.org/CVERecord?id=CVE-2026-53062 Référence CVE CVE-2026-53063 https://www.cve.org/CVERecord?id=CVE-2026-53063 Référence CVE CVE-2026-53064 https://www.cve.org/CVERecord?id=CVE-2026-53064 Référence CVE CVE-2026-53069 https://www.cve.org/CVERecord?id=CVE-2026-53069 Référence CVE CVE-2026-53074 https://www.cve.org/CVERecord?id=CVE-2026-53074 Référence CVE CVE-2026-53083 https://www.cve.org/CVERecord?id=CVE-2026-53083 Référence CVE CVE-2026-53088 https://www.cve.org/CVERecord?id=CVE-2026-53088 Référence CVE CVE-2026-53106 https://www.cve.org/CVERecord?id=CVE-2026-53106 Référence CVE CVE-2026-53107 https://www.cve.org/CVERecord?id=CVE-2026-53107 Référence CVE CVE-2026-53123 https://www.cve.org/CVERecord?id=CVE-2026-53123 Référence CVE CVE-2026-53129 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53055 Référence CVE CVE-2026-53056 https://www.cve.org/CVERecord?id=CVE-2026-53056 Référence CVE CVE-2026-53057 https://www.cve.org/CVERecord?id=CVE-2026-53057 Référence CVE CVE-2026-53058 https://www.cve.org/CVERecord?id=CVE-2026-53058 Référence CVE CVE-2026-53059 https://www.cve.org/CVERecord?id=CVE-2026-53059 Référence CVE CVE-2026-53060 https://www.cve.org/CVERecord?id=CVE-2026-53060 Référence CVE CVE-2026-53061 https://www.cve.org/CVERecord?id=CVE-2026-53061 Référence CVE CVE-2026-53062 https://www.cve.org/CVERecord?id=CVE-2026-53062 Référence CVE CVE-2026-53063 https://www.cve.org/CVERecord?id=CVE-2026-53063 Référence CVE CVE-2026-53064 https://www.cve.org/CVERecord?id=CVE-2026-53064 Référence CVE CVE-2026-53065 https://www.cve.org/CVERecord?id=CVE-2026-53065 Référence CVE CVE-2026-53066 https://www.cve.org/CVERecord?id=CVE-2026-53066 Référence CVE CVE-2026-53067 https://www.cve.org/CVERecord?id=CVE-2026-53067 Référence CVE CVE-2026-53068 https://www.cve.org/CVERecord?id=CVE-2026-53068 Référence CVE CVE-2026-53069 https://www.cve.org/CVERecord?id=CVE-2026-53069 Référence CVE CVE-2026-53070 https://www.cve.org/CVERecord?id=CVE-2026-53070 Référence CVE CVE-2026-53071 https://www.cve.org/CVERecord?id=CVE-2026-53071 Référence CVE CVE-2026-53072 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-53038 Référence CVE CVE-2026-53045 https://www.cve.org/CVERecord?id=CVE-2026-53045 Référence CVE CVE-2026-53047 https://www.cve.org/CVERecord?id=CVE-2026-53047 Référence CVE CVE-2026-53051 https://www.cve.org/CVERecord?id=CVE-2026-53051 Référence CVE CVE-2026-53052 https://www.cve.org/CVERecord?id=CVE-2026-53052 Référence CVE CVE-2026-53056 https://www.cve.org/CVERecord?id=CVE-2026-53056 Référence CVE CVE-2026-53058 https://www.cve.org/CVERecord?id=CVE-2026-53058 Référence CVE CVE-2026-53062 https://www.cve.org/CVERecord?id=CVE-2026-53062 Référence CVE CVE-2026-53063 https://www.cve.org/CVERecord?id=CVE-2026-53063 Référence CVE CVE-2026-53064 https://www.cve.org/CVERecord?id=CVE-2026-53064 Référence CVE CVE-2026-53065 https://www.cve.org/CVERecord?id=CVE-2026-53065 Référence CVE CVE-2026-53066 https://www.cve.org/CVERecord?id=CVE-2026-53066 Référence CVE CVE-2026-53068 https://www.cve.org/CVERecord?id=CVE-2026-53068 Référence CVE CVE-2026-53069 https://www.cve.org/CVERecord?id=CVE-2026-53069 Référence CVE CVE-2026-53070 https://www.cve.org/CVERecord?id=CVE-2026-53070 Référence CVE CVE-2026-53071 https://www.cve.org/CVERecord?id=CVE-2026-53071 Référence CVE CVE-2026-53072 https://www.cve.org/CVERecord?id=CVE-2026-53072 Référence CVE CVE-2026-53073 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53006 Référence CVE CVE-2026-53016 https://www.cve.org/CVERecord?id=CVE-2026-53016 Référence CVE CVE-2026-53021 https://www.cve.org/CVERecord?id=CVE-2026-53021 Référence CVE CVE-2026-53036 https://www.cve.org/CVERecord?id=CVE-2026-53036 Référence CVE CVE-2026-53039 https://www.cve.org/CVERecord?id=CVE-2026-53039 Référence CVE CVE-2026-53050 https://www.cve.org/CVERecord?id=CVE-2026-53050 Référence CVE CVE-2026-53060 https://www.cve.org/CVERecord?id=CVE-2026-53060 Référence CVE CVE-2026-53062 https://www.cve.org/CVERecord?id=CVE-2026-53062 Référence CVE CVE-2026-53063 https://www.cve.org/CVERecord?id=CVE-2026-53063 Référence CVE CVE-2026-53064 https://www.cve.org/CVERecord?id=CVE-2026-53064 Référence CVE CVE-2026-53080 https://www.cve.org/CVERecord?id=CVE-2026-53080 Référence CVE CVE-2026-53093 https://www.cve.org/CVERecord?id=CVE-2026-53093 Référence CVE CVE-2026-53107 https://www.cve.org/CVERecord?id=CVE-2026-53107 Référence CVE CVE-2026-53129 https://www.cve.org/CVERecord?id=CVE-2026-53129 Référence CVE CVE-2026-53131 https://www.cve.org/CVERecord?id=CVE-2026-53131 Référence CVE CVE-2026-53134 https://www.cve.org/CVERecord?id=CVE-2026-53134 Référence CVE CVE-2026-53146 https://www.cve.org/CVERecord?id=CVE-2026-53146 Référence CVE CVE-2026-53147 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53046 Référence CVE CVE-2026-53047 https://www.cve.org/CVERecord?id=CVE-2026-53047 Référence CVE CVE-2026-53048 https://www.cve.org/CVERecord?id=CVE-2026-53048 Référence CVE CVE-2026-53049 https://www.cve.org/CVERecord?id=CVE-2026-53049 Référence CVE CVE-2026-53050 https://www.cve.org/CVERecord?id=CVE-2026-53050 Référence CVE CVE-2026-53059 https://www.cve.org/CVERecord?id=CVE-2026-53059 Référence CVE CVE-2026-53060 https://www.cve.org/CVERecord?id=CVE-2026-53060 Référence CVE CVE-2026-53061 https://www.cve.org/CVERecord?id=CVE-2026-53061 Référence CVE CVE-2026-53062 https://www.cve.org/CVERecord?id=CVE-2026-53062 Référence CVE CVE-2026-53064 https://www.cve.org/CVERecord?id=CVE-2026-53064 Référence CVE CVE-2026-53065 https://www.cve.org/CVERecord?id=CVE-2026-53065 Référence CVE CVE-2026-53068 https://www.cve.org/CVERecord?id=CVE-2026-53068 Référence CVE CVE-2026-53069 https://www.cve.org/CVERecord?id=CVE-2026-53069 Référence CVE CVE-2026-53071 https://www.cve.org/CVERecord?id=CVE-2026-53071 Référence CVE CVE-2026-53072 https://www.cve.org/CVERecord?id=CVE-2026-53072 Référence CVE CVE-2026-53073 https://www.cve.org/CVERecord?id=CVE-2026-53073 Référence CVE CVE-2026-53074 https://www.cve.org/CVERecord?id=CVE-2026-53074 Référence CVE CVE-2026-53075 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53055 Référence CVE CVE-2026-53056 https://www.cve.org/CVERecord?id=CVE-2026-53056 Référence CVE CVE-2026-53057 https://www.cve.org/CVERecord?id=CVE-2026-53057 Référence CVE CVE-2026-53058 https://www.cve.org/CVERecord?id=CVE-2026-53058 Référence CVE CVE-2026-53059 https://www.cve.org/CVERecord?id=CVE-2026-53059 Référence CVE CVE-2026-53060 https://www.cve.org/CVERecord?id=CVE-2026-53060 Référence CVE CVE-2026-53061 https://www.cve.org/CVERecord?id=CVE-2026-53061 Référence CVE CVE-2026-53062 https://www.cve.org/CVERecord?id=CVE-2026-53062 Référence CVE CVE-2026-53063 https://www.cve.org/CVERecord?id=CVE-2026-53063 Référence CVE CVE-2026-53064 https://www.cve.org/CVERecord?id=CVE-2026-53064 Référence CVE CVE-2026-53065 https://www.cve.org/CVERecord?id=CVE-2026-53065 Référence CVE CVE-2026-53066 https://www.cve.org/CVERecord?id=CVE-2026-53066 Référence CVE CVE-2026-53067 https://www.cve.org/CVERecord?id=CVE-2026-53067 Référence CVE CVE-2026-53068 https://www.cve.org/CVERecord?id=CVE-2026-53068 Référence CVE CVE-2026-53069 https://www.cve.org/CVERecord?id=CVE-2026-53069 Référence CVE CVE-2026-53070 https://www.cve.org/CVERecord?id=CVE-2026-53070 Référence CVE CVE-2026-53071 https://www.cve.org/CVERecord?id=CVE-2026-53071 Référence CVE CVE-2026-53072 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53055 Référence CVE CVE-2026-53056 https://www.cve.org/CVERecord?id=CVE-2026-53056 Référence CVE CVE-2026-53057 https://www.cve.org/CVERecord?id=CVE-2026-53057 Référence CVE CVE-2026-53058 https://www.cve.org/CVERecord?id=CVE-2026-53058 Référence CVE CVE-2026-53059 https://www.cve.org/CVERecord?id=CVE-2026-53059 Référence CVE CVE-2026-53060 https://www.cve.org/CVERecord?id=CVE-2026-53060 Référence CVE CVE-2026-53061 https://www.cve.org/CVERecord?id=CVE-2026-53061 Référence CVE CVE-2026-53062 https://www.cve.org/CVERecord?id=CVE-2026-53062 Référence CVE CVE-2026-53063 https://www.cve.org/CVERecord?id=CVE-2026-53063 Référence CVE CVE-2026-53064 https://www.cve.org/CVERecord?id=CVE-2026-53064 Référence CVE CVE-2026-53065 https://www.cve.org/CVERecord?id=CVE-2026-53065 Référence CVE CVE-2026-53066 https://www.cve.org/CVERecord?id=CVE-2026-53066 Référence CVE CVE-2026-53067 https://www.cve.org/CVERecord?id=CVE-2026-53067 Référence CVE CVE-2026-53068 https://www.cve.org/CVERecord?id=CVE-2026-53068 Référence CVE CVE-2026-53069 https://www.cve.org/CVERecord?id=CVE-2026-53069 Référence CVE CVE-2026-53070 https://www.cve.org/CVERecord?id=CVE-2026-53070 Référence CVE CVE-2026-53071 https://www.cve.org/CVERecord?id=CVE-2026-53071 Référence CVE CVE-2026-53072 https://www.cve.org/CVERecord?id=

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

u 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53050 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53056 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53058 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53059 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53060 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53061 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53062 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53063 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53064 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53066 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53068 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53071 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53072 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53073 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53074 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53075 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53076 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linu

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

d?id=CVE-2026-53049 Référence CVE CVE-2026-53050 https://www.cve.org/CVERecord?id=CVE-2026-53050 Référence CVE CVE-2026-53052 https://www.cve.org/CVERecord?id=CVE-2026-53052 Référence CVE CVE-2026-53056 https://www.cve.org/CVERecord?id=CVE-2026-53056 Référence CVE CVE-2026-53059 https://www.cve.org/CVERecord?id=CVE-2026-53059 Référence CVE CVE-2026-53060 https://www.cve.org/CVERecord?id=CVE-2026-53060 Référence CVE CVE-2026-53061 https://www.cve.org/CVERecord?id=CVE-2026-53061 Référence CVE CVE-2026-53062 https://www.cve.org/CVERecord?id=CVE-2026-53062 Référence CVE CVE-2026-53063 https://www.cve.org/CVERecord?id=CVE-2026-53063 Référence CVE CVE-2026-53064 https://www.cve.org/CVERecord?id=CVE-2026-53064 Référence CVE CVE-2026-53065 https://www.cve.org/CVERecord?id=CVE-2026-53065 Référence CVE CVE-2026-53066 https://www.cve.org/CVERecord?id=CVE-2026-53066 Référence CVE CVE-2026-53068 https://www.cve.org/CVERecord?id=CVE-2026-53068 Référence CVE CVE-2026-53069 https://www.cve.org/CVERecord?id=CVE-2026-53069 Référence CVE CVE-2026-53070 https://www.cve.org/CVERecord?id=CVE-2026-53070 Référence CVE CVE-2026-53071 https://www.cve.org/CVERecord?id=CVE-2026-53071 Référence CVE CVE-2026-53072 https://www.cve.org/CVERecord?id=CVE-2026-53072 Référence CVE CVE-2026-53073 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-024719LinuxのLinux KernelにおけるNULL ポインタデリファレンスに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。dm cache: パススルーモードにおける同時書き込み時のヌルポインタ参照の修正です。パススルーモードでは、dm-cacheがキャッシュエントリの無効化を開始し、同じキャッシュされたブロックへの同時書き込みによりbioプリズンセルロックが失敗した場合、mg-＞cellがNULLのままになることがあります。invalidate_complete()のエラー処理経路では、条件に関係なくセルのロック解除と解放を試みるため、NULLポインタ参照が発生します。以下はエラー例です。KASAN: null-ptr-deref 範囲 [0x0000000000000000-0x0000000000000007] CPU: 0 UID: 0 PID: 134 Comm: fio Not tainted 6.19.0-rc7 #3 PREEMPTRIP: 0010:dm_cell_unlock_v2+0x3f/0x210 ＜省略＞ 呼び出し履歴: invalidate_complete+0xef/0x430 map_bio+0x130f/0x1a10 cache_map+0x320/0x6b0 __map_bio+0x458/0x510 dm_submit_bio+0x40e/0x16d0 __submit_bio+0x419/0x870 ＜省略＞ 再現手順は以下の通りです。1. キャッシュデバイスの作成 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. 最初のデータブロックをキャッシュに昇格させる fio --filename=/dev/mapper/cache --name=populate --rw=write --bs=4k --direct=1 --size=64k 3. キャッシュをパススルーモードでリロードする 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. 最初のキャッシュブロックに対して同時書き込みを行う fio --filename=/dev/mapper/cache --name=test --rw=randwrite --bs=4k --randrepeat=0 --direct=1 --numjobs=2 --size=64k 修正内容は、mg-＞cellをロック解除しようとする前に、その有効性を確認することです。

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
Linux: < 4.12, 5.10.258 ≤ 5.10.*, 5.15.209 ≤ 5.15.*, 6.1.175 ≤ 6.1.*, 6.6.141 ≤ 6.6.*, 6.12.91 ≤ 6.12.*, 6.18.33 ≤ 6.18.*, 7.0.10 ≤ 7.0.*, 7.1 ≤ *
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 24 Jun 2026 · Last source change 24 Jun 2026, 16:30 UTC · CWE-476 · NULL Pointer Dereference

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
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-38932
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

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-38932↗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-53064 · cve.blacktree.nl