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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
31,531 | libtiff | ce6841d9e41d621ba23cf18b190ee6a23b2cc833 | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/ce6841d9e41d621ba23cf18b190ee6a23b2cc833 | fix possible OOB write in gif2tiff.c | 0 | readscreen(void)
{
unsigned char buf[7];
fread(buf,1,7,infile);
global = buf[4] & 0x80;
if (global) {
globalbits = (buf[4] & 0x07) + 1;
fread(globalmap,3,((size_t)1)<<globalbits,infile);
}
}
| 294,646,594,417,387,600,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2013-4244 | The LZW decompressor in the gif2tiff tool in libtiff 4.0.3 and earlier allows context-dependent attackers to cause a denial of service (out-of-bounds write and crash) or possibly execute arbitrary code via a crafted GIF image. | https://nvd.nist.gov/vuln/detail/CVE-2013-4244 |
31,532 | libtiff | ce6841d9e41d621ba23cf18b190ee6a23b2cc833 | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/ce6841d9e41d621ba23cf18b190ee6a23b2cc833 | fix possible OOB write in gif2tiff.c | 0 | usage(void)
{
char buf[BUFSIZ];
int i;
setbuf(stderr, buf);
fprintf(stderr, "%s\n\n", TIFFGetVersion());
for (i = 0; stuff[i] != NULL; i++)
fprintf(stderr, "%s\n", stuff[i]);
exit(-1);
}
| 5,803,112,175,954,747,000,000,000,000,000,000,000 | tiff2bw.c | 210,326,292,647,667,700,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4244 | The LZW decompressor in the gif2tiff tool in libtiff 4.0.3 and earlier allows context-dependent attackers to cause a denial of service (out-of-bounds write and crash) or possibly execute arbitrary code via a crafted GIF image. | https://nvd.nist.gov/vuln/detail/CVE-2013-4244 |
31,533 | linux | 9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | arm64: don't kill the kernel on a bad esr from el0
Rather than completely killing the kernel if we receive an esr value we
can't deal with in the el0 handlers, send the process a SIGILL and log
the esr value in the hope that we can debug it. If we receive a bad esr
from el1, we'll die() as before.
Signed-off-by: Mark... | 0 | void __pgd_error(const char *file, int line, unsigned long val)
{
printk("%s:%d: bad pgd %016lx.\n", file, line, val);
}
| 188,768,855,349,243,970,000,000,000,000,000,000,000 | traps.c | 209,503,121,353,299,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-4220 | The bad_mode function in arch/arm64/kernel/traps.c in the Linux kernel before 3.9.5 on the ARM64 platform allows local users to cause a denial of service (system crash) via vectors involving an attempted register access that triggers an unexpected value in the Exception Syndrome Register (ESR). | https://nvd.nist.gov/vuln/detail/CVE-2013-4220 |
31,534 | linux | 9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | arm64: don't kill the kernel on a bad esr from el0
Rather than completely killing the kernel if we receive an esr value we
can't deal with in the el0 handlers, send the process a SIGILL and log
the esr value in the hope that we can debug it. If we receive a bad esr
from el1, we'll die() as before.
Signed-off-by: Mark... | 0 | void __pmd_error(const char *file, int line, unsigned long val)
{
printk("%s:%d: bad pmd %016lx.\n", file, line, val);
}
| 323,711,645,023,990,500,000,000,000,000,000,000,000 | traps.c | 209,503,121,353,299,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-4220 | The bad_mode function in arch/arm64/kernel/traps.c in the Linux kernel before 3.9.5 on the ARM64 platform allows local users to cause a denial of service (system crash) via vectors involving an attempted register access that triggers an unexpected value in the Exception Syndrome Register (ESR). | https://nvd.nist.gov/vuln/detail/CVE-2013-4220 |
31,535 | linux | 9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | arm64: don't kill the kernel on a bad esr from el0
Rather than completely killing the kernel if we receive an esr value we
can't deal with in the el0 handlers, send the process a SIGILL and log
the esr value in the hope that we can debug it. If we receive a bad esr
from el1, we'll die() as before.
Signed-off-by: Mark... | 0 | void __pte_error(const char *file, int line, unsigned long val)
{
printk("%s:%d: bad pte %016lx.\n", file, line, val);
}
| 225,311,807,046,247,850,000,000,000,000,000,000,000 | traps.c | 209,503,121,353,299,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-4220 | The bad_mode function in arch/arm64/kernel/traps.c in the Linux kernel before 3.9.5 on the ARM64 platform allows local users to cause a denial of service (system crash) via vectors involving an attempted register access that triggers an unexpected value in the Exception Syndrome Register (ESR). | https://nvd.nist.gov/vuln/detail/CVE-2013-4220 |
31,536 | linux | 9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | arm64: don't kill the kernel on a bad esr from el0
Rather than completely killing the kernel if we receive an esr value we
can't deal with in the el0 handlers, send the process a SIGILL and log
the esr value in the hope that we can debug it. If we receive a bad esr
from el1, we'll die() as before.
Signed-off-by: Mark... | 0 | void arm64_notify_die(const char *str, struct pt_regs *regs,
struct siginfo *info, int err)
{
if (user_mode(regs))
force_sig_info(info->si_signo, info, current);
else
die(str, regs, err);
}
| 218,147,079,642,409,240,000,000,000,000,000,000,000 | traps.c | 209,503,121,353,299,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-4220 | The bad_mode function in arch/arm64/kernel/traps.c in the Linux kernel before 3.9.5 on the ARM64 platform allows local users to cause a denial of service (system crash) via vectors involving an attempted register access that triggers an unexpected value in the Exception Syndrome Register (ESR). | https://nvd.nist.gov/vuln/detail/CVE-2013-4220 |
31,537 | linux | 9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | arm64: don't kill the kernel on a bad esr from el0
Rather than completely killing the kernel if we receive an esr value we
can't deal with in the el0 handlers, send the process a SIGILL and log
the esr value in the hope that we can debug it. If we receive a bad esr
from el1, we'll die() as before.
Signed-off-by: Mark... | 0 | asmlinkage void __exception do_undefinstr(struct pt_regs *regs)
{
siginfo_t info;
void __user *pc = (void __user *)instruction_pointer(regs);
#ifdef CONFIG_COMPAT
/* check for AArch32 breakpoint instructions */
if (compat_user_mode(regs) && aarch32_break_trap(regs) == 0)
return;
#endif
if (show_unhandled_signa... | 214,868,026,604,698,600,000,000,000,000,000,000,000 | traps.c | 209,503,121,353,299,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-4220 | The bad_mode function in arch/arm64/kernel/traps.c in the Linux kernel before 3.9.5 on the ARM64 platform allows local users to cause a denial of service (system crash) via vectors involving an attempted register access that triggers an unexpected value in the Exception Syndrome Register (ESR). | https://nvd.nist.gov/vuln/detail/CVE-2013-4220 |
31,538 | linux | 9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | arm64: don't kill the kernel on a bad esr from el0
Rather than completely killing the kernel if we receive an esr value we
can't deal with in the el0 handlers, send the process a SIGILL and log
the esr value in the hope that we can debug it. If we receive a bad esr
from el1, we'll die() as before.
Signed-off-by: Mark... | 0 | static void dump_backtrace(struct pt_regs *regs, struct task_struct *tsk)
{
struct stackframe frame;
const register unsigned long current_sp asm ("sp");
pr_debug("%s(regs = %p tsk = %p)\n", __func__, regs, tsk);
if (!tsk)
tsk = current;
if (regs) {
frame.fp = regs->regs[29];
frame.sp = regs->sp;
frame.p... | 217,138,376,174,856,700,000,000,000,000,000,000,000 | traps.c | 209,503,121,353,299,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-4220 | The bad_mode function in arch/arm64/kernel/traps.c in the Linux kernel before 3.9.5 on the ARM64 platform allows local users to cause a denial of service (system crash) via vectors involving an attempted register access that triggers an unexpected value in the Exception Syndrome Register (ESR). | https://nvd.nist.gov/vuln/detail/CVE-2013-4220 |
31,539 | linux | 9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | arm64: don't kill the kernel on a bad esr from el0
Rather than completely killing the kernel if we receive an esr value we
can't deal with in the el0 handlers, send the process a SIGILL and log
the esr value in the hope that we can debug it. If we receive a bad esr
from el1, we'll die() as before.
Signed-off-by: Mark... | 0 | static void dump_backtrace_entry(unsigned long where, unsigned long stack)
{
print_ip_sym(where);
if (in_exception_text(where))
dump_mem("", "Exception stack", stack,
stack + sizeof(struct pt_regs));
}
| 194,751,962,848,309,700,000,000,000,000,000,000,000 | traps.c | 209,503,121,353,299,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-4220 | The bad_mode function in arch/arm64/kernel/traps.c in the Linux kernel before 3.9.5 on the ARM64 platform allows local users to cause a denial of service (system crash) via vectors involving an attempted register access that triggers an unexpected value in the Exception Syndrome Register (ESR). | https://nvd.nist.gov/vuln/detail/CVE-2013-4220 |
31,540 | linux | 9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | arm64: don't kill the kernel on a bad esr from el0
Rather than completely killing the kernel if we receive an esr value we
can't deal with in the el0 handlers, send the process a SIGILL and log
the esr value in the hope that we can debug it. If we receive a bad esr
from el1, we'll die() as before.
Signed-off-by: Mark... | 0 | static void dump_instr(const char *lvl, struct pt_regs *regs)
{
unsigned long addr = instruction_pointer(regs);
mm_segment_t fs;
char str[sizeof("00000000 ") * 5 + 2 + 1], *p = str;
int i;
/*
* We need to switch to kernel mode so that we can use __get_user
* to safely read from kernel space. Note that we now... | 59,015,306,577,407,240,000,000,000,000,000,000,000 | traps.c | 209,503,121,353,299,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-4220 | The bad_mode function in arch/arm64/kernel/traps.c in the Linux kernel before 3.9.5 on the ARM64 platform allows local users to cause a denial of service (system crash) via vectors involving an attempted register access that triggers an unexpected value in the Exception Syndrome Register (ESR). | https://nvd.nist.gov/vuln/detail/CVE-2013-4220 |
31,541 | linux | 9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | arm64: don't kill the kernel on a bad esr from el0
Rather than completely killing the kernel if we receive an esr value we
can't deal with in the el0 handlers, send the process a SIGILL and log
the esr value in the hope that we can debug it. If we receive a bad esr
from el1, we'll die() as before.
Signed-off-by: Mark... | 0 | static void dump_mem(const char *lvl, const char *str, unsigned long bottom,
unsigned long top)
{
unsigned long first;
mm_segment_t fs;
int i;
/*
* We need to switch to kernel mode so that we can use __get_user
* to safely read from kernel space. Note that we now dump the
* code first, just in case t... | 87,940,954,182,042,480,000,000,000,000,000,000,000 | traps.c | 209,503,121,353,299,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-4220 | The bad_mode function in arch/arm64/kernel/traps.c in the Linux kernel before 3.9.5 on the ARM64 platform allows local users to cause a denial of service (system crash) via vectors involving an attempted register access that triggers an unexpected value in the Exception Syndrome Register (ESR). | https://nvd.nist.gov/vuln/detail/CVE-2013-4220 |
31,542 | linux | 9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | arm64: don't kill the kernel on a bad esr from el0
Rather than completely killing the kernel if we receive an esr value we
can't deal with in the el0 handlers, send the process a SIGILL and log
the esr value in the hope that we can debug it. If we receive a bad esr
from el1, we'll die() as before.
Signed-off-by: Mark... | 0 | void show_stack(struct task_struct *tsk, unsigned long *sp)
{
dump_backtrace(NULL, tsk);
barrier();
}
| 286,465,090,568,883,830,000,000,000,000,000,000,000 | traps.c | 209,503,121,353,299,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-4220 | The bad_mode function in arch/arm64/kernel/traps.c in the Linux kernel before 3.9.5 on the ARM64 platform allows local users to cause a denial of service (system crash) via vectors involving an attempted register access that triggers an unexpected value in the Exception Syndrome Register (ESR). | https://nvd.nist.gov/vuln/detail/CVE-2013-4220 |
31,543 | linux | 9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | arm64: don't kill the kernel on a bad esr from el0
Rather than completely killing the kernel if we receive an esr value we
can't deal with in the el0 handlers, send the process a SIGILL and log
the esr value in the hope that we can debug it. If we receive a bad esr
from el1, we'll die() as before.
Signed-off-by: Mark... | 0 | void __init trap_init(void)
{
return;
}
| 217,223,174,801,348,030,000,000,000,000,000,000,000 | traps.c | 209,503,121,353,299,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-4220 | The bad_mode function in arch/arm64/kernel/traps.c in the Linux kernel before 3.9.5 on the ARM64 platform allows local users to cause a denial of service (system crash) via vectors involving an attempted register access that triggers an unexpected value in the Exception Syndrome Register (ESR). | https://nvd.nist.gov/vuln/detail/CVE-2013-4220 |
31,544 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | int create_user_ns(struct cred *new)
{
struct user_namespace *ns, *parent_ns = new->user_ns;
kuid_t owner = new->euid;
kgid_t group = new->egid;
int ret;
/*
* Verify that we can not violate the policy of which files
* may be accessed that is specified by the root directory,
* by verifing that the root direc... | 260,780,994,828,150,100,000,000,000,000,000,000,000 | user_namespace.c | 98,994,324,473,258,400,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,545 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | void free_user_ns(struct user_namespace *ns)
{
struct user_namespace *parent;
do {
parent = ns->parent;
proc_free_inum(ns->proc_inum);
kmem_cache_free(user_ns_cachep, ns);
ns = parent;
} while (atomic_dec_and_test(&parent->count));
}
| 120,903,551,984,080,370,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,546 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | gid_t from_kgid_munged(struct user_namespace *targ, kgid_t kgid)
{
gid_t gid;
gid = from_kgid(targ, kgid);
if (gid == (gid_t) -1)
gid = overflowgid;
return gid;
}
| 281,882,858,514,126,100,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,547 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | projid_t from_kprojid(struct user_namespace *targ, kprojid_t kprojid)
{
/* Map the uid from a global kernel uid */
return map_id_up(&targ->projid_map, __kprojid_val(kprojid));
}
| 214,721,425,357,496,570,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,548 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | uid_t from_kuid(struct user_namespace *targ, kuid_t kuid)
{
/* Map the uid from a global kernel uid */
return map_id_up(&targ->uid_map, __kuid_val(kuid));
}
| 224,600,826,829,235,140,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,549 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | uid_t from_kuid_munged(struct user_namespace *targ, kuid_t kuid)
{
uid_t uid;
uid = from_kuid(targ, kuid);
if (uid == (uid_t) -1)
uid = overflowuid;
return uid;
}
| 250,455,526,978,972,000,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,550 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | static int gid_m_show(struct seq_file *seq, void *v)
{
struct user_namespace *ns = seq->private;
struct uid_gid_extent *extent = v;
struct user_namespace *lower_ns;
gid_t lower;
lower_ns = seq_user_ns(seq);
if ((lower_ns == ns) && lower_ns->parent)
lower_ns = lower_ns->parent;
lower = from_kgid(lower_ns, KGI... | 312,165,148,397,211,530,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,551 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | static void *gid_m_start(struct seq_file *seq, loff_t *ppos)
{
struct user_namespace *ns = seq->private;
return m_start(seq, ppos, &ns->gid_map);
}
| 309,864,327,666,131,670,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,552 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | static void *m_next(struct seq_file *seq, void *v, loff_t *pos)
{
(*pos)++;
return seq->op->start(seq, pos);
}
| 116,714,614,295,440,400,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,553 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | static void *m_start(struct seq_file *seq, loff_t *ppos, struct uid_gid_map *map)
{
struct uid_gid_extent *extent = NULL;
loff_t pos = *ppos;
if (pos < map->nr_extents)
extent = &map->extent[pos];
return extent;
}
| 184,909,699,097,484,450,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,554 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | static void m_stop(struct seq_file *seq, void *v)
{
return;
}
| 287,149,761,685,050,000,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,555 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | kgid_t make_kgid(struct user_namespace *ns, gid_t gid)
{
/* Map the gid to a global kernel gid */
return KGIDT_INIT(map_id_down(&ns->gid_map, gid));
}
| 304,928,524,008,647,900,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,556 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | kprojid_t make_kprojid(struct user_namespace *ns, projid_t projid)
{
/* Map the uid to a global kernel uid */
return KPROJIDT_INIT(map_id_down(&ns->projid_map, projid));
}
| 154,023,946,582,301,030,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,557 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | kuid_t make_kuid(struct user_namespace *ns, uid_t uid)
{
/* Map the uid to a global kernel uid */
return KUIDT_INIT(map_id_down(&ns->uid_map, uid));
}
| 229,621,776,765,947,400,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,558 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | static u32 map_id_down(struct uid_gid_map *map, u32 id)
{
unsigned idx, extents;
u32 first, last;
/* Find the matching extent */
extents = map->nr_extents;
smp_read_barrier_depends();
for (idx = 0; idx < extents; idx++) {
first = map->extent[idx].first;
last = first + map->extent[idx].count - 1;
if (id >= ... | 250,341,569,542,113,200,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,559 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | static u32 map_id_range_down(struct uid_gid_map *map, u32 id, u32 count)
{
unsigned idx, extents;
u32 first, last, id2;
id2 = id + count - 1;
/* Find the matching extent */
extents = map->nr_extents;
smp_read_barrier_depends();
for (idx = 0; idx < extents; idx++) {
first = map->extent[idx].first;
last = fi... | 219,952,163,957,432,550,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,560 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | static u32 map_id_up(struct uid_gid_map *map, u32 id)
{
unsigned idx, extents;
u32 first, last;
/* Find the matching extent */
extents = map->nr_extents;
smp_read_barrier_depends();
for (idx = 0; idx < extents; idx++) {
first = map->extent[idx].lower_first;
last = first + map->extent[idx].count - 1;
if (id... | 46,853,857,216,885,480,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,561 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | static ssize_t map_write(struct file *file, const char __user *buf,
size_t count, loff_t *ppos,
int cap_setid,
struct uid_gid_map *map,
struct uid_gid_map *parent_map)
{
struct seq_file *seq = file->private_data;
struct user_namespace *ns = seq->private;
struct uid_gid_map new_map;
unsigned idx;
st... | 8,670,254,885,132,260,000,000,000,000,000,000,000 | user_namespace.c | 98,994,324,473,258,400,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,562 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | static bool mappings_overlap(struct uid_gid_map *new_map, struct uid_gid_extent *extent)
{
u32 upper_first, lower_first, upper_last, lower_last;
unsigned idx;
upper_first = extent->first;
lower_first = extent->lower_first;
upper_last = upper_first + extent->count - 1;
lower_last = lower_first + extent->count - 1... | 249,264,831,546,401,920,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,563 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | ssize_t proc_gid_map_write(struct file *file, const char __user *buf, size_t size, loff_t *ppos)
{
struct seq_file *seq = file->private_data;
struct user_namespace *ns = seq->private;
struct user_namespace *seq_ns = seq_user_ns(seq);
if (!ns->parent)
return -EPERM;
if ((seq_ns != ns) && (seq_ns != ns->parent))... | 85,282,672,127,881,580,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,564 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | ssize_t proc_projid_map_write(struct file *file, const char __user *buf, size_t size, loff_t *ppos)
{
struct seq_file *seq = file->private_data;
struct user_namespace *ns = seq->private;
struct user_namespace *seq_ns = seq_user_ns(seq);
if (!ns->parent)
return -EPERM;
if ((seq_ns != ns) && (seq_ns != ns->paren... | 164,425,746,542,252,390,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,565 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | ssize_t proc_uid_map_write(struct file *file, const char __user *buf, size_t size, loff_t *ppos)
{
struct seq_file *seq = file->private_data;
struct user_namespace *ns = seq->private;
struct user_namespace *seq_ns = seq_user_ns(seq);
if (!ns->parent)
return -EPERM;
if ((seq_ns != ns) && (seq_ns != ns->parent))... | 328,807,451,381,726,740,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,566 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | static int projid_m_show(struct seq_file *seq, void *v)
{
struct user_namespace *ns = seq->private;
struct uid_gid_extent *extent = v;
struct user_namespace *lower_ns;
projid_t lower;
lower_ns = seq_user_ns(seq);
if ((lower_ns == ns) && lower_ns->parent)
lower_ns = lower_ns->parent;
lower = from_kprojid(lowe... | 145,692,140,690,820,000,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,567 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | static void *projid_m_start(struct seq_file *seq, loff_t *ppos)
{
struct user_namespace *ns = seq->private;
return m_start(seq, ppos, &ns->projid_map);
}
| 327,122,467,052,406,080,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,568 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | static void set_cred_user_ns(struct cred *cred, struct user_namespace *user_ns)
{
/* Start with the same capabilities as init but useless for doing
* anything as the capabilities are bound to the new user namespace.
*/
cred->securebits = SECUREBITS_DEFAULT;
cred->cap_inheritable = CAP_EMPTY_SET;
cred->cap_permi... | 320,208,435,210,906,000,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,569 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | static int uid_m_show(struct seq_file *seq, void *v)
{
struct user_namespace *ns = seq->private;
struct uid_gid_extent *extent = v;
struct user_namespace *lower_ns;
uid_t lower;
lower_ns = seq_user_ns(seq);
if ((lower_ns == ns) && lower_ns->parent)
lower_ns = lower_ns->parent;
lower = from_kuid(lower_ns, KUI... | 307,834,910,542,145,250,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,570 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | static void *uid_m_start(struct seq_file *seq, loff_t *ppos)
{
struct user_namespace *ns = seq->private;
return m_start(seq, ppos, &ns->uid_map);
}
| 307,158,699,425,379,500,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,571 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | static __init int user_namespaces_init(void)
{
user_ns_cachep = KMEM_CACHE(user_namespace, SLAB_PANIC);
return 0;
}
| 233,825,284,997,420,160,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,572 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | static void *userns_get(struct task_struct *task)
{
struct user_namespace *user_ns;
rcu_read_lock();
user_ns = get_user_ns(__task_cred(task)->user_ns);
rcu_read_unlock();
return user_ns;
}
| 213,939,604,601,749,900,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,573 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | static int userns_install(struct nsproxy *nsproxy, void *ns)
{
struct user_namespace *user_ns = ns;
struct cred *cred;
/* Don't allow gaining capabilities by reentering
* the same user namespace.
*/
if (user_ns == current_user_ns())
return -EINVAL;
/* Threaded processes may not enter a different user names... | 320,278,194,620,945,220,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,574 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | static unsigned int userns_inum(void *ns)
{
struct user_namespace *user_ns = ns;
return user_ns->proc_inum;
}
| 218,176,703,030,564,150,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,575 | linux | 6160968cee8b90a5dd95318d716e31d7775c4ef3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6160968cee8b90a5dd95318d716e31d7775c4ef3 | userns: unshare_userns(&cred) should not populate cred on failure
unshare_userns(new_cred) does *new_cred = prepare_creds() before
create_user_ns() which can fail. However, the caller expects that
it doesn't need to take care of new_cred if unshare_userns() fails.
We could change the single caller, sys_unshare(), but... | 0 | static void userns_put(void *ns)
{
put_user_ns(ns);
}
| 36,056,046,824,772,300,000,000,000,000,000,000,000 | user_namespace.c | 9,948,127,664,871,343,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4205 | Memory leak in the unshare_userns function in kernel/user_namespace.c in the Linux kernel before 3.10.6 allows local users to cause a denial of service (memory consumption) via an invalid CLONE_NEWUSER unshare call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4205 |
31,576 | linux | 75a493e60ac4bbe2e977e7129d6d8cbb0dd236be | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/75a493e60ac4bbe2e977e7129d6d8cbb0dd236be | ipv6: ip6_append_data_mtu did not care about pmtudisc and frag_size
If the socket had an IPV6_MTU value set, ip6_append_data_mtu lost track
of this when appending the second frame on a corked socket. This results
in the following splat:
[37598.993962] ------------[ cut here ]------------
[37598.994008] kernel BUG at ... | 0 | int ip6_forward(struct sk_buff *skb)
{
struct dst_entry *dst = skb_dst(skb);
struct ipv6hdr *hdr = ipv6_hdr(skb);
struct inet6_skb_parm *opt = IP6CB(skb);
struct net *net = dev_net(dst->dev);
u32 mtu;
if (net->ipv6.devconf_all->forwarding == 0)
goto error;
if (skb_warn_if_lro(skb))
goto drop;
if (!xfrm6_... | 219,836,144,083,647,650,000,000,000,000,000,000,000 | ip6_output.c | 19,620,935,478,555,194,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4163 | The ip6_append_data_mtu function in net/ipv6/ip6_output.c in the IPv6 implementation in the Linux kernel through 3.10.3 does not properly maintain information about whether the IPV6_MTU setsockopt option had been specified, which allows local users to cause a denial of service (BUG and system crash) via a crafted appli... | https://nvd.nist.gov/vuln/detail/CVE-2013-4163 |
31,577 | linux | 75a493e60ac4bbe2e977e7129d6d8cbb0dd236be | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/75a493e60ac4bbe2e977e7129d6d8cbb0dd236be | ipv6: ip6_append_data_mtu did not care about pmtudisc and frag_size
If the socket had an IPV6_MTU value set, ip6_append_data_mtu lost track
of this when appending the second frame on a corked socket. This results
in the following splat:
[37598.993962] ------------[ cut here ]------------
[37598.994008] kernel BUG at ... | 0 | int ip6_xmit(struct sock *sk, struct sk_buff *skb, struct flowi6 *fl6,
struct ipv6_txoptions *opt, int tclass)
{
struct net *net = sock_net(sk);
struct ipv6_pinfo *np = inet6_sk(sk);
struct in6_addr *first_hop = &fl6->daddr;
struct dst_entry *dst = skb_dst(skb);
struct ipv6hdr *hdr;
u8 proto = fl6->flowi6_... | 62,915,468,145,584,110,000,000,000,000,000,000,000 | ip6_output.c | 19,620,935,478,555,194,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4163 | The ip6_append_data_mtu function in net/ipv6/ip6_output.c in the IPv6 implementation in the Linux kernel through 3.10.3 does not properly maintain information about whether the IPV6_MTU setsockopt option had been specified, which allows local users to cause a denial of service (BUG and system crash) via a crafted appli... | https://nvd.nist.gov/vuln/detail/CVE-2013-4163 |
31,578 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | void __udp4_lib_err(struct sk_buff *skb, u32 info, struct udp_table *udptable)
{
struct inet_sock *inet;
const struct iphdr *iph = (const struct iphdr *)skb->data;
struct udphdr *uh = (struct udphdr *)(skb->data+(iph->ihl<<2));
const int type = icmp_hdr(skb)->type;
const int code = icmp_hdr(skb)->code;
struct soc... | 139,978,762,149,622,450,000,000,000,000,000,000,000 | udp.c | 285,492,838,466,761,200,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,579 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | static inline int compute_score(struct sock *sk, struct net *net, __be32 saddr,
unsigned short hnum,
__be16 sport, __be32 daddr, __be16 dport, int dif)
{
int score = -1;
if (net_eq(sock_net(sk), net) && udp_sk(sk)->udp_port_hash == hnum &&
!ipv6_only_sock(sk)) {
struct inet_sock *inet = inet_sk(sk);
... | 276,742,587,629,619,950,000,000,000,000,000,000,000 | udp.c | 197,428,295,876,416,400,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,580 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | static inline int compute_score2(struct sock *sk, struct net *net,
__be32 saddr, __be16 sport,
__be32 daddr, unsigned int hnum, int dif)
{
int score = -1;
if (net_eq(sock_net(sk), net) && !ipv6_only_sock(sk)) {
struct inet_sock *inet = inet_sk(sk);
if (inet->inet_rcv_saddr != daddr)
return -1;
if... | 238,450,232,328,574,100,000,000,000,000,000,000,000 | udp.c | 197,428,295,876,416,400,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,581 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | static unsigned int first_packet_length(struct sock *sk)
{
struct sk_buff_head list_kill, *rcvq = &sk->sk_receive_queue;
struct sk_buff *skb;
unsigned int res;
__skb_queue_head_init(&list_kill);
spin_lock_bh(&rcvq->lock);
while ((skb = skb_peek(rcvq)) != NULL &&
udp_lib_checksum_complete(skb)) {
UDP_INC_STA... | 226,657,976,992,091,360,000,000,000,000,000,000,000 | udp.c | 273,251,318,651,126,540,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,582 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | static int __init set_uhash_entries(char *str)
{
ssize_t ret;
if (!str)
return 0;
ret = kstrtoul(str, 0, &uhash_entries);
if (ret)
return 0;
if (uhash_entries && uhash_entries < UDP_HTABLE_SIZE_MIN)
uhash_entries = UDP_HTABLE_SIZE_MIN;
return 1;
}
| 111,236,514,769,976,020,000,000,000,000,000,000,000 | udp.c | 34,572,501,297,250,960,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,583 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | struct sk_buff *skb_udp_tunnel_segment(struct sk_buff *skb,
netdev_features_t features)
{
struct sk_buff *segs = ERR_PTR(-EINVAL);
int mac_len = skb->mac_len;
int tnl_hlen = skb_inner_mac_header(skb) - skb_transport_header(skb);
__be16 protocol = skb->protocol;
netdev_features_t enc_features;
int outer... | 260,109,780,245,007,420,000,000,000,000,000,000,000 | udp.c | 285,492,838,466,761,200,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,584 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | static void udp4_format_sock(struct sock *sp, struct seq_file *f,
int bucket, int *len)
{
struct inet_sock *inet = inet_sk(sp);
__be32 dest = inet->inet_daddr;
__be32 src = inet->inet_rcv_saddr;
__u16 destp = ntohs(inet->inet_dport);
__u16 srcp = ntohs(inet->inet_sport);
seq_printf(f, "%5d: %08X:%04X %08X... | 165,328,649,412,267,760,000,000,000,000,000,000,000 | udp.c | 285,492,838,466,761,200,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,585 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | static struct sock *udp4_lib_lookup2(struct net *net,
__be32 saddr, __be16 sport,
__be32 daddr, unsigned int hnum, int dif,
struct udp_hslot *hslot2, unsigned int slot2)
{
struct sock *sk, *result;
struct hlist_nulls_node *node;
int score, badness, matches = 0, reuseport = 0;
u32 hash = 0;
begin:
result = N... | 113,183,680,675,666,230,000,000,000,000,000,000,000 | udp.c | 285,492,838,466,761,200,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,586 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | void udp_destroy_sock(struct sock *sk)
{
struct udp_sock *up = udp_sk(sk);
bool slow = lock_sock_fast(sk);
udp_flush_pending_frames(sk);
unlock_sock_fast(sk, slow);
if (static_key_false(&udp_encap_needed) && up->encap_type) {
void (*encap_destroy)(struct sock *sk);
encap_destroy = ACCESS_ONCE(up->encap_destroy... | 287,427,937,133,542,500,000,000,000,000,000,000,000 | udp.c | 34,572,501,297,250,960,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,587 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | int udp_disconnect(struct sock *sk, int flags)
{
struct inet_sock *inet = inet_sk(sk);
/*
* 1003.1g - break association.
*/
sk->sk_state = TCP_CLOSE;
inet->inet_daddr = 0;
inet->inet_dport = 0;
sock_rps_reset_rxhash(sk);
sk->sk_bound_dev_if = 0;
if (!(sk->sk_userlocks & SOCK_BINDADDR_LOCK))
inet_reset_sa... | 340,247,347,777,699,150,000,000,000,000,000,000,000 | udp.c | 273,251,318,651,126,540,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,588 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | void udp_encap_enable(void)
{
if (!static_key_enabled(&udp_encap_needed))
static_key_slow_inc(&udp_encap_needed);
}
| 55,467,397,995,020,190,000,000,000,000,000,000,000 | udp.c | 34,572,501,297,250,960,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,589 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | void __init udp_init(void)
{
unsigned long limit;
udp_table_init(&udp_table, "UDP");
limit = nr_free_buffer_pages() / 8;
limit = max(limit, 128UL);
sysctl_udp_mem[0] = limit / 4 * 3;
sysctl_udp_mem[1] = limit;
sysctl_udp_mem[2] = sysctl_udp_mem[0] * 2;
sysctl_udp_rmem_min = SK_MEM_QUANTUM;
sysctl_udp_wmem_mi... | 186,983,095,238,951,070,000,000,000,000,000,000,000 | udp.c | 273,251,318,651,126,540,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,590 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | int udp_lib_get_port(struct sock *sk, unsigned short snum,
int (*saddr_comp)(const struct sock *sk1,
const struct sock *sk2),
unsigned int hash2_nulladdr)
{
struct udp_hslot *hslot, *hslot2;
struct udp_table *udptable = sk->sk_prot->h.udp_table;
int error = 1;
struct net *net = sock_net(sk)... | 231,283,886,149,272,570,000,000,000,000,000,000,000 | udp.c | 285,492,838,466,761,200,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,591 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | static int udp_lib_lport_inuse2(struct net *net, __u16 num,
struct udp_hslot *hslot2,
struct sock *sk,
int (*saddr_comp)(const struct sock *sk1,
const struct sock *sk2))
{
struct sock *sk2;
struct hlist_nulls_node *node;
kuid_t uid = sock_i_uid(sk);
int res = 0;
spin_lock(&hsl... | 135,756,759,880,664,720,000,000,000,000,000,000,000 | udp.c | 197,428,295,876,416,400,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,592 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | int udp_lib_setsockopt(struct sock *sk, int level, int optname,
char __user *optval, unsigned int optlen,
int (*push_pending_frames)(struct sock *))
{
struct udp_sock *up = udp_sk(sk);
int val;
int err = 0;
int is_udplite = IS_UDPLITE(sk);
if (optlen < sizeof(int))
return -EINVAL;
if (get_us... | 103,411,015,790,914,850,000,000,000,000,000,000,000 | udp.c | 197,428,295,876,416,400,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,593 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | unsigned int udp_poll(struct file *file, struct socket *sock, poll_table *wait)
{
unsigned int mask = datagram_poll(file, sock, wait);
struct sock *sk = sock->sk;
sock_rps_record_flow(sk);
/* Check for false positives due to checksum errors */
if ((mask & POLLRDNORM) && !(file->f_flags & O_NONBLOCK) &&
!(sk... | 331,357,066,512,146,360,000,000,000,000,000,000,000 | udp.c | 273,251,318,651,126,540,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,594 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | int udp_proc_register(struct net *net, struct udp_seq_afinfo *afinfo)
{
struct proc_dir_entry *p;
int rc = 0;
afinfo->seq_ops.start = udp_seq_start;
afinfo->seq_ops.next = udp_seq_next;
afinfo->seq_ops.stop = udp_seq_stop;
p = proc_create_data(afinfo->name, S_IRUGO, net->proc_net,
afinfo->seq_fops, a... | 192,857,188,006,160,200,000,000,000,000,000,000,000 | udp.c | 34,572,501,297,250,960,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,595 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | static int udp_send_skb(struct sk_buff *skb, struct flowi4 *fl4)
{
struct sock *sk = skb->sk;
struct inet_sock *inet = inet_sk(sk);
struct udphdr *uh;
int err = 0;
int is_udplite = IS_UDPLITE(sk);
int offset = skb_transport_offset(skb);
int len = skb->len - offset;
__wsum csum = 0;
/*
* Create a UDP header
... | 14,321,175,047,748,090,000,000,000,000,000,000,000 | udp.c | 197,428,295,876,416,400,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,596 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | int udp_sendmsg(struct kiocb *iocb, struct sock *sk, struct msghdr *msg,
size_t len)
{
struct inet_sock *inet = inet_sk(sk);
struct udp_sock *up = udp_sk(sk);
struct flowi4 fl4_stack;
struct flowi4 *fl4;
int ulen = len;
struct ipcm_cookie ipc;
struct rtable *rt = NULL;
int free = 0;
int connected = 0;
__b... | 265,531,834,432,080,230,000,000,000,000,000,000,000 | udp.c | 285,492,838,466,761,200,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,597 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | int udp_sendpage(struct sock *sk, struct page *page, int offset,
size_t size, int flags)
{
struct inet_sock *inet = inet_sk(sk);
struct udp_sock *up = udp_sk(sk);
int ret;
if (!up->pending) {
struct msghdr msg = { .msg_flags = flags|MSG_MORE };
/* Call udp_sendmsg to specify destination address which
* ... | 38,603,628,829,565,875,000,000,000,000,000,000,000 | udp.c | 197,428,295,876,416,400,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,598 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | int udp_seq_open(struct inode *inode, struct file *file)
{
struct udp_seq_afinfo *afinfo = PDE_DATA(inode);
struct udp_iter_state *s;
int err;
err = seq_open_net(inode, file, &afinfo->seq_ops,
sizeof(struct udp_iter_state));
if (err < 0)
return err;
s = ((struct seq_file *)file->private_data)->private;
... | 139,616,463,592,290,780,000,000,000,000,000,000,000 | udp.c | 34,572,501,297,250,960,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,599 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | void __init udp_table_init(struct udp_table *table, const char *name)
{
unsigned int i;
table->hash = alloc_large_system_hash(name,
2 * sizeof(struct udp_hslot),
uhash_entries,
21, /* one slot per 2 MB */
0,
&table->log,
&table->mask,
UDP_H... | 179,862,280,201,698,300,000,000,000,000,000,000,000 | udp.c | 273,251,318,651,126,540,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,600 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | void __udp6_lib_err(struct sk_buff *skb, struct inet6_skb_parm *opt,
u8 type, u8 code, int offset, __be32 info,
struct udp_table *udptable)
{
struct ipv6_pinfo *np;
const struct ipv6hdr *hdr = (const struct ipv6hdr *)skb->data;
const struct in6_addr *saddr = &hdr->saddr;
const struct in6_addr *daddr = &... | 48,265,444,092,189,960,000,000,000,000,000,000,000 | udp.c | 11,079,377,978,935,842,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,601 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | struct sock *__udp6_lib_lookup(struct net *net,
const struct in6_addr *saddr, __be16 sport,
const struct in6_addr *daddr, __be16 dport,
int dif, struct udp_table *udptable)
{
struct sock *sk, *result;
struct hlist_nulls_node *node;
unsigned short hnum = ntohs(dport);
unsigned int hash2... | 129,737,554,806,519,700,000,000,000,000,000,000,000 | udp.c | 11,079,377,978,935,842,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,602 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | int __udp6_lib_rcv(struct sk_buff *skb, struct udp_table *udptable,
int proto)
{
struct net *net = dev_net(skb->dev);
struct sock *sk;
struct udphdr *uh;
const struct in6_addr *saddr, *daddr;
u32 ulen = 0;
if (!pskb_may_pull(skb, sizeof(struct udphdr)))
goto discard;
saddr = &ipv6_hdr(skb)->saddr;
dadd... | 314,689,641,002,975,500,000,000,000,000,000,000,000 | udp.c | 11,079,377,978,935,842,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,603 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | static int __udpv6_queue_rcv_skb(struct sock *sk, struct sk_buff *skb)
{
int rc;
if (!ipv6_addr_any(&inet6_sk(sk)->daddr))
sock_rps_save_rxhash(sk, skb);
rc = sock_queue_rcv_skb(sk, skb);
if (rc < 0) {
int is_udplite = IS_UDPLITE(sk);
/* Note that an ENOMEM error is charged twice */
if (rc == -ENOMEM)
... | 11,453,549,908,757,925,000,000,000,000,000,000,000 | udp.c | 11,079,377,978,935,842,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,604 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | static void flush_stack(struct sock **stack, unsigned int count,
struct sk_buff *skb, unsigned int final)
{
struct sk_buff *skb1 = NULL;
struct sock *sk;
unsigned int i;
for (i = 0; i < count; i++) {
sk = stack[i];
if (likely(skb1 == NULL))
skb1 = (i == final) ? skb : skb_clone(skb, GFP_ATOMIC);
if (!s... | 231,784,788,282,481,100,000,000,000,000,000,000,000 | udp.c | 67,886,294,310,334,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,605 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | static struct sock *udp6_lib_lookup2(struct net *net,
const struct in6_addr *saddr, __be16 sport,
const struct in6_addr *daddr, unsigned int hnum, int dif,
struct udp_hslot *hslot2, unsigned int slot2)
{
struct sock *sk, *result;
struct hlist_nulls_node *node;
int score, badness, matches = 0, reuseport = 0;
u... | 30,024,302,486,200,865,000,000,000,000,000,000,000 | udp.c | 11,079,377,978,935,842,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,606 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | int udp6_seq_show(struct seq_file *seq, void *v)
{
if (v == SEQ_START_TOKEN) {
seq_puts(seq, IPV6_SEQ_DGRAM_HEADER);
} else {
int bucket = ((struct udp_iter_state *)seq->private)->bucket;
struct inet_sock *inet = inet_sk(v);
__u16 srcp = ntohs(inet->inet_sport);
__u16 destp = ntohs(inet->inet_dport);
ip6_... | 216,041,829,457,868,580,000,000,000,000,000,000,000 | udp.c | 245,096,869,505,899,420,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,607 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | void udp_v6_clear_sk(struct sock *sk, int size)
{
struct inet_sock *inet = inet_sk(sk);
/* we do not want to clear pinet6 field, because of RCU lookups */
sk_prot_clear_portaddr_nulls(sk, offsetof(struct inet_sock, pinet6));
size -= offsetof(struct inet_sock, pinet6) + sizeof(inet->pinet6);
memset(&inet->pinet6 ... | 259,772,707,497,024,660,000,000,000,000,000,000,000 | udp.c | 245,096,869,505,899,420,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,608 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | void udpv6_destroy_sock(struct sock *sk)
{
struct udp_sock *up = udp_sk(sk);
lock_sock(sk);
udp_v6_flush_pending_frames(sk);
release_sock(sk);
if (static_key_false(&udpv6_encap_needed) && up->encap_type) {
void (*encap_destroy)(struct sock *sk);
encap_destroy = ACCESS_ONCE(up->encap_destroy);
if (encap_dest... | 220,714,606,703,135,170,000,000,000,000,000,000,000 | udp.c | 245,096,869,505,899,420,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,609 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | int udpv6_queue_rcv_skb(struct sock *sk, struct sk_buff *skb)
{
struct udp_sock *up = udp_sk(sk);
int rc;
int is_udplite = IS_UDPLITE(sk);
if (!xfrm6_policy_check(sk, XFRM_POLICY_IN, skb))
goto drop;
if (static_key_false(&udpv6_encap_needed) && up->encap_type) {
int (*encap_rcv)(struct sock *sk, struct sk_bu... | 41,992,303,159,905,475,000,000,000,000,000,000,000 | udp.c | 67,886,294,310,334,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,610 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | int udpv6_sendmsg(struct kiocb *iocb, struct sock *sk,
struct msghdr *msg, size_t len)
{
struct ipv6_txoptions opt_space;
struct udp_sock *up = udp_sk(sk);
struct inet_sock *inet = inet_sk(sk);
struct ipv6_pinfo *np = inet6_sk(sk);
struct sockaddr_in6 *sin6 = (struct sockaddr_in6 *) msg->msg_name;
struct in6_... | 66,810,573,445,956,140,000,000,000,000,000,000,000 | udp.c | 11,079,377,978,935,842,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
31,611 | linux | c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | bridge: fix some kernel warning in multicast timer
Several people reported the warning: "kernel BUG at kernel/timer.c:729!"
and the stack trace is:
#7 [ffff880214d25c10] mod_timer+501 at ffffffff8106d905
#8 [ffff880214d25c50] br_multicast_del_pg.isra.20+261 at ffffffffa0731d25 [bridge]
#9 [ffff880214d25c80] br_mul... | 0 | static int __br_mdb_add(struct net *net, struct net_bridge *br,
struct br_mdb_entry *entry)
{
struct br_ip ip;
struct net_device *dev;
struct net_bridge_port *p;
int ret;
if (!netif_running(br->dev) || br->multicast_disabled)
return -EINVAL;
dev = __dev_get_by_index(net, entry->ifindex);
if (!dev)
retur... | 222,137,537,297,733,800,000,000,000,000,000,000,000 | br_mdb.c | 123,212,080,278,406,970,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4129 | The bridge multicast implementation in the Linux kernel through 3.10.3 does not check whether a certain timer is armed before modifying the timeout value of that timer, which allows local users to cause a denial of service (BUG and system crash) via vectors involving the shutdown of a KVM virtual machine, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2013-4129 |
31,612 | linux | c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | bridge: fix some kernel warning in multicast timer
Several people reported the warning: "kernel BUG at kernel/timer.c:729!"
and the stack trace is:
#7 [ffff880214d25c10] mod_timer+501 at ffffffff8106d905
#8 [ffff880214d25c50] br_multicast_del_pg.isra.20+261 at ffffffffa0731d25 [bridge]
#9 [ffff880214d25c80] br_mul... | 0 | static void __br_mdb_notify(struct net_device *dev, struct br_mdb_entry *entry,
int type)
{
struct net *net = dev_net(dev);
struct sk_buff *skb;
int err = -ENOBUFS;
skb = nlmsg_new(rtnl_mdb_nlmsg_size(), GFP_ATOMIC);
if (!skb)
goto errout;
err = nlmsg_populate_mdb_fill(skb, dev, entry, 0, 0, type, NTF_... | 316,925,220,158,239,400,000,000,000,000,000,000,000 | br_mdb.c | 123,212,080,278,406,970,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4129 | The bridge multicast implementation in the Linux kernel through 3.10.3 does not check whether a certain timer is armed before modifying the timeout value of that timer, which allows local users to cause a denial of service (BUG and system crash) via vectors involving the shutdown of a KVM virtual machine, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2013-4129 |
31,613 | linux | c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | bridge: fix some kernel warning in multicast timer
Several people reported the warning: "kernel BUG at kernel/timer.c:729!"
and the stack trace is:
#7 [ffff880214d25c10] mod_timer+501 at ffffffff8106d905
#8 [ffff880214d25c50] br_multicast_del_pg.isra.20+261 at ffffffffa0731d25 [bridge]
#9 [ffff880214d25c80] br_mul... | 0 | static int br_mdb_add(struct sk_buff *skb, struct nlmsghdr *nlh)
{
struct net *net = sock_net(skb->sk);
struct br_mdb_entry *entry;
struct net_device *dev;
struct net_bridge *br;
int err;
err = br_mdb_parse(skb, nlh, &dev, &entry);
if (err < 0)
return err;
br = netdev_priv(dev);
err = __br_mdb_add(net, br... | 33,780,793,280,192,630,000,000,000,000,000,000,000 | br_mdb.c | 123,212,080,278,406,970,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4129 | The bridge multicast implementation in the Linux kernel through 3.10.3 does not check whether a certain timer is armed before modifying the timeout value of that timer, which allows local users to cause a denial of service (BUG and system crash) via vectors involving the shutdown of a KVM virtual machine, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2013-4129 |
31,614 | linux | c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | bridge: fix some kernel warning in multicast timer
Several people reported the warning: "kernel BUG at kernel/timer.c:729!"
and the stack trace is:
#7 [ffff880214d25c10] mod_timer+501 at ffffffff8106d905
#8 [ffff880214d25c50] br_multicast_del_pg.isra.20+261 at ffffffffa0731d25 [bridge]
#9 [ffff880214d25c80] br_mul... | 0 | static int br_mdb_add_group(struct net_bridge *br, struct net_bridge_port *port,
struct br_ip *group, unsigned char state)
{
struct net_bridge_mdb_entry *mp;
struct net_bridge_port_group *p;
struct net_bridge_port_group __rcu **pp;
struct net_bridge_mdb_htable *mdb;
int err;
mdb = mlock_dereference(br->md... | 195,804,913,618,198,260,000,000,000,000,000,000,000 | br_mdb.c | 123,212,080,278,406,970,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4129 | The bridge multicast implementation in the Linux kernel through 3.10.3 does not check whether a certain timer is armed before modifying the timeout value of that timer, which allows local users to cause a denial of service (BUG and system crash) via vectors involving the shutdown of a KVM virtual machine, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2013-4129 |
31,615 | linux | c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | bridge: fix some kernel warning in multicast timer
Several people reported the warning: "kernel BUG at kernel/timer.c:729!"
and the stack trace is:
#7 [ffff880214d25c10] mod_timer+501 at ffffffff8106d905
#8 [ffff880214d25c50] br_multicast_del_pg.isra.20+261 at ffffffffa0731d25 [bridge]
#9 [ffff880214d25c80] br_mul... | 0 | static int br_mdb_del(struct sk_buff *skb, struct nlmsghdr *nlh)
{
struct net_device *dev;
struct br_mdb_entry *entry;
struct net_bridge *br;
int err;
err = br_mdb_parse(skb, nlh, &dev, &entry);
if (err < 0)
return err;
br = netdev_priv(dev);
err = __br_mdb_del(br, entry);
if (!err)
__br_mdb_notify(dev,... | 308,616,497,462,275,970,000,000,000,000,000,000,000 | br_mdb.c | 123,212,080,278,406,970,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4129 | The bridge multicast implementation in the Linux kernel through 3.10.3 does not check whether a certain timer is armed before modifying the timeout value of that timer, which allows local users to cause a denial of service (BUG and system crash) via vectors involving the shutdown of a KVM virtual machine, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2013-4129 |
31,616 | linux | c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | bridge: fix some kernel warning in multicast timer
Several people reported the warning: "kernel BUG at kernel/timer.c:729!"
and the stack trace is:
#7 [ffff880214d25c10] mod_timer+501 at ffffffff8106d905
#8 [ffff880214d25c50] br_multicast_del_pg.isra.20+261 at ffffffffa0731d25 [bridge]
#9 [ffff880214d25c80] br_mul... | 0 | static int br_mdb_dump(struct sk_buff *skb, struct netlink_callback *cb)
{
struct net_device *dev;
struct net *net = sock_net(skb->sk);
struct nlmsghdr *nlh = NULL;
int idx = 0, s_idx;
s_idx = cb->args[0];
rcu_read_lock();
/* In theory this could be wrapped to 0... */
cb->seq = net->dev_base_seq + br_mdb_reh... | 232,169,171,286,612,770,000,000,000,000,000,000,000 | br_mdb.c | 123,212,080,278,406,970,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4129 | The bridge multicast implementation in the Linux kernel through 3.10.3 does not check whether a certain timer is armed before modifying the timeout value of that timer, which allows local users to cause a denial of service (BUG and system crash) via vectors involving the shutdown of a KVM virtual machine, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2013-4129 |
31,617 | linux | c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | bridge: fix some kernel warning in multicast timer
Several people reported the warning: "kernel BUG at kernel/timer.c:729!"
and the stack trace is:
#7 [ffff880214d25c10] mod_timer+501 at ffffffff8106d905
#8 [ffff880214d25c50] br_multicast_del_pg.isra.20+261 at ffffffffa0731d25 [bridge]
#9 [ffff880214d25c80] br_mul... | 0 | static int br_mdb_fill_info(struct sk_buff *skb, struct netlink_callback *cb,
struct net_device *dev)
{
struct net_bridge *br = netdev_priv(dev);
struct net_bridge_mdb_htable *mdb;
struct nlattr *nest, *nest2;
int i, err = 0;
int idx = 0, s_idx = cb->args[1];
if (br->multicast_disabled)
return 0;
mdb ... | 8,555,647,361,424,232,000,000,000,000,000,000,000 | br_mdb.c | 123,212,080,278,406,970,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4129 | The bridge multicast implementation in the Linux kernel through 3.10.3 does not check whether a certain timer is armed before modifying the timeout value of that timer, which allows local users to cause a denial of service (BUG and system crash) via vectors involving the shutdown of a KVM virtual machine, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2013-4129 |
31,618 | linux | c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | bridge: fix some kernel warning in multicast timer
Several people reported the warning: "kernel BUG at kernel/timer.c:729!"
and the stack trace is:
#7 [ffff880214d25c10] mod_timer+501 at ffffffff8106d905
#8 [ffff880214d25c50] br_multicast_del_pg.isra.20+261 at ffffffffa0731d25 [bridge]
#9 [ffff880214d25c80] br_mul... | 0 | void br_mdb_init(void)
{
rtnl_register(PF_BRIDGE, RTM_GETMDB, NULL, br_mdb_dump, NULL);
rtnl_register(PF_BRIDGE, RTM_NEWMDB, br_mdb_add, NULL, NULL);
rtnl_register(PF_BRIDGE, RTM_DELMDB, br_mdb_del, NULL, NULL);
}
| 323,171,408,487,751,940,000,000,000,000,000,000,000 | br_mdb.c | 123,212,080,278,406,970,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4129 | The bridge multicast implementation in the Linux kernel through 3.10.3 does not check whether a certain timer is armed before modifying the timeout value of that timer, which allows local users to cause a denial of service (BUG and system crash) via vectors involving the shutdown of a KVM virtual machine, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2013-4129 |
31,619 | linux | c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | bridge: fix some kernel warning in multicast timer
Several people reported the warning: "kernel BUG at kernel/timer.c:729!"
and the stack trace is:
#7 [ffff880214d25c10] mod_timer+501 at ffffffff8106d905
#8 [ffff880214d25c50] br_multicast_del_pg.isra.20+261 at ffffffffa0731d25 [bridge]
#9 [ffff880214d25c80] br_mul... | 0 | void br_mdb_notify(struct net_device *dev, struct net_bridge_port *port,
struct br_ip *group, int type)
{
struct br_mdb_entry entry;
memset(&entry, 0, sizeof(entry));
entry.ifindex = port->dev->ifindex;
entry.addr.proto = group->proto;
entry.addr.u.ip4 = group->u.ip4;
#if IS_ENABLED(CONFIG_IPV6)
entry.addr.... | 130,272,528,257,047,970,000,000,000,000,000,000,000 | br_mdb.c | 123,212,080,278,406,970,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4129 | The bridge multicast implementation in the Linux kernel through 3.10.3 does not check whether a certain timer is armed before modifying the timeout value of that timer, which allows local users to cause a denial of service (BUG and system crash) via vectors involving the shutdown of a KVM virtual machine, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2013-4129 |
31,620 | linux | c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | bridge: fix some kernel warning in multicast timer
Several people reported the warning: "kernel BUG at kernel/timer.c:729!"
and the stack trace is:
#7 [ffff880214d25c10] mod_timer+501 at ffffffff8106d905
#8 [ffff880214d25c50] br_multicast_del_pg.isra.20+261 at ffffffffa0731d25 [bridge]
#9 [ffff880214d25c80] br_mul... | 0 | static int br_mdb_parse(struct sk_buff *skb, struct nlmsghdr *nlh,
struct net_device **pdev, struct br_mdb_entry **pentry)
{
struct net *net = sock_net(skb->sk);
struct br_mdb_entry *entry;
struct br_port_msg *bpm;
struct nlattr *tb[MDBA_SET_ENTRY_MAX+1];
struct net_device *dev;
int err;
err = nlmsg_parse(nl... | 5,770,388,487,470,172,000,000,000,000,000,000,000 | br_mdb.c | 123,212,080,278,406,970,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4129 | The bridge multicast implementation in the Linux kernel through 3.10.3 does not check whether a certain timer is armed before modifying the timeout value of that timer, which allows local users to cause a denial of service (BUG and system crash) via vectors involving the shutdown of a KVM virtual machine, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2013-4129 |
31,621 | linux | c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | bridge: fix some kernel warning in multicast timer
Several people reported the warning: "kernel BUG at kernel/timer.c:729!"
and the stack trace is:
#7 [ffff880214d25c10] mod_timer+501 at ffffffff8106d905
#8 [ffff880214d25c50] br_multicast_del_pg.isra.20+261 at ffffffffa0731d25 [bridge]
#9 [ffff880214d25c80] br_mul... | 0 | void br_mdb_uninit(void)
{
rtnl_unregister(PF_BRIDGE, RTM_GETMDB);
rtnl_unregister(PF_BRIDGE, RTM_NEWMDB);
rtnl_unregister(PF_BRIDGE, RTM_DELMDB);
}
| 300,154,913,234,350,940,000,000,000,000,000,000,000 | br_mdb.c | 123,212,080,278,406,970,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4129 | The bridge multicast implementation in the Linux kernel through 3.10.3 does not check whether a certain timer is armed before modifying the timeout value of that timer, which allows local users to cause a denial of service (BUG and system crash) via vectors involving the shutdown of a KVM virtual machine, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2013-4129 |
31,622 | linux | c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | bridge: fix some kernel warning in multicast timer
Several people reported the warning: "kernel BUG at kernel/timer.c:729!"
and the stack trace is:
#7 [ffff880214d25c10] mod_timer+501 at ffffffff8106d905
#8 [ffff880214d25c50] br_multicast_del_pg.isra.20+261 at ffffffffa0731d25 [bridge]
#9 [ffff880214d25c80] br_mul... | 0 | static int br_rports_fill_info(struct sk_buff *skb, struct netlink_callback *cb,
struct net_device *dev)
{
struct net_bridge *br = netdev_priv(dev);
struct net_bridge_port *p;
struct nlattr *nest;
if (!br->multicast_router || hlist_empty(&br->router_list))
return 0;
nest = nla_nest_start(skb, MDBA_RO... | 317,357,874,668,680,580,000,000,000,000,000,000,000 | br_mdb.c | 123,212,080,278,406,970,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4129 | The bridge multicast implementation in the Linux kernel through 3.10.3 does not check whether a certain timer is armed before modifying the timeout value of that timer, which allows local users to cause a denial of service (BUG and system crash) via vectors involving the shutdown of a KVM virtual machine, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2013-4129 |
31,623 | linux | c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | bridge: fix some kernel warning in multicast timer
Several people reported the warning: "kernel BUG at kernel/timer.c:729!"
and the stack trace is:
#7 [ffff880214d25c10] mod_timer+501 at ffffffff8106d905
#8 [ffff880214d25c50] br_multicast_del_pg.isra.20+261 at ffffffffa0731d25 [bridge]
#9 [ffff880214d25c80] br_mul... | 0 | static bool is_valid_mdb_entry(struct br_mdb_entry *entry)
{
if (entry->ifindex == 0)
return false;
if (entry->addr.proto == htons(ETH_P_IP)) {
if (!ipv4_is_multicast(entry->addr.u.ip4))
return false;
if (ipv4_is_local_multicast(entry->addr.u.ip4))
return false;
#if IS_ENABLED(CONFIG_IPV6)
} else if (en... | 187,479,080,729,393,930,000,000,000,000,000,000,000 | br_mdb.c | 123,212,080,278,406,970,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4129 | The bridge multicast implementation in the Linux kernel through 3.10.3 does not check whether a certain timer is armed before modifying the timeout value of that timer, which allows local users to cause a denial of service (BUG and system crash) via vectors involving the shutdown of a KVM virtual machine, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2013-4129 |
31,624 | linux | c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | bridge: fix some kernel warning in multicast timer
Several people reported the warning: "kernel BUG at kernel/timer.c:729!"
and the stack trace is:
#7 [ffff880214d25c10] mod_timer+501 at ffffffff8106d905
#8 [ffff880214d25c50] br_multicast_del_pg.isra.20+261 at ffffffffa0731d25 [bridge]
#9 [ffff880214d25c80] br_mul... | 0 | static int nlmsg_populate_mdb_fill(struct sk_buff *skb,
struct net_device *dev,
struct br_mdb_entry *entry, u32 pid,
u32 seq, int type, unsigned int flags)
{
struct nlmsghdr *nlh;
struct br_port_msg *bpm;
struct nlattr *nest, *nest2;
nlh = nlmsg_put(skb, pid, seq, type, sizeof(*bpm), NLM_F_MUL... | 322,191,472,691,287,120,000,000,000,000,000,000,000 | br_mdb.c | 123,212,080,278,406,970,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4129 | The bridge multicast implementation in the Linux kernel through 3.10.3 does not check whether a certain timer is armed before modifying the timeout value of that timer, which allows local users to cause a denial of service (BUG and system crash) via vectors involving the shutdown of a KVM virtual machine, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2013-4129 |
31,625 | linux | c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | bridge: fix some kernel warning in multicast timer
Several people reported the warning: "kernel BUG at kernel/timer.c:729!"
and the stack trace is:
#7 [ffff880214d25c10] mod_timer+501 at ffffffff8106d905
#8 [ffff880214d25c50] br_multicast_del_pg.isra.20+261 at ffffffffa0731d25 [bridge]
#9 [ffff880214d25c80] br_mul... | 0 | static inline size_t rtnl_mdb_nlmsg_size(void)
{
return NLMSG_ALIGN(sizeof(struct br_port_msg))
+ nla_total_size(sizeof(struct br_mdb_entry));
}
| 39,271,230,487,493,520,000,000,000,000,000,000,000 | br_mdb.c | 123,212,080,278,406,970,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4129 | The bridge multicast implementation in the Linux kernel through 3.10.3 does not check whether a certain timer is armed before modifying the timeout value of that timer, which allows local users to cause a denial of service (BUG and system crash) via vectors involving the shutdown of a KVM virtual machine, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2013-4129 |
31,626 | linux | c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | bridge: fix some kernel warning in multicast timer
Several people reported the warning: "kernel BUG at kernel/timer.c:729!"
and the stack trace is:
#7 [ffff880214d25c10] mod_timer+501 at ffffffff8106d905
#8 [ffff880214d25c50] br_multicast_del_pg.isra.20+261 at ffffffffa0731d25 [bridge]
#9 [ffff880214d25c80] br_mul... | 0 | static inline int __br_ip4_hash(struct net_bridge_mdb_htable *mdb, __be32 ip,
__u16 vid)
{
return jhash_2words((__force u32)ip, vid, mdb->secret) & (mdb->max - 1);
}
| 206,853,075,583,925,870,000,000,000,000,000,000,000 | br_multicast.c | 184,713,466,390,494,330,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4129 | The bridge multicast implementation in the Linux kernel through 3.10.3 does not check whether a certain timer is armed before modifying the timeout value of that timer, which allows local users to cause a denial of service (BUG and system crash) via vectors involving the shutdown of a KVM virtual machine, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2013-4129 |
31,627 | linux | c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | bridge: fix some kernel warning in multicast timer
Several people reported the warning: "kernel BUG at kernel/timer.c:729!"
and the stack trace is:
#7 [ffff880214d25c10] mod_timer+501 at ffffffff8106d905
#8 [ffff880214d25c50] br_multicast_del_pg.isra.20+261 at ffffffffa0731d25 [bridge]
#9 [ffff880214d25c80] br_mul... | 0 | static inline int __br_ip6_hash(struct net_bridge_mdb_htable *mdb,
const struct in6_addr *ip,
__u16 vid)
{
return jhash_2words(ipv6_addr_hash(ip), vid,
mdb->secret) & (mdb->max - 1);
}
| 212,386,871,011,172,330,000,000,000,000,000,000,000 | br_multicast.c | 184,713,466,390,494,330,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4129 | The bridge multicast implementation in the Linux kernel through 3.10.3 does not check whether a certain timer is armed before modifying the timeout value of that timer, which allows local users to cause a denial of service (BUG and system crash) via vectors involving the shutdown of a KVM virtual machine, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2013-4129 |
31,628 | linux | c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | bridge: fix some kernel warning in multicast timer
Several people reported the warning: "kernel BUG at kernel/timer.c:729!"
and the stack trace is:
#7 [ffff880214d25c10] mod_timer+501 at ffffffff8106d905
#8 [ffff880214d25c50] br_multicast_del_pg.isra.20+261 at ffffffffa0731d25 [bridge]
#9 [ffff880214d25c80] br_mul... | 0 | static struct net_bridge_mdb_entry *__br_mdb_ip_get(
struct net_bridge_mdb_htable *mdb, struct br_ip *dst, int hash)
{
struct net_bridge_mdb_entry *mp;
hlist_for_each_entry_rcu(mp, &mdb->mhash[hash], hlist[mdb->ver]) {
if (br_ip_equal(&mp->addr, dst))
return mp;
}
return NULL;
}
| 15,792,682,280,466,006,000,000,000,000,000,000,000 | br_multicast.c | 184,713,466,390,494,330,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4129 | The bridge multicast implementation in the Linux kernel through 3.10.3 does not check whether a certain timer is armed before modifying the timeout value of that timer, which allows local users to cause a denial of service (BUG and system crash) via vectors involving the shutdown of a KVM virtual machine, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2013-4129 |
31,629 | linux | c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | bridge: fix some kernel warning in multicast timer
Several people reported the warning: "kernel BUG at kernel/timer.c:729!"
and the stack trace is:
#7 [ffff880214d25c10] mod_timer+501 at ffffffff8106d905
#8 [ffff880214d25c50] br_multicast_del_pg.isra.20+261 at ffffffffa0731d25 [bridge]
#9 [ffff880214d25c80] br_mul... | 0 | static int br_ip4_multicast_add_group(struct net_bridge *br,
struct net_bridge_port *port,
__be32 group,
__u16 vid)
{
struct br_ip br_group;
if (ipv4_is_local_multicast(group))
return 0;
br_group.u.ip4 = group;
br_group.proto = htons(ETH_P_IP);
br_group.vid = vid;
return br_mult... | 217,469,939,142,443,800,000,000,000,000,000,000,000 | br_multicast.c | 184,713,466,390,494,330,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4129 | The bridge multicast implementation in the Linux kernel through 3.10.3 does not check whether a certain timer is armed before modifying the timeout value of that timer, which allows local users to cause a denial of service (BUG and system crash) via vectors involving the shutdown of a KVM virtual machine, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2013-4129 |
31,630 | linux | c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | bridge: fix some kernel warning in multicast timer
Several people reported the warning: "kernel BUG at kernel/timer.c:729!"
and the stack trace is:
#7 [ffff880214d25c10] mod_timer+501 at ffffffff8106d905
#8 [ffff880214d25c50] br_multicast_del_pg.isra.20+261 at ffffffffa0731d25 [bridge]
#9 [ffff880214d25c80] br_mul... | 0 | static struct sk_buff *br_ip4_multicast_alloc_query(struct net_bridge *br,
__be32 group)
{
struct sk_buff *skb;
struct igmphdr *ih;
struct ethhdr *eth;
struct iphdr *iph;
skb = netdev_alloc_skb_ip_align(br->dev, sizeof(*eth) + sizeof(*iph) +
sizeof(*ih) + 4);
if (!skb)
goto out;
skb->protoco... | 103,031,142,829,206,330,000,000,000,000,000,000,000 | br_multicast.c | 184,713,466,390,494,330,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4129 | The bridge multicast implementation in the Linux kernel through 3.10.3 does not check whether a certain timer is armed before modifying the timeout value of that timer, which allows local users to cause a denial of service (BUG and system crash) via vectors involving the shutdown of a KVM virtual machine, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2013-4129 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.