CVE-2025-68211 — linux / linux_kernel
In the Linux kernel, the following vulnerability has been resolved:
ksm: use range-walk function to jump over holes in scan_get_next_rmap_item
Currently, scan_get_next_rmap_item() walks every page address in a VMA to locate mergeable pages. This becomes highly inefficient when scanning large virtual memory areas that contain mostly unmapped regions, causing ksmd to use large amount of cpu without deduplicating much pages.
This patch replaces the per-address lookup with a range walk using walk_page_range(). The range walker allows KSM to skip over entire unmapped holes in a VMA, avoiding unnecessary lookups. This problem was previously discussed in [1].
Consider the following test program which creates a 32 TiB mapping in the virtual address space but only populates a single page:
#include <unistd.h> #include <stdio.h> #include <sys/mman.h>
/* 32 TiB */ const size_t size = 32ul * 1024 * 1024 * 1024 * 1024;
int main() { char *area = mmap(NULL, size, PROT_READ | PROT_WRITE, MAP_NORESERVE | MAP_PRIVATE | MAP_ANON, -1, 0);
if (area == MAP_FAILED) {
perror("mmap() failed\n");
return -1;
}
/* Populate a single page such that we get an anon_vma. */
*area = 0;
/* Enable KSM. */
madvise(area, size, MADV_MERGEABLE);
pause();
return 0;
}
$ ./ksm-sparse & $ echo 1 > /sys/kernel/mm/ksm/run
Without this patch ksmd uses 100% of the cpu for a long time (more then 1 hour in my test machine) scanning all the 32 TiB virtual address space that contain only one mapped page. This makes ksmd essentially deadlocked not able to deduplicate anything of value. With this patch ksmd walks only the one mapped page and skips the rest of the 32 TiB virtual address space, making the scan fast using little cpu.
| Software | From | Fixed in |
|---|---|---|
| linux / linux_kernel | 2.6.32 | 5.10.249 |
| linux / linux_kernel | 5.11 | 5.15.199 |
| linux / linux_kernel | 5.16 | 6.1.161 |
| linux / linux_kernel | 6.2 | 6.6.121 |
| linux / linux_kernel | 6.7 | 6.12.59 |
| linux / linux_kernel | 6.13 | 6.17.9 |
| linux / linux_kernel | 6.18-rc1 | 6.18-rc1.x |
| linux / linux_kernel | 6.18-rc2 | 6.18-rc2.x |
| linux / linux_kernel | 6.18-rc3 | 6.18-rc3.x |
| linux / linux_kernel | 6.18-rc4 | 6.18-rc4.x |
| linux / linux_kernel | 6.18-rc5 | 6.18-rc5.x |
- https://git.kernel.org/stable/c/10644e8839544dd5699c03c8fb1aeeefc41602fd
- https://git.kernel.org/stable/c/220cb3e425e17587f560335924cba9f16a842c64
- https://git.kernel.org/stable/c/67137b715b7db28d82e4ed07a7092c2fa6ba7adb
- https://git.kernel.org/stable/c/74f78421c925b6d17695566f0c5941de57fd44b3
- https://git.kernel.org/stable/c/9c2f8a9b68024e5ebb4813665845ec0a95f2eac3
- https://git.kernel.org/stable/c/f5548c318d6520d4fa3c5ed6003eeb710763cbc5
- https://git.kernel.org/stable/c/f62973e0767e4fcd6799087787fca08ca2a85b8c
Deep Security Visibility Without the Complexity
SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.
- No setup fees
- 5-min deployment
- Cancel anytime
Frequently Asked Questions
A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.
CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.
A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.
Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.
Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.
SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.