Examples of using Kernel memory in English and their translations into Russian
{-}
-
Official
-
Colloquial
Kernel memory disclosure in SCTP.
Elevation of privilege vulnerability in kernel memory system.
Kernel memory disclosure in sockbuf control messages.
Information disclosure vulnerability in kernel memory subsystem.
Fragments of kernel memory may be included in SCTP packets and transmitted over the network.
Elevation of privilege vulnerability in kernel memory subsystem.
Julian Seward andMichael Tuexen reported a kernel memory disclosure when initializing the SCTP state cookie being sent in INIT-ACK chunks, a buffer allocated from the kernel stack is not completely initialized.
Local users can gain access to sensitive kernel memory.
An abridged 12,000 lines of the C source code of the kernel, memory manager, and file system of MINIX 1.0 are printed in the book.
Local users could gain access to sensitive kernel memory.
For user's convenience, DiskCryptor's driver caches entered passwords in the kernel memory, and automatically chooses the appropriate password during the volume mount.
A local user could obtain access to sensitive kernel memory.
By doing so the attacker gained full control about the kernel memory space and was able to alter any value in memory. .
Reading a directory containing such name entries would leak information from kernel memory.
A user in a guest operating system could corrupt kernel memory, resulting in a denial of service.
Local users with the CAP_NET_ADMIN capability could gain access to sensitive kernel memory.
Prior to NT 6.0, the system opened on-disk files as memory-mapped files in kernel memory space, which used the same memory pools as other kernel components.
A remote attacker could take advantage of this flaw to obtain potentially sensitive information from kernel memory.
A local user with access to a udl framebuffer device could exploit this to overwrite kernel memory, leading to privilege escalation.
Fix the mISDN_sock_recvmsg function to prevent local users from obtaining sensitive information from kernel memory.
ADLAB discovered a possible memory overrun in the ISDN subsystem that may permit a local user to overwrite kernel memory by issuing ioctls with unterminated data.
These actions may involve the creation or deletion of device files, andmay also trigger the loading of particular firmware files into kernel memory.
It was discovered that the KLSI KL5KUSB105 serial USB device driver could log the contents of uninitialised kernel memory, resulting in an information leak.
Several vulnerabilities have been discovered in the FreeBSD kernel that may lead to a denial of service orpossibly disclosure of kernel memory.
On a 64-bit kernel a local user with access to a suitable video device can exploit this to overwrite kernel memory, leading to privilege escalation.
Fix the ALSA control implementation to prevent local users from causing a denialof service attack and from obtaining sensitive information from kernel memory.
On a 64-bit kernel, a local user with the CAP_NET_ADMINcapability(in any user namespace) could use this to overwrite kernel memory, possibly leading to privilege escalation.
Dan Carpenter reported issues in the cpqarray driver for Compaq Smart2 Controllers andthe cciss driver for HP Smart Array controllers allowing users to gain access to sensitive kernel memory.
Local users could gain access to sensitive kernel memory.
It was discovered that the kvm_emulate_hypercall function in KVM does not prevent access to MMU hypercalls from ring 0, which allows local guest OS users to causea denial of service(guest kernel crash) and read or write guest kernel memory.