idx int64 | project string | commit_id string | project_url string | commit_url string | commit_message string | target int64 | func string | func_hash float64 | file_name string | file_hash float64 | cwe list | cve string | cve_desc string | nvd_url string |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
32,363 | linux | 9b3e617f3df53822345a8573b6d358f6b9e5ed87 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9b3e617f3df53822345a8573b6d358f6b9e5ed87 | atm: update msg_namelen in vcc_recvmsg()
The current code does not fill the msg_name member in case it is set.
It also does not set the msg_namelen member to 0 and therefore makes
net/socket.c leak the local, uninitialized sockaddr_storage variable
to userland -- 128 bytes of kernel stack memory.
Fix that by simply s... | 0 | static int check_ci(const struct atm_vcc *vcc, short vpi, int vci)
{
struct hlist_head *head = &vcc_hash[vci & (VCC_HTABLE_SIZE - 1)];
struct sock *s;
struct atm_vcc *walk;
sk_for_each(s, head) {
walk = atm_sk(s);
if (walk->dev != vcc->dev)
continue;
if (test_bit(ATM_VF_ADDR, &walk->flags) && walk->vpi ==... | 176,047,553,517,841,700,000,000,000,000,000,000,000 | common.c | 105,103,316,668,524,350,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3222 | The vcc_recvmsg function in net/atm/common.c in the Linux kernel before 3.9-rc7 does not initialize a certain length variable, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-3222 |
32,364 | linux | 9b3e617f3df53822345a8573b6d358f6b9e5ed87 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9b3e617f3df53822345a8573b6d358f6b9e5ed87 | atm: update msg_namelen in vcc_recvmsg()
The current code does not fill the msg_name member in case it is set.
It also does not set the msg_namelen member to 0 and therefore makes
net/socket.c leak the local, uninitialized sockaddr_storage variable
to userland -- 128 bytes of kernel stack memory.
Fix that by simply s... | 0 | static int check_tp(const struct atm_trafprm *tp)
{
/* @@@ Should be merged with adjust_tp */
if (!tp->traffic_class || tp->traffic_class == ATM_ANYCLASS)
return 0;
if (tp->traffic_class != ATM_UBR && !tp->min_pcr && !tp->pcr &&
!tp->max_pcr)
return -EINVAL;
if (tp->min_pcr == ATM_MAX_PCR)
return -EINVAL... | 74,242,288,669,545,020,000,000,000,000,000,000,000 | common.c | 105,103,316,668,524,350,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3222 | The vcc_recvmsg function in net/atm/common.c in the Linux kernel before 3.9-rc7 does not initialize a certain length variable, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-3222 |
32,365 | linux | 9b3e617f3df53822345a8573b6d358f6b9e5ed87 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9b3e617f3df53822345a8573b6d358f6b9e5ed87 | atm: update msg_namelen in vcc_recvmsg()
The current code does not fill the msg_name member in case it is set.
It also does not set the msg_namelen member to 0 and therefore makes
net/socket.c leak the local, uninitialized sockaddr_storage variable
to userland -- 128 bytes of kernel stack memory.
Fix that by simply s... | 0 | static int find_ci(const struct atm_vcc *vcc, short *vpi, int *vci)
{
static short p; /* poor man's per-device cache */
static int c;
short old_p;
int old_c;
int err;
if (*vpi != ATM_VPI_ANY && *vci != ATM_VCI_ANY) {
err = check_ci(vcc, *vpi, *vci);
return err;
}
/* last scan may have left values ou... | 41,194,436,494,809,783,000,000,000,000,000,000,000 | common.c | 105,103,316,668,524,350,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3222 | The vcc_recvmsg function in net/atm/common.c in the Linux kernel before 3.9-rc7 does not initialize a certain length variable, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-3222 |
32,366 | linux | 9b3e617f3df53822345a8573b6d358f6b9e5ed87 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9b3e617f3df53822345a8573b6d358f6b9e5ed87 | atm: update msg_namelen in vcc_recvmsg()
The current code does not fill the msg_name member in case it is set.
It also does not set the msg_namelen member to 0 and therefore makes
net/socket.c leak the local, uninitialized sockaddr_storage variable
to userland -- 128 bytes of kernel stack memory.
Fix that by simply s... | 0 | void unregister_atmdevice_notifier(struct notifier_block *nb)
{
atomic_notifier_chain_unregister(&atm_dev_notify_chain, nb);
}
| 45,307,119,258,764,740,000,000,000,000,000,000,000 | common.c | 105,103,316,668,524,350,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3222 | The vcc_recvmsg function in net/atm/common.c in the Linux kernel before 3.9-rc7 does not initialize a certain length variable, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-3222 |
32,367 | linux | 9b3e617f3df53822345a8573b6d358f6b9e5ed87 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9b3e617f3df53822345a8573b6d358f6b9e5ed87 | atm: update msg_namelen in vcc_recvmsg()
The current code does not fill the msg_name member in case it is set.
It also does not set the msg_namelen member to 0 and therefore makes
net/socket.c leak the local, uninitialized sockaddr_storage variable
to userland -- 128 bytes of kernel stack memory.
Fix that by simply s... | 0 | int vcc_connect(struct socket *sock, int itf, short vpi, int vci)
{
struct atm_dev *dev;
struct atm_vcc *vcc = ATM_SD(sock);
int error;
pr_debug("(vpi %d, vci %d)\n", vpi, vci);
if (sock->state == SS_CONNECTED)
return -EISCONN;
if (sock->state != SS_UNCONNECTED)
return -EINVAL;
if (!(vpi || vci))
return -... | 77,356,300,317,472,440,000,000,000,000,000,000,000 | common.c | 105,103,316,668,524,350,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3222 | The vcc_recvmsg function in net/atm/common.c in the Linux kernel before 3.9-rc7 does not initialize a certain length variable, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-3222 |
32,368 | linux | 9b3e617f3df53822345a8573b6d358f6b9e5ed87 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9b3e617f3df53822345a8573b6d358f6b9e5ed87 | atm: update msg_namelen in vcc_recvmsg()
The current code does not fill the msg_name member in case it is set.
It also does not set the msg_namelen member to 0 and therefore makes
net/socket.c leak the local, uninitialized sockaddr_storage variable
to userland -- 128 bytes of kernel stack memory.
Fix that by simply s... | 0 | int vcc_create(struct net *net, struct socket *sock, int protocol, int family)
{
struct sock *sk;
struct atm_vcc *vcc;
sock->sk = NULL;
if (sock->type == SOCK_STREAM)
return -EINVAL;
sk = sk_alloc(net, family, GFP_KERNEL, &vcc_proto);
if (!sk)
return -ENOMEM;
sock_init_data(sock, sk);
sk->sk_state_change =... | 60,548,578,128,287,160,000,000,000,000,000,000,000 | common.c | 105,103,316,668,524,350,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3222 | The vcc_recvmsg function in net/atm/common.c in the Linux kernel before 3.9-rc7 does not initialize a certain length variable, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-3222 |
32,369 | linux | 9b3e617f3df53822345a8573b6d358f6b9e5ed87 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9b3e617f3df53822345a8573b6d358f6b9e5ed87 | atm: update msg_namelen in vcc_recvmsg()
The current code does not fill the msg_name member in case it is set.
It also does not set the msg_namelen member to 0 and therefore makes
net/socket.c leak the local, uninitialized sockaddr_storage variable
to userland -- 128 bytes of kernel stack memory.
Fix that by simply s... | 0 | static void vcc_def_wakeup(struct sock *sk)
{
struct socket_wq *wq;
rcu_read_lock();
wq = rcu_dereference(sk->sk_wq);
if (wq_has_sleeper(wq))
wake_up(&wq->wait);
rcu_read_unlock();
}
| 32,165,670,469,224,660,000,000,000,000,000,000,000 | common.c | 105,103,316,668,524,350,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3222 | The vcc_recvmsg function in net/atm/common.c in the Linux kernel before 3.9-rc7 does not initialize a certain length variable, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-3222 |
32,370 | linux | 9b3e617f3df53822345a8573b6d358f6b9e5ed87 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9b3e617f3df53822345a8573b6d358f6b9e5ed87 | atm: update msg_namelen in vcc_recvmsg()
The current code does not fill the msg_name member in case it is set.
It also does not set the msg_namelen member to 0 and therefore makes
net/socket.c leak the local, uninitialized sockaddr_storage variable
to userland -- 128 bytes of kernel stack memory.
Fix that by simply s... | 0 | int vcc_getsockopt(struct socket *sock, int level, int optname,
char __user *optval, int __user *optlen)
{
struct atm_vcc *vcc;
int len;
if (get_user(len, optlen))
return -EFAULT;
if (__SO_LEVEL_MATCH(optname, level) && len != __SO_SIZE(optname))
return -EINVAL;
vcc = ATM_SD(sock);
switch (optname) {
... | 152,612,806,643,551,200,000,000,000,000,000,000,000 | common.c | 105,103,316,668,524,350,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3222 | The vcc_recvmsg function in net/atm/common.c in the Linux kernel before 3.9-rc7 does not initialize a certain length variable, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-3222 |
32,371 | linux | 9b3e617f3df53822345a8573b6d358f6b9e5ed87 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9b3e617f3df53822345a8573b6d358f6b9e5ed87 | atm: update msg_namelen in vcc_recvmsg()
The current code does not fill the msg_name member in case it is set.
It also does not set the msg_namelen member to 0 and therefore makes
net/socket.c leak the local, uninitialized sockaddr_storage variable
to userland -- 128 bytes of kernel stack memory.
Fix that by simply s... | 0 | void vcc_insert_socket(struct sock *sk)
{
write_lock_irq(&vcc_sklist_lock);
__vcc_insert_socket(sk);
write_unlock_irq(&vcc_sklist_lock);
}
| 26,812,373,791,236,246,000,000,000,000,000,000,000 | common.c | 105,103,316,668,524,350,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3222 | The vcc_recvmsg function in net/atm/common.c in the Linux kernel before 3.9-rc7 does not initialize a certain length variable, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-3222 |
32,372 | linux | 9b3e617f3df53822345a8573b6d358f6b9e5ed87 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9b3e617f3df53822345a8573b6d358f6b9e5ed87 | atm: update msg_namelen in vcc_recvmsg()
The current code does not fill the msg_name member in case it is set.
It also does not set the msg_namelen member to 0 and therefore makes
net/socket.c leak the local, uninitialized sockaddr_storage variable
to userland -- 128 bytes of kernel stack memory.
Fix that by simply s... | 0 | unsigned int vcc_poll(struct file *file, struct socket *sock, poll_table *wait)
{
struct sock *sk = sock->sk;
struct atm_vcc *vcc;
unsigned int mask;
sock_poll_wait(file, sk_sleep(sk), wait);
mask = 0;
vcc = ATM_SD(sock);
/* exceptional events */
if (sk->sk_err)
mask = POLLERR;
if (test_bit(ATM_VF_RELEAS... | 64,112,739,607,388,040,000,000,000,000,000,000,000 | common.c | 105,103,316,668,524,350,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3222 | The vcc_recvmsg function in net/atm/common.c in the Linux kernel before 3.9-rc7 does not initialize a certain length variable, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-3222 |
32,373 | linux | 9b3e617f3df53822345a8573b6d358f6b9e5ed87 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9b3e617f3df53822345a8573b6d358f6b9e5ed87 | atm: update msg_namelen in vcc_recvmsg()
The current code does not fill the msg_name member in case it is set.
It also does not set the msg_namelen member to 0 and therefore makes
net/socket.c leak the local, uninitialized sockaddr_storage variable
to userland -- 128 bytes of kernel stack memory.
Fix that by simply s... | 0 | void vcc_process_recv_queue(struct atm_vcc *vcc)
{
struct sk_buff_head queue, *rq;
struct sk_buff *skb, *tmp;
unsigned long flags;
__skb_queue_head_init(&queue);
rq = &sk_atm(vcc)->sk_receive_queue;
spin_lock_irqsave(&rq->lock, flags);
skb_queue_splice_init(rq, &queue);
spin_unlock_irqrestore(&rq->lock, flags... | 289,377,062,615,470,560,000,000,000,000,000,000,000 | common.c | 105,103,316,668,524,350,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3222 | The vcc_recvmsg function in net/atm/common.c in the Linux kernel before 3.9-rc7 does not initialize a certain length variable, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-3222 |
32,374 | linux | 9b3e617f3df53822345a8573b6d358f6b9e5ed87 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9b3e617f3df53822345a8573b6d358f6b9e5ed87 | atm: update msg_namelen in vcc_recvmsg()
The current code does not fill the msg_name member in case it is set.
It also does not set the msg_namelen member to 0 and therefore makes
net/socket.c leak the local, uninitialized sockaddr_storage variable
to userland -- 128 bytes of kernel stack memory.
Fix that by simply s... | 0 | static void vcc_release_cb(struct sock *sk)
{
struct atm_vcc *vcc = atm_sk(sk);
if (vcc->release_cb)
vcc->release_cb(vcc);
}
| 9,645,875,502,639,261,000,000,000,000,000,000,000 | common.c | 105,103,316,668,524,350,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3222 | The vcc_recvmsg function in net/atm/common.c in the Linux kernel before 3.9-rc7 does not initialize a certain length variable, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-3222 |
32,375 | linux | 9b3e617f3df53822345a8573b6d358f6b9e5ed87 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9b3e617f3df53822345a8573b6d358f6b9e5ed87 | atm: update msg_namelen in vcc_recvmsg()
The current code does not fill the msg_name member in case it is set.
It also does not set the msg_namelen member to 0 and therefore makes
net/socket.c leak the local, uninitialized sockaddr_storage variable
to userland -- 128 bytes of kernel stack memory.
Fix that by simply s... | 0 | static void vcc_remove_socket(struct sock *sk)
{
write_lock_irq(&vcc_sklist_lock);
sk_del_node_init(sk);
write_unlock_irq(&vcc_sklist_lock);
}
| 59,192,502,028,530,860,000,000,000,000,000,000,000 | common.c | 105,103,316,668,524,350,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3222 | The vcc_recvmsg function in net/atm/common.c in the Linux kernel before 3.9-rc7 does not initialize a certain length variable, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-3222 |
32,376 | linux | 9b3e617f3df53822345a8573b6d358f6b9e5ed87 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9b3e617f3df53822345a8573b6d358f6b9e5ed87 | atm: update msg_namelen in vcc_recvmsg()
The current code does not fill the msg_name member in case it is set.
It also does not set the msg_namelen member to 0 and therefore makes
net/socket.c leak the local, uninitialized sockaddr_storage variable
to userland -- 128 bytes of kernel stack memory.
Fix that by simply s... | 0 | int vcc_sendmsg(struct kiocb *iocb, struct socket *sock, struct msghdr *m,
size_t total_len)
{
struct sock *sk = sock->sk;
DEFINE_WAIT(wait);
struct atm_vcc *vcc;
struct sk_buff *skb;
int eff, error;
const void __user *buff;
int size;
lock_sock(sk);
if (sock->state != SS_CONNECTED) {
error = -ENOTCONN;
... | 89,528,672,087,595,640,000,000,000,000,000,000,000 | common.c | 105,103,316,668,524,350,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3222 | The vcc_recvmsg function in net/atm/common.c in the Linux kernel before 3.9-rc7 does not initialize a certain length variable, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-3222 |
32,377 | linux | 9b3e617f3df53822345a8573b6d358f6b9e5ed87 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9b3e617f3df53822345a8573b6d358f6b9e5ed87 | atm: update msg_namelen in vcc_recvmsg()
The current code does not fill the msg_name member in case it is set.
It also does not set the msg_namelen member to 0 and therefore makes
net/socket.c leak the local, uninitialized sockaddr_storage variable
to userland -- 128 bytes of kernel stack memory.
Fix that by simply s... | 0 | int vcc_setsockopt(struct socket *sock, int level, int optname,
char __user *optval, unsigned int optlen)
{
struct atm_vcc *vcc;
unsigned long value;
int error;
if (__SO_LEVEL_MATCH(optname, level) && optlen != __SO_SIZE(optname))
return -EINVAL;
vcc = ATM_SD(sock);
switch (optname) {
case SO_ATMQOS:
{... | 317,219,039,499,375,900,000,000,000,000,000,000,000 | common.c | 105,103,316,668,524,350,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3222 | The vcc_recvmsg function in net/atm/common.c in the Linux kernel before 3.9-rc7 does not initialize a certain length variable, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-3222 |
32,378 | linux | 9b3e617f3df53822345a8573b6d358f6b9e5ed87 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9b3e617f3df53822345a8573b6d358f6b9e5ed87 | atm: update msg_namelen in vcc_recvmsg()
The current code does not fill the msg_name member in case it is set.
It also does not set the msg_namelen member to 0 and therefore makes
net/socket.c leak the local, uninitialized sockaddr_storage variable
to userland -- 128 bytes of kernel stack memory.
Fix that by simply s... | 0 | static void vcc_sock_destruct(struct sock *sk)
{
if (atomic_read(&sk->sk_rmem_alloc))
printk(KERN_DEBUG "%s: rmem leakage (%d bytes) detected.\n",
__func__, atomic_read(&sk->sk_rmem_alloc));
if (atomic_read(&sk->sk_wmem_alloc))
printk(KERN_DEBUG "%s: wmem leakage (%d bytes) detected.\n",
__func... | 231,534,879,686,583,000,000,000,000,000,000,000,000 | common.c | 105,103,316,668,524,350,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3222 | The vcc_recvmsg function in net/atm/common.c in the Linux kernel before 3.9-rc7 does not initialize a certain length variable, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-3222 |
32,379 | linux | 9b3e617f3df53822345a8573b6d358f6b9e5ed87 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9b3e617f3df53822345a8573b6d358f6b9e5ed87 | atm: update msg_namelen in vcc_recvmsg()
The current code does not fill the msg_name member in case it is set.
It also does not set the msg_namelen member to 0 and therefore makes
net/socket.c leak the local, uninitialized sockaddr_storage variable
to userland -- 128 bytes of kernel stack memory.
Fix that by simply s... | 0 | static inline int vcc_writable(struct sock *sk)
{
struct atm_vcc *vcc = atm_sk(sk);
return (vcc->qos.txtp.max_sdu +
atomic_read(&sk->sk_wmem_alloc)) <= sk->sk_sndbuf;
}
| 74,717,804,561,704,460,000,000,000,000,000,000,000 | common.c | 105,103,316,668,524,350,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3222 | The vcc_recvmsg function in net/atm/common.c in the Linux kernel before 3.9-rc7 does not initialize a certain length variable, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-3222 |
32,380 | linux | 9b3e617f3df53822345a8573b6d358f6b9e5ed87 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9b3e617f3df53822345a8573b6d358f6b9e5ed87 | atm: update msg_namelen in vcc_recvmsg()
The current code does not fill the msg_name member in case it is set.
It also does not set the msg_namelen member to 0 and therefore makes
net/socket.c leak the local, uninitialized sockaddr_storage variable
to userland -- 128 bytes of kernel stack memory.
Fix that by simply s... | 0 | static void vcc_write_space(struct sock *sk)
{
struct socket_wq *wq;
rcu_read_lock();
if (vcc_writable(sk)) {
wq = rcu_dereference(sk->sk_wq);
if (wq_has_sleeper(wq))
wake_up_interruptible(&wq->wait);
sk_wake_async(sk, SOCK_WAKE_SPACE, POLL_OUT);
}
rcu_read_unlock();
}
| 163,498,722,590,085,270,000,000,000,000,000,000,000 | common.c | 105,103,316,668,524,350,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3222 | The vcc_recvmsg function in net/atm/common.c in the Linux kernel before 3.9-rc7 does not initialize a certain length variable, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-3222 |
32,381 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 0 | static void __exit algif_hash_exit(void)
{
int err = af_alg_unregister_type(&algif_type_hash);
BUG_ON(err);
}
| 326,624,210,308,864,830,000,000,000,000,000,000,000 | algif_hash.c | 274,659,569,534,280,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
32,382 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 0 | static int __init algif_hash_init(void)
{
return af_alg_register_type(&algif_type_hash);
}
| 320,944,972,784,273,500,000,000,000,000,000,000,000 | algif_hash.c | 274,659,569,534,280,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
32,383 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 0 | static int hash_accept_parent(void *private, struct sock *sk)
{
struct hash_ctx *ctx;
struct alg_sock *ask = alg_sk(sk);
unsigned len = sizeof(*ctx) + crypto_ahash_reqsize(private);
unsigned ds = crypto_ahash_digestsize(private);
ctx = sock_kmalloc(sk, len, GFP_KERNEL);
if (!ctx)
return -ENOMEM;
ctx->result ... | 23,727,910,820,066,810,000,000,000,000,000,000,000 | algif_hash.c | 274,659,569,534,280,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
32,384 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 0 | static void *hash_bind(const char *name, u32 type, u32 mask)
{
return crypto_alloc_ahash(name, type, mask);
}
| 309,109,559,685,153,080,000,000,000,000,000,000,000 | algif_hash.c | 274,659,569,534,280,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
32,385 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 0 | static void hash_release(void *private)
{
crypto_free_ahash(private);
}
| 230,408,753,474,746,600,000,000,000,000,000,000,000 | algif_hash.c | 274,659,569,534,280,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
32,386 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 0 | static int hash_sendmsg(struct kiocb *unused, struct socket *sock,
struct msghdr *msg, size_t ignored)
{
int limit = ALG_MAX_PAGES * PAGE_SIZE;
struct sock *sk = sock->sk;
struct alg_sock *ask = alg_sk(sk);
struct hash_ctx *ctx = ask->private;
unsigned long iovlen;
struct iovec *iov;
long copied = 0;
int err... | 261,253,400,889,008,200,000,000,000,000,000,000,000 | algif_hash.c | 274,659,569,534,280,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
32,387 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 0 | static ssize_t hash_sendpage(struct socket *sock, struct page *page,
int offset, size_t size, int flags)
{
struct sock *sk = sock->sk;
struct alg_sock *ask = alg_sk(sk);
struct hash_ctx *ctx = ask->private;
int err;
lock_sock(sk);
sg_init_table(ctx->sgl.sg, 1);
sg_set_page(ctx->sgl.sg, page, size, offse... | 338,917,893,358,097,480,000,000,000,000,000,000,000 | algif_hash.c | 274,659,569,534,280,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
32,388 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 0 | static int hash_setkey(void *private, const u8 *key, unsigned int keylen)
{
return crypto_ahash_setkey(private, key, keylen);
}
| 147,070,203,827,623,530,000,000,000,000,000,000,000 | algif_hash.c | 274,659,569,534,280,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
32,389 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 0 | static void hash_sock_destruct(struct sock *sk)
{
struct alg_sock *ask = alg_sk(sk);
struct hash_ctx *ctx = ask->private;
sock_kfree_s(sk, ctx->result,
crypto_ahash_digestsize(crypto_ahash_reqtfm(&ctx->req)));
sock_kfree_s(sk, ctx, ctx->len);
af_alg_release_parent(sk);
}
| 8,011,995,952,780,395,000,000,000,000,000,000,000 | algif_hash.c | 274,659,569,534,280,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
32,390 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 0 | static void __exit algif_skcipher_exit(void)
{
int err = af_alg_unregister_type(&algif_type_skcipher);
BUG_ON(err);
}
| 209,108,984,436,871,170,000,000,000,000,000,000,000 | algif_skcipher.c | 322,536,590,163,032,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
32,391 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 0 | static int skcipher_accept_parent(void *private, struct sock *sk)
{
struct skcipher_ctx *ctx;
struct alg_sock *ask = alg_sk(sk);
unsigned int len = sizeof(*ctx) + crypto_ablkcipher_reqsize(private);
ctx = sock_kmalloc(sk, len, GFP_KERNEL);
if (!ctx)
return -ENOMEM;
ctx->iv = sock_kmalloc(sk, crypto_ablkcipher... | 220,053,733,644,805,800,000,000,000,000,000,000,000 | algif_skcipher.c | 322,536,590,163,032,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
32,392 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 0 | static int skcipher_alloc_sgl(struct sock *sk)
{
struct alg_sock *ask = alg_sk(sk);
struct skcipher_ctx *ctx = ask->private;
struct skcipher_sg_list *sgl;
struct scatterlist *sg = NULL;
sgl = list_entry(ctx->tsgl.prev, struct skcipher_sg_list, list);
if (!list_empty(&ctx->tsgl))
sg = sgl->sg;
if (!sg || sgl-... | 191,480,504,894,179,570,000,000,000,000,000,000,000 | algif_skcipher.c | 322,536,590,163,032,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
32,393 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 0 | static void *skcipher_bind(const char *name, u32 type, u32 mask)
{
return crypto_alloc_ablkcipher(name, type, mask);
}
| 158,350,728,887,714,880,000,000,000,000,000,000,000 | algif_skcipher.c | 322,536,590,163,032,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
32,394 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 0 | static void skcipher_free_sgl(struct sock *sk)
{
struct alg_sock *ask = alg_sk(sk);
struct skcipher_ctx *ctx = ask->private;
skcipher_pull_sgl(sk, ctx->used);
}
| 32,355,860,785,599,080,000,000,000,000,000,000,000 | algif_skcipher.c | 322,536,590,163,032,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
32,395 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 0 | static unsigned int skcipher_poll(struct file *file, struct socket *sock,
poll_table *wait)
{
struct sock *sk = sock->sk;
struct alg_sock *ask = alg_sk(sk);
struct skcipher_ctx *ctx = ask->private;
unsigned int mask;
sock_poll_wait(file, sk_sleep(sk), wait);
mask = 0;
if (ctx->used)
mask |= POLLIN | PO... | 163,328,299,392,790,040,000,000,000,000,000,000,000 | algif_skcipher.c | 322,536,590,163,032,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
32,396 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 0 | static void skcipher_pull_sgl(struct sock *sk, int used)
{
struct alg_sock *ask = alg_sk(sk);
struct skcipher_ctx *ctx = ask->private;
struct skcipher_sg_list *sgl;
struct scatterlist *sg;
int i;
while (!list_empty(&ctx->tsgl)) {
sgl = list_first_entry(&ctx->tsgl, struct skcipher_sg_list,
list);
s... | 170,137,221,366,080,700,000,000,000,000,000,000,000 | algif_skcipher.c | 322,536,590,163,032,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
32,397 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 0 | static void skcipher_release(void *private)
{
crypto_free_ablkcipher(private);
}
| 107,888,782,665,045,280,000,000,000,000,000,000,000 | algif_skcipher.c | 322,536,590,163,032,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
32,398 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 0 | static int skcipher_sendmsg(struct kiocb *unused, struct socket *sock,
struct msghdr *msg, size_t size)
{
struct sock *sk = sock->sk;
struct alg_sock *ask = alg_sk(sk);
struct skcipher_ctx *ctx = ask->private;
struct crypto_ablkcipher *tfm = crypto_ablkcipher_reqtfm(&ctx->req);
unsigned ivsize = crypto_ablk... | 70,112,858,600,753,540,000,000,000,000,000,000,000 | algif_skcipher.c | 322,536,590,163,032,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
32,399 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 0 | static ssize_t skcipher_sendpage(struct socket *sock, struct page *page,
int offset, size_t size, int flags)
{
struct sock *sk = sock->sk;
struct alg_sock *ask = alg_sk(sk);
struct skcipher_ctx *ctx = ask->private;
struct skcipher_sg_list *sgl;
int err = -EINVAL;
lock_sock(sk);
if (!ctx->more && ctx->used)... | 212,340,345,887,587,000,000,000,000,000,000,000,000 | algif_skcipher.c | 322,536,590,163,032,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
32,400 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 0 | static int skcipher_setkey(void *private, const u8 *key, unsigned int keylen)
{
return crypto_ablkcipher_setkey(private, key, keylen);
}
| 330,705,643,657,178,200,000,000,000,000,000,000,000 | algif_skcipher.c | 322,536,590,163,032,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
32,401 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 0 | static inline int skcipher_sndbuf(struct sock *sk)
{
struct alg_sock *ask = alg_sk(sk);
struct skcipher_ctx *ctx = ask->private;
return max_t(int, max_t(int, sk->sk_sndbuf & PAGE_MASK, PAGE_SIZE) -
ctx->used, 0);
}
| 210,085,881,758,484,660,000,000,000,000,000,000,000 | algif_skcipher.c | 322,536,590,163,032,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
32,402 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 0 | static void skcipher_sock_destruct(struct sock *sk)
{
struct alg_sock *ask = alg_sk(sk);
struct skcipher_ctx *ctx = ask->private;
struct crypto_ablkcipher *tfm = crypto_ablkcipher_reqtfm(&ctx->req);
skcipher_free_sgl(sk);
sock_kfree_s(sk, ctx->iv, crypto_ablkcipher_ivsize(tfm));
sock_kfree_s(sk, ctx, ctx->len);
... | 30,530,974,250,241,436,000,000,000,000,000,000,000 | algif_skcipher.c | 322,536,590,163,032,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
32,403 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 0 | static int skcipher_wait_for_data(struct sock *sk, unsigned flags)
{
struct alg_sock *ask = alg_sk(sk);
struct skcipher_ctx *ctx = ask->private;
long timeout;
DEFINE_WAIT(wait);
int err = -ERESTARTSYS;
if (flags & MSG_DONTWAIT) {
return -EAGAIN;
}
set_bit(SOCK_ASYNC_WAITDATA, &sk->sk_socket->flags);
for (... | 11,333,538,273,033,121,000,000,000,000,000,000,000 | algif_skcipher.c | 322,536,590,163,032,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
32,404 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 0 | static int skcipher_wait_for_wmem(struct sock *sk, unsigned flags)
{
long timeout;
DEFINE_WAIT(wait);
int err = -ERESTARTSYS;
if (flags & MSG_DONTWAIT)
return -EAGAIN;
set_bit(SOCK_ASYNC_NOSPACE, &sk->sk_socket->flags);
for (;;) {
if (signal_pending(current))
break;
prepare_to_wait(sk_sleep(sk), &wait... | 1,908,716,526,850,776,400,000,000,000,000,000,000 | algif_skcipher.c | 322,536,590,163,032,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
32,405 | linux | 72a763d805a48ac8c0bf48fdb510e84c12de51fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/72a763d805a48ac8c0bf48fdb510e84c12de51fe | crypto: algif - suppress sending source address information in recvmsg
The current code does not set the msg_namelen member to 0 and therefore
makes net/socket.c leak the local sockaddr_storage variable to userland
-- 128 bytes of kernel stack memory. Fix that.
Cc: <stable@vger.kernel.org> # 2.6.38
Signed-off-by: Mat... | 0 | static inline bool skcipher_writable(struct sock *sk)
{
return PAGE_SIZE <= skcipher_sndbuf(sk);
}
| 26,111,739,397,323,457,000,000,000,000,000,000,000 | algif_skcipher.c | 322,536,590,163,032,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-3076 | The crypto API in the Linux kernel through 3.9-rc8 does not initialize certain length variables, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call, related to the hash_recvmsg function in crypto/algif_hash.c and the skcipher_recvmsg function ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3076 |
32,406 | linux | 12ae030d54ef250706da5642fc7697cc60ad0df7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/12ae030d54ef250706da5642fc7697cc60ad0df7 | perf/ftrace: Fix paranoid level for enabling function tracer
The current default perf paranoid level is "1" which has
"perf_paranoid_kernel()" return false, and giving any operations that
use it, access to normal users. Unfortunately, this includes function
tracing and normal users should not be allowed to enable func... | 0 | int perf_ftrace_event_register(struct ftrace_event_call *call,
enum trace_reg type, void *data)
{
switch (type) {
case TRACE_REG_REGISTER:
case TRACE_REG_UNREGISTER:
break;
case TRACE_REG_PERF_REGISTER:
case TRACE_REG_PERF_UNREGISTER:
return 0;
case TRACE_REG_PERF_OPEN:
return perf_ftrace_function... | 274,056,081,943,264,130,000,000,000,000,000,000,000 | trace_event_perf.c | 17,968,683,985,346,208,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2930 | The perf_trace_event_perm function in kernel/trace/trace_event_perf.c in the Linux kernel before 3.12.2 does not properly restrict access to the perf subsystem, which allows local users to enable function tracing via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2930 |
32,407 | linux | 12ae030d54ef250706da5642fc7697cc60ad0df7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/12ae030d54ef250706da5642fc7697cc60ad0df7 | perf/ftrace: Fix paranoid level for enabling function tracer
The current default perf paranoid level is "1" which has
"perf_paranoid_kernel()" return false, and giving any operations that
use it, access to normal users. Unfortunately, this includes function
tracing and normal users should not be allowed to enable func... | 0 | perf_ftrace_function_call(unsigned long ip, unsigned long parent_ip,
struct ftrace_ops *ops, struct pt_regs *pt_regs)
{
struct ftrace_entry *entry;
struct hlist_head *head;
struct pt_regs regs;
int rctx;
head = this_cpu_ptr(event_function.perf_events);
if (hlist_empty(head))
return;
#define ENTRY_SIZE (A... | 317,004,018,185,759,560,000,000,000,000,000,000,000 | trace_event_perf.c | 17,968,683,985,346,208,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2930 | The perf_trace_event_perm function in kernel/trace/trace_event_perf.c in the Linux kernel before 3.12.2 does not properly restrict access to the perf subsystem, which allows local users to enable function tracing via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2930 |
32,408 | linux | 12ae030d54ef250706da5642fc7697cc60ad0df7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/12ae030d54ef250706da5642fc7697cc60ad0df7 | perf/ftrace: Fix paranoid level for enabling function tracer
The current default perf paranoid level is "1" which has
"perf_paranoid_kernel()" return false, and giving any operations that
use it, access to normal users. Unfortunately, this includes function
tracing and normal users should not be allowed to enable func... | 0 | static void perf_ftrace_function_disable(struct perf_event *event)
{
ftrace_function_local_disable(&event->ftrace_ops);
}
| 310,821,724,351,611,450,000,000,000,000,000,000,000 | trace_event_perf.c | 17,968,683,985,346,208,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2930 | The perf_trace_event_perm function in kernel/trace/trace_event_perf.c in the Linux kernel before 3.12.2 does not properly restrict access to the perf subsystem, which allows local users to enable function tracing via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2930 |
32,409 | linux | 12ae030d54ef250706da5642fc7697cc60ad0df7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/12ae030d54ef250706da5642fc7697cc60ad0df7 | perf/ftrace: Fix paranoid level for enabling function tracer
The current default perf paranoid level is "1" which has
"perf_paranoid_kernel()" return false, and giving any operations that
use it, access to normal users. Unfortunately, this includes function
tracing and normal users should not be allowed to enable func... | 0 | static void perf_ftrace_function_enable(struct perf_event *event)
{
ftrace_function_local_enable(&event->ftrace_ops);
}
| 259,806,911,794,317,680,000,000,000,000,000,000,000 | trace_event_perf.c | 17,968,683,985,346,208,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2930 | The perf_trace_event_perm function in kernel/trace/trace_event_perf.c in the Linux kernel before 3.12.2 does not properly restrict access to the perf subsystem, which allows local users to enable function tracing via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2930 |
32,410 | linux | 12ae030d54ef250706da5642fc7697cc60ad0df7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/12ae030d54ef250706da5642fc7697cc60ad0df7 | perf/ftrace: Fix paranoid level for enabling function tracer
The current default perf paranoid level is "1" which has
"perf_paranoid_kernel()" return false, and giving any operations that
use it, access to normal users. Unfortunately, this includes function
tracing and normal users should not be allowed to enable func... | 0 | static int perf_ftrace_function_register(struct perf_event *event)
{
struct ftrace_ops *ops = &event->ftrace_ops;
ops->flags |= FTRACE_OPS_FL_CONTROL;
ops->func = perf_ftrace_function_call;
return register_ftrace_function(ops);
}
| 78,316,952,782,647,310,000,000,000,000,000,000,000 | trace_event_perf.c | 17,968,683,985,346,208,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2930 | The perf_trace_event_perm function in kernel/trace/trace_event_perf.c in the Linux kernel before 3.12.2 does not properly restrict access to the perf subsystem, which allows local users to enable function tracing via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2930 |
32,411 | linux | 12ae030d54ef250706da5642fc7697cc60ad0df7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/12ae030d54ef250706da5642fc7697cc60ad0df7 | perf/ftrace: Fix paranoid level for enabling function tracer
The current default perf paranoid level is "1" which has
"perf_paranoid_kernel()" return false, and giving any operations that
use it, access to normal users. Unfortunately, this includes function
tracing and normal users should not be allowed to enable func... | 0 | static int perf_ftrace_function_unregister(struct perf_event *event)
{
struct ftrace_ops *ops = &event->ftrace_ops;
int ret = unregister_ftrace_function(ops);
ftrace_free_filter(ops);
return ret;
}
| 205,716,570,935,778,000,000,000,000,000,000,000,000 | trace_event_perf.c | 17,968,683,985,346,208,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2930 | The perf_trace_event_perm function in kernel/trace/trace_event_perf.c in the Linux kernel before 3.12.2 does not properly restrict access to the perf subsystem, which allows local users to enable function tracing via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2930 |
32,412 | linux | 12ae030d54ef250706da5642fc7697cc60ad0df7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/12ae030d54ef250706da5642fc7697cc60ad0df7 | perf/ftrace: Fix paranoid level for enabling function tracer
The current default perf paranoid level is "1" which has
"perf_paranoid_kernel()" return false, and giving any operations that
use it, access to normal users. Unfortunately, this includes function
tracing and normal users should not be allowed to enable func... | 0 | int perf_trace_add(struct perf_event *p_event, int flags)
{
struct ftrace_event_call *tp_event = p_event->tp_event;
struct hlist_head __percpu *pcpu_list;
struct hlist_head *list;
pcpu_list = tp_event->perf_events;
if (WARN_ON_ONCE(!pcpu_list))
return -EINVAL;
if (!(flags & PERF_EF_START))
p_event->hw.state... | 183,950,344,747,779,660,000,000,000,000,000,000,000 | trace_event_perf.c | 17,968,683,985,346,208,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2930 | The perf_trace_event_perm function in kernel/trace/trace_event_perf.c in the Linux kernel before 3.12.2 does not properly restrict access to the perf subsystem, which allows local users to enable function tracing via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2930 |
32,413 | linux | 12ae030d54ef250706da5642fc7697cc60ad0df7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/12ae030d54ef250706da5642fc7697cc60ad0df7 | perf/ftrace: Fix paranoid level for enabling function tracer
The current default perf paranoid level is "1" which has
"perf_paranoid_kernel()" return false, and giving any operations that
use it, access to normal users. Unfortunately, this includes function
tracing and normal users should not be allowed to enable func... | 0 | __kprobes void *perf_trace_buf_prepare(int size, unsigned short type,
struct pt_regs *regs, int *rctxp)
{
struct trace_entry *entry;
unsigned long flags;
char *raw_data;
int pc;
BUILD_BUG_ON(PERF_MAX_TRACE_SIZE % sizeof(unsigned long));
if (WARN_ONCE(size > PERF_MAX_TRACE_SIZE,
"perf buffer not la... | 251,374,611,077,459,140,000,000,000,000,000,000,000 | trace_event_perf.c | 17,968,683,985,346,208,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2930 | The perf_trace_event_perm function in kernel/trace/trace_event_perf.c in the Linux kernel before 3.12.2 does not properly restrict access to the perf subsystem, which allows local users to enable function tracing via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2930 |
32,414 | linux | 12ae030d54ef250706da5642fc7697cc60ad0df7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/12ae030d54ef250706da5642fc7697cc60ad0df7 | perf/ftrace: Fix paranoid level for enabling function tracer
The current default perf paranoid level is "1" which has
"perf_paranoid_kernel()" return false, and giving any operations that
use it, access to normal users. Unfortunately, this includes function
tracing and normal users should not be allowed to enable func... | 0 | void perf_trace_del(struct perf_event *p_event, int flags)
{
struct ftrace_event_call *tp_event = p_event->tp_event;
hlist_del_rcu(&p_event->hlist_entry);
tp_event->class->reg(tp_event, TRACE_REG_PERF_DEL, p_event);
}
| 245,576,118,888,359,970,000,000,000,000,000,000,000 | trace_event_perf.c | 17,968,683,985,346,208,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2930 | The perf_trace_event_perm function in kernel/trace/trace_event_perf.c in the Linux kernel before 3.12.2 does not properly restrict access to the perf subsystem, which allows local users to enable function tracing via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2930 |
32,415 | linux | 12ae030d54ef250706da5642fc7697cc60ad0df7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/12ae030d54ef250706da5642fc7697cc60ad0df7 | perf/ftrace: Fix paranoid level for enabling function tracer
The current default perf paranoid level is "1" which has
"perf_paranoid_kernel()" return false, and giving any operations that
use it, access to normal users. Unfortunately, this includes function
tracing and normal users should not be allowed to enable func... | 0 | void perf_trace_destroy(struct perf_event *p_event)
{
mutex_lock(&event_mutex);
perf_trace_event_close(p_event);
perf_trace_event_unreg(p_event);
mutex_unlock(&event_mutex);
}
| 153,499,714,488,875,290,000,000,000,000,000,000,000 | trace_event_perf.c | 17,968,683,985,346,208,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2930 | The perf_trace_event_perm function in kernel/trace/trace_event_perf.c in the Linux kernel before 3.12.2 does not properly restrict access to the perf subsystem, which allows local users to enable function tracing via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2930 |
32,416 | linux | 12ae030d54ef250706da5642fc7697cc60ad0df7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/12ae030d54ef250706da5642fc7697cc60ad0df7 | perf/ftrace: Fix paranoid level for enabling function tracer
The current default perf paranoid level is "1" which has
"perf_paranoid_kernel()" return false, and giving any operations that
use it, access to normal users. Unfortunately, this includes function
tracing and normal users should not be allowed to enable func... | 0 | static void perf_trace_event_close(struct perf_event *p_event)
{
struct ftrace_event_call *tp_event = p_event->tp_event;
tp_event->class->reg(tp_event, TRACE_REG_PERF_CLOSE, p_event);
}
| 94,628,861,525,554,470,000,000,000,000,000,000,000 | trace_event_perf.c | 17,968,683,985,346,208,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2930 | The perf_trace_event_perm function in kernel/trace/trace_event_perf.c in the Linux kernel before 3.12.2 does not properly restrict access to the perf subsystem, which allows local users to enable function tracing via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2930 |
32,417 | linux | 12ae030d54ef250706da5642fc7697cc60ad0df7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/12ae030d54ef250706da5642fc7697cc60ad0df7 | perf/ftrace: Fix paranoid level for enabling function tracer
The current default perf paranoid level is "1" which has
"perf_paranoid_kernel()" return false, and giving any operations that
use it, access to normal users. Unfortunately, this includes function
tracing and normal users should not be allowed to enable func... | 0 | static int perf_trace_event_open(struct perf_event *p_event)
{
struct ftrace_event_call *tp_event = p_event->tp_event;
return tp_event->class->reg(tp_event, TRACE_REG_PERF_OPEN, p_event);
}
| 59,982,581,065,850,250,000,000,000,000,000,000,000 | trace_event_perf.c | 17,968,683,985,346,208,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2930 | The perf_trace_event_perm function in kernel/trace/trace_event_perf.c in the Linux kernel before 3.12.2 does not properly restrict access to the perf subsystem, which allows local users to enable function tracing via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2930 |
32,418 | linux | 12ae030d54ef250706da5642fc7697cc60ad0df7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/12ae030d54ef250706da5642fc7697cc60ad0df7 | perf/ftrace: Fix paranoid level for enabling function tracer
The current default perf paranoid level is "1" which has
"perf_paranoid_kernel()" return false, and giving any operations that
use it, access to normal users. Unfortunately, this includes function
tracing and normal users should not be allowed to enable func... | 0 | static int perf_trace_event_reg(struct ftrace_event_call *tp_event,
struct perf_event *p_event)
{
struct hlist_head __percpu *list;
int ret = -ENOMEM;
int cpu;
p_event->tp_event = tp_event;
if (tp_event->perf_refcount++ > 0)
return 0;
list = alloc_percpu(struct hlist_head);
if (!list)
goto fail;
for_... | 183,870,025,001,714,620,000,000,000,000,000,000,000 | trace_event_perf.c | 17,968,683,985,346,208,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2930 | The perf_trace_event_perm function in kernel/trace/trace_event_perf.c in the Linux kernel before 3.12.2 does not properly restrict access to the perf subsystem, which allows local users to enable function tracing via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2930 |
32,419 | linux | 12ae030d54ef250706da5642fc7697cc60ad0df7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/12ae030d54ef250706da5642fc7697cc60ad0df7 | perf/ftrace: Fix paranoid level for enabling function tracer
The current default perf paranoid level is "1" which has
"perf_paranoid_kernel()" return false, and giving any operations that
use it, access to normal users. Unfortunately, this includes function
tracing and normal users should not be allowed to enable func... | 0 | static void perf_trace_event_unreg(struct perf_event *p_event)
{
struct ftrace_event_call *tp_event = p_event->tp_event;
int i;
if (--tp_event->perf_refcount > 0)
goto out;
tp_event->class->reg(tp_event, TRACE_REG_PERF_UNREGISTER, NULL);
/*
* Ensure our callback won't be called anymore. The buffers
* will... | 145,899,067,151,165,740,000,000,000,000,000,000,000 | trace_event_perf.c | 17,968,683,985,346,208,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2930 | The perf_trace_event_perm function in kernel/trace/trace_event_perf.c in the Linux kernel before 3.12.2 does not properly restrict access to the perf subsystem, which allows local users to enable function tracing via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2930 |
32,420 | linux | 12ae030d54ef250706da5642fc7697cc60ad0df7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/12ae030d54ef250706da5642fc7697cc60ad0df7 | perf/ftrace: Fix paranoid level for enabling function tracer
The current default perf paranoid level is "1" which has
"perf_paranoid_kernel()" return false, and giving any operations that
use it, access to normal users. Unfortunately, this includes function
tracing and normal users should not be allowed to enable func... | 0 | int perf_trace_init(struct perf_event *p_event)
{
struct ftrace_event_call *tp_event;
int event_id = p_event->attr.config;
int ret = -EINVAL;
mutex_lock(&event_mutex);
list_for_each_entry(tp_event, &ftrace_events, list) {
if (tp_event->event.type == event_id &&
tp_event->class && tp_event->class->reg &&
... | 108,048,357,792,441,700,000,000,000,000,000,000,000 | trace_event_perf.c | 17,968,683,985,346,208,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2930 | The perf_trace_event_perm function in kernel/trace/trace_event_perf.c in the Linux kernel before 3.12.2 does not properly restrict access to the perf subsystem, which allows local users to enable function tracing via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2930 |
32,421 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | SYSCALL_DEFINE1(uselib, const char __user *, library)
{
struct file *file;
struct filename *tmp = getname(library);
int error = PTR_ERR(tmp);
static const struct open_flags uselib_flags = {
.open_flag = O_LARGEFILE | O_RDONLY | __FMODE_EXEC,
.acc_mode = MAY_READ | MAY_EXEC | MAY_OPEN,
.intent = LOOKUP_OPEN,
... | 255,303,131,109,739,570,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,422 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | SYSCALL_DEFINE3(execve,
const char __user *, filename,
const char __user *const __user *, argv,
const char __user *const __user *, envp)
{
struct filename *path = getname(filename);
int error = PTR_ERR(path);
if (!IS_ERR(path)) {
error = do_execve(path->name, argv, envp);
putname(path);
}
return error;
}... | 90,375,289,875,587,160,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,423 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | static int __bprm_mm_init(struct linux_binprm *bprm)
{
int err;
struct vm_area_struct *vma = NULL;
struct mm_struct *mm = bprm->mm;
bprm->vma = vma = kmem_cache_zalloc(vm_area_cachep, GFP_KERNEL);
if (!vma)
return -ENOMEM;
down_write(&mm->mmap_sem);
vma->vm_mm = mm;
/*
* Place the stack at the largest st... | 136,532,939,064,880,830,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,424 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | static int __bprm_mm_init(struct linux_binprm *bprm)
{
bprm->p = PAGE_SIZE * MAX_ARG_PAGES - sizeof(void *);
return 0;
}
| 17,969,997,652,701,835,000,000,000,000,000,000,000 | exec.c | 186,853,442,526,040,300,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,425 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | int __get_dumpable(unsigned long mm_flags)
{
int ret;
ret = mm_flags & MMF_DUMPABLE_MASK;
return (ret > SUID_DUMP_USER) ? SUID_DUMP_ROOT : ret;
}
| 182,266,520,214,612,400,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,426 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | void __register_binfmt(struct linux_binfmt * fmt, int insert)
{
BUG_ON(!fmt);
if (WARN_ON(!fmt->load_binary))
return;
write_lock(&binfmt_lock);
insert ? list_add(&fmt->lh, &formats) :
list_add_tail(&fmt->lh, &formats);
write_unlock(&binfmt_lock);
}
| 311,920,105,701,502,640,000,000,000,000,000,000,000 | exec.c | 186,853,442,526,040,300,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,427 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | static void acct_arg_size(struct linux_binprm *bprm, unsigned long pages)
{
struct mm_struct *mm = current->mm;
long diff = (long)(pages - bprm->vma_pages);
if (!mm || !diff)
return;
bprm->vma_pages = pages;
add_mm_counter(mm, MM_ANONPAGES, diff);
}
| 31,936,467,476,640,723,000,000,000,000,000,000,000 | exec.c | 186,853,442,526,040,300,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,428 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | static inline void acct_arg_size(struct linux_binprm *bprm, unsigned long pages)
{
}
| 251,143,456,176,608,300,000,000,000,000,000,000,000 | exec.c | 186,853,442,526,040,300,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,429 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | int bprm_change_interp(char *interp, struct linux_binprm *bprm)
{
/* If a binfmt changed the interp, free it first. */
if (bprm->interp != bprm->filename)
kfree(bprm->interp);
bprm->interp = kstrdup(interp, GFP_KERNEL);
if (!bprm->interp)
return -ENOMEM;
return 0;
}
| 34,895,327,609,647,007,000,000,000,000,000,000,000 | exec.c | 186,853,442,526,040,300,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,430 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | static int check_unsafe_exec(struct linux_binprm *bprm)
{
struct task_struct *p = current, *t;
unsigned n_fs;
int res = 0;
if (p->ptrace) {
if (p->ptrace & PT_PTRACE_CAP)
bprm->unsafe |= LSM_UNSAFE_PTRACE_CAP;
else
bprm->unsafe |= LSM_UNSAFE_PTRACE;
}
/*
* This isn't strictly necessary, but it makes... | 235,749,435,145,174,800,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,431 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | static int compat_do_execve(const char *filename,
const compat_uptr_t __user *__argv,
const compat_uptr_t __user *__envp)
{
struct user_arg_ptr argv = {
.is_compat = true,
.ptr.compat = __argv,
};
struct user_arg_ptr envp = {
.is_compat = true,
.ptr.compat = __envp,
};
return do_execve_common(filename, a... | 202,395,569,185,015,730,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,432 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | asmlinkage long compat_sys_execve(const char __user * filename,
const compat_uptr_t __user * argv,
const compat_uptr_t __user * envp)
{
struct filename *path = getname(filename);
int error = PTR_ERR(path);
if (!IS_ERR(path)) {
error = compat_do_execve(path->name, argv, envp);
putname(path);
}
return error;
}... | 258,444,903,866,947,860,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,433 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | static int copy_strings(int argc, struct user_arg_ptr argv,
struct linux_binprm *bprm)
{
struct page *kmapped_page = NULL;
char *kaddr = NULL;
unsigned long kpos = 0;
int ret;
while (argc-- > 0) {
const char __user *str;
int len;
unsigned long pos;
ret = -EFAULT;
str = get_user_arg_ptr(argv, argc);
... | 158,987,767,292,924,980,000,000,000,000,000,000,000 | exec.c | 186,853,442,526,040,300,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,434 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | int copy_strings_kernel(int argc, const char *const *__argv,
struct linux_binprm *bprm)
{
int r;
mm_segment_t oldfs = get_fs();
struct user_arg_ptr argv = {
.ptr.native = (const char __user *const __user *)__argv,
};
set_fs(KERNEL_DS);
r = copy_strings(argc, argv, bprm);
set_fs(oldfs);
return r;
}
| 106,584,181,123,179,300,000,000,000,000,000,000,000 | exec.c | 186,853,442,526,040,300,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,435 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | static int count(struct user_arg_ptr argv, int max)
{
int i = 0;
if (argv.ptr.native != NULL) {
for (;;) {
const char __user *p = get_user_arg_ptr(argv, i);
if (!p)
break;
if (IS_ERR(p))
return -EFAULT;
if (i >= max)
return -E2BIG;
++i;
if (fatal_signal_pending(current))
retur... | 146,108,405,788,662,900,000,000,000,000,000,000,000 | exec.c | 186,853,442,526,040,300,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,436 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | static int de_thread(struct task_struct *tsk)
{
struct signal_struct *sig = tsk->signal;
struct sighand_struct *oldsighand = tsk->sighand;
spinlock_t *lock = &oldsighand->siglock;
if (thread_group_empty(tsk))
goto no_thread_group;
/*
* Kill all other threads in the thread group.
*/
spin_lock_irq(lock);
i... | 4,341,094,242,792,878,400,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,437 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | int do_execve(const char *filename,
const char __user *const __user *__argv,
const char __user *const __user *__envp)
{
struct user_arg_ptr argv = { .ptr.native = __argv };
struct user_arg_ptr envp = { .ptr.native = __envp };
return do_execve_common(filename, argv, envp);
}
| 333,489,141,338,629,430,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,438 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | static int do_execve_common(const char *filename,
struct user_arg_ptr argv,
struct user_arg_ptr envp)
{
struct linux_binprm *bprm;
struct file *file;
struct files_struct *displaced;
bool clear_in_exec;
int retval;
/*
* We move the actual failure in case of RLIMIT_NPROC excess from
* set*uid() to exec... | 94,353,977,222,173,800,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,439 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | static int exec_binprm(struct linux_binprm *bprm)
{
pid_t old_pid, old_vpid;
int ret;
/* Need to fetch pid before load_binary changes it */
old_pid = current->pid;
rcu_read_lock();
old_vpid = task_pid_nr_ns(current, task_active_pid_ns(current->parent));
rcu_read_unlock();
ret = search_binary_handler(bprm);
i... | 235,305,339,630,383,300,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,440 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | static int exec_mmap(struct mm_struct *mm)
{
struct task_struct *tsk;
struct mm_struct * old_mm, *active_mm;
/* Notify parent that we're no longer interested in the old VM */
tsk = current;
old_mm = current->mm;
mm_release(tsk, old_mm);
if (old_mm) {
sync_mm_rss(old_mm);
/*
* Make sure that if there is ... | 320,014,632,828,033,550,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,441 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | static void filename_to_taskname(char *tcomm, const char *fn, unsigned int len)
{
int i, ch;
/* Copies the binary name from after last slash */
for (i = 0; (ch = *(fn++)) != '\0';) {
if (ch == '/')
i = 0; /* overwrite what we wrote */
else
if (i < len - 1)
tcomm[i++] = ch;
}
tcomm[i] = '\0';
}
| 282,708,652,321,908,070,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,442 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | static void flush_arg_page(struct linux_binprm *bprm, unsigned long pos,
struct page *page)
{
flush_cache_page(bprm->vma, pos, page_to_pfn(page));
}
| 106,302,646,153,558,950,000,000,000,000,000,000,000 | exec.c | 186,853,442,526,040,300,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,443 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | static void flush_arg_page(struct linux_binprm *bprm, unsigned long pos,
struct page *page)
{
}
| 316,480,774,344,869,960,000,000,000,000,000,000,000 | exec.c | 186,853,442,526,040,300,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,444 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | int flush_old_exec(struct linux_binprm * bprm)
{
int retval;
/*
* Make sure we have a private signal table and that
* we are unassociated from the previous thread group.
*/
retval = de_thread(current);
if (retval)
goto out;
set_mm_exe_file(bprm->mm, bprm->file);
filename_to_taskname(bprm->tcomm, bprm->... | 40,613,958,417,519,910,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,445 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | static void free_arg_page(struct linux_binprm *bprm, int i)
{
}
| 210,462,033,441,448,640,000,000,000,000,000,000,000 | exec.c | 308,031,869,849,184,730,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,446 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | static void free_arg_page(struct linux_binprm *bprm, int i)
{
if (bprm->page[i]) {
__free_page(bprm->page[i]);
bprm->page[i] = NULL;
}
}
| 191,758,725,538,843,980,000,000,000,000,000,000,000 | exec.c | 186,853,442,526,040,300,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,447 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | static void free_arg_pages(struct linux_binprm *bprm)
{
}
| 266,858,809,968,290,220,000,000,000,000,000,000,000 | exec.c | 186,853,442,526,040,300,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,448 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | static void free_arg_pages(struct linux_binprm *bprm)
{
int i;
for (i = 0; i < MAX_ARG_PAGES; i++)
free_arg_page(bprm, i);
}
| 104,118,278,279,983,380,000,000,000,000,000,000,000 | exec.c | 186,853,442,526,040,300,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,449 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | void free_bprm(struct linux_binprm *bprm)
{
free_arg_pages(bprm);
if (bprm->cred) {
mutex_unlock(¤t->signal->cred_guard_mutex);
abort_creds(bprm->cred);
}
/* If a binfmt changed the interp, free it. */
if (bprm->interp != bprm->filename)
kfree(bprm->interp);
kfree(bprm);
}
| 271,337,475,248,874,050,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,450 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | static struct page *get_arg_page(struct linux_binprm *bprm, unsigned long pos,
int write)
{
struct page *page;
int ret;
#ifdef CONFIG_STACK_GROWSUP
if (write) {
ret = expand_downwards(bprm->vma, pos);
if (ret < 0)
return NULL;
}
#endif
ret = get_user_pages(current, bprm->mm, pos,
1, write, 1, &page, N... | 37,131,983,142,753,880,000,000,000,000,000,000,000 | exec.c | 308,031,869,849,184,730,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,451 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | static struct page *get_arg_page(struct linux_binprm *bprm, unsigned long pos,
int write)
{
struct page *page;
page = bprm->page[pos / PAGE_SIZE];
if (!page && write) {
page = alloc_page(GFP_HIGHUSER|__GFP_ZERO);
if (!page)
return NULL;
bprm->page[pos / PAGE_SIZE] = page;
}
return page;
}
| 93,865,760,830,095,320,000,000,000,000,000,000,000 | exec.c | 186,853,442,526,040,300,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,452 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | int get_dumpable(struct mm_struct *mm)
{
return __get_dumpable(mm->flags);
}
| 305,467,129,273,615,380,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,453 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | char *get_task_comm(char *buf, struct task_struct *tsk)
{
/* buf must be at least sizeof(tsk->comm) in size */
task_lock(tsk);
strncpy(buf, tsk->comm, sizeof(tsk->comm));
task_unlock(tsk);
return buf;
}
| 3,087,692,218,245,549,000,000,000,000,000,000,000 | exec.c | 186,853,442,526,040,300,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,454 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | static const char __user *get_user_arg_ptr(struct user_arg_ptr argv, int nr)
{
const char __user *native;
#ifdef CONFIG_COMPAT
if (unlikely(argv.is_compat)) {
compat_uptr_t compat;
if (get_user(compat, argv.ptr.compat + nr))
return ERR_PTR(-EFAULT);
return compat_ptr(compat);
}
#endif
if (get_user(nati... | 90,128,697,859,786,900,000,000,000,000,000,000,000 | exec.c | 186,853,442,526,040,300,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,455 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | void install_exec_creds(struct linux_binprm *bprm)
{
security_bprm_committing_creds(bprm);
commit_creds(bprm->cred);
bprm->cred = NULL;
/*
* Disable monitoring for regular users
* when executing setuid binaries. Must
* wait until new credentials are committed
* by commit_creds() above
*/
if (get_dumpab... | 218,740,386,456,446,570,000,000,000,000,000,000,000 | exec.c | 186,853,442,526,040,300,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,456 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | int kernel_read(struct file *file, loff_t offset,
char *addr, unsigned long count)
{
mm_segment_t old_fs;
loff_t pos = offset;
int result;
old_fs = get_fs();
set_fs(get_ds());
/* The cast to a user pointer is valid due to the set_fs() */
result = vfs_read(file, (void __user *)addr, count, &pos);
set_fs(old_f... | 136,846,451,765,104,520,000,000,000,000,000,000,000 | exec.c | 186,853,442,526,040,300,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,457 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | struct file *open_exec(const char *name)
{
struct file *file;
int err;
struct filename tmp = { .name = name };
static const struct open_flags open_exec_flags = {
.open_flag = O_LARGEFILE | O_RDONLY | __FMODE_EXEC,
.acc_mode = MAY_EXEC | MAY_OPEN,
.intent = LOOKUP_OPEN,
.lookup_flags = LOOKUP_FOLLOW,
};
f... | 318,056,545,170,452,970,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,458 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | int prepare_binprm(struct linux_binprm *bprm)
{
umode_t mode;
struct inode * inode = file_inode(bprm->file);
int retval;
mode = inode->i_mode;
if (bprm->file->f_op == NULL)
return -EACCES;
/* clear any previous set[ug]id data from a previous binary */
bprm->cred->euid = current_euid();
bprm->cred->egid = cu... | 5,633,802,467,116,254,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,459 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | static void put_arg_page(struct page *page)
{
put_page(page);
}
| 254,943,294,055,741,080,000,000,000,000,000,000,000 | exec.c | 186,853,442,526,040,300,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,460 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | static inline void put_binfmt(struct linux_binfmt * fmt)
{
module_put(fmt->module);
}
| 87,528,572,440,147,950,000,000,000,000,000,000,000 | exec.c | 186,853,442,526,040,300,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,461 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | ssize_t read_code(struct file *file, unsigned long addr, loff_t pos, size_t len)
{
ssize_t res = file->f_op->read(file, (void __user *)addr, len, &pos);
if (res > 0)
flush_icache_range(addr, addr + len);
return res;
}
| 94,358,312,864,024,250,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
32,462 | linux | d049f74f2dbe71354d43d393ac3a188947811348 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d049f74f2dbe71354d43d393ac3a188947811348 | exec/ptrace: fix get_dumpable() incorrect tests
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for non-SUID_DUMP_USER(1) rather than
SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a
protected state. Almost all places did this correctly, excepti... | 0 | int remove_arg_zero(struct linux_binprm *bprm)
{
int ret = 0;
unsigned long offset;
char *kaddr;
struct page *page;
if (!bprm->argc)
return 0;
do {
offset = bprm->p & ~PAGE_MASK;
page = get_arg_page(bprm, bprm->p, 0);
if (!page) {
ret = -EFAULT;
goto out;
}
kaddr = kmap_atomic(page);
for (;... | 213,566,439,928,922,000,000,000,000,000,000,000,000 | exec.c | 308,031,869,849,184,730,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2929 | The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h. | https://nvd.nist.gov/vuln/detail/CVE-2013-2929 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.