affected products in the CVE record: Linux · Linuxthe product type of Linux kernel in nday's product registry
stage
DIS
disclosed
cvss
7.8 HIGH v3.1
# Lifecycle
x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet
# Summary
In the Linux kernel, the following vulnerability has been resolved:
binder: fix UAF of alloc->vma in race with munmap()
[ cmllamas: clean forward port from commit 015ac18be7de ("binder: fix
UAF of alloc->vma in race with munmap()") in 5.10 stable. It is needed
in mainline after the revert of commit a43cfc87caaf ("android: binder:
stop saving a pointer to the VMA") as pointed out by Liam. The commit
log and tags have been tweaked to reflect this. ]
In commit 720c24192404 ("ANDROID: binder: change down_write to
down_read") binder assumed the mmap read lock is sufficient to protect
alloc->vma inside binder_update_page_range(). This used to be accurate
until commit dd2283f2605e ("mm: mmap: zap pages with read mmap_sem in
munmap"), which now downgrades the mmap_lock after detaching the vma
from the rbtree in munmap(). Then it proceeds to teardown and free the
vma with only the read lock held.
This means that accesses to alloc->vma in binder_update_page_range() now
will race with vm_area_free() in munmap() and can cause a UAF as shown
in the following KASAN trace:
==================================================================BUG: KASAN: use-after-free in vm_insert_page+0x7c/0x1f0Read of size 8 at addr ffff16204ad00600 by task server/558
CPU: 3 PID: 558 Comm: server Not tainted 5.10.150-00001-gdc8dcf942daa #1
Hardware name: linux,dummy-virt (DT)
Call trace:dump_backtrace+0x0/0x2a0show_stack+0x18/0x2cdump_stack+0xf8/0x164print_address_description.constprop.0+0x9c/0x538kasan_report+0x120/0x200__asan_load8+0xa0/0xc4vm_insert_page+0x7c/0x1f0binder_update_page_range+0x278/0x50cbinder_alloc_new_buf+0x3f0/0xba0binder_transaction+0x64c/0x3040binder_thread_write+0x924/0x2020binder_ioctl+0x1610/0x2e5c__arm64_sys_ioctl+0xd4/0x120el0_svc_common.constprop.0+0xac/0x270do_el0_svc+0x38/0xa0el0_svc+0x1c/0x2cel0_sync_handler+0xe8/0x114el0_sync+0x180/0x1c0Allocated by task 559:kasan_save_stack+0x38/0x6c__kasan_kmalloc.constprop.0+0xe4/0xf0kasan_slab_alloc+0x18/0x2ckmem_cache_alloc+0x1b0/0x2d0vm_area_alloc+0x28/0x94mmap_region+0x378/0x920do_mmap+0x3f0/0x600vm_mmap_pgoff+0x150/0x17cksys_mmap_pgoff+0x284/0x2dc__arm64_sys_mmap+0x84/0xa4el0_svc_common.constprop.0+0xac/0x270do_el0_svc+0x38/0xa0el0_svc+0x1c/0x2cel0_sync_handler+0xe8/0x114el0_sync+0x180/0x1c0Freed by task 560:kasan_save_stack+0x38/0x6ckasan_set_track+0x28/0x40kasan_set_free_info+0x24/0x4c__kasan_slab_free+0x100/0x164kasan_slab_free+0x14/0x20kmem_cache_free+0xc4/0x34cvm_area_free+0x1c/0x2cremove_vma+0x7c/0x94__do_munmap+0x358/0x710__vm_munmap+0xbc/0x130__arm64_sys_munmap+0x4c/0x64el0_svc_common.constprop.0+0xac/0x270do_el0_svc+0x38/0xa0el0_svc+0x1c/0x2cel0_sync_handler+0xe8/0x114el0_sync+0x180/0x1c0[...]
==================================================================
To prevent the race above, revert back to taking the mmap write lock
inside binder_update_page_range(). One might expect an increase of mmap
lock contention. However, binder already serializes these calls via top
level alloc->mutex. Also, there was no performance impact shown when
running the binder benchmark tests.
Original text of the CVE record (cvelist), shown as published.
# Exploit conditions
What an attack needs, read from the CVSS vector.
Attack vector AV:L
Local: needs a local or SSH session, or a user tricked into acting on the machine
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:L
Low: ordinary user privileges
User interaction UI:N
None: no action by anyone other than the attacker
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 3.1 vector from the CVE record, scored by the CNA Linux.
Your account is suspended: you cannot comment, reply, edit or report. You can still delete your own comments.
formatting
↵↵
empty line: new paragraph
↵
line break: kept as is
*…*
emphasis
**…**
bold
`…`
inline code
```
on its own line: starts and ends a code block
> …
quote
- …
list
1. …
numbered list
[…](https://…)
link (http and https only)
https://…
bare address: link
CVE-2026-1234
links to that vulnerability on nday
\*
shows the character itself
Headings, images, tables, nested lists and HTML are shown as plain text.
Links from new accounts are shown as plain text; CVE IDs are always linked.
reported
# Keyboard shortcuts
j / k
next / previous row (list rows or events)
Enter
open the vulnerability under the cursor
/
search (Esc leaves the box)
y
copy the CVE ID
o
open the event's source (vulnerability page)
u
back
?
show / hide this help
sign inaccountmodadminAdminProfileFollowingSecurityDeveloperSign outSigned in.Sign-in method linked to your account.Sign-in was cancelled at the provider; nothing changed.That login already belongs to another nday account, or this account already has one from the same provider. Nothing was linked.Sign-in did not complete. Try again.You are still signed in as before: that login belongs to another nday account, or to none yet. Sign out first to use it.Linking was not completed because your last sign-in is no longer recent. Confirm it's you on the account page, then link again.This account is suspended, so new sign-in methods cannot be linked.Dismissworking…Delete this comment? This cannot be undone.Hidden by a moderator: {reason}text (moderators only)earlier versions: {n}replaced at {time}Posting needs the community rules accepted (version {version}).The community rules changed (version {version}); read and accept them to continue.Reported. A moderator will look at it.You have already reported this comment.You are signed out. Sign in again to continue.The request was refused as cross-site. Reload the page and try again.The session token changed. Reload the page and try again.Your account is suspended.Choose a handle on your account page first.Accept the current community rules first.Only moderators can do this.Only the author can do this.You cannot report your own comment.This comment changed in the meantime. Reload the page to see it as it is now.This comment or vulnerability does not exist (any more).Not a valid CVE ID.Only a visible top-level comment can get replies.This thread has reached its reply limit.You posted the same text here a moment ago.A comment needs 1 to {max} characters.Comments cannot be posted from this site language.Unknown purpose, or a purpose on a reply. Reload the page and try again.The reason is missing or too long.The note is too long.Unknown resolution.This position in the list is no longer valid. Reload the page.The request was malformed. Reload the page and try again.The text is too large.Too many requests. Try again in {seconds} s.Too many requests. Try again later.Daily limit reached. Try again after {time}.The server is busy. Try again in a moment.This address does not take comments. Open the page on the main site.Server error. Try again later.Network error: nday could not be reached. Check the connection and try again.The community rules changed while you were reading. Read them again.Write something first.Too long: {n} characters, at most {max}.Tick the box to accept the community rules first.Something went wrong ({code}). Try again.No comments yet.The discussion could not be loaded right now.more commentsfirst commentsmore repliesreplies[deleted account]link to this commenteditedposted on the {language} siteHidden by a moderator.Deleted by its author.technical analysisreproduction reportfix reportdetection methodquestionPlease include the affected version, the environment (OS, configuration), what you did and what happened, and your source.Please include the fixed version or patch, the environment, how you checked the fix and what happened, and your source.show {n} moreview on XThe posts could not be loaded.nday has not collected any post on X by listed researchers that mentions this CVE.expandcollapsesending…Sent. An editor will look at it; you can follow its status here.titlesummaryaffected products or versionsfix informationtimeline eventsource linksotherwaiting for an editoracceptednot acceptedsent {at}Editors' note: {note}Sign in first.Your account is suspended.Choose a public handle on your account page first.Accept the current community rules on your account page first.The page's session expired; try again.The request was refused; reload the page and try again.Choose what is wrong.Write what is wrong, within the length limit.The evidence link must be a full http:// or https:// address.You already have several reports on this vulnerability waiting for an editor; wait until they are handled.This vulnerability already has many reports waiting for an editor; try again later.You reached the limit of reports for 24 hours; try again later.Too many requests; wait a moment and try again.This vulnerability was not found.The report is too large.Network error; try again.Write what is wrong first.Too long: at most {max} characters.Something went wrong; try again later.