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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
39,634 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | static inline int fetch_robust_entry(struct robust_list __user **entry,
struct robust_list __user * __user *head,
int *pi)
{
unsigned long uentry;
if (get_user(uentry, (unsigned long __user *)head))
return -EFAULT;
*entry = (void __user *)(uentry & ~1UL);
*pi = uentry & 1;
return 0;
}
| 141,651,844,009,288,180,000,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,635 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | static int fixup_owner(u32 __user *uaddr, int fshared, struct futex_q *q,
int locked)
{
struct task_struct *owner;
int ret = 0;
if (locked) {
/*
* Got the lock. We might not be the anticipated owner if we
* did a lock-steal - fix up the PI-state in that case:
*/
if (q->pi_state->owner != curre... | 2,625,528,272,206,088,700,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,636 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | static int __init futex_init(void)
{
u32 curval;
int i;
/*
* This will fail and we want it. Some arch implementations do
* runtime detection of the futex_atomic_cmpxchg_inatomic()
* functionality. We want to know that before we call in any
* of the complex code paths. Also we want to prevent
* registratio... | 2,071,913,706,054,977,600,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,637 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | static int futex_lock_pi(u32 __user *uaddr, int fshared,
int detect, ktime_t *time, int trylock)
{
struct hrtimer_sleeper timeout, *to = NULL;
struct futex_hash_bucket *hb;
struct futex_q q;
int res, ret;
if (refill_pi_state_cache())
return -ENOMEM;
if (time) {
to = &timeout;
hrtimer_init_on_stack(&to... | 313,081,896,396,572,500,000,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,638 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | static int futex_lock_pi_atomic(u32 __user *uaddr, struct futex_hash_bucket *hb,
union futex_key *key,
struct futex_pi_state **ps,
struct task_struct *task, int set_waiters)
{
int lock_taken, ret, ownerdied = 0;
u32 uval, newval, curval;
retry:
ret = lock_taken = 0;
/*
* To avoid races, we attempt t... | 325,572,980,175,164,900,000,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,639 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | static int futex_proxy_trylock_atomic(u32 __user *pifutex,
struct futex_hash_bucket *hb1,
struct futex_hash_bucket *hb2,
union futex_key *key1, union futex_key *key2,
struct futex_pi_state **ps, int set_waiters)
{
struct futex_q *top_waiter = NULL;
u32 curval;
int ret;
if (get_futex_value_locke... | 96,469,885,949,863,880,000,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,640 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | static int futex_requeue(u32 __user *uaddr1, int fshared, u32 __user *uaddr2,
int nr_wake, int nr_requeue, u32 *cmpval,
int requeue_pi)
{
union futex_key key1 = FUTEX_KEY_INIT, key2 = FUTEX_KEY_INIT;
int drop_count = 0, task_count = 0, ret;
struct futex_pi_state *pi_state = NULL;
struct futex_hash_bucket *h... | 222,416,542,510,442,500,000,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,641 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | static int futex_unlock_pi(u32 __user *uaddr, int fshared)
{
struct futex_hash_bucket *hb;
struct futex_q *this, *next;
u32 uval;
struct plist_head *head;
union futex_key key = FUTEX_KEY_INIT;
int ret;
retry:
if (get_user(uval, uaddr))
return -EFAULT;
/*
* We release only a lock we actually own:
*/
if (... | 175,685,348,151,995,340,000,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,642 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | static void futex_wait_queue_me(struct futex_hash_bucket *hb, struct futex_q *q,
struct hrtimer_sleeper *timeout)
{
/*
* The task state is guaranteed to be set before another task can
* wake it. set_current_state() is implemented using set_mb() and
* queue_me() calls spin_unlock() upon completion, both seria... | 269,792,059,783,447,030,000,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,643 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | static long futex_wait_restart(struct restart_block *restart)
{
u32 __user *uaddr = (u32 __user *)restart->futex.uaddr;
int fshared = 0;
ktime_t t, *tp = NULL;
if (restart->futex.flags & FLAGS_HAS_TIMEOUT) {
t.tv64 = restart->futex.time;
tp = &t;
}
restart->fn = do_no_restart_syscall;
if (restart->futex.fla... | 22,691,154,917,033,470,000,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,644 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | static int futex_wake(u32 __user *uaddr, int fshared, int nr_wake, u32 bitset)
{
struct futex_hash_bucket *hb;
struct futex_q *this, *next;
struct plist_head *head;
union futex_key key = FUTEX_KEY_INIT;
int ret;
if (!bitset)
return -EINVAL;
ret = get_futex_key(uaddr, fshared, &key);
if (unlikely(ret != 0))
... | 76,425,603,369,784,470,000,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,645 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | futex_wake_op(u32 __user *uaddr1, int fshared, u32 __user *uaddr2,
int nr_wake, int nr_wake2, int op)
{
union futex_key key1 = FUTEX_KEY_INIT, key2 = FUTEX_KEY_INIT;
struct futex_hash_bucket *hb1, *hb2;
struct plist_head *head;
struct futex_q *this, *next;
int ret, op_ret;
retry:
ret = get_futex_key(uaddr... | 23,524,001,185,344,204,000,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,646 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | get_futex_key(u32 __user *uaddr, int fshared, union futex_key *key)
{
unsigned long address = (unsigned long)uaddr;
struct mm_struct *mm = current->mm;
struct page *page;
int err;
/*
* The futex address must be "naturally" aligned.
*/
key->both.offset = address % PAGE_SIZE;
if (unlikely((address % sizeof(u3... | 198,985,195,031,848,800,000,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,647 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | static void get_futex_key_refs(union futex_key *key)
{
if (!key->both.ptr)
return;
switch (key->both.offset & (FUT_OFF_INODE|FUT_OFF_MMSHARED)) {
case FUT_OFF_INODE:
atomic_inc(&key->shared.inode->i_count);
break;
case FUT_OFF_MMSHARED:
atomic_inc(&key->private.mm->mm_count);
break;
}
}
| 211,452,984,740,100,760,000,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,648 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | int handle_early_requeue_pi_wakeup(struct futex_hash_bucket *hb,
struct futex_q *q, union futex_key *key2,
struct hrtimer_sleeper *timeout)
{
int ret = 0;
/*
* With the hb lock held, we avoid races while we process the wakeup.
* We only need to hold hb (and not hb2) to ensure atomicity as the
* w... | 170,689,741,641,364,630,000,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,649 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | int handle_futex_death(u32 __user *uaddr, struct task_struct *curr, int pi)
{
u32 uval, nval, mval;
retry:
if (get_user(uval, uaddr))
return -1;
if ((uval & FUTEX_TID_MASK) == task_pid_vnr(curr)) {
/*
* Ok, this dying thread is truly holding a futex
* of interest. Set the OWNER_DIED bit atomically
* v... | 168,438,423,718,368,130,000,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,650 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | static struct futex_hash_bucket *hash_futex(union futex_key *key)
{
u32 hash = jhash2((u32*)&key->both.word,
(sizeof(key->both.word)+sizeof(key->both.ptr))/4,
key->both.offset);
return &futex_queues[hash & ((1 << FUTEX_HASHBITS)-1)];
}
| 204,477,287,877,926,200,000,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,651 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | lookup_pi_state(u32 uval, struct futex_hash_bucket *hb,
union futex_key *key, struct futex_pi_state **ps)
{
struct futex_pi_state *pi_state = NULL;
struct futex_q *this, *next;
struct plist_head *head;
struct task_struct *p;
pid_t pid = uval & FUTEX_TID_MASK;
head = &hb->chain;
plist_for_each_entry_safe(this... | 155,891,246,346,047,040,000,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,652 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | void put_futex_key(int fshared, union futex_key *key)
{
drop_futex_key_refs(key);
}
| 248,887,169,378,038,570,000,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,653 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | static inline void queue_me(struct futex_q *q, struct futex_hash_bucket *hb)
{
int prio;
/*
* The priority used to register this element is
* - either the real thread-priority for the real-time threads
* (i.e. threads with a priority lower than MAX_RT_PRIO)
* - or MAX_RT_PRIO for non-RT threads.
* Thus, al... | 131,269,396,135,673,620,000,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,654 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | void requeue_futex(struct futex_q *q, struct futex_hash_bucket *hb1,
struct futex_hash_bucket *hb2, union futex_key *key2)
{
/*
* If key1 and key2 hash to the same bucket, no need to
* requeue.
*/
if (likely(&hb1->chain != &hb2->chain)) {
plist_del(&q->list, &hb1->chain);
plist_add(&q->list, &hb2->cha... | 115,487,187,682,105,350,000,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,655 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | void requeue_pi_wake_futex(struct futex_q *q, union futex_key *key,
struct futex_hash_bucket *hb)
{
get_futex_key_refs(key);
q->key = *key;
WARN_ON(plist_node_empty(&q->list));
plist_del(&q->list, &q->list.plist);
WARN_ON(!q->rt_waiter);
q->rt_waiter = NULL;
q->lock_ptr = &hb->lock;
#ifdef CONFIG_DEBUG_... | 203,592,790,157,401,600,000,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,656 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | static int unlock_futex_pi(u32 __user *uaddr, u32 uval)
{
u32 oldval;
/*
* There is no waiter, so we unlock the futex. The owner died
* bit has not to be preserved here. We are the owner:
*/
oldval = cmpxchg_futex_value_locked(uaddr, uval, 0);
if (oldval == -EFAULT)
return oldval;
if (oldval != uval)
r... | 164,408,662,362,122,040,000,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,657 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | static int unqueue_me(struct futex_q *q)
{
spinlock_t *lock_ptr;
int ret = 0;
/* In the common case we don't take the spinlock, which is nice. */
retry:
lock_ptr = q->lock_ptr;
barrier();
if (lock_ptr != NULL) {
spin_lock(lock_ptr);
/*
* q->lock_ptr can change between reading it and
* spin_lock(), caus... | 158,858,731,198,554,670,000,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,658 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | static void wake_futex(struct futex_q *q)
{
struct task_struct *p = q->task;
/*
* We set q->lock_ptr = NULL _before_ we wake up the task. If
* a non futex wake up happens on another CPU then the task
* might exit and p would dereference a non existing task
* struct. Prevent this by holding a reference on p a... | 43,738,247,883,655,610,000,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,659 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | static int wake_futex_pi(u32 __user *uaddr, u32 uval, struct futex_q *this)
{
struct task_struct *new_owner;
struct futex_pi_state *pi_state = this->pi_state;
u32 curval, newval;
if (!pi_state)
return -EINVAL;
/*
* If current does not own the pi_state then the futex is
* inconsistent and user space fiddled... | 213,374,254,078,325,730,000,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
39,660 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | SYSCALL_DEFINE2(mkdir, const char __user *, pathname, int, mode)
{
return sys_mkdirat(AT_FDCWD, pathname, mode);
}
| 289,872,181,570,681,300,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,661 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | SYSCALL_DEFINE2(rename, const char __user *, oldname, const char __user *, newname)
{
return sys_renameat(AT_FDCWD, oldname, AT_FDCWD, newname);
}
| 191,495,839,112,284,430,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,662 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | SYSCALL_DEFINE3(mkdirat, int, dfd, const char __user *, pathname, int, mode)
{
int error = 0;
char * tmp;
struct dentry *dentry;
struct nameidata nd;
error = user_path_parent(dfd, pathname, &nd, &tmp);
if (error)
goto out_err;
dentry = lookup_create(&nd, 1);
error = PTR_ERR(dentry);
if (IS_ERR(dentry))
g... | 57,582,337,065,613,490,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,663 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | SYSCALL_DEFINE4(mknodat, int, dfd, const char __user *, filename, int, mode,
unsigned, dev)
{
int error;
char *tmp;
struct dentry *dentry;
struct nameidata nd;
if (S_ISDIR(mode))
return -EPERM;
error = user_path_parent(dfd, filename, &nd, &tmp);
if (error)
return error;
dentry = lookup_create(&nd, 0);
... | 122,970,224,256,743,270,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,664 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | SYSCALL_DEFINE4(renameat, int, olddfd, const char __user *, oldname,
int, newdfd, const char __user *, newname)
{
struct dentry *old_dir, *new_dir;
struct dentry *old_dentry, *new_dentry;
struct dentry *trap;
struct nameidata oldnd, newnd;
char *from;
char *to;
int error;
error = user_path_parent(olddfd, old... | 284,287,542,216,648,600,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,665 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | SYSCALL_DEFINE5(linkat, int, olddfd, const char __user *, oldname,
int, newdfd, const char __user *, newname, int, flags)
{
struct dentry *new_dentry;
struct nameidata nd;
struct path old_path;
int error;
char *to;
if ((flags & ~AT_SYMLINK_FOLLOW) != 0)
return -EINVAL;
error = user_path_at(olddfd, oldname,... | 202,120,422,427,765,840,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,666 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static int __follow_mount(struct path *path)
{
int res = 0;
while (d_mountpoint(path->dentry)) {
struct vfsmount *mounted = lookup_mnt(path);
if (!mounted)
break;
dput(path->dentry);
if (res)
mntput(path->mnt);
path->mnt = mounted;
path->dentry = dget(mounted->mnt_root);
res = 1;
}
return res;
}... | 275,822,948,606,246,950,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,667 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static struct dentry *__lookup_hash(struct qstr *name,
struct dentry *base, struct nameidata *nd)
{
struct dentry *dentry;
struct inode *inode;
int err;
inode = base->d_inode;
/*
* See if the low-level filesystem might want
* to use its own hash..
*/
if (base->d_op && base->d_op->d_hash) {
err = base-... | 115,779,872,712,361,050,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,668 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static int __lookup_one_len(const char *name, struct qstr *this,
struct dentry *base, int len)
{
unsigned long hash;
unsigned int c;
this->name = name;
this->len = len;
if (!len)
return -EACCES;
hash = init_name_hash();
while (len--) {
c = *(const unsigned char *)name++;
if (c == '/' || c == '\0')
r... | 46,483,632,174,550,880,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,669 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static int __open_namei_create(struct nameidata *nd, struct path *path,
int flag, int mode)
{
int error;
struct dentry *dir = nd->path.dentry;
if (!IS_POSIXACL(dir->d_inode))
mode &= ~current_umask();
error = security_path_mknod(&nd->path, path->dentry, mode, 0);
if (error)
goto out_unlock;
error = vfs_c... | 230,831,793,481,863,500,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,670 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | int __page_symlink(struct inode *inode, const char *symname, int len, int nofs)
{
struct address_space *mapping = inode->i_mapping;
struct page *page;
void *fsdata;
int err;
char *kaddr;
unsigned int flags = AOP_FLAG_UNINTERRUPTIBLE;
if (nofs)
flags |= AOP_FLAG_NOFS;
retry:
err = pagecache_write_begin(NULL, ... | 307,436,586,239,261,500,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,671 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static __always_inline int __vfs_follow_link(struct nameidata *nd, const char *link)
{
int res = 0;
char *name;
if (IS_ERR(link))
goto fail;
if (*link == '/') {
set_root(nd);
path_put(&nd->path);
nd->path = nd->root;
path_get(&nd->root);
}
res = link_path_walk(link, nd);
if (nd->depth || res || nd->l... | 73,908,309,227,798,510,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,672 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static int acl_permission_check(struct inode *inode, int mask,
int (*check_acl)(struct inode *inode, int mask))
{
umode_t mode = inode->i_mode;
mask &= MAY_READ | MAY_WRITE | MAY_EXEC;
if (current_fsuid() == inode->i_uid)
mode >>= 6;
else {
if (IS_POSIXACL(inode) && (mode & S_IRWXG) && check_acl) {
int... | 330,107,251,242,584,460,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,673 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static inline int check_sticky(struct inode *dir, struct inode *inode)
{
uid_t fsuid = current_fsuid();
if (!(dir->i_mode & S_ISVTX))
return 0;
if (inode->i_uid == fsuid)
return 0;
if (dir->i_uid == fsuid)
return 0;
return !capable(CAP_FOWNER);
}
| 172,466,672,956,184,030,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,674 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | void dentry_unhash(struct dentry *dentry)
{
dget(dentry);
shrink_dcache_parent(dentry);
spin_lock(&dcache_lock);
spin_lock(&dentry->d_lock);
if (atomic_read(&dentry->d_count) == 2)
__d_drop(dentry);
spin_unlock(&dentry->d_lock);
spin_unlock(&dcache_lock);
}
| 119,835,419,323,788,270,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,675 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | int deny_write_access(struct file * file)
{
struct inode *inode = file->f_path.dentry->d_inode;
spin_lock(&inode->i_lock);
if (atomic_read(&inode->i_writecount) > 0) {
spin_unlock(&inode->i_lock);
return -ETXTBSY;
}
atomic_dec(&inode->i_writecount);
spin_unlock(&inode->i_lock);
return 0;
}
| 183,625,260,313,450,740,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,676 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | struct file *do_filp_open(int dfd, const char *pathname,
int open_flag, int mode, int acc_mode)
{
struct file *filp;
struct nameidata nd;
int error;
struct path path, save;
struct dentry *dir;
int count = 0;
int will_truncate;
int flag = open_to_namei_flags(open_flag);
/*
* O_SYNC is implemented as __O_SY... | 222,156,192,724,021,220,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,677 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static inline int do_follow_link(struct path *path, struct nameidata *nd)
{
int err = -ELOOP;
if (current->link_count >= MAX_NESTED_LINKS)
goto loop;
if (current->total_link_count >= 40)
goto loop;
BUG_ON(nd->depth >= MAX_NESTED_LINKS);
cond_resched();
err = security_inode_follow_link(path->dentry, nd);
if (... | 115,746,741,847,543,340,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,678 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static int do_getname(const char __user *filename, char *page)
{
int retval;
unsigned long len = PATH_MAX;
if (!segment_eq(get_fs(), KERNEL_DS)) {
if ((unsigned long) filename >= TASK_SIZE)
return -EFAULT;
if (TASK_SIZE - (unsigned long) filename < PATH_MAX)
len = TASK_SIZE - (unsigned long) filename;
}
... | 248,954,058,977,312,540,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,679 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static int do_lookup(struct nameidata *nd, struct qstr *name,
struct path *path)
{
struct vfsmount *mnt = nd->path.mnt;
struct dentry *dentry, *parent;
struct inode *dir;
/*
* See if the low-level filesystem might want
* to use its own hash..
*/
if (nd->path.dentry->d_op && nd->path.dentry->d_op->d_ha... | 330,452,211,275,410,330,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,680 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static int do_path_lookup(int dfd, const char *name,
unsigned int flags, struct nameidata *nd)
{
int retval = path_init(dfd, name, flags, nd);
if (!retval)
retval = path_walk(name, nd);
if (unlikely(!retval && !audit_dummy_context() && nd->path.dentry &&
nd->path.dentry->d_inode))
audit_inode(name, nd->p... | 217,186,002,884,943,220,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,681 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | do_revalidate(struct dentry *dentry, struct nameidata *nd)
{
int status = dentry->d_op->d_revalidate(dentry, nd);
if (unlikely(status <= 0)) {
/*
* The dentry failed validation.
* If d_revalidate returned 0 attempt to invalidate
* the dentry otherwise d_revalidate is asking us
* to return a fail status.... | 61,045,031,884,827,660,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,682 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static long do_rmdir(int dfd, const char __user *pathname)
{
int error = 0;
char * name;
struct dentry *dentry;
struct nameidata nd;
error = user_path_parent(dfd, pathname, &nd, &name);
if (error)
return error;
switch(nd.last_type) {
case LAST_DOTDOT:
error = -ENOTEMPTY;
goto exit1;
case LAST_DOT:
er... | 103,664,314,444,215,100,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,683 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static long do_unlinkat(int dfd, const char __user *pathname)
{
int error;
char *name;
struct dentry *dentry;
struct nameidata nd;
struct inode *inode = NULL;
error = user_path_parent(dfd, pathname, &nd, &name);
if (error)
return error;
error = -EISDIR;
if (nd.last_type != LAST_NORM)
goto exit1;
nd.fla... | 339,062,792,605,735,150,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,684 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static int exec_permission(struct inode *inode)
{
int ret;
if (inode->i_op->permission) {
ret = inode->i_op->permission(inode, MAY_EXEC);
if (!ret)
goto ok;
return ret;
}
ret = acl_permission_check(inode, MAY_EXEC, inode->i_op->check_acl);
if (!ret)
goto ok;
if (capable(CAP_DAC_OVERRIDE) || capable(C... | 253,821,701,628,633,700,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,685 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | struct file *filp_open(const char *filename, int flags, int mode)
{
return do_filp_open(AT_FDCWD, filename, flags, mode, 0);
}
| 53,385,582,972,805,175,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,686 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | int follow_down(struct path *path)
{
struct vfsmount *mounted;
mounted = lookup_mnt(path);
if (mounted) {
dput(path->dentry);
mntput(path->mnt);
path->mnt = mounted;
path->dentry = dget(mounted->mnt_root);
return 1;
}
return 0;
}
| 253,763,404,006,620,650,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,687 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | int follow_up(struct path *path)
{
struct vfsmount *parent;
struct dentry *mountpoint;
spin_lock(&vfsmount_lock);
parent = path->mnt->mnt_parent;
if (parent == path->mnt) {
spin_unlock(&vfsmount_lock);
return 0;
}
mntget(parent);
mountpoint = dget(path->mnt->mnt_mountpoint);
spin_unlock(&vfsmount_lock);
d... | 337,072,904,388,806,160,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,688 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | force_reval_path(struct path *path, struct nameidata *nd)
{
int status;
struct dentry *dentry = path->dentry;
/*
* only check on filesystems where it's possible for the dentry to
* become stale. It's assumed that if this flag is set then the
* d_revalidate op will also be defined.
*/
if (!(dentry->d_sb->s_... | 170,018,180,657,904,650,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,689 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | int generic_permission(struct inode *inode, int mask,
int (*check_acl)(struct inode *inode, int mask))
{
int ret;
/*
* Do the basic POSIX ACL permission checks.
*/
ret = acl_permission_check(inode, mask, check_acl);
if (ret != -EACCES)
return ret;
/*
* Read/write DACs are always overridable.
* Execut... | 133,727,484,816,674,930,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,690 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | int generic_readlink(struct dentry *dentry, char __user *buffer, int buflen)
{
struct nameidata nd;
void *cookie;
int res;
nd.depth = 0;
cookie = dentry->d_inode->i_op->follow_link(dentry, &nd);
if (IS_ERR(cookie))
return PTR_ERR(cookie);
res = vfs_readlink(dentry, buffer, buflen, nd_get_link(&nd));
if (den... | 267,623,212,021,221,180,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,691 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | char * getname(const char __user * filename)
{
char *tmp, *result;
result = ERR_PTR(-ENOMEM);
tmp = __getname();
if (tmp) {
int retval = do_getname(filename, tmp);
result = tmp;
if (retval < 0) {
__putname(tmp);
result = ERR_PTR(retval);
}
}
audit_getname(result);
return result;
}
| 18,816,031,694,170,518,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,692 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static int handle_truncate(struct path *path)
{
struct inode *inode = path->dentry->d_inode;
int error = get_write_access(inode);
if (error)
return error;
/*
* Refuse to truncate files with mandatory locks held on them.
*/
error = locks_verify_locked(inode);
if (!error)
error = security_path_truncate(path... | 295,313,535,922,378,500,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,693 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | int inode_permission(struct inode *inode, int mask)
{
int retval;
if (mask & MAY_WRITE) {
umode_t mode = inode->i_mode;
/*
* Nobody gets write access to a read-only fs.
*/
if (IS_RDONLY(inode) &&
(S_ISREG(mode) || S_ISDIR(mode) || S_ISLNK(mode)))
return -EROFS;
/*
* Nobody gets write acce... | 248,694,449,183,005,130,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,694 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static int link_path_walk(const char *name, struct nameidata *nd)
{
struct path next;
struct inode *inode;
int err;
unsigned int lookup_flags = nd->flags;
while (*name=='/')
name++;
if (!*name)
goto return_reval;
inode = nd->path.dentry->d_inode;
if (nd->depth)
lookup_flags = LOOKUP_FOLLOW | (nd->flags... | 206,794,519,046,845,530,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,695 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | struct dentry *lookup_create(struct nameidata *nd, int is_dir)
{
struct dentry *dentry = ERR_PTR(-EEXIST);
mutex_lock_nested(&nd->path.dentry->d_inode->i_mutex, I_MUTEX_PARENT);
/*
* Yucky last component or no last component at all?
* (foo/., foo/.., /////)
*/
if (nd->last_type != LAST_NORM)
goto fail;
nd... | 90,152,285,728,561,500,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,696 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static inline int lookup_flags(unsigned int f)
{
unsigned long retval = LOOKUP_FOLLOW;
if (f & O_NOFOLLOW)
retval &= ~LOOKUP_FOLLOW;
if (f & O_DIRECTORY)
retval |= LOOKUP_DIRECTORY;
return retval;
}
| 151,827,939,500,646,040,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,697 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static struct dentry *lookup_hash(struct nameidata *nd)
{
int err;
err = exec_permission(nd->path.dentry->d_inode);
if (err)
return ERR_PTR(err);
return __lookup_hash(&nd->last, nd->path.dentry, nd);
}
| 258,832,687,004,396,270,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,698 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | struct dentry *lookup_one_len(const char *name, struct dentry *base, int len)
{
int err;
struct qstr this;
WARN_ON_ONCE(!mutex_is_locked(&base->d_inode->i_mutex));
err = __lookup_one_len(name, &this, base, len);
if (err)
return ERR_PTR(err);
err = exec_permission(base->d_inode);
if (err)
return ERR_PTR(er... | 88,938,947,708,551,900,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,699 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static inline int may_create(struct inode *dir, struct dentry *child)
{
if (child->d_inode)
return -EEXIST;
if (IS_DEADDIR(dir))
return -ENOENT;
return inode_permission(dir, MAY_WRITE | MAY_EXEC);
}
| 327,548,654,811,459,870,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,700 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static int may_delete(struct inode *dir,struct dentry *victim,int isdir)
{
int error;
if (!victim->d_inode)
return -ENOENT;
BUG_ON(victim->d_parent->d_inode != dir);
audit_inode_child(victim->d_name.name, victim, dir);
error = inode_permission(dir, MAY_WRITE | MAY_EXEC);
if (error)
return error;
if (IS_AP... | 118,188,348,372,215,850,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,701 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static int may_mknod(mode_t mode)
{
switch (mode & S_IFMT) {
case S_IFREG:
case S_IFCHR:
case S_IFBLK:
case S_IFIFO:
case S_IFSOCK:
case 0: /* zero mode translates to S_IFREG */
return 0;
case S_IFDIR:
return -EPERM;
default:
return -EINVAL;
}
}
| 16,517,759,485,569,024,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,702 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | int may_open(struct path *path, int acc_mode, int flag)
{
struct dentry *dentry = path->dentry;
struct inode *inode = dentry->d_inode;
int error;
if (!inode)
return -ENOENT;
switch (inode->i_mode & S_IFMT) {
case S_IFLNK:
return -ELOOP;
case S_IFDIR:
if (acc_mode & MAY_WRITE)
return -EISDIR;
break;
... | 119,339,563,633,246,200,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,703 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static inline int open_to_namei_flags(int flag)
{
if ((flag+1) & O_ACCMODE)
flag++;
return flag;
}
| 100,226,100,479,755,440,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,704 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static int open_will_truncate(int flag, struct inode *inode)
{
/*
* We'll never write to the fs underlying
* a device file.
*/
if (special_file(inode->i_mode))
return 0;
return (flag & O_TRUNC);
}
| 278,796,184,088,283,750,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,705 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | int page_readlink(struct dentry *dentry, char __user *buffer, int buflen)
{
struct page *page = NULL;
char *s = page_getlink(dentry, &page);
int res = vfs_readlink(dentry,buffer,buflen,s);
if (page) {
kunmap(page);
page_cache_release(page);
}
return res;
}
| 235,730,651,229,743,450,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,706 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static int path_init(int dfd, const char *name, unsigned int flags, struct nameidata *nd)
{
int retval = 0;
int fput_needed;
struct file *file;
nd->last_type = LAST_ROOT; /* if there are only slashes... */
nd->flags = flags;
nd->depth = 0;
nd->root.mnt = NULL;
if (*name=='/') {
set_root(nd);
nd->path = nd... | 99,300,220,523,539,730,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,707 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | void path_put(struct path *path)
{
dput(path->dentry);
mntput(path->mnt);
}
| 327,370,642,506,489,570,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,708 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static inline void path_to_nameidata(struct path *path, struct nameidata *nd)
{
dput(nd->path.dentry);
if (nd->path.mnt != path->mnt)
mntput(nd->path.mnt);
nd->path.mnt = path->mnt;
nd->path.dentry = path->dentry;
}
| 205,969,784,782,530,520,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,709 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static int path_walk(const char *name, struct nameidata *nd)
{
struct path save = nd->path;
int result;
current->total_link_count = 0;
/* make sure the stuff we saved doesn't go away */
path_get(&save);
result = link_path_walk(name, nd);
if (result == -ESTALE) {
/* nd->path had been dropped */
current->to... | 261,977,364,114,742,620,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,710 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | void putname(const char *name)
{
if (unlikely(!audit_dummy_context()))
audit_putname(name);
else
__putname(name);
}
| 112,214,863,697,928,530,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,711 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static __always_inline void set_root(struct nameidata *nd)
{
if (!nd->root.mnt) {
struct fs_struct *fs = current->fs;
read_lock(&fs->lock);
nd->root = fs->root;
path_get(&nd->root);
read_unlock(&fs->lock);
}
}
| 79,793,428,487,885,590,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,712 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static int user_path_parent(int dfd, const char __user *path,
struct nameidata *nd, char **name)
{
char *s = getname(path);
int error;
if (IS_ERR(s))
return PTR_ERR(s);
error = do_path_lookup(dfd, s, LOOKUP_PARENT, nd);
if (error)
putname(s);
else
*name = s;
return error;
}
| 144,515,811,268,591,640,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,713 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | int vfs_create(struct inode *dir, struct dentry *dentry, int mode,
struct nameidata *nd)
{
int error = may_create(dir, dentry);
if (error)
return error;
if (!dir->i_op->create)
return -EACCES; /* shouldn't it be ENOSYS? */
mode &= S_IALLUGO;
mode |= S_IFREG;
error = security_inode_create(dir, dentry, mode... | 129,711,671,767,599,630,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,714 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | int vfs_follow_link(struct nameidata *nd, const char *link)
{
return __vfs_follow_link(nd, link);
}
| 136,530,870,454,092,510,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,715 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | int vfs_link(struct dentry *old_dentry, struct inode *dir, struct dentry *new_dentry)
{
struct inode *inode = old_dentry->d_inode;
int error;
if (!inode)
return -ENOENT;
error = may_create(dir, new_dentry);
if (error)
return error;
if (dir->i_sb != inode->i_sb)
return -EXDEV;
/*
* A link to an append... | 48,556,202,845,266,660,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,716 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | int vfs_mkdir(struct inode *dir, struct dentry *dentry, int mode)
{
int error = may_create(dir, dentry);
if (error)
return error;
if (!dir->i_op->mkdir)
return -EPERM;
mode &= (S_IRWXUGO|S_ISVTX);
error = security_inode_mkdir(dir, dentry, mode);
if (error)
return error;
vfs_dq_init(dir);
error = dir->... | 286,443,490,758,319,300,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,717 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | int vfs_path_lookup(struct dentry *dentry, struct vfsmount *mnt,
const char *name, unsigned int flags,
struct nameidata *nd)
{
int retval;
/* same as do_path_lookup */
nd->last_type = LAST_ROOT;
nd->flags = flags;
nd->depth = 0;
nd->path.dentry = dentry;
nd->path.mnt = mnt;
path_get(&nd->path);
n... | 22,666,331,378,350,916,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,718 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | int vfs_readlink(struct dentry *dentry, char __user *buffer, int buflen, const char *link)
{
int len;
len = PTR_ERR(link);
if (IS_ERR(link))
goto out;
len = strlen(link);
if (len > (unsigned) buflen)
len = buflen;
if (copy_to_user(buffer, link, len))
len = -EFAULT;
out:
return len;
}
| 70,400,709,552,969,130,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,719 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | int vfs_rename(struct inode *old_dir, struct dentry *old_dentry,
struct inode *new_dir, struct dentry *new_dentry)
{
int error;
int is_dir = S_ISDIR(old_dentry->d_inode->i_mode);
const char *old_name;
if (old_dentry->d_inode == new_dentry->d_inode)
return 0;
error = may_delete(old_dir, old_dentry, is... | 144,944,783,131,241,330,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,720 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static int vfs_rename_dir(struct inode *old_dir, struct dentry *old_dentry,
struct inode *new_dir, struct dentry *new_dentry)
{
int error = 0;
struct inode *target;
/*
* If we are going to change the parent - check write permissions,
* we'll need to flip '..'.
*/
if (new_dir != old_dir) {
error = inod... | 161,397,786,430,556,860,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,721 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static int vfs_rename_other(struct inode *old_dir, struct dentry *old_dentry,
struct inode *new_dir, struct dentry *new_dentry)
{
struct inode *target;
int error;
error = security_inode_rename(old_dir, old_dentry, new_dir, new_dentry);
if (error)
return error;
dget(new_dentry);
target = new_dentry->d_i... | 84,471,041,689,519,020,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,722 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | int vfs_rmdir(struct inode *dir, struct dentry *dentry)
{
int error = may_delete(dir, dentry, 1);
if (error)
return error;
if (!dir->i_op->rmdir)
return -EPERM;
vfs_dq_init(dir);
mutex_lock(&dentry->d_inode->i_mutex);
dentry_unhash(dentry);
if (d_mountpoint(dentry))
error = -EBUSY;
else {
error = se... | 36,037,075,536,244,834,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,723 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | int vfs_symlink(struct inode *dir, struct dentry *dentry, const char *oldname)
{
int error = may_create(dir, dentry);
if (error)
return error;
if (!dir->i_op->symlink)
return -EPERM;
error = security_inode_symlink(dir, dentry, oldname);
if (error)
return error;
vfs_dq_init(dir);
error = dir->i_op->syml... | 12,254,718,573,051,011,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,724 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | int vfs_unlink(struct inode *dir, struct dentry *dentry)
{
int error = may_delete(dir, dentry, 0);
if (error)
return error;
if (!dir->i_op->unlink)
return -EPERM;
vfs_dq_init(dir);
mutex_lock(&dentry->d_inode->i_mutex);
if (d_mountpoint(dentry))
error = -EBUSY;
else {
error = security_inode_unlink(di... | 15,767,691,418,311,256,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,725 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | void added_exe_file_vma(struct mm_struct *mm)
{
mm->num_exe_file_vmas++;
}
| 91,692,920,051,852,590,000,000,000,000,000,000,000 | base.c | 97,077,772,234,708,240,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,726 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static int check_mem_permission(struct task_struct *task)
{
/*
* A task can always look at itself, in case it chooses
* to use system calls instead of load instructions.
*/
if (task == current)
return 0;
/*
* If current is actively ptrace'ing, and would also be
* permitted to freshly attach with ptrace ... | 249,547,695,666,540,950,000,000,000,000,000,000,000 | base.c | 97,077,772,234,708,240,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,727 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static int comm_open(struct inode *inode, struct file *filp)
{
int ret;
ret = single_open(filp, comm_show, NULL);
if (!ret) {
struct seq_file *m = filp->private_data;
m->private = inode;
}
return ret;
}
| 250,468,720,293,524,300,000,000,000,000,000,000,000 | base.c | 97,077,772,234,708,240,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,728 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | void dup_mm_exe_file(struct mm_struct *oldmm, struct mm_struct *newmm)
{
/* It's safe to write the exe_file pointer without exe_file_lock because
* this is called during fork when the task is not yet in /proc */
newmm->exe_file = get_mm_exe_file(oldmm);
}
| 11,161,431,625,250,126,000,000,000,000,000,000,000 | base.c | 97,077,772,234,708,240,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,729 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static ssize_t environ_read(struct file *file, char __user *buf,
size_t count, loff_t *ppos)
{
struct task_struct *task = get_proc_task(file->f_dentry->d_inode);
char *page;
unsigned long src = *ppos;
int ret = -ESRCH;
struct mm_struct *mm;
if (!task)
goto out_no_task;
if (!ptrace_may_access(task, PTRACE_... | 257,608,711,390,750,200,000,000,000,000,000,000,000 | base.c | 97,077,772,234,708,240,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,730 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | struct file *get_mm_exe_file(struct mm_struct *mm)
{
struct file *exe_file;
/* We need mmap_sem to protect against races with removal of
* VM_EXECUTABLE vmas */
down_read(&mm->mmap_sem);
exe_file = mm->exe_file;
if (exe_file)
get_file(exe_file);
up_read(&mm->mmap_sem);
return exe_file;
}
| 185,137,246,964,688,680,000,000,000,000,000,000,000 | base.c | 97,077,772,234,708,240,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,731 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static int get_nr_threads(struct task_struct *tsk)
{
unsigned long flags;
int count = 0;
if (lock_task_sighand(tsk, &flags)) {
count = atomic_read(&tsk->signal->count);
unlock_task_sighand(tsk, &flags);
}
return count;
}
| 316,112,392,963,096,580,000,000,000,000,000,000,000 | base.c | 97,077,772,234,708,240,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,732 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static int lstats_show_proc(struct seq_file *m, void *v)
{
int i;
struct inode *inode = m->private;
struct task_struct *task = get_proc_task(inode);
if (!task)
return -ESRCH;
seq_puts(m, "Latency Top version : v0.1\n");
for (i = 0; i < 32; i++) {
if (task->latency_record[i].backtrace[0]) {
int q;
seq_p... | 130,990,866,146,731,160,000,000,000,000,000,000,000 | base.c | 97,077,772,234,708,240,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
39,733 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static int mem_open(struct inode* inode, struct file* file)
{
file->private_data = (void*)((long)current->self_exec_id);
return 0;
}
| 22,569,910,710,169,160,000,000,000,000,000,000,000 | base.c | 97,077,772,234,708,240,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.