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

PCI/P2PDMA: Release per-CPU pgmap ref when vm_insert_page() fails

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 27 May 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.85-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.18.14-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.18.14-1Debian Security Tracker ↗Source updated 5 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-45880 · CSAF 2.0 · revision 10 · interimSUSE Product Security TeamCVE-2026-45880
47 known affected

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

  • cluster-md-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • dlm-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • gfs2-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • kernel-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • kernel-devel as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • kernel-macros as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • kernel-source as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • ocfs2-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • reiserfs-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • cluster-md-kmp-default as component of SUSE Linux Enterprise Server 15 SP6
  • dlm-kmp-default as component of SUSE Linux Enterprise Server 15 SP6
Summary
In the Linux kernel, the following vulnerability has been resolved: PCI/P2PDMA: Release per-CPU pgmap ref when vm_insert_page() fails When vm_insert_page() fails in p2pmem_alloc_mmap(), p2pmem_alloc_mmap() doesn't invoke percpu_ref_put() to free the per-CPU ref of pgmap acquired after gen_pool_alloc_owner(), and memunmap_pages() will hang forever when trying to remove the PCI device. Fix it by adding the missed percpu_ref_put().
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-32346

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: PCI/P2PDMA: Release per-CPU pgmap ref when vm_insert_page() fails When vm_insert_page() fails in p2pmem_alloc_mmap(), p2pmem_alloc_mmap() doesn't invoke percpu_ref_put() to free the per-CPU ref of pgmap acquired after gen_pool_alloc_owner(), and memunmap_pages() will hang forever when trying to remove the PCI device. Fix it by adding the missed percpu_ref_put().

What

In the Linux kernel, the following vulnerability has been resolved: PCI/P2PDMA: Release per-CPU pgmap ref when vm_insert_page() fails When vm_insert_page() fails in p2pmem_alloc_mmap(), p2pmem_alloc_mmap() doesn't invoke percpu_ref_put() to free the per-CPU ref of pgmap acquired after gen_pool_alloc_owner(), and memunmap_pages() will hang forever when trying to remove the PCI device. Fix it by adding the missed percpu_ref_put().

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: PCI/P2PDMA: Release per-CPU pgmap ref when vm_insert_page() fails When vm_insert_page() fails in p2pmem_alloc_mmap(), p2pmem_alloc_mmap() doesn't invoke percpu_ref_put() to free the per-CPU ref of pgmap acquired after gen_pool_alloc_owner(), and memunmap_pages() will hang forever when trying to remove the PCI device. Fix it by adding the missed percpu_ref_put().

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-1700Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260603Security Bulletin 3 Jun 2026

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

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

d?id=CVE-2026-45869 Référence CVE CVE-2026-45871 https://www.cve.org/CVERecord?id=CVE-2026-45871 Référence CVE CVE-2026-45872 https://www.cve.org/CVERecord?id=CVE-2026-45872 Référence CVE CVE-2026-45873 https://www.cve.org/CVERecord?id=CVE-2026-45873 Référence CVE CVE-2026-45874 https://www.cve.org/CVERecord?id=CVE-2026-45874 Référence CVE CVE-2026-45875 https://www.cve.org/CVERecord?id=CVE-2026-45875 Référence CVE CVE-2026-45877 https://www.cve.org/CVERecord?id=CVE-2026-45877 Référence CVE CVE-2026-45878 https://www.cve.org/CVERecord?id=CVE-2026-45878 Référence CVE CVE-2026-45879 https://www.cve.org/CVERecord?id=CVE-2026-45879 Référence CVE CVE-2026-45880 https://www.cve.org/CVERecord?id=CVE-2026-45880 Référence CVE CVE-2026-45881 https://www.cve.org/CVERecord?id=CVE-2026-45881 Référence CVE CVE-2026-45882 https://www.cve.org/CVERecord?id=CVE-2026-45882 Référence CVE CVE-2026-45883 https://www.cve.org/CVERecord?id=CVE-2026-45883 Référence CVE CVE-2026-45885 https://www.cve.org/CVERecord?id=CVE-2026-45885 Référence CVE CVE-2026-45895 https://www.cve.org/CVERecord?id=CVE-2026-45895 Référence CVE CVE-2026-45900 https://www.cve.org/CVERecord?id=CVE-2026-45900 Référence CVE CVE-2026-45902 https://www.cve.org/CVERecord?id=CVE-2026-45902 Référence CVE CVE-2026-45904 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-45869 Référence CVE CVE-2026-45870 https://www.cve.org/CVERecord?id=CVE-2026-45870 Référence CVE CVE-2026-45871 https://www.cve.org/CVERecord?id=CVE-2026-45871 Référence CVE CVE-2026-45872 https://www.cve.org/CVERecord?id=CVE-2026-45872 Référence CVE CVE-2026-45873 https://www.cve.org/CVERecord?id=CVE-2026-45873 Référence CVE CVE-2026-45875 https://www.cve.org/CVERecord?id=CVE-2026-45875 Référence CVE CVE-2026-45877 https://www.cve.org/CVERecord?id=CVE-2026-45877 Référence CVE CVE-2026-45878 https://www.cve.org/CVERecord?id=CVE-2026-45878 Référence CVE CVE-2026-45879 https://www.cve.org/CVERecord?id=CVE-2026-45879 Référence CVE CVE-2026-45880 https://www.cve.org/CVERecord?id=CVE-2026-45880 Référence CVE CVE-2026-45881 https://www.cve.org/CVERecord?id=CVE-2026-45881 Référence CVE CVE-2026-45882 https://www.cve.org/CVERecord?id=CVE-2026-45882 Référence CVE CVE-2026-45883 https://www.cve.org/CVERecord?id=CVE-2026-45883 Référence CVE CVE-2026-45884 https://www.cve.org/CVERecord?id=CVE-2026-45884 Référence CVE CVE-2026-45885 https://www.cve.org/CVERecord?id=CVE-2026-45885 Référence CVE CVE-2026-45886 https://www.cve.org/CVERecord?id=CVE-2026-45886 Référence CVE CVE-2026-45890 https://www.cve.org/CVERecord?id=CVE-2026-45890 Référence CVE CVE-2026-45891 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-45862 Référence CVE CVE-2026-45867 https://www.cve.org/CVERecord?id=CVE-2026-45867 Référence CVE CVE-2026-45868 https://www.cve.org/CVERecord?id=CVE-2026-45868 Référence CVE CVE-2026-45869 https://www.cve.org/CVERecord?id=CVE-2026-45869 Référence CVE CVE-2026-45870 https://www.cve.org/CVERecord?id=CVE-2026-45870 Référence CVE CVE-2026-45871 https://www.cve.org/CVERecord?id=CVE-2026-45871 Référence CVE CVE-2026-45875 https://www.cve.org/CVERecord?id=CVE-2026-45875 Référence CVE CVE-2026-45877 https://www.cve.org/CVERecord?id=CVE-2026-45877 Référence CVE CVE-2026-45879 https://www.cve.org/CVERecord?id=CVE-2026-45879 Référence CVE CVE-2026-45880 https://www.cve.org/CVERecord?id=CVE-2026-45880 Référence CVE CVE-2026-45881 https://www.cve.org/CVERecord?id=CVE-2026-45881 Référence CVE CVE-2026-45883 https://www.cve.org/CVERecord?id=CVE-2026-45883 Référence CVE CVE-2026-45884 https://www.cve.org/CVERecord?id=CVE-2026-45884 Référence CVE CVE-2026-45885 https://www.cve.org/CVERecord?id=CVE-2026-45885 Référence CVE CVE-2026-45888 https://www.cve.org/CVERecord?id=CVE-2026-45888 Référence CVE CVE-2026-45891 https://www.cve.org/CVERecord?id=CVE-2026-45891 Référence CVE CVE-2026-45894 https://www.cve.org/CVERecord?id=CVE-2026-45894 Référence CVE CVE-2026-45899 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-45869 Référence CVE CVE-2026-45870 https://www.cve.org/CVERecord?id=CVE-2026-45870 Référence CVE CVE-2026-45871 https://www.cve.org/CVERecord?id=CVE-2026-45871 Référence CVE CVE-2026-45872 https://www.cve.org/CVERecord?id=CVE-2026-45872 Référence CVE CVE-2026-45873 https://www.cve.org/CVERecord?id=CVE-2026-45873 Référence CVE CVE-2026-45875 https://www.cve.org/CVERecord?id=CVE-2026-45875 Référence CVE CVE-2026-45877 https://www.cve.org/CVERecord?id=CVE-2026-45877 Référence CVE CVE-2026-45878 https://www.cve.org/CVERecord?id=CVE-2026-45878 Référence CVE CVE-2026-45879 https://www.cve.org/CVERecord?id=CVE-2026-45879 Référence CVE CVE-2026-45880 https://www.cve.org/CVERecord?id=CVE-2026-45880 Référence CVE CVE-2026-45881 https://www.cve.org/CVERecord?id=CVE-2026-45881 Référence CVE CVE-2026-45882 https://www.cve.org/CVERecord?id=CVE-2026-45882 Référence CVE CVE-2026-45883 https://www.cve.org/CVERecord?id=CVE-2026-45883 Référence CVE CVE-2026-45884 https://www.cve.org/CVERecord?id=CVE-2026-45884 Référence CVE CVE-2026-45885 https://www.cve.org/CVERecord?id=CVE-2026-45885 Référence CVE CVE-2026-45886 https://www.cve.org/CVERecord?id=CVE-2026-45886 Référence CVE CVE-2026-45890 https://www.cve.org/CVERecord?id=CVE-2026-45890 Référence CVE CVE-2026-45891 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-45869 Référence CVE CVE-2026-45870 https://www.cve.org/CVERecord?id=CVE-2026-45870 Référence CVE CVE-2026-45871 https://www.cve.org/CVERecord?id=CVE-2026-45871 Référence CVE CVE-2026-45872 https://www.cve.org/CVERecord?id=CVE-2026-45872 Référence CVE CVE-2026-45873 https://www.cve.org/CVERecord?id=CVE-2026-45873 Référence CVE CVE-2026-45875 https://www.cve.org/CVERecord?id=CVE-2026-45875 Référence CVE CVE-2026-45877 https://www.cve.org/CVERecord?id=CVE-2026-45877 Référence CVE CVE-2026-45878 https://www.cve.org/CVERecord?id=CVE-2026-45878 Référence CVE CVE-2026-45879 https://www.cve.org/CVERecord?id=CVE-2026-45879 Référence CVE CVE-2026-45880 https://www.cve.org/CVERecord?id=CVE-2026-45880 Référence CVE CVE-2026-45881 https://www.cve.org/CVERecord?id=CVE-2026-45881 Référence CVE CVE-2026-45882 https://www.cve.org/CVERecord?id=CVE-2026-45882 Référence CVE CVE-2026-45883 https://www.cve.org/CVERecord?id=CVE-2026-45883 Référence CVE CVE-2026-45884 https://www.cve.org/CVERecord?id=CVE-2026-45884 Référence CVE CVE-2026-45885 https://www.cve.org/CVERecord?id=CVE-2026-45885 Référence CVE CVE-2026-45886 https://www.cve.org/CVERecord?id=CVE-2026-45886 Référence CVE CVE-2026-45890 https://www.cve.org/CVERecord?id=CVE-2026-45890 Référence CVE CVE-2026-45891 https://www.cve.org/CVERecord?id=

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

Linuxカーネルにおいて、以下の脆弱性が修正されました。PCI/P2PDMAにおいて、vm_insert_page()が失敗した場合にper-CPUのpgmap参照を適切に解放します。p2pmem_alloc_mmap()内でvm_insert_page()が失敗すると、p2pmem_alloc_mmap()はgen_pool_alloc_owner()で取得したpgmapのper-CPU参照を解放するためのpercpu_ref_put()を呼び出しませんでした。その結果、memunmap_pages()がPCIデバイスの削除時に永久にハングする問題が発生していました。この問題は、欠落していたpercpu_ref_put()を追加することで修正されました。

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.2, 6.6.128 ≤ 6.6.*, 6.12.75 ≤ 6.12.*, 6.18.14 ≤ 6.18.*, 6.19.4 ≤ 6.19.*, 7.0 ≤ *
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 27 May 2026 · Last source change 27 May 2026, 12:16 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-32346
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-32346↗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-45880 · cve.blacktree.nl