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,463 | 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 search_binary_handler(struct linux_binprm *bprm)
{
bool need_retry = IS_ENABLED(CONFIG_MODULES);
struct linux_binfmt *fmt;
int retval;
/* This allows 4 levels of binfmt rewrites before failing hard. */
if (bprm->recursion_depth > 5)
return -ELOOP;
retval = security_bprm_check(bprm);
if (retval)
return ... | 254,880,014,290,718,340,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,464 | 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 set_binfmt(struct linux_binfmt *new)
{
struct mm_struct *mm = current->mm;
if (mm->binfmt)
module_put(mm->binfmt->module);
mm->binfmt = new;
if (new)
__module_get(new->module);
}
| 52,008,152,901,866,770,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,465 | 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 set_dumpable(struct mm_struct *mm, int value)
{
switch (value) {
case SUID_DUMP_DISABLE:
clear_bit(MMF_DUMPABLE, &mm->flags);
smp_wmb();
clear_bit(MMF_DUMP_SECURELY, &mm->flags);
break;
case SUID_DUMP_USER:
set_bit(MMF_DUMPABLE, &mm->flags);
smp_wmb();
clear_bit(MMF_DUMP_SECURELY, &mm->flags);
b... | 56,555,344,195,112,180,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,466 | 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 set_task_comm(struct task_struct *tsk, char *buf)
{
task_lock(tsk);
trace_task_rename(tsk, buf);
strlcpy(tsk->comm, buf, sizeof(tsk->comm));
task_unlock(tsk);
perf_event_comm(tsk);
}
| 176,361,018,394,869,000,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,467 | 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 setup_arg_pages(struct linux_binprm *bprm,
unsigned long stack_top,
int executable_stack)
{
unsigned long ret;
unsigned long stack_shift;
struct mm_struct *mm = current->mm;
struct vm_area_struct *vma = bprm->vma;
struct vm_area_struct *prev = NULL;
unsigned long vm_flags;
unsigned long stack_bas... | 318,828,516,615,163,200,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,468 | 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 setup_new_exec(struct linux_binprm * bprm)
{
arch_pick_mmap_layout(current->mm);
/* This is the point of no return */
current->sas_ss_sp = current->sas_ss_size = 0;
if (uid_eq(current_euid(), current_uid()) && gid_eq(current_egid(), current_gid()))
set_dumpable(current->mm, SUID_DUMP_USER);
else
set_dum... | 176,940,465,179,121,640,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,469 | 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 unregister_binfmt(struct linux_binfmt * fmt)
{
write_lock(&binfmt_lock);
list_del(&fmt->lh);
write_unlock(&binfmt_lock);
}
| 190,069,638,108,715,400,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,470 | 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 bool valid_arg_len(struct linux_binprm *bprm, long len)
{
return len <= MAX_ARG_STRLEN;
}
| 246,080,825,716,887,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,471 | 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 bool valid_arg_len(struct linux_binprm *bprm, long len)
{
return len <= bprm->p;
}
| 17,242,778,922,935,030,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,472 | 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 would_dump(struct linux_binprm *bprm, struct file *file)
{
if (inode_permission(file_inode(file), MAY_READ) < 0)
bprm->interp_flags |= BINPRM_FLAGS_ENFORCE_NONDUMP;
}
| 168,464,502,780,276,020,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,473 | 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 bool __ptrace_detach(struct task_struct *tracer, struct task_struct *p)
{
bool dead;
__ptrace_unlink(p);
if (p->exit_state != EXIT_ZOMBIE)
return false;
dead = !thread_group_leader(p);
if (!dead && thread_group_empty(p)) {
if (!same_thread_group(p->real_parent, tracer))
dead = do_notify_parent(p,... | 189,174,819,411,549,350,000,000,000,000,000,000,000 | ptrace.c | 269,111,176,348,979,430,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,474 | 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 __ptrace_link(struct task_struct *child, struct task_struct *new_parent)
{
BUG_ON(!list_empty(&child->ptrace_entry));
list_add(&child->ptrace_entry, &new_parent->ptraced);
child->parent = new_parent;
}
| 108,866,843,771,620,100,000,000,000,000,000,000,000 | ptrace.c | 316,279,739,902,479,560,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,475 | 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 __ptrace_unlink(struct task_struct *child)
{
BUG_ON(!child->ptrace);
child->ptrace = 0;
child->parent = child->real_parent;
list_del_init(&child->ptrace_entry);
spin_lock(&child->sighand->siglock);
/*
* Clear all pending traps and TRAPPING. TRAPPING should be
* cleared regardless of JOBCTL_STOP_PENDI... | 220,966,642,556,722,640,000,000,000,000,000,000,000 | ptrace.c | 316,279,739,902,479,560,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,476 | 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 compat_ptrace_request(struct task_struct *child, compat_long_t request,
compat_ulong_t addr, compat_ulong_t data)
{
compat_ulong_t __user *datap = compat_ptr(data);
compat_ulong_t word;
siginfo_t siginfo;
int ret;
switch (request) {
case PTRACE_PEEKTEXT:
case PTRACE_PEEKDATA:
ret = access_process_vm(... | 186,412,952,506,678,840,000,000,000,000,000,000,000 | ptrace.c | 316,279,739,902,479,560,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,477 | 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_ptrace(compat_long_t request, compat_long_t pid,
compat_long_t addr, compat_long_t data)
{
struct task_struct *child;
long ret;
if (request == PTRACE_TRACEME) {
ret = ptrace_traceme();
goto out;
}
child = ptrace_get_task_struct(pid);
if (IS_ERR(child)) {
ret = PTR_ERR(chil... | 318,712,719,924,699,830,000,000,000,000,000,000,000 | ptrace.c | 316,279,739,902,479,560,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,478 | 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 | find_regset(const struct user_regset_view *view, unsigned int type)
{
const struct user_regset *regset;
int n;
for (n = 0; n < view->n; ++n) {
regset = view->regsets + n;
if (regset->core_note_type == type)
return regset;
}
return NULL;
}
| 93,549,786,321,077,380,000,000,000,000,000,000,000 | ptrace.c | 269,111,176,348,979,430,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,479 | 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 generic_ptrace_peekdata(struct task_struct *tsk, unsigned long addr,
unsigned long data)
{
unsigned long tmp;
int copied;
copied = access_process_vm(tsk, addr, &tmp, sizeof(tmp), 0);
if (copied != sizeof(tmp))
return -EIO;
return put_user(tmp, (unsigned long __user *)data);
}
| 163,700,568,135,255,170,000,000,000,000,000,000,000 | ptrace.c | 316,279,739,902,479,560,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,480 | 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 generic_ptrace_pokedata(struct task_struct *tsk, unsigned long addr,
unsigned long data)
{
int copied;
copied = access_process_vm(tsk, addr, &data, sizeof(data), 1);
return (copied == sizeof(data)) ? 0 : -EIO;
}
| 135,250,489,048,026,920,000,000,000,000,000,000,000 | ptrace.c | 316,279,739,902,479,560,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,481 | 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 ptrace_attach(struct task_struct *task, long request,
unsigned long addr,
unsigned long flags)
{
bool seize = (request == PTRACE_SEIZE);
int retval;
retval = -EIO;
if (seize) {
if (addr != 0)
goto out;
if (flags & ~(unsigned long)PTRACE_O_MASK)
goto out;
flags = PT_PTRACED | PT_SEIZE... | 435,702,909,541,135,800,000,000,000,000,000,000 | ptrace.c | 316,279,739,902,479,560,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,482 | 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 ptrace_check_attach(struct task_struct *child, bool ignore_state)
{
int ret = -ESRCH;
/*
* We take the read lock around doing both checks to close a
* possible race where someone else was tracing our child and
* detached between these two checks. After this locked check,
* we are sure that this i... | 102,448,781,139,793,820,000,000,000,000,000,000,000 | ptrace.c | 269,111,176,348,979,430,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,483 | 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 task_struct *ptrace_get_task_struct(pid_t pid)
{
struct task_struct *child;
rcu_read_lock();
child = find_task_by_vpid(pid);
if (child)
get_task_struct(child);
rcu_read_unlock();
if (!child)
return ERR_PTR(-ESRCH);
return child;
}
| 254,519,400,956,428,300,000,000,000,000,000,000,000 | ptrace.c | 316,279,739,902,479,560,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,484 | 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 ptrace_getsiginfo(struct task_struct *child, siginfo_t *info)
{
unsigned long flags;
int error = -ESRCH;
if (lock_task_sighand(child, &flags)) {
error = -EINVAL;
if (likely(child->last_siginfo != NULL)) {
*info = *child->last_siginfo;
error = 0;
}
unlock_task_sighand(child, &flags);
}
ret... | 27,163,593,518,638,175,000,000,000,000,000,000,000 | ptrace.c | 316,279,739,902,479,560,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,485 | 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 ptrace_has_cap(struct user_namespace *ns, unsigned int mode)
{
if (mode & PTRACE_MODE_NOAUDIT)
return has_ns_capability_noaudit(current, ns, CAP_SYS_PTRACE);
else
return has_ns_capability(current, ns, CAP_SYS_PTRACE);
}
| 167,609,354,675,023,200,000,000,000,000,000,000,000 | ptrace.c | 269,111,176,348,979,430,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,486 | 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 | bool ptrace_may_access(struct task_struct *task, unsigned int mode)
{
int err;
task_lock(task);
err = __ptrace_may_access(task, mode);
task_unlock(task);
return !err;
}
| 124,476,777,935,941,770,000,000,000,000,000,000,000 | ptrace.c | 269,111,176,348,979,430,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,487 | 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 ptrace_peek_siginfo(struct task_struct *child,
unsigned long addr,
unsigned long data)
{
struct ptrace_peeksiginfo_args arg;
struct sigpending *pending;
struct sigqueue *q;
int ret, i;
ret = copy_from_user(&arg, (void __user *) addr,
sizeof(struct ptrace_peeksiginfo_args));
if (ret)
retu... | 86,203,809,125,878,740,000,000,000,000,000,000,000 | ptrace.c | 316,279,739,902,479,560,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,488 | 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 ptrace_readdata(struct task_struct *tsk, unsigned long src, char __user *dst, int len)
{
int copied = 0;
while (len > 0) {
char buf[128];
int this_len, retval;
this_len = (len > sizeof(buf)) ? sizeof(buf) : len;
retval = access_process_vm(tsk, src, buf, this_len, 0);
if (!retval) {
if (copied)
... | 114,891,443,411,032,400,000,000,000,000,000,000,000 | ptrace.c | 316,279,739,902,479,560,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,489 | 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 ptrace_regset(struct task_struct *task, int req, unsigned int type,
struct iovec *kiov)
{
const struct user_regset_view *view = task_user_regset_view(task);
const struct user_regset *regset = find_regset(view, type);
int regset_no;
if (!regset || (kiov->iov_len % regset->size) != 0)
return -EINVAL... | 249,657,205,818,064,000,000,000,000,000,000,000,000 | ptrace.c | 269,111,176,348,979,430,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,490 | 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 ptrace_request(struct task_struct *child, long request,
unsigned long addr, unsigned long data)
{
bool seized = child->ptrace & PT_SEIZED;
int ret = -EIO;
siginfo_t siginfo, *si;
void __user *datavp = (void __user *) data;
unsigned long __user *datalp = datavp;
unsigned long flags;
switch (request) {
... | 139,459,394,384,146,720,000,000,000,000,000,000,000 | ptrace.c | 316,279,739,902,479,560,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,491 | 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 ptrace_setoptions(struct task_struct *child, unsigned long data)
{
unsigned flags;
if (data & ~(unsigned long)PTRACE_O_MASK)
return -EINVAL;
/* Avoid intermediate state when all opts are cleared */
flags = child->ptrace;
flags &= ~(PTRACE_O_MASK << PT_OPT_FLAG_SHIFT);
flags |= (data << PT_OPT_FLAG_... | 180,116,075,193,698,700,000,000,000,000,000,000,000 | ptrace.c | 316,279,739,902,479,560,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,492 | 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 ptrace_setsiginfo(struct task_struct *child, const siginfo_t *info)
{
unsigned long flags;
int error = -ESRCH;
if (lock_task_sighand(child, &flags)) {
error = -EINVAL;
if (likely(child->last_siginfo != NULL)) {
*child->last_siginfo = *info;
error = 0;
}
unlock_task_sighand(child, &flags);
... | 304,520,062,530,758,860,000,000,000,000,000,000,000 | ptrace.c | 316,279,739,902,479,560,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,493 | 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 ptrace_traceme(void)
{
int ret = -EPERM;
write_lock_irq(&tasklist_lock);
/* Are we already being traced? */
if (!current->ptrace) {
ret = security_ptrace_traceme(current->parent);
/*
* Check PF_EXITING to ensure ->real_parent has not passed
* exit_ptrace(). Otherwise we don't report the error ... | 301,840,335,198,003,100,000,000,000,000,000,000,000 | ptrace.c | 316,279,739,902,479,560,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,494 | 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 ptrace_trapping_sleep_fn(void *flags)
{
schedule();
return 0;
}
| 171,892,800,825,186,570,000,000,000,000,000,000,000 | ptrace.c | 316,279,739,902,479,560,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,495 | 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 ptrace_unfreeze_traced(struct task_struct *task)
{
if (task->state != __TASK_TRACED)
return;
WARN_ON(!task->ptrace || task->parent != current);
spin_lock_irq(&task->sighand->siglock);
if (__fatal_signal_pending(task))
wake_up_state(task, __TASK_TRACED);
else
task->state = TASK_TRACED;
spin_unl... | 87,668,705,811,526,100,000,000,000,000,000,000,000 | ptrace.c | 316,279,739,902,479,560,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,496 | 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 ptrace_writedata(struct task_struct *tsk, char __user *src, unsigned long dst, int len)
{
int copied = 0;
while (len > 0) {
char buf[128];
int this_len, retval;
this_len = (len > sizeof(buf)) ? sizeof(buf) : len;
if (copy_from_user(buf, src, this_len))
return -EFAULT;
retval = access_process_vm(tsk... | 254,935,533,156,451,730,000,000,000,000,000,000,000 | ptrace.c | 316,279,739,902,479,560,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,497 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | static struct iscsi_param *__iscsi_check_key(
char *key,
int sender,
struct iscsi_param_list *param_list)
{
struct iscsi_param *param;
if (strlen(key) > KEY_MAXLEN) {
pr_err("Length of key name \"%s\" exceeds %d.\n",
key, KEY_MAXLEN);
return NULL;
}
param = iscsi_find_param_from_key(key, param_list);
i... | 14,623,852,582,035,057,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,498 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | int iscsi_change_param_value(
char *keyvalue,
struct iscsi_param_list *param_list,
int check_key)
{
char *key = NULL, *value = NULL;
struct iscsi_param *param;
int sender = 0;
if (iscsi_extract_key_value(keyvalue, &key, &value) < 0)
return -1;
if (!check_key) {
param = __iscsi_check_key(keyvalue, sender, ... | 207,562,527,794,291,160,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,499 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | static int iscsi_check_acceptor_state(struct iscsi_param *param, char *value,
struct iscsi_conn *conn)
{
u8 acceptor_boolean_value = 0, proposer_boolean_value = 0;
char *negoitated_value = NULL;
if (IS_PSTATE_ACCEPTOR(param)) {
pr_err("Received key \"%s\" twice, protocol error.\n",
param->name);
return ... | 336,162,139,825,111,630,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,500 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | static int iscsi_check_boolean_value(struct iscsi_param *param, char *value)
{
if (strcmp(value, YES) && strcmp(value, NO)) {
pr_err("Illegal value for \"%s\", must be either"
" \"%s\" or \"%s\".\n", param->name, YES, NO);
return -1;
}
return 0;
}
| 243,805,551,402,045,670,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,501 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | static int iscsi_check_for_auth_key(char *key)
{
/*
* RFC 1994
*/
if (!strcmp(key, "CHAP_A") || !strcmp(key, "CHAP_I") ||
!strcmp(key, "CHAP_C") || !strcmp(key, "CHAP_N") ||
!strcmp(key, "CHAP_R"))
return 1;
/*
* RFC 2945
*/
if (!strcmp(key, "SRP_U") || !strcmp(key, "SRP_N") ||
!strcmp(key... | 305,696,859,767,003,860,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,502 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | static struct iscsi_param *iscsi_check_key(
char *key,
int phase,
int sender,
struct iscsi_param_list *param_list)
{
struct iscsi_param *param;
/*
* Key name length must not exceed 63 bytes. (See iSCSI v20 5.1)
*/
if (strlen(key) > KEY_MAXLEN) {
pr_err("Length of key name \"%s\" exceeds %d.\n",
key, KEY... | 112,318,659,858,381,450,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,503 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | int iscsi_check_negotiated_keys(struct iscsi_param_list *param_list)
{
int ret = 0;
struct iscsi_param *param;
list_for_each_entry(param, ¶m_list->param_list, p_list) {
if (IS_PSTATE_NEGOTIATE(param) &&
IS_PSTATE_PROPOSER(param) &&
!IS_PSTATE_RESPONSE_GOT(param) &&
!IS_PSTATE_REPLY_OPTIONAL(... | 319,187,892,038,591,800,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,504 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | static int iscsi_check_numerical_range_value(struct iscsi_param *param, char *value)
{
char *left_val_ptr = NULL, *right_val_ptr = NULL;
char *tilde_ptr = NULL;
u32 left_val, right_val, local_left_val;
if (strcmp(param->name, IFMARKINT) &&
strcmp(param->name, OFMARKINT)) {
pr_err("Only parameters \"%s\" or ... | 324,285,205,735,173,140,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,505 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | static void iscsi_check_proposer_for_optional_reply(struct iscsi_param *param)
{
if (IS_TYPE_BOOL_AND(param)) {
if (!strcmp(param->value, NO))
SET_PSTATE_REPLY_OPTIONAL(param);
} else if (IS_TYPE_BOOL_OR(param)) {
if (!strcmp(param->value, YES))
SET_PSTATE_REPLY_OPTIONAL(param);
/*
* Required for gPX... | 300,276,949,612,219,200,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,506 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | static int iscsi_check_proposer_state(struct iscsi_param *param, char *value)
{
if (IS_PSTATE_RESPONSE_GOT(param)) {
pr_err("Received key \"%s\" twice, protocol error.\n",
param->name);
return -1;
}
if (IS_TYPE_NUMBER_RANGE(param)) {
u32 left_val = 0, right_val = 0, recieved_value = 0;
char *left_val_pt... | 5,197,452,209,033,086,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,507 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | static int iscsi_check_string_or_list_value(struct iscsi_param *param, char *value)
{
if (IS_PSTATE_PROPOSER(param))
return 0;
if (IS_TYPERANGE_AUTH_PARAM(param)) {
if (strcmp(value, KRB5) && strcmp(value, SPKM1) &&
strcmp(value, SPKM2) && strcmp(value, SRP) &&
strcmp(value, CHAP) && strcmp(value, NO... | 261,103,611,066,160,800,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,508 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | static int iscsi_check_value(struct iscsi_param *param, char *value)
{
char *comma_ptr = NULL;
if (!strcmp(value, REJECT)) {
if (!strcmp(param->name, IFMARKINT) ||
!strcmp(param->name, OFMARKINT)) {
/*
* Reject is not fatal for [I,O]FMarkInt, and causes
* [I,O]FMarker to be reset to No. (See iSCS... | 205,790,126,453,573,900,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,509 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | int iscsi_copy_param_list(
struct iscsi_param_list **dst_param_list,
struct iscsi_param_list *src_param_list,
int leading)
{
struct iscsi_param *param = NULL;
struct iscsi_param *new_param = NULL;
struct iscsi_param_list *param_list = NULL;
param_list = kzalloc(sizeof(struct iscsi_param_list), GFP_KERNEL);
if ... | 9,965,455,641,362,561,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,510 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | int iscsi_create_default_params(struct iscsi_param_list **param_list_ptr)
{
struct iscsi_param *param = NULL;
struct iscsi_param_list *pl;
pl = kzalloc(sizeof(struct iscsi_param_list), GFP_KERNEL);
if (!pl) {
pr_err("Unable to allocate memory for"
" struct iscsi_param_list.\n");
return -1 ;
}
INIT_LIST_H... | 115,835,967,649,658,350,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,511 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | void iscsi_dump_conn_ops(struct iscsi_conn_ops *conn_ops)
{
pr_debug("HeaderDigest: %s\n", (conn_ops->HeaderDigest) ?
"CRC32C" : "None");
pr_debug("DataDigest: %s\n", (conn_ops->DataDigest) ?
"CRC32C" : "None");
pr_debug("MaxRecvDataSegmentLength: %u\n",
conn_ops->MaxRecvDataSegmentLength);
pr_debug("OF... | 78,810,742,575,016,390,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,512 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | void iscsi_dump_sess_ops(struct iscsi_sess_ops *sess_ops)
{
pr_debug("InitiatorName: %s\n", sess_ops->InitiatorName);
pr_debug("InitiatorAlias: %s\n", sess_ops->InitiatorAlias);
pr_debug("TargetName: %s\n", sess_ops->TargetName);
pr_debug("TargetAlias: %s\n", sess_ops->TargetAlias);
pr_debug("TargetPortalGroupTag:... | 64,449,456,941,734,590,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,513 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | static int iscsi_enforce_integrity_rules(
u8 phase,
struct iscsi_param_list *param_list)
{
char *tmpptr;
u8 DataSequenceInOrder = 0;
u8 ErrorRecoveryLevel = 0, SessionType = 0;
u8 IFMarker = 0, OFMarker = 0;
u8 IFMarkInt_Reject = 1, OFMarkInt_Reject = 1;
u32 FirstBurstLength = 0, MaxBurstLength = 0;
struct isc... | 125,022,350,695,159,410,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,514 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | int iscsi_extract_key_value(char *textbuf, char **key, char **value)
{
*value = strchr(textbuf, '=');
if (!*value) {
pr_err("Unable to locate \"=\" separator for key,"
" ignoring request.\n");
return -1;
}
*key = textbuf;
**value = '\0';
*value = *value + 1;
return 0;
}
| 277,687,375,969,202,100,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,515 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | struct iscsi_param *iscsi_find_param_from_key(
char *key,
struct iscsi_param_list *param_list)
{
struct iscsi_param *param;
if (!key || !param_list) {
pr_err("Key or parameter list pointer is NULL.\n");
return NULL;
}
list_for_each_entry(param, ¶m_list->param_list, p_list) {
if (!strcmp(key, param->na... | 264,519,397,394,732,700,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,516 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | int iscsi_login_rx_data(
struct iscsi_conn *conn,
char *buf,
int length)
{
int rx_got;
struct kvec iov;
memset(&iov, 0, sizeof(struct kvec));
iov.iov_len = length;
iov.iov_base = buf;
/*
* Initial Marker-less Interval.
* Add the values regardless of IFMarker/OFMarker, considering
* it may not be negoit... | 339,970,436,113,804,180,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,517 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | int iscsi_login_tx_data(
struct iscsi_conn *conn,
char *pdu_buf,
char *text_buf,
int text_length)
{
int length, tx_sent, iov_cnt = 1;
struct kvec iov[2];
length = (ISCSI_HDR_LEN + text_length);
memset(&iov[0], 0, 2 * sizeof(struct kvec));
iov[0].iov_len = ISCSI_HDR_LEN;
iov[0].iov_base = pdu_buf;
if (te... | 308,336,069,818,285,200,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,518 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | static void iscsi_release_extra_responses(struct iscsi_param_list *param_list)
{
struct iscsi_extra_response *er, *er_tmp;
list_for_each_entry_safe(er, er_tmp, ¶m_list->extra_response_list,
er_list) {
list_del(&er->er_list);
kfree(er);
}
}
| 261,820,189,403,968,860,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,519 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | void iscsi_release_param_list(struct iscsi_param_list *param_list)
{
struct iscsi_param *param, *param_tmp;
list_for_each_entry_safe(param, param_tmp, ¶m_list->param_list,
p_list) {
list_del(¶m->p_list);
kfree(param->name);
kfree(param->value);
kfree(param);
}
iscsi_release_extra_responses(par... | 116,928,754,839,026,850,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,520 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | void iscsi_set_connection_parameters(
struct iscsi_conn_ops *ops,
struct iscsi_param_list *param_list)
{
char *tmpptr;
struct iscsi_param *param;
pr_debug("---------------------------------------------------"
"---------------\n");
list_for_each_entry(param, ¶m_list->param_list, p_list) {
/*
* Special... | 310,169,431,783,245,520,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,521 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | static struct iscsi_param *iscsi_set_default_param(struct iscsi_param_list *param_list,
char *name, char *value, u8 phase, u8 scope, u8 sender,
u16 type_range, u8 use)
{
struct iscsi_param *param = NULL;
param = kzalloc(sizeof(struct iscsi_param), GFP_KERNEL);
if (!param) {
pr_err("Unable to allocate memory f... | 117,673,885,824,584,360,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,522 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | int iscsi_set_keys_irrelevant_for_discovery(
struct iscsi_param_list *param_list)
{
struct iscsi_param *param;
list_for_each_entry(param, ¶m_list->param_list, p_list) {
if (!strcmp(param->name, MAXCONNECTIONS))
param->state &= ~PSTATE_NEGOTIATE;
else if (!strcmp(param->name, INITIALR2T))
param->state ... | 228,259,145,309,655,330,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,523 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | int iscsi_set_keys_to_negotiate(
struct iscsi_param_list *param_list,
bool iser)
{
struct iscsi_param *param;
param_list->iser = iser;
list_for_each_entry(param, ¶m_list->param_list, p_list) {
param->state = 0;
if (!strcmp(param->name, AUTHMETHOD)) {
SET_PSTATE_NEGOTIATE(param);
} else if (!strcmp(p... | 338,678,343,276,988,770,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,524 | linux | cea4dcfdad926a27a18e188720efe0f2c9403456 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cea4dcfdad926a27a18e188720efe0f2c9403456 | iscsi-target: fix heap buffer overflow on error
If a key was larger than 64 bytes, as checked by iscsi_check_key(), the
error response packet, generated by iscsi_add_notunderstood_response(),
would still attempt to copy the entire key into the packet, overflowing
the structure on the heap.
Remote preauthentication ke... | 0 | int iscsi_update_param_value(struct iscsi_param *param, char *value)
{
kfree(param->value);
param->value = kstrdup(value, GFP_KERNEL);
if (!param->value) {
pr_err("Unable to allocate memory for value.\n");
return -ENOMEM;
}
pr_debug("iSCSI Parameter updated to %s=%s\n",
param->name, param->value);
return... | 61,076,976,566,669,910,000,000,000,000,000,000,000 | iscsi_target_parameters.c | 260,263,344,392,188,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2850 | Heap-based buffer overflow in the iscsi_add_notunderstood_response function in drivers/target/iscsi/iscsi_target_parameters.c in the iSCSI target subsystem in the Linux kernel through 3.9.4 allows remote attackers to cause a denial of service (memory corruption and OOPS) or possibly execute arbitrary code via a long ke... | https://nvd.nist.gov/vuln/detail/CVE-2013-2850 |
32,527 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | int __rtnl_af_register(struct rtnl_af_ops *ops)
{
list_add_tail(&ops->list, &rtnl_af_ops);
return 0;
}
| 147,369,975,616,674,140,000,000,000,000,000,000,000 | rtnetlink.c | 84,143,673,137,336,160,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,528 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | void __rtnl_af_unregister(struct rtnl_af_ops *ops)
{
list_del(&ops->list);
}
| 991,712,125,201,408,400,000,000,000,000,000,000 | rtnetlink.c | 52,999,236,997,935,370,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,529 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static void __rtnl_kill_links(struct net *net, struct rtnl_link_ops *ops)
{
struct net_device *dev;
LIST_HEAD(list_kill);
for_each_netdev(net, dev) {
if (dev->rtnl_link_ops == ops)
ops->dellink(dev, &list_kill);
}
unregister_netdevice_many(&list_kill);
}
| 188,550,641,225,580,300,000,000,000,000,000,000,000 | rtnetlink.c | 52,999,236,997,935,370,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,530 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | void __rtnl_link_unregister(struct rtnl_link_ops *ops)
{
struct net *net;
for_each_net(net) {
__rtnl_kill_links(net, ops);
}
list_del(&ops->list);
}
| 227,077,488,795,715,260,000,000,000,000,000,000,000 | rtnetlink.c | 52,999,236,997,935,370,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,531 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | int __rtnl_register(int protocol, int msgtype,
rtnl_doit_func doit, rtnl_dumpit_func dumpit,
rtnl_calcit_func calcit)
{
struct rtnl_link *tab;
int msgindex;
BUG_ON(protocol < 0 || protocol > RTNL_FAMILY_MAX);
msgindex = rtm_msgindex(msgtype);
tab = rtnl_msg_handlers[protocol];
if (tab == NULL) {
t... | 106,980,236,407,890,800,000,000,000,000,000,000,000 | rtnetlink.c | 52,999,236,997,935,370,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,532 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | void __rtnl_unlock(void)
{
mutex_unlock(&rtnl_mutex);
}
| 213,161,650,593,996,750,000,000,000,000,000,000,000 | rtnetlink.c | 52,999,236,997,935,370,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,533 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static inline size_t bridge_nlmsg_size(void)
{
return NLMSG_ALIGN(sizeof(struct ifinfomsg))
+ nla_total_size(IFNAMSIZ) /* IFLA_IFNAME */
+ nla_total_size(MAX_ADDR_LEN) /* IFLA_ADDRESS */
+ nla_total_size(sizeof(u32)) /* IFLA_MASTER */
+ nla_total_size(sizeof(u32)) /* IFLA_MTU */
+ nla_total_size(sizeof(u32))... | 48,609,787,424,168,160,000,000,000,000,000,000,000 | rtnetlink.c | 52,999,236,997,935,370,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,534 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static void copy_rtnl_link_stats(struct rtnl_link_stats *a,
const struct rtnl_link_stats64 *b)
{
a->rx_packets = b->rx_packets;
a->tx_packets = b->tx_packets;
a->rx_bytes = b->rx_bytes;
a->tx_bytes = b->tx_bytes;
a->rx_errors = b->rx_errors;
a->tx_errors = b->tx_errors;
a->rx_dropped = b->rx_dropped;
a->tx... | 335,213,937,483,703,350,000,000,000,000,000,000,000 | rtnetlink.c | 84,143,673,137,336,160,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,535 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static void copy_rtnl_link_stats64(void *v, const struct rtnl_link_stats64 *b)
{
memcpy(v, b, sizeof(*b));
}
| 187,687,532,395,925,720,000,000,000,000,000,000,000 | rtnetlink.c | 52,999,236,997,935,370,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,536 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static int do_set_master(struct net_device *dev, int ifindex)
{
struct net_device *upper_dev = netdev_master_upper_dev_get(dev);
const struct net_device_ops *ops;
int err;
if (upper_dev) {
if (upper_dev->ifindex == ifindex)
return 0;
ops = upper_dev->netdev_ops;
if (ops->ndo_del_slave) {
err = ops->ndo... | 131,272,554,796,457,880,000,000,000,000,000,000,000 | rtnetlink.c | 52,999,236,997,935,370,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,537 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static int do_setlink(struct net_device *dev, struct ifinfomsg *ifm,
struct nlattr **tb, char *ifname, int modified)
{
const struct net_device_ops *ops = dev->netdev_ops;
int err;
if (tb[IFLA_NET_NS_PID] || tb[IFLA_NET_NS_FD]) {
struct net *net = rtnl_link_get_net(dev_net(dev), tb);
if (IS_ERR(net)) {
... | 104,371,996,648,796,810,000,000,000,000,000,000,000 | rtnetlink.c | 84,143,673,137,336,160,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,538 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static int do_setvfinfo(struct net_device *dev, struct nlattr *attr)
{
int rem, err = -EINVAL;
struct nlattr *vf;
const struct net_device_ops *ops = dev->netdev_ops;
nla_for_each_nested(vf, attr, rem) {
switch (nla_type(vf)) {
case IFLA_VF_MAC: {
struct ifla_vf_mac *ivm;
ivm = nla_data(vf);
err = -EOP... | 46,766,821,058,518,090,000,000,000,000,000,000,000 | rtnetlink.c | 84,143,673,137,336,160,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,539 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static noinline size_t if_nlmsg_size(const struct net_device *dev,
u32 ext_filter_mask)
{
return NLMSG_ALIGN(sizeof(struct ifinfomsg))
+ nla_total_size(IFNAMSIZ) /* IFLA_IFNAME */
+ nla_total_size(IFALIASZ) /* IFLA_IFALIAS */
+ nla_total_size(IFNAMSIZ) /* IFLA_QDISC */
+ nla_to... | 295,204,299,574,955,800,000,000,000,000,000,000,000 | rtnetlink.c | 84,143,673,137,336,160,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,540 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | int lockdep_rtnl_is_held(void)
{
return lockdep_is_held(&rtnl_mutex);
}
| 178,494,444,145,862,340,000,000,000,000,000,000,000 | rtnetlink.c | 84,143,673,137,336,160,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,541 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static int nlmsg_populate_fdb(struct sk_buff *skb,
struct netlink_callback *cb,
struct net_device *dev,
int *idx,
struct netdev_hw_addr_list *list)
{
struct netdev_hw_addr *ha;
int err;
u32 portid, seq;
portid = NETLINK_CB(cb->skb).portid;
seq = cb->nlh->nlmsg_seq;
list_for_e... | 124,381,405,054,932,760,000,000,000,000,000,000,000 | rtnetlink.c | 84,143,673,137,336,160,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,542 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static int nlmsg_populate_fdb_fill(struct sk_buff *skb,
struct net_device *dev,
u8 *addr, u32 pid, u32 seq,
int type, unsigned int flags)
{
struct nlmsghdr *nlh;
struct ndmsg *ndm;
nlh = nlmsg_put(skb, pid, seq, type, sizeof(*ndm), NLM_F_MULTI);
if (!nlh)
return -EMSGSIZE;
ndm = nlmsg_data... | 244,548,379,906,775,200,000,000,000,000,000,000,000 | rtnetlink.c | 84,143,673,137,336,160,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,543 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static inline int rtm_msgindex(int msgtype)
{
int msgindex = msgtype - RTM_BASE;
/*
* msgindex < 0 implies someone tried to register a netlink
* control code. msgindex >= RTM_NR_MSGTYPES may indicate that
* the message type has not been added to linux/rtnetlink.h
*/
BUG_ON(msgindex < 0 || msgindex >= RTM_NR... | 165,625,382,742,220,500,000,000,000,000,000,000,000 | rtnetlink.c | 52,999,236,997,935,370,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,544 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | void rtmsg_ifinfo(int type, struct net_device *dev, unsigned int change)
{
struct net *net = dev_net(dev);
struct sk_buff *skb;
int err = -ENOBUFS;
size_t if_info_size;
skb = nlmsg_new((if_info_size = if_nlmsg_size(dev, 0)), GFP_KERNEL);
if (skb == NULL)
goto errout;
err = rtnl_fill_ifinfo(skb, dev, type, 0,... | 82,419,320,212,879,100,000,000,000,000,000,000,000 | rtnetlink.c | 84,143,673,137,336,160,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,545 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static int rtnetlink_event(struct notifier_block *this, unsigned long event, void *ptr)
{
struct net_device *dev = ptr;
switch (event) {
case NETDEV_UP:
case NETDEV_DOWN:
case NETDEV_PRE_UP:
case NETDEV_POST_INIT:
case NETDEV_REGISTER:
case NETDEV_CHANGE:
case NETDEV_PRE_TYPE_CHANGE:
case NETDEV_GOING_DOWN:
... | 171,383,737,637,008,150,000,000,000,000,000,000,000 | rtnetlink.c | 84,143,673,137,336,160,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,546 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static void __net_exit rtnetlink_net_exit(struct net *net)
{
netlink_kernel_release(net->rtnl);
net->rtnl = NULL;
}
| 70,546,300,915,937,340,000,000,000,000,000,000,000 | rtnetlink.c | 52,999,236,997,935,370,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,547 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static int __net_init rtnetlink_net_init(struct net *net)
{
struct sock *sk;
struct netlink_kernel_cfg cfg = {
.groups = RTNLGRP_MAX,
.input = rtnetlink_rcv,
.cb_mutex = &rtnl_mutex,
.flags = NL_CFG_F_NONROOT_RECV,
};
sk = netlink_kernel_create(net, NETLINK_ROUTE, &cfg);
if (!sk)
return -ENOMEM;
net... | 24,459,669,194,635,464,000,000,000,000,000,000,000 | rtnetlink.c | 52,999,236,997,935,370,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,548 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | int rtnetlink_put_metrics(struct sk_buff *skb, u32 *metrics)
{
struct nlattr *mx;
int i, valid = 0;
mx = nla_nest_start(skb, RTA_METRICS);
if (mx == NULL)
return -ENOBUFS;
for (i = 0; i < RTAX_MAX; i++) {
if (metrics[i]) {
valid++;
if (nla_put_u32(skb, i+1, metrics[i]))
goto nla_put_failure;
}
}... | 285,015,822,049,679,800,000,000,000,000,000,000,000 | rtnetlink.c | 84,143,673,137,336,160,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,549 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static void rtnetlink_rcv(struct sk_buff *skb)
{
rtnl_lock();
netlink_rcv_skb(skb, &rtnetlink_rcv_msg);
rtnl_unlock();
}
| 294,896,361,337,141,150,000,000,000,000,000,000,000 | rtnetlink.c | 52,999,236,997,935,370,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,550 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static int rtnetlink_rcv_msg(struct sk_buff *skb, struct nlmsghdr *nlh)
{
struct net *net = sock_net(skb->sk);
rtnl_doit_func doit;
int sz_idx, kind;
int min_len;
int family;
int type;
int err;
type = nlh->nlmsg_type;
if (type > RTM_MAX)
return -EOPNOTSUPP;
type -= RTM_BASE;
/* All the messages must hav... | 232,405,497,552,928,800,000,000,000,000,000,000,000 | rtnetlink.c | 84,143,673,137,336,160,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,551 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | int rtnetlink_send(struct sk_buff *skb, struct net *net, u32 pid, unsigned int group, int echo)
{
struct sock *rtnl = net->rtnl;
int err = 0;
NETLINK_CB(skb).dst_group = group;
if (echo)
atomic_inc(&skb->users);
netlink_broadcast(rtnl, skb, pid, group, GFP_KERNEL);
if (echo)
err = netlink_unicast(rtnl, skb, ... | 94,211,864,581,981,570,000,000,000,000,000,000,000 | rtnetlink.c | 52,999,236,997,935,370,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,552 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | int rtnl_af_register(struct rtnl_af_ops *ops)
{
int err;
rtnl_lock();
err = __rtnl_af_register(ops);
rtnl_unlock();
return err;
}
| 236,379,413,012,337,330,000,000,000,000,000,000,000 | rtnetlink.c | 84,143,673,137,336,160,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,553 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | void rtnl_af_unregister(struct rtnl_af_ops *ops)
{
rtnl_lock();
__rtnl_af_unregister(ops);
rtnl_unlock();
}
| 253,957,297,785,918,340,000,000,000,000,000,000,000 | rtnetlink.c | 52,999,236,997,935,370,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,554 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static int rtnl_bridge_dellink(struct sk_buff *skb, struct nlmsghdr *nlh,
void *arg)
{
struct net *net = sock_net(skb->sk);
struct ifinfomsg *ifm;
struct net_device *dev;
struct nlattr *br_spec, *attr = NULL;
int rem, err = -EOPNOTSUPP;
u16 oflags, flags = 0;
bool have_flags = false;
if (nlmsg_len(nl... | 102,751,450,725,886,200,000,000,000,000,000,000,000 | rtnetlink.c | 84,143,673,137,336,160,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,555 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static int rtnl_bridge_notify(struct net_device *dev, u16 flags)
{
struct net *net = dev_net(dev);
struct net_device *br_dev = netdev_master_upper_dev_get(dev);
struct sk_buff *skb;
int err = -EOPNOTSUPP;
skb = nlmsg_new(bridge_nlmsg_size(), GFP_ATOMIC);
if (!skb) {
err = -ENOMEM;
goto errout;
}
if ((!fla... | 112,626,108,168,252,650,000,000,000,000,000,000,000 | rtnetlink.c | 84,143,673,137,336,160,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,556 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static int rtnl_bridge_setlink(struct sk_buff *skb, struct nlmsghdr *nlh,
void *arg)
{
struct net *net = sock_net(skb->sk);
struct ifinfomsg *ifm;
struct net_device *dev;
struct nlattr *br_spec, *attr = NULL;
int rem, err = -EOPNOTSUPP;
u16 oflags, flags = 0;
bool have_flags = false;
if (nlmsg_len(nl... | 166,491,749,498,830,430,000,000,000,000,000,000,000 | rtnetlink.c | 84,143,673,137,336,160,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,557 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static u16 rtnl_calcit(struct sk_buff *skb, struct nlmsghdr *nlh)
{
struct net *net = sock_net(skb->sk);
struct net_device *dev;
struct nlattr *tb[IFLA_MAX+1];
u32 ext_filter_mask = 0;
u16 min_ifinfo_dump_size = 0;
if (nlmsg_parse(nlh, sizeof(struct rtgenmsg), tb, IFLA_MAX,
ifla_policy) >= 0) {
if (tb[IFLA_... | 225,786,254,706,437,300,000,000,000,000,000,000,000 | rtnetlink.c | 84,143,673,137,336,160,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,558 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | int rtnl_configure_link(struct net_device *dev, const struct ifinfomsg *ifm)
{
unsigned int old_flags;
int err;
old_flags = dev->flags;
if (ifm && (ifm->ifi_flags || ifm->ifi_change)) {
err = __dev_change_flags(dev, rtnl_dev_combine_flags(dev, ifm));
if (err < 0)
return err;
}
dev->rtnl_link_state = RTNL... | 327,428,460,555,353,700,000,000,000,000,000,000,000 | rtnetlink.c | 84,143,673,137,336,160,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,559 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | struct net_device *rtnl_create_link(struct net *net,
char *ifname, const struct rtnl_link_ops *ops, struct nlattr *tb[])
{
int err;
struct net_device *dev;
unsigned int num_tx_queues = 1;
unsigned int num_rx_queues = 1;
if (tb[IFLA_NUM_TX_QUEUES])
num_tx_queues = nla_get_u32(tb[IFLA_NUM_TX_QUEUES]);
else if (... | 126,462,491,259,883,540,000,000,000,000,000,000,000 | rtnetlink.c | 84,143,673,137,336,160,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,560 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static int rtnl_dellink(struct sk_buff *skb, struct nlmsghdr *nlh, void *arg)
{
struct net *net = sock_net(skb->sk);
const struct rtnl_link_ops *ops;
struct net_device *dev;
struct ifinfomsg *ifm;
char ifname[IFNAMSIZ];
struct nlattr *tb[IFLA_MAX+1];
int err;
LIST_HEAD(list_kill);
err = nlmsg_parse(nlh, sizeo... | 48,434,127,083,404,640,000,000,000,000,000,000,000 | rtnetlink.c | 84,143,673,137,336,160,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,561 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static unsigned int rtnl_dev_combine_flags(const struct net_device *dev,
const struct ifinfomsg *ifm)
{
unsigned int flags = ifm->ifi_flags;
/* bugwards compatibility: ifi_change == 0 is treated as ~0 */
if (ifm->ifi_change)
flags = (flags & ifm->ifi_change) |
(rtnl_dev_get_flags(dev) & ~ifm->ifi_chang... | 70,660,762,468,011,990,000,000,000,000,000,000,000 | rtnetlink.c | 52,999,236,997,935,370,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,562 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static int rtnl_dump_all(struct sk_buff *skb, struct netlink_callback *cb)
{
int idx;
int s_idx = cb->family;
if (s_idx == 0)
s_idx = 1;
for (idx = 1; idx <= RTNL_FAMILY_MAX; idx++) {
int type = cb->nlh->nlmsg_type-RTM_BASE;
if (idx < s_idx || idx == PF_PACKET)
continue;
if (rtnl_msg_handlers[idx] == NU... | 326,249,994,786,526,000,000,000,000,000,000,000,000 | rtnetlink.c | 84,143,673,137,336,160,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,563 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static int rtnl_dump_ifinfo(struct sk_buff *skb, struct netlink_callback *cb)
{
struct net *net = sock_net(skb->sk);
int h, s_h;
int idx = 0, s_idx;
struct net_device *dev;
struct hlist_head *head;
struct nlattr *tb[IFLA_MAX+1];
u32 ext_filter_mask = 0;
s_h = cb->args[0];
s_idx = cb->args[1];
rcu_read_lock(... | 203,266,930,619,421,900,000,000,000,000,000,000,000 | rtnetlink.c | 84,143,673,137,336,160,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
32,564 | linux | 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/84d73cd3fb142bf1298a8c13fd4ca50fd2432372 | rtnl: fix info leak on RTM_GETLINK request for VF devices
Initialize the mac address buffer with 0 as the driver specific function
will probably not fill the whole buffer. In fact, all in-kernel drivers
fill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible
bytes. Therefore we currently leak 26 bytes ... | 0 | static int rtnl_fdb_add(struct sk_buff *skb, struct nlmsghdr *nlh, void *arg)
{
struct net *net = sock_net(skb->sk);
struct ndmsg *ndm;
struct nlattr *tb[NDA_MAX+1];
struct net_device *dev;
u8 *addr;
int err;
err = nlmsg_parse(nlh, sizeof(*ndm), tb, NDA_MAX, NULL);
if (err < 0)
return err;
ndm = nlmsg_data... | 81,936,572,379,995,240,000,000,000,000,000,000,000 | rtnetlink.c | 84,143,673,137,336,160,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2635 | The rtnl_fill_ifinfo function in net/core/rtnetlink.c in the Linux kernel before 3.8.4 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-2635 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.