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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
36,925 | ettercap | e3abe7d7585ecc420a7cab73313216613aadad5a | https://github.com/Ettercap/ettercap | https://github.com/Ettercap/ettercap/commit/e3abe7d7585ecc420a7cab73313216613aadad5a | Fixed heap overflow caused by length | 0 | static inline void hex_encode(unsigned char *str, int len, unsigned char *out)
{
int i;
for (i = 0; i < len; ++i) {
out[0] = itoa16[str[i]>>4];
out[1] = itoa16[str[i]&0xF];
out += 2;
}
}
| 215,881,275,030,106,570,000,000,000,000,000,000,000 | ec_postgresql.c | 284,688,323,983,812,370,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-6395 | Heap-based buffer overflow in the dissector_postgresql function in dissectors/ec_postgresql.c in Ettercap before 0.8.1 allows remote attackers to cause a denial of service or possibly execute arbitrary code via a crafted password length value that is inconsistent with the actual length of the password. | https://nvd.nist.gov/vuln/detail/CVE-2014-6395 |
36,926 | ettercap | e3abe7d7585ecc420a7cab73313216613aadad5a | https://github.com/Ettercap/ettercap | https://github.com/Ettercap/ettercap/commit/e3abe7d7585ecc420a7cab73313216613aadad5a | Fixed heap overflow caused by length | 0 | void __init postgresql_init(void)
{
dissect_add("postgresql", APP_LAYER_TCP, 5432, dissector_postgresql);
}
| 233,970,341,704,250,700,000,000,000,000,000,000,000 | ec_postgresql.c | 284,688,323,983,812,370,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-6395 | Heap-based buffer overflow in the dissector_postgresql function in dissectors/ec_postgresql.c in Ettercap before 0.8.1 allows remote attackers to cause a denial of service or possibly execute arbitrary code via a crafted password length value that is inconsistent with the actual length of the password. | https://nvd.nist.gov/vuln/detail/CVE-2014-6395 |
36,927 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | static sector_t _isofs_bmap(struct address_space *mapping, sector_t block)
{
return generic_block_bmap(mapping,block,isofs_get_block);
}
| 60,873,304,599,297,100,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,928 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | static void destroy_inodecache(void)
{
/*
* Make sure all delayed rcu free inodes are flushed before we
* destroy cache.
*/
rcu_barrier();
kmem_cache_destroy(isofs_inode_cachep);
}
| 255,981,358,953,676,140,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,929 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | static void __exit exit_iso9660_fs(void)
{
unregister_filesystem(&iso9660_fs_type);
#ifdef CONFIG_ZISOFS
zisofs_cleanup();
#endif
destroy_inodecache();
}
| 262,757,957,037,628,400,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,930 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | static int __init init_inodecache(void)
{
isofs_inode_cachep = kmem_cache_create("isofs_inode_cache",
sizeof(struct iso_inode_info),
0, (SLAB_RECLAIM_ACCOUNT|
SLAB_MEM_SPREAD),
init_once);
if (isofs_inode_cachep == NULL)
return -ENOMEM;
return 0;
}
| 34,914,129,612,938,860,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,931 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | static int __init init_iso9660_fs(void)
{
int err = init_inodecache();
if (err)
goto out;
#ifdef CONFIG_ZISOFS
err = zisofs_init();
if (err)
goto out1;
#endif
err = register_filesystem(&iso9660_fs_type);
if (err)
goto out2;
return 0;
out2:
#ifdef CONFIG_ZISOFS
zisofs_cleanup();
out1:
#endif
destroy_inode... | 32,872,788,764,704,720,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,932 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | static void init_once(void *foo)
{
struct iso_inode_info *ei = foo;
inode_init_once(&ei->vfs_inode);
}
| 305,462,433,474,810,280,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,933 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | static struct inode *isofs_alloc_inode(struct super_block *sb)
{
struct iso_inode_info *ei;
ei = kmem_cache_alloc(isofs_inode_cachep, GFP_KERNEL);
if (!ei)
return NULL;
return &ei->vfs_inode;
}
| 152,135,031,204,845,910,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,934 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | static int isofs_bmap(struct inode *inode, sector_t block)
{
struct buffer_head dummy;
int error;
dummy.b_state = 0;
dummy.b_blocknr = -1000;
error = isofs_get_block(inode, block, &dummy, 0);
if (!error)
return dummy.b_blocknr;
return 0;
}
| 178,044,895,625,445,940,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,935 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | struct buffer_head *isofs_bread(struct inode *inode, sector_t block)
{
sector_t blknr = isofs_bmap(inode, block);
if (!blknr)
return NULL;
return sb_bread(inode->i_sb, blknr);
}
| 221,394,265,966,976,060,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,936 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | isofs_dentry_cmp(const struct dentry *parent, const struct dentry *dentry,
unsigned int len, const char *str, const struct qstr *name)
{
return isofs_dentry_cmp_common(len, str, name, 0, 0);
}
| 256,602,821,466,663,600,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,937 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | static int isofs_dentry_cmp_common(
unsigned int len, const char *str,
const struct qstr *name, int ms, int ci)
{
int alen, blen;
/* A filename cannot end in '.' or we treat it like it has none */
alen = name->len;
blen = len;
if (ms) {
while (alen && name->name[alen-1] == '.')
alen--;
while (blen && s... | 315,168,301,123,516,780,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,938 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | isofs_dentry_cmp_ms(const struct dentry *parent, const struct dentry *dentry,
unsigned int len, const char *str, const struct qstr *name)
{
return isofs_dentry_cmp_common(len, str, name, 1, 0);
}
| 75,874,608,862,622,840,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,939 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | isofs_dentry_cmpi(const struct dentry *parent, const struct dentry *dentry,
unsigned int len, const char *str, const struct qstr *name)
{
return isofs_dentry_cmp_common(len, str, name, 0, 1);
}
| 87,500,534,559,592,540,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,940 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | isofs_dentry_cmpi_ms(const struct dentry *parent, const struct dentry *dentry,
unsigned int len, const char *str, const struct qstr *name)
{
return isofs_dentry_cmp_common(len, str, name, 1, 1);
}
| 298,940,326,107,101,800,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,941 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | static void isofs_destroy_inode(struct inode *inode)
{
call_rcu(&inode->i_rcu, isofs_i_callback);
}
| 152,464,149,379,370,700,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,942 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | static int isofs_fill_super(struct super_block *s, void *data, int silent)
{
struct buffer_head *bh = NULL, *pri_bh = NULL;
struct hs_primary_descriptor *h_pri = NULL;
struct iso_primary_descriptor *pri = NULL;
struct iso_supplementary_descriptor *sec = NULL;
struct iso_directory_record *rootp;
struct inode *inod... | 41,576,013,362,083,085,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,943 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | static int isofs_get_block(struct inode *inode, sector_t iblock,
struct buffer_head *bh_result, int create)
{
int ret;
if (create) {
printk(KERN_DEBUG "%s: Kernel tries to allocate a block\n", __func__);
return -EROFS;
}
ret = isofs_get_blocks(inode, iblock, &bh_result, 1);
return ret < 0 ? ret : 0;
}
| 210,495,836,388,169,880,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,944 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | int isofs_get_blocks(struct inode *inode, sector_t iblock,
struct buffer_head **bh, unsigned long nblocks)
{
unsigned long b_off = iblock;
unsigned offset, sect_size;
unsigned int firstext;
unsigned long nextblk, nextoff;
int section, rv, error;
struct iso_inode_info *ei = ISOFS_I(inode);
error = -EIO;
... | 131,920,994,739,409,980,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,945 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | static unsigned int isofs_get_last_session(struct super_block *sb, s32 session)
{
struct cdrom_multisession ms_info;
unsigned int vol_desc_start;
struct block_device *bdev = sb->s_bdev;
int i;
vol_desc_start=0;
ms_info.addr_format=CDROM_LBA;
if(session >= 0 && session <= 99) {
struct cdrom_tocentry Te;
Te.c... | 12,743,097,085,392,233,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,946 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | isofs_hash(const struct dentry *dentry, struct qstr *qstr)
{
return isofs_hash_common(qstr, 0);
}
| 162,645,229,915,826,600,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,947 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | isofs_hash_common(struct qstr *qstr, int ms)
{
const char *name;
int len;
len = qstr->len;
name = qstr->name;
if (ms) {
while (len && name[len-1] == '.')
len--;
}
qstr->hash = full_name_hash(name, len);
return 0;
}
| 45,752,324,501,227,120,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,948 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | isofs_hash_ms(const struct dentry *dentry, struct qstr *qstr)
{
return isofs_hash_common(qstr, 1);
}
| 66,165,114,795,412,870,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,949 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | isofs_hashi(const struct dentry *dentry, struct qstr *qstr)
{
return isofs_hashi_common(qstr, 0);
}
| 278,772,612,526,616,080,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,950 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | isofs_hashi_common(struct qstr *qstr, int ms)
{
const char *name;
int len;
char c;
unsigned long hash;
len = qstr->len;
name = qstr->name;
if (ms) {
while (len && name[len-1] == '.')
len--;
}
hash = init_name_hash();
while (len--) {
c = tolower(*name++);
hash = partial_name_hash(c, hash);
}
qstr-... | 68,653,803,034,003,210,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,951 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | isofs_hashi_ms(const struct dentry *dentry, struct qstr *qstr)
{
return isofs_hashi_common(qstr, 1);
}
| 225,697,634,862,410,400,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,952 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | static void isofs_i_callback(struct rcu_head *head)
{
struct inode *inode = container_of(head, struct inode, i_rcu);
kmem_cache_free(isofs_inode_cachep, ISOFS_I(inode));
}
| 159,184,890,504,824,320,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,953 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | static int isofs_iget5_test(struct inode *ino, void *data)
{
struct iso_inode_info *i = ISOFS_I(ino);
struct isofs_iget5_callback_data *d =
(struct isofs_iget5_callback_data*)data;
return (i->i_iget5_block == d->block)
&& (i->i_iget5_offset == d->offset);
}
| 129,664,581,136,998,460,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,954 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | static struct dentry *isofs_mount(struct file_system_type *fs_type,
int flags, const char *dev_name, void *data)
{
/* We don't support read-write mounts */
if (!(flags & MS_RDONLY))
return ERR_PTR(-EACCES);
return mount_bdev(fs_type, flags, dev_name, data, isofs_fill_super);
}
| 204,629,491,182,910,120,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,955 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | static void isofs_put_super(struct super_block *sb)
{
struct isofs_sb_info *sbi = ISOFS_SB(sb);
#ifdef CONFIG_JOLIET
unload_nls(sbi->s_nls_iocharset);
#endif
kfree(sbi);
sb->s_fs_info = NULL;
return;
}
| 234,308,097,745,898,800,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,956 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | static int isofs_read_level3_size(struct inode *inode)
{
unsigned long bufsize = ISOFS_BUFFER_SIZE(inode);
int high_sierra = ISOFS_SB(inode->i_sb)->s_high_sierra;
struct buffer_head *bh = NULL;
unsigned long block, offset, block_saved, offset_saved;
int i = 0;
int more_entries = 0;
struct iso_directory_record *t... | 168,812,469,291,999,070,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,957 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | static int isofs_readpage(struct file *file, struct page *page)
{
return mpage_readpage(page, isofs_get_block);
}
| 152,708,094,927,575,200,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,958 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | static int isofs_readpages(struct file *file, struct address_space *mapping,
struct list_head *pages, unsigned nr_pages)
{
return mpage_readpages(mapping, pages, nr_pages, isofs_get_block);
}
| 50,803,750,007,892,510,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,959 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | static int isofs_remount(struct super_block *sb, int *flags, char *data)
{
sync_filesystem(sb);
if (!(*flags & MS_RDONLY))
return -EROFS;
return 0;
}
| 219,857,180,328,455,380,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,960 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | static int isofs_statfs (struct dentry *dentry, struct kstatfs *buf)
{
struct super_block *sb = dentry->d_sb;
u64 id = huge_encode_dev(sb->s_bdev->bd_dev);
buf->f_type = ISOFS_SUPER_MAGIC;
buf->f_bsize = sb->s_blocksize;
buf->f_blocks = (ISOFS_SB(sb)->s_nzones
<< (ISOFS_SB(sb)->s_log_zone_size - sb->s_blocksize... | 88,019,680,981,889,270,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,961 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | static int parse_options(char *options, struct iso9660_options *popt)
{
char *p;
int option;
popt->map = 'n';
popt->rock = 1;
popt->joliet = 1;
popt->cruft = 0;
popt->hide = 0;
popt->showassoc = 0;
popt->check = 'u'; /* unset */
popt->nocompress = 0;
popt->blocksize = 1024;
popt->fmode = popt->dmode = ISO... | 97,149,486,917,088,140,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,962 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 0 | static bool rootdir_empty(struct super_block *sb, unsigned long block)
{
int offset = 0, files = 0, de_len;
struct iso_directory_record *de;
struct buffer_head *bh;
bh = sb_bread(sb, block);
if (!bh)
return true;
while (files < 3) {
de = (struct iso_directory_record *) (bh->b_data + offset);
de_len = *(uns... | 309,616,488,140,014,370,000,000,000,000,000,000,000 | inode.c | 129,288,806,133,508,120,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
36,971 | krb5 | d1f707024f1d0af6e54a18885322d70fa15ec4d3 | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/d1f707024f1d0af6e54a18885322d70fa15ec4d3 | Fix LDAP misused policy name crash [CVE-2014-5353]
In krb5_ldap_get_password_policy_from_dn, if LDAP_SEARCH returns
successfully with no results, return KRB5_KDB_NOENTRY instead of
returning success with a zeroed-out policy object. This fixes a null
dereference when an admin attempts to use an LDAP ticket policy name... | 0 | add_policy_mods(krb5_context context, LDAPMod ***mods, osa_policy_ent_t policy,
int op)
{
krb5_error_code st;
char *strval[2] = { NULL };
st = krb5_add_int_mem_ldap_mod(mods, "krbmaxpwdlife", op,
(int)policy->pw_max_life);
if (st)
return st;
... | 275,779,762,928,974,800,000,000,000,000,000,000,000 | ldap_pwd_policy.c | 296,616,813,955,699,930,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2014-5353 | The krb5_ldap_get_password_policy_from_dn function in plugins/kdb/ldap/libkdb_ldap/ldap_pwd_policy.c in MIT Kerberos 5 (aka krb5) before 1.13.1, when the KDC uses LDAP, allows remote authenticated users to cause a denial of service (daemon crash) via a successful LDAP query with no results, as demonstrated by using an ... | https://nvd.nist.gov/vuln/detail/CVE-2014-5353 |
36,972 | krb5 | d1f707024f1d0af6e54a18885322d70fa15ec4d3 | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/d1f707024f1d0af6e54a18885322d70fa15ec4d3 | Fix LDAP misused policy name crash [CVE-2014-5353]
In krb5_ldap_get_password_policy_from_dn, if LDAP_SEARCH returns
successfully with no results, return KRB5_KDB_NOENTRY instead of
returning success with a zeroed-out policy object. This fixes a null
dereference when an admin attempts to use an LDAP ticket policy name... | 0 | krb5_ldap_get_password_policy(krb5_context context, char *name,
osa_policy_ent_t *policy)
{
krb5_error_code st = 0;
char *policy_dn = NULL;
/* Clear the global error string */
krb5_clear_error_message(context);
/* validate the input ... | 28,133,375,696,201,260,000,000,000,000,000,000,000 | ldap_pwd_policy.c | 296,616,813,955,699,930,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2014-5353 | The krb5_ldap_get_password_policy_from_dn function in plugins/kdb/ldap/libkdb_ldap/ldap_pwd_policy.c in MIT Kerberos 5 (aka krb5) before 1.13.1, when the KDC uses LDAP, allows remote authenticated users to cause a denial of service (daemon crash) via a successful LDAP query with no results, as demonstrated by using an ... | https://nvd.nist.gov/vuln/detail/CVE-2014-5353 |
36,973 | krb5 | d1f707024f1d0af6e54a18885322d70fa15ec4d3 | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/d1f707024f1d0af6e54a18885322d70fa15ec4d3 | Fix LDAP misused policy name crash [CVE-2014-5353]
In krb5_ldap_get_password_policy_from_dn, if LDAP_SEARCH returns
successfully with no results, return KRB5_KDB_NOENTRY instead of
returning success with a zeroed-out policy object. This fixes a null
dereference when an admin attempts to use an LDAP ticket policy name... | 0 | krb5_ldap_put_password_policy(krb5_context context, osa_policy_ent_t policy)
{
char *policy_dn=NULL;
krb5_error_code st=0;
LDAP *ld=NULL;
LDAPMod **mods=NULL;
kdb5_dal_handle *dal_handle=NULL;
krb5_ldap_con... | 196,816,148,911,449,970,000,000,000,000,000,000,000 | ldap_pwd_policy.c | 296,616,813,955,699,930,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2014-5353 | The krb5_ldap_get_password_policy_from_dn function in plugins/kdb/ldap/libkdb_ldap/ldap_pwd_policy.c in MIT Kerberos 5 (aka krb5) before 1.13.1, when the KDC uses LDAP, allows remote authenticated users to cause a denial of service (daemon crash) via a successful LDAP query with no results, as demonstrated by using an ... | https://nvd.nist.gov/vuln/detail/CVE-2014-5353 |
36,974 | krb5 | d1f707024f1d0af6e54a18885322d70fa15ec4d3 | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/d1f707024f1d0af6e54a18885322d70fa15ec4d3 | Fix LDAP misused policy name crash [CVE-2014-5353]
In krb5_ldap_get_password_policy_from_dn, if LDAP_SEARCH returns
successfully with no results, return KRB5_KDB_NOENTRY instead of
returning success with a zeroed-out policy object. This fixes a null
dereference when an admin attempts to use an LDAP ticket policy name... | 0 | populate_policy(krb5_context context,
LDAP *ld,
LDAPMessage *ent,
char *pol_name,
osa_policy_ent_t pol_entry)
{
int st = 0;
pol_entry->name = strdup(pol_name);
CHECK_NULL(pol_entry->name);
pol_entry->version = 1;
get_ui4(ld, ent, "krb... | 258,206,858,774,242,600,000,000,000,000,000,000,000 | ldap_pwd_policy.c | 296,616,813,955,699,930,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2014-5353 | The krb5_ldap_get_password_policy_from_dn function in plugins/kdb/ldap/libkdb_ldap/ldap_pwd_policy.c in MIT Kerberos 5 (aka krb5) before 1.13.1, when the KDC uses LDAP, allows remote authenticated users to cause a denial of service (daemon crash) via a successful LDAP query with no results, as demonstrated by using an ... | https://nvd.nist.gov/vuln/detail/CVE-2014-5353 |
36,975 | krb5 | af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | Return only new keys in randkey [CVE-2014-5351]
In kadmind's randkey operation, if a client specifies the keepold
flag, do not include the preserved old keys in the response.
CVE-2014-5351:
An authenticated remote attacker can retrieve the current keys for a
service principal when generating a new set of keys for th... | 0 | apply_keysalt_policy(kadm5_server_handle_t handle, const char *policy,
int n_ks_tuple, krb5_key_salt_tuple *ks_tuple,
int *new_n_kstp, krb5_key_salt_tuple **new_kstp)
{
kadm5_ret_t ret;
kadm5_policy_ent_rec polent;
krb5_boolean have_polent;
int ak_n_ks_tuple = 0... | 203,973,829,286,895,500,000,000,000,000,000,000,000 | svr_principal.c | 254,658,728,888,016,480,000,000,000,000,000,000,000 | [
"CWE-255"
] | CVE-2014-5351 | The kadm5_randkey_principal_3 function in lib/kadm5/srv/svr_principal.c in kadmind in MIT Kerberos 5 (aka krb5) before 1.13 sends old keys in a response to a -randkey -keepold request, which allows remote authenticated users to forge tickets by leveraging administrative access. | https://nvd.nist.gov/vuln/detail/CVE-2014-5351 |
36,976 | krb5 | af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | Return only new keys in randkey [CVE-2014-5351]
In kadmind's randkey operation, if a client specifies the keepold
flag, do not include the preserved old keys in the response.
CVE-2014-5351:
An authenticated remote attacker can retrieve the current keys for a
service principal when generating a new set of keys for th... | 0 | check_1_6_dummy(kadm5_principal_ent_t entry, long mask,
int n_ks_tuple, krb5_key_salt_tuple *ks_tuple, char **passptr)
{
int i;
char *password = *passptr;
/* Old-style randkey operations disallowed tickets to start. */
if (password == NULL || !(mask & KADM5_ATTRIBUTES) ||
!(entr... | 192,189,665,348,241,600,000,000,000,000,000,000,000 | svr_principal.c | 254,658,728,888,016,480,000,000,000,000,000,000,000 | [
"CWE-255"
] | CVE-2014-5351 | The kadm5_randkey_principal_3 function in lib/kadm5/srv/svr_principal.c in kadmind in MIT Kerberos 5 (aka krb5) before 1.13 sends old keys in a response to a -randkey -keepold request, which allows remote authenticated users to forge tickets by leveraging administrative access. | https://nvd.nist.gov/vuln/detail/CVE-2014-5351 |
36,977 | krb5 | af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | Return only new keys in randkey [CVE-2014-5351]
In kadmind's randkey operation, if a client specifies the keepold
flag, do not include the preserved old keys in the response.
CVE-2014-5351:
An authenticated remote attacker can retrieve the current keys for a
service principal when generating a new set of keys for th... | 0 | int create_history_entry(krb5_context context,
krb5_keyblock *hist_key, int n_key_data,
krb5_key_data *key_data, osa_pw_hist_ent *hist)
{
krb5_error_code ret;
krb5_keyblock key;
krb5_keysalt salt;
int i;
hist->key_data = k5calloc(n_key_data, sizeof(... | 301,124,656,239,948,500,000,000,000,000,000,000,000 | svr_principal.c | 254,658,728,888,016,480,000,000,000,000,000,000,000 | [
"CWE-255"
] | CVE-2014-5351 | The kadm5_randkey_principal_3 function in lib/kadm5/srv/svr_principal.c in kadmind in MIT Kerberos 5 (aka krb5) before 1.13 sends old keys in a response to a -randkey -keepold request, which allows remote authenticated users to forge tickets by leveraging administrative access. | https://nvd.nist.gov/vuln/detail/CVE-2014-5351 |
36,978 | krb5 | af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | Return only new keys in randkey [CVE-2014-5351]
In kadmind's randkey operation, if a client specifies the keepold
flag, do not include the preserved old keys in the response.
CVE-2014-5351:
An authenticated remote attacker can retrieve the current keys for a
service principal when generating a new set of keys for th... | 0 | get_policy(kadm5_server_handle_t handle, const char *name,
kadm5_policy_ent_t policy_out, krb5_boolean *have_pol_out)
{
kadm5_ret_t ret;
*have_pol_out = FALSE;
if (name == NULL)
return 0;
ret = kadm5_get_policy(handle->lhandle, (char *)name, policy_out);
if (ret == 0)
*ha... | 295,594,627,351,378,470,000,000,000,000,000,000,000 | svr_principal.c | 254,658,728,888,016,480,000,000,000,000,000,000,000 | [
"CWE-255"
] | CVE-2014-5351 | The kadm5_randkey_principal_3 function in lib/kadm5/srv/svr_principal.c in kadmind in MIT Kerberos 5 (aka krb5) before 1.13 sends old keys in a response to a -randkey -keepold request, which allows remote authenticated users to forge tickets by leveraging administrative access. | https://nvd.nist.gov/vuln/detail/CVE-2014-5351 |
36,979 | krb5 | af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | Return only new keys in randkey [CVE-2014-5351]
In kadmind's randkey operation, if a client specifies the keepold
flag, do not include the preserved old keys in the response.
CVE-2014-5351:
An authenticated remote attacker can retrieve the current keys for a
service principal when generating a new set of keys for th... | 0 | kadm5_chpass_principal_3(void *server_handle,
krb5_principal principal, krb5_boolean keepold,
int n_ks_tuple, krb5_key_salt_tuple *ks_tuple,
char *password)
{
krb5_int32 now;
kadm5_policy_ent_rec pol;
osa_prin... | 2,528,322,530,495,493,200,000,000,000,000,000,000 | svr_principal.c | 254,658,728,888,016,480,000,000,000,000,000,000,000 | [
"CWE-255"
] | CVE-2014-5351 | The kadm5_randkey_principal_3 function in lib/kadm5/srv/svr_principal.c in kadmind in MIT Kerberos 5 (aka krb5) before 1.13 sends old keys in a response to a -randkey -keepold request, which allows remote authenticated users to forge tickets by leveraging administrative access. | https://nvd.nist.gov/vuln/detail/CVE-2014-5351 |
36,980 | krb5 | af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | Return only new keys in randkey [CVE-2014-5351]
In kadmind's randkey operation, if a client specifies the keepold
flag, do not include the preserved old keys in the response.
CVE-2014-5351:
An authenticated remote attacker can retrieve the current keys for a
service principal when generating a new set of keys for th... | 0 | kadm5_delete_principal(void *server_handle, krb5_principal principal)
{
unsigned int ret;
krb5_db_entry *kdb;
osa_princ_ent_rec adb;
kadm5_server_handle_t handle = server_handle;
CHECK_HANDLE(server_handle);
krb5_clear_error_message(handle->context);
... | 228,586,002,840,872,830,000,000,000,000,000,000,000 | svr_principal.c | 254,658,728,888,016,480,000,000,000,000,000,000,000 | [
"CWE-255"
] | CVE-2014-5351 | The kadm5_randkey_principal_3 function in lib/kadm5/srv/svr_principal.c in kadmind in MIT Kerberos 5 (aka krb5) before 1.13 sends old keys in a response to a -randkey -keepold request, which allows remote authenticated users to forge tickets by leveraging administrative access. | https://nvd.nist.gov/vuln/detail/CVE-2014-5351 |
36,981 | krb5 | af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | Return only new keys in randkey [CVE-2014-5351]
In kadmind's randkey operation, if a client specifies the keepold
flag, do not include the preserved old keys in the response.
CVE-2014-5351:
An authenticated remote attacker can retrieve the current keys for a
service principal when generating a new set of keys for th... | 0 | kadm5_get_principal(void *server_handle, krb5_principal principal,
kadm5_principal_ent_t entry,
long in_mask)
{
krb5_db_entry *kdb;
osa_princ_ent_rec adb;
krb5_error_code ret = 0;
long mask;
int i;
... | 269,658,960,817,773,000,000,000,000,000,000,000,000 | svr_principal.c | 254,658,728,888,016,480,000,000,000,000,000,000,000 | [
"CWE-255"
] | CVE-2014-5351 | The kadm5_randkey_principal_3 function in lib/kadm5/srv/svr_principal.c in kadmind in MIT Kerberos 5 (aka krb5) before 1.13 sends old keys in a response to a -randkey -keepold request, which allows remote authenticated users to forge tickets by leveraging administrative access. | https://nvd.nist.gov/vuln/detail/CVE-2014-5351 |
36,982 | krb5 | af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | Return only new keys in randkey [CVE-2014-5351]
In kadmind's randkey operation, if a client specifies the keepold
flag, do not include the preserved old keys in the response.
CVE-2014-5351:
An authenticated remote attacker can retrieve the current keys for a
service principal when generating a new set of keys for th... | 0 | kadm5_purgekeys(void *server_handle,
krb5_principal principal,
int keepkvno)
{
kadm5_server_handle_t handle = server_handle;
kadm5_ret_t ret;
krb5_db_entry *kdb;
osa_princ_ent_rec adb;
krb5_key_data *old_keydata;
int n_old_keydata;
int i, j, k;
CHECK_HAND... | 82,699,563,061,099,680,000,000,000,000,000,000,000 | svr_principal.c | 254,658,728,888,016,480,000,000,000,000,000,000,000 | [
"CWE-255"
] | CVE-2014-5351 | The kadm5_randkey_principal_3 function in lib/kadm5/srv/svr_principal.c in kadmind in MIT Kerberos 5 (aka krb5) before 1.13 sends old keys in a response to a -randkey -keepold request, which allows remote authenticated users to forge tickets by leveraging administrative access. | https://nvd.nist.gov/vuln/detail/CVE-2014-5351 |
36,983 | krb5 | af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | Return only new keys in randkey [CVE-2014-5351]
In kadmind's randkey operation, if a client specifies the keepold
flag, do not include the preserved old keys in the response.
CVE-2014-5351:
An authenticated remote attacker can retrieve the current keys for a
service principal when generating a new set of keys for th... | 0 | kadm5_setkey_principal_3(void *server_handle,
krb5_principal principal,
krb5_boolean keepold,
int n_ks_tuple, krb5_key_salt_tuple *ks_tuple,
krb5_keyblock *keyblocks,
int n_keys)
{
krb5_db_en... | 69,998,072,157,673,010,000,000,000,000,000,000,000 | svr_principal.c | 254,658,728,888,016,480,000,000,000,000,000,000,000 | [
"CWE-255"
] | CVE-2014-5351 | The kadm5_randkey_principal_3 function in lib/kadm5/srv/svr_principal.c in kadmind in MIT Kerberos 5 (aka krb5) before 1.13 sends old keys in a response to a -randkey -keepold request, which allows remote authenticated users to forge tickets by leveraging administrative access. | https://nvd.nist.gov/vuln/detail/CVE-2014-5351 |
36,984 | krb5 | af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | Return only new keys in randkey [CVE-2014-5351]
In kadmind's randkey operation, if a client specifies the keepold
flag, do not include the preserved old keys in the response.
CVE-2014-5351:
An authenticated remote attacker can retrieve the current keys for a
service principal when generating a new set of keys for th... | 0 | kadm5_setv4key_principal(void *server_handle,
krb5_principal principal,
krb5_keyblock *keyblock)
{
krb5_db_entry *kdb;
osa_princ_ent_rec adb;
krb5_int32 now;
kadm5_policy_ent_rec pol;
krb5_keysalt ... | 301,438,626,738,594,840,000,000,000,000,000,000,000 | svr_principal.c | 254,658,728,888,016,480,000,000,000,000,000,000,000 | [
"CWE-255"
] | CVE-2014-5351 | The kadm5_randkey_principal_3 function in lib/kadm5/srv/svr_principal.c in kadmind in MIT Kerberos 5 (aka krb5) before 1.13 sends old keys in a response to a -randkey -keepold request, which allows remote authenticated users to forge tickets by leveraging administrative access. | https://nvd.nist.gov/vuln/detail/CVE-2014-5351 |
36,985 | krb5 | af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | Return only new keys in randkey [CVE-2014-5351]
In kadmind's randkey operation, if a client specifies the keepold
flag, do not include the preserved old keys in the response.
CVE-2014-5351:
An authenticated remote attacker can retrieve the current keys for a
service principal when generating a new set of keys for th... | 0 | ks_tuple_present(int n_ks_tuple, krb5_key_salt_tuple *ks_tuple,
krb5_key_salt_tuple *looking_for)
{
int i;
for (i = 0; i < n_ks_tuple; i++) {
if (ks_tuple[i].ks_enctype == looking_for->ks_enctype &&
ks_tuple[i].ks_salttype == looking_for->ks_salttype)
return TRU... | 32,230,767,086,888,200,000,000,000,000,000,000,000 | svr_principal.c | 254,658,728,888,016,480,000,000,000,000,000,000,000 | [
"CWE-255"
] | CVE-2014-5351 | The kadm5_randkey_principal_3 function in lib/kadm5/srv/svr_principal.c in kadmind in MIT Kerberos 5 (aka krb5) before 1.13 sends old keys in a response to a -randkey -keepold request, which allows remote authenticated users to forge tickets by leveraging administrative access. | https://nvd.nist.gov/vuln/detail/CVE-2014-5351 |
36,986 | krb5 | af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | Return only new keys in randkey [CVE-2014-5351]
In kadmind's randkey operation, if a client specifies the keepold
flag, do not include the preserved old keys in the response.
CVE-2014-5351:
An authenticated remote attacker can retrieve the current keys for a
service principal when generating a new set of keys for th... | 0 | make_ks_from_keys(krb5_context context, int n_keys, krb5_keyblock *keyblocks,
krb5_key_salt_tuple **ks_tuple)
{
int i;
*ks_tuple = calloc(n_keys, sizeof(**ks_tuple));
if (*ks_tuple == NULL)
return ENOMEM;
for (i = 0; i < n_keys; i++) {
(*ks_tuple)[i].ks_enctype = keyb... | 287,289,296,208,852,600,000,000,000,000,000,000,000 | svr_principal.c | 254,658,728,888,016,480,000,000,000,000,000,000,000 | [
"CWE-255"
] | CVE-2014-5351 | The kadm5_randkey_principal_3 function in lib/kadm5/srv/svr_principal.c in kadmind in MIT Kerberos 5 (aka krb5) before 1.13 sends old keys in a response to a -randkey -keepold request, which allows remote authenticated users to forge tickets by leveraging administrative access. | https://nvd.nist.gov/vuln/detail/CVE-2014-5351 |
37,013 | linux | 9566d6742852c527bf5af38af5cbb878dad75705 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9566d6742852c527bf5af38af5cbb878dad75705 | mnt: Correct permission checks in do_remount
While invesgiating the issue where in "mount --bind -oremount,ro ..."
would result in later "mount --bind -oremount,rw" succeeding even if
the mount started off locked I realized that there are several
additional mount flags that should be locked and are not.
In particular... | 0 | SYSCALL_DEFINE2(pivot_root, const char __user *, new_root,
const char __user *, put_old)
{
struct path new, old, parent_path, root_parent, root;
struct mount *new_mnt, *root_mnt, *old_mnt;
struct mountpoint *old_mp, *root_mp;
int error;
if (!may_mount())
return -EPERM;
error = user_path_dir(new_root, &new);... | 262,010,153,246,038,900,000,000,000,000,000,000,000 | namespace.c | 291,925,216,484,681,430,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-5207 | fs/namespace.c in the Linux kernel through 3.16.1 does not properly restrict clearing MNT_NODEV, MNT_NOSUID, and MNT_NOEXEC and changing MNT_ATIME_MASK during a remount of a bind mount, which allows local users to gain privileges, interfere with backups and auditing on systems that had atime enabled, or cause a denial ... | https://nvd.nist.gov/vuln/detail/CVE-2014-5207 |
37,028 | linux | 9566d6742852c527bf5af38af5cbb878dad75705 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9566d6742852c527bf5af38af5cbb878dad75705 | mnt: Correct permission checks in do_remount
While invesgiating the issue where in "mount --bind -oremount,ro ..."
would result in later "mount --bind -oremount,rw" succeeding even if
the mount started off locked I realized that there are several
additional mount flags that should be locked and are not.
In particular... | 0 | long do_mount(const char *dev_name, const char *dir_name,
const char *type_page, unsigned long flags, void *data_page)
{
struct path path;
int retval = 0;
int mnt_flags = 0;
/* Discard magic */
if ((flags & MS_MGC_MSK) == MS_MGC_VAL)
flags &= ~MS_MGC_MSK;
/* Basic sanity checks */
if (!dir_name || !*dir_n... | 45,474,974,246,593,900,000,000,000,000,000,000,000 | namespace.c | 291,925,216,484,681,430,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-5207 | fs/namespace.c in the Linux kernel through 3.16.1 does not properly restrict clearing MNT_NODEV, MNT_NOSUID, and MNT_NOEXEC and changing MNT_ATIME_MASK during a remount of a bind mount, which allows local users to gain privileges, interfere with backups and auditing on systems that had atime enabled, or cause a denial ... | https://nvd.nist.gov/vuln/detail/CVE-2014-5207 |
37,102 | 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 | SYSCALL_DEFINE1(rmdir, const char __user *, pathname)
{
return do_rmdir(AT_FDCWD, pathname);
}
| 261,709,051,802,130,260,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,103 | 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 | SYSCALL_DEFINE1(unlink, const char __user *, pathname)
{
return do_unlinkat(AT_FDCWD, pathname);
}
| 38,416,106,898,414,107,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,104 | 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 | SYSCALL_DEFINE2(mkdir, const char __user *, pathname, umode_t, mode)
{
return sys_mkdirat(AT_FDCWD, pathname, mode);
}
| 72,477,223,576,245,910,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,105 | 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 | SYSCALL_DEFINE2(symlink, const char __user *, oldname, const char __user *, newname)
{
return sys_symlinkat(oldname, AT_FDCWD, newname);
}
| 143,759,587,113,364,950,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,106 | 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 | SYSCALL_DEFINE2(link, const char __user *, oldname, const char __user *, newname)
{
return sys_linkat(AT_FDCWD, oldname, AT_FDCWD, newname, 0);
}
| 196,235,201,692,641,340,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,107 | 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 | SYSCALL_DEFINE2(rename, const char __user *, oldname, const char __user *, newname)
{
return sys_renameat2(AT_FDCWD, oldname, AT_FDCWD, newname, 0);
}
| 229,930,042,562,362,100,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,108 | 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 | SYSCALL_DEFINE3(mknod, const char __user *, filename, umode_t, mode, unsigned, dev)
{
return sys_mknodat(AT_FDCWD, filename, mode, dev);
}
| 56,059,881,829,307,980,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,109 | 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 | SYSCALL_DEFINE3(mkdirat, int, dfd, const char __user *, pathname, umode_t, mode)
{
struct dentry *dentry;
struct path path;
int error;
unsigned int lookup_flags = LOOKUP_DIRECTORY;
retry:
dentry = user_path_create(dfd, pathname, &path, lookup_flags);
if (IS_ERR(dentry))
return PTR_ERR(dentry);
if (!IS_POSIXA... | 252,495,535,629,620,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,110 | 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 | SYSCALL_DEFINE3(unlinkat, int, dfd, const char __user *, pathname, int, flag)
{
if ((flag & ~AT_REMOVEDIR) != 0)
return -EINVAL;
if (flag & AT_REMOVEDIR)
return do_rmdir(dfd, pathname);
return do_unlinkat(dfd, pathname);
}
| 28,336,766,131,256,048,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,111 | 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 | SYSCALL_DEFINE3(symlinkat, const char __user *, oldname,
int, newdfd, const char __user *, newname)
{
int error;
struct filename *from;
struct dentry *dentry;
struct path path;
unsigned int lookup_flags = 0;
from = getname(oldname);
if (IS_ERR(from))
return PTR_ERR(from);
retry:
dentry = user_path_create(n... | 116,155,753,136,232,210,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,112 | 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 | SYSCALL_DEFINE4(renameat, int, olddfd, const char __user *, oldname,
int, newdfd, const char __user *, newname)
{
return sys_renameat2(olddfd, oldname, newdfd, newname, 0);
}
| 138,088,316,289,186,120,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,113 | 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 | SYSCALL_DEFINE5(linkat, int, olddfd, const char __user *, oldname,
int, newdfd, const char __user *, newname, int, flags)
{
struct dentry *new_dentry;
struct path old_path, new_path;
struct inode *delegated_inode = NULL;
int how = 0;
int error;
if ((flags & ~(AT_SYMLINK_FOLLOW | AT_EMPTY_PATH)) != 0)
return ... | 184,052,890,000,503,940,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,114 | 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 | SYSCALL_DEFINE5(renameat2, int, olddfd, const char __user *, oldname,
int, newdfd, const char __user *, newname, unsigned int, flags)
{
struct dentry *old_dir, *new_dir;
struct dentry *old_dentry, *new_dentry;
struct dentry *trap;
struct nameidata oldnd, newnd;
struct inode *delegated_inode = NULL;
struct filen... | 112,080,439,975,032,300,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,115 | 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 __follow_mount_rcu(struct nameidata *nd, struct path *path,
struct inode **inode)
{
for (;;) {
struct mount *mounted;
/*
* Don't forget we might have a non-mountpoint managed dentry
* that wants to block transit.
*/
if (unlikely(managed_dentry_might_block(path->dentry)))
return ... | 132,888,462,159,972,270,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,116 | 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;
if (unlikely(mask & MAY_WRITE)) {
/*
* Nobody gets write access to an immutable file.
*/
if (IS_IMMUTABLE(inode))
return -EACCES;
}
retval = do_inode_permission(inode, mask);
if (retval)
return retval;
retval = devcgroup_inode_p... | 133,448,862,134,937,270,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,117 | 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 qstr *name,
struct dentry *base, unsigned int flags)
{
bool need_lookup;
struct dentry *dentry;
dentry = lookup_dcache(name, base, flags, &need_lookup);
if (!need_lookup)
return dentry;
return lookup_real(base->d_inode, dentry, flags);
}
| 100,343,022,783,422,190,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,118 | 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, int nofs)
{
struct address_space *mapping = inode->i_mapping;
struct page *page;
void *fsdata;
int err;
char *kaddr;
unsigned int flags = AOP_FLAG_UNINTERRUPTIBLE;
if (nofs)
flags |= AOP_FLAG_NOFS;
retry:
err = pagecache_write_begin(NULL, ... | 203,593,213,644,097,950,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,119 | 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 acl_permission_check(struct inode *inode, int mask)
{
unsigned int mode = inode->i_mode;
if (likely(uid_eq(current_fsuid(), inode->i_uid)))
mode >>= 6;
else {
if (IS_POSIXACL(inode) && (mode & S_IRWXG)) {
int error = check_acl(inode, mask);
if (error != -EAGAIN)
return error;
}
if (in_... | 13,787,508,554,865,965,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,120 | 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 atomic_open(struct nameidata *nd, struct dentry *dentry,
struct path *path, struct file *file,
const struct open_flags *op,
bool got_write, bool need_lookup,
int *opened)
{
struct inode *dir = nd->path.dentry->d_inode;
unsigned open_flag = open_to_namei_flags(op->open_flag);
umode_t mode;
in... | 127,299,923,056,171,240,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,121 | 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 check_acl(struct inode *inode, int mask)
{
#ifdef CONFIG_FS_POSIX_ACL
struct posix_acl *acl;
if (mask & MAY_NOT_BLOCK) {
acl = get_cached_acl_rcu(inode, ACL_TYPE_ACCESS);
if (!acl)
return -EAGAIN;
/* no ->get_acl() calls in RCU mode... */
if (acl == ACL_NOT_CACHED)
retur... | 147,176,295,180,458,820,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,122 | 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 complete_walk(struct nameidata *nd)
{
struct dentry *dentry = nd->path.dentry;
int status;
if (nd->flags & LOOKUP_RCU) {
nd->flags &= ~LOOKUP_RCU;
if (!(nd->flags & LOOKUP_ROOT))
nd->root.mnt = NULL;
if (!legitimize_mnt(nd->path.mnt, nd->m_seq)) {
rcu_read_unlock();
return -ECHILD;
}
... | 3,087,183,013,305,663,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,123 | 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 d_revalidate(struct dentry *dentry, unsigned int flags)
{
return dentry->d_op->d_revalidate(dentry, flags);
}
| 163,748,761,388,966,350,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,124 | 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 dentry_unhash(struct dentry *dentry)
{
shrink_dcache_parent(dentry);
spin_lock(&dentry->d_lock);
if (dentry->d_lockref.count == 1)
__d_drop(dentry);
spin_unlock(&dentry->d_lock);
}
| 4,555,585,957,209,531,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,125 | 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 file *do_file_open_root(struct dentry *dentry, struct vfsmount *mnt,
const char *name, const struct open_flags *op)
{
struct nameidata nd;
struct file *file;
struct filename filename = { .name = name };
int flags = op->lookup_flags | LOOKUP_ROOT;
nd.root.mnt = mnt;
nd.root.dentry = dentry;
if (d_is_sy... | 179,843,373,855,304,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,126 | 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 file *do_filp_open(int dfd, struct filename *pathname,
const struct open_flags *op)
{
struct nameidata nd;
int flags = op->lookup_flags;
struct file *filp;
filp = path_openat(dfd, pathname, &nd, op, flags | LOOKUP_RCU);
if (unlikely(filp == ERR_PTR(-ECHILD)))
filp = path_openat(dfd, pathname, &nd, op, ... | 203,036,766,305,539,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,127 | 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 do_inode_permission(struct inode *inode, int mask)
{
if (unlikely(!(inode->i_opflags & IOP_FASTPERM))) {
if (likely(inode->i_op->permission))
return inode->i_op->permission(inode, mask);
/* This gets set once for the inode lifetime */
spin_lock(&inode->i_lock);
inode->i_opflags |= IOP_FAS... | 155,692,972,030,785,810,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,128 | 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 do_last(struct nameidata *nd, struct path *path,
struct file *file, const struct open_flags *op,
int *opened, struct filename *name)
{
struct dentry *dir = nd->path.dentry;
int open_flag = op->open_flag;
bool will_truncate = (open_flag & O_TRUNC) != 0;
bool got_write = false;
int acc_mode = op... | 249,385,654,899,664,640,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,129 | 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 do_path_lookup(int dfd, const char *name,
unsigned int flags, struct nameidata *nd)
{
struct filename filename = { .name = name };
return filename_lookup(dfd, &filename, flags, nd);
}
| 39,787,654,994,097,460,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,130 | 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 long do_rmdir(int dfd, const char __user *pathname)
{
int error = 0;
struct filename *name;
struct dentry *dentry;
struct nameidata nd;
unsigned int lookup_flags = 0;
retry:
name = user_path_parent(dfd, pathname, &nd, lookup_flags);
if (IS_ERR(name))
return PTR_ERR(name);
switch(nd.last_type) {
case ... | 323,877,408,392,622,620,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,131 | 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 do_tmpfile(int dfd, struct filename *pathname,
struct nameidata *nd, int flags,
const struct open_flags *op,
struct file *file, int *opened)
{
static const struct qstr name = QSTR_INIT("/", 1);
struct dentry *dentry, *child;
struct inode *dir;
int error = path_lookupat(dfd, pathname->name,
fl... | 85,126,165,080,292,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,132 | 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 done_path_create(struct path *path, struct dentry *dentry)
{
dput(dentry);
mutex_unlock(&path->dentry->d_inode->i_mutex);
mnt_drop_write(path->mnt);
path_put(path);
}
| 146,044,654,578,378,090,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,133 | 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 filename_lookup(int dfd, struct filename *name,
unsigned int flags, struct nameidata *nd)
{
int retval = path_lookupat(dfd, name->name, flags | LOOKUP_RCU, nd);
if (unlikely(retval == -ECHILD))
retval = path_lookupat(dfd, name->name, flags, nd);
if (unlikely(retval == -ESTALE))
retval = path_looku... | 237,121,330,401,745,020,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,134 | 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 final_putname(struct filename *name)
{
if (name->separate) {
__putname(name->name);
kfree(name);
} else {
__putname(name);
}
}
| 67,991,282,077,821,240,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,135 | 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 int fold_hash(unsigned long hash)
{
hash += hash >> (8*sizeof(int));
return hash;
}
| 127,888,043,264,253,820,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,136 | 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 follow_automount(struct path *path, unsigned flags,
bool *need_mntput)
{
struct vfsmount *mnt;
int err;
if (!path->dentry->d_op || !path->dentry->d_op->d_automount)
return -EREMOTE;
/* We don't want to mount if someone's just doing a stat -
* unless they're stat'ing a directory and appended ... | 163,183,939,055,478,080,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,137 | 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 follow_dotdot(struct nameidata *nd)
{
set_root(nd);
while(1) {
struct dentry *old = nd->path.dentry;
if (nd->path.dentry == nd->root.dentry &&
nd->path.mnt == nd->root.mnt) {
break;
}
if (nd->path.dentry != nd->path.mnt->mnt_root) {
/* rare case of legitimate dget_parent()... */
n... | 203,625,559,262,542,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,138 | 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 follow_dotdot_rcu(struct nameidata *nd)
{
set_root_rcu(nd);
while (1) {
if (nd->path.dentry == nd->root.dentry &&
nd->path.mnt == nd->root.mnt) {
break;
}
if (nd->path.dentry != nd->path.mnt->mnt_root) {
struct dentry *old = nd->path.dentry;
struct dentry *parent = old->d_parent;
u... | 44,605,734,719,030,740,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,139 | 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 follow_down_one(struct path *path)
{
struct vfsmount *mounted;
mounted = lookup_mnt(path);
if (mounted) {
dput(path->dentry);
mntput(path->mnt);
path->mnt = mounted;
path->dentry = dget(mounted->mnt_root);
return 1;
}
return 0;
}
| 169,446,508,662,969,320,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,140 | 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 | follow_link(struct path *link, struct nameidata *nd, void **p)
{
struct dentry *dentry = link->dentry;
int error;
char *s;
BUG_ON(nd->flags & LOOKUP_RCU);
if (link->mnt == nd->path.mnt)
mntget(link->mnt);
error = -ELOOP;
if (unlikely(current->total_link_count >= 40))
goto out_put_nd_path;
cond_resched()... | 332,106,071,677,925,760,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,141 | 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 follow_mount(struct path *path)
{
while (d_mountpoint(path->dentry)) {
struct vfsmount *mounted = lookup_mnt(path);
if (!mounted)
break;
dput(path->dentry);
mntput(path->mnt);
path->mnt = mounted;
path->dentry = dget(mounted->mnt_root);
}
}
| 20,581,008,422,567,398,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,142 | 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 follow_up(struct path *path)
{
struct mount *mnt = real_mount(path->mnt);
struct mount *parent;
struct dentry *mountpoint;
read_seqlock_excl(&mount_lock);
parent = mnt->mnt_parent;
if (parent == mnt) {
read_sequnlock_excl(&mount_lock);
return 0;
}
mntget(&parent->mnt);
mountpoint = dget(mnt->mnt_mount... | 167,036,458,949,638,490,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,143 | 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 follow_up_rcu(struct path *path)
{
struct mount *mnt = real_mount(path->mnt);
struct mount *parent;
struct dentry *mountpoint;
parent = mnt->mnt_parent;
if (&parent->mnt == path->mnt)
return 0;
mountpoint = mnt->mnt_mountpoint;
path->dentry = mountpoint;
path->mnt = &parent->mnt;
return 1;
}
| 267,831,245,114,381,270,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,144 | 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 | unsigned int full_name_hash(const unsigned char *name, unsigned int len)
{
unsigned long a, mask;
unsigned long hash = 0;
for (;;) {
a = load_unaligned_zeropad(name);
if (len < sizeof(unsigned long))
break;
hash += a;
hash *= 9;
name += sizeof(unsigned long);
len -= sizeof(unsigned long);
if (!len)... | 270,529,396,281,337,480,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,145 | 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 | unsigned int full_name_hash(const unsigned char *name, unsigned int len)
{
unsigned long hash = init_name_hash();
while (len--)
hash = partial_name_hash(*name++, hash);
return end_name_hash(hash);
}
| 72,688,130,808,315,240,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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.