CVE-2026-46013 Vulnerability Analysis & Exploit Details

CVE-2026-46013
Vulnerability Scoring

5.5
/10
Significant Risk

Security assessments indicate that CVE-2026-46013 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-46013 Details

Status: Analyzed

Last updated: 🕒 16 Jun 2026, 15:24 UTC
Originally published on: 🕑 27 May 2026, 14:17 UTC

Time between publication and last update: 20 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVE-2026-46013 Vulnerability Summary

CVE-2026-46013: In the Linux kernel, the following vulnerability has been resolved: mm/memfd_luo: fix physical address conversion in put_folios cleanup In memfd_luo_retrieve_folios()'s put_folios cleanup path: 1. kho_restore_folio() expects a phys_addr_t (physical address) but receives a raw PFN (pfolio->pfn). This causes kho_restore_page() to check the wrong physical address (pfn << PAGE_SHIFT instead of the actual physical address). 2. This loop lacks the !pfolio->pfn check that exists in the main retrieval loop and memfd_luo_discard_folios(), which could incorrectly process sparse file holes where pfn=0. Fix by converting PFN to physical address with PFN_PHYS() and adding the !pfolio->pfn check, matching the pattern used elsewhere in this file. This issue was identified by the AI review. https://sashiko.dev/#/patchset/20260323110747.193569-1-duanchenghao@kylinos.cn

Assessing the Risk of CVE-2026-46013

Access Complexity Graph

The exploitability of CVE-2026-46013 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-46013

CVE-2026-46013 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-46013, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-46013, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2026-46013 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2026-46013 poses no threat to data integrity.
  • Availability: High
    CVE-2026-46013 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-46013 References

External References

CWE Common Weakness Enumeration

NVD-CWE-noinfo

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:6.19:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.12:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.12:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.13:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.13:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.14:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.14:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19:rc6:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19:rc6:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19:rc7:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19:rc7:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19:rc8:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19:rc8:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0.3:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-46013: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-48777 – FileBrowser Quantum is a free, self-hosted, web-based file manager. Versions prior to 1.3.2-stable, 1.4.0-beta and 1.4.1-beta are vulnerable to Pat...
  • CVE-2026-47750 – stable-diffusion.cpp is a pure C/C++ library for running diffusion model (Stable Diffusion, Flux, Wan, Qwen Image, Z-Image, and more) inference. In...
  • CVE-2026-47747 – stable-diffusion.cpp is a pure C/C++ library for running diffusion model (Stable Diffusion, Flux, Wan, Qwen Image, Z-Image, and more) inference. In...
  • CVE-2026-46448 – In OpenStack Nova before 33.0.2, the server create API does not strip certain hint data. The resulting instance has no Placement allocation.
  • CVE-2026-22313 – The device has a webserver that exposes a REST API authenticated with a token on the management network. By exploiting an OS command injection vuln...