Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-40218: mm/damon/vaddr: do not repeat pte_offset_map_lock() until success

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.20% (FIRST EPSS).
  • Fixed version: Linux Linux 0ccd91cf749536d41307a07e60ec14ab0dbf21f5, 677ebfe5d00f94adec0c0204f6e6e2a82d3f77bf, ac42320ec873bfe726141069cfdd90ee5bc4e885; azl3 kernel 6.6.112.1-2 on Azure Linux 3.0 6.6.117.1-1.

Low priority for now. Upgrade to Linux Linux 0ccd91cf749536d41307a07e60ec14ab0dbf21f5, 677ebfe5d00f94adec0c0204f6e6e2a82d3f77bf, ac42320ec873bfe726141069cfdd90ee5bc4e885; azl3 kernel 6.6.112.1-2 on Azure Linux 3.0 6.6.117.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/vaddr: do not repeat pte_offset_map_lock() until success DAMON's virtual address space operation set implementation (vaddr) calls pte_offset_map_lock() inside the page table walk callback function. This is for reading and writing page table accessed bits. If pte_offset_map_lock() fails, it retries by returning the page table walk callback function with ACTION_AGAIN. pte_offset_map_lock() can continuously fail if the target is a pmd migration entry, though. Hence it could cause an infinite page table walk if the migration cannot be done until the page table walk is finished. This indeed caused a soft lockup when CPU hotplugging and DAMON were running in parallel. Avoid the infinite loop by simply not retrying the page table walk. DAMON is promising only a best-effort accuracy, so missing access to such pages is no problem.

—No exploit Fix available
Published
Dec 4, 2025
Updated
Oct 19, 2026
EPSS
0.2% · 10th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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.

Follow CVE-2025-40218

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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

    • 6.5affected
    • 7780d04046a2288ab85d88bedacc60fa4fad9971 and later · before 677ebfe5d00f94adec0c0204f6e6e2a82d3f77bfaffected · git
    • 7780d04046a2288ab85d88bedacc60fa4fad9971 and later · before ac42320ec873bfe726141069cfdd90ee5bc4e885affected · git
    • 7780d04046a2288ab85d88bedacc60fa4fad9971 and later · before 0ccd91cf749536d41307a07e60ec14ab0dbf21f5affected · git
    • 7780d04046a2288ab85d88bedacc60fa4fad9971 and later · before b93af2cc8e036754c0d9970d9ddc47f43cc94b9faffected · git
    • before 6.5not affected · semver
    • 6.6.113 and later · up to and including 6.6.*not affected · semver
    • 6.12.54 and later · up to and including 6.12.*not affected · semver
    • 6.17.4 and later · up to and including 6.17.*not affected · semver
    • 6.18 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:13linuxbefore 6.12.57-16.12.57-1
Debian:14linuxbefore 6.17.6-16.17.6-1
openSUSE:Leap 16.0dtb-aarch64before 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-64kbbefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-azurebefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-defaultbefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-default-basebefore 6.12.0-160000.9.1.160000.2.66.12.0-160000.9.1.160000.2.6
openSUSE:Leap 16.0kernel-docsbefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-kvmsmallbefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-obs-buildbefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-obs-qabefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-rtbefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-sourcebefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-symsbefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-zfcpdumpbefore 6.12.0-160000.9.16.12.0-160000.9.1
SUSE:Linux Enterprise Server 16.0kernel-azurebefore 6.12.0-160000.9.16.12.0-160000.9.1
SUSE:Linux Enterprise Server 16.0kernel-docsbefore 6.12.0-160000.9.16.12.0-160000.9.1
SUSE:Linux Enterprise Server 16.0kernel-kvmsmallbefore 6.12.0-160000.9.16.12.0-160000.9.1
SUSE:Linux Enterprise Server 16.0kernel-obs-qabefore 6.12.0-160000.9.16.12.0-160000.9.1
SUSE:Linux Enterprise Server 16.0kernel-symsbefore 6.12.0-160000.9.16.12.0-160000.9.1
SUSE:Linux Enterprise Server 16.0kernel-zfcpdumpbefore 6.12.0-160000.9.16.12.0-160000.9.1
SUSE:Linux Micro 6.2kernel-64kbbefore 6.12.0-160000.9.16.12.0-160000.9.1
SUSE:Linux Micro 6.2kernel-defaultbefore 6.12.0-160000.9.16.12.0-160000.9.1
SUSE:Linux Micro 6.2kernel-default-basebefore 6.12.0-160000.9.1.160000.2.66.12.0-160000.9.1.160000.2.6

+3

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-40216Dec 4, 2025 · io_uring/rsrc: don't rely on user vaddr alignment
    31Monitor
  • ← EarlierCVE-2025-40217Dec 4, 2025 · pidfs: validate extensible ioctls
    0Monitor
  • Later →CVE-2025-40219Dec 4, 2025 · PCI/IOV: Fix race between SR-IOV enable/disable and hotplug
    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 / packageFixed versionSource
Linux Linux0ccd91cf749536d41307a07e60ec14ab0dbf21f5Vendor (CNA)
Linux Linux677ebfe5d00f94adec0c0204f6e6e2a82d3f77bfVendor (CNA)
Linux Linuxac42320ec873bfe726141069cfdd90ee5bc4e885Vendor (CNA)
Linux Linuxb93af2cc8e036754c0d9970d9ddc47f43cc94b9fVendor (CNA)
azl3 kernel 6.6.112.1-2 on Azure Linux 3.06.6.117.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.12.57-1 · Debian:13Package registry (OSV)
opensuse:dtb-aarch646.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-64kb6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-azure6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default-base6.12.0-160000.9.1.160000.2.6 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-docs6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-kvmsmall6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-build6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-qa6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-rt6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-source6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-syms6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
suse:kernel-64kb6.12.0-160000.9.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-azure6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-default6.12.0-160000.9.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-default-base6.12.0-160000.9.1.160000.2.6 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-docs6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-kvmsmall6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-obs-build6.12.0-160000.9.1 · SUSE:Linux Micro Extras 6.2Package registry (OSV)
suse:kernel-obs-qa6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-rt6.12.0-160000.9.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-source6.12.0-160000.9.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-syms6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-zfcpdump6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0Package 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.

No history yet (it accumulates with the daily EPSS job).

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 researchers

Finders, 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).

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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records