uacce: implement mremap in uacce_vm_ops to return -EPERM
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: uacce: implement mremap in uacce_vm_ops to return -EPERM The current uacce_vm_ops does not support the mremap operation of vm_operations_struct. Implement .mremap to return -EPERM to remind users. The reason we need to explicitly disable mremap is that when the driver does not implement .mremap, it uses the default mremap method. This could lead to a risk scenario: An application might first mmap address p1, then mremap to p2, followed by munmap(p1), and finally munmap(p2). Since the default mremap copies the original vma's vm_private_data (i.e., q) to the new vma, both munmap operations would trigger vma_close, causing q->qfr to be freed twice(qfr will be set to null here, so repeated release is ok).
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
5.7
References 7
git.kernel.org
- stable/c/78d99f062d42e3af2ca46bde1a8e46e0dfd372e3
- stable/c/ebfa85658a39b49ec3901ceea7535b73aa0429e6
- stable/c/75b29bdc935ff93b8e8bf6f6b4d8a4810b26e06f
- stable/c/4c042bc71474dbe417c268f4bfb8ec196f802f07
- stable/c/a407ddd61b3e6afc5ccfcd1478797171cf5686ee
- stable/c/ba29b59d124e725e0377f09b2044909c91d657a1
- stable/c/02695347be532b628f22488300d40c4eba48b9b7