CVE-2025-22045
Vulnerability Scoring
Analysis In Progress
CVE-2025-22045 Vulnerability Analysis & Exploit Details
CVE-2025-22045
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-2025-22045 Details
Status: Awaiting Analysis
Last updated: 🕗 17 Apr 2025, 20:22 UTC
Originally published on: 🕒 16 Apr 2025, 15:15 UTC
Time between publication and last update: 1 days
CVSS Release:
CVE-2025-22045 Vulnerability Summary
CVE-2025-22045: In the Linux kernel, the following vulnerability has been resolved: x86/mm: Fix flush_tlb_range() when used for zapping normal PMDs On the following path, flush_tlb_range() can be used for zapping normal PMD entries (PMD entries that point to page tables) together with the PTE entries in the pointed-to page table: collapse_pte_mapped_thp pmdp_collapse_flush flush_tlb_range The arm64 version of flush_tlb_range() has a comment describing that it can be used for page table removal, and does not use any last-level invalidation optimizations. Fix the X86 version by making it behave the same way. Currently, X86 only uses this information for the following two purposes, which I think means the issue doesn't have much impact: - In native_flush_tlb_multi() for checking if lazy TLB CPUs need to be IPI'd to avoid issues with speculative page table walks. - In Hyper-V TLB paravirtualization, again for lazy TLB stuff. The patch "x86/mm: only invalidate final translations with INVLPGB" which is currently under review (see <https://lore.kernel.org/all/20241230175550.4046587-13-riel@surriel.com/>) would probably be making the impact of this a lot worse.
Assessing the Risk of CVE-2025-22045
Access Complexity Graph
The exploitability of CVE-2025-22045 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-2025-22045
No exploitability data is available for CVE-2025-22045.
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-2025-22045, 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-2025-22045, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.
-
Confidentiality:
None
CVE-2025-22045 does not compromise confidentiality.
-
Integrity:
None
CVE-2025-22045 does not impact data integrity.
-
Availability:
None
CVE-2025-22045 does not affect system availability.
CVE-2025-22045 References
External References
- https://git.kernel.org/stable/c/0708fd6bd8161871bfbadced2ca4319b84ab44fe
- https://git.kernel.org/stable/c/0a8f806ea6b5dd64b3d1f05ff774817d5f7ddbd1
- https://git.kernel.org/stable/c/320ac1af4c0bdb92c864dc9250d1329234820edf
- https://git.kernel.org/stable/c/3ef938c3503563bfc2ac15083557f880d29c2e64
- https://git.kernel.org/stable/c/556d446068f90981e5d71ca686bdaccdd545d491
- https://git.kernel.org/stable/c/618d5612ecb7bfc1c85342daafeb2b47e29e77a3
- https://git.kernel.org/stable/c/7085895c59e4057ffae17f58990ccb630087d0d2
- https://git.kernel.org/stable/c/78d6f9a9eb2a5da6fcbd76d6191d24b0dcc321be
- https://git.kernel.org/stable/c/93224deb50a8d20df3884f3672ce9f982129aa50
CWE Common Weakness Enumeration
Unknown
Protect Your Infrastructure against CVE-2025-22045: 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-2025-3816 – A vulnerability classified as critical was found in westboy CicadasCMS 2.0. This vulnerability affects unknown code of the file /system/schedule/sa...
- CVE-2025-3808 – A vulnerability has been found in zhenfeng13 My-BBS 1.0 and classified as problematic. This vulnerability affects unknown code. The manipulation le...
- CVE-2025-3807 – A vulnerability, which was classified as critical, was found in zhenfeng13 My-BBS 1.0. This affects the function Upload of the file src/main/java/c...
- CVE-2025-3806 – A vulnerability, which was classified as problematic, has been found in dazhouda lecms up to 3.0.3. Affected by this issue is some unknown function...
- CVE-2025-3805 – A vulnerability classified as critical was found in sarrionandia tournatrack up to 4c13a23f43da5317eea4614870a7a8510fc540ec. Affected by this vulne...