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

dma-mapping: move dma_map_resource() sanity check into debug code

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 89 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 19 Jul 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 89 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.

17 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 13 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 · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).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.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-aws-6.14Affected, 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-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-azure-fde-6.14Affected, 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-nvidia-6.14Affected, 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-gcp-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-hwe-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-lowlatency-hwe-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-nvidia-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-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-oracle-6.14Affected, 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
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-64149 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: dma-mapping: move dma_map_resource() sanity check into debug code
76 known affected

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

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the Linux kernel's Direct Memory Access (DMA) mapping subsystem. On ARM64 systems configured with SPARSEMEM (a memory management model), the dma_map_resource() function could incorrectly identify valid memory-mapped input/output (MMIO) addresses as random access memory (RAM). This false identification would trigger a warning and cause the DMA mapping operation to fail, leading to system instability or a denial of service.
Remediation
Fix deferred
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-45834

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 89 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: dma-mapping: move dma_map_resource() sanity check into debug code dma_map_resource() uses pfn_valid() to ensure the range is not RAM. However, pfn_valid() only checks for availability of the memory map for a PFN but it does not ensure that the PFN is actually backed by RAM. On ARM64 with SPARSEMEM (128MB section granularity), MMIO addresses that share a section with RAM will falsely trigger the WARN_ON_ONCE and cause dma_map_resource() to return DMA_MAPPING_ERROR. This causes a WARNING on Raspberry Pi 4 during spi_bcm2835 probe because the SPI FIFO register (0xfe204004) falls in the same sparsemem section as the end of RAM (0xf8000000-0xfbffffff), both in section 31 (0xf8000000-0xffffffff). Move the sanity check from dma_map_resource() into debug_dma_map_phys() and replace the unreliable pfn_valid() with pfn_valid() && !PageReserved(), which correctly identifies actual usable RAM without false positives for MMIO regions that happen to have struct pages. Since dma_map_resource() is dma_map_phys(DMA_ATTR_MMIO), the check applies equally to both APIs. Any non-reserved page represents kernel memory to a sufficient degree that using DMA_ATTR_MMIO on it is almost certainly wrong and risks breaking coherency on non-coherent platforms. ZONE_DEVICE pages used for PCI P2P DMA (MEMORY_DEVICE_PCI_P2PDMA) have PageReserved set, so they will not trigger a false positive. The check no longer blocks the mapping and uses err_printk() to integrate with dma-debug filtering.

What

In the Linux kernel, the following vulnerability has been resolved: dma-mapping: move dma_map_resource() sanity check into debug code dma_map_resource() uses pfn_valid() to ensure the range is not RAM. However, pfn_valid() only checks for availability of the memory map for a PFN but it does not ensure that the PFN is actually backed by RAM. On ARM64 with SPARSEMEM (128MB section granularity), MMIO addresses that share a section with RAM will falsely trigger the WARN_ON_ONCE and cause dma_map_resource() to return DMA_MAPPING_ERROR. This causes a WARNING on Raspberry Pi 4 during spi_bcm2835 probe because the SPI FIFO register (0xfe204004) falls in the same sparsemem section as the end of RAM (0xf8000000-0xfbffffff), both in section 31 (0xf8000000-0xffffffff). Move the sanity check from dma_map_resource() into debug_dma_map_phys() and replace the unreliable pfn_valid() with pfn_valid() && !PageReserved(), which correctly identifies actual usable RAM without false positives for MMIO regions that happen to have struct pages. Since dma_map_resource() is dma_map_phys(DMA_ATTR_MMIO), the check applies equally to both APIs. Any non-reserved page represents kernel memory to a sufficient degree that using DMA_ATTR_MMIO on it is almost certainly wrong and risks breaking coherency on non-coherent platforms. ZONE_DEVICE pages used for PCI P2P DMA (MEMORY_DEVICE_PCI_P2PDMA) have PageReserved set, so they will not trigger a false positive. The check no longer blocks the mapping and uses err_printk() to integrate with dma-debug filtering.

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: dma-mapping: move dma_map_resource() sanity check into debug code dma_map_resource() uses pfn_valid() to ensure the range is not RAM. However, pfn_valid() only checks for availability of the memory map for a PFN but it does not ensure that the PFN is actually backed by RAM. On ARM64 with SPARSEMEM (128MB section granularity), MMIO addresses that share a section with RAM will falsely trigger the WARN_ON_ONCE and cause dma_map_resource() to return DMA_MAPPING_ERROR. This causes a WARNING on Raspberry Pi 4 during spi_bcm2835 probe because the SPI FIFO register (0xfe204004) falls in the same sparsemem section as the end of RAM (0xf8000000-0xfbffffff), both in section 31 (0xf8000000-0xffffffff). Move the sanity check from dma_map_resource() into debug_dma_map_phys() and replace the unreliable pfn_valid() with pfn_valid() && !PageReserved(), which correctly identifies actual usable RAM without false positives for MMIO regions that happen to have struct pages. Since dma_map_resource() is dma_map_phys(DMA_ATTR_MMIO), the check applies equally to both APIs. Any non-reserved page represents kernel memory to a sufficient degree that using DMA_ATTR_MMIO on it is almost certainly wrong and risks breaking coherency on non-coherent platforms. ZONE_DEVICE pages used for PCI P2P DMA (MEMORY_DEVICE_PCI_P2PDMA) have PageReserved set, so they will not trigger a false positive. The check no longer blocks the mapping and uses err_printk() to integrate with dma-debug filtering.

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: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.
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-2403Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260722Security Bulletin 22 Jul 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 Jul 2026, published on 22 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-64140 Référence CVE CVE-2026-64141 https://www.cve.org/CVERecord?id=CVE-2026-64141 Référence CVE CVE-2026-64142 https://www.cve.org/CVERecord?id=CVE-2026-64142 Référence CVE CVE-2026-64143 https://www.cve.org/CVERecord?id=CVE-2026-64143 Référence CVE CVE-2026-64144 https://www.cve.org/CVERecord?id=CVE-2026-64144 Référence CVE CVE-2026-64145 https://www.cve.org/CVERecord?id=CVE-2026-64145 Référence CVE CVE-2026-64146 https://www.cve.org/CVERecord?id=CVE-2026-64146 Référence CVE CVE-2026-64147 https://www.cve.org/CVERecord?id=CVE-2026-64147 Référence CVE CVE-2026-64148 https://www.cve.org/CVERecord?id=CVE-2026-64148 Référence CVE CVE-2026-64149 https://www.cve.org/CVERecord?id=CVE-2026-64149 Référence CVE CVE-2026-64150 https://www.cve.org/CVERecord?id=CVE-2026-64150 Référence CVE CVE-2026-64151 https://www.cve.org/CVERecord?id=CVE-2026-64151 Référence CVE CVE-2026-64152 https://www.cve.org/CVERecord?id=CVE-2026-64152 Référence CVE CVE-2026-64153 https://www.cve.org/CVERecord?id=CVE-2026-64153 Référence CVE CVE-2026-64154 https://www.cve.org/CVERecord?id=CVE-2026-64154 Référence CVE CVE-2026-64155 https://www.cve.org/CVERecord?id=CVE-2026-64155 Référence CVE CVE-2026-64156 https://www.cve.org/CVERecord?id=CVE-2026-64156 Référence CVE CVE-2026-64157 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-64140 Référence CVE CVE-2026-64141 https://www.cve.org/CVERecord?id=CVE-2026-64141 Référence CVE CVE-2026-64142 https://www.cve.org/CVERecord?id=CVE-2026-64142 Référence CVE CVE-2026-64143 https://www.cve.org/CVERecord?id=CVE-2026-64143 Référence CVE CVE-2026-64144 https://www.cve.org/CVERecord?id=CVE-2026-64144 Référence CVE CVE-2026-64145 https://www.cve.org/CVERecord?id=CVE-2026-64145 Référence CVE CVE-2026-64146 https://www.cve.org/CVERecord?id=CVE-2026-64146 Référence CVE CVE-2026-64147 https://www.cve.org/CVERecord?id=CVE-2026-64147 Référence CVE CVE-2026-64148 https://www.cve.org/CVERecord?id=CVE-2026-64148 Référence CVE CVE-2026-64149 https://www.cve.org/CVERecord?id=CVE-2026-64149 Référence CVE CVE-2026-64150 https://www.cve.org/CVERecord?id=CVE-2026-64150 Référence CVE CVE-2026-64151 https://www.cve.org/CVERecord?id=CVE-2026-64151 Référence CVE CVE-2026-64152 https://www.cve.org/CVERecord?id=CVE-2026-64152 Référence CVE CVE-2026-64153 https://www.cve.org/CVERecord?id=CVE-2026-64153 Référence CVE CVE-2026-64154 https://www.cve.org/CVERecord?id=CVE-2026-64154 Référence CVE CVE-2026-64155 https://www.cve.org/CVERecord?id=CVE-2026-64155 Référence CVE CVE-2026-64156 https://www.cve.org/CVERecord?id=CVE-2026-64156 Référence CVE CVE-2026-64157 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-64140 Référence CVE CVE-2026-64141 https://www.cve.org/CVERecord?id=CVE-2026-64141 Référence CVE CVE-2026-64142 https://www.cve.org/CVERecord?id=CVE-2026-64142 Référence CVE CVE-2026-64143 https://www.cve.org/CVERecord?id=CVE-2026-64143 Référence CVE CVE-2026-64144 https://www.cve.org/CVERecord?id=CVE-2026-64144 Référence CVE CVE-2026-64145 https://www.cve.org/CVERecord?id=CVE-2026-64145 Référence CVE CVE-2026-64146 https://www.cve.org/CVERecord?id=CVE-2026-64146 Référence CVE CVE-2026-64147 https://www.cve.org/CVERecord?id=CVE-2026-64147 Référence CVE CVE-2026-64148 https://www.cve.org/CVERecord?id=CVE-2026-64148 Référence CVE CVE-2026-64149 https://www.cve.org/CVERecord?id=CVE-2026-64149 Référence CVE CVE-2026-64150 https://www.cve.org/CVERecord?id=CVE-2026-64150 Référence CVE CVE-2026-64151 https://www.cve.org/CVERecord?id=CVE-2026-64151 Référence CVE CVE-2026-64152 https://www.cve.org/CVERecord?id=CVE-2026-64152 Référence CVE CVE-2026-64153 https://www.cve.org/CVERecord?id=CVE-2026-64153 Référence CVE CVE-2026-64154 https://www.cve.org/CVERecord?id=CVE-2026-64154 Référence CVE CVE-2026-64155 https://www.cve.org/CVERecord?id=CVE-2026-64155 Référence CVE CVE-2026-64156 https://www.cve.org/CVERecord?id=CVE-2026-64156 Référence CVE CVE-2026-64157 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-64140 Référence CVE CVE-2026-64141 https://www.cve.org/CVERecord?id=CVE-2026-64141 Référence CVE CVE-2026-64142 https://www.cve.org/CVERecord?id=CVE-2026-64142 Référence CVE CVE-2026-64143 https://www.cve.org/CVERecord?id=CVE-2026-64143 Référence CVE CVE-2026-64144 https://www.cve.org/CVERecord?id=CVE-2026-64144 Référence CVE CVE-2026-64145 https://www.cve.org/CVERecord?id=CVE-2026-64145 Référence CVE CVE-2026-64146 https://www.cve.org/CVERecord?id=CVE-2026-64146 Référence CVE CVE-2026-64147 https://www.cve.org/CVERecord?id=CVE-2026-64147 Référence CVE CVE-2026-64148 https://www.cve.org/CVERecord?id=CVE-2026-64148 Référence CVE CVE-2026-64149 https://www.cve.org/CVERecord?id=CVE-2026-64149 Référence CVE CVE-2026-64150 https://www.cve.org/CVERecord?id=CVE-2026-64150 Référence CVE CVE-2026-64151 https://www.cve.org/CVERecord?id=CVE-2026-64151 Référence CVE CVE-2026-64152 https://www.cve.org/CVERecord?id=CVE-2026-64152 Référence CVE CVE-2026-64153 https://www.cve.org/CVERecord?id=CVE-2026-64153 Référence CVE CVE-2026-64154 https://www.cve.org/CVERecord?id=CVE-2026-64154 Référence CVE CVE-2026-64155 https://www.cve.org/CVERecord?id=CVE-2026-64155 Référence CVE CVE-2026-64156 https://www.cve.org/CVERecord?id=CVE-2026-64156 Référence CVE CVE-2026-64157 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-64140 Référence CVE CVE-2026-64141 https://www.cve.org/CVERecord?id=CVE-2026-64141 Référence CVE CVE-2026-64142 https://www.cve.org/CVERecord?id=CVE-2026-64142 Référence CVE CVE-2026-64143 https://www.cve.org/CVERecord?id=CVE-2026-64143 Référence CVE CVE-2026-64144 https://www.cve.org/CVERecord?id=CVE-2026-64144 Référence CVE CVE-2026-64145 https://www.cve.org/CVERecord?id=CVE-2026-64145 Référence CVE CVE-2026-64146 https://www.cve.org/CVERecord?id=CVE-2026-64146 Référence CVE CVE-2026-64147 https://www.cve.org/CVERecord?id=CVE-2026-64147 Référence CVE CVE-2026-64148 https://www.cve.org/CVERecord?id=CVE-2026-64148 Référence CVE CVE-2026-64149 https://www.cve.org/CVERecord?id=CVE-2026-64149 Référence CVE CVE-2026-64150 https://www.cve.org/CVERecord?id=CVE-2026-64150 Référence CVE CVE-2026-64151 https://www.cve.org/CVERecord?id=CVE-2026-64151 Référence CVE CVE-2026-64152 https://www.cve.org/CVERecord?id=CVE-2026-64152 Référence CVE CVE-2026-64153 https://www.cve.org/CVERecord?id=CVE-2026-64153 Référence CVE CVE-2026-64154 https://www.cve.org/CVERecord?id=CVE-2026-64154 Référence CVE CVE-2026-64155 https://www.cve.org/CVERecord?id=CVE-2026-64155 Référence CVE CVE-2026-64156 https://www.cve.org/CVERecord?id=CVE-2026-64156 Référence CVE CVE-2026-64157 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-64140 Référence CVE CVE-2026-64141 https://www.cve.org/CVERecord?id=CVE-2026-64141 Référence CVE CVE-2026-64142 https://www.cve.org/CVERecord?id=CVE-2026-64142 Référence CVE CVE-2026-64143 https://www.cve.org/CVERecord?id=CVE-2026-64143 Référence CVE CVE-2026-64144 https://www.cve.org/CVERecord?id=CVE-2026-64144 Référence CVE CVE-2026-64145 https://www.cve.org/CVERecord?id=CVE-2026-64145 Référence CVE CVE-2026-64146 https://www.cve.org/CVERecord?id=CVE-2026-64146 Référence CVE CVE-2026-64147 https://www.cve.org/CVERecord?id=CVE-2026-64147 Référence CVE CVE-2026-64148 https://www.cve.org/CVERecord?id=CVE-2026-64148 Référence CVE CVE-2026-64149 https://www.cve.org/CVERecord?id=CVE-2026-64149 Référence CVE CVE-2026-64150 https://www.cve.org/CVERecord?id=CVE-2026-64150 Référence CVE CVE-2026-64151 https://www.cve.org/CVERecord?id=CVE-2026-64151 Référence CVE CVE-2026-64152 https://www.cve.org/CVERecord?id=CVE-2026-64152 Référence CVE CVE-2026-64153 https://www.cve.org/CVERecord?id=CVE-2026-64153 Référence CVE CVE-2026-64154 https://www.cve.org/CVERecord?id=CVE-2026-64154 Référence CVE CVE-2026-64155 https://www.cve.org/CVERecord?id=CVE-2026-64155 Référence CVE CVE-2026-64156 https://www.cve.org/CVERecord?id=CVE-2026-64156 Référence CVE CVE-2026-64157 https://www.cve.org/CVERecord?id=

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

Linuxカーネルにおいて、以下の脆弱性が修正されました。dma-mappingのdma_map_resource()関数の整合性チェックをデバッグコードに移動しました。dma_map_resource()はpfn_valid()を使用して、範囲がRAMでないことを確認しています。しかし、pfn_valid()はPFNに対応するメモリマップの有無のみをチェックしており、PFNが実際にRAMであることを保証しません。ARM64のSPARSEMEM（128MBセクション粒度）環境では、RAMと同じセクションを共有するMMIOアドレスが誤ってWARN_ON_ONCEを発生させ、その結果dma_map_resource()がDMA_MAPPING_ERRORを返す問題がありました。この問題により、Raspberry Pi 4のspi_bcm2835のプローブ時にWARNINGが発生します。これは、SPI FIFOレジスタ(0xfe204004)がRAMの末端領域(0xf8000000-0xfbffffff)と同じスパースメムセクション（31セクション：0xf8000000-0xffffffff）に存在するためです。dma_map_resource()の整合性チェックはdebug_dma_map_phys()へ移動し、信頼性の低いpfn_valid()をpfn_valid()かつ!PageReserved()に置き換えました。これにより、実際に使用可能なRAMを正しく識別し、構造体pageを持つMMIO領域での誤検出を防ぎます。dma_map_resource()はdma_map_phys(DMA_ATTR_MMIO)と同様の動作をするため、両APIに同じチェックが適用される仕組みです。予約されていないページはカーネルメモリとみなされるため、それにDMA_ATTR_MMIOを使用するのはほぼ間違いであり、非コヒーレントプラットフォームでのコヒーレンシー破壊のリスクがあります。PCIのP2P DMA（MEMORY_DEVICE_PCI_P2PDMA）で使用されるZONE_DEVICEページにはPageReservedがセットされているため、誤検出の対象にはなりません。このチェックはマッピングをブロックせず、err_printk()を用いてdma-debugのフィルタリング機能へ統合されています。

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: < 6.18, 6.18.34 ≤ 6.18.*, 7.0.11 ≤ 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 19 Jul 2026 · Last source change 19 Jul 2026, 15:40 UTC · CWE not yet assigned

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-45834
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
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 ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: added patch: git.kernel.org/004a777879ff629f6e0ca3d09ad09fa3452bcc4d; added patch: git.kernel.org/181e67bc11c5ec5b87c6c512c2078752b23ca8d4; 1 further additions.
    Before
    remediation: git.kernel.org/181e67bc11c5ec5b87c6c512c2078752b23ca8d4
    After
    patch: git.kernel.org/004a777879ff629f6e0ca3d09ad09fa3452bcc4d · patch: git.kernel.org/181e67bc11c5ec5b87c6c512c2078752b23ca8d4 · patch: git.kernel.org/af0c3f05866237f7592219bfe05387bc3bfc99b5 · 1 more references
    git.kernel.org ↗
  2. SeveritySeverity changed from Unknown to Medium.
    Before
    Unknown
    After
    Medium
    NIST NVD ↗
  3. CVSS scoreCVSS score changed from not recorded to 5.5 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).
    Before
    not recorded
    After
    5.5 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
    NIST NVD ↗
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-45834↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor 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-64149 · cve.blacktree.nl