CVE-2026-68164: mm/damon/core: disallow overlapping input ranges for damon_set_regions()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 06a4beeeec8f03f0b3e9c78a98f1ae4f0f18cfbd, 4b4a3e7ef7bb622237495db9ba4dfd7417d6530e, 6ce0db97fb37ab8cf8596edca0e3de8618ab009a; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 06a4beeeec8f03f0b3e9c78a98f1ae4f0f18cfbd, 4b4a3e7ef7bb622237495db9ba4dfd7417d6530e, 6ce0db97fb37ab8cf8596edca0e3de8618ab009a; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: mm/damon/core: disallow overlapping input ranges for damon_set_regions() damon_set_regions() assumes the input ranges are sorted by the address and don't overlap each other. Hence the assumption was initially to be explicitly validated. But commit 97d482f4592f ("mm/damon/sysfs: reuse damon_set_regions() for regions setting") has mistakenly removed the validation. This can make DAMON behave in unexpected ways. At the best, the monitoring results snapshot will just look weird since there will be overlapping regions. DAMOS will also work weirdly, applying the same action multiple times for overlapping regions, and make DAMOS quota weird. More seriously, depending on the setup and regions updates sequence, negative size regions can be made. It will trigger WARN_ONCE() if the kernel is built with CONFIG_DAMON_DEBUG_SANITY=y. Depending on the monitoring results, the negative size region can further trigger division by zero in damon_merge_two_regions(). Note that some of the consequences including the WARN_ONCE() and the divide by zero depend on commits that were introduced after the root cause commit 97d482f4592f ("mm/damon/sysfs: reuse damon_set_regions() for regions setting"). Fix the problems by checking the assumption and returning an error if the input ranges don't meet the assumption. The issue was discovered [1] by Sashiko.
- Published
- Aug 10, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.19affected
- 97d482f4592fde2322c319f07bc54f3a0d37861c and later · before a5c453fffb6f2ce75fc10b5d8bc475f1758010bdaffected · git
- 97d482f4592fde2322c319f07bc54f3a0d37861c and later · before 4b4a3e7ef7bb622237495db9ba4dfd7417d6530eaffected · git
- 97d482f4592fde2322c319f07bc54f3a0d37861c and later · before 06a4beeeec8f03f0b3e9c78a98f1ae4f0f18cfbdaffected · git
- 97d482f4592fde2322c319f07bc54f3a0d37861c and later · before 6ce0db97fb37ab8cf8596edca0e3de8618ab009aaffected · git
- 97d482f4592fde2322c319f07bc54f3a0d37861c and later · before e33adf96afb5883f84b0d98747976bde293e33cbaffected · git
- 97d482f4592fde2322c319f07bc54f3a0d37861c and later · before 954157679ec34661c2e87e7eb796104a797c32dbaffected · git
- before 5.19not affected · semver
- 6.1.183 and later · up to and including 6.1.*not affected · semver
- 6.6.148 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.101-1~deb12u1 | 6.12.101-1~deb12u1 |
| Debian:13 | linux | before 6.12.101-1 | 6.12.101-1 |
| Debian:14 | linux | before 7.1.6-1 | 7.1.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-68161Aug 10, 2026 · sctp: close UDP tunnel sockets during netns teardown39Monitor
- ← EarlierCVE-2026-68162Aug 10, 2026 · sctp: avoid auth_enable sysctl UAF during netns teardown31Monitor
- Later →CVE-2026-68165Aug 10, 2026 · mm/damon/core: validate ranges in damon_set_regions()0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 06a4beeeec8f03f0b3e9c78a98f1ae4f0f18cfbd | Vendor (CNA) |
| Linux Linux | 4b4a3e7ef7bb622237495db9ba4dfd7417d6530e | Vendor (CNA) |
| Linux Linux | 6ce0db97fb37ab8cf8596edca0e3de8618ab009a | Vendor (CNA) |
| Linux Linux | 954157679ec34661c2e87e7eb796104a797c32db | Vendor (CNA) |
| Linux Linux | a5c453fffb6f2ce75fc10b5d8bc475f1758010bd | Vendor (CNA) |
| Linux Linux | e33adf96afb5883f84b0d98747976bde293e33cb | Vendor (CNA) |
| azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 | 6.6.150.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/4b4a3e7ef7bb622237495db9ba4dfd7417d6530e
- git.kernel.org/stable/c/6ce0db97fb37ab8cf8596edca0e3de8618ab009a
- git.kernel.org/stable/c/954157679ec34661c2e87e7eb796104a797c32db
- git.kernel.org/stable/c/a5c453fffb6f2ce75fc10b5d8bc475f1758010bd
- git.kernel.org/stable/c/e33adf96afb5883f84b0d98747976bde293e33cb
Vendor advisories and official records. Exploit/PoC links are deliberately left out.