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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
33,638 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | struct dentry *ext4_get_parent(struct dentry *child)
{
__u32 ino;
static const struct qstr dotdot = QSTR_INIT("..", 2);
struct ext4_dir_entry_2 * de;
struct buffer_head *bh;
bh = ext4_find_entry(child->d_inode, &dotdot, &de, NULL);
if (!bh)
return ERR_PTR(-ENOENT);
ino = le32_to_cpu(de->inode);
brelse(bh);
... | 246,366,023,605,970,370,000,000,000,000,000,000,000 | namei.c | 232,123,123,324,503,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,639 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | int ext4_handle_dirty_dirent_node(handle_t *handle,
struct inode *inode,
struct buffer_head *bh)
{
ext4_dirent_csum_set(inode, (struct ext4_dir_entry *)bh->b_data);
return ext4_handle_dirty_metadata(handle, inode, bh);
}
| 98,789,192,014,307,760,000,000,000,000,000,000,000 | namei.c | 232,123,123,324,503,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,640 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | static inline int ext4_handle_dirty_dx_node(handle_t *handle,
struct inode *inode,
struct buffer_head *bh)
{
ext4_dx_csum_set(inode, (struct ext4_dir_entry *)bh->b_data);
return ext4_handle_dirty_metadata(handle, inode, bh);
}
| 72,397,388,304,528,250,000,000,000,000,000,000,000 | namei.c | 113,178,550,349,909,030,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,641 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | int ext4_htree_fill_tree(struct file *dir_file, __u32 start_hash,
__u32 start_minor_hash, __u32 *next_hash)
{
struct dx_hash_info hinfo;
struct ext4_dir_entry_2 *de;
struct dx_frame frames[2], *frame;
struct inode *dir;
ext4_lblk_t block;
int count = 0;
int ret, err;
__u32 hashval;
dxtrace(printk(KERN_DEB... | 24,789,324,387,898,450,000,000,000,000,000,000,000 | namei.c | 232,123,123,324,503,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,642 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | static int ext4_htree_next_block(struct inode *dir, __u32 hash,
struct dx_frame *frame,
struct dx_frame *frames,
__u32 *start_hash)
{
struct dx_frame *p;
struct buffer_head *bh;
int err, num_frames = 0;
__u32 bhash;
p = frame;
/*
* Find the next leaf page by incrementing the frame pointer.
* I... | 319,748,449,564,764,300,000,000,000,000,000,000,000 | namei.c | 232,123,123,324,503,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,643 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | static void ext4_inc_count(handle_t *handle, struct inode *inode)
{
inc_nlink(inode);
if (is_dx(inode) && inode->i_nlink > 1) {
/* limit is 16-bit i_links_count */
if (inode->i_nlink >= EXT4_LINK_MAX || inode->i_nlink == 2) {
set_nlink(inode, 1);
EXT4_SET_RO_COMPAT_FEATURE(inode->i_sb,
EXT4_FEATU... | 324,764,938,798,956,000,000,000,000,000,000,000,000 | namei.c | 232,123,123,324,503,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,644 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | struct ext4_dir_entry_2 *ext4_init_dot_dotdot(struct inode *inode,
struct ext4_dir_entry_2 *de,
int blocksize, int csum_size,
unsigned int parent_ino, int dotdot_real_len)
{
de->inode = cpu_to_le32(inode->i_ino);
de->name_len = 1;
de->rec_len = ext4_rec_len_to_disk(EXT4_DIR_REC_LEN(de->name_len),
... | 140,945,889,924,448,180,000,000,000,000,000,000,000 | namei.c | 113,178,550,349,909,030,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,645 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | static int ext4_init_new_dir(handle_t *handle, struct inode *dir,
struct inode *inode)
{
struct buffer_head *dir_block = NULL;
struct ext4_dir_entry_2 *de;
struct ext4_dir_entry_tail *t;
unsigned int blocksize = dir->i_sb->s_blocksize;
int csum_size = 0;
int err;
if (EXT4_HAS_RO_COMPAT_FEATURE(dir->i_sb... | 128,837,719,398,360,520,000,000,000,000,000,000,000 | namei.c | 232,123,123,324,503,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,646 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | void ext4_insert_dentry(struct inode *inode,
struct ext4_dir_entry_2 *de,
int buf_size,
const char *name, int namelen)
{
int nlen, rlen;
nlen = EXT4_DIR_REC_LEN(de->name_len);
rlen = ext4_rec_len_from_disk(de->rec_len, buf_size);
if (de->inode) {
struct ext4_dir_entry_2 *de1 =
(struct ext4_dir_entr... | 122,781,334,047,806,800,000,000,000,000,000,000,000 | namei.c | 232,123,123,324,503,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,647 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | static int ext4_link(struct dentry *old_dentry,
struct inode *dir, struct dentry *dentry)
{
handle_t *handle;
struct inode *inode = old_dentry->d_inode;
int err, retries = 0;
if (inode->i_nlink >= EXT4_LINK_MAX)
return -EMLINK;
dquot_initialize(dir);
retry:
handle = ext4_journal_start(dir, EXT4_DATA_T... | 125,258,397,547,092,900,000,000,000,000,000,000,000 | namei.c | 232,123,123,324,503,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,648 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | static struct dentry *ext4_lookup(struct inode *dir, struct dentry *dentry, unsigned int flags)
{
struct inode *inode;
struct ext4_dir_entry_2 *de;
struct buffer_head *bh;
if (dentry->d_name.len > EXT4_NAME_LEN)
return ERR_PTR(-ENAMETOOLONG);
bh = ext4_find_entry(dir, &dentry->d_name, &de, NULL);
inode = NULL... | 2,535,891,867,988,625,400,000,000,000,000,000,000 | namei.c | 232,123,123,324,503,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,649 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | static inline int ext4_match (int len, const char * const name,
struct ext4_dir_entry_2 * de)
{
if (len != de->name_len)
return 0;
if (!de->inode)
return 0;
return !memcmp(name, de->name, len);
}
| 80,001,345,871,164,060,000,000,000,000,000,000,000 | namei.c | 232,123,123,324,503,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,650 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | static int ext4_mkdir(struct inode *dir, struct dentry *dentry, umode_t mode)
{
handle_t *handle;
struct inode *inode;
int err, retries = 0;
if (EXT4_DIR_LINK_MAX(dir))
return -EMLINK;
dquot_initialize(dir);
retry:
handle = ext4_journal_start(dir, EXT4_DATA_TRANS_BLOCKS(dir->i_sb) +
EXT4_INDEX_EXTRA_TRA... | 34,109,746,179,525,430,000,000,000,000,000,000,000 | namei.c | 232,123,123,324,503,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,651 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | static int ext4_mknod(struct inode *dir, struct dentry *dentry,
umode_t mode, dev_t rdev)
{
handle_t *handle;
struct inode *inode;
int err, retries = 0;
if (!new_valid_dev(rdev))
return -EINVAL;
dquot_initialize(dir);
retry:
handle = ext4_journal_start(dir, EXT4_DATA_TRANS_BLOCKS(dir->i_sb) +
EX... | 326,162,113,244,601,450,000,000,000,000,000,000,000 | namei.c | 232,123,123,324,503,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,652 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | ext4_next_entry(struct ext4_dir_entry_2 *p, unsigned long blocksize)
{
return (struct ext4_dir_entry_2 *)((char *)p +
ext4_rec_len_from_disk(p->rec_len, blocksize));
}
| 43,319,599,520,727,400,000,000,000,000,000,000,000 | namei.c | 113,178,550,349,909,030,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,653 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | int ext4_orphan_add(handle_t *handle, struct inode *inode)
{
struct super_block *sb = inode->i_sb;
struct ext4_iloc iloc;
int err = 0, rc;
if (!EXT4_SB(sb)->s_journal)
return 0;
mutex_lock(&EXT4_SB(sb)->s_orphan_lock);
if (!list_empty(&EXT4_I(inode)->i_orphan))
goto out_unlock;
/*
* Orphan handling is o... | 49,180,516,333,045,100,000,000,000,000,000,000,000 | namei.c | 232,123,123,324,503,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,654 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | static int ext4_rename(struct inode *old_dir, struct dentry *old_dentry,
struct inode *new_dir, struct dentry *new_dentry)
{
handle_t *handle;
struct inode *old_inode, *new_inode;
struct buffer_head *old_bh, *new_bh, *dir_bh;
struct ext4_dir_entry_2 *old_de, *new_de;
int retval, force_da_alloc = 0;
int i... | 163,404,326,121,923,510,000,000,000,000,000,000,000 | namei.c | 232,123,123,324,503,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,655 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | static int ext4_rmdir(struct inode *dir, struct dentry *dentry)
{
int retval;
struct inode *inode;
struct buffer_head *bh;
struct ext4_dir_entry_2 *de;
handle_t *handle;
/* Initialize quotas before so that eventual writes go in
* separate transaction */
dquot_initialize(dir);
dquot_initialize(dentry->d_inode... | 143,625,435,509,105,580,000,000,000,000,000,000,000 | namei.c | 232,123,123,324,503,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,656 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | static inline void ext4_set_de_type(struct super_block *sb,
struct ext4_dir_entry_2 *de,
umode_t mode) {
if (EXT4_HAS_INCOMPAT_FEATURE(sb, EXT4_FEATURE_INCOMPAT_FILETYPE))
de->file_type = ext4_type_by_mode[(mode & S_IFMT)>>S_SHIFT];
}
| 156,146,134,401,531,320,000,000,000,000,000,000,000 | namei.c | 232,123,123,324,503,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,657 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | static int ext4_symlink(struct inode *dir,
struct dentry *dentry, const char *symname)
{
handle_t *handle;
struct inode *inode;
int l, err, retries = 0;
int credits;
l = strlen(symname)+1;
if (l > dir->i_sb->s_blocksize)
return -ENAMETOOLONG;
dquot_initialize(dir);
if (l > EXT4_N_BLOCKS * 4) {
/*
*... | 200,040,445,837,950,170,000,000,000,000,000,000,000 | namei.c | 232,123,123,324,503,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,658 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | static int ext4_unlink(struct inode *dir, struct dentry *dentry)
{
int retval;
struct inode *inode;
struct buffer_head *bh;
struct ext4_dir_entry_2 *de;
handle_t *handle;
trace_ext4_unlink_enter(dir, dentry);
/* Initialize quotas before so that eventual writes go
* in separate transaction */
dquot_initialize... | 251,206,646,466,283,420,000,000,000,000,000,000,000 | namei.c | 232,123,123,324,503,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,659 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | static struct ext4_dir_entry_tail *get_dirent_tail(struct inode *inode,
struct ext4_dir_entry *de)
{
struct ext4_dir_entry_tail *t;
#ifdef PARANOID
struct ext4_dir_entry *d, *top;
d = de;
top = (struct ext4_dir_entry *)(((void *)de) +
(EXT4_BLOCK_SIZE(inode->i_sb) -
sizeof(struct ext4_dir_entry_tail)... | 226,483,234,881,905,320,000,000,000,000,000,000,000 | namei.c | 232,123,123,324,503,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,660 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | void initialize_dirent_tail(struct ext4_dir_entry_tail *t,
unsigned int blocksize)
{
memset(t, 0, sizeof(struct ext4_dir_entry_tail));
t->det_rec_len = ext4_rec_len_to_disk(
sizeof(struct ext4_dir_entry_tail), blocksize);
t->det_reserved_ft = EXT4_FT_DIR_CSUM;
}
| 125,969,363,591,304,600,000,000,000,000,000,000,000 | namei.c | 232,123,123,324,503,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,661 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | static int is_dx_internal_node(struct inode *dir, ext4_lblk_t block,
struct ext4_dir_entry *de)
{
struct super_block *sb = dir->i_sb;
if (!is_dx(dir))
return 0;
if (block == 0)
return 1;
if (de->inode == 0 &&
ext4_rec_len_from_disk(de->rec_len, sb->s_blocksize) ==
sb->s_blocksize)
return 1;... | 264,940,061,818,672,400,000,000,000,000,000,000,000 | namei.c | 113,178,550,349,909,030,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,662 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | static int make_indexed_dir(handle_t *handle, struct dentry *dentry,
struct inode *inode, struct buffer_head *bh)
{
struct inode *dir = dentry->d_parent->d_inode;
const char *name = dentry->d_name.name;
int namelen = dentry->d_name.len;
struct buffer_head *bh2;
struct dx_root *root;
struct dx_frame frames... | 103,894,034,753,160,360,000,000,000,000,000,000,000 | namei.c | 232,123,123,324,503,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,663 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | int search_dir(struct buffer_head *bh,
char *search_buf,
int buf_size,
struct inode *dir,
const struct qstr *d_name,
unsigned int offset,
struct ext4_dir_entry_2 **res_dir)
{
struct ext4_dir_entry_2 * de;
char * dlimit;
int de_len;
const char *name = d_name->name;
in... | 320,483,970,100,918,270,000,000,000,000,000,000,000 | namei.c | 232,123,123,324,503,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,664 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | static inline int search_dirblock(struct buffer_head *bh,
struct inode *dir,
const struct qstr *d_name,
unsigned int offset,
struct ext4_dir_entry_2 **res_dir)
{
return search_dir(bh, bh->b_data, dir->i_sb->s_blocksize, dir,
d_name, offset, res_dir);
}
| 318,532,413,246,443,500,000,000,000,000,000,000,000 | namei.c | 232,123,123,324,503,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,665 | linux | 0e9a9a1ad619e7e987815d20262d36a2f95717ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e9a9a1ad619e7e987815d20262d36a2f95717ca | ext4: avoid hang when mounting non-journal filesystems with orphan list
When trying to mount a file system which does not contain a journal,
but which does have a orphan list containing an inode which needs to
be truncated, the mount call with hang forever in
ext4_orphan_cleanup() because ext4_orphan_del() will return... | 0 | static void warn_no_space_for_csum(struct inode *inode)
{
ext4_warning(inode->i_sb, "no space in directory inode %lu leaf for "
"checksum. Please run e2fsck -D.", inode->i_ino);
}
| 235,695,095,319,407,360,000,000,000,000,000,000,000 | namei.c | 232,123,123,324,503,340,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2015 | The ext4_orphan_del function in fs/ext4/namei.c in the Linux kernel before 3.7.3 does not properly handle orphan-list entries for non-journal filesystems, which allows physically proximate attackers to cause a denial of service (system hang) via a crafted filesystem on removable media, as demonstrated by the e2fsprogs ... | https://nvd.nist.gov/vuln/detail/CVE-2013-2015 |
33,666 | linux | 92f28d973cce45ef5823209aab3138eb45d8b349 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/92f28d973cce45ef5823209aab3138eb45d8b349 | scm: Require CAP_SYS_ADMIN over the current pidns to spoof pids.
Don't allow spoofing pids over unix domain sockets in the corner
cases where a user has created a user namespace but has not yet
created a pid namespace.
Cc: stable@vger.kernel.org
Reported-by: Andy Lutomirski <luto@amacapital.net>
Signed-off-by: "Eric ... | 0 | int __scm_send(struct socket *sock, struct msghdr *msg, struct scm_cookie *p)
{
struct cmsghdr *cmsg;
int err;
for (cmsg = CMSG_FIRSTHDR(msg); cmsg; cmsg = CMSG_NXTHDR(msg, cmsg))
{
err = -EINVAL;
/* Verify that cmsg_len is at least sizeof(struct cmsghdr) */
/* The first check was omitted in <= 2.2.5. The r... | 120,839,095,463,257,050,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-1958 | The scm_check_creds function in net/core/scm.c in the Linux kernel before 3.8.6 does not properly enforce capability requirements for controlling the PID value associated with a UNIX domain socket, which allows local users to bypass intended access restrictions by leveraging the time interval during which a user namesp... | https://nvd.nist.gov/vuln/detail/CVE-2013-1958 |
33,667 | linux | 92f28d973cce45ef5823209aab3138eb45d8b349 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/92f28d973cce45ef5823209aab3138eb45d8b349 | scm: Require CAP_SYS_ADMIN over the current pidns to spoof pids.
Don't allow spoofing pids over unix domain sockets in the corner
cases where a user has created a user namespace but has not yet
created a pid namespace.
Cc: stable@vger.kernel.org
Reported-by: Andy Lutomirski <luto@amacapital.net>
Signed-off-by: "Eric ... | 0 | void scm_detach_fds(struct msghdr *msg, struct scm_cookie *scm)
{
struct cmsghdr __user *cm
= (__force struct cmsghdr __user*)msg->msg_control;
int fdmax = 0;
int fdnum = scm->fp->count;
struct file **fp = scm->fp->fp;
int __user *cmfptr;
int err = 0, i;
if (MSG_CMSG_COMPAT & msg->msg_flags) {
scm_detach_f... | 15,712,551,525,574,337,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-1958 | The scm_check_creds function in net/core/scm.c in the Linux kernel before 3.8.6 does not properly enforce capability requirements for controlling the PID value associated with a UNIX domain socket, which allows local users to bypass intended access restrictions by leveraging the time interval during which a user namesp... | https://nvd.nist.gov/vuln/detail/CVE-2013-1958 |
33,668 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | SYSCALL_DEFINE1(oldumount, char __user *, name)
{
return sys_umount(name, 0);
}
| 61,741,053,849,207,900,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,669 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | SYSCALL_DEFINE2(umount, char __user *, name, int, flags)
{
struct path path;
struct mount *mnt;
int retval;
int lookup_flags = 0;
if (flags & ~(MNT_FORCE | MNT_DETACH | MNT_EXPIRE | UMOUNT_NOFOLLOW))
return -EINVAL;
if (!may_mount())
return -EPERM;
if (!(flags & UMOUNT_NOFOLLOW))
lookup_flags |= LOOKUP_... | 209,813,518,553,251,480,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,670 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 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;
int error;
if (!may_mount())
return -EPERM;
error = user_path_dir(new_root, &new);
if (error)
goto out0;
error = user_path_di... | 229,434,777,855,048,720,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,671 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | SYSCALL_DEFINE5(mount, char __user *, dev_name, char __user *, dir_name,
char __user *, type, unsigned long, flags, void __user *, data)
{
int ret;
char *kernel_type;
struct filename *kernel_dir;
char *kernel_dev;
unsigned long data_page;
ret = copy_mount_string(type, &kernel_type);
if (ret < 0)
goto out_ty... | 62,326,780,343,218,720,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,672 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | void __mnt_drop_write(struct vfsmount *mnt)
{
preempt_disable();
mnt_dec_writers(real_mount(mnt));
preempt_enable();
}
| 26,595,928,445,480,490,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,673 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | void __mnt_drop_write_file(struct file *file)
{
__mnt_drop_write(file->f_path.mnt);
}
| 52,277,179,877,654,530,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,674 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | int __mnt_is_readonly(struct vfsmount *mnt)
{
if (mnt->mnt_flags & MNT_READONLY)
return 1;
if (mnt->mnt_sb->s_flags & MS_RDONLY)
return 1;
return 0;
}
| 146,637,071,863,572,800,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,675 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static void __mnt_unmake_readonly(struct mount *mnt)
{
br_write_lock(&vfsmount_lock);
mnt->mnt.mnt_flags &= ~MNT_READONLY;
br_write_unlock(&vfsmount_lock);
}
| 226,010,183,462,882,200,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,676 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | int __mnt_want_write(struct vfsmount *m)
{
struct mount *mnt = real_mount(m);
int ret = 0;
preempt_disable();
mnt_inc_writers(mnt);
/*
* The store to mnt_inc_writers must be visible before we pass
* MNT_WRITE_HOLD loop below, so that the slowpath can see our
* incremented count after it has set MNT_WRITE_HO... | 323,821,145,923,099,700,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,677 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | int __mnt_want_write_file(struct file *file)
{
struct inode *inode = file_inode(file);
if (!(file->f_mode & FMODE_WRITE) || special_file(inode->i_mode))
return __mnt_want_write(file->f_path.mnt);
else
return mnt_clone_write(file->f_path.mnt);
}
| 279,850,656,332,536,350,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,678 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static struct mnt_namespace *alloc_mnt_ns(struct user_namespace *user_ns)
{
struct mnt_namespace *new_ns;
int ret;
new_ns = kmalloc(sizeof(struct mnt_namespace), GFP_KERNEL);
if (!new_ns)
return ERR_PTR(-ENOMEM);
ret = proc_alloc_inum(&new_ns->proc_inum);
if (ret) {
kfree(new_ns);
return ERR_PTR(ret);
}
... | 287,815,234,503,563,660,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,679 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static struct mount *alloc_vfsmnt(const char *name)
{
struct mount *mnt = kmem_cache_zalloc(mnt_cache, GFP_KERNEL);
if (mnt) {
int err;
err = mnt_alloc_id(mnt);
if (err)
goto out_free_cache;
if (name) {
mnt->mnt_devname = kstrdup(name, GFP_KERNEL);
if (!mnt->mnt_devname)
goto out_free_id;
}
... | 302,853,928,103,913,100,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,680 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static void attach_mnt(struct mount *mnt, struct path *path)
{
mnt_set_mountpoint(real_mount(path->mnt), path->dentry, mnt);
list_add_tail(&mnt->mnt_hash, mount_hashtable +
hash(path->mnt, path->dentry));
list_add_tail(&mnt->mnt_child, &real_mount(path->mnt)->mnt_mounts);
}
| 267,564,166,895,172,600,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,681 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static int attach_recursive_mnt(struct mount *source_mnt,
struct path *path, struct path *parent_path)
{
LIST_HEAD(tree_list);
struct mount *dest_mnt = real_mount(path->mnt);
struct dentry *dest_dentry = path->dentry;
struct mount *child, *p;
int err;
if (IS_MNT_SHARED(dest_mnt)) {
err = invent_group_ids(so... | 96,953,501,913,317,400,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,682 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static inline int check_mnt(struct mount *mnt)
{
return mnt->mnt_ns == current->nsproxy->mnt_ns;
}
| 275,246,108,839,212,400,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,683 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static void cleanup_group_ids(struct mount *mnt, struct mount *end)
{
struct mount *p;
for (p = mnt; p != end; p = next_mnt(p, mnt)) {
if (p->mnt_group_id && !IS_MNT_SHARED(p))
mnt_release_group_id(p);
}
}
| 88,656,576,700,652,450,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,684 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | struct vfsmount *collect_mounts(struct path *path)
{
struct mount *tree;
down_write(&namespace_sem);
tree = copy_tree(real_mount(path->mnt), path->dentry,
CL_COPY_ALL | CL_PRIVATE);
up_write(&namespace_sem);
if (IS_ERR(tree))
return NULL;
return &tree->mnt;
}
| 276,274,406,555,029,400,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,685 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static void commit_tree(struct mount *mnt)
{
struct mount *parent = mnt->mnt_parent;
struct mount *m;
LIST_HEAD(head);
struct mnt_namespace *n = parent->mnt_ns;
BUG_ON(parent == mnt);
list_add_tail(&head, &mnt->mnt_list);
list_for_each_entry(m, &head, mnt_list)
m->mnt_ns = n;
list_splice(&head, n->list.pre... | 131,756,923,560,360,500,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,686 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | struct mnt_namespace *copy_mnt_ns(unsigned long flags, struct mnt_namespace *ns,
struct user_namespace *user_ns, struct fs_struct *new_fs)
{
struct mnt_namespace *new_ns;
BUG_ON(!ns);
get_mnt_ns(ns);
if (!(flags & CLONE_NEWNS))
return ns;
new_ns = dup_mnt_ns(ns, user_ns, new_fs);
put_mnt_ns(ns);
return n... | 314,701,411,068,522,000,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,687 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | int copy_mount_options(const void __user * data, unsigned long *where)
{
int i;
unsigned long page;
unsigned long size;
*where = 0;
if (!data)
return 0;
if (!(page = __get_free_page(GFP_KERNEL)))
return -ENOMEM;
/* We only care that *some* data at the address the user
* gave us is valid. Just in case, ... | 92,171,790,642,976,500,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,688 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | int copy_mount_string(const void __user *data, char **where)
{
char *tmp;
if (!data) {
*where = NULL;
return 0;
}
tmp = strndup_user(data, PAGE_SIZE);
if (IS_ERR(tmp))
return PTR_ERR(tmp);
*where = tmp;
return 0;
}
| 205,667,398,414,090,600,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,689 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | struct mount *copy_tree(struct mount *mnt, struct dentry *dentry,
int flag)
{
struct mount *res, *p, *q, *r;
struct path path;
if (!(flag & CL_COPY_ALL) && IS_MNT_UNBINDABLE(mnt))
return ERR_PTR(-EINVAL);
res = q = clone_mnt(mnt, dentry, flag);
if (IS_ERR(q))
return q;
q->mnt_mountpoint = mnt->mnt_mou... | 153,074,672,777,395,750,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,690 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static struct mnt_namespace *create_mnt_ns(struct vfsmount *m)
{
struct mnt_namespace *new_ns = alloc_mnt_ns(&init_user_ns);
if (!IS_ERR(new_ns)) {
struct mount *mnt = real_mount(m);
mnt->mnt_ns = new_ns;
new_ns->root = mnt;
list_add(&new_ns->list, &mnt->mnt_list);
} else {
mntput(m);
}
return new_ns;
}
| 238,608,831,674,095,550,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,691 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | bool current_chrooted(void)
{
/* Does the current process have a non-standard root */
struct path ns_root;
struct path fs_root;
bool chrooted;
/* Find the namespace root */
ns_root.mnt = ¤t->nsproxy->mnt_ns->root->mnt;
ns_root.dentry = ns_root.mnt->mnt_root;
path_get(&ns_root);
while (d_mountpoint(ns_ro... | 192,834,472,218,085,150,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,692 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static void dentry_reset_mounted(struct dentry *dentry)
{
unsigned u;
for (u = 0; u < HASH_SIZE; u++) {
struct mount *p;
list_for_each_entry(p, &mount_hashtable[u], mnt_hash) {
if (p->mnt_mountpoint == dentry)
return;
}
}
spin_lock(&dentry->d_lock);
dentry->d_flags &= ~DCACHE_MOUNTED;
spin_unlock(&... | 208,211,860,400,216,570,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,693 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static void detach_mnt(struct mount *mnt, struct path *old_path)
{
old_path->dentry = mnt->mnt_mountpoint;
old_path->mnt = &mnt->mnt_parent->mnt;
mnt->mnt_parent = mnt;
mnt->mnt_mountpoint = mnt->mnt.mnt_root;
list_del_init(&mnt->mnt_child);
list_del_init(&mnt->mnt_hash);
dentry_reset_mounted(old_path->dentry);
... | 86,523,382,275,881,580,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,694 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static int do_add_mount(struct mount *newmnt, struct path *path, int mnt_flags)
{
int err;
mnt_flags &= ~(MNT_SHARED | MNT_WRITE_HOLD | MNT_INTERNAL);
err = lock_mount(path);
if (err)
return err;
err = -EINVAL;
if (unlikely(!check_mnt(real_mount(path->mnt)))) {
/* that's acceptable only for automounts done... | 177,212,518,171,377,540,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,695 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static int do_change_type(struct path *path, int flag)
{
struct mount *m;
struct mount *mnt = real_mount(path->mnt);
int recurse = flag & MS_REC;
int type;
int err = 0;
if (path->dentry != path->mnt->mnt_root)
return -EINVAL;
type = flags_to_propagation_type(flag);
if (!type)
return -EINVAL;
down_write(... | 188,737,795,805,797,130,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,696 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static int do_loopback(struct path *path, const char *old_name,
int recurse)
{
LIST_HEAD(umount_list);
struct path old_path;
struct mount *mnt = NULL, *old;
int err;
if (!old_name || !*old_name)
return -EINVAL;
err = kern_path(old_name, LOOKUP_FOLLOW|LOOKUP_AUTOMOUNT, &old_path);
if (err)
return err;
e... | 240,601,166,830,774,530,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,697 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 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... | 225,487,638,901,060,260,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,698 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static int do_remount(struct path *path, int flags, int mnt_flags,
void *data)
{
int err;
struct super_block *sb = path->mnt->mnt_sb;
struct mount *mnt = real_mount(path->mnt);
if (!check_mnt(mnt))
return -EINVAL;
if (path->dentry != path->mnt->mnt_root)
return -EINVAL;
err = security_sb_remount(sb... | 160,307,290,069,952,010,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,699 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static int do_umount(struct mount *mnt, int flags)
{
struct super_block *sb = mnt->mnt.mnt_sb;
int retval;
LIST_HEAD(umount_list);
retval = security_sb_umount(&mnt->mnt, flags);
if (retval)
return retval;
/*
* Allow userspace to request a mountpoint be expired rather than
* unmounting unconditionally. Unm... | 125,030,534,381,599,570,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,700 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | void drop_collected_mounts(struct vfsmount *mnt)
{
LIST_HEAD(umount_list);
down_write(&namespace_sem);
br_write_lock(&vfsmount_lock);
umount_tree(real_mount(mnt), 0, &umount_list);
br_write_unlock(&vfsmount_lock);
up_write(&namespace_sem);
release_mounts(&umount_list);
}
| 234,088,196,974,631,500,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,701 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static long exact_copy_from_user(void *to, const void __user * from,
unsigned long n)
{
char *t = to;
const char __user *f = from;
char c;
if (!access_ok(VERIFY_READ, from, n))
return n;
while (n) {
if (__get_user(c, f)) {
memset(t, 0, n);
break;
}
*t++ = c;
f++;
n--;
}
return n;
}
| 314,743,046,921,008,440,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,702 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | int finish_automount(struct vfsmount *m, struct path *path)
{
struct mount *mnt = real_mount(m);
int err;
/* The new mount record should have at least 2 refs to prevent it being
* expired before we get a chance to add it
*/
BUG_ON(mnt_get_count(mnt) < 2);
if (m->mnt_sb == path->mnt->mnt_sb &&
m->mnt_root... | 150,343,518,699,133,550,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,703 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static int flags_to_propagation_type(int flags)
{
int type = flags & ~(MS_REC | MS_SILENT);
/* Fail if any non-propagation flags are set */
if (type & ~(MS_SHARED | MS_PRIVATE | MS_SLAVE | MS_UNBINDABLE))
return 0;
/* Only one propagation flag should be set */
if (!is_power_of_2(type))
return 0;
return type;... | 80,432,577,807,784,980,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,704 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static void free_mnt_ns(struct mnt_namespace *ns)
{
proc_free_inum(ns->proc_inum);
put_user_ns(ns->user_ns);
kfree(ns);
}
| 325,290,383,984,014,300,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,705 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static struct vfsmount *fs_set_subtype(struct vfsmount *mnt, const char *fstype)
{
int err;
const char *subtype = strchr(fstype, '.');
if (subtype) {
subtype++;
err = -EINVAL;
if (!subtype[0])
goto err;
} else
subtype = "";
mnt->mnt_sb->s_subtype = kstrdup(subtype, GFP_KERNEL);
err = -ENOMEM;
if (!mn... | 176,773,615,963,467,270,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,706 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | int generic_show_options(struct seq_file *m, struct dentry *root)
{
const char *options;
rcu_read_lock();
options = rcu_dereference(root->d_sb->s_options);
if (options != NULL && options[0]) {
seq_putc(m, ',');
mangle(m, options);
}
rcu_read_unlock();
return 0;
}
| 255,292,442,945,538,350,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,707 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static int graft_tree(struct mount *mnt, struct path *path)
{
if (mnt->mnt.mnt_sb->s_flags & MS_NOUSER)
return -EINVAL;
if (S_ISDIR(path->dentry->d_inode->i_mode) !=
S_ISDIR(mnt->mnt.mnt_root->d_inode->i_mode))
return -ENOTDIR;
if (d_unlinked(path->dentry))
return -ENOENT;
return attach_recursive_mn... | 239,251,705,558,547,900,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,708 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static inline unsigned long hash(struct vfsmount *mnt, struct dentry *dentry)
{
unsigned long tmp = ((unsigned long)mnt / L1_CACHE_BYTES);
tmp += ((unsigned long)dentry / L1_CACHE_BYTES);
tmp = tmp + (tmp >> HASH_SHIFT);
return tmp & (HASH_SIZE - 1);
}
| 291,303,149,681,749,820,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,709 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static void __init init_mount_tree(void)
{
struct vfsmount *mnt;
struct mnt_namespace *ns;
struct path root;
struct file_system_type *type;
type = get_fs_type("rootfs");
if (!type)
panic("Can't find rootfs type");
mnt = vfs_kern_mount(type, 0, "rootfs", NULL);
put_filesystem(type);
if (IS_ERR(mnt))
panic(... | 40,806,493,523,620,490,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,710 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static int invent_group_ids(struct mount *mnt, bool recurse)
{
struct mount *p;
for (p = mnt; p; p = recurse ? next_mnt(p, mnt) : NULL) {
if (!p->mnt_group_id && !IS_MNT_SHARED(p)) {
int err = mnt_alloc_group_id(p);
if (err) {
cleanup_group_ids(mnt, p);
return err;
}
}
}
return 0;
}
| 89,032,158,439,076,240,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,711 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | bool is_path_reachable(struct mount *mnt, struct dentry *dentry,
const struct path *root)
{
while (&mnt->mnt != root->mnt && mnt_has_parent(mnt)) {
dentry = mnt->mnt_mountpoint;
mnt = mnt->mnt_parent;
}
return &mnt->mnt == root->mnt && is_subdir(dentry, root->dentry);
}
| 103,257,377,859,755,580,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,712 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | struct vfsmount *kern_mount_data(struct file_system_type *type, void *data)
{
struct vfsmount *mnt;
mnt = vfs_kern_mount(type, MS_KERNMOUNT, type->name, data);
if (!IS_ERR(mnt)) {
/*
* it is a longterm mount, don't release mnt until
* we unmount before file sys is unregistered
*/
real_mount(mnt)->mnt_ns ... | 289,023,106,314,817,330,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,713 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | void kern_unmount(struct vfsmount *mnt)
{
/* release long term mount so mount point can be released */
if (!IS_ERR_OR_NULL(mnt)) {
br_write_lock(&vfsmount_lock);
real_mount(mnt)->mnt_ns = NULL;
br_write_unlock(&vfsmount_lock);
mntput(mnt);
}
}
| 51,940,462,328,449,760,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,714 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static int lock_mount(struct path *path)
{
struct vfsmount *mnt;
retry:
mutex_lock(&path->dentry->d_inode->i_mutex);
if (unlikely(cant_mount(path->dentry))) {
mutex_unlock(&path->dentry->d_inode->i_mutex);
return -ENOENT;
}
down_write(&namespace_sem);
mnt = lookup_mnt(path);
if (likely(!mnt))
return 0;
up... | 14,105,796,755,969,462,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,715 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | struct vfsmount *lookup_mnt(struct path *path)
{
struct mount *child_mnt;
br_read_lock(&vfsmount_lock);
child_mnt = __lookup_mnt(path->mnt, path->dentry, 1);
if (child_mnt) {
mnt_add_count(child_mnt, 1);
br_read_unlock(&vfsmount_lock);
return &child_mnt->mnt;
} else {
br_read_unlock(&vfsmount_lock);
ret... | 106,285,637,744,077,640,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,716 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static void *m_next(struct seq_file *m, void *v, loff_t *pos)
{
struct proc_mounts *p = proc_mounts(m);
return seq_list_next(v, &p->ns->list, pos);
}
| 8,874,363,241,501,333,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,717 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static int m_show(struct seq_file *m, void *v)
{
struct proc_mounts *p = proc_mounts(m);
struct mount *r = list_entry(v, struct mount, mnt_list);
return p->show(m, &r->mnt);
}
| 104,854,912,452,590,430,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,718 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static void *m_start(struct seq_file *m, loff_t *pos)
{
struct proc_mounts *p = proc_mounts(m);
down_read(&namespace_sem);
return seq_list_start(&p->ns->list, *pos);
}
| 213,792,570,480,289,800,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,719 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static void m_stop(struct seq_file *m, void *v)
{
up_read(&namespace_sem);
}
| 84,704,226,563,030,170,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,720 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static inline void mangle(struct seq_file *m, const char *s)
{
seq_escape(m, s, " \t\n\\");
}
| 261,570,753,070,822,100,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,721 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | void mark_mounts_for_expiry(struct list_head *mounts)
{
struct mount *mnt, *next;
LIST_HEAD(graveyard);
LIST_HEAD(umounts);
if (list_empty(mounts))
return;
down_write(&namespace_sem);
br_write_lock(&vfsmount_lock);
/* extract from the expiration list every vfsmount that matches the
* following criteria:
... | 77,812,032,648,719,710,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,722 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static inline bool may_mount(void)
{
return ns_capable(current->nsproxy->mnt_ns->user_ns, CAP_SYS_ADMIN);
}
| 300,176,658,383,434,100,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,723 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | int may_umount(struct vfsmount *mnt)
{
int ret = 1;
down_read(&namespace_sem);
br_write_lock(&vfsmount_lock);
if (propagate_mount_busy(real_mount(mnt), 2))
ret = 0;
br_write_unlock(&vfsmount_lock);
up_read(&namespace_sem);
return ret;
}
| 240,646,607,194,952,500,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,724 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static inline void mnt_add_count(struct mount *mnt, int n)
{
#ifdef CONFIG_SMP
this_cpu_add(mnt->mnt_pcp->mnt_count, n);
#else
preempt_disable();
mnt->mnt_count += n;
preempt_enable();
#endif
}
| 75,850,654,601,864,710,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,725 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static int mnt_alloc_group_id(struct mount *mnt)
{
int res;
if (!ida_pre_get(&mnt_group_ida, GFP_KERNEL))
return -ENOMEM;
res = ida_get_new_above(&mnt_group_ida,
mnt_group_start,
&mnt->mnt_group_id);
if (!res)
mnt_group_start = mnt->mnt_group_id + 1;
return res;
}
| 338,901,021,453,720,400,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,726 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static int mnt_alloc_id(struct mount *mnt)
{
int res;
retry:
ida_pre_get(&mnt_id_ida, GFP_KERNEL);
spin_lock(&mnt_id_lock);
res = ida_get_new_above(&mnt_id_ida, mnt_id_start, &mnt->mnt_id);
if (!res)
mnt_id_start = mnt->mnt_id + 1;
spin_unlock(&mnt_id_lock);
if (res == -EAGAIN)
goto retry;
return res;
}
| 133,434,882,991,925,220,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,727 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | int mnt_clone_write(struct vfsmount *mnt)
{
/* superblock may be r/o */
if (__mnt_is_readonly(mnt))
return -EROFS;
preempt_disable();
mnt_inc_writers(real_mount(mnt));
preempt_enable();
return 0;
}
| 232,669,270,973,366,700,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,728 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static inline void mnt_dec_writers(struct mount *mnt)
{
#ifdef CONFIG_SMP
this_cpu_dec(mnt->mnt_pcp->mnt_writers);
#else
mnt->mnt_writers--;
#endif
}
| 88,305,042,336,601,490,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,729 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | void mnt_drop_write(struct vfsmount *mnt)
{
__mnt_drop_write(mnt);
sb_end_write(mnt->mnt_sb);
}
| 204,968,060,085,719,170,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,730 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | void mnt_drop_write_file(struct file *file)
{
mnt_drop_write(file->f_path.mnt);
}
| 61,612,730,580,532,100,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,731 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static void mnt_free_id(struct mount *mnt)
{
int id = mnt->mnt_id;
spin_lock(&mnt_id_lock);
ida_remove(&mnt_id_ida, id);
if (mnt_id_start > id)
mnt_id_start = id;
spin_unlock(&mnt_id_lock);
}
| 45,580,188,478,194,920,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,732 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static unsigned int mnt_get_writers(struct mount *mnt)
{
#ifdef CONFIG_SMP
unsigned int count = 0;
int cpu;
for_each_possible_cpu(cpu) {
count += per_cpu_ptr(mnt->mnt_pcp, cpu)->mnt_writers;
}
return count;
#else
return mnt->mnt_writers;
#endif
}
| 223,810,007,820,238,330,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,733 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static inline void mnt_inc_writers(struct mount *mnt)
{
#ifdef CONFIG_SMP
this_cpu_inc(mnt->mnt_pcp->mnt_writers);
#else
mnt->mnt_writers++;
#endif
}
| 13,350,662,442,145,713,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,734 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | void __init mnt_init(void)
{
unsigned u;
int err;
init_rwsem(&namespace_sem);
mnt_cache = kmem_cache_create("mnt_cache", sizeof(struct mount),
0, SLAB_HWCACHE_ALIGN | SLAB_PANIC, NULL);
mount_hashtable = (struct list_head *)__get_free_page(GFP_ATOMIC);
if (!mount_hashtable)
panic("Failed to allocate moun... | 58,441,663,974,321,150,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,735 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static int mnt_is_readonly(struct vfsmount *mnt)
{
if (mnt->mnt_sb->s_readonly_remount)
return 1;
/* Order wrt setting s_flags/s_readonly_remount in do_remount() */
smp_rmb();
return __mnt_is_readonly(mnt);
}
| 23,374,278,569,916,574,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,736 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static int mnt_make_readonly(struct mount *mnt)
{
int ret = 0;
br_write_lock(&vfsmount_lock);
mnt->mnt.mnt_flags |= MNT_WRITE_HOLD;
/*
* After storing MNT_WRITE_HOLD, we'll read the counters. This store
* should be visible before we do.
*/
smp_mb();
/*
* With writers on hold, if this value is zero, then... | 226,264,392,996,458,730,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
33,737 | linux | 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 | vfs: Carefully propogate mounts across user namespaces
As a matter of policy MNT_READONLY should not be changable if the
original mounter had more privileges than creator of the mount
namespace.
Add the flag CL_UNPRIVILEGED to note when we are copying a mount from
a mount namespace that requires more privileges to a ... | 0 | static bool mnt_ns_loop(struct path *path)
{
/* Could bind mounting the mount namespace inode cause a
* mount namespace loop?
*/
struct inode *inode = path->dentry->d_inode;
struct proc_inode *ei;
struct mnt_namespace *mnt_ns;
if (!proc_ns_inode(inode))
return false;
ei = PROC_I(inode);
if (ei->ns_ops !=... | 101,295,441,471,630,500,000,000,000,000,000,000,000 | namespace.c | 303,832,579,392,698,380,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-1957 | The clone_mnt function in fs/namespace.c in the Linux kernel before 3.8.6 does not properly restrict changes to the MNT_READONLY flag, which allows local users to bypass an intended read-only property of a filesystem by leveraging a separate mount namespace. | https://nvd.nist.gov/vuln/detail/CVE-2013-1957 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.