When msync(MS_INVALIDATE) is called on a mapping of an unmanaged device object, the physical pages in the mapping
Source GCVE Database
Not known to be exploited · CVSS 8.8 High.
Data as of 16 Nov 2026, 20:25 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 8.8 |
|---|
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
AI-suggested
Until an official fix is available, restrict unprivileged local users' access to devices that provide memory-mapped I/O to reduce the risk of exploitation.
Description
CVE-2026-49418 is a kernel vulnerability triggered when msync(MS_INVALIDATE) is called on a memory mapping of an unmanaged device object. This causes physical pages to be marked invalid but remain in the pager's page list, leading to a corrupted page list and a double free on object destruction. An unprivileged local user with access to a device providing memory-mapped I/O can exploit this use-after-free condition. The vulnerability affects a specific pool of objects called "fictitious pages" that are never recycled for other purposes. Exploitation may allow privilege escalation.