CVE-2026-23097
Vulnerability Scoring
Analysis In Progress
CVE-2026-23097 Vulnerability Analysis & Exploit Details
CVE-2026-23097
Attack Complexity Details
-
Attack Complexity:
Attack Complexity Analysis In Progress
-
Attack Vector:
Attack Vector Under Analysis
-
Privileges Required:
None
No authentication is required for exploitation.
-
Scope:
Impact is confined to the initially vulnerable component.
-
User Interaction:
None
No user interaction is necessary for exploitation.
CVE-2026-23097 Details
Status: Awaiting Analysis
Last updated: 🕔 06 Feb 2026, 17:16 UTC
Originally published on: 🕔 04 Feb 2026, 17:16 UTC
Time between publication and last update: 2 days
CVSS Release:
CVE-2026-23097 Vulnerability Summary
CVE-2026-23097: In the Linux kernel, the following vulnerability has been resolved: migrate: correct lock ordering for hugetlb file folios Syzbot has found a deadlock (analyzed by Lance Yang): 1) Task (5749): Holds folio_lock, then tries to acquire i_mmap_rwsem(read lock). 2) Task (5754): Holds i_mmap_rwsem(write lock), then tries to acquire folio_lock. migrate_pages() -> migrate_hugetlbs() -> unmap_and_move_huge_page() <- Takes folio_lock! -> remove_migration_ptes() -> __rmap_walk_file() -> i_mmap_lock_read() <- Waits for i_mmap_rwsem(read lock)! hugetlbfs_fallocate() -> hugetlbfs_punch_hole() <- Takes i_mmap_rwsem(write lock)! -> hugetlbfs_zero_partial_page() -> filemap_lock_hugetlb_folio() -> filemap_lock_folio() -> __filemap_get_folio <- Waits for folio_lock! The migration path is the one taking locks in the wrong order according to the documentation at the top of mm/rmap.c. So expand the scope of the existing i_mmap_lock to cover the calls to remove_migration_ptes() too. This is (mostly) how it used to be after commit c0d0381ade79. That was removed by 336bf30eb765 for both file & anon hugetlb pages when it should only have been removed for anon hugetlb pages.
Assessing the Risk of CVE-2026-23097
Access Complexity Graph
The exploitability of CVE-2026-23097 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-23097
No exploitability data is available for CVE-2026-23097.
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-23097, 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-23097, 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-23097 does not compromise confidentiality.
-
Integrity:
None
CVE-2026-23097 does not impact data integrity.
-
Availability:
None
CVE-2026-23097 does not affect system availability.
CVE-2026-23097 References
External References
- https://git.kernel.org/stable/c/1b68efce6dd483d22f50d0d3800c4cfda14b1305
- https://git.kernel.org/stable/c/526394af4e8ade89cacd1a9ce2b97712712fcc34
- https://git.kernel.org/stable/c/5edb9854f8df5428b40990a1c7d60507da5bd330
- https://git.kernel.org/stable/c/ad97b9a55246eb940a26ac977f80892a395cabf9
- https://git.kernel.org/stable/c/b75070823b89009f5123fd0e05a8e0c3d39937c1
- https://git.kernel.org/stable/c/b7880cb166ab62c2409046b2347261abf701530e
- https://git.kernel.org/stable/c/e7396d23f9d5739f56cf9ab430c3a169f5508394
CWE Common Weakness Enumeration
Unknown
Protect Your Infrastructure against CVE-2026-23097: 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-3288 – A security issue was discovered in ingress-nginx where the `nginx.ingress.kubernetes.io/rewrite-target` Ingress annotation can be used to inject co...
- CVE-2026-31816 – Budibase is a low code platform for creating internal tools, workflows, and admin panels. In 3.31.4 and earlier, the Budibase server's authorized()...
- CVE-2026-30240 – Budibase is a low code platform for creating internal tools, workflows, and admin panels. In 3.31.5 and earlier, a path traversal vulnerability in ...
- CVE-2026-25960 – vLLM is an inference and serving engine for large language models (LLMs). The SSRF protection fix for CVE-2026-24779 add in 0.15.1 can be bypassed ...
- CVE-2026-25737 – Budibase is a low code platform for creating internal tools, workflows, and admin panels. In 3.24.0 and earlier, an arbitrary file upload vulnerabi...