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,738 | 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_pin(struct vfsmount *mnt)
{
br_write_lock(&vfsmount_lock);
real_mount(mnt)->mnt_pinned++;
br_write_unlock(&vfsmount_lock);
}
| 272,209,935,707,669,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,739 | 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_release_group_id(struct mount *mnt)
{
int id = mnt->mnt_group_id;
ida_remove(&mnt_group_ida, id);
if (mnt_group_start > id)
mnt_group_start = id;
mnt->mnt_group_id = 0;
}
| 317,894,250,775,869,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,740 | 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_set_expiry(struct vfsmount *mnt, struct list_head *expiry_list)
{
down_write(&namespace_sem);
br_write_lock(&vfsmount_lock);
list_add_tail(&real_mount(mnt)->mnt_expire, expiry_list);
br_write_unlock(&vfsmount_lock);
up_write(&namespace_sem);
}
| 286,351,221,978,039,470,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,741 | 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_unpin(struct vfsmount *m)
{
struct mount *mnt = real_mount(m);
br_write_lock(&vfsmount_lock);
if (mnt->mnt_pinned) {
mnt_add_count(mnt, 1);
mnt->mnt_pinned--;
}
br_write_unlock(&vfsmount_lock);
}
| 62,189,303,765,707,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,742 | 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)
{
int ret;
sb_start_write(m->mnt_sb);
ret = __mnt_want_write(m);
if (ret)
sb_end_write(m->mnt_sb);
return ret;
}
| 51,076,588,737,920,635,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,743 | 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)
{
int ret;
sb_start_write(file->f_path.mnt->mnt_sb);
ret = __mnt_want_write_file(file);
if (ret)
sb_end_write(file->f_path.mnt->mnt_sb);
return ret;
}
| 4,478,046,012,360,819,500,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,744 | 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 *mntget(struct vfsmount *mnt)
{
if (mnt)
mnt_add_count(real_mount(mnt), 1);
return mnt;
}
| 117,189,612,336,508,470,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,745 | 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 *mntns_get(struct task_struct *task)
{
struct mnt_namespace *ns = NULL;
struct nsproxy *nsproxy;
rcu_read_lock();
nsproxy = task_nsproxy(task);
if (nsproxy) {
ns = nsproxy->mnt_ns;
get_mnt_ns(ns);
}
rcu_read_unlock();
return ns;
}
| 340,012,197,360,680,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,746 | 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 mntns_install(struct nsproxy *nsproxy, void *ns)
{
struct fs_struct *fs = current->fs;
struct mnt_namespace *mnt_ns = ns;
struct path root;
if (!ns_capable(mnt_ns->user_ns, CAP_SYS_ADMIN) ||
!nsown_capable(CAP_SYS_CHROOT) ||
!nsown_capable(CAP_SYS_ADMIN))
return -EPERM;
if (fs->users != 1)... | 234,293,968,544,571,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,747 | 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 mntns_inum(void *ns)
{
struct mnt_namespace *mnt_ns = ns;
return mnt_ns->proc_inum;
}
| 7,924,108,731,779,983,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,748 | 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 mntns_put(void *ns)
{
put_mnt_ns(ns);
}
| 314,199,529,218,470,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,749 | 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 mntput(struct vfsmount *mnt)
{
if (mnt) {
struct mount *m = real_mount(mnt);
/* avoid cacheline pingpong, hope gcc doesn't get "smart" */
if (unlikely(m->mnt_expiry_mark))
m->mnt_expiry_mark = 0;
mntput_no_expire(m);
}
}
| 154,844,064,985,965,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,750 | 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 mntput_no_expire(struct mount *mnt)
{
put_again:
#ifdef CONFIG_SMP
br_read_lock(&vfsmount_lock);
if (likely(mnt->mnt_ns)) {
/* shouldn't be the last one */
mnt_add_count(mnt, -1);
br_read_unlock(&vfsmount_lock);
return;
}
br_read_unlock(&vfsmount_lock);
br_write_lock(&vfsmount_lock);
mnt_add_... | 105,788,169,100,167,770,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,751 | 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 dentry *mount_subtree(struct vfsmount *mnt, const char *name)
{
struct mnt_namespace *ns;
struct super_block *s;
struct path path;
int err;
ns = create_mnt_ns(mnt);
if (IS_ERR(ns))
return ERR_CAST(ns);
err = vfs_path_lookup(mnt->mnt_root, mnt,
name, LOOKUP_FOLLOW|LOOKUP_AUTOMOUNT, &path);
put_mnt... | 64,149,066,323,696,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,752 | 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 *next_mnt(struct mount *p, struct mount *root)
{
struct list_head *next = p->mnt_mounts.next;
if (next == &p->mnt_mounts) {
while (1) {
if (p == root)
return NULL;
next = p->mnt_child.next;
if (next != &p->mnt_parent->mnt_mounts)
break;
p = p->mnt_parent;
}
}
return list_... | 1,851,414,244,918,128,300,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,753 | 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 our_mnt(struct vfsmount *mnt)
{
return check_mnt(real_mount(mnt));
}
| 5,187,507,087,354,423,400,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,754 | 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 path_is_under(struct path *path1, struct path *path2)
{
int res;
br_read_lock(&vfsmount_lock);
res = is_path_reachable(real_mount(path1->mnt), path1->dentry, path2);
br_read_unlock(&vfsmount_lock);
return res;
}
| 289,847,151,862,299,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,755 | 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 put_mnt_ns(struct mnt_namespace *ns)
{
LIST_HEAD(umount_list);
if (!atomic_dec_and_test(&ns->count))
return;
down_write(&namespace_sem);
br_write_lock(&vfsmount_lock);
umount_tree(ns->root, 0, &umount_list);
br_write_unlock(&vfsmount_lock);
up_write(&namespace_sem);
release_mounts(&umount_list);
free_m... | 104,476,819,481,983,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,756 | 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 release_mounts(struct list_head *head)
{
struct mount *mnt;
while (!list_empty(head)) {
mnt = list_first_entry(head, struct mount, mnt_hash);
list_del_init(&mnt->mnt_hash);
if (mnt_has_parent(mnt)) {
struct dentry *dentry;
struct mount *m;
br_write_lock(&vfsmount_lock);
dentry = mnt->mnt_mount... | 93,093,687,096,012,320,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,757 | 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 replace_mount_options(struct super_block *sb, char *options)
{
char *old = sb->s_options;
rcu_assign_pointer(sb->s_options, options);
if (old) {
synchronize_rcu();
kfree(old);
}
}
| 220,092,781,902,704,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,758 | 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 save_mount_options(struct super_block *sb, char *options)
{
BUG_ON(sb->s_options);
rcu_assign_pointer(sb->s_options, kstrdup(options, GFP_KERNEL));
}
| 32,291,842,967,164,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,759 | 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 sb_prepare_remount_readonly(struct super_block *sb)
{
struct mount *mnt;
int err = 0;
/* Racy optimization. Recheck the counter under MNT_WRITE_HOLD */
if (atomic_long_read(&sb->s_remove_count))
return -EBUSY;
br_write_lock(&vfsmount_lock);
list_for_each_entry(mnt, &sb->s_mounts, mnt_instance) {
if (!(... | 198,179,497,519,469,560,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,760 | 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 select_submounts(struct mount *parent, struct list_head *graveyard)
{
struct mount *this_parent = parent;
struct list_head *next;
int found = 0;
repeat:
next = this_parent->mnt_mounts.next;
resume:
while (next != &this_parent->mnt_mounts) {
struct list_head *tmp = next;
struct mount *mnt = list_ent... | 296,966,026,946,132,250,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,761 | 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 shrink_submounts(struct mount *mnt, struct list_head *umounts)
{
LIST_HEAD(graveyard);
struct mount *m;
/* extract submounts of 'mountpoint' from the expiration list */
while (select_submounts(mnt, &graveyard)) {
while (!list_empty(&graveyard)) {
m = list_first_entry(&graveyard, struct mount,
... | 112,499,962,131,357,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,762 | 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 *skip_mnt_tree(struct mount *p)
{
struct list_head *prev = p->mnt_mounts.prev;
while (prev != &p->mnt_mounts) {
p = list_entry(prev, struct mount, mnt_child);
prev = p->mnt_mounts.prev;
}
return p;
}
| 16,687,017,273,376,160,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,763 | 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 touch_mnt_namespace(struct mnt_namespace *ns)
{
if (ns) {
ns->event = ++event;
wake_up_interruptible(&ns->poll);
}
}
| 124,401,461,250,180,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,764 | 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 tree_contains_unbindable(struct mount *mnt)
{
struct mount *p;
for (p = mnt; p; p = next_mnt(p, mnt)) {
if (IS_MNT_UNBINDABLE(p))
return 1;
}
return 0;
}
| 266,881,706,325,951,320,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,765 | 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 umount_tree(struct mount *mnt, int propagate, struct list_head *kill)
{
LIST_HEAD(tmp_list);
struct mount *p;
for (p = mnt; p; p = next_mnt(p, mnt))
list_move(&p->mnt_hash, &tmp_list);
if (propagate)
propagate_umount(&tmp_list);
list_for_each_entry(p, &tmp_list, mnt_hash) {
list_del_init(&p->mnt_expi... | 61,970,026,494,873,680,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,766 | 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 unlock_mount(struct path *path)
{
up_write(&namespace_sem);
mutex_unlock(&path->dentry->d_inode->i_mutex);
}
| 194,001,320,696,533,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,767 | 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 | vfs_kern_mount(struct file_system_type *type, int flags, const char *name, void *data)
{
struct mount *mnt;
struct dentry *root;
if (!type)
return ERR_PTR(-ENODEV);
mnt = alloc_vfsmnt(name);
if (!mnt)
return ERR_PTR(-ENOMEM);
if (flags & MS_KERNMOUNT)
mnt->mnt.mnt_flags = MNT_INTERNAL;
root = mount_fs(... | 248,629,011,794,128,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,768 | 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 __propagate_umount(struct mount *mnt)
{
struct mount *parent = mnt->mnt_parent;
struct mount *m;
BUG_ON(parent == mnt);
for (m = propagation_next(parent, parent); m;
m = propagation_next(m, parent)) {
struct mount *child = __lookup_mnt(&m->mnt,
mnt->mnt_mountpoint, 0);
/*
* umount the ... | 329,769,268,652,409,800,000,000,000,000,000,000,000 | pnode.c | 144,197,309,928,247,370,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,769 | 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 change_mnt_propagation(struct mount *mnt, int type)
{
if (type == MS_SHARED) {
set_mnt_shared(mnt);
return;
}
do_make_slave(mnt);
if (type != MS_SLAVE) {
list_del_init(&mnt->mnt_slave);
mnt->mnt_master = NULL;
if (type == MS_UNBINDABLE)
mnt->mnt.mnt_flags |= MNT_UNBINDABLE;
else
mnt->mnt.mnt_... | 249,920,830,497,194,730,000,000,000,000,000,000,000 | pnode.c | 144,197,309,928,247,370,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,770 | 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_make_slave(struct mount *mnt)
{
struct mount *peer_mnt = mnt, *master = mnt->mnt_master;
struct mount *slave_mnt;
/*
* slave 'mnt' to a peer mount that has the
* same root dentry. If none is available then
* slave it to anything that is available.
*/
while ((peer_mnt = next_peer(peer_mnt)) !=... | 187,626,813,893,947,980,000,000,000,000,000,000,000 | pnode.c | 144,197,309,928,247,370,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,771 | 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 struct mount *first_slave(struct mount *p)
{
return list_entry(p->mnt_slave_list.next, struct mount, mnt_slave);
}
| 224,468,400,363,652,470,000,000,000,000,000,000,000 | pnode.c | 144,197,309,928,247,370,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,772 | 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 get_dominating_id(struct mount *mnt, const struct path *root)
{
struct mount *m;
for (m = mnt->mnt_master; m != NULL; m = m->mnt_master) {
struct mount *d = get_peer_under_root(m, mnt->mnt_ns, root);
if (d)
return d->mnt_group_id;
}
return 0;
}
| 128,915,022,118,470,410,000,000,000,000,000,000,000 | pnode.c | 144,197,309,928,247,370,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,773 | 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 *get_peer_under_root(struct mount *mnt,
struct mnt_namespace *ns,
const struct path *root)
{
struct mount *m = mnt;
do {
/* Check the namespace first for optimization */
if (m->mnt_ns == ns && is_path_reachable(m, m->mnt.mnt_root, root))
return m;
m = next_peer(m);
} while ... | 150,721,686,634,299,060,000,000,000,000,000,000,000 | pnode.c | 144,197,309,928,247,370,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,774 | 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 *get_source(struct mount *dest,
struct mount *last_dest,
struct mount *last_src,
int *type)
{
struct mount *p_last_src = NULL;
struct mount *p_last_dest = NULL;
while (last_dest != dest->mnt_master) {
p_last_dest = last_dest;
p_last_src = last_src;
last_dest = last_dest->mnt_ma... | 26,072,454,494,466,700,000,000,000,000,000,000,000 | pnode.c | 144,197,309,928,247,370,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,775 | 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 struct mount *next_peer(struct mount *p)
{
return list_entry(p->mnt_share.next, struct mount, mnt_share);
}
| 83,419,060,235,720,310,000,000,000,000,000,000,000 | pnode.c | 144,197,309,928,247,370,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,776 | 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 struct mount *next_slave(struct mount *p)
{
return list_entry(p->mnt_slave.next, struct mount, mnt_slave);
}
| 168,844,052,086,341,040,000,000,000,000,000,000,000 | pnode.c | 144,197,309,928,247,370,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,777 | 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 propagate_mount_busy(struct mount *mnt, int refcnt)
{
struct mount *m, *child;
struct mount *parent = mnt->mnt_parent;
int ret = 0;
if (mnt == parent)
return do_refcount_check(mnt, refcnt);
/*
* quickly check if the current mount can be unmounted.
* If not, we don't have to go checking for all other
... | 292,206,540,854,156,260,000,000,000,000,000,000,000 | pnode.c | 144,197,309,928,247,370,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,778 | 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 propagate_umount(struct list_head *list)
{
struct mount *mnt;
list_for_each_entry(mnt, list, mnt_hash)
__propagate_umount(mnt);
return 0;
}
| 312,600,519,037,369,870,000,000,000,000,000,000,000 | pnode.c | 144,197,309,928,247,370,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,779 | 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 *propagation_next(struct mount *m,
struct mount *origin)
{
/* are there any slaves of this mount? */
if (!IS_MNT_NEW(m) && !list_empty(&m->mnt_slave_list))
return first_slave(m);
while (1) {
struct mount *master = m->mnt_master;
if (master == origin->mnt_master) {
struct mount *n... | 287,845,558,814,463,600,000,000,000,000,000,000,000 | pnode.c | 144,197,309,928,247,370,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,780 | linux | 3151527ee007b73a0ebd296010f1c0454a919c7d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/3151527ee007b73a0ebd296010f1c0454a919c7d | userns: Don't allow creation if the user is chrooted
Guarantee that the policy of which files may be access that is
established by setting the root directory will not be violated
by user namespaces by verifying that the root directory points
to the root of the mount namespace at the time of user namespace
creation.
... | 0 | static int change_mount_flags(struct vfsmount *mnt, int ms_flags)
{
int error = 0;
int readonly_request = 0;
if (ms_flags & MS_RDONLY)
readonly_request = 1;
if (readonly_request == __mnt_is_readonly(mnt))
return 0;
if (readonly_request)
error = mnt_make_readonly(real_mount(mnt));
else
__mnt_unmake_reado... | 289,170,215,415,079,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-1956 | The create_user_ns function in kernel/user_namespace.c in the Linux kernel before 3.8.6 does not check whether a chroot directory exists that differs from the namespace root directory, which allows local users to bypass intended filesystem restrictions via a crafted clone system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-1956 |
33,781 | curl | 2eb8dcf26cb37f09cffe26909a646e702dbcab66 | https://github.com/curl/curl | https://github.com/bagder/curl/commit/2eb8dcf26cb37f09cffe26909a646e702dbcab66 | cookie: fix tailmatching to prevent cross-domain leakage
Cookies set for 'example.com' could accidentaly also be sent by libcurl
to the 'bexample.com' (ie with a prefix to the first domain name).
This is a security vulnerabilty, CVE-2013-1944.
Bug: http://curl.haxx.se/docs/adv_20130412.html | 0 | Curl_cookie_add(struct SessionHandle *data,
/* The 'data' pointer here may be NULL at times, and thus
must only be used very carefully for things that can deal
with data being NULL. Such as infof() and similar */
struct CookieInfo *c,
... | 152,717,550,892,313,640,000,000,000,000,000,000,000 | cookie.c | 172,533,994,898,264,380,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-1944 | The tailMatch function in cookie.c in cURL and libcurl before 7.30.0 does not properly match the path domain when sending cookies, which allows remote attackers to steal cookies via a matching suffix in the domain of a URL. | https://nvd.nist.gov/vuln/detail/CVE-2013-1944 |
33,782 | curl | 2eb8dcf26cb37f09cffe26909a646e702dbcab66 | https://github.com/curl/curl | https://github.com/bagder/curl/commit/2eb8dcf26cb37f09cffe26909a646e702dbcab66 | cookie: fix tailmatching to prevent cross-domain leakage
Cookies set for 'example.com' could accidentaly also be sent by libcurl
to the 'bexample.com' (ie with a prefix to the first domain name).
This is a security vulnerabilty, CVE-2013-1944.
Bug: http://curl.haxx.se/docs/adv_20130412.html | 0 | void Curl_cookie_cleanup(struct CookieInfo *c)
{
struct Cookie *co;
struct Cookie *next;
if(c) {
if(c->filename)
free(c->filename);
co = c->cookies;
while(co) {
next = co->next;
freecookie(co);
co = next;
}
free(c); /* free the base struct as well */
}
}
| 290,170,016,485,075,700,000,000,000,000,000,000,000 | cookie.c | 172,533,994,898,264,380,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-1944 | The tailMatch function in cookie.c in cURL and libcurl before 7.30.0 does not properly match the path domain when sending cookies, which allows remote attackers to steal cookies via a matching suffix in the domain of a URL. | https://nvd.nist.gov/vuln/detail/CVE-2013-1944 |
33,783 | curl | 2eb8dcf26cb37f09cffe26909a646e702dbcab66 | https://github.com/curl/curl | https://github.com/bagder/curl/commit/2eb8dcf26cb37f09cffe26909a646e702dbcab66 | cookie: fix tailmatching to prevent cross-domain leakage
Cookies set for 'example.com' could accidentaly also be sent by libcurl
to the 'bexample.com' (ie with a prefix to the first domain name).
This is a security vulnerabilty, CVE-2013-1944.
Bug: http://curl.haxx.se/docs/adv_20130412.html | 0 | void Curl_cookie_clearall(struct CookieInfo *cookies)
{
if(cookies) {
Curl_cookie_freelist(cookies->cookies, TRUE);
cookies->cookies = NULL;
cookies->numcookies = 0;
}
}
| 310,058,918,841,306,600,000,000,000,000,000,000,000 | cookie.c | 44,707,159,199,394,280,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-1944 | The tailMatch function in cookie.c in cURL and libcurl before 7.30.0 does not properly match the path domain when sending cookies, which allows remote attackers to steal cookies via a matching suffix in the domain of a URL. | https://nvd.nist.gov/vuln/detail/CVE-2013-1944 |
33,784 | curl | 2eb8dcf26cb37f09cffe26909a646e702dbcab66 | https://github.com/curl/curl | https://github.com/bagder/curl/commit/2eb8dcf26cb37f09cffe26909a646e702dbcab66 | cookie: fix tailmatching to prevent cross-domain leakage
Cookies set for 'example.com' could accidentaly also be sent by libcurl
to the 'bexample.com' (ie with a prefix to the first domain name).
This is a security vulnerabilty, CVE-2013-1944.
Bug: http://curl.haxx.se/docs/adv_20130412.html | 0 | void Curl_cookie_clearsess(struct CookieInfo *cookies)
{
struct Cookie *first, *curr, *next, *prev = NULL;
if(!cookies || !cookies->cookies)
return;
first = curr = prev = cookies->cookies;
for(; curr; curr = next) {
next = curr->next;
if(!curr->expires) {
if(first == curr)
first = n... | 218,368,549,288,004,440,000,000,000,000,000,000,000 | cookie.c | 44,707,159,199,394,280,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-1944 | The tailMatch function in cookie.c in cURL and libcurl before 7.30.0 does not properly match the path domain when sending cookies, which allows remote attackers to steal cookies via a matching suffix in the domain of a URL. | https://nvd.nist.gov/vuln/detail/CVE-2013-1944 |
33,785 | curl | 2eb8dcf26cb37f09cffe26909a646e702dbcab66 | https://github.com/curl/curl | https://github.com/bagder/curl/commit/2eb8dcf26cb37f09cffe26909a646e702dbcab66 | cookie: fix tailmatching to prevent cross-domain leakage
Cookies set for 'example.com' could accidentaly also be sent by libcurl
to the 'bexample.com' (ie with a prefix to the first domain name).
This is a security vulnerabilty, CVE-2013-1944.
Bug: http://curl.haxx.se/docs/adv_20130412.html | 0 | void Curl_cookie_freelist(struct Cookie *co, bool cookiestoo)
{
struct Cookie *next;
if(co) {
while(co) {
next = co->next;
if(cookiestoo)
freecookie(co);
else
free(co); /* we only free the struct since the "members" are all just
pointed out in the main cook... | 283,072,372,228,715,700,000,000,000,000,000,000,000 | cookie.c | 172,533,994,898,264,380,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-1944 | The tailMatch function in cookie.c in cURL and libcurl before 7.30.0 does not properly match the path domain when sending cookies, which allows remote attackers to steal cookies via a matching suffix in the domain of a URL. | https://nvd.nist.gov/vuln/detail/CVE-2013-1944 |
33,786 | curl | 2eb8dcf26cb37f09cffe26909a646e702dbcab66 | https://github.com/curl/curl | https://github.com/bagder/curl/commit/2eb8dcf26cb37f09cffe26909a646e702dbcab66 | cookie: fix tailmatching to prevent cross-domain leakage
Cookies set for 'example.com' could accidentaly also be sent by libcurl
to the 'bexample.com' (ie with a prefix to the first domain name).
This is a security vulnerabilty, CVE-2013-1944.
Bug: http://curl.haxx.se/docs/adv_20130412.html | 0 | struct Cookie *Curl_cookie_getlist(struct CookieInfo *c,
const char *host, const char *path,
bool secure)
{
struct Cookie *newco;
struct Cookie *co;
time_t now = time(NULL);
struct Cookie *mainco=NULL;
size_t matches = 0;
if(!c || !c->co... | 207,288,199,131,599,930,000,000,000,000,000,000,000 | cookie.c | 172,533,994,898,264,380,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-1944 | The tailMatch function in cookie.c in cURL and libcurl before 7.30.0 does not properly match the path domain when sending cookies, which allows remote attackers to steal cookies via a matching suffix in the domain of a URL. | https://nvd.nist.gov/vuln/detail/CVE-2013-1944 |
33,787 | curl | 2eb8dcf26cb37f09cffe26909a646e702dbcab66 | https://github.com/curl/curl | https://github.com/bagder/curl/commit/2eb8dcf26cb37f09cffe26909a646e702dbcab66 | cookie: fix tailmatching to prevent cross-domain leakage
Cookies set for 'example.com' could accidentaly also be sent by libcurl
to the 'bexample.com' (ie with a prefix to the first domain name).
This is a security vulnerabilty, CVE-2013-1944.
Bug: http://curl.haxx.se/docs/adv_20130412.html | 0 | struct CookieInfo *Curl_cookie_init(struct SessionHandle *data,
const char *file,
struct CookieInfo *inc,
bool newsession)
{
struct CookieInfo *c;
FILE *fp;
bool fromfile=TRUE;
if(NULL == inc) {
/* w... | 208,986,064,508,898,270,000,000,000,000,000,000,000 | cookie.c | 172,533,994,898,264,380,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-1944 | The tailMatch function in cookie.c in cURL and libcurl before 7.30.0 does not properly match the path domain when sending cookies, which allows remote attackers to steal cookies via a matching suffix in the domain of a URL. | https://nvd.nist.gov/vuln/detail/CVE-2013-1944 |
33,788 | curl | 2eb8dcf26cb37f09cffe26909a646e702dbcab66 | https://github.com/curl/curl | https://github.com/bagder/curl/commit/2eb8dcf26cb37f09cffe26909a646e702dbcab66 | cookie: fix tailmatching to prevent cross-domain leakage
Cookies set for 'example.com' could accidentaly also be sent by libcurl
to the 'bexample.com' (ie with a prefix to the first domain name).
This is a security vulnerabilty, CVE-2013-1944.
Bug: http://curl.haxx.se/docs/adv_20130412.html | 0 | struct curl_slist *Curl_cookie_list(struct SessionHandle *data)
{
struct curl_slist *list = NULL;
struct curl_slist *beg;
struct Cookie *c;
char *line;
if((data->cookies == NULL) ||
(data->cookies->numcookies == 0))
return NULL;
c = data->cookies->cookies;
while(c) {
/* fill the list with... | 258,233,719,085,335,560,000,000,000,000,000,000,000 | cookie.c | 172,533,994,898,264,380,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-1944 | The tailMatch function in cookie.c in cURL and libcurl before 7.30.0 does not properly match the path domain when sending cookies, which allows remote attackers to steal cookies via a matching suffix in the domain of a URL. | https://nvd.nist.gov/vuln/detail/CVE-2013-1944 |
33,789 | curl | 2eb8dcf26cb37f09cffe26909a646e702dbcab66 | https://github.com/curl/curl | https://github.com/bagder/curl/commit/2eb8dcf26cb37f09cffe26909a646e702dbcab66 | cookie: fix tailmatching to prevent cross-domain leakage
Cookies set for 'example.com' could accidentaly also be sent by libcurl
to the 'bexample.com' (ie with a prefix to the first domain name).
This is a security vulnerabilty, CVE-2013-1944.
Bug: http://curl.haxx.se/docs/adv_20130412.html | 0 | void Curl_flush_cookies(struct SessionHandle *data, int cleanup)
{
if(data->set.str[STRING_COOKIEJAR]) {
if(data->change.cookielist) {
/* If there is a list of cookie files to read, do it first so that
we have all the told files read before we write the new jar.
Curl_cookie_loadfiles() LOC... | 292,352,264,229,674,000,000,000,000,000,000,000,000 | cookie.c | 44,707,159,199,394,280,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-1944 | The tailMatch function in cookie.c in cURL and libcurl before 7.30.0 does not properly match the path domain when sending cookies, which allows remote attackers to steal cookies via a matching suffix in the domain of a URL. | https://nvd.nist.gov/vuln/detail/CVE-2013-1944 |
33,790 | curl | 2eb8dcf26cb37f09cffe26909a646e702dbcab66 | https://github.com/curl/curl | https://github.com/bagder/curl/commit/2eb8dcf26cb37f09cffe26909a646e702dbcab66 | cookie: fix tailmatching to prevent cross-domain leakage
Cookies set for 'example.com' could accidentaly also be sent by libcurl
to the 'bexample.com' (ie with a prefix to the first domain name).
This is a security vulnerabilty, CVE-2013-1944.
Bug: http://curl.haxx.se/docs/adv_20130412.html | 0 | static int cookie_output(struct CookieInfo *c, const char *dumphere)
{
struct Cookie *co;
FILE *out;
bool use_stdout=FALSE;
if((NULL == c) || (0 == c->numcookies))
/* If there are no known cookies, we don't write or even create any
destination file */
return 0;
if(strequal("-", dumphere)) {
... | 256,300,340,728,824,080,000,000,000,000,000,000,000 | cookie.c | 172,533,994,898,264,380,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-1944 | The tailMatch function in cookie.c in cURL and libcurl before 7.30.0 does not properly match the path domain when sending cookies, which allows remote attackers to steal cookies via a matching suffix in the domain of a URL. | https://nvd.nist.gov/vuln/detail/CVE-2013-1944 |
33,791 | curl | 2eb8dcf26cb37f09cffe26909a646e702dbcab66 | https://github.com/curl/curl | https://github.com/bagder/curl/commit/2eb8dcf26cb37f09cffe26909a646e702dbcab66 | cookie: fix tailmatching to prevent cross-domain leakage
Cookies set for 'example.com' could accidentaly also be sent by libcurl
to the 'bexample.com' (ie with a prefix to the first domain name).
This is a security vulnerabilty, CVE-2013-1944.
Bug: http://curl.haxx.se/docs/adv_20130412.html | 0 | static int cookie_sort(const void *p1, const void *p2)
{
struct Cookie *c1 = *(struct Cookie **)p1;
struct Cookie *c2 = *(struct Cookie **)p2;
size_t l1, l2;
/* 1 - compare cookie path lengths */
l1 = c1->path ? strlen(c1->path) : 0;
l2 = c2->path ? strlen(c2->path) : 0;
if(l1 != l2)
return (l2 > l1... | 70,233,655,286,596,160,000,000,000,000,000,000,000 | cookie.c | 44,707,159,199,394,280,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-1944 | The tailMatch function in cookie.c in cURL and libcurl before 7.30.0 does not properly match the path domain when sending cookies, which allows remote attackers to steal cookies via a matching suffix in the domain of a URL. | https://nvd.nist.gov/vuln/detail/CVE-2013-1944 |
33,792 | curl | 2eb8dcf26cb37f09cffe26909a646e702dbcab66 | https://github.com/curl/curl | https://github.com/bagder/curl/commit/2eb8dcf26cb37f09cffe26909a646e702dbcab66 | cookie: fix tailmatching to prevent cross-domain leakage
Cookies set for 'example.com' could accidentaly also be sent by libcurl
to the 'bexample.com' (ie with a prefix to the first domain name).
This is a security vulnerabilty, CVE-2013-1944.
Bug: http://curl.haxx.se/docs/adv_20130412.html | 0 | static char *get_netscape_format(const struct Cookie *co)
{
return aprintf(
"%s" /* httponly preamble */
"%s%s\t" /* domain */
"%s\t" /* tailmatch */
"%s\t" /* path */
"%s\t" /* secure */
"%" FORMAT_OFF_T "\t" /* expires */
"%s\t" /* name */
"%s", /* value */
co->h... | 158,996,562,322,567,170,000,000,000,000,000,000,000 | cookie.c | 172,533,994,898,264,380,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-1944 | The tailMatch function in cookie.c in cURL and libcurl before 7.30.0 does not properly match the path domain when sending cookies, which allows remote attackers to steal cookies via a matching suffix in the domain of a URL. | https://nvd.nist.gov/vuln/detail/CVE-2013-1944 |
33,793 | curl | 2eb8dcf26cb37f09cffe26909a646e702dbcab66 | https://github.com/curl/curl | https://github.com/bagder/curl/commit/2eb8dcf26cb37f09cffe26909a646e702dbcab66 | cookie: fix tailmatching to prevent cross-domain leakage
Cookies set for 'example.com' could accidentaly also be sent by libcurl
to the 'bexample.com' (ie with a prefix to the first domain name).
This is a security vulnerabilty, CVE-2013-1944.
Bug: http://curl.haxx.se/docs/adv_20130412.html | 0 | static void strstore(char **str, const char *newstr)
{
if(*str)
free(*str);
*str = strdup(newstr);
}
| 219,722,665,191,120,660,000,000,000,000,000,000,000 | cookie.c | 172,533,994,898,264,380,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-1944 | The tailMatch function in cookie.c in cURL and libcurl before 7.30.0 does not properly match the path domain when sending cookies, which allows remote attackers to steal cookies via a matching suffix in the domain of a URL. | https://nvd.nist.gov/vuln/detail/CVE-2013-1944 |
33,794 | linux | fa3d315a4ce2c0891cdde262562e710d95fba19e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fa3d315a4ce2c0891cdde262562e710d95fba19e | KVM: Validate userspace_addr of memslot when registered
This way, we can avoid checking the user space address many times when
we read the guest memory.
Although we can do the same for write if we check which slots are
writable, we do not care write now: reading the guest memory happens
more often than writing.
[avi... | 0 | static struct kvm_memory_slot *__gfn_to_memslot(struct kvm_memslots *slots,
gfn_t gfn)
{
int i;
for (i = 0; i < slots->nmemslots; ++i) {
struct kvm_memory_slot *memslot = &slots->memslots[i];
if (gfn >= memslot->base_gfn
&& gfn < memslot->base_gfn + memslot->npages)
return memslot;
}
return NUL... | 81,071,792,638,432,860,000,000,000,000,000,000,000 | kvm_main.c | 85,104,854,010,246,830,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-1943 | The KVM subsystem in the Linux kernel before 3.0 does not check whether kernel addresses are specified during allocation of memory slots for use in a guest's physical address space, which allows local users to gain privileges or obtain sensitive information from kernel memory via a crafted application, related to arch/... | https://nvd.nist.gov/vuln/detail/CVE-2013-1943 |
33,795 | linux | fa3d315a4ce2c0891cdde262562e710d95fba19e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fa3d315a4ce2c0891cdde262562e710d95fba19e | KVM: Validate userspace_addr of memslot when registered
This way, we can avoid checking the user space address many times when
we read the guest memory.
Although we can do the same for write if we check which slots are
writable, we do not care write now: reading the guest memory happens
more often than writing.
[avi... | 0 | static int kvm_create_dirty_bitmap(struct kvm_memory_slot *memslot)
{
unsigned long dirty_bytes = 2 * kvm_dirty_bitmap_bytes(memslot);
if (dirty_bytes > PAGE_SIZE)
memslot->dirty_bitmap = vzalloc(dirty_bytes);
else
memslot->dirty_bitmap = kzalloc(dirty_bytes, GFP_KERNEL);
if (!memslot->dirty_bitmap)
return ... | 319,140,887,399,313,500,000,000,000,000,000,000,000 | kvm_main.c | 85,104,854,010,246,830,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-1943 | The KVM subsystem in the Linux kernel before 3.0 does not check whether kernel addresses are specified during allocation of memory slots for use in a guest's physical address space, which allows local users to gain privileges or obtain sensitive information from kernel memory via a crafted application, related to arch/... | https://nvd.nist.gov/vuln/detail/CVE-2013-1943 |
33,796 | linux | fa3d315a4ce2c0891cdde262562e710d95fba19e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fa3d315a4ce2c0891cdde262562e710d95fba19e | KVM: Validate userspace_addr of memslot when registered
This way, we can avoid checking the user space address many times when
we read the guest memory.
Although we can do the same for write if we check which slots are
writable, we do not care write now: reading the guest memory happens
more often than writing.
[avi... | 0 | void kvm_free_physmem(struct kvm *kvm)
{
int i;
struct kvm_memslots *slots = kvm->memslots;
for (i = 0; i < slots->nmemslots; ++i)
kvm_free_physmem_slot(&slots->memslots[i], NULL);
kfree(kvm->memslots);
}
| 160,223,952,570,975,370,000,000,000,000,000,000,000 | kvm_main.c | 85,104,854,010,246,830,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-1943 | The KVM subsystem in the Linux kernel before 3.0 does not check whether kernel addresses are specified during allocation of memory slots for use in a guest's physical address space, which allows local users to gain privileges or obtain sensitive information from kernel memory via a crafted application, related to arch/... | https://nvd.nist.gov/vuln/detail/CVE-2013-1943 |
33,797 | linux | fa3d315a4ce2c0891cdde262562e710d95fba19e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fa3d315a4ce2c0891cdde262562e710d95fba19e | KVM: Validate userspace_addr of memslot when registered
This way, we can avoid checking the user space address many times when
we read the guest memory.
Although we can do the same for write if we check which slots are
writable, we do not care write now: reading the guest memory happens
more often than writing.
[avi... | 0 | int kvm_init(void *opaque, unsigned vcpu_size, unsigned vcpu_align,
struct module *module)
{
int r;
int cpu;
r = kvm_arch_init(opaque);
if (r)
goto out_fail;
bad_page = alloc_page(GFP_KERNEL | __GFP_ZERO);
if (bad_page == NULL) {
r = -ENOMEM;
goto out;
}
bad_pfn = page_to_pfn(bad_page);
hwpoison... | 205,518,016,660,706,020,000,000,000,000,000,000,000 | kvm_main.c | 85,104,854,010,246,830,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-1943 | The KVM subsystem in the Linux kernel before 3.0 does not check whether kernel addresses are specified during allocation of memory slots for use in a guest's physical address space, which allows local users to gain privileges or obtain sensitive information from kernel memory via a crafted application, related to arch/... | https://nvd.nist.gov/vuln/detail/CVE-2013-1943 |
33,798 | linux | fa3d315a4ce2c0891cdde262562e710d95fba19e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fa3d315a4ce2c0891cdde262562e710d95fba19e | KVM: Validate userspace_addr of memslot when registered
This way, we can avoid checking the user space address many times when
we read the guest memory.
Although we can do the same for write if we check which slots are
writable, we do not care write now: reading the guest memory happens
more often than writing.
[avi... | 0 | static void kvm_init_debug(void)
{
struct kvm_stats_debugfs_item *p;
kvm_debugfs_dir = debugfs_create_dir("kvm", NULL);
for (p = debugfs_entries; p->name; ++p)
p->dentry = debugfs_create_file(p->name, 0444, kvm_debugfs_dir,
(void *)(long)p->offset,
stat_fops[p->kind]);
}
| 68,954,295,285,923,810,000,000,000,000,000,000,000 | kvm_main.c | 85,104,854,010,246,830,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-1943 | The KVM subsystem in the Linux kernel before 3.0 does not check whether kernel addresses are specified during allocation of memory slots for use in a guest's physical address space, which allows local users to gain privileges or obtain sensitive information from kernel memory via a crafted application, related to arch/... | https://nvd.nist.gov/vuln/detail/CVE-2013-1943 |
33,799 | linux | fa3d315a4ce2c0891cdde262562e710d95fba19e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fa3d315a4ce2c0891cdde262562e710d95fba19e | KVM: Validate userspace_addr of memslot when registered
This way, we can avoid checking the user space address many times when
we read the guest memory.
Although we can do the same for write if we check which slots are
writable, we do not care write now: reading the guest memory happens
more often than writing.
[avi... | 0 | static void kvm_io_bus_destroy(struct kvm_io_bus *bus)
{
int i;
for (i = 0; i < bus->dev_count; i++) {
struct kvm_io_device *pos = bus->devs[i];
kvm_iodevice_destructor(pos);
}
kfree(bus);
}
| 318,174,538,739,056,400,000,000,000,000,000,000,000 | kvm_main.c | 85,104,854,010,246,830,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-1943 | The KVM subsystem in the Linux kernel before 3.0 does not check whether kernel addresses are specified during allocation of memory slots for use in a guest's physical address space, which allows local users to gain privileges or obtain sensitive information from kernel memory via a crafted application, related to arch/... | https://nvd.nist.gov/vuln/detail/CVE-2013-1943 |
33,800 | linux | fa3d315a4ce2c0891cdde262562e710d95fba19e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fa3d315a4ce2c0891cdde262562e710d95fba19e | KVM: Validate userspace_addr of memslot when registered
This way, we can avoid checking the user space address many times when
we read the guest memory.
Although we can do the same for write if we check which slots are
writable, we do not care write now: reading the guest memory happens
more often than writing.
[avi... | 0 | int kvm_io_bus_read(struct kvm *kvm, enum kvm_bus bus_idx, gpa_t addr,
int len, void *val)
{
int i;
struct kvm_io_bus *bus;
bus = srcu_dereference(kvm->buses[bus_idx], &kvm->srcu);
for (i = 0; i < bus->dev_count; i++)
if (!kvm_iodevice_read(bus->devs[i], addr, len, val))
return 0;
return -EOPNOTSUPP;
}... | 118,586,045,997,920,550,000,000,000,000,000,000,000 | kvm_main.c | 85,104,854,010,246,830,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-1943 | The KVM subsystem in the Linux kernel before 3.0 does not check whether kernel addresses are specified during allocation of memory slots for use in a guest's physical address space, which allows local users to gain privileges or obtain sensitive information from kernel memory via a crafted application, related to arch/... | https://nvd.nist.gov/vuln/detail/CVE-2013-1943 |
33,801 | linux | fa3d315a4ce2c0891cdde262562e710d95fba19e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fa3d315a4ce2c0891cdde262562e710d95fba19e | KVM: Validate userspace_addr of memslot when registered
This way, we can avoid checking the user space address many times when
we read the guest memory.
Although we can do the same for write if we check which slots are
writable, we do not care write now: reading the guest memory happens
more often than writing.
[avi... | 0 | int kvm_io_bus_register_dev(struct kvm *kvm, enum kvm_bus bus_idx,
struct kvm_io_device *dev)
{
struct kvm_io_bus *new_bus, *bus;
bus = kvm->buses[bus_idx];
if (bus->dev_count > NR_IOBUS_DEVS-1)
return -ENOSPC;
new_bus = kzalloc(sizeof(struct kvm_io_bus), GFP_KERNEL);
if (!new_bus)
return -ENOMEM;
me... | 293,872,068,679,652,160,000,000,000,000,000,000,000 | kvm_main.c | 85,104,854,010,246,830,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-1943 | The KVM subsystem in the Linux kernel before 3.0 does not check whether kernel addresses are specified during allocation of memory slots for use in a guest's physical address space, which allows local users to gain privileges or obtain sensitive information from kernel memory via a crafted application, related to arch/... | https://nvd.nist.gov/vuln/detail/CVE-2013-1943 |
33,802 | linux | fa3d315a4ce2c0891cdde262562e710d95fba19e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fa3d315a4ce2c0891cdde262562e710d95fba19e | KVM: Validate userspace_addr of memslot when registered
This way, we can avoid checking the user space address many times when
we read the guest memory.
Although we can do the same for write if we check which slots are
writable, we do not care write now: reading the guest memory happens
more often than writing.
[avi... | 0 | int kvm_io_bus_write(struct kvm *kvm, enum kvm_bus bus_idx, gpa_t addr,
int len, const void *val)
{
int i;
struct kvm_io_bus *bus;
bus = srcu_dereference(kvm->buses[bus_idx], &kvm->srcu);
for (i = 0; i < bus->dev_count; i++)
if (!kvm_iodevice_write(bus->devs[i], addr, len, val))
return 0;
return -EOPN... | 75,927,320,266,110,570,000,000,000,000,000,000,000 | kvm_main.c | 85,104,854,010,246,830,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-1943 | The KVM subsystem in the Linux kernel before 3.0 does not check whether kernel addresses are specified during allocation of memory slots for use in a guest's physical address space, which allows local users to gain privileges or obtain sensitive information from kernel memory via a crafted application, related to arch/... | https://nvd.nist.gov/vuln/detail/CVE-2013-1943 |
33,803 | linux | fa3d315a4ce2c0891cdde262562e710d95fba19e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fa3d315a4ce2c0891cdde262562e710d95fba19e | KVM: Validate userspace_addr of memslot when registered
This way, we can avoid checking the user space address many times when
we read the guest memory.
Although we can do the same for write if we check which slots are
writable, we do not care write now: reading the guest memory happens
more often than writing.
[avi... | 0 | int kvm_is_visible_gfn(struct kvm *kvm, gfn_t gfn)
{
int i;
struct kvm_memslots *slots = kvm_memslots(kvm);
for (i = 0; i < KVM_MEMORY_SLOTS; ++i) {
struct kvm_memory_slot *memslot = &slots->memslots[i];
if (memslot->flags & KVM_MEMSLOT_INVALID)
continue;
if (gfn >= memslot->base_gfn
&& gfn < memsl... | 169,021,393,263,499,690,000,000,000,000,000,000,000 | kvm_main.c | 85,104,854,010,246,830,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-1943 | The KVM subsystem in the Linux kernel before 3.0 does not check whether kernel addresses are specified during allocation of memory slots for use in a guest's physical address space, which allows local users to gain privileges or obtain sensitive information from kernel memory via a crafted application, related to arch/... | https://nvd.nist.gov/vuln/detail/CVE-2013-1943 |
33,804 | linux | fa3d315a4ce2c0891cdde262562e710d95fba19e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fa3d315a4ce2c0891cdde262562e710d95fba19e | KVM: Validate userspace_addr of memslot when registered
This way, we can avoid checking the user space address many times when
we read the guest memory.
Although we can do the same for write if we check which slots are
writable, we do not care write now: reading the guest memory happens
more often than writing.
[avi... | 0 | static long kvm_vcpu_ioctl(struct file *filp,
unsigned int ioctl, unsigned long arg)
{
struct kvm_vcpu *vcpu = filp->private_data;
void __user *argp = (void __user *)arg;
int r;
struct kvm_fpu *fpu = NULL;
struct kvm_sregs *kvm_sregs = NULL;
if (vcpu->kvm->mm != current->mm)
return -EIO;
#if defined(CON... | 169,212,151,993,966,000,000,000,000,000,000,000,000 | kvm_main.c | 85,104,854,010,246,830,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-1943 | The KVM subsystem in the Linux kernel before 3.0 does not check whether kernel addresses are specified during allocation of memory slots for use in a guest's physical address space, which allows local users to gain privileges or obtain sensitive information from kernel memory via a crafted application, related to arch/... | https://nvd.nist.gov/vuln/detail/CVE-2013-1943 |
33,805 | linux | fa3d315a4ce2c0891cdde262562e710d95fba19e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fa3d315a4ce2c0891cdde262562e710d95fba19e | KVM: Validate userspace_addr of memslot when registered
This way, we can avoid checking the user space address many times when
we read the guest memory.
Although we can do the same for write if we check which slots are
writable, we do not care write now: reading the guest memory happens
more often than writing.
[avi... | 0 | static int kvm_vm_ioctl_create_vcpu(struct kvm *kvm, u32 id)
{
int r;
struct kvm_vcpu *vcpu, *v;
vcpu = kvm_arch_vcpu_create(kvm, id);
if (IS_ERR(vcpu))
return PTR_ERR(vcpu);
preempt_notifier_init(&vcpu->preempt_notifier, &kvm_preempt_ops);
r = kvm_arch_vcpu_setup(vcpu);
if (r)
return r;
mutex_lock(&kvm... | 304,547,520,342,110,050,000,000,000,000,000,000,000 | kvm_main.c | 85,104,854,010,246,830,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-1943 | The KVM subsystem in the Linux kernel before 3.0 does not check whether kernel addresses are specified during allocation of memory slots for use in a guest's physical address space, which allows local users to gain privileges or obtain sensitive information from kernel memory via a crafted application, related to arch/... | https://nvd.nist.gov/vuln/detail/CVE-2013-1943 |
33,806 | linux | fa3d315a4ce2c0891cdde262562e710d95fba19e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fa3d315a4ce2c0891cdde262562e710d95fba19e | KVM: Validate userspace_addr of memslot when registered
This way, we can avoid checking the user space address many times when
we read the guest memory.
Although we can do the same for write if we check which slots are
writable, we do not care write now: reading the guest memory happens
more often than writing.
[avi... | 0 | int kvm_write_guest_cached(struct kvm *kvm, struct gfn_to_hva_cache *ghc,
void *data, unsigned long len)
{
struct kvm_memslots *slots = kvm_memslots(kvm);
int r;
if (slots->generation != ghc->generation)
kvm_gfn_to_hva_cache_init(kvm, ghc, ghc->gpa);
if (kvm_is_error_hva(ghc->hva))
return -EFAULT;
r =... | 169,643,554,048,657,790,000,000,000,000,000,000,000 | kvm_main.c | 85,104,854,010,246,830,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-1943 | The KVM subsystem in the Linux kernel before 3.0 does not check whether kernel addresses are specified during allocation of memory slots for use in a guest's physical address space, which allows local users to gain privileges or obtain sensitive information from kernel memory via a crafted application, related to arch/... | https://nvd.nist.gov/vuln/detail/CVE-2013-1943 |
33,807 | linux | fa3d315a4ce2c0891cdde262562e710d95fba19e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fa3d315a4ce2c0891cdde262562e710d95fba19e | KVM: Validate userspace_addr of memslot when registered
This way, we can avoid checking the user space address many times when
we read the guest memory.
Although we can do the same for write if we check which slots are
writable, we do not care write now: reading the guest memory happens
more often than writing.
[avi... | 0 | int kvm_write_guest_page(struct kvm *kvm, gfn_t gfn, const void *data,
int offset, int len)
{
int r;
unsigned long addr;
addr = gfn_to_hva(kvm, gfn);
if (kvm_is_error_hva(addr))
return -EFAULT;
r = copy_to_user((void __user *)addr + offset, data, len);
if (r)
return -EFAULT;
mark_page_dirty(kvm, gfn);
... | 258,247,605,115,069,960,000,000,000,000,000,000,000 | kvm_main.c | 85,104,854,010,246,830,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-1943 | The KVM subsystem in the Linux kernel before 3.0 does not check whether kernel addresses are specified during allocation of memory slots for use in a guest's physical address space, which allows local users to gain privileges or obtain sensitive information from kernel memory via a crafted application, related to arch/... | https://nvd.nist.gov/vuln/detail/CVE-2013-1943 |
33,808 | linux | fa3d315a4ce2c0891cdde262562e710d95fba19e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fa3d315a4ce2c0891cdde262562e710d95fba19e | KVM: Validate userspace_addr of memslot when registered
This way, we can avoid checking the user space address many times when
we read the guest memory.
Although we can do the same for write if we check which slots are
writable, we do not care write now: reading the guest memory happens
more often than writing.
[avi... | 0 | void mark_page_dirty_in_slot(struct kvm *kvm, struct kvm_memory_slot *memslot,
gfn_t gfn)
{
if (memslot && memslot->dirty_bitmap) {
unsigned long rel_gfn = gfn - memslot->base_gfn;
__set_bit_le(rel_gfn, memslot->dirty_bitmap);
}
}
| 189,206,751,661,273,970,000,000,000,000,000,000,000 | kvm_main.c | 85,104,854,010,246,830,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-1943 | The KVM subsystem in the Linux kernel before 3.0 does not check whether kernel addresses are specified during allocation of memory slots for use in a guest's physical address space, which allows local users to gain privileges or obtain sensitive information from kernel memory via a crafted application, related to arch/... | https://nvd.nist.gov/vuln/detail/CVE-2013-1943 |
33,809 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static int __tg3_readphy(struct tg3 *tp, unsigned int phy_addr, int reg,
u32 *val)
{
u32 frame_val;
unsigned int loops;
int ret;
if ((tp->mi_mode & MAC_MI_MODE_AUTO_POLL) != 0) {
tw32_f(MAC_MI_MODE,
(tp->mi_mode & ~MAC_MI_MODE_AUTO_POLL));
udelay(80);
}
tg3_ape_lock(tp, tp->phy_ape_lock);
*val ... | 329,861,010,544,565,830,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,810 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static void __tg3_set_coalesce(struct tg3 *tp, struct ethtool_coalesce *ec)
{
tg3_coal_tx_init(tp, ec);
tg3_coal_rx_init(tp, ec);
if (!tg3_flag(tp, 5705_PLUS)) {
u32 val = ec->stats_block_coalesce_usecs;
tw32(HOSTCC_RXCOAL_TICK_INT, ec->rx_coalesce_usecs_irq);
tw32(HOSTCC_TXCOAL_TICK_INT, ec->tx_coalesce_use... | 307,868,517,376,272,000,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,811 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static void __tg3_set_rx_mode(struct net_device *dev)
{
struct tg3 *tp = netdev_priv(dev);
u32 rx_mode;
rx_mode = tp->rx_mode & ~(RX_MODE_PROMISC |
RX_MODE_KEEP_VLAN_TAG);
#if !defined(CONFIG_VLAN_8021Q) && !defined(CONFIG_VLAN_8021Q_MODULE)
/* When ASF is in use, we always keep the RX_MODE_KEEP_VLAN_TAG
... | 98,323,303,871,248,950,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,812 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static int __tg3_writephy(struct tg3 *tp, unsigned int phy_addr, int reg,
u32 val)
{
u32 frame_val;
unsigned int loops;
int ret;
if ((tp->phy_flags & TG3_PHYFLG_IS_FET) &&
(reg == MII_CTRL1000 || reg == MII_TG3_AUX_CTRL))
return 0;
if ((tp->mi_mode & MAC_MI_MODE_AUTO_POLL) != 0) {
tw32_f(MAC_MI_MOD... | 275,353,911,065,976,720,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,813 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static inline int _tg3_flag(enum TG3_FLAGS flag, unsigned long *bits)
{
return test_bit(flag, bits);
}
| 247,567,455,184,909,600,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,814 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static inline void _tg3_flag_clear(enum TG3_FLAGS flag, unsigned long *bits)
{
clear_bit(flag, bits);
}
| 2,108,782,641,618,762,600,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,815 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static inline void _tg3_flag_set(enum TG3_FLAGS flag, unsigned long *bits)
{
set_bit(flag, bits);
}
| 338,868,323,826,520,400,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,816 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static void _tw32_flush(struct tg3 *tp, u32 off, u32 val, u32 usec_wait)
{
if (tg3_flag(tp, PCIX_TARGET_HWBUG) || tg3_flag(tp, ICH_WORKAROUND))
/* Non-posted methods */
tp->write32(tp, off, val);
else {
/* Posted method */
tg3_write32(tp, off, val);
if (usec_wait)
udelay(usec_wait);
tp->read32(tp, off)... | 253,643,389,788,175,400,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,817 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static inline u32 calc_crc(unsigned char *buf, int len)
{
u32 reg;
u32 tmp;
int j, k;
reg = 0xffffffff;
for (j = 0; j < len; j++) {
reg ^= buf[j];
for (k = 0; k < 8; k++) {
tmp = reg & 0x01;
reg >>= 1;
if (tmp)
reg ^= 0xedb88320;
}
}
return ~reg;
}
| 114,683,150,003,423,900,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,818 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static inline u64 get_stat64(tg3_stat64_t *val)
{
return ((u64)val->high << 32) | ((u64)val->low);
}
| 170,217,078,982,898,600,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,819 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static bool tg3_10_100_only_device(struct tg3 *tp,
const struct pci_device_id *ent)
{
u32 grc_misc_cfg = tr32(GRC_MISC_CFG) & GRC_MISC_CFG_BOARD_ID_MASK;
if ((tg3_asic_rev(tp) == ASIC_REV_5703 &&
(grc_misc_cfg == 0x8000 || grc_misc_cfg == 0x4000)) ||
(tp->phy_flags & TG3_PHYFLG_IS_FET))
return tr... | 53,690,169,541,251,800,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,820 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static inline int tg3_40bit_overflow_test(struct tg3 *tp, dma_addr_t mapping,
int len)
{
#if defined(CONFIG_HIGHMEM) && (BITS_PER_LONG == 64)
if (tg3_flag(tp, 40BIT_DMA_BUG))
return ((u64) mapping + len) > DMA_BIT_MASK(40);
return 0;
#else
return 0;
#endif
}
| 331,245,748,959,845,200,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,821 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static inline int tg3_4g_overflow_test(dma_addr_t mapping, int len)
{
u32 base = (u32) mapping & 0xffffffff;
return (base > 0xffffdcc0) && (base + len + 8 < base);
}
| 294,096,060,903,098,020,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,822 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static int tg3_5700_link_polarity(struct tg3 *tp, u32 speed)
{
if (tp->led_ctrl == LED_CTRL_MODE_PHY_2)
return 1;
else if ((tp->phy_id & TG3_PHY_ID_MASK) == TG3_PHY_ID_BCM5411) {
if (speed != SPEED_10)
return 1;
} else if (speed == SPEED_10)
return 1;
return 0;
}
| 258,766,975,042,746,800,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,823 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static int tg3_abort_hw(struct tg3 *tp, int silent)
{
int i, err;
tg3_disable_ints(tp);
tp->rx_mode &= ~RX_MODE_ENABLE;
tw32_f(MAC_RX_MODE, tp->rx_mode);
udelay(10);
err = tg3_stop_block(tp, RCVBDI_MODE, RCVBDI_MODE_ENABLE, silent);
err |= tg3_stop_block(tp, RCVLPC_MODE, RCVLPC_MODE_ENABLE, silent);
err |= ... | 299,708,963,104,386,700,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,824 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static void tg3_adjust_link(struct net_device *dev)
{
u8 oldflowctrl, linkmesg = 0;
u32 mac_mode, lcl_adv, rmt_adv;
struct tg3 *tp = netdev_priv(dev);
struct phy_device *phydev = tp->mdio_bus->phy_map[TG3_PHY_MII_ADDR];
spin_lock_bh(&tp->lock);
mac_mode = tp->mac_mode & ~(MAC_MODE_PORT_MODE_MASK |
MAC_M... | 179,367,933,532,695,500,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,825 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static u16 tg3_advert_flowctrl_1000X(u8 flow_ctrl)
{
u16 miireg;
if ((flow_ctrl & FLOW_CTRL_TX) && (flow_ctrl & FLOW_CTRL_RX))
miireg = ADVERTISE_1000XPAUSE;
else if (flow_ctrl & FLOW_CTRL_TX)
miireg = ADVERTISE_1000XPSE_ASYM;
else if (flow_ctrl & FLOW_CTRL_RX)
miireg = ADVERTISE_1000XPAUSE | ADVERTISE_1000X... | 306,076,086,443,298,600,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,826 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static int tg3_alloc_consistent(struct tg3 *tp)
{
int i;
tp->hw_stats = dma_alloc_coherent(&tp->pdev->dev,
sizeof(struct tg3_hw_stats),
&tp->stats_mapping,
GFP_KERNEL);
if (!tp->hw_stats)
goto err_out;
memset(tp->hw_stats, 0, sizeof(struct tg3_hw_stats));
for (i = 0; i < tp->irq_cnt; i++)... | 252,370,299,261,941,170,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,827 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static int tg3_alloc_rx_data(struct tg3 *tp, struct tg3_rx_prodring_set *tpr,
u32 opaque_key, u32 dest_idx_unmasked,
unsigned int *frag_size)
{
struct tg3_rx_buffer_desc *desc;
struct ring_info *map;
u8 *data;
dma_addr_t mapping;
int skb_size, data_size, dest_idx;
switch (opaque_key) {
case RXD_... | 22,774,308,262,367,657,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,828 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static void tg3_ape_driver_state_change(struct tg3 *tp, int kind)
{
u32 event;
u32 apedata;
if (!tg3_flag(tp, ENABLE_APE))
return;
switch (kind) {
case RESET_KIND_INIT:
tg3_ape_write32(tp, TG3_APE_HOST_SEG_SIG,
APE_HOST_SEG_SIG_MAGIC);
tg3_ape_write32(tp, TG3_APE_HOST_SEG_LEN,
APE_HOST_SEG_LEN_MAGI... | 13,123,951,491,043,340,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,829 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static int tg3_ape_event_lock(struct tg3 *tp, u32 timeout_us)
{
u32 apedata;
while (timeout_us) {
if (tg3_ape_lock(tp, TG3_APE_LOCK_MEM))
return -EBUSY;
apedata = tg3_ape_read32(tp, TG3_APE_EVENT_STATUS);
if (!(apedata & APE_EVENT_STATUS_EVENT_PENDING))
break;
tg3_ape_unlock(tp, TG3_APE_LOCK_MEM);
... | 35,064,521,903,062,347,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,830 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static int tg3_ape_lock(struct tg3 *tp, int locknum)
{
int i, off;
int ret = 0;
u32 status, req, gnt, bit;
if (!tg3_flag(tp, ENABLE_APE))
return 0;
switch (locknum) {
case TG3_APE_LOCK_GPIO:
if (tg3_asic_rev(tp) == ASIC_REV_5761)
return 0;
case TG3_APE_LOCK_GRC:
case TG3_APE_LOCK_MEM:
if (!tp->pci_fn... | 236,327,794,721,886,100,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,831 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static void tg3_ape_lock_init(struct tg3 *tp)
{
int i;
u32 regbase, bit;
if (tg3_asic_rev(tp) == ASIC_REV_5761)
regbase = TG3_APE_LOCK_GRANT;
else
regbase = TG3_APE_PER_LOCK_GRANT;
/* Make sure the driver hasn't any stale locks. */
for (i = TG3_APE_LOCK_PHY0; i <= TG3_APE_LOCK_GPIO; i++) {
switch (i) {
... | 200,546,366,549,343,340,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,832 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static int tg3_ape_otp_read(struct tg3 *tp, u32 offset, u32 *val)
{
int i, err;
u32 val2, off = offset * 8;
err = tg3_nvram_lock(tp);
if (err)
return err;
tg3_ape_write32(tp, TG3_APE_OTP_ADDR, off | APE_OTP_ADDR_CPU_ENABLE);
tg3_ape_write32(tp, TG3_APE_OTP_CTRL, APE_OTP_CTRL_PROG_EN |
APE_OTP_CTRL_CMD_RD |... | 270,004,360,019,013,550,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,833 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static int tg3_ape_send_event(struct tg3 *tp, u32 event)
{
int err;
u32 apedata;
apedata = tg3_ape_read32(tp, TG3_APE_SEG_SIG);
if (apedata != APE_SEG_SIG_MAGIC)
return -EAGAIN;
apedata = tg3_ape_read32(tp, TG3_APE_FW_STATUS);
if (!(apedata & APE_FW_STATUS_READY))
return -EAGAIN;
/* Wait for up to 1 milli... | 327,746,367,905,971,300,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,834 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static void tg3_ape_unlock(struct tg3 *tp, int locknum)
{
u32 gnt, bit;
if (!tg3_flag(tp, ENABLE_APE))
return;
switch (locknum) {
case TG3_APE_LOCK_GPIO:
if (tg3_asic_rev(tp) == ASIC_REV_5761)
return;
case TG3_APE_LOCK_GRC:
case TG3_APE_LOCK_MEM:
if (!tp->pci_fn)
bit = APE_LOCK_GRANT_DRIVER;
else
... | 134,466,037,574,485,360,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,835 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static void tg3_ape_write32(struct tg3 *tp, u32 off, u32 val)
{
writel(val, tp->aperegs + off);
}
| 292,515,406,511,946,800,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,836 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static void tg3_aux_stat_to_speed_duplex(struct tg3 *tp, u32 val, u16 *speed, u8 *duplex)
{
switch (val & MII_TG3_AUX_STAT_SPDMASK) {
case MII_TG3_AUX_STAT_10HALF:
*speed = SPEED_10;
*duplex = DUPLEX_HALF;
break;
case MII_TG3_AUX_STAT_10FULL:
*speed = SPEED_10;
*duplex = DUPLEX_FULL;
break;
case MII_T... | 227,624,398,152,705,500,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
33,837 | linux | 715230a44310a8cf66fbfb5a46f9a62a9b2de424 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/715230a44310a8cf66fbfb5a46f9a62a9b2de424 | tg3: fix length overflow in VPD firmware parsing
Commit 184b89044fb6e2a74611dafa69b1dce0d98612c6 ("tg3: Use VPD fw version
when present") introduced VPD parsing that contained a potential length
overflow.
Limit the hardware's reported firmware string length (max 255 bytes) to
stay inside the driver's firmware string ... | 0 | static int tg3_bmcr_reset(struct tg3 *tp)
{
u32 phy_control;
int limit, err;
/* OK, reset it, and poll the BMCR_RESET bit until it
* clears or we time out.
*/
phy_control = BMCR_RESET;
err = tg3_writephy(tp, MII_BMCR, phy_control);
if (err != 0)
return -EBUSY;
limit = 5000;
while (limit--) {
err = tg3... | 216,163,275,147,981,570,000,000,000,000,000,000,000 | tg3.c | 309,569,115,333,965,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-1929 | Heap-based buffer overflow in the tg3_read_vpd function in drivers/net/ethernet/broadcom/tg3.c in the Linux kernel before 3.8.6 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via crafted firmware that specifies a long string in the Vital Product Data... | https://nvd.nist.gov/vuln/detail/CVE-2013-1929 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.