Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CVE-2026-49418— Use-after-free in device pager page list

Quick assessment

Affected
FreeBSD FreeBSD
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

当对未管理的设备对象映射调用 msync(MS_INVALIDATE) 时,映射范围内的物理页被标记为无效,但仍保留在分页器(pager)的页面列表中。随后发生的页面错误(page fault)会导致故障处理程序将该页重新插入到该对象的列表中。这种操作会破坏列表结构,并在对象销毁时导致页面被双重释放(double free)。 拥有设备访问权限且无需特权的本地用户,若能访问提供内存映射 I/O(MMIO)的设备,即可在内核中触发释放后使用(use-after-free)漏洞。不过,该漏洞的影响范围仅限于一组对象(即

AI Predicted 4.4 Difficulty: Hard EPSS 0.28% · P21

Affected Version Matrix 4

VendorProduct Version RangeStatus
FreeBSD FreeBSD 15.1-RELEASE< p1 affected
15.0-RELEASE< p11 affected
14.4-RELEASE< p7 affected
14.3-RELEASE< p16 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-49418

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Use-after-free in device pager page list
Source: CVE Program / CVE List V5
Vulnerability Description
When msync(MS_INVALIDATE) is called on a mapping of an unmanaged device object, the physical pages in the mapping range are marked invalid but remain in the pager's page list. A subsequent page fault will cause the fault handler to re-insert the page into the object's list. This corrupts the list, and on object destruction the page is freed twice. An unprivileged local user with access to a device that provides memory-mapped I/O can trigger a use-after-free in the kernel, though this is limited to a pool of objects ("fictitious pages") that are never recycled for a different purpose. It may be possible to exploit this to escalate privileges.
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
释放后使用
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
FreeBSD FreeBSD 15.1-RELEASE ~ p1 -

II. Public POCs for CVE-2026-49418

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-49418

登录查看更多情报信息。

Vendor Advisories for CVE-2026-49418 (1)

Same Patch Batch · FreeBSD · 2026-08-19 · 23 CVEs total

CVE-2026-49423 Remote DOS via uninitialized memory access in KTLS receive
CVE-2026-58087 Heap out-of-bounds access in semctl(2)
CVE-2026-58088 Race condition in ELF core dump segment counting
CVE-2026-58083 Use-after-free in kqueue copy-on-fork
CVE-2026-58084 Kernel stack disclosure via timer_settime(2)
CVE-2026-58085 Missing MAC validation in wg(4) packet decryption
CVE-2026-58086 ktrace(2) privilege incorrectly validated in jails
CVE-2026-49425 Kernel stack disclosure in 32-bit compatibility support
CVE-2026-49424 Kernel stack disclosure in Linux compatibility layer
CVE-2026-58081 Heap based buffer overflow in iconv(3)
CVE-2026-58082 Stack based buffer overflow in iconv(3)
CVE-2026-49419 Jail reference count underflow
CVE-2026-49426 Incorrect audit records for ptrace(2) syscall requests
CVE-2026-49427 posixshm: largepage shared memory objects not explicitly wired
CVE-2026-49428 posixshm: system calls can incorrectly free memory of largepage objects
CVE-2026-49420 Buffer overflow in libalias RTSP handler
CVE-2026-49422 Use-after-free in TCP RACK stack option handler
CVE-2026-49421 unlinkat(2) ignores AT_RESOLVE_BENEATH flag
CVE-2026-49430 Kernel heap overflow in ZFS_IOC_RECV_NEW ioctl
CVE-2026-49429 Kernel heap overflow in ZFS_IOC_USERSPACE_MANY ioctl

Showing top 20 of 23 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2026-49418

No comments yet


Leave a comment