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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
28,900 | linux | 1d1221f375c94ef961ba8574ac4f85c8870ddd51 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1d1221f375c94ef961ba8574ac4f85c8870ddd51 | proc: restrict access to /proc/PID/io
/proc/PID/io may be used for gathering private information. E.g. for
openssh and vsftpd daemons wchars/rchars may be used to learn the
precise password length. Restrict it to processes being able to ptrace
the target process.
ptrace_may_access() is needed to prevent keeping op... | 0 | static int proc_root_link(struct inode *inode, struct path *path)
{
struct task_struct *task = get_proc_task(inode);
int result = -ENOENT;
if (task) {
result = get_task_root(task, path);
put_task_struct(task);
}
return result;
}
| 128,413,163,246,280,890,000,000,000,000,000,000,000 | base.c | 164,068,791,576,710,960,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2495 | fs/proc/base.c in the Linux kernel before 2.6.39.4 does not properly restrict access to /proc/#####/io files, which allows local users to obtain sensitive I/O statistics by polling a file, as demonstrated by discovering the length of another user's password. | https://nvd.nist.gov/vuln/detail/CVE-2011-2495 |
28,901 | linux | 1d1221f375c94ef961ba8574ac4f85c8870ddd51 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1d1221f375c94ef961ba8574ac4f85c8870ddd51 | proc: restrict access to /proc/PID/io
/proc/PID/io may be used for gathering private information. E.g. for
openssh and vsftpd daemons wchars/rchars may be used to learn the
precise password length. Restrict it to processes being able to ptrace
the target process.
ptrace_may_access() is needed to prevent keeping op... | 0 | static void proc_self_put_link(struct dentry *dentry, struct nameidata *nd,
void *cookie)
{
char *s = nd_get_link(nd);
if (!IS_ERR(s))
__putname(s);
}
| 297,185,478,178,017,030,000,000,000,000,000,000,000 | base.c | 164,068,791,576,710,960,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2495 | fs/proc/base.c in the Linux kernel before 2.6.39.4 does not properly restrict access to /proc/#####/io files, which allows local users to obtain sensitive I/O statistics by polling a file, as demonstrated by discovering the length of another user's password. | https://nvd.nist.gov/vuln/detail/CVE-2011-2495 |
28,902 | linux | 1d1221f375c94ef961ba8574ac4f85c8870ddd51 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1d1221f375c94ef961ba8574ac4f85c8870ddd51 | proc: restrict access to /proc/PID/io
/proc/PID/io may be used for gathering private information. E.g. for
openssh and vsftpd daemons wchars/rchars may be used to learn the
precise password length. Restrict it to processes being able to ptrace
the target process.
ptrace_may_access() is needed to prevent keeping op... | 0 | static int proc_self_readlink(struct dentry *dentry, char __user *buffer,
int buflen)
{
struct pid_namespace *ns = dentry->d_sb->s_fs_info;
pid_t tgid = task_tgid_nr_ns(current, ns);
char tmp[PROC_NUMBUF];
if (!tgid)
return -ENOENT;
sprintf(tmp, "%d", tgid);
return vfs_readlink(dentry,buffer,buflen,tmp... | 51,354,347,033,077,360,000,000,000,000,000,000,000 | base.c | 97,077,772,234,708,240,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2495 | fs/proc/base.c in the Linux kernel before 2.6.39.4 does not properly restrict access to /proc/#####/io files, which allows local users to obtain sensitive I/O statistics by polling a file, as demonstrated by discovering the length of another user's password. | https://nvd.nist.gov/vuln/detail/CVE-2011-2495 |
28,903 | linux | 1d1221f375c94ef961ba8574ac4f85c8870ddd51 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1d1221f375c94ef961ba8574ac4f85c8870ddd51 | proc: restrict access to /proc/PID/io
/proc/PID/io may be used for gathering private information. E.g. for
openssh and vsftpd daemons wchars/rchars may be used to learn the
precise password length. Restrict it to processes being able to ptrace
the target process.
ptrace_may_access() is needed to prevent keeping op... | 0 | static ssize_t proc_sessionid_read(struct file * file, char __user * buf,
size_t count, loff_t *ppos)
{
struct inode * inode = file->f_path.dentry->d_inode;
struct task_struct *task = get_proc_task(inode);
ssize_t length;
char tmpbuf[TMPBUFLEN];
if (!task)
return -ESRCH;
length = scnprintf(tmpbuf, TMPBUF... | 47,658,197,566,127,510,000,000,000,000,000,000,000 | base.c | 97,077,772,234,708,240,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2495 | fs/proc/base.c in the Linux kernel before 2.6.39.4 does not properly restrict access to /proc/#####/io files, which allows local users to obtain sensitive I/O statistics by polling a file, as demonstrated by discovering the length of another user's password. | https://nvd.nist.gov/vuln/detail/CVE-2011-2495 |
28,904 | linux | 1d1221f375c94ef961ba8574ac4f85c8870ddd51 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1d1221f375c94ef961ba8574ac4f85c8870ddd51 | proc: restrict access to /proc/PID/io
/proc/PID/io may be used for gathering private information. E.g. for
openssh and vsftpd daemons wchars/rchars may be used to learn the
precise password length. Restrict it to processes being able to ptrace
the target process.
ptrace_may_access() is needed to prevent keeping op... | 0 | int proc_setattr(struct dentry *dentry, struct iattr *attr)
{
int error;
struct inode *inode = dentry->d_inode;
if (attr->ia_valid & ATTR_MODE)
return -EPERM;
error = inode_change_ok(inode, attr);
if (error)
return error;
if ((attr->ia_valid & ATTR_SIZE) &&
attr->ia_size != i_size_read(inode)) {
err... | 93,764,130,573,909,390,000,000,000,000,000,000,000 | base.c | 164,068,791,576,710,960,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2495 | fs/proc/base.c in the Linux kernel before 2.6.39.4 does not properly restrict access to /proc/#####/io files, which allows local users to obtain sensitive I/O statistics by polling a file, as demonstrated by discovering the length of another user's password. | https://nvd.nist.gov/vuln/detail/CVE-2011-2495 |
28,905 | linux | 1d1221f375c94ef961ba8574ac4f85c8870ddd51 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1d1221f375c94ef961ba8574ac4f85c8870ddd51 | proc: restrict access to /proc/PID/io
/proc/PID/io may be used for gathering private information. E.g. for
openssh and vsftpd daemons wchars/rchars may be used to learn the
precise password length. Restrict it to processes being able to ptrace
the target process.
ptrace_may_access() is needed to prevent keeping op... | 0 | static int proc_single_open(struct inode *inode, struct file *filp)
{
return single_open(filp, proc_single_show, inode);
}
| 265,636,578,146,334,200,000,000,000,000,000,000,000 | base.c | 164,068,791,576,710,960,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2495 | fs/proc/base.c in the Linux kernel before 2.6.39.4 does not properly restrict access to /proc/#####/io files, which allows local users to obtain sensitive I/O statistics by polling a file, as demonstrated by discovering the length of another user's password. | https://nvd.nist.gov/vuln/detail/CVE-2011-2495 |
28,906 | linux | 1d1221f375c94ef961ba8574ac4f85c8870ddd51 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1d1221f375c94ef961ba8574ac4f85c8870ddd51 | proc: restrict access to /proc/PID/io
/proc/PID/io may be used for gathering private information. E.g. for
openssh and vsftpd daemons wchars/rchars may be used to learn the
precise password length. Restrict it to processes being able to ptrace
the target process.
ptrace_may_access() is needed to prevent keeping op... | 0 | static int proc_task_fill_cache(struct file *filp, void *dirent, filldir_t filldir,
struct task_struct *task, int tid)
{
char name[PROC_NUMBUF];
int len = snprintf(name, sizeof(name), "%d", tid);
return proc_fill_cache(filp, dirent, filldir, name, len,
proc_task_instantiate, task, NULL);
}
| 101,182,010,251,966,030,000,000,000,000,000,000,000 | base.c | 97,077,772,234,708,240,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2495 | fs/proc/base.c in the Linux kernel before 2.6.39.4 does not properly restrict access to /proc/#####/io files, which allows local users to obtain sensitive I/O statistics by polling a file, as demonstrated by discovering the length of another user's password. | https://nvd.nist.gov/vuln/detail/CVE-2011-2495 |
28,907 | linux | 1d1221f375c94ef961ba8574ac4f85c8870ddd51 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1d1221f375c94ef961ba8574ac4f85c8870ddd51 | proc: restrict access to /proc/PID/io
/proc/PID/io may be used for gathering private information. E.g. for
openssh and vsftpd daemons wchars/rchars may be used to learn the
precise password length. Restrict it to processes being able to ptrace
the target process.
ptrace_may_access() is needed to prevent keeping op... | 0 | static int proc_task_getattr(struct vfsmount *mnt, struct dentry *dentry, struct kstat *stat)
{
struct inode *inode = dentry->d_inode;
struct task_struct *p = get_proc_task(inode);
generic_fillattr(inode, stat);
if (p) {
stat->nlink += get_nr_threads(p);
put_task_struct(p);
}
return 0;
}
| 267,621,131,581,344,470,000,000,000,000,000,000,000 | base.c | 97,077,772,234,708,240,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2495 | fs/proc/base.c in the Linux kernel before 2.6.39.4 does not properly restrict access to /proc/#####/io files, which allows local users to obtain sensitive I/O statistics by polling a file, as demonstrated by discovering the length of another user's password. | https://nvd.nist.gov/vuln/detail/CVE-2011-2495 |
28,908 | linux | 1d1221f375c94ef961ba8574ac4f85c8870ddd51 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1d1221f375c94ef961ba8574ac4f85c8870ddd51 | proc: restrict access to /proc/PID/io
/proc/PID/io may be used for gathering private information. E.g. for
openssh and vsftpd daemons wchars/rchars may be used to learn the
precise password length. Restrict it to processes being able to ptrace
the target process.
ptrace_may_access() is needed to prevent keeping op... | 0 | static struct dentry *proc_task_instantiate(struct inode *dir,
struct dentry *dentry, struct task_struct *task, const void *ptr)
{
struct dentry *error = ERR_PTR(-ENOENT);
struct inode *inode;
inode = proc_pid_make_inode(dir->i_sb, task);
if (!inode)
goto out;
inode->i_mode = S_IFDIR|S_IRUGO|S_IXUGO;
inode->i... | 226,115,713,185,550,900,000,000,000,000,000,000,000 | base.c | 164,068,791,576,710,960,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2495 | fs/proc/base.c in the Linux kernel before 2.6.39.4 does not properly restrict access to /proc/#####/io files, which allows local users to obtain sensitive I/O statistics by polling a file, as demonstrated by discovering the length of another user's password. | https://nvd.nist.gov/vuln/detail/CVE-2011-2495 |
28,909 | linux | 1d1221f375c94ef961ba8574ac4f85c8870ddd51 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1d1221f375c94ef961ba8574ac4f85c8870ddd51 | proc: restrict access to /proc/PID/io
/proc/PID/io may be used for gathering private information. E.g. for
openssh and vsftpd daemons wchars/rchars may be used to learn the
precise password length. Restrict it to processes being able to ptrace
the target process.
ptrace_may_access() is needed to prevent keeping op... | 0 | static int proc_task_readdir(struct file * filp, void * dirent, filldir_t filldir)
{
struct dentry *dentry = filp->f_path.dentry;
struct inode *inode = dentry->d_inode;
struct task_struct *leader = NULL;
struct task_struct *task;
int retval = -ENOENT;
ino_t ino;
int tid;
struct pid_namespace *ns;
task = get_p... | 8,935,384,450,525,988,000,000,000,000,000,000,000 | base.c | 97,077,772,234,708,240,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2495 | fs/proc/base.c in the Linux kernel before 2.6.39.4 does not properly restrict access to /proc/#####/io files, which allows local users to obtain sensitive I/O statistics by polling a file, as demonstrated by discovering the length of another user's password. | https://nvd.nist.gov/vuln/detail/CVE-2011-2495 |
28,910 | linux | 1d1221f375c94ef961ba8574ac4f85c8870ddd51 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1d1221f375c94ef961ba8574ac4f85c8870ddd51 | proc: restrict access to /proc/PID/io
/proc/PID/io may be used for gathering private information. E.g. for
openssh and vsftpd daemons wchars/rchars may be used to learn the
precise password length. Restrict it to processes being able to ptrace
the target process.
ptrace_may_access() is needed to prevent keeping op... | 0 | static struct dentry *proc_tgid_base_lookup(struct inode *dir, struct dentry *dentry, struct nameidata *nd){
return proc_pident_lookup(dir, dentry,
tgid_base_stuff, ARRAY_SIZE(tgid_base_stuff));
}
| 108,451,239,700,710,110,000,000,000,000,000,000,000 | base.c | 97,077,772,234,708,240,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2495 | fs/proc/base.c in the Linux kernel before 2.6.39.4 does not properly restrict access to /proc/#####/io files, which allows local users to obtain sensitive I/O statistics by polling a file, as demonstrated by discovering the length of another user's password. | https://nvd.nist.gov/vuln/detail/CVE-2011-2495 |
28,911 | linux | 1d1221f375c94ef961ba8574ac4f85c8870ddd51 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1d1221f375c94ef961ba8574ac4f85c8870ddd51 | proc: restrict access to /proc/PID/io
/proc/PID/io may be used for gathering private information. E.g. for
openssh and vsftpd daemons wchars/rchars may be used to learn the
precise password length. Restrict it to processes being able to ptrace
the target process.
ptrace_may_access() is needed to prevent keeping op... | 0 | static int proc_tgid_base_readdir(struct file * filp,
void * dirent, filldir_t filldir)
{
return proc_pident_readdir(filp,dirent,filldir,
tgid_base_stuff,ARRAY_SIZE(tgid_base_stuff));
}
| 246,435,363,651,626,340,000,000,000,000,000,000,000 | base.c | 97,077,772,234,708,240,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2495 | fs/proc/base.c in the Linux kernel before 2.6.39.4 does not properly restrict access to /proc/#####/io files, which allows local users to obtain sensitive I/O statistics by polling a file, as demonstrated by discovering the length of another user's password. | https://nvd.nist.gov/vuln/detail/CVE-2011-2495 |
28,912 | linux | 1d1221f375c94ef961ba8574ac4f85c8870ddd51 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1d1221f375c94ef961ba8574ac4f85c8870ddd51 | proc: restrict access to /proc/PID/io
/proc/PID/io may be used for gathering private information. E.g. for
openssh and vsftpd daemons wchars/rchars may be used to learn the
precise password length. Restrict it to processes being able to ptrace
the target process.
ptrace_may_access() is needed to prevent keeping op... | 0 | static int proc_tgid_io_accounting(struct task_struct *task, char *buffer)
{
return do_io_accounting(task, buffer, 1);
}
| 164,751,488,855,929,430,000,000,000,000,000,000,000 | base.c | 97,077,772,234,708,240,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2495 | fs/proc/base.c in the Linux kernel before 2.6.39.4 does not properly restrict access to /proc/#####/io files, which allows local users to obtain sensitive I/O statistics by polling a file, as demonstrated by discovering the length of another user's password. | https://nvd.nist.gov/vuln/detail/CVE-2011-2495 |
28,913 | linux | 1d1221f375c94ef961ba8574ac4f85c8870ddd51 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1d1221f375c94ef961ba8574ac4f85c8870ddd51 | proc: restrict access to /proc/PID/io
/proc/PID/io may be used for gathering private information. E.g. for
openssh and vsftpd daemons wchars/rchars may be used to learn the
precise password length. Restrict it to processes being able to ptrace
the target process.
ptrace_may_access() is needed to prevent keeping op... | 0 | static struct dentry *proc_tid_base_lookup(struct inode *dir, struct dentry *dentry, struct nameidata *nd){
return proc_pident_lookup(dir, dentry,
tid_base_stuff, ARRAY_SIZE(tid_base_stuff));
}
| 329,821,662,974,823,120,000,000,000,000,000,000,000 | base.c | 97,077,772,234,708,240,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2495 | fs/proc/base.c in the Linux kernel before 2.6.39.4 does not properly restrict access to /proc/#####/io files, which allows local users to obtain sensitive I/O statistics by polling a file, as demonstrated by discovering the length of another user's password. | https://nvd.nist.gov/vuln/detail/CVE-2011-2495 |
28,914 | linux | 1d1221f375c94ef961ba8574ac4f85c8870ddd51 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1d1221f375c94ef961ba8574ac4f85c8870ddd51 | proc: restrict access to /proc/PID/io
/proc/PID/io may be used for gathering private information. E.g. for
openssh and vsftpd daemons wchars/rchars may be used to learn the
precise password length. Restrict it to processes being able to ptrace
the target process.
ptrace_may_access() is needed to prevent keeping op... | 0 | static int proc_tid_base_readdir(struct file * filp,
void * dirent, filldir_t filldir)
{
return proc_pident_readdir(filp,dirent,filldir,
tid_base_stuff,ARRAY_SIZE(tid_base_stuff));
}
| 157,127,246,678,013,700,000,000,000,000,000,000,000 | base.c | 97,077,772,234,708,240,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2495 | fs/proc/base.c in the Linux kernel before 2.6.39.4 does not properly restrict access to /proc/#####/io files, which allows local users to obtain sensitive I/O statistics by polling a file, as demonstrated by discovering the length of another user's password. | https://nvd.nist.gov/vuln/detail/CVE-2011-2495 |
28,915 | linux | 1d1221f375c94ef961ba8574ac4f85c8870ddd51 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1d1221f375c94ef961ba8574ac4f85c8870ddd51 | proc: restrict access to /proc/PID/io
/proc/PID/io may be used for gathering private information. E.g. for
openssh and vsftpd daemons wchars/rchars may be used to learn the
precise password length. Restrict it to processes being able to ptrace
the target process.
ptrace_may_access() is needed to prevent keeping op... | 0 | static int proc_tid_io_accounting(struct task_struct *task, char *buffer)
{
return do_io_accounting(task, buffer, 0);
}
| 67,250,009,185,236,220,000,000,000,000,000,000,000 | base.c | 97,077,772,234,708,240,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2495 | fs/proc/base.c in the Linux kernel before 2.6.39.4 does not properly restrict access to /proc/#####/io files, which allows local users to obtain sensitive I/O statistics by polling a file, as demonstrated by discovering the length of another user's password. | https://nvd.nist.gov/vuln/detail/CVE-2011-2495 |
28,916 | linux | 1d1221f375c94ef961ba8574ac4f85c8870ddd51 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1d1221f375c94ef961ba8574ac4f85c8870ddd51 | proc: restrict access to /proc/PID/io
/proc/PID/io may be used for gathering private information. E.g. for
openssh and vsftpd daemons wchars/rchars may be used to learn the
precise password length. Restrict it to processes being able to ptrace
the target process.
ptrace_may_access() is needed to prevent keeping op... | 0 | static int sched_autogroup_open(struct inode *inode, struct file *filp)
{
int ret;
ret = single_open(filp, sched_autogroup_show, NULL);
if (!ret) {
struct seq_file *m = filp->private_data;
m->private = inode;
}
return ret;
}
| 106,666,530,546,124,650,000,000,000,000,000,000,000 | base.c | 164,068,791,576,710,960,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2495 | fs/proc/base.c in the Linux kernel before 2.6.39.4 does not properly restrict access to /proc/#####/io files, which allows local users to obtain sensitive I/O statistics by polling a file, as demonstrated by discovering the length of another user's password. | https://nvd.nist.gov/vuln/detail/CVE-2011-2495 |
28,917 | linux | 1d1221f375c94ef961ba8574ac4f85c8870ddd51 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1d1221f375c94ef961ba8574ac4f85c8870ddd51 | proc: restrict access to /proc/PID/io
/proc/PID/io may be used for gathering private information. E.g. for
openssh and vsftpd daemons wchars/rchars may be used to learn the
precise password length. Restrict it to processes being able to ptrace
the target process.
ptrace_may_access() is needed to prevent keeping op... | 0 | sched_autogroup_write(struct file *file, const char __user *buf,
size_t count, loff_t *offset)
{
struct inode *inode = file->f_path.dentry->d_inode;
struct task_struct *p;
char buffer[PROC_NUMBUF];
int nice;
int err;
memset(buffer, 0, sizeof(buffer));
if (count > sizeof(buffer) - 1)
count = sizeof(buffer... | 286,634,369,825,674,530,000,000,000,000,000,000,000 | base.c | 164,068,791,576,710,960,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2495 | fs/proc/base.c in the Linux kernel before 2.6.39.4 does not properly restrict access to /proc/#####/io files, which allows local users to obtain sensitive I/O statistics by polling a file, as demonstrated by discovering the length of another user's password. | https://nvd.nist.gov/vuln/detail/CVE-2011-2495 |
28,918 | linux | 1d1221f375c94ef961ba8574ac4f85c8870ddd51 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1d1221f375c94ef961ba8574ac4f85c8870ddd51 | proc: restrict access to /proc/PID/io
/proc/PID/io may be used for gathering private information. E.g. for
openssh and vsftpd daemons wchars/rchars may be used to learn the
precise password length. Restrict it to processes being able to ptrace
the target process.
ptrace_may_access() is needed to prevent keeping op... | 0 | static int sched_open(struct inode *inode, struct file *filp)
{
return single_open(filp, sched_show, inode);
}
| 99,523,569,056,607,650,000,000,000,000,000,000,000 | base.c | 164,068,791,576,710,960,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2495 | fs/proc/base.c in the Linux kernel before 2.6.39.4 does not properly restrict access to /proc/#####/io files, which allows local users to obtain sensitive I/O statistics by polling a file, as demonstrated by discovering the length of another user's password. | https://nvd.nist.gov/vuln/detail/CVE-2011-2495 |
28,919 | linux | 1d1221f375c94ef961ba8574ac4f85c8870ddd51 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1d1221f375c94ef961ba8574ac4f85c8870ddd51 | proc: restrict access to /proc/PID/io
/proc/PID/io may be used for gathering private information. E.g. for
openssh and vsftpd daemons wchars/rchars may be used to learn the
precise password length. Restrict it to processes being able to ptrace
the target process.
ptrace_may_access() is needed to prevent keeping op... | 0 | sched_write(struct file *file, const char __user *buf,
size_t count, loff_t *offset)
{
struct inode *inode = file->f_path.dentry->d_inode;
struct task_struct *p;
p = get_proc_task(inode);
if (!p)
return -ESRCH;
proc_sched_set_task(p);
put_task_struct(p);
return count;
}
| 70,993,686,161,819,800,000,000,000,000,000,000,000 | base.c | 97,077,772,234,708,240,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2495 | fs/proc/base.c in the Linux kernel before 2.6.39.4 does not properly restrict access to /proc/#####/io files, which allows local users to obtain sensitive I/O statistics by polling a file, as demonstrated by discovering the length of another user's password. | https://nvd.nist.gov/vuln/detail/CVE-2011-2495 |
28,920 | linux | 1d1221f375c94ef961ba8574ac4f85c8870ddd51 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1d1221f375c94ef961ba8574ac4f85c8870ddd51 | proc: restrict access to /proc/PID/io
/proc/PID/io may be used for gathering private information. E.g. for
openssh and vsftpd daemons wchars/rchars may be used to learn the
precise password length. Restrict it to processes being able to ptrace
the target process.
ptrace_may_access() is needed to prevent keeping op... | 0 | static int task_dumpable(struct task_struct *task)
{
int dumpable = 0;
struct mm_struct *mm;
task_lock(task);
mm = task->mm;
if (mm)
dumpable = get_dumpable(mm);
task_unlock(task);
if(dumpable == 1)
return 1;
return 0;
}
| 198,629,081,677,192,700,000,000,000,000,000,000,000 | base.c | 97,077,772,234,708,240,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2495 | fs/proc/base.c in the Linux kernel before 2.6.39.4 does not properly restrict access to /proc/#####/io files, which allows local users to obtain sensitive I/O statistics by polling a file, as demonstrated by discovering the length of another user's password. | https://nvd.nist.gov/vuln/detail/CVE-2011-2495 |
28,921 | linux | 1d1221f375c94ef961ba8574ac4f85c8870ddd51 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1d1221f375c94ef961ba8574ac4f85c8870ddd51 | proc: restrict access to /proc/PID/io
/proc/PID/io may be used for gathering private information. E.g. for
openssh and vsftpd daemons wchars/rchars may be used to learn the
precise password length. Restrict it to processes being able to ptrace
the target process.
ptrace_may_access() is needed to prevent keeping op... | 0 | static void unlock_trace(struct task_struct *task)
{
mutex_unlock(&task->signal->cred_guard_mutex);
}
| 158,424,625,117,311,120,000,000,000,000,000,000,000 | base.c | 164,068,791,576,710,960,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2495 | fs/proc/base.c in the Linux kernel before 2.6.39.4 does not properly restrict access to /proc/#####/io files, which allows local users to obtain sensitive I/O statistics by polling a file, as demonstrated by discovering the length of another user's password. | https://nvd.nist.gov/vuln/detail/CVE-2011-2495 |
28,939 | linux | 0449641130f5652b344ef6fa39fa019d7e94660a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0449641130f5652b344ef6fa39fa019d7e94660a | ext4: init timer earlier to avoid a kernel panic in __save_error_info
During mount, when we fail to open journal inode or root inode, the
__save_error_info will mod_timer. But actually s_err_report isn't
initialized yet and the kernel oops. The detailed information can
be found https://bugzilla.kernel.org/show_bug.cgi... | 0 | __releases(bitlock)
__acquires(bitlock)
{
struct va_format vaf;
va_list args;
struct ext4_super_block *es = EXT4_SB(sb)->s_es;
es->s_last_error_ino = cpu_to_le32(ino);
es->s_last_error_block = cpu_to_le64(block);
__save_error_info(sb, function, line);
va_start(args, fmt);
vaf.fmt = fmt;
vaf.va = &args;
pri... | 266,279,927,481,748,980,000,000,000,000,000,000,000 | None | null | [
"CWE-703"
] | CVE-2011-2493 | The ext4_fill_super function in fs/ext4/super.c in the Linux kernel before 2.6.39 does not properly initialize a certain error-report data structure, which allows local users to cause a denial of service (OOPS) by attempting to mount a crafted ext4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-2493 |
28,940 | linux | 0449641130f5652b344ef6fa39fa019d7e94660a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0449641130f5652b344ef6fa39fa019d7e94660a | ext4: init timer earlier to avoid a kernel panic in __save_error_info
During mount, when we fail to open journal inode or root inode, the
__save_error_info will mod_timer. But actually s_err_report isn't
initialized yet and the kernel oops. The detailed information can
be found https://bugzilla.kernel.org/show_bug.cgi... | 0 | static ssize_t delayed_allocation_blocks_show(struct ext4_attr *a,
struct ext4_sb_info *sbi,
char *buf)
{
return snprintf(buf, PAGE_SIZE, "%llu\n",
(s64) percpu_counter_sum(&sbi->s_dirtyblocks_counter));
}
| 170,303,026,186,523,640,000,000,000,000,000,000,000 | super.c | 44,415,732,563,068,330,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-2493 | The ext4_fill_super function in fs/ext4/super.c in the Linux kernel before 2.6.39 does not properly initialize a certain error-report data structure, which allows local users to cause a denial of service (OOPS) by attempting to mount a crafted ext4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-2493 |
28,941 | linux | 0449641130f5652b344ef6fa39fa019d7e94660a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0449641130f5652b344ef6fa39fa019d7e94660a | ext4: init timer earlier to avoid a kernel panic in __save_error_info
During mount, when we fail to open journal inode or root inode, the
__save_error_info will mod_timer. But actually s_err_report isn't
initialized yet and the kernel oops. The detailed information can
be found https://bugzilla.kernel.org/show_bug.cgi... | 0 | static int ext4_commit_super(struct super_block *sb, int sync)
{
struct ext4_super_block *es = EXT4_SB(sb)->s_es;
struct buffer_head *sbh = EXT4_SB(sb)->s_sbh;
int error = 0;
if (!sbh)
return error;
if (buffer_write_io_error(sbh)) {
/*
* Oh, dear. A previous attempt to write the
* superblock failed. T... | 222,966,057,907,949,040,000,000,000,000,000,000,000 | super.c | 44,415,732,563,068,330,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-2493 | The ext4_fill_super function in fs/ext4/super.c in the Linux kernel before 2.6.39 does not properly initialize a certain error-report data structure, which allows local users to cause a denial of service (OOPS) by attempting to mount a crafted ext4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-2493 |
28,942 | linux | 0449641130f5652b344ef6fa39fa019d7e94660a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0449641130f5652b344ef6fa39fa019d7e94660a | ext4: init timer earlier to avoid a kernel panic in __save_error_info
During mount, when we fail to open journal inode or root inode, the
__save_error_info will mod_timer. But actually s_err_report isn't
initialized yet and the kernel oops. The detailed information can
be found https://bugzilla.kernel.org/show_bug.cgi... | 0 | static void ext4_destroy_inode(struct inode *inode)
{
ext4_ioend_wait(inode);
if (!list_empty(&(EXT4_I(inode)->i_orphan))) {
ext4_msg(inode->i_sb, KERN_ERR,
"Inode %lu (%p): orphan list check failed!",
inode->i_ino, EXT4_I(inode));
print_hex_dump(KERN_INFO, "", DUMP_PREFIX_ADDRESS, 16, 4,
EXT4_I(inode... | 319,490,232,088,168,100,000,000,000,000,000,000,000 | super.c | 44,415,732,563,068,330,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-2493 | The ext4_fill_super function in fs/ext4/super.c in the Linux kernel before 2.6.39 does not properly initialize a certain error-report data structure, which allows local users to cause a denial of service (OOPS) by attempting to mount a crafted ext4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-2493 |
28,943 | linux | 0449641130f5652b344ef6fa39fa019d7e94660a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0449641130f5652b344ef6fa39fa019d7e94660a | ext4: init timer earlier to avoid a kernel panic in __save_error_info
During mount, when we fail to open journal inode or root inode, the
__save_error_info will mod_timer. But actually s_err_report isn't
initialized yet and the kernel oops. The detailed information can
be found https://bugzilla.kernel.org/show_bug.cgi... | 0 | static int ext4_feature_set_ok(struct super_block *sb, int readonly)
{
if (EXT4_HAS_INCOMPAT_FEATURE(sb, ~EXT4_FEATURE_INCOMPAT_SUPP)) {
ext4_msg(sb, KERN_ERR,
"Couldn't mount because of "
"unsupported optional features (%x)",
(le32_to_cpu(EXT4_SB(sb)->s_es->s_feature_incompat) &
~EXT4_FEATURE_INCOMPAT_S... | 312,307,130,102,182,600,000,000,000,000,000,000,000 | super.c | 44,415,732,563,068,330,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-2493 | The ext4_fill_super function in fs/ext4/super.c in the Linux kernel before 2.6.39 does not properly initialize a certain error-report data structure, which allows local users to cause a denial of service (OOPS) by attempting to mount a crafted ext4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-2493 |
28,944 | linux | 0449641130f5652b344ef6fa39fa019d7e94660a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0449641130f5652b344ef6fa39fa019d7e94660a | ext4: init timer earlier to avoid a kernel panic in __save_error_info
During mount, when we fail to open journal inode or root inode, the
__save_error_info will mod_timer. But actually s_err_report isn't
initialized yet and the kernel oops. The detailed information can
be found https://bugzilla.kernel.org/show_bug.cgi... | 0 | static int ext4_fill_flex_info(struct super_block *sb)
{
struct ext4_sb_info *sbi = EXT4_SB(sb);
struct ext4_group_desc *gdp = NULL;
ext4_group_t flex_group_count;
ext4_group_t flex_group;
int groups_per_flex = 0;
size_t size;
int i;
sbi->s_log_groups_per_flex = sbi->s_es->s_log_groups_per_flex;
groups_per_fl... | 23,227,800,798,374,945,000,000,000,000,000,000,000 | super.c | 44,415,732,563,068,330,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-2493 | The ext4_fill_super function in fs/ext4/super.c in the Linux kernel before 2.6.39 does not properly initialize a certain error-report data structure, which allows local users to cause a denial of service (OOPS) by attempting to mount a crafted ext4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-2493 |
28,945 | linux | 0449641130f5652b344ef6fa39fa019d7e94660a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0449641130f5652b344ef6fa39fa019d7e94660a | ext4: init timer earlier to avoid a kernel panic in __save_error_info
During mount, when we fail to open journal inode or root inode, the
__save_error_info will mod_timer. But actually s_err_report isn't
initialized yet and the kernel oops. The detailed information can
be found https://bugzilla.kernel.org/show_bug.cgi... | 0 | __u32 ext4_free_blks_count(struct super_block *sb,
struct ext4_group_desc *bg)
{
return le16_to_cpu(bg->bg_free_blocks_count_lo) |
(EXT4_DESC_SIZE(sb) >= EXT4_MIN_DESC_SIZE_64BIT ?
(__u32)le16_to_cpu(bg->bg_free_blocks_count_hi) << 16 : 0);
}
| 155,762,344,035,869,390,000,000,000,000,000,000,000 | super.c | 44,415,732,563,068,330,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-2493 | The ext4_fill_super function in fs/ext4/super.c in the Linux kernel before 2.6.39 does not properly initialize a certain error-report data structure, which allows local users to cause a denial of service (OOPS) by attempting to mount a crafted ext4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-2493 |
28,946 | linux | 0449641130f5652b344ef6fa39fa019d7e94660a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0449641130f5652b344ef6fa39fa019d7e94660a | ext4: init timer earlier to avoid a kernel panic in __save_error_info
During mount, when we fail to open journal inode or root inode, the
__save_error_info will mod_timer. But actually s_err_report isn't
initialized yet and the kernel oops. The detailed information can
be found https://bugzilla.kernel.org/show_bug.cgi... | 0 | void ext4_free_blks_set(struct super_block *sb,
struct ext4_group_desc *bg, __u32 count)
{
bg->bg_free_blocks_count_lo = cpu_to_le16((__u16)count);
if (EXT4_DESC_SIZE(sb) >= EXT4_MIN_DESC_SIZE_64BIT)
bg->bg_free_blocks_count_hi = cpu_to_le16(count >> 16);
}
| 263,774,342,282,227,730,000,000,000,000,000,000,000 | super.c | 44,415,732,563,068,330,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-2493 | The ext4_fill_super function in fs/ext4/super.c in the Linux kernel before 2.6.39 does not properly initialize a certain error-report data structure, which allows local users to cause a denial of service (OOPS) by attempting to mount a crafted ext4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-2493 |
28,947 | linux | 0449641130f5652b344ef6fa39fa019d7e94660a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0449641130f5652b344ef6fa39fa019d7e94660a | ext4: init timer earlier to avoid a kernel panic in __save_error_info
During mount, when we fail to open journal inode or root inode, the
__save_error_info will mod_timer. But actually s_err_report isn't
initialized yet and the kernel oops. The detailed information can
be found https://bugzilla.kernel.org/show_bug.cgi... | 0 | static unsigned long ext4_get_stripe_size(struct ext4_sb_info *sbi)
{
unsigned long stride = le16_to_cpu(sbi->s_es->s_raid_stride);
unsigned long stripe_width =
le32_to_cpu(sbi->s_es->s_raid_stripe_width);
if (sbi->s_stripe && sbi->s_stripe <= sbi->s_blocks_per_group)
return sbi->s_stripe;
if (stripe_width <... | 229,426,710,318,096,000,000,000,000,000,000,000,000 | super.c | 44,415,732,563,068,330,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-2493 | The ext4_fill_super function in fs/ext4/super.c in the Linux kernel before 2.6.39 does not properly initialize a certain error-report data structure, which allows local users to cause a denial of service (OOPS) by attempting to mount a crafted ext4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-2493 |
28,948 | linux | 0449641130f5652b344ef6fa39fa019d7e94660a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0449641130f5652b344ef6fa39fa019d7e94660a | ext4: init timer earlier to avoid a kernel panic in __save_error_info
During mount, when we fail to open journal inode or root inode, the
__save_error_info will mod_timer. But actually s_err_report isn't
initialized yet and the kernel oops. The detailed information can
be found https://bugzilla.kernel.org/show_bug.cgi... | 0 | static int __init ext4_init_fs(void)
{
int i, err;
ext4_check_flag_values();
for (i = 0; i < EXT4_WQ_HASH_SZ; i++) {
mutex_init(&ext4__aio_mutex[i]);
init_waitqueue_head(&ext4__ioend_wq[i]);
}
err = ext4_init_pageio();
if (err)
return err;
err = ext4_init_system_zone();
if (err)
goto out7;
ext4_kset... | 102,904,705,708,493,020,000,000,000,000,000,000,000 | super.c | 44,415,732,563,068,330,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-2493 | The ext4_fill_super function in fs/ext4/super.c in the Linux kernel before 2.6.39 does not properly initialize a certain error-report data structure, which allows local users to cause a denial of service (OOPS) by attempting to mount a crafted ext4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-2493 |
28,949 | linux | 0449641130f5652b344ef6fa39fa019d7e94660a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0449641130f5652b344ef6fa39fa019d7e94660a | ext4: init timer earlier to avoid a kernel panic in __save_error_info
During mount, when we fail to open journal inode or root inode, the
__save_error_info will mod_timer. But actually s_err_report isn't
initialized yet and the kernel oops. The detailed information can
be found https://bugzilla.kernel.org/show_bug.cgi... | 0 | handle_t *ext4_journal_start_sb(struct super_block *sb, int nblocks)
{
journal_t *journal;
if (sb->s_flags & MS_RDONLY)
return ERR_PTR(-EROFS);
vfs_check_frozen(sb, SB_FREEZE_TRANS);
/* Special case here: if the journal has aborted behind our
* backs (eg. EIO in the commit thread), then we still need to
* t... | 314,215,654,483,330,080,000,000,000,000,000,000,000 | super.c | 44,415,732,563,068,330,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-2493 | The ext4_fill_super function in fs/ext4/super.c in the Linux kernel before 2.6.39 does not properly initialize a certain error-report data structure, which allows local users to cause a denial of service (OOPS) by attempting to mount a crafted ext4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-2493 |
28,950 | linux | 0449641130f5652b344ef6fa39fa019d7e94660a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0449641130f5652b344ef6fa39fa019d7e94660a | ext4: init timer earlier to avoid a kernel panic in __save_error_info
During mount, when we fail to open journal inode or root inode, the
__save_error_info will mod_timer. But actually s_err_report isn't
initialized yet and the kernel oops. The detailed information can
be found https://bugzilla.kernel.org/show_bug.cgi... | 0 | static void ext4_lazyinode_timeout(unsigned long data)
{
struct task_struct *p = (struct task_struct *)data;
wake_up_process(p);
}
| 331,455,792,510,263,700,000,000,000,000,000,000,000 | super.c | 44,415,732,563,068,330,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-2493 | The ext4_fill_super function in fs/ext4/super.c in the Linux kernel before 2.6.39 does not properly initialize a certain error-report data structure, which allows local users to cause a denial of service (OOPS) by attempting to mount a crafted ext4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-2493 |
28,951 | linux | 0449641130f5652b344ef6fa39fa019d7e94660a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0449641130f5652b344ef6fa39fa019d7e94660a | ext4: init timer earlier to avoid a kernel panic in __save_error_info
During mount, when we fail to open journal inode or root inode, the
__save_error_info will mod_timer. But actually s_err_report isn't
initialized yet and the kernel oops. The detailed information can
be found https://bugzilla.kernel.org/show_bug.cgi... | 0 | static loff_t ext4_max_size(int blkbits, int has_huge_files)
{
loff_t res;
loff_t upper_limit = MAX_LFS_FILESIZE;
/* small i_blocks in vfs inode? */
if (!has_huge_files || sizeof(blkcnt_t) < sizeof(u64)) {
/*
* CONFIG_LBDAF is not enabled implies the inode
* i_block represent total blocks in 512 bytes
*... | 205,250,778,915,489,230,000,000,000,000,000,000,000 | super.c | 44,415,732,563,068,330,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-2493 | The ext4_fill_super function in fs/ext4/super.c in the Linux kernel before 2.6.39 does not properly initialize a certain error-report data structure, which allows local users to cause a denial of service (OOPS) by attempting to mount a crafted ext4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-2493 |
28,952 | linux | 0449641130f5652b344ef6fa39fa019d7e94660a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0449641130f5652b344ef6fa39fa019d7e94660a | ext4: init timer earlier to avoid a kernel panic in __save_error_info
During mount, when we fail to open journal inode or root inode, the
__save_error_info will mod_timer. But actually s_err_report isn't
initialized yet and the kernel oops. The detailed information can
be found https://bugzilla.kernel.org/show_bug.cgi... | 0 | static void ext4_put_super(struct super_block *sb)
{
struct ext4_sb_info *sbi = EXT4_SB(sb);
struct ext4_super_block *es = sbi->s_es;
int i, err;
ext4_unregister_li_request(sb);
dquot_disable(sb, -1, DQUOT_USAGE_ENABLED | DQUOT_LIMITS_ENABLED);
flush_workqueue(sbi->dio_unwritten_wq);
destroy_workqueue(sbi->dio... | 183,109,893,236,342,640,000,000,000,000,000,000,000 | super.c | 44,415,732,563,068,330,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-2493 | The ext4_fill_super function in fs/ext4/super.c in the Linux kernel before 2.6.39 does not properly initialize a certain error-report data structure, which allows local users to cause a denial of service (OOPS) by attempting to mount a crafted ext4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-2493 |
28,953 | linux | 0449641130f5652b344ef6fa39fa019d7e94660a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0449641130f5652b344ef6fa39fa019d7e94660a | ext4: init timer earlier to avoid a kernel panic in __save_error_info
During mount, when we fail to open journal inode or root inode, the
__save_error_info will mod_timer. But actually s_err_report isn't
initialized yet and the kernel oops. The detailed information can
be found https://bugzilla.kernel.org/show_bug.cgi... | 0 | static int ext4_quota_off(struct super_block *sb, int type)
{
struct inode *inode = sb_dqopt(sb)->files[type];
handle_t *handle;
/* Force all delayed allocation blocks to be allocated.
* Caller already holds s_umount sem */
if (test_opt(sb, DELALLOC))
sync_filesystem(sb);
/* Update modification times of quot... | 297,382,097,674,747,400,000,000,000,000,000,000,000 | super.c | 44,415,732,563,068,330,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-2493 | The ext4_fill_super function in fs/ext4/super.c in the Linux kernel before 2.6.39 does not properly initialize a certain error-report data structure, which allows local users to cause a denial of service (OOPS) by attempting to mount a crafted ext4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-2493 |
28,954 | linux | 0449641130f5652b344ef6fa39fa019d7e94660a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0449641130f5652b344ef6fa39fa019d7e94660a | ext4: init timer earlier to avoid a kernel panic in __save_error_info
During mount, when we fail to open journal inode or root inode, the
__save_error_info will mod_timer. But actually s_err_report isn't
initialized yet and the kernel oops. The detailed information can
be found https://bugzilla.kernel.org/show_bug.cgi... | 0 | static int ext4_register_li_request(struct super_block *sb,
ext4_group_t first_not_zeroed)
{
struct ext4_sb_info *sbi = EXT4_SB(sb);
struct ext4_li_request *elr;
ext4_group_t ngroups = EXT4_SB(sb)->s_groups_count;
int ret = 0;
if (sbi->s_li_request != NULL)
return 0;
if (first_not_zeroed == ngroups ||... | 126,035,321,481,872,080,000,000,000,000,000,000,000 | super.c | 44,415,732,563,068,330,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-2493 | The ext4_fill_super function in fs/ext4/super.c in the Linux kernel before 2.6.39 does not properly initialize a certain error-report data structure, which allows local users to cause a denial of service (OOPS) by attempting to mount a crafted ext4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-2493 |
28,955 | linux | 0449641130f5652b344ef6fa39fa019d7e94660a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0449641130f5652b344ef6fa39fa019d7e94660a | ext4: init timer earlier to avoid a kernel panic in __save_error_info
During mount, when we fail to open journal inode or root inode, the
__save_error_info will mod_timer. But actually s_err_report isn't
initialized yet and the kernel oops. The detailed information can
be found https://bugzilla.kernel.org/show_bug.cgi... | 0 | static int ext4_remount(struct super_block *sb, int *flags, char *data)
{
struct ext4_super_block *es;
struct ext4_sb_info *sbi = EXT4_SB(sb);
ext4_fsblk_t n_blocks_count = 0;
unsigned long old_sb_flags;
struct ext4_mount_options old_opts;
int enable_quota = 0;
ext4_group_t g;
unsigned int journal_ioprio = DEFA... | 66,143,985,217,278,070,000,000,000,000,000,000,000 | super.c | 44,415,732,563,068,330,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-2493 | The ext4_fill_super function in fs/ext4/super.c in the Linux kernel before 2.6.39 does not properly initialize a certain error-report data structure, which allows local users to cause a denial of service (OOPS) by attempting to mount a crafted ext4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-2493 |
28,956 | linux | 0449641130f5652b344ef6fa39fa019d7e94660a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0449641130f5652b344ef6fa39fa019d7e94660a | ext4: init timer earlier to avoid a kernel panic in __save_error_info
During mount, when we fail to open journal inode or root inode, the
__save_error_info will mod_timer. But actually s_err_report isn't
initialized yet and the kernel oops. The detailed information can
be found https://bugzilla.kernel.org/show_bug.cgi... | 0 | static int ext4_run_li_request(struct ext4_li_request *elr)
{
struct ext4_group_desc *gdp = NULL;
ext4_group_t group, ngroups;
struct super_block *sb;
unsigned long timeout = 0;
int ret = 0;
sb = elr->lr_super;
ngroups = EXT4_SB(sb)->s_groups_count;
for (group = elr->lr_next_group; group < ngroups; group++) {... | 9,654,773,990,902,666,000,000,000,000,000,000,000 | super.c | 44,415,732,563,068,330,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-2493 | The ext4_fill_super function in fs/ext4/super.c in the Linux kernel before 2.6.39 does not properly initialize a certain error-report data structure, which allows local users to cause a denial of service (OOPS) by attempting to mount a crafted ext4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-2493 |
28,957 | linux | 0449641130f5652b344ef6fa39fa019d7e94660a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0449641130f5652b344ef6fa39fa019d7e94660a | ext4: init timer earlier to avoid a kernel panic in __save_error_info
During mount, when we fail to open journal inode or root inode, the
__save_error_info will mod_timer. But actually s_err_report isn't
initialized yet and the kernel oops. The detailed information can
be found https://bugzilla.kernel.org/show_bug.cgi... | 0 | static int ext4_setup_super(struct super_block *sb, struct ext4_super_block *es,
int read_only)
{
struct ext4_sb_info *sbi = EXT4_SB(sb);
int res = 0;
if (le32_to_cpu(es->s_rev_level) > EXT4_MAX_SUPP_REV) {
ext4_msg(sb, KERN_ERR, "revision level too high, "
"forcing read-only mode");
res = MS_RDONLY;... | 198,134,935,179,940,130,000,000,000,000,000,000,000 | super.c | 44,415,732,563,068,330,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-2493 | The ext4_fill_super function in fs/ext4/super.c in the Linux kernel before 2.6.39 does not properly initialize a certain error-report data structure, which allows local users to cause a denial of service (OOPS) by attempting to mount a crafted ext4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-2493 |
28,958 | linux | 0449641130f5652b344ef6fa39fa019d7e94660a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0449641130f5652b344ef6fa39fa019d7e94660a | ext4: init timer earlier to avoid a kernel panic in __save_error_info
During mount, when we fail to open journal inode or root inode, the
__save_error_info will mod_timer. But actually s_err_report isn't
initialized yet and the kernel oops. The detailed information can
be found https://bugzilla.kernel.org/show_bug.cgi... | 0 | static int ext4_statfs(struct dentry *dentry, struct kstatfs *buf)
{
struct super_block *sb = dentry->d_sb;
struct ext4_sb_info *sbi = EXT4_SB(sb);
struct ext4_super_block *es = sbi->s_es;
u64 fsid;
if (test_opt(sb, MINIX_DF)) {
sbi->s_overhead_last = 0;
} else if (sbi->s_blocks_last != ext4_blocks_count(es)) ... | 215,125,283,526,668,600,000,000,000,000,000,000,000 | super.c | 44,415,732,563,068,330,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-2493 | The ext4_fill_super function in fs/ext4/super.c in the Linux kernel before 2.6.39 does not properly initialize a certain error-report data structure, which allows local users to cause a denial of service (OOPS) by attempting to mount a crafted ext4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-2493 |
28,959 | linux | 0449641130f5652b344ef6fa39fa019d7e94660a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0449641130f5652b344ef6fa39fa019d7e94660a | ext4: init timer earlier to avoid a kernel panic in __save_error_info
During mount, when we fail to open journal inode or root inode, the
__save_error_info will mod_timer. But actually s_err_report isn't
initialized yet and the kernel oops. The detailed information can
be found https://bugzilla.kernel.org/show_bug.cgi... | 0 | static void ext4_unregister_li_request(struct super_block *sb)
{
struct ext4_li_request *elr = EXT4_SB(sb)->s_li_request;
if (!ext4_li_info)
return;
mutex_lock(&ext4_li_info->li_list_mtx);
ext4_remove_li_request(elr);
mutex_unlock(&ext4_li_info->li_list_mtx);
}
| 314,924,223,885,537,480,000,000,000,000,000,000,000 | super.c | 44,415,732,563,068,330,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-2493 | The ext4_fill_super function in fs/ext4/super.c in the Linux kernel before 2.6.39 does not properly initialize a certain error-report data structure, which allows local users to cause a denial of service (OOPS) by attempting to mount a crafted ext4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-2493 |
28,960 | linux | 0449641130f5652b344ef6fa39fa019d7e94660a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0449641130f5652b344ef6fa39fa019d7e94660a | ext4: init timer earlier to avoid a kernel panic in __save_error_info
During mount, when we fail to open journal inode or root inode, the
__save_error_info will mod_timer. But actually s_err_report isn't
initialized yet and the kernel oops. The detailed information can
be found https://bugzilla.kernel.org/show_bug.cgi... | 0 | static int parse_options(char *options, struct super_block *sb,
unsigned long *journal_devnum,
unsigned int *journal_ioprio,
ext4_fsblk_t *n_blocks_count, int is_remount)
{
struct ext4_sb_info *sbi = EXT4_SB(sb);
char *p;
substring_t args[MAX_OPT_ARGS];
int data_opt = 0;
int option;
#ifdef CONFIG_QUOTA... | 136,432,154,871,632,260,000,000,000,000,000,000,000 | super.c | 44,415,732,563,068,330,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-2493 | The ext4_fill_super function in fs/ext4/super.c in the Linux kernel before 2.6.39 does not properly initialize a certain error-report data structure, which allows local users to cause a denial of service (OOPS) by attempting to mount a crafted ext4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-2493 |
29,216 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | int __ksm_enter(struct mm_struct *mm)
{
struct mm_slot *mm_slot;
int needs_wakeup;
mm_slot = alloc_mm_slot();
if (!mm_slot)
return -ENOMEM;
/* Check ksm_run too? Would need tighter locking */
needs_wakeup = list_empty(&ksm_mm_head.mm_list);
spin_lock(&ksm_mmlist_lock);
insert_to_mm_slots_hash(mm, mm_slot)... | 261,307,346,972,783,200,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,217 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | void __ksm_exit(struct mm_struct *mm)
{
struct mm_slot *mm_slot;
int easy_to_free = 0;
/*
* This process is exiting: if it's straightforward (as is the
* case when ksmd was never running), free mm_slot immediately.
* But if it's at the cursor or has rmap_items linked to it, use
* mmap_sem to synchronize wit... | 249,811,368,794,229,500,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,218 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static inline struct mm_slot *alloc_mm_slot(void)
{
if (!mm_slot_cache) /* initialization failed */
return NULL;
return kmem_cache_zalloc(mm_slot_cache, GFP_KERNEL);
}
| 33,389,473,461,800,380,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,219 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static inline struct rmap_item *alloc_rmap_item(void)
{
struct rmap_item *rmap_item;
rmap_item = kmem_cache_zalloc(rmap_item_cache, GFP_KERNEL);
if (rmap_item)
ksm_rmap_items++;
return rmap_item;
}
| 6,688,162,341,738,951,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,220 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static void break_cow(struct rmap_item *rmap_item)
{
struct mm_struct *mm = rmap_item->mm;
unsigned long addr = rmap_item->address;
struct vm_area_struct *vma;
/*
* It is not an accident that whenever we want to break COW
* to undo, we also need to drop a reference to the anon_vma.
*/
put_anon_vma(rmap_item... | 308,382,746,638,153,340,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,221 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static int break_ksm(struct vm_area_struct *vma, unsigned long addr)
{
struct page *page;
int ret = 0;
do {
cond_resched();
page = follow_page(vma, addr, FOLL_GET);
if (IS_ERR_OR_NULL(page))
break;
if (PageKsm(page))
ret = handle_mm_fault(vma->vm_mm, vma, addr,
FAULT_FLAG_WRITE);
else
ret ... | 100,660,214,341,647,430,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,222 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static void cmp_and_merge_page(struct page *page, struct rmap_item *rmap_item)
{
struct rmap_item *tree_rmap_item;
struct page *tree_page = NULL;
struct stable_node *stable_node;
struct page *kpage;
unsigned int checksum;
int err;
remove_rmap_item_from_tree(rmap_item);
/* We first start with searching the pag... | 335,497,765,163,528,470,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,223 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static inline void free_mm_slot(struct mm_slot *mm_slot)
{
kmem_cache_free(mm_slot_cache, mm_slot);
}
| 54,575,234,956,623,950,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,224 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static inline void free_rmap_item(struct rmap_item *rmap_item)
{
ksm_rmap_items--;
rmap_item->mm = NULL; /* debug safety */
kmem_cache_free(rmap_item_cache, rmap_item);
}
| 88,927,397,810,402,200,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,225 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static inline void free_stable_node(struct stable_node *stable_node)
{
kmem_cache_free(stable_node_cache, stable_node);
}
| 6,357,463,652,760,366,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,226 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static ssize_t full_scans_show(struct kobject *kobj,
struct kobj_attribute *attr, char *buf)
{
return sprintf(buf, "%lu\n", ksm_scan.seqnr);
}
| 153,888,121,106,364,750,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,227 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static struct page *get_ksm_page(struct stable_node *stable_node)
{
struct page *page;
void *expected_mapping;
page = pfn_to_page(stable_node->kpfn);
expected_mapping = (void *)stable_node +
(PAGE_MAPPING_ANON | PAGE_MAPPING_KSM);
rcu_read_lock();
if (page->mapping != expected_mapping)
goto stale;
if (!ge... | 185,929,465,238,675,350,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,228 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static struct page *get_mergeable_page(struct rmap_item *rmap_item)
{
struct mm_struct *mm = rmap_item->mm;
unsigned long addr = rmap_item->address;
struct vm_area_struct *vma;
struct page *page;
down_read(&mm->mmap_sem);
if (ksm_test_exit(mm))
goto out;
vma = find_vma(mm, addr);
if (!vma || vma->vm_start > ... | 253,734,313,578,961,700,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,229 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static struct mm_slot *get_mm_slot(struct mm_struct *mm)
{
struct mm_slot *mm_slot;
struct hlist_head *bucket;
struct hlist_node *node;
bucket = &mm_slots_hash[hash_ptr(mm, MM_SLOTS_HASH_SHIFT)];
hlist_for_each_entry(mm_slot, node, bucket, link) {
if (mm == mm_slot->mm)
return mm_slot;
}
return NULL;
}
| 116,080,795,814,971,660,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,230 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static struct rmap_item *get_next_rmap_item(struct mm_slot *mm_slot,
struct rmap_item **rmap_list,
unsigned long addr)
{
struct rmap_item *rmap_item;
while (*rmap_list) {
rmap_item = *rmap_list;
if ((rmap_item->address & PAGE_MASK) == addr)
return rmap_item;
if (rmap_item->address > addr)
... | 58,821,413,001,228,020,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,231 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static inline int in_stable_tree(struct rmap_item *rmap_item)
{
return rmap_item->address & STABLE_FLAG;
}
| 74,073,086,479,555,420,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,232 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static void insert_to_mm_slots_hash(struct mm_struct *mm,
struct mm_slot *mm_slot)
{
struct hlist_head *bucket;
bucket = &mm_slots_hash[hash_ptr(mm, MM_SLOTS_HASH_SHIFT)];
mm_slot->mm = mm;
hlist_add_head(&mm_slot->link, bucket);
}
| 284,599,742,128,826,000,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,233 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static struct stable_node *ksm_check_stable_tree(unsigned long start_pfn,
unsigned long end_pfn)
{
struct rb_node *node;
for (node = rb_first(&root_stable_tree); node; node = rb_next(node)) {
struct stable_node *stable_node;
stable_node = rb_entry(node, struct stable_node, node);
if (stable_node->kpfn ... | 194,515,161,336,822,730,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,234 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static void ksm_do_scan(unsigned int scan_npages)
{
struct rmap_item *rmap_item;
struct page *uninitialized_var(page);
while (scan_npages-- && likely(!freezing(current))) {
cond_resched();
rmap_item = scan_get_next_rmap_item(&page);
if (!rmap_item)
return;
if (!PageKsm(page) || !in_stable_tree(rmap_item)... | 150,922,362,597,553,500,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,235 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | struct page *ksm_does_need_to_copy(struct page *page,
struct vm_area_struct *vma, unsigned long address)
{
struct page *new_page;
new_page = alloc_page_vma(GFP_HIGHUSER_MOVABLE, vma, address);
if (new_page) {
copy_user_highpage(new_page, page, address, vma);
SetPageDirty(new_page);
__SetPageUptodate(new_p... | 85,700,094,067,931,480,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,236 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | int ksm_madvise(struct vm_area_struct *vma, unsigned long start,
unsigned long end, int advice, unsigned long *vm_flags)
{
struct mm_struct *mm = vma->vm_mm;
int err;
switch (advice) {
case MADV_MERGEABLE:
/*
* Be somewhat over-protective for now!
*/
if (*vm_flags & (VM_MERGEABLE | VM_SHARED | VM_MAYS... | 179,335,193,406,477,580,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,237 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | void ksm_migrate_page(struct page *newpage, struct page *oldpage)
{
struct stable_node *stable_node;
VM_BUG_ON(!PageLocked(oldpage));
VM_BUG_ON(!PageLocked(newpage));
VM_BUG_ON(newpage->mapping != oldpage->mapping);
stable_node = page_stable_node(newpage);
if (stable_node) {
VM_BUG_ON(stable_node->kpfn != pag... | 250,647,005,203,336,700,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,238 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static int ksm_scan_thread(void *nothing)
{
set_freezable();
set_user_nice(current, 5);
while (!kthread_should_stop()) {
mutex_lock(&ksm_thread_mutex);
if (ksmd_should_run())
ksm_do_scan(ksm_thread_pages_to_scan);
mutex_unlock(&ksm_thread_mutex);
try_to_freeze();
if (ksmd_should_run()) {
schedule_... | 179,831,821,906,945,760,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,239 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static void __init ksm_slab_free(void)
{
kmem_cache_destroy(mm_slot_cache);
kmem_cache_destroy(stable_node_cache);
kmem_cache_destroy(rmap_item_cache);
mm_slot_cache = NULL;
}
| 44,140,656,271,820,150,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,240 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static int __init ksm_slab_init(void)
{
rmap_item_cache = KSM_KMEM_CACHE(rmap_item, 0);
if (!rmap_item_cache)
goto out;
stable_node_cache = KSM_KMEM_CACHE(stable_node, 0);
if (!stable_node_cache)
goto out_free1;
mm_slot_cache = KSM_KMEM_CACHE(mm_slot, 0);
if (!mm_slot_cache)
goto out_free2;
return 0;
o... | 111,702,036,895,015,830,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,241 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static inline bool ksm_test_exit(struct mm_struct *mm)
{
return atomic_read(&mm->mm_users) == 0;
}
| 129,275,367,263,156,040,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,242 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static int ksmd_should_run(void)
{
return (ksm_run & KSM_RUN_MERGE) && !list_empty(&ksm_mm_head.mm_list);
}
| 311,218,960,429,363,640,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,243 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static int memcmp_pages(struct page *page1, struct page *page2)
{
char *addr1, *addr2;
int ret;
addr1 = kmap_atomic(page1, KM_USER0);
addr2 = kmap_atomic(page2, KM_USER1);
ret = memcmp(addr1, addr2, PAGE_SIZE);
kunmap_atomic(addr2, KM_USER1);
kunmap_atomic(addr1, KM_USER0);
return ret;
}
| 54,670,407,369,051,740,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,244 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | int page_referenced_ksm(struct page *page, struct mem_cgroup *memcg,
unsigned long *vm_flags)
{
struct stable_node *stable_node;
struct rmap_item *rmap_item;
struct hlist_node *hlist;
unsigned int mapcount = page_mapcount(page);
int referenced = 0;
int search_new_forks = 0;
VM_BUG_ON(!PageKsm(page));
VM_BUG... | 145,127,708,614,783,800,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,245 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static struct page *page_trans_compound_anon(struct page *page)
{
if (PageTransCompound(page)) {
struct page *head = compound_trans_head(page);
/*
* head may actually be splitted and freed from under
* us but it's ok here.
*/
if (PageAnon(head))
return head;
}
return NULL;
}
| 92,406,268,497,036,770,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,246 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static int page_trans_compound_anon_split(struct page *page)
{
int ret = 0;
struct page *transhuge_head = page_trans_compound_anon(page);
if (transhuge_head) {
/* Get the reference on the head to split it. */
if (get_page_unless_zero(transhuge_head)) {
/*
* Recheck we got the reference while the head
... | 119,616,115,936,173,990,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,247 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static inline int pages_identical(struct page *page1, struct page *page2)
{
return !memcmp_pages(page1, page2);
}
| 137,397,099,360,866,020,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,248 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static ssize_t pages_shared_show(struct kobject *kobj,
struct kobj_attribute *attr, char *buf)
{
return sprintf(buf, "%lu\n", ksm_pages_shared);
}
| 66,692,450,755,948,240,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,249 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static ssize_t pages_sharing_show(struct kobject *kobj,
struct kobj_attribute *attr, char *buf)
{
return sprintf(buf, "%lu\n", ksm_pages_sharing);
}
| 42,198,648,311,082,187,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,250 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static ssize_t pages_to_scan_store(struct kobject *kobj,
struct kobj_attribute *attr,
const char *buf, size_t count)
{
int err;
unsigned long nr_pages;
err = strict_strtoul(buf, 10, &nr_pages);
if (err || nr_pages > UINT_MAX)
return -EINVAL;
ksm_thread_pages_to_scan = nr_pages;
return count;
}
| 225,242,745,983,099,450,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,251 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static ssize_t pages_unshared_show(struct kobject *kobj,
struct kobj_attribute *attr, char *buf)
{
return sprintf(buf, "%lu\n", ksm_pages_unshared);
}
| 7,600,290,765,614,373,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,252 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static ssize_t pages_volatile_show(struct kobject *kobj,
struct kobj_attribute *attr, char *buf)
{
long ksm_pages_volatile;
ksm_pages_volatile = ksm_rmap_items - ksm_pages_shared
- ksm_pages_sharing - ksm_pages_unshared;
/*
* It was not worth any locking to calculate that statistic,
* but it might th... | 283,330,180,133,201,340,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,253 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static void remove_rmap_item_from_tree(struct rmap_item *rmap_item)
{
if (rmap_item->address & STABLE_FLAG) {
struct stable_node *stable_node;
struct page *page;
stable_node = rmap_item->head;
page = get_ksm_page(stable_node);
if (!page)
goto out;
lock_page(page);
hlist_del(&rmap_item->hlist);
unl... | 301,995,568,990,175,800,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,254 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static void remove_trailing_rmap_items(struct mm_slot *mm_slot,
struct rmap_item **rmap_list)
{
while (*rmap_list) {
struct rmap_item *rmap_item = *rmap_list;
*rmap_list = rmap_item->rmap_list;
remove_rmap_item_from_tree(rmap_item);
free_rmap_item(rmap_item);
}
}
| 209,748,472,681,760,100,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,255 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static int replace_page(struct vm_area_struct *vma, struct page *page,
struct page *kpage, pte_t orig_pte)
{
struct mm_struct *mm = vma->vm_mm;
pgd_t *pgd;
pud_t *pud;
pmd_t *pmd;
pte_t *ptep;
spinlock_t *ptl;
unsigned long addr;
int err = -EFAULT;
addr = page_address_in_vma(page, vma);
if (addr == -EFAUL... | 103,803,027,391,781,500,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,256 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | int rmap_walk_ksm(struct page *page, int (*rmap_one)(struct page *,
struct vm_area_struct *, unsigned long, void *), void *arg)
{
struct stable_node *stable_node;
struct hlist_node *hlist;
struct rmap_item *rmap_item;
int ret = SWAP_AGAIN;
int search_new_forks = 0;
VM_BUG_ON(!PageKsm(page));
VM_BUG_ON(!Page... | 68,927,726,742,776,020,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,257 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static ssize_t run_show(struct kobject *kobj, struct kobj_attribute *attr,
char *buf)
{
return sprintf(buf, "%u\n", ksm_run);
}
| 258,328,537,535,129,230,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,258 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static ssize_t sleep_millisecs_show(struct kobject *kobj,
struct kobj_attribute *attr, char *buf)
{
return sprintf(buf, "%u\n", ksm_thread_sleep_millisecs);
}
| 315,656,501,992,141,600,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,259 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static ssize_t sleep_millisecs_store(struct kobject *kobj,
struct kobj_attribute *attr,
const char *buf, size_t count)
{
unsigned long msecs;
int err;
err = strict_strtoul(buf, 10, &msecs);
if (err || msecs > UINT_MAX)
return -EINVAL;
ksm_thread_sleep_millisecs = msecs;
return count;
}
| 158,357,117,330,462,970,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,260 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static struct stable_node *stable_tree_insert(struct page *kpage)
{
struct rb_node **new = &root_stable_tree.rb_node;
struct rb_node *parent = NULL;
struct stable_node *stable_node;
while (*new) {
struct page *tree_page;
int ret;
cond_resched();
stable_node = rb_entry(*new, struct stable_node, node);
tr... | 254,060,267,257,833,830,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,261 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static int try_to_merge_one_page(struct vm_area_struct *vma,
struct page *page, struct page *kpage)
{
pte_t orig_pte = __pte(0);
int err = -EFAULT;
if (page == kpage) /* ksm page forked */
return 0;
if (!(vma->vm_flags & VM_MERGEABLE))
goto out;
if (PageTransCompound(page) && page_trans_compound_anon_... | 183,800,801,045,379,730,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,262 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static struct page *try_to_merge_two_pages(struct rmap_item *rmap_item,
struct page *page,
struct rmap_item *tree_rmap_item,
struct page *tree_page)
{
int err;
err = try_to_merge_with_ksm_page(rmap_item, page, NULL);
if (!err) {
err = try_to_merge_with_ksm_page(tree_rmap_item,
tree_... | 4,739,993,032,622,363,500,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,263 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static int try_to_merge_with_ksm_page(struct rmap_item *rmap_item,
struct page *page, struct page *kpage)
{
struct mm_struct *mm = rmap_item->mm;
struct vm_area_struct *vma;
int err = -EFAULT;
down_read(&mm->mmap_sem);
if (ksm_test_exit(mm))
goto out;
vma = find_vma(mm, rmap_item->address);
if (!vma... | 101,776,456,742,618,250,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,264 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | int try_to_unmap_ksm(struct page *page, enum ttu_flags flags)
{
struct stable_node *stable_node;
struct hlist_node *hlist;
struct rmap_item *rmap_item;
int ret = SWAP_AGAIN;
int search_new_forks = 0;
VM_BUG_ON(!PageKsm(page));
VM_BUG_ON(!PageLocked(page));
stable_node = page_stable_node(page);
if (!stable_no... | 235,320,674,894,231,800,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,265 | linux | 2b472611a32a72f4a118c069c2d62a1a3f087afd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b472611a32a72f4a118c069c2d62a1a3f087afd | ksm: fix NULL pointer dereference in scan_get_next_rmap_item()
Andrea Righi reported a case where an exiting task can race against
ksmd::scan_get_next_rmap_item (http://lkml.org/lkml/2011/6/1/742) easily
triggering a NULL pointer dereference in ksmd.
ksm_scan.mm_slot == &ksm_mm_head with only one registered mm
CPU 1... | 0 | static int unmerge_and_remove_all_rmap_items(void)
{
struct mm_slot *mm_slot;
struct mm_struct *mm;
struct vm_area_struct *vma;
int err = 0;
spin_lock(&ksm_mmlist_lock);
ksm_scan.mm_slot = list_entry(ksm_mm_head.mm_list.next,
struct mm_slot, mm_list);
spin_unlock(&ksm_mmlist_lock);
for (mm_slot = ksm_sc... | 323,644,214,273,652,950,000,000,000,000,000,000,000 | ksm.c | 91,806,157,513,520,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-2183 | Race condition in the scan_get_next_rmap_item function in mm/ksm.c in the Linux kernel before 2.6.39.3, when Kernel SamePage Merging (KSM) is enabled, allows local users to cause a denial of service (NULL pointer dereference) or possibly have unspecified other impact via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2011-2183 |
29,266 | linux | cae13fe4cc3f24820ffb990c09110626837e85d4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cae13fe4cc3f24820ffb990c09110626837e85d4 | Fix for buffer overflow in ldm_frag_add not sufficient
As Ben Hutchings discovered [1], the patch for CVE-2011-1017 (buffer
overflow in ldm_frag_add) is not sufficient. The original patch in
commit c340b1d64000 ("fs/partitions/ldm.c: fix oops caused by corrupted
partition table") does not consider that, for subsequen... | 0 | static void _ldm_printk (const char *level, const char *function,
const char *fmt, ...)
{
static char buf[128];
va_list args;
va_start (args, fmt);
vsnprintf (buf, sizeof (buf), fmt, args);
va_end (args);
printk ("%s%s(): %s\n", level, function, buf);
}
| 51,955,216,568,999,360,000,000,000,000,000,000,000 | ldm.c | 193,102,196,756,441,320,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-2182 | The ldm_frag_add function in fs/partitions/ldm.c in the Linux kernel before 2.6.39.1 does not properly handle memory allocation for non-initial fragments, which might allow local users to conduct buffer overflow attacks, and gain privileges or obtain sensitive information, via a crafted LDM partition table. NOTE: this... | https://nvd.nist.gov/vuln/detail/CVE-2011-2182 |
29,267 | linux | cae13fe4cc3f24820ffb990c09110626837e85d4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cae13fe4cc3f24820ffb990c09110626837e85d4 | Fix for buffer overflow in ldm_frag_add not sufficient
As Ben Hutchings discovered [1], the patch for CVE-2011-1017 (buffer
overflow in ldm_frag_add) is not sufficient. The original patch in
commit c340b1d64000 ("fs/partitions/ldm.c: fix oops caused by corrupted
partition table") does not consider that, for subsequen... | 0 | static bool ldm_compare_privheads (const struct privhead *ph1,
const struct privhead *ph2)
{
BUG_ON (!ph1 || !ph2);
return ((ph1->ver_major == ph2->ver_major) &&
(ph1->ver_minor == ph2->ver_minor) &&
(ph1->logical_disk_start == ph2->logical_disk_start) &&
(ph1->logical_disk_size == ... | 14,965,633,432,808,446,000,000,000,000,000,000,000 | ldm.c | 193,102,196,756,441,320,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-2182 | The ldm_frag_add function in fs/partitions/ldm.c in the Linux kernel before 2.6.39.1 does not properly handle memory allocation for non-initial fragments, which might allow local users to conduct buffer overflow attacks, and gain privileges or obtain sensitive information, via a crafted LDM partition table. NOTE: this... | https://nvd.nist.gov/vuln/detail/CVE-2011-2182 |
29,268 | linux | cae13fe4cc3f24820ffb990c09110626837e85d4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cae13fe4cc3f24820ffb990c09110626837e85d4 | Fix for buffer overflow in ldm_frag_add not sufficient
As Ben Hutchings discovered [1], the patch for CVE-2011-1017 (buffer
overflow in ldm_frag_add) is not sufficient. The original patch in
commit c340b1d64000 ("fs/partitions/ldm.c: fix oops caused by corrupted
partition table") does not consider that, for subsequen... | 0 | static bool ldm_compare_tocblocks (const struct tocblock *toc1,
const struct tocblock *toc2)
{
BUG_ON (!toc1 || !toc2);
return ((toc1->bitmap1_start == toc2->bitmap1_start) &&
(toc1->bitmap1_size == toc2->bitmap1_size) &&
(toc1->bitmap2_start == toc2->bitmap2_start) &&
(toc1->bitmap2_size == toc2->bit... | 99,522,478,142,241,360,000,000,000,000,000,000,000 | ldm.c | 193,102,196,756,441,320,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-2182 | The ldm_frag_add function in fs/partitions/ldm.c in the Linux kernel before 2.6.39.1 does not properly handle memory allocation for non-initial fragments, which might allow local users to conduct buffer overflow attacks, and gain privileges or obtain sensitive information, via a crafted LDM partition table. NOTE: this... | https://nvd.nist.gov/vuln/detail/CVE-2011-2182 |
29,269 | linux | cae13fe4cc3f24820ffb990c09110626837e85d4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cae13fe4cc3f24820ffb990c09110626837e85d4 | Fix for buffer overflow in ldm_frag_add not sufficient
As Ben Hutchings discovered [1], the patch for CVE-2011-1017 (buffer
overflow in ldm_frag_add) is not sufficient. The original patch in
commit c340b1d64000 ("fs/partitions/ldm.c: fix oops caused by corrupted
partition table") does not consider that, for subsequen... | 0 | static bool ldm_create_data_partitions (struct parsed_partitions *pp,
const struct ldmdb *ldb)
{
struct list_head *item;
struct vblk *vb;
struct vblk *disk;
struct vblk_part *part;
int part_num = 1;
BUG_ON (!pp || !ldb);
disk = ldm_get_disk_objid (ldb);
if (!disk) {
ldm_crit ("Can't find the ID of this... | 193,814,273,475,171,370,000,000,000,000,000,000,000 | ldm.c | 193,102,196,756,441,320,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-2182 | The ldm_frag_add function in fs/partitions/ldm.c in the Linux kernel before 2.6.39.1 does not properly handle memory allocation for non-initial fragments, which might allow local users to conduct buffer overflow attacks, and gain privileges or obtain sensitive information, via a crafted LDM partition table. NOTE: this... | https://nvd.nist.gov/vuln/detail/CVE-2011-2182 |
29,270 | linux | cae13fe4cc3f24820ffb990c09110626837e85d4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cae13fe4cc3f24820ffb990c09110626837e85d4 | Fix for buffer overflow in ldm_frag_add not sufficient
As Ben Hutchings discovered [1], the patch for CVE-2011-1017 (buffer
overflow in ldm_frag_add) is not sufficient. The original patch in
commit c340b1d64000 ("fs/partitions/ldm.c: fix oops caused by corrupted
partition table") does not consider that, for subsequen... | 0 | static bool ldm_frag_commit (struct list_head *frags, struct ldmdb *ldb)
{
struct frag *f;
struct list_head *item;
BUG_ON (!frags || !ldb);
list_for_each (item, frags) {
f = list_entry (item, struct frag, list);
if (f->map != 0xFF) {
ldm_error ("VBLK group %d is incomplete (0x%02x).",
f->group, f->map... | 24,467,191,584,307,684,000,000,000,000,000,000,000 | ldm.c | 193,102,196,756,441,320,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-2182 | The ldm_frag_add function in fs/partitions/ldm.c in the Linux kernel before 2.6.39.1 does not properly handle memory allocation for non-initial fragments, which might allow local users to conduct buffer overflow attacks, and gain privileges or obtain sensitive information, via a crafted LDM partition table. NOTE: this... | https://nvd.nist.gov/vuln/detail/CVE-2011-2182 |
29,271 | linux | cae13fe4cc3f24820ffb990c09110626837e85d4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cae13fe4cc3f24820ffb990c09110626837e85d4 | Fix for buffer overflow in ldm_frag_add not sufficient
As Ben Hutchings discovered [1], the patch for CVE-2011-1017 (buffer
overflow in ldm_frag_add) is not sufficient. The original patch in
commit c340b1d64000 ("fs/partitions/ldm.c: fix oops caused by corrupted
partition table") does not consider that, for subsequen... | 0 | static void ldm_frag_free (struct list_head *list)
{
struct list_head *item, *tmp;
BUG_ON (!list);
list_for_each_safe (item, tmp, list)
kfree (list_entry (item, struct frag, list));
}
| 16,398,320,472,430,605,000,000,000,000,000,000,000 | ldm.c | 193,102,196,756,441,320,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-2182 | The ldm_frag_add function in fs/partitions/ldm.c in the Linux kernel before 2.6.39.1 does not properly handle memory allocation for non-initial fragments, which might allow local users to conduct buffer overflow attacks, and gain privileges or obtain sensitive information, via a crafted LDM partition table. NOTE: this... | https://nvd.nist.gov/vuln/detail/CVE-2011-2182 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.