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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
37,146 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | int generic_permission(struct inode *inode, int mask)
{
int ret;
/*
* Do the basic permission checks.
*/
ret = acl_permission_check(inode, mask);
if (ret != -EACCES)
return ret;
if (S_ISDIR(inode->i_mode)) {
/* DACs are overridable for directories */
if (capable_wrt_inode_uidgid(inode, CAP_DAC_OVERRIDE... | 193,654,471,671,808,700,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,147 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | getname(const char __user * filename)
{
return getname_flags(filename, 0, NULL);
}
| 229,269,825,715,320,000,000,000,000,000,000,000,000 | namei.c | 40,476,466,110,984,527,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,148 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | getname_flags(const char __user *filename, int flags, int *empty)
{
struct filename *result, *err;
int len;
long max;
char *kname;
result = audit_reusename(filename);
if (result)
return result;
result = __getname();
if (unlikely(!result))
return ERR_PTR(-ENOMEM);
/*
* First, try to embed the struct fi... | 196,419,530,904,888,140,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,149 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | getname_kernel(const char * filename)
{
struct filename *result;
char *kname;
int len;
len = strlen(filename);
if (len >= EMBEDDED_NAME_MAX)
return ERR_PTR(-ENAMETOOLONG);
result = __getname();
if (unlikely(!result))
return ERR_PTR(-ENOMEM);
kname = (char *)result + sizeof(*result);
result->name = kname... | 229,104,505,000,991,100,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,150 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static inline int handle_dots(struct nameidata *nd, int type)
{
if (type == LAST_DOTDOT) {
if (nd->flags & LOOKUP_RCU) {
if (follow_dotdot_rcu(nd))
return -ECHILD;
} else
follow_dotdot(nd);
}
return 0;
}
| 161,652,015,873,940,600,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,151 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static int handle_truncate(struct file *filp)
{
struct path *path = &filp->f_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(filp);
if (!error)
... | 56,615,588,134,952,410,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,152 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static inline unsigned long hash_name(const char *name, unsigned int *hashp)
{
unsigned long a, b, adata, bdata, mask, hash, len;
const struct word_at_a_time constants = WORD_AT_A_TIME_CONSTANTS;
hash = a = 0;
len = -sizeof(unsigned long);
do {
hash = (hash + a) * 9;
len += sizeof(unsigned long);
a = load_u... | 24,719,390,584,821,390,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,153 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static inline unsigned long hash_name(const char *name, unsigned int *hashp)
{
unsigned long hash = init_name_hash();
unsigned long len = 0, c;
c = (unsigned char)*name;
do {
len++;
hash = partial_name_hash(c, hash);
c = (unsigned char)name[len];
} while (c && c != '/');
*hashp = end_name_hash(hash);
retu... | 199,376,644,756,804,500,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,154 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | int inode_permission(struct inode *inode, int mask)
{
int retval;
retval = sb_permission(inode->i_sb, inode, mask);
if (retval)
return retval;
return __inode_permission(inode, mask);
}
| 98,247,686,859,725,890,000,000,000,000,000,000,000 | namei.c | 40,476,466,110,984,527,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,155 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | int kern_path(const char *name, unsigned int flags, struct path *path)
{
struct nameidata nd;
int res = do_path_lookup(AT_FDCWD, name, flags, &nd);
if (!res)
*path = nd.path;
return res;
}
| 48,259,338,220,569,080,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,156 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | struct dentry *kern_path_create(int dfd, const char *pathname,
struct path *path, unsigned int lookup_flags)
{
struct dentry *dentry = ERR_PTR(-EEXIST);
struct nameidata nd;
int err2;
int error;
bool is_dir = (lookup_flags & LOOKUP_DIRECTORY);
/*
* Note that only LOOKUP_REVAL and LOOKUP_DIRECTORY matter he... | 272,992,160,997,687,100,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,157 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | struct dentry *kern_path_locked(const char *name, struct path *path)
{
struct nameidata nd;
struct dentry *d;
int err = do_path_lookup(AT_FDCWD, name, LOOKUP_PARENT, &nd);
if (err)
return ERR_PTR(err);
if (nd.last_type != LAST_NORM) {
path_put(&nd.path);
return ERR_PTR(-EINVAL);
}
mutex_lock_nested(&nd.pat... | 211,110,372,516,384,700,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,158 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | kern_path_mountpoint(int dfd, const char *name, struct path *path,
unsigned int flags)
{
struct filename s = {.name = name};
return filename_mountpoint(dfd, &s, path, flags);
}
| 7,864,083,845,133,503,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,159 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static int link_path_walk(const char *name, struct nameidata *nd)
{
struct path next;
int err;
while (*name=='/')
name++;
if (!*name)
return 0;
/* At this point we know we have a real path component. */
for(;;) {
struct qstr this;
long len;
int type;
err = may_lookup(nd);
if (err)
break;
... | 214,765,861,799,865,150,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,160 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | struct dentry *lock_rename(struct dentry *p1, struct dentry *p2)
{
struct dentry *p;
if (p1 == p2) {
mutex_lock_nested(&p1->d_inode->i_mutex, I_MUTEX_PARENT);
return NULL;
}
mutex_lock(&p1->d_inode->i_sb->s_vfs_rename_mutex);
p = d_ancestor(p2, p1);
if (p) {
mutex_lock_nested(&p2->d_inode->i_mutex, I_MUT... | 234,577,166,449,735,470,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,161 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static struct dentry *lookup_dcache(struct qstr *name, struct dentry *dir,
unsigned int flags, bool *need_lookup)
{
struct dentry *dentry;
int error;
*need_lookup = false;
dentry = d_lookup(dir, name);
if (dentry) {
if (dentry->d_flags & DCACHE_OP_REVALIDATE) {
error = d_revalidate(dentry, flags);
... | 309,393,935,095,343,930,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,162 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static int lookup_fast(struct nameidata *nd,
struct path *path, struct inode **inode)
{
struct vfsmount *mnt = nd->path.mnt;
struct dentry *dentry, *parent = nd->path.dentry;
int need_reval = 1;
int status = 1;
int err;
/*
* Rename seqlock is not required here because in the off chance
* of a false ... | 147,129,874,348,513,400,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,163 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static struct dentry *lookup_hash(struct nameidata *nd)
{
return __lookup_hash(&nd->last, nd->path.dentry, nd->flags);
}
| 281,951,333,664,497,400,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,164 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static inline int lookup_last(struct nameidata *nd, struct path *path)
{
if (nd->last_type == LAST_NORM && nd->last.name[nd->last.len])
nd->flags |= LOOKUP_FOLLOW | LOOKUP_DIRECTORY;
nd->flags &= ~LOOKUP_PARENT;
return walk_component(nd, path, nd->flags & LOOKUP_FOLLOW);
}
| 284,241,831,236,341,200,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,165 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | struct dentry *lookup_one_len(const char *name, struct dentry *base, int len)
{
struct qstr this;
unsigned int c;
int err;
WARN_ON_ONCE(!mutex_is_locked(&base->d_inode->i_mutex));
this.name = name;
this.len = len;
this.hash = full_name_hash(name, len);
if (!len)
return ERR_PTR(-EACCES);
if (unlikely(name[... | 49,260,825,161,676,540,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,166 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static int lookup_open(struct nameidata *nd, struct path *path,
struct file *file,
const struct open_flags *op,
bool got_write, int *opened)
{
struct dentry *dir = nd->path.dentry;
struct inode *dir_inode = dir->d_inode;
struct dentry *dentry;
int error;
bool need_lookup;
*opened &= ~FILE_CREATED;
dent... | 255,922,941,840,995,570,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,167 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static struct dentry *lookup_real(struct inode *dir, struct dentry *dentry,
unsigned int flags)
{
struct dentry *old;
/* Don't create child dentry for a dead directory. */
if (unlikely(IS_DEADDIR(dir))) {
dput(dentry);
return ERR_PTR(-ENOENT);
}
old = dir->i_op->lookup(dir, dentry, flags);
if (unlikel... | 243,690,125,696,541,900,000,000,000,000,000,000,000 | namei.c | 40,476,466,110,984,527,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,168 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static int lookup_slow(struct nameidata *nd, struct path *path)
{
struct dentry *dentry, *parent;
int err;
parent = nd->path.dentry;
BUG_ON(nd->inode != parent->d_inode);
mutex_lock(&parent->d_inode->i_mutex);
dentry = __lookup_hash(&nd->last, parent, nd->flags);
mutex_unlock(&parent->d_inode->i_mutex);
if (I... | 232,592,599,502,022,150,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,169 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static inline bool managed_dentry_might_block(struct dentry *dentry)
{
return (dentry->d_flags & DCACHE_MANAGE_TRANSIT &&
dentry->d_op->d_manage(dentry, true) < 0);
}
| 90,301,957,191,525,160,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,170 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static inline int may_create(struct inode *dir, struct dentry *child)
{
audit_inode_child(dir, child, AUDIT_TYPE_CHILD_CREATE);
if (child->d_inode)
return -EEXIST;
if (IS_DEADDIR(dir))
return -ENOENT;
return inode_permission(dir, MAY_WRITE | MAY_EXEC);
}
| 40,790,339,995,189,150,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,171 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static int may_delete(struct inode *dir, struct dentry *victim, bool isdir)
{
struct inode *inode = victim->d_inode;
int error;
if (d_is_negative(victim))
return -ENOENT;
BUG_ON(!inode);
BUG_ON(victim->d_parent->d_inode != dir);
audit_inode_child(dir, victim, AUDIT_TYPE_CHILD_DELETE);
error = inode_permissi... | 337,239,184,702,035,970,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,172 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static inline int may_follow_link(struct path *link, struct nameidata *nd)
{
const struct inode *inode;
const struct inode *parent;
if (!sysctl_protected_symlinks)
return 0;
/* Allowed if owner and follower match. */
inode = link->dentry->d_inode;
if (uid_eq(current_cred()->fsuid, inode->i_uid))
return 0;
... | 157,323,817,577,516,040,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,173 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static int may_linkat(struct path *link)
{
const struct cred *cred;
struct inode *inode;
if (!sysctl_protected_hardlinks)
return 0;
cred = current_cred();
inode = link->dentry->d_inode;
/* Source inode owner (or CAP_FOWNER) can hardlink all they like,
* otherwise, it must be a safe source.
*/
if (uid_eq... | 201,205,605,449,563,630,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,174 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static inline int may_lookup(struct nameidata *nd)
{
if (nd->flags & LOOKUP_RCU) {
int err = inode_permission(nd->inode, MAY_EXEC|MAY_NOT_BLOCK);
if (err != -ECHILD)
return err;
if (unlazy_walk(nd, NULL))
return -ECHILD;
}
return inode_permission(nd->inode, MAY_EXEC);
}
| 184,604,306,794,632,160,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,175 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static int may_mknod(umode_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;
}
}
| 101,721,206,364,820,650,000,000,000,000,000,000,000 | namei.c | 40,476,466,110,984,527,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,176 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static int may_o_create(struct path *dir, struct dentry *dentry, umode_t mode)
{
int error = security_path_mknod(dir, dentry, mode, 0);
if (error)
return error;
error = inode_permission(dir->dentry->d_inode, MAY_WRITE | MAY_EXEC);
if (error)
return error;
return security_inode_create(dir->dentry->d_inode, de... | 268,810,635,608,523,920,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,177 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static int may_open(struct path *path, int acc_mode, int flag)
{
struct dentry *dentry = path->dentry;
struct inode *inode = dentry->d_inode;
int error;
/* O_PATH? */
if (!acc_mode)
return 0;
if (!inode)
return -ENOENT;
switch (inode->i_mode & S_IFMT) {
case S_IFLNK:
return -ELOOP;
case S_IFDIR:
if ... | 156,830,244,117,982,140,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,178 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | void nd_jump_link(struct nameidata *nd, struct path *path)
{
path_put(&nd->path);
nd->path = *path;
nd->inode = nd->path.dentry->d_inode;
nd->flags |= LOOKUP_JUMPED;
}
| 331,773,445,198,693,250,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,179 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static inline int nested_symlink(struct path *path, struct nameidata *nd)
{
int res;
if (unlikely(current->link_count >= MAX_NESTED_LINKS)) {
path_put_conditional(path, nd);
path_put(&nd->path);
return -ELOOP;
}
BUG_ON(nd->depth >= MAX_NESTED_LINKS);
nd->depth++;
current->link_count++;
do {
struct pat... | 12,492,941,541,916,672,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,180 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static inline int open_to_namei_flags(int flag)
{
if ((flag & O_ACCMODE) == 3)
flag--;
return flag;
}
| 154,325,697,440,692,800,000,000,000,000,000,000,000 | namei.c | 40,476,466,110,984,527,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,181 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | void *page_follow_link_light(struct dentry *dentry, struct nameidata *nd)
{
struct page *page = NULL;
nd_set_link(nd, page_getlink(dentry, &page));
return page;
}
| 172,560,219,697,225,250,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,182 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static char *page_getlink(struct dentry * dentry, struct page **ppage)
{
char *kaddr;
struct page *page;
struct address_space *mapping = dentry->d_inode->i_mapping;
page = read_mapping_page(mapping, 0, NULL);
if (IS_ERR(page))
return (char*)page;
*ppage = page;
kaddr = kmap(page);
nd_terminate_link(kaddr, den... | 308,872,366,317,682,030,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,183 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | void page_put_link(struct dentry *dentry, struct nameidata *nd, void *cookie)
{
struct page *page = cookie;
if (page) {
kunmap(page);
page_cache_release(page);
}
}
| 225,337,180,678,910,550,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,184 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | int page_readlink(struct dentry *dentry, char __user *buffer, int buflen)
{
struct page *page = NULL;
int res = readlink_copy(buffer, buflen, page_getlink(dentry, &page));
if (page) {
kunmap(page);
page_cache_release(page);
}
return res;
}
| 32,557,163,404,052,320,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,185 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | int page_symlink(struct inode *inode, const char *symname, int len)
{
return __page_symlink(inode, symname, len,
!(mapping_gfp_mask(inode->i_mapping) & __GFP_FS));
}
| 160,736,534,140,462,020,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,186 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | void path_get(const struct path *path)
{
mntget(path->mnt);
dget(path->dentry);
}
| 109,569,498,425,396,050,000,000,000,000,000,000,000 | namei.c | 40,476,466,110,984,527,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,187 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static int path_init(int dfd, const char *name, unsigned int flags,
struct nameidata *nd, struct file **fp)
{
int retval = 0;
nd->last_type = LAST_ROOT; /* if there are only slashes... */
nd->flags = flags | LOOKUP_JUMPED;
nd->depth = 0;
if (flags & LOOKUP_ROOT) {
struct dentry *root = nd->root.dentry;
... | 108,927,280,038,407,570,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,188 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static int path_lookupat(int dfd, const char *name,
unsigned int flags, struct nameidata *nd)
{
struct file *base = NULL;
struct path path;
int err;
/*
* Path walking is largely split up into 2 different synchronisation
* schemes, rcu-walk and ref-walk (explained in
* Documentation/filesystems/path-looku... | 31,070,612,013,835,024,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,189 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | path_mountpoint(int dfd, const char *name, struct path *path, unsigned int flags)
{
struct file *base = NULL;
struct nameidata nd;
int err;
err = path_init(dfd, name, flags | LOOKUP_PARENT, &nd, &base);
if (unlikely(err))
return err;
current->total_link_count = 0;
err = link_path_walk(name, &nd);
if (err)
... | 295,347,984,741,279,500,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,190 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static struct file *path_openat(int dfd, struct filename *pathname,
struct nameidata *nd, const struct open_flags *op, int flags)
{
struct file *base = NULL;
struct file *file;
struct path path;
int opened = 0;
int error;
file = get_empty_filp();
if (IS_ERR(file))
return file;
file->f_flags = op->open_fla... | 135,783,708,058,485,100,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,191 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | void path_put(const struct path *path)
{
dput(path->dentry);
mntput(path->mnt);
}
| 184,459,665,719,819,630,000,000,000,000,000,000,000 | namei.c | 40,476,466,110,984,527,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,192 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static void path_put_conditional(struct path *path, struct nameidata *nd)
{
dput(path->dentry);
if (path->mnt != nd->path.mnt)
mntput(path->mnt);
}
| 286,236,205,760,698,200,000,000,000,000,000,000,000 | namei.c | 40,476,466,110,984,527,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,193 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static inline void path_to_nameidata(const struct path *path,
struct nameidata *nd)
{
if (!(nd->flags & LOOKUP_RCU)) {
dput(nd->path.dentry);
if (nd->path.mnt != path->mnt)
mntput(nd->path.mnt);
}
nd->path.mnt = path->mnt;
nd->path.dentry = path->dentry;
}
| 291,221,335,771,744,040,000,000,000,000,000,000,000 | namei.c | 40,476,466,110,984,527,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,194 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static inline void put_link(struct nameidata *nd, struct path *link, void *cookie)
{
struct inode *inode = link->dentry->d_inode;
if (inode->i_op->put_link)
inode->i_op->put_link(link->dentry, nd, cookie);
path_put(link);
}
| 213,009,459,141,322,400,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,195 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | void putname(struct filename *name)
{
if (unlikely(!audit_dummy_context()))
return audit_putname(name);
final_putname(name);
}
| 271,666,135,120,767,400,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,196 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | int readlink_copy(char __user *buffer, int buflen, const char *link)
{
int 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;
}
| 288,072,019,572,886,160,000,000,000,000,000,000,000 | namei.c | 40,476,466,110,984,527,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,197 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static bool safe_hardlink_source(struct inode *inode)
{
umode_t mode = inode->i_mode;
/* Special files should not get pinned to the filesystem. */
if (!S_ISREG(mode))
return false;
/* Setuid files should not get pinned to the filesystem. */
if (mode & S_ISUID)
return false;
/* Executable setgid files shoul... | 95,699,370,710,095,380,000,000,000,000,000,000,000 | namei.c | 40,476,466,110,984,527,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,198 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static int sb_permission(struct super_block *sb, struct inode *inode, int mask)
{
if (unlikely(mask & MAY_WRITE)) {
umode_t mode = inode->i_mode;
/* Nobody gets write access to a read-only fs. */
if ((sb->s_flags & MS_RDONLY) &&
(S_ISREG(mode) || S_ISDIR(mode) || S_ISLNK(mode)))
return -EROFS;
}
retu... | 248,205,174,141,868,720,000,000,000,000,000,000,000 | namei.c | 40,476,466,110,984,527,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,199 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static __always_inline void set_root(struct nameidata *nd)
{
if (!nd->root.mnt)
get_fs_root(current->fs, &nd->root);
}
| 190,118,268,545,375,880,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,200 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static __always_inline void set_root_rcu(struct nameidata *nd)
{
if (!nd->root.mnt) {
struct fs_struct *fs = current->fs;
unsigned seq;
do {
seq = read_seqcount_begin(&fs->seq);
nd->root = fs->root;
nd->seq = __read_seqcount_begin(&nd->root.dentry->d_seq);
} while (read_seqcount_retry(&fs->seq, seq))... | 289,957,414,540,575,260,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,201 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static inline int should_follow_link(struct dentry *dentry, int follow)
{
return unlikely(d_is_symlink(dentry)) ? follow : 0;
}
| 43,766,106,685,829,100,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,202 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static void terminate_walk(struct nameidata *nd)
{
if (!(nd->flags & LOOKUP_RCU)) {
path_put(&nd->path);
} else {
nd->flags &= ~LOOKUP_RCU;
if (!(nd->flags & LOOKUP_ROOT))
nd->root.mnt = NULL;
rcu_read_unlock();
}
}
| 122,693,264,371,124,690,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,203 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static int unlazy_walk(struct nameidata *nd, struct dentry *dentry)
{
struct fs_struct *fs = current->fs;
struct dentry *parent = nd->path.dentry;
BUG_ON(!(nd->flags & LOOKUP_RCU));
/*
* After legitimizing the bastards, terminate_walk()
* will do the right thing for non-RCU mode, and all our
* subsequent ex... | 297,875,357,647,635,180,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,204 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | void unlock_rename(struct dentry *p1, struct dentry *p2)
{
mutex_unlock(&p1->d_inode->i_mutex);
if (p1 != p2) {
mutex_unlock(&p2->d_inode->i_mutex);
mutex_unlock(&p1->d_inode->i_sb->s_vfs_rename_mutex);
}
}
| 302,094,108,337,980,530,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,205 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | int user_path_at(int dfd, const char __user *name, unsigned flags,
struct path *path)
{
return user_path_at_empty(dfd, name, flags, path, NULL);
}
| 250,931,259,148,058,540,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,206 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | int user_path_at_empty(int dfd, const char __user *name, unsigned flags,
struct path *path, int *empty)
{
struct nameidata nd;
struct filename *tmp = getname_flags(name, flags, empty);
int err = PTR_ERR(tmp);
if (!IS_ERR(tmp)) {
BUG_ON(flags & LOOKUP_PARENT);
err = filename_lookup(dfd, tmp, flags, &nd);
... | 307,792,709,251,762,100,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,207 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | struct dentry *user_path_create(int dfd, const char __user *pathname,
struct path *path, unsigned int lookup_flags)
{
struct filename *tmp = getname(pathname);
struct dentry *res;
if (IS_ERR(tmp))
return ERR_CAST(tmp);
res = kern_path_create(dfd, tmp->name, path, lookup_flags);
putname(tmp);
return res;
}
| 6,464,367,343,891,424,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,208 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | user_path_mountpoint_at(int dfd, const char __user *name, unsigned int flags,
struct path *path)
{
struct filename *s = getname(name);
int error;
if (IS_ERR(s))
return PTR_ERR(s);
error = filename_mountpoint(dfd, s, path, flags);
putname(s);
return error;
}
| 296,841,352,065,066,730,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,209 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | user_path_parent(int dfd, const char __user *path, struct nameidata *nd,
unsigned int flags)
{
struct filename *s = getname(path);
int error;
/* only LOOKUP_REVAL is allowed in extra flags */
flags &= LOOKUP_REVAL;
if (IS_ERR(s))
return s;
error = filename_lookup(dfd, s, flags | LOOKUP_PARENT, nd);
if (e... | 227,461,597,470,066,200,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,210 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | int vfs_create(struct inode *dir, struct dentry *dentry, umode_t mode,
bool want_excl)
{
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);
... | 306,752,722,620,621,500,000,000,000,000,000,000,000 | namei.c | 40,476,466,110,984,527,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,211 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | int vfs_link(struct dentry *old_dentry, struct inode *dir, struct dentry *new_dentry, struct inode **delegated_inode)
{
struct inode *inode = old_dentry->d_inode;
unsigned max_links = dir->i_sb->s_max_links;
int error;
if (!inode)
return -ENOENT;
error = may_create(dir, new_dentry);
if (error)
return error;... | 265,529,924,168,778,650,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,212 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | int vfs_mkdir(struct inode *dir, struct dentry *dentry, umode_t mode)
{
int error = may_create(dir, dentry);
unsigned max_links = dir->i_sb->s_max_links;
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)
... | 79,420,352,931,721,510,000,000,000,000,000,000,000 | namei.c | 40,476,466,110,984,527,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,213 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | int vfs_mknod(struct inode *dir, struct dentry *dentry, umode_t mode, dev_t dev)
{
int error = may_create(dir, dentry);
if (error)
return error;
if ((S_ISCHR(mode) || S_ISBLK(mode)) && !capable(CAP_MKNOD))
return -EPERM;
if (!dir->i_op->mknod)
return -EPERM;
error = devcgroup_inode_mknod(mode, dev);
if ... | 261,121,426,532,968,930,000,000,000,000,000,000,000 | namei.c | 40,476,466,110,984,527,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,214 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | int vfs_path_lookup(struct dentry *dentry, struct vfsmount *mnt,
const char *name, unsigned int flags,
struct path *path)
{
struct nameidata nd;
int err;
nd.root.dentry = dentry;
nd.root.mnt = mnt;
BUG_ON(flags & LOOKUP_PARENT);
/* the first argument of do_path_lookup() is ignored with LOOKUP_ROOT */
... | 39,594,205,988,532,060,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,215 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | int vfs_rename(struct inode *old_dir, struct dentry *old_dentry,
struct inode *new_dir, struct dentry *new_dentry,
struct inode **delegated_inode, unsigned int flags)
{
int error;
bool is_dir = d_is_dir(old_dentry);
const unsigned char *old_name;
struct inode *source = old_dentry->d_inode;
struct i... | 128,434,707,579,331,430,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,216 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 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;
dget(dentry);
mutex_lock(&dentry->d_inode->i_mutex);
error = -EBUSY;
if (d_mountpoint(dentry))
goto out;
error = security_inode_rmdir(dir, d... | 156,117,240,404,580,450,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,217 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 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;
error = dir->i_op->symlink(dir, dentry, ol... | 154,976,412,801,739,220,000,000,000,000,000,000,000 | namei.c | 40,476,466,110,984,527,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,218 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | int vfs_unlink(struct inode *dir, struct dentry *dentry, struct inode **delegated_inode)
{
struct inode *target = dentry->d_inode;
int error = may_delete(dir, dentry, 0);
if (error)
return error;
if (!dir->i_op->unlink)
return -EPERM;
mutex_lock(&target->i_mutex);
if (d_mountpoint(dentry))
error = -EBUSY... | 169,762,951,885,403,100,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,219 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | static inline int walk_component(struct nameidata *nd, struct path *path,
int follow)
{
struct inode *inode;
int err;
/*
* "." and ".." are special - ".." especially so because it has
* to be able to know about the current root directory and
* parent relationships.
*/
if (unlikely(nd->last_type != LAST_NO... | 66,985,132,080,448,130,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
37,256 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | static int _snd_ctl_register_ioctl(snd_kctl_ioctl_func_t fcn, struct list_head *lists)
{
struct snd_kctl_ioctl *pn;
pn = kzalloc(sizeof(struct snd_kctl_ioctl), GFP_KERNEL);
if (pn == NULL)
return -ENOMEM;
pn->fioctl = fcn;
down_write(&snd_ioctl_rwsem);
list_add_tail(&pn->list, lists);
up_write(&snd_ioctl_rwse... | 231,447,101,867,565,330,000,000,000,000,000,000,000 | control.c | 255,950,300,769,870,240,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
37,257 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | static int _snd_ctl_unregister_ioctl(snd_kctl_ioctl_func_t fcn,
struct list_head *lists)
{
struct snd_kctl_ioctl *p;
if (snd_BUG_ON(!fcn))
return -EINVAL;
down_write(&snd_ioctl_rwsem);
list_for_each_entry(p, lists, list) {
if (p->fioctl == fcn) {
list_del(&p->list);
up_write(&snd_ioctl_rwsem);
... | 286,073,903,658,219,550,000,000,000,000,000,000,000 | control.c | 255,950,300,769,870,240,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
37,258 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | int snd_ctl_activate_id(struct snd_card *card, struct snd_ctl_elem_id *id,
int active)
{
struct snd_kcontrol *kctl;
struct snd_kcontrol_volatile *vd;
unsigned int index_offset;
int ret;
down_write(&card->controls_rwsem);
kctl = snd_ctl_find_id(card, id);
if (kctl == NULL) {
ret = -ENOENT;
goto unlock;
}... | 246,146,308,065,289,360,000,000,000,000,000,000,000 | control.c | 179,532,723,377,993,540,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
37,259 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | int snd_ctl_boolean_mono_info(struct snd_kcontrol *kcontrol,
struct snd_ctl_elem_info *uinfo)
{
uinfo->type = SNDRV_CTL_ELEM_TYPE_BOOLEAN;
uinfo->count = 1;
uinfo->value.integer.min = 0;
uinfo->value.integer.max = 1;
return 0;
}
| 281,930,492,844,041,630,000,000,000,000,000,000,000 | control.c | 255,950,300,769,870,240,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
37,260 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | static int snd_ctl_card_info(struct snd_card *card, struct snd_ctl_file * ctl,
unsigned int cmd, void __user *arg)
{
struct snd_ctl_card_info *info;
info = kzalloc(sizeof(*info), GFP_KERNEL);
if (! info)
return -ENOMEM;
down_read(&snd_ioctl_rwsem);
info->card = card->number;
strlcpy(info->id, card->id,... | 97,197,608,204,677,320,000,000,000,000,000,000,000 | control.c | 179,532,723,377,993,540,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
37,261 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | int snd_ctl_create(struct snd_card *card)
{
static struct snd_device_ops ops = {
.dev_free = snd_ctl_dev_free,
.dev_register = snd_ctl_dev_register,
.dev_disconnect = snd_ctl_dev_disconnect,
};
if (snd_BUG_ON(!card))
return -ENXIO;
return snd_device_new(card, SNDRV_DEV_CONTROL, card, &ops);
}
| 89,855,396,919,898,090,000,000,000,000,000,000,000 | control.c | 179,532,723,377,993,540,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
37,262 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | static int snd_ctl_dev_disconnect(struct snd_device *device)
{
struct snd_card *card = device->device_data;
struct snd_ctl_file *ctl;
int err, cardnum;
if (snd_BUG_ON(!card))
return -ENXIO;
cardnum = card->number;
if (snd_BUG_ON(cardnum < 0 || cardnum >= SNDRV_CARDS))
return -ENXIO;
read_lock(&card->ctl_fi... | 334,179,000,248,754,340,000,000,000,000,000,000,000 | control.c | 179,532,723,377,993,540,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
37,263 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | static int snd_ctl_dev_free(struct snd_device *device)
{
struct snd_card *card = device->device_data;
struct snd_kcontrol *control;
down_write(&card->controls_rwsem);
while (!list_empty(&card->controls)) {
control = snd_kcontrol(card->controls.next);
snd_ctl_remove(card, control);
}
up_write(&card->controls_... | 309,064,993,738,509,370,000,000,000,000,000,000,000 | control.c | 179,532,723,377,993,540,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
37,264 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | static int snd_ctl_dev_register(struct snd_device *device)
{
struct snd_card *card = device->device_data;
int err, cardnum;
char name[16];
if (snd_BUG_ON(!card))
return -ENXIO;
cardnum = card->number;
if (snd_BUG_ON(cardnum < 0 || cardnum >= SNDRV_CARDS))
return -ENXIO;
sprintf(name, "controlC%i", cardnum);... | 18,006,447,539,959,834,000,000,000,000,000,000,000 | control.c | 179,532,723,377,993,540,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
37,265 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | static int snd_ctl_elem_add(struct snd_ctl_file *file,
struct snd_ctl_elem_info *info, int replace)
{
struct snd_card *card = file->card;
struct snd_kcontrol kctl, *_kctl;
unsigned int access;
long private_size;
struct user_element *ue;
int idx, err;
if (info->count < 1)
return -EINVAL;
access = info-... | 114,802,544,875,218,840,000,000,000,000,000,000,000 | control.c | 179,532,723,377,993,540,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
37,266 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | static int snd_ctl_elem_add_user(struct snd_ctl_file *file,
struct snd_ctl_elem_info __user *_info, int replace)
{
struct snd_ctl_elem_info info;
if (copy_from_user(&info, _info, sizeof(info)))
return -EFAULT;
return snd_ctl_elem_add(file, &info, replace);
}
| 305,057,399,166,362,300,000,000,000,000,000,000,000 | control.c | 179,532,723,377,993,540,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
37,267 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | static int snd_ctl_elem_info(struct snd_ctl_file *ctl,
struct snd_ctl_elem_info *info)
{
struct snd_card *card = ctl->card;
struct snd_kcontrol *kctl;
struct snd_kcontrol_volatile *vd;
unsigned int index_offset;
int result;
down_read(&card->controls_rwsem);
kctl = snd_ctl_find_id(card, &info->id);
if ... | 14,856,946,520,282,611,000,000,000,000,000,000,000 | control.c | 179,532,723,377,993,540,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
37,268 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | static int snd_ctl_elem_info_user(struct snd_ctl_file *ctl,
struct snd_ctl_elem_info __user *_info)
{
struct snd_ctl_elem_info info;
int result;
if (copy_from_user(&info, _info, sizeof(info)))
return -EFAULT;
snd_power_lock(ctl->card);
result = snd_power_wait(ctl->card, SNDRV_CTL_POWER_D0);
if (result >=... | 21,397,557,958,317,286,000,000,000,000,000,000,000 | control.c | 179,532,723,377,993,540,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
37,269 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | static int snd_ctl_elem_init_enum_names(struct user_element *ue)
{
char *names, *p;
size_t buf_len, name_len;
unsigned int i;
const uintptr_t user_ptrval = ue->info.value.enumerated.names_ptr;
if (ue->info.value.enumerated.names_length > 64 * 1024)
return -EINVAL;
names = memdup_user((const void __user *)user... | 217,563,908,729,059,270,000,000,000,000,000,000,000 | control.c | 179,532,723,377,993,540,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
37,270 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | static int snd_ctl_elem_list(struct snd_card *card,
struct snd_ctl_elem_list __user *_list)
{
struct list_head *plist;
struct snd_ctl_elem_list list;
struct snd_kcontrol *kctl;
struct snd_ctl_elem_id *dst, *id;
unsigned int offset, space, jidx;
if (copy_from_user(&list, _list, sizeof(list)))
return -E... | 105,127,993,000,977,080,000,000,000,000,000,000,000 | control.c | 179,532,723,377,993,540,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
37,271 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | static int snd_ctl_elem_lock(struct snd_ctl_file *file,
struct snd_ctl_elem_id __user *_id)
{
struct snd_card *card = file->card;
struct snd_ctl_elem_id id;
struct snd_kcontrol *kctl;
struct snd_kcontrol_volatile *vd;
int result;
if (copy_from_user(&id, _id, sizeof(id)))
return -EFAULT;
down_write(&c... | 179,668,486,831,935,900,000,000,000,000,000,000,000 | control.c | 255,950,300,769,870,240,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
37,272 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | static int snd_ctl_elem_read(struct snd_card *card,
struct snd_ctl_elem_value *control)
{
struct snd_kcontrol *kctl;
struct snd_kcontrol_volatile *vd;
unsigned int index_offset;
int result;
down_read(&card->controls_rwsem);
kctl = snd_ctl_find_id(card, &control->id);
if (kctl == NULL) {
result = -ENOE... | 130,757,256,041,335,430,000,000,000,000,000,000,000 | control.c | 179,532,723,377,993,540,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
37,273 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | static int snd_ctl_elem_remove(struct snd_ctl_file *file,
struct snd_ctl_elem_id __user *_id)
{
struct snd_ctl_elem_id id;
if (copy_from_user(&id, _id, sizeof(id)))
return -EFAULT;
return snd_ctl_remove_user_ctl(file, &id);
}
| 282,585,928,928,469,540,000,000,000,000,000,000,000 | control.c | 255,950,300,769,870,240,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
37,274 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | static int snd_ctl_elem_unlock(struct snd_ctl_file *file,
struct snd_ctl_elem_id __user *_id)
{
struct snd_card *card = file->card;
struct snd_ctl_elem_id id;
struct snd_kcontrol *kctl;
struct snd_kcontrol_volatile *vd;
int result;
if (copy_from_user(&id, _id, sizeof(id)))
return -EFAULT;
down_writ... | 287,454,362,389,453,900,000,000,000,000,000,000,000 | control.c | 255,950,300,769,870,240,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
37,275 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | static int snd_ctl_elem_user_enum_info(struct snd_kcontrol *kcontrol,
struct snd_ctl_elem_info *uinfo)
{
struct user_element *ue = kcontrol->private_data;
const char *names;
unsigned int item;
item = uinfo->value.enumerated.item;
*uinfo = ue->info;
item = min(item, uinfo->value.enumerated.items - 1)... | 301,200,818,336,071,800,000,000,000,000,000,000,000 | control.c | 179,532,723,377,993,540,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
37,276 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | static void snd_ctl_elem_user_free(struct snd_kcontrol *kcontrol)
{
struct user_element *ue = kcontrol->private_data;
kfree(ue->tlv_data);
kfree(ue->priv_data);
kfree(ue);
}
| 239,814,261,174,748,100,000,000,000,000,000,000,000 | control.c | 179,532,723,377,993,540,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
37,277 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | static int snd_ctl_elem_user_get(struct snd_kcontrol *kcontrol,
struct snd_ctl_elem_value *ucontrol)
{
struct user_element *ue = kcontrol->private_data;
mutex_lock(&ue->card->user_ctl_lock);
memcpy(&ucontrol->value, ue->elem_data, ue->elem_data_size);
mutex_unlock(&ue->card->user_ctl_lock);
return 0;
}
| 219,166,482,398,479,800,000,000,000,000,000,000,000 | control.c | 179,532,723,377,993,540,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
37,278 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | static int snd_ctl_elem_user_info(struct snd_kcontrol *kcontrol,
struct snd_ctl_elem_info *uinfo)
{
struct user_element *ue = kcontrol->private_data;
*uinfo = ue->info;
return 0;
}
| 159,404,618,488,044,970,000,000,000,000,000,000,000 | control.c | 179,532,723,377,993,540,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
37,279 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | static int snd_ctl_elem_user_put(struct snd_kcontrol *kcontrol,
struct snd_ctl_elem_value *ucontrol)
{
int change;
struct user_element *ue = kcontrol->private_data;
mutex_lock(&ue->card->user_ctl_lock);
change = memcmp(&ucontrol->value, ue->elem_data, ue->elem_data_size) != 0;
if (change)
memcpy(ue->elem_d... | 104,983,800,351,499,750,000,000,000,000,000,000,000 | control.c | 179,532,723,377,993,540,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
37,280 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | static int snd_ctl_elem_user_tlv(struct snd_kcontrol *kcontrol,
int op_flag,
unsigned int size,
unsigned int __user *tlv)
{
struct user_element *ue = kcontrol->private_data;
int change = 0;
void *new_data;
if (op_flag > 0) {
if (size > 1024 * 128) /* sane value */
return -EINVAL;
new_data = ... | 276,478,217,347,798,740,000,000,000,000,000,000,000 | control.c | 179,532,723,377,993,540,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
37,281 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 0 | static int snd_ctl_elem_write(struct snd_card *card, struct snd_ctl_file *file,
struct snd_ctl_elem_value *control)
{
struct snd_kcontrol *kctl;
struct snd_kcontrol_volatile *vd;
unsigned int index_offset;
int result;
down_read(&card->controls_rwsem);
kctl = snd_ctl_find_id(card, &control->id);
if (kct... | 177,716,092,449,550,470,000,000,000,000,000,000,000 | control.c | 179,532,723,377,993,540,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.