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,601 | linux | b5b515445f4f5a905c5dd27e6e682868ccd6c09d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b5b515445f4f5a905c5dd27e6e682868ccd6c09d | [SCSI] pmcraid: reject negative request size
There's a code path in pmcraid that can be reached via device ioctl that
causes all sorts of ugliness, including heap corruption or triggering the
OOM killer due to consecutive allocation of large numbers of pages.
First, the user can call pmcraid_chr_ioctl(), with a type
... | 0 | void pmcraid_unregister_interrupt_handler(struct pmcraid_instance *pinstance)
{
int i;
for (i = 0; i < pinstance->num_hrrq; i++)
free_irq(pinstance->hrrq_vector[i].vector,
&(pinstance->hrrq_vector[i]));
if (pinstance->interrupt_mode) {
pci_disable_msix(pinstance->pdev);
pinstance->interrupt_mode = 0;
}
... | 9,713,927,811,461,827,000,000,000,000,000,000,000 | pmcraid.c | 5,320,847,727,715,775,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2011-2906 | Integer signedness error in the pmcraid_ioctl_passthrough function in drivers/scsi/pmcraid.c in the Linux kernel before 3.1 might allow local users to cause a denial of service (memory consumption or memory corruption) via a negative size value in an ioctl call. NOTE: this may be a vulnerability only in unusual environ... | https://nvd.nist.gov/vuln/detail/CVE-2011-2906 |
28,602 | linux | b5b515445f4f5a905c5dd27e6e682868ccd6c09d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b5b515445f4f5a905c5dd27e6e682868ccd6c09d | [SCSI] pmcraid: reject negative request size
There's a code path in pmcraid that can be reached via device ioctl that
causes all sorts of ugliness, including heap corruption or triggering the
OOM killer due to consecutive allocation of large numbers of pages.
First, the user can call pmcraid_chr_ioctl(), with a type
... | 0 | static void pmcraid_worker_function(struct work_struct *workp)
{
struct pmcraid_instance *pinstance;
struct pmcraid_resource_entry *res;
struct pmcraid_resource_entry *temp;
struct scsi_device *sdev;
unsigned long lock_flags;
unsigned long host_lock_flags;
u16 fw_version;
u8 bus, target, lun;
pinstance = cont... | 133,425,728,073,763,080,000,000,000,000,000,000,000 | pmcraid.c | 5,320,847,727,715,775,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2011-2906 | Integer signedness error in the pmcraid_ioctl_passthrough function in drivers/scsi/pmcraid.c in the Linux kernel before 3.1 might allow local users to cause a denial of service (memory consumption or memory corruption) via a negative size value in an ioctl call. NOTE: this may be a vulnerability only in unusual environ... | https://nvd.nist.gov/vuln/detail/CVE-2011-2906 |
28,648 | linux | 0d0138ebe24b94065580bd2601f8bb7eb6152f56 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0d0138ebe24b94065580bd2601f8bb7eb6152f56 | xtensa: prevent arbitrary read in ptrace
Prevent an arbitrary kernel read. Check the user pointer with access_ok()
before copying data in.
[akpm@linux-foundation.org: s/EIO/EFAULT/]
Signed-off-by: Dan Rosenberg <drosenberg@vsecurity.com>
Cc: Christian Zankel <chris@zankel.net>
Cc: Oleg Nesterov <oleg@redhat.com>
Cc:... | 0 | void do_syscall_trace(void)
{
/*
* The 0x80 provides a way for the tracing parent to distinguish
* between a syscall stop and SIGTRAP delivery
*/
ptrace_notify(SIGTRAP|((current->ptrace & PT_TRACESYSGOOD) ? 0x80 : 0));
/*
* this isn't the same as continuing with a signal, but it will do
* for normal use. ... | 116,711,099,543,454,850,000,000,000,000,000,000,000 | ptrace.c | 233,747,206,076,002,530,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-2707 | The ptrace_setxregs function in arch/xtensa/kernel/ptrace.c in the Linux kernel before 3.1 does not validate user-space pointers, which allows local users to obtain sensitive information from kernel memory locations via a crafted PTRACE_SETXTREGS request. | https://nvd.nist.gov/vuln/detail/CVE-2011-2707 |
28,649 | linux | 0d0138ebe24b94065580bd2601f8bb7eb6152f56 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0d0138ebe24b94065580bd2601f8bb7eb6152f56 | xtensa: prevent arbitrary read in ptrace
Prevent an arbitrary kernel read. Check the user pointer with access_ok()
before copying data in.
[akpm@linux-foundation.org: s/EIO/EFAULT/]
Signed-off-by: Dan Rosenberg <drosenberg@vsecurity.com>
Cc: Christian Zankel <chris@zankel.net>
Cc: Oleg Nesterov <oleg@redhat.com>
Cc:... | 0 | void do_syscall_trace_enter(struct pt_regs *regs)
{
if (test_thread_flag(TIF_SYSCALL_TRACE)
&& (current->ptrace & PT_PTRACED))
do_syscall_trace();
#if 0
if (unlikely(current->audit_context))
audit_syscall_entry(current, AUDIT_ARCH_XTENSA..);
#endif
}
| 223,431,770,058,501,350,000,000,000,000,000,000,000 | ptrace.c | 233,747,206,076,002,530,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-2707 | The ptrace_setxregs function in arch/xtensa/kernel/ptrace.c in the Linux kernel before 3.1 does not validate user-space pointers, which allows local users to obtain sensitive information from kernel memory locations via a crafted PTRACE_SETXTREGS request. | https://nvd.nist.gov/vuln/detail/CVE-2011-2707 |
28,650 | linux | 0d0138ebe24b94065580bd2601f8bb7eb6152f56 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0d0138ebe24b94065580bd2601f8bb7eb6152f56 | xtensa: prevent arbitrary read in ptrace
Prevent an arbitrary kernel read. Check the user pointer with access_ok()
before copying data in.
[akpm@linux-foundation.org: s/EIO/EFAULT/]
Signed-off-by: Dan Rosenberg <drosenberg@vsecurity.com>
Cc: Christian Zankel <chris@zankel.net>
Cc: Oleg Nesterov <oleg@redhat.com>
Cc:... | 0 | void do_syscall_trace_leave(struct pt_regs *regs)
{
if ((test_thread_flag(TIF_SYSCALL_TRACE))
&& (current->ptrace & PT_PTRACED))
do_syscall_trace();
}
| 75,710,825,656,452,610,000,000,000,000,000,000,000 | ptrace.c | 233,747,206,076,002,530,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-2707 | The ptrace_setxregs function in arch/xtensa/kernel/ptrace.c in the Linux kernel before 3.1 does not validate user-space pointers, which allows local users to obtain sensitive information from kernel memory locations via a crafted PTRACE_SETXTREGS request. | https://nvd.nist.gov/vuln/detail/CVE-2011-2707 |
28,651 | linux | 0d0138ebe24b94065580bd2601f8bb7eb6152f56 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0d0138ebe24b94065580bd2601f8bb7eb6152f56 | xtensa: prevent arbitrary read in ptrace
Prevent an arbitrary kernel read. Check the user pointer with access_ok()
before copying data in.
[akpm@linux-foundation.org: s/EIO/EFAULT/]
Signed-off-by: Dan Rosenberg <drosenberg@vsecurity.com>
Cc: Christian Zankel <chris@zankel.net>
Cc: Oleg Nesterov <oleg@redhat.com>
Cc:... | 0 | void ptrace_disable(struct task_struct *child)
{
/* Nothing to do.. */
}
| 286,266,123,153,657,770,000,000,000,000,000,000,000 | ptrace.c | 233,747,206,076,002,530,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-2707 | The ptrace_setxregs function in arch/xtensa/kernel/ptrace.c in the Linux kernel before 3.1 does not validate user-space pointers, which allows local users to obtain sensitive information from kernel memory locations via a crafted PTRACE_SETXTREGS request. | https://nvd.nist.gov/vuln/detail/CVE-2011-2707 |
28,652 | linux | 0d0138ebe24b94065580bd2601f8bb7eb6152f56 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0d0138ebe24b94065580bd2601f8bb7eb6152f56 | xtensa: prevent arbitrary read in ptrace
Prevent an arbitrary kernel read. Check the user pointer with access_ok()
before copying data in.
[akpm@linux-foundation.org: s/EIO/EFAULT/]
Signed-off-by: Dan Rosenberg <drosenberg@vsecurity.com>
Cc: Christian Zankel <chris@zankel.net>
Cc: Oleg Nesterov <oleg@redhat.com>
Cc:... | 0 | int ptrace_getregs(struct task_struct *child, void __user *uregs)
{
struct pt_regs *regs = task_pt_regs(child);
xtensa_gregset_t __user *gregset = uregs;
unsigned long wm = regs->wmask;
unsigned long wb = regs->windowbase;
int live, i;
if (!access_ok(VERIFY_WRITE, uregs, sizeof(xtensa_gregset_t)))
return -EIO;... | 266,960,363,786,843,800,000,000,000,000,000,000,000 | ptrace.c | 233,747,206,076,002,530,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-2707 | The ptrace_setxregs function in arch/xtensa/kernel/ptrace.c in the Linux kernel before 3.1 does not validate user-space pointers, which allows local users to obtain sensitive information from kernel memory locations via a crafted PTRACE_SETXTREGS request. | https://nvd.nist.gov/vuln/detail/CVE-2011-2707 |
28,653 | linux | 0d0138ebe24b94065580bd2601f8bb7eb6152f56 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0d0138ebe24b94065580bd2601f8bb7eb6152f56 | xtensa: prevent arbitrary read in ptrace
Prevent an arbitrary kernel read. Check the user pointer with access_ok()
before copying data in.
[akpm@linux-foundation.org: s/EIO/EFAULT/]
Signed-off-by: Dan Rosenberg <drosenberg@vsecurity.com>
Cc: Christian Zankel <chris@zankel.net>
Cc: Oleg Nesterov <oleg@redhat.com>
Cc:... | 0 | int ptrace_getxregs(struct task_struct *child, void __user *uregs)
{
struct pt_regs *regs = task_pt_regs(child);
struct thread_info *ti = task_thread_info(child);
elf_xtregs_t __user *xtregs = uregs;
int ret = 0;
if (!access_ok(VERIFY_WRITE, uregs, sizeof(elf_xtregs_t)))
return -EIO;
#if XTENSA_HAVE_COPROCESSO... | 119,343,053,772,877,670,000,000,000,000,000,000,000 | ptrace.c | 233,747,206,076,002,530,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-2707 | The ptrace_setxregs function in arch/xtensa/kernel/ptrace.c in the Linux kernel before 3.1 does not validate user-space pointers, which allows local users to obtain sensitive information from kernel memory locations via a crafted PTRACE_SETXTREGS request. | https://nvd.nist.gov/vuln/detail/CVE-2011-2707 |
28,654 | linux | 0d0138ebe24b94065580bd2601f8bb7eb6152f56 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0d0138ebe24b94065580bd2601f8bb7eb6152f56 | xtensa: prevent arbitrary read in ptrace
Prevent an arbitrary kernel read. Check the user pointer with access_ok()
before copying data in.
[akpm@linux-foundation.org: s/EIO/EFAULT/]
Signed-off-by: Dan Rosenberg <drosenberg@vsecurity.com>
Cc: Christian Zankel <chris@zankel.net>
Cc: Oleg Nesterov <oleg@redhat.com>
Cc:... | 0 | int ptrace_peekusr(struct task_struct *child, long regno, long __user *ret)
{
struct pt_regs *regs;
unsigned long tmp;
regs = task_pt_regs(child);
tmp = 0; /* Default return value. */
switch(regno) {
case REG_AR_BASE ... REG_AR_BASE + XCHAL_NUM_AREGS - 1:
tmp = regs->areg[regno - REG_AR_BASE];
break;
... | 169,904,428,582,888,830,000,000,000,000,000,000,000 | ptrace.c | 233,747,206,076,002,530,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-2707 | The ptrace_setxregs function in arch/xtensa/kernel/ptrace.c in the Linux kernel before 3.1 does not validate user-space pointers, which allows local users to obtain sensitive information from kernel memory locations via a crafted PTRACE_SETXTREGS request. | https://nvd.nist.gov/vuln/detail/CVE-2011-2707 |
28,655 | linux | 0d0138ebe24b94065580bd2601f8bb7eb6152f56 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0d0138ebe24b94065580bd2601f8bb7eb6152f56 | xtensa: prevent arbitrary read in ptrace
Prevent an arbitrary kernel read. Check the user pointer with access_ok()
before copying data in.
[akpm@linux-foundation.org: s/EIO/EFAULT/]
Signed-off-by: Dan Rosenberg <drosenberg@vsecurity.com>
Cc: Christian Zankel <chris@zankel.net>
Cc: Oleg Nesterov <oleg@redhat.com>
Cc:... | 0 | int ptrace_pokeusr(struct task_struct *child, long regno, long val)
{
struct pt_regs *regs;
regs = task_pt_regs(child);
switch (regno) {
case REG_AR_BASE ... REG_AR_BASE + XCHAL_NUM_AREGS - 1:
regs->areg[regno - REG_AR_BASE] = val;
break;
case REG_A_BASE ... REG_A_BASE + 15:
regs->areg[regno - REG_A_B... | 2,715,785,102,502,374,000,000,000,000,000,000,000 | ptrace.c | 233,747,206,076,002,530,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-2707 | The ptrace_setxregs function in arch/xtensa/kernel/ptrace.c in the Linux kernel before 3.1 does not validate user-space pointers, which allows local users to obtain sensitive information from kernel memory locations via a crafted PTRACE_SETXTREGS request. | https://nvd.nist.gov/vuln/detail/CVE-2011-2707 |
28,656 | linux | 0d0138ebe24b94065580bd2601f8bb7eb6152f56 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0d0138ebe24b94065580bd2601f8bb7eb6152f56 | xtensa: prevent arbitrary read in ptrace
Prevent an arbitrary kernel read. Check the user pointer with access_ok()
before copying data in.
[akpm@linux-foundation.org: s/EIO/EFAULT/]
Signed-off-by: Dan Rosenberg <drosenberg@vsecurity.com>
Cc: Christian Zankel <chris@zankel.net>
Cc: Oleg Nesterov <oleg@redhat.com>
Cc:... | 0 | int ptrace_setregs(struct task_struct *child, void __user *uregs)
{
struct pt_regs *regs = task_pt_regs(child);
xtensa_gregset_t *gregset = uregs;
const unsigned long ps_mask = PS_CALLINC_MASK | PS_OWB_MASK;
unsigned long ps;
unsigned long wb;
if (!access_ok(VERIFY_WRITE, uregs, sizeof(xtensa_gregset_t)))
retu... | 181,722,339,940,502,700,000,000,000,000,000,000,000 | ptrace.c | 233,747,206,076,002,530,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-2707 | The ptrace_setxregs function in arch/xtensa/kernel/ptrace.c in the Linux kernel before 3.1 does not validate user-space pointers, which allows local users to obtain sensitive information from kernel memory locations via a crafted PTRACE_SETXTREGS request. | https://nvd.nist.gov/vuln/detail/CVE-2011-2707 |
28,657 | linux | 0d0138ebe24b94065580bd2601f8bb7eb6152f56 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0d0138ebe24b94065580bd2601f8bb7eb6152f56 | xtensa: prevent arbitrary read in ptrace
Prevent an arbitrary kernel read. Check the user pointer with access_ok()
before copying data in.
[akpm@linux-foundation.org: s/EIO/EFAULT/]
Signed-off-by: Dan Rosenberg <drosenberg@vsecurity.com>
Cc: Christian Zankel <chris@zankel.net>
Cc: Oleg Nesterov <oleg@redhat.com>
Cc:... | 0 | void user_disable_single_step(struct task_struct *child)
{
child->ptrace &= ~PT_SINGLESTEP;
}
| 177,818,778,041,763,740,000,000,000,000,000,000,000 | ptrace.c | 233,747,206,076,002,530,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-2707 | The ptrace_setxregs function in arch/xtensa/kernel/ptrace.c in the Linux kernel before 3.1 does not validate user-space pointers, which allows local users to obtain sensitive information from kernel memory locations via a crafted PTRACE_SETXTREGS request. | https://nvd.nist.gov/vuln/detail/CVE-2011-2707 |
28,658 | linux | 0d0138ebe24b94065580bd2601f8bb7eb6152f56 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0d0138ebe24b94065580bd2601f8bb7eb6152f56 | xtensa: prevent arbitrary read in ptrace
Prevent an arbitrary kernel read. Check the user pointer with access_ok()
before copying data in.
[akpm@linux-foundation.org: s/EIO/EFAULT/]
Signed-off-by: Dan Rosenberg <drosenberg@vsecurity.com>
Cc: Christian Zankel <chris@zankel.net>
Cc: Oleg Nesterov <oleg@redhat.com>
Cc:... | 0 | void user_enable_single_step(struct task_struct *child)
{
child->ptrace |= PT_SINGLESTEP;
}
| 295,618,801,613,271,150,000,000,000,000,000,000,000 | ptrace.c | 233,747,206,076,002,530,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-2707 | The ptrace_setxregs function in arch/xtensa/kernel/ptrace.c in the Linux kernel before 3.1 does not validate user-space pointers, which allows local users to obtain sensitive information from kernel memory locations via a crafted PTRACE_SETXTREGS request. | https://nvd.nist.gov/vuln/detail/CVE-2011-2707 |
28,686 | linux | fc66c5210ec2539e800e87d7b3a985323c7be96e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fc66c5210ec2539e800e87d7b3a985323c7be96e | perf, x86: Fix Intel fixed counters base initialization
The following patch solves the problems introduced by Robert's
commit 41bf498 and reported by Arun Sharma. This commit gets rid
of the base + index notation for reading and writing PMU msrs.
The problem is that for fixed counters, the new calculation for
the bas... | 0 | static void backtrace_warning(void *data, char *msg)
{
/* Ignore warnings */
}
| 52,567,902,929,427,510,000,000,000,000,000,000,000 | perf_event.c | 188,501,751,316,886,220,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2011-2521 | The x86_assign_hw_event function in arch/x86/kernel/cpu/perf_event.c in the Performance Events subsystem in the Linux kernel before 2.6.39 does not properly calculate counter values, which allows local users to cause a denial of service (panic) via the perf program. | https://nvd.nist.gov/vuln/detail/CVE-2011-2521 |
28,687 | linux | fc66c5210ec2539e800e87d7b3a985323c7be96e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fc66c5210ec2539e800e87d7b3a985323c7be96e | perf, x86: Fix Intel fixed counters base initialization
The following patch solves the problems introduced by Robert's
commit 41bf498 and reported by Arun Sharma. This commit gets rid
of the base + index notation for reading and writing PMU msrs.
The problem is that for fixed counters, the new calculation for
the bas... | 0 | static bool check_hw_exists(void)
{
u64 val, val_new = 0;
int i, reg, ret = 0;
/*
* Check to see if the BIOS enabled any of the counters, if so
* complain and bail.
*/
for (i = 0; i < x86_pmu.num_counters; i++) {
reg = x86_pmu_config_addr(i);
ret = rdmsrl_safe(reg, &val);
if (ret)
goto msr_fail;
i... | 190,934,564,305,270,600,000,000,000,000,000,000,000 | perf_event.c | 188,501,751,316,886,220,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2011-2521 | The x86_assign_hw_event function in arch/x86/kernel/cpu/perf_event.c in the Performance Events subsystem in the Linux kernel before 2.6.39 does not properly calculate counter values, which allows local users to cause a denial of service (panic) via the perf program. | https://nvd.nist.gov/vuln/detail/CVE-2011-2521 |
28,688 | linux | fc66c5210ec2539e800e87d7b3a985323c7be96e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fc66c5210ec2539e800e87d7b3a985323c7be96e | perf, x86: Fix Intel fixed counters base initialization
The following patch solves the problems introduced by Robert's
commit 41bf498 and reported by Arun Sharma. This commit gets rid
of the base + index notation for reading and writing PMU msrs.
The problem is that for fixed counters, the new calculation for
the bas... | 0 | perf_event_nmi_handler(struct notifier_block *self,
unsigned long cmd, void *__args)
{
struct die_args *args = __args;
unsigned int this_nmi;
int handled;
if (!atomic_read(&active_events))
return NOTIFY_DONE;
switch (cmd) {
case DIE_NMI:
break;
case DIE_NMIUNKNOWN:
this_nmi = percpu_read(irq_stat.__n... | 298,338,354,259,950,000,000,000,000,000,000,000,000 | perf_event.c | 188,501,751,316,886,220,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2011-2521 | The x86_assign_hw_event function in arch/x86/kernel/cpu/perf_event.c in the Performance Events subsystem in the Linux kernel before 2.6.39 does not properly calculate counter values, which allows local users to cause a denial of service (panic) via the perf program. | https://nvd.nist.gov/vuln/detail/CVE-2011-2521 |
28,689 | linux | fc66c5210ec2539e800e87d7b3a985323c7be96e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fc66c5210ec2539e800e87d7b3a985323c7be96e | perf, x86: Fix Intel fixed counters base initialization
The following patch solves the problems introduced by Robert's
commit 41bf498 and reported by Arun Sharma. This commit gets rid
of the base + index notation for reading and writing PMU msrs.
The problem is that for fixed counters, the new calculation for
the bas... | 0 | static int x86_pmu_add(struct perf_event *event, int flags)
{
struct cpu_hw_events *cpuc = &__get_cpu_var(cpu_hw_events);
struct hw_perf_event *hwc;
int assign[X86_PMC_IDX_MAX];
int n, n0, ret;
hwc = &event->hw;
perf_pmu_disable(event->pmu);
n0 = cpuc->n_events;
ret = n = collect_events(cpuc, event, false);
... | 284,725,963,753,607,000,000,000,000,000,000,000,000 | perf_event.c | 188,501,751,316,886,220,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2011-2521 | The x86_assign_hw_event function in arch/x86/kernel/cpu/perf_event.c in the Performance Events subsystem in the Linux kernel before 2.6.39 does not properly calculate counter values, which allows local users to cause a denial of service (panic) via the perf program. | https://nvd.nist.gov/vuln/detail/CVE-2011-2521 |
28,690 | linux | fc66c5210ec2539e800e87d7b3a985323c7be96e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fc66c5210ec2539e800e87d7b3a985323c7be96e | perf, x86: Fix Intel fixed counters base initialization
The following patch solves the problems introduced by Robert's
commit 41bf498 and reported by Arun Sharma. This commit gets rid
of the base + index notation for reading and writing PMU msrs.
The problem is that for fixed counters, the new calculation for
the bas... | 0 | static inline int x86_pmu_addr_offset(int index)
{
if (boot_cpu_has(X86_FEATURE_PERFCTR_CORE))
return index << 1;
return index;
}
| 209,179,166,674,292,480,000,000,000,000,000,000,000 | perf_event.c | 188,501,751,316,886,220,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2011-2521 | The x86_assign_hw_event function in arch/x86/kernel/cpu/perf_event.c in the Performance Events subsystem in the Linux kernel before 2.6.39 does not properly calculate counter values, which allows local users to cause a denial of service (panic) via the perf program. | https://nvd.nist.gov/vuln/detail/CVE-2011-2521 |
28,691 | linux | fc66c5210ec2539e800e87d7b3a985323c7be96e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fc66c5210ec2539e800e87d7b3a985323c7be96e | perf, x86: Fix Intel fixed counters base initialization
The following patch solves the problems introduced by Robert's
commit 41bf498 and reported by Arun Sharma. This commit gets rid
of the base + index notation for reading and writing PMU msrs.
The problem is that for fixed counters, the new calculation for
the bas... | 0 | static int x86_pmu_handle_irq(struct pt_regs *regs)
{
struct perf_sample_data data;
struct cpu_hw_events *cpuc;
struct perf_event *event;
int idx, handled = 0;
u64 val;
perf_sample_data_init(&data, 0);
cpuc = &__get_cpu_var(cpu_hw_events);
for (idx = 0; idx < x86_pmu.num_counters; idx++) {
if (!test_bit(id... | 76,202,822,923,359,910,000,000,000,000,000,000,000 | perf_event.c | 188,501,751,316,886,220,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2011-2521 | The x86_assign_hw_event function in arch/x86/kernel/cpu/perf_event.c in the Performance Events subsystem in the Linux kernel before 2.6.39 does not properly calculate counter values, which allows local users to cause a denial of service (panic) via the perf program. | https://nvd.nist.gov/vuln/detail/CVE-2011-2521 |
28,692 | linux | fc66c5210ec2539e800e87d7b3a985323c7be96e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fc66c5210ec2539e800e87d7b3a985323c7be96e | perf, x86: Fix Intel fixed counters base initialization
The following patch solves the problems introduced by Robert's
commit 41bf498 and reported by Arun Sharma. This commit gets rid
of the base + index notation for reading and writing PMU msrs.
The problem is that for fixed counters, the new calculation for
the bas... | 0 | static int x86_setup_perfctr(struct perf_event *event)
{
struct perf_event_attr *attr = &event->attr;
struct hw_perf_event *hwc = &event->hw;
u64 config;
if (!is_sampling_event(event)) {
hwc->sample_period = x86_pmu.max_period;
hwc->last_period = hwc->sample_period;
local64_set(&hwc->period_left, hwc->sample... | 191,008,817,903,166,030,000,000,000,000,000,000,000 | perf_event.c | 188,501,751,316,886,220,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2011-2521 | The x86_assign_hw_event function in arch/x86/kernel/cpu/perf_event.c in the Performance Events subsystem in the Linux kernel before 2.6.39 does not properly calculate counter values, which allows local users to cause a denial of service (panic) via the perf program. | https://nvd.nist.gov/vuln/detail/CVE-2011-2521 |
28,693 | linux | 4e78c724d47e2342aa8fde61f6b8536f662f795f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4e78c724d47e2342aa8fde61f6b8536f662f795f | TOMOYO: Fix oops in tomoyo_mount_acl().
In tomoyo_mount_acl() since 2.6.36, kern_path() was called without checking
dev_name != NULL. As a result, an unprivileged user can trigger oops by issuing
mount(NULL, "/", "ext3", 0, NULL) request.
Fix this by checking dev_name != NULL before calling kern_path(dev_name).
Signe... | 0 | int tomoyo_mount_permission(char *dev_name, struct path *path, char *type,
unsigned long flags, void *data_page)
{
struct tomoyo_request_info r;
int error;
int idx;
if (tomoyo_init_request_info(&r, NULL, TOMOYO_MAC_FILE_MOUNT)
== TOMOYO_CONFIG_DISABLED)
return 0;
if ((flags & MS_MGC_MSK) == MS_MGC_V... | 33,216,479,416,895,265,000,000,000,000,000,000,000 | mount.c | 8,263,568,831,189,900,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-2518 | The tomoyo_mount_acl function in security/tomoyo/mount.c in the Linux kernel before 2.6.39.2 calls the kern_path function with arguments taken directly from a mount system call, which allows local users to cause a denial of service (OOPS) or possibly have unspecified other impact via a NULL value for the device name. | https://nvd.nist.gov/vuln/detail/CVE-2011-2518 |
28,694 | linux | 4e78c724d47e2342aa8fde61f6b8536f662f795f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4e78c724d47e2342aa8fde61f6b8536f662f795f | TOMOYO: Fix oops in tomoyo_mount_acl().
In tomoyo_mount_acl() since 2.6.36, kern_path() was called without checking
dev_name != NULL. As a result, an unprivileged user can trigger oops by issuing
mount(NULL, "/", "ext3", 0, NULL) request.
Fix this by checking dev_name != NULL before calling kern_path(dev_name).
Signe... | 0 | static bool tomoyo_same_mount_acl(const struct tomoyo_acl_info *a,
const struct tomoyo_acl_info *b)
{
const struct tomoyo_mount_acl *p1 = container_of(a, typeof(*p1), head);
const struct tomoyo_mount_acl *p2 = container_of(b, typeof(*p2), head);
return tomoyo_same_acl_head(&p1->head, &p2->head) &&
tomoyo_sam... | 312,167,932,804,343,930,000,000,000,000,000,000,000 | mount.c | 8,263,568,831,189,900,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-2518 | The tomoyo_mount_acl function in security/tomoyo/mount.c in the Linux kernel before 2.6.39.2 calls the kern_path function with arguments taken directly from a mount system call, which allows local users to cause a denial of service (OOPS) or possibly have unspecified other impact via a NULL value for the device name. | https://nvd.nist.gov/vuln/detail/CVE-2011-2518 |
28,695 | linux | 4e78c724d47e2342aa8fde61f6b8536f662f795f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4e78c724d47e2342aa8fde61f6b8536f662f795f | TOMOYO: Fix oops in tomoyo_mount_acl().
In tomoyo_mount_acl() since 2.6.36, kern_path() was called without checking
dev_name != NULL. As a result, an unprivileged user can trigger oops by issuing
mount(NULL, "/", "ext3", 0, NULL) request.
Fix this by checking dev_name != NULL before calling kern_path(dev_name).
Signe... | 0 | int tomoyo_write_mount(char *data, struct tomoyo_domain_info *domain,
const bool is_delete)
{
struct tomoyo_mount_acl e = { .head.type = TOMOYO_TYPE_MOUNT_ACL };
int error = is_delete ? -ENOENT : -ENOMEM;
char *w[4];
if (!tomoyo_tokenize(data, w, sizeof(w)) || !w[3][0])
return -EINVAL;
if (!tomoyo_parse... | 47,540,341,082,602,890,000,000,000,000,000,000,000 | mount.c | 8,263,568,831,189,900,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-2518 | The tomoyo_mount_acl function in security/tomoyo/mount.c in the Linux kernel before 2.6.39.2 calls the kern_path function with arguments taken directly from a mount system call, which allows local users to cause a denial of service (OOPS) or possibly have unspecified other impact via a NULL value for the device name. | https://nvd.nist.gov/vuln/detail/CVE-2011-2518 |
28,823 | linux | 982134ba62618c2d69fbbbd166d0a11ee3b7e3d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/982134ba62618c2d69fbbbd166d0a11ee3b7e3d8 | mm: avoid wrapping vm_pgoff in mremap()
The normal mmap paths all avoid creating a mapping where the pgoff
inside the mapping could wrap around due to overflow. However, an
expanding mremap() can take such a non-wrapping mapping and make it
bigger and cause a wrapping condition.
Noticed by Robert Swiecki when runnin... | 0 | SYSCALL_DEFINE5(mremap, unsigned long, addr, unsigned long, old_len,
unsigned long, new_len, unsigned long, flags,
unsigned long, new_addr)
{
unsigned long ret;
down_write(¤t->mm->mmap_sem);
ret = do_mremap(addr, old_len, new_len, flags, new_addr);
up_write(¤t->mm->mmap_sem);
return ret;
}
| 117,881,271,027,442,040,000,000,000,000,000,000,000 | mremap.c | 191,286,780,299,224,640,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2011-2496 | Integer overflow in the vma_to_resize function in mm/mremap.c in the Linux kernel before 2.6.39 allows local users to cause a denial of service (BUG_ON and system crash) via a crafted mremap system call that expands a memory mapping. | https://nvd.nist.gov/vuln/detail/CVE-2011-2496 |
28,824 | linux | 982134ba62618c2d69fbbbd166d0a11ee3b7e3d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/982134ba62618c2d69fbbbd166d0a11ee3b7e3d8 | mm: avoid wrapping vm_pgoff in mremap()
The normal mmap paths all avoid creating a mapping where the pgoff
inside the mapping could wrap around due to overflow. However, an
expanding mremap() can take such a non-wrapping mapping and make it
bigger and cause a wrapping condition.
Noticed by Robert Swiecki when runnin... | 0 | static pmd_t *alloc_new_pmd(struct mm_struct *mm, struct vm_area_struct *vma,
unsigned long addr)
{
pgd_t *pgd;
pud_t *pud;
pmd_t *pmd;
pgd = pgd_offset(mm, addr);
pud = pud_alloc(mm, pgd, addr);
if (!pud)
return NULL;
pmd = pmd_alloc(mm, pud, addr);
if (!pmd)
return NULL;
VM_BUG_ON(pmd_trans_hug... | 231,689,658,745,528,250,000,000,000,000,000,000,000 | mremap.c | 191,286,780,299,224,640,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2011-2496 | Integer overflow in the vma_to_resize function in mm/mremap.c in the Linux kernel before 2.6.39 allows local users to cause a denial of service (BUG_ON and system crash) via a crafted mremap system call that expands a memory mapping. | https://nvd.nist.gov/vuln/detail/CVE-2011-2496 |
28,825 | linux | 982134ba62618c2d69fbbbd166d0a11ee3b7e3d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/982134ba62618c2d69fbbbd166d0a11ee3b7e3d8 | mm: avoid wrapping vm_pgoff in mremap()
The normal mmap paths all avoid creating a mapping where the pgoff
inside the mapping could wrap around due to overflow. However, an
expanding mremap() can take such a non-wrapping mapping and make it
bigger and cause a wrapping condition.
Noticed by Robert Swiecki when runnin... | 0 | unsigned long do_mremap(unsigned long addr,
unsigned long old_len, unsigned long new_len,
unsigned long flags, unsigned long new_addr)
{
struct mm_struct *mm = current->mm;
struct vm_area_struct *vma;
unsigned long ret = -EINVAL;
unsigned long charged = 0;
if (flags & ~(MREMAP_FIXED | MREMAP_MAYMOVE))
goto ou... | 124,408,323,639,437,740,000,000,000,000,000,000,000 | mremap.c | 191,286,780,299,224,640,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2011-2496 | Integer overflow in the vma_to_resize function in mm/mremap.c in the Linux kernel before 2.6.39 allows local users to cause a denial of service (BUG_ON and system crash) via a crafted mremap system call that expands a memory mapping. | https://nvd.nist.gov/vuln/detail/CVE-2011-2496 |
28,826 | linux | 982134ba62618c2d69fbbbd166d0a11ee3b7e3d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/982134ba62618c2d69fbbbd166d0a11ee3b7e3d8 | mm: avoid wrapping vm_pgoff in mremap()
The normal mmap paths all avoid creating a mapping where the pgoff
inside the mapping could wrap around due to overflow. However, an
expanding mremap() can take such a non-wrapping mapping and make it
bigger and cause a wrapping condition.
Noticed by Robert Swiecki when runnin... | 0 | unsigned long move_page_tables(struct vm_area_struct *vma,
unsigned long old_addr, struct vm_area_struct *new_vma,
unsigned long new_addr, unsigned long len)
{
unsigned long extent, next, old_end;
pmd_t *old_pmd, *new_pmd;
old_end = old_addr + len;
flush_cache_range(vma, old_addr, old_end);
for (; old_addr <... | 119,465,115,453,888,340,000,000,000,000,000,000,000 | mremap.c | 191,286,780,299,224,640,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2011-2496 | Integer overflow in the vma_to_resize function in mm/mremap.c in the Linux kernel before 2.6.39 allows local users to cause a denial of service (BUG_ON and system crash) via a crafted mremap system call that expands a memory mapping. | https://nvd.nist.gov/vuln/detail/CVE-2011-2496 |
28,827 | linux | 982134ba62618c2d69fbbbd166d0a11ee3b7e3d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/982134ba62618c2d69fbbbd166d0a11ee3b7e3d8 | mm: avoid wrapping vm_pgoff in mremap()
The normal mmap paths all avoid creating a mapping where the pgoff
inside the mapping could wrap around due to overflow. However, an
expanding mremap() can take such a non-wrapping mapping and make it
bigger and cause a wrapping condition.
Noticed by Robert Swiecki when runnin... | 0 | static void move_ptes(struct vm_area_struct *vma, pmd_t *old_pmd,
unsigned long old_addr, unsigned long old_end,
struct vm_area_struct *new_vma, pmd_t *new_pmd,
unsigned long new_addr)
{
struct address_space *mapping = NULL;
struct mm_struct *mm = vma->vm_mm;
pte_t *old_pte, *new_pte, pte;
spinlock_t *old_ptl... | 39,499,448,690,742,143,000,000,000,000,000,000,000 | mremap.c | 191,286,780,299,224,640,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2011-2496 | Integer overflow in the vma_to_resize function in mm/mremap.c in the Linux kernel before 2.6.39 allows local users to cause a denial of service (BUG_ON and system crash) via a crafted mremap system call that expands a memory mapping. | https://nvd.nist.gov/vuln/detail/CVE-2011-2496 |
28,828 | linux | 982134ba62618c2d69fbbbd166d0a11ee3b7e3d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/982134ba62618c2d69fbbbd166d0a11ee3b7e3d8 | mm: avoid wrapping vm_pgoff in mremap()
The normal mmap paths all avoid creating a mapping where the pgoff
inside the mapping could wrap around due to overflow. However, an
expanding mremap() can take such a non-wrapping mapping and make it
bigger and cause a wrapping condition.
Noticed by Robert Swiecki when runnin... | 0 | static unsigned long move_vma(struct vm_area_struct *vma,
unsigned long old_addr, unsigned long old_len,
unsigned long new_len, unsigned long new_addr)
{
struct mm_struct *mm = vma->vm_mm;
struct vm_area_struct *new_vma;
unsigned long vm_flags = vma->vm_flags;
unsigned long new_pgoff;
unsigned long moved_len;
... | 139,272,049,155,509,500,000,000,000,000,000,000,000 | mremap.c | 191,286,780,299,224,640,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2011-2496 | Integer overflow in the vma_to_resize function in mm/mremap.c in the Linux kernel before 2.6.39 allows local users to cause a denial of service (BUG_ON and system crash) via a crafted mremap system call that expands a memory mapping. | https://nvd.nist.gov/vuln/detail/CVE-2011-2496 |
28,829 | linux | 982134ba62618c2d69fbbbd166d0a11ee3b7e3d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/982134ba62618c2d69fbbbd166d0a11ee3b7e3d8 | mm: avoid wrapping vm_pgoff in mremap()
The normal mmap paths all avoid creating a mapping where the pgoff
inside the mapping could wrap around due to overflow. However, an
expanding mremap() can take such a non-wrapping mapping and make it
bigger and cause a wrapping condition.
Noticed by Robert Swiecki when runnin... | 0 | static unsigned long mremap_to(unsigned long addr,
unsigned long old_len, unsigned long new_addr,
unsigned long new_len)
{
struct mm_struct *mm = current->mm;
struct vm_area_struct *vma;
unsigned long ret = -EINVAL;
unsigned long charged = 0;
unsigned long map_flags;
if (new_addr & ~PAGE_MASK)
goto out;
if... | 326,827,103,882,411,840,000,000,000,000,000,000,000 | mremap.c | 191,286,780,299,224,640,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2011-2496 | Integer overflow in the vma_to_resize function in mm/mremap.c in the Linux kernel before 2.6.39 allows local users to cause a denial of service (BUG_ON and system crash) via a crafted mremap system call that expands a memory mapping. | https://nvd.nist.gov/vuln/detail/CVE-2011-2496 |
28,830 | 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 mm_struct *__check_mem_permission(struct task_struct *task)
{
struct mm_struct *mm;
mm = get_task_mm(task);
if (!mm)
return ERR_PTR(-EINVAL);
/*
* A task can always look at itself, in case it chooses
* to use system calls instead of load instructions.
*/
if (task == current)
return mm;
... | 328,678,509,721,344,570,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,831 | 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 mm_struct *check_mem_permission(struct task_struct *task)
{
struct mm_struct *mm;
int err;
/*
* Avoid racing if task exec's as we might get a new mm but validate
* against old credentials.
*/
err = mutex_lock_killable(&task->signal->cred_guard_mutex);
if (err)
return ERR_PTR(err);
mm = __c... | 134,283,619,187,619,570,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,832 | 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 comm_open(struct inode *inode, struct file *filp)
{
return single_open(filp, comm_show, inode);
}
| 282,915,051,777,625,100,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,833 | 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 comm_show(struct seq_file *m, void *v)
{
struct inode *inode = m->private;
struct task_struct *p;
p = get_proc_task(inode);
if (!p)
return -ESRCH;
task_lock(p);
seq_printf(m, "%s\n", p->comm);
task_unlock(p);
put_task_struct(p);
return 0;
}
| 44,113,981,518,569,460,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,834 | 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 comm_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[TASK_COMM_LEN];
memset(buffer, 0, sizeof(buffer));
if (count > sizeof(buffer) - 1)
count = sizeof(buffer) - 1;
if (copy... | 26,788,528,643,315,548,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,835 | 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 do_proc_readlink(struct path *path, char __user *buffer, int buflen)
{
char *tmp = (char*)__get_free_page(GFP_TEMPORARY);
char *pathname;
int len;
if (!tmp)
return -ENOMEM;
pathname = d_path(path, tmp, PAGE_SIZE);
len = PTR_ERR(pathname);
if (IS_ERR(pathname))
goto out;
len = tmp + PAGE_SIZE - ... | 30,826,599,570,329,560,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,836 | 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 environ_read(struct file *file, char __user *buf,
size_t count, loff_t *ppos)
{
struct task_struct *task = get_proc_task(file->f_dentry->d_inode);
char *page;
unsigned long src = *ppos;
int ret = -ESRCH;
struct mm_struct *mm;
if (!task)
goto out_no_task;
ret = -ENOMEM;
page = (char *)__get... | 67,014,582,427,412,340,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,837 | 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 task_struct *first_tid(struct task_struct *leader,
int tid, int nr, struct pid_namespace *ns)
{
struct task_struct *pos;
rcu_read_lock();
/* Attempt to start with the pid of a thread */
if (tid && (nr > 0)) {
pos = find_task_by_pid_ns(tid, ns);
if (pos && (pos->group_leader == leader))
goto ... | 113,746,198,939,869,910,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,838 | 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 get_task_root(struct task_struct *task, struct path *root)
{
int result = -ENOENT;
task_lock(task);
if (task->fs) {
get_fs_root(task->fs, root);
result = 0;
}
task_unlock(task);
return result;
}
| 34,320,991,170,866,826,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,839 | 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 lstats_show_proc(struct seq_file *m, void *v)
{
int i;
struct inode *inode = m->private;
struct task_struct *task = get_proc_task(inode);
if (!task)
return -ESRCH;
seq_puts(m, "Latency Top version : v0.1\n");
for (i = 0; i < 32; i++) {
struct latency_record *lr = &task->latency_record[i];
if (lr... | 302,485,199,952,959,340,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,840 | 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 | loff_t mem_lseek(struct file *file, loff_t offset, int orig)
{
switch (orig) {
case 0:
file->f_pos = offset;
break;
case 1:
file->f_pos += offset;
break;
default:
return -EINVAL;
}
force_successful_syscall_return();
return file->f_pos;
}
| 41,160,552,357,080,760,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,841 | 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 mem_open(struct inode* inode, struct file* file)
{
file->private_data = (void*)((long)current->self_exec_id);
/* OK to pass negative loff_t, we can catch out-of-range */
file->f_mode |= FMODE_UNSIGNED_OFFSET;
return 0;
}
| 132,900,747,483,627,240,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,842 | 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 mem_read(struct file * file, char __user * buf,
size_t count, loff_t *ppos)
{
struct task_struct *task = get_proc_task(file->f_path.dentry->d_inode);
char *page;
unsigned long src = *ppos;
int ret = -ESRCH;
struct mm_struct *mm;
if (!task)
goto out_no_task;
ret = -ENOMEM;
page = (char *)__... | 191,553,743,917,889,640,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,843 | 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 mem_write(struct file * file, const char __user *buf,
size_t count, loff_t *ppos)
{
int copied;
char *page;
struct task_struct *task = get_proc_task(file->f_path.dentry->d_inode);
unsigned long dst = *ppos;
struct mm_struct *mm;
copied = -ESRCH;
if (!task)
goto out_no_task;
copied = -ENOM... | 55,125,781,824,444,440,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,844 | 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 | struct mm_struct *mm_for_maps(struct task_struct *task)
{
struct mm_struct *mm;
int err;
err = mutex_lock_killable(&task->signal->cred_guard_mutex);
if (err)
return ERR_PTR(err);
mm = get_task_mm(task);
if (mm && mm != current->mm &&
!ptrace_may_access(task, PTRACE_MODE_READ)) {
mmput(mm);
mm = ERR_PT... | 2,849,747,257,301,408,500,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,845 | 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 mountinfo_open(struct inode *inode, struct file *file)
{
return mounts_open_common(inode, file, &mountinfo_op);
}
| 139,017,087,727,677,500,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,846 | 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 mounts_open(struct inode *inode, struct file *file)
{
return mounts_open_common(inode, file, &mounts_op);
}
| 44,813,398,649,309,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,847 | 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 mounts_open_common(struct inode *inode, struct file *file,
const struct seq_operations *op)
{
struct task_struct *task = get_proc_task(inode);
struct nsproxy *nsp;
struct mnt_namespace *ns = NULL;
struct path root;
struct proc_mounts *p;
int ret = -EINVAL;
if (task) {
rcu_read_lock();
ns... | 76,424,578,571,699,960,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,848 | 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 unsigned mounts_poll(struct file *file, poll_table *wait)
{
struct proc_mounts *p = file->private_data;
unsigned res = POLLIN | POLLRDNORM;
poll_wait(file, &p->ns->poll, wait);
if (mnt_had_events(p))
res |= POLLERR | POLLPRI;
return res;
}
| 281,677,783,949,358,840,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,849 | 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 mounts_release(struct inode *inode, struct file *file)
{
struct proc_mounts *p = file->private_data;
path_put(&p->root);
put_mnt_ns(p->ns);
return seq_release(inode, file);
}
| 45,235,125,055,080,580,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,850 | 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 mountstats_open(struct inode *inode, struct file *file)
{
return mounts_open_common(inode, file, &mountstats_op);
}
| 45,685,118,018,196,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,851 | 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 unsigned name_to_int(struct dentry *dentry)
{
const char *name = dentry->d_name.name;
int len = dentry->d_name.len;
unsigned n = 0;
if (len > 1 && *name == '0')
goto out;
while (len-- > 0) {
unsigned c = *name++ - '0';
if (c > 9)
goto out;
if (n >= (~0U-9)/10)
goto out;
n *= 10;
n += c;
... | 227,518,259,685,000,040,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,852 | 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 tgid_iter next_tgid(struct pid_namespace *ns, struct tgid_iter iter)
{
struct pid *pid;
if (iter.task)
put_task_struct(iter.task);
rcu_read_lock();
retry:
iter.task = NULL;
pid = find_ge_pid(iter.tgid, ns);
if (pid) {
iter.tgid = pid_nr_ns(pid, ns);
iter.task = pid_task(pid, PIDTYPE_PID);
/... | 61,452,095,810,102,330,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,853 | 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 task_struct *next_tid(struct task_struct *start)
{
struct task_struct *pos = NULL;
rcu_read_lock();
if (pid_alive(start)) {
pos = next_thread(start);
if (thread_group_leader(pos))
pos = NULL;
else
get_task_struct(pos);
}
rcu_read_unlock();
put_task_struct(start);
return pos;
}
| 57,737,774,584,224,050,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,854 | 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 oom_adjust_read(struct file *file, char __user *buf,
size_t count, loff_t *ppos)
{
struct task_struct *task = get_proc_task(file->f_path.dentry->d_inode);
char buffer[PROC_NUMBUF];
size_t len;
int oom_adjust = OOM_DISABLE;
unsigned long flags;
if (!task)
return -ESRCH;
if (lock_task_sighan... | 224,384,312,200,076,000,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,855 | 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 oom_score_adj_read(struct file *file, char __user *buf,
size_t count, loff_t *ppos)
{
struct task_struct *task = get_proc_task(file->f_path.dentry->d_inode);
char buffer[PROC_NUMBUF];
int oom_score_adj = OOM_SCORE_ADJ_MIN;
unsigned long flags;
size_t len;
if (!task)
return -ESRCH;
if (lock... | 369,221,460,873,453,600,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,856 | 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 pid_delete_dentry(const struct dentry * dentry)
{
/* Is the task we represent dead?
* If so, then don't put the dentry on the lru list,
* kill it immediately.
*/
return !proc_pid(dentry->d_inode)->tasks[PIDTYPE_PID].first;
}
| 253,973,953,638,070,950,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,857 | 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 unsigned int pid_entry_count_dirs(const struct pid_entry *entries,
unsigned int n)
{
unsigned int i;
unsigned int count;
count = 0;
for (i = 0; i < n; ++i) {
if (S_ISDIR(entries[i].mode))
++count;
}
return count;
}
| 336,837,449,964,926,300,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,858 | 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 pid_getattr(struct vfsmount *mnt, struct dentry *dentry, struct kstat *stat)
{
struct inode *inode = dentry->d_inode;
struct task_struct *task;
const struct cred *cred;
generic_fillattr(inode, stat);
rcu_read_lock();
stat->uid = 0;
stat->gid = 0;
task = pid_task(proc_pid(inode), PIDTYPE_PID);
if (task) {... | 93,862,429,769,092,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,859 | 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_attr_dir_lookup(struct inode *dir,
struct dentry *dentry, struct nameidata *nd)
{
return proc_pident_lookup(dir, dentry,
attr_dir_stuff, ARRAY_SIZE(attr_dir_stuff));
}
| 300,467,620,995,443,450,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,860 | 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_attr_dir_readdir(struct file * filp,
void * dirent, filldir_t filldir)
{
return proc_pident_readdir(filp,dirent,filldir,
attr_dir_stuff,ARRAY_SIZE(attr_dir_stuff));
}
| 268,104,078,869,045,500,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,861 | 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_base_instantiate(struct inode *dir,
struct dentry *dentry, struct task_struct *task, const void *ptr)
{
const struct pid_entry *p = ptr;
struct inode *inode;
struct proc_inode *ei;
struct dentry *error;
/* Allocate the inode */
error = ERR_PTR(-ENOMEM);
inode = new_inode(dir->i_sb);
... | 200,627,719,101,777,970,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,862 | 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_base_lookup(struct inode *dir, struct dentry *dentry)
{
struct dentry *error;
struct task_struct *task = get_proc_task(dir);
const struct pid_entry *p, *last;
error = ERR_PTR(-ENOENT);
if (!task)
goto out_no_task;
/* Lookup the directory entry */
last = &proc_base_stuff[ARRAY_SIZE... | 98,014,233,228,354,250,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,863 | 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_coredump_filter_read(struct file *file, char __user *buf,
size_t count, loff_t *ppos)
{
struct task_struct *task = get_proc_task(file->f_dentry->d_inode);
struct mm_struct *mm;
char buffer[PROC_NUMBUF];
size_t len;
int ret;
if (!task)
return -ESRCH;
ret = 0;
mm = get_task_mm(task);... | 80,489,048,421,103,260,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,864 | 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_coredump_filter_write(struct file *file,
const char __user *buf,
size_t count,
loff_t *ppos)
{
struct task_struct *task;
struct mm_struct *mm;
char buffer[PROC_NUMBUF], *end;
unsigned int val;
int ret;
int i;
unsigned long mask;
ret = -EFAULT;
memset(buffer, 0, sizeof(... | 35,657,362,540,990,660,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,865 | 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_cwd_link(struct inode *inode, struct path *path)
{
struct task_struct *task = get_proc_task(inode);
int result = -ENOENT;
if (task) {
task_lock(task);
if (task->fs) {
get_fs_pwd(task->fs, path);
result = 0;
}
task_unlock(task);
put_task_struct(task);
}
return result;
}
| 171,165,477,187,180,540,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,866 | 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_exe_link(struct inode *inode, struct path *exe_path)
{
struct task_struct *task;
struct mm_struct *mm;
struct file *exe_file;
task = get_proc_task(inode);
if (!task)
return -ENOENT;
mm = get_task_mm(task);
put_task_struct(task);
if (!mm)
return -ENOENT;
exe_file = get_mm_exe_file(mm);
mmp... | 269,444,019,368,899,860,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,867 | 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_fault_inject_read(struct file * file, char __user * buf,
size_t count, loff_t *ppos)
{
struct task_struct *task = get_proc_task(file->f_dentry->d_inode);
char buffer[PROC_NUMBUF];
size_t len;
int make_it_fail;
if (!task)
return -ESRCH;
make_it_fail = task->make_it_fail;
put_task_... | 161,679,153,474,768,600,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,868 | 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_fault_inject_write(struct file * file,
const char __user * buf, size_t count, loff_t *ppos)
{
struct task_struct *task;
char buffer[PROC_NUMBUF], *end;
int make_it_fail;
if (!capable(CAP_SYS_RESOURCE))
return -EPERM;
memset(buffer, 0, sizeof(buffer));
if (count > sizeof(buffer) - 1)
co... | 182,274,563,021,447,940,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,869 | 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_fd_access_allowed(struct inode *inode)
{
struct task_struct *task;
int allowed = 0;
/* Allow access to a task's file descriptors if it is us or we
* may use ptrace attach to the process and find out that
* information.
*/
task = get_proc_task(inode);
if (task) {
allowed = ptrace_may_access(... | 149,529,688,308,330,560,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,870 | 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_fd_info(struct inode *inode, struct path *path, char *info)
{
struct task_struct *task = get_proc_task(inode);
struct files_struct *files = NULL;
struct file *file;
int fd = proc_fd(inode);
if (task) {
files = get_files_struct(task);
put_task_struct(task);
}
if (files) {
/*
* We are not... | 116,663,837,441,276,990,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,871 | 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_fd_link(struct inode *inode, struct path *path)
{
return proc_fd_info(inode, path, NULL);
}
| 186,440,961,922,409,300,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,872 | 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_fd_permission(struct inode *inode, int mask, unsigned int flags)
{
int rv = generic_permission(inode, mask, flags, NULL);
if (rv == 0)
return 0;
if (task_pid(current) == proc_pid(inode))
rv = 0;
return rv;
}
| 248,865,065,578,219,230,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,873 | 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_fdinfo_instantiate(struct inode *dir,
struct dentry *dentry, struct task_struct *task, const void *ptr)
{
unsigned fd = *(unsigned *)ptr;
struct inode *inode;
struct proc_inode *ei;
struct dentry *error = ERR_PTR(-ENOENT);
inode = proc_pid_make_inode(dir->i_sb, task);
if (!inode)
... | 11,082,087,121,689,973,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,874 | 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_fdinfo_read(struct file *file, char __user *buf,
size_t len, loff_t *ppos)
{
char tmp[PROC_FDINFO_MAX];
int err = proc_fd_info(file->f_path.dentry->d_inode, NULL, tmp);
if (!err)
err = simple_read_from_buffer(buf, len, ppos, tmp, strlen(tmp));
return err;
}
| 312,299,344,753,508,330,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,875 | 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_fill_cache(struct file *filp, void *dirent, filldir_t filldir,
const char *name, int len,
instantiate_t instantiate, struct task_struct *task, const void *ptr)
{
struct dentry *child, *dir = filp->f_path.dentry;
struct inode *inode;
struct qstr qname;
ino_t ino = 0;
unsigned type = DT_UNKNOWN;
qname.n... | 72,927,017,082,719,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,876 | 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 | void proc_flush_task(struct task_struct *task)
{
int i;
struct pid *pid, *tgid;
struct upid *upid;
pid = task_pid(task);
tgid = task_tgid(task);
for (i = 0; i <= pid->level; i++) {
upid = &pid->numbers[i];
proc_flush_task_mnt(upid->ns->proc_mnt, upid->nr,
tgid->numbers[i].nr);
}
upid = &pid->numbers... | 272,463,534,805,846,600,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,877 | 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_info_read(struct file * file, char __user * buf,
size_t count, loff_t *ppos)
{
struct inode * inode = file->f_path.dentry->d_inode;
unsigned long page;
ssize_t length;
struct task_struct *task = get_proc_task(inode);
length = -ESRCH;
if (!task)
goto out_no_task;
if (count > PROC_BLOC... | 51,823,392,988,969,630,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,878 | 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_loginuid_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, TMPBUFL... | 217,941,975,941,222,400,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,879 | 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_loginuid_write(struct file * file, const char __user * buf,
size_t count, loff_t *ppos)
{
struct inode * inode = file->f_path.dentry->d_inode;
char *page, *tmp;
ssize_t length;
uid_t loginuid;
if (!capable(CAP_AUDIT_CONTROL))
return -EPERM;
rcu_read_lock();
if (current != pid_task(... | 146,702,178,584,533,800,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,880 | 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_lookupfd(struct inode *dir, struct dentry *dentry,
struct nameidata *nd)
{
return proc_lookupfd_common(dir, dentry, proc_fd_instantiate);
}
| 179,896,425,449,981,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,881 | 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_lookupfd_common(struct inode *dir,
struct dentry *dentry,
instantiate_t instantiate)
{
struct task_struct *task = get_proc_task(dir);
unsigned fd = name_to_int(dentry);
struct dentry *result = ERR_PTR(-ENOENT);
if (!task)
goto out_no_task;
if (fd == ~0U)
goto out;
... | 275,288,660,158,625,940,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,882 | 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_lookupfdinfo(struct inode *dir,
struct dentry *dentry,
struct nameidata *nd)
{
return proc_lookupfd_common(dir, dentry, proc_fdinfo_instantiate);
}
| 121,401,779,101,448,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,883 | 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_pid_attr_read(struct file * file, char __user * buf,
size_t count, loff_t *ppos)
{
struct inode * inode = file->f_path.dentry->d_inode;
char *p = NULL;
ssize_t length;
struct task_struct *task = get_proc_task(inode);
if (!task)
return -ESRCH;
length = security_getprocattr(task,
... | 287,634,817,587,299,580,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,884 | 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_pid_cmdline(struct task_struct *task, char * buffer)
{
int res = 0;
unsigned int len;
struct mm_struct *mm = get_task_mm(task);
if (!mm)
goto out;
if (!mm->arg_end)
goto out_mm; /* Shh! No looking before we're done */
len = mm->arg_end - mm->arg_start;
if (len > PAGE_SIZE)
len = PAGE_SI... | 70,725,328,445,138,730,000,000,000,000,000,000,000 | None | null | [
"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,885 | 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_pid_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_... | 135,143,587,318,214,990,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,886 | 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_pid_limits(struct task_struct *task, char *buffer)
{
unsigned int i;
int count = 0;
unsigned long flags;
char *bufptr = buffer;
struct rlimit rlim[RLIM_NLIMITS];
if (!lock_task_sighand(task, &flags))
return 0;
memcpy(rlim, task->signal->rlim, sizeof(struct rlimit) * RLIM_NLIMITS);
unlock_tas... | 289,759,311,530,555,000,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,887 | 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 | struct dentry *proc_pid_lookup(struct inode *dir, struct dentry * dentry, struct nameidata *nd)
{
struct dentry *result;
struct task_struct *task;
unsigned tgid;
struct pid_namespace *ns;
result = proc_base_lookup(dir, dentry);
if (!IS_ERR(result) || PTR_ERR(result) != -ENOENT)
goto out;
tgid = name_to_int(d... | 8,754,186,368,034,308,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,888 | 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 | struct inode *proc_pid_make_inode(struct super_block * sb, struct task_struct *task)
{
struct inode * inode;
struct proc_inode *ei;
const struct cred *cred;
/* We need a new inode */
inode = new_inode(sb);
if (!inode)
goto out;
/* Common stuff */
ei = PROC_I(inode);
inode->i_ino = get_next_ino();
inode->... | 170,837,404,621,389,350,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,889 | 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_pid_personality(struct seq_file *m, struct pid_namespace *ns,
struct pid *pid, struct task_struct *task)
{
int err = lock_trace(task);
if (!err) {
seq_printf(m, "%08x\n", task->personality);
unlock_trace(task);
}
return err;
}
| 205,960,070,670,831,780,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,890 | 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_pid_readdir(struct file * filp, void * dirent, filldir_t filldir)
{
unsigned int nr;
struct task_struct *reaper;
struct tgid_iter iter;
struct pid_namespace *ns;
if (filp->f_pos >= PID_MAX_LIMIT + TGID_OFFSET)
goto out_no_task;
nr = filp->f_pos - FIRST_PROCESS_ENTRY;
reaper = get_proc_task(filp->f_p... | 74,701,833,808,987,230,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,891 | 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_pid_readlink(struct dentry * dentry, char __user * buffer, int buflen)
{
int error = -EACCES;
struct inode *inode = dentry->d_inode;
struct path path;
/* Are we allowed to snoop on the tasks file descriptors? */
if (!proc_fd_access_allowed(inode))
goto out;
error = PROC_I(inode)->op.proc_get_l... | 336,489,978,795,242,300,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,892 | 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_pid_schedstat(struct task_struct *task, char *buffer)
{
return sprintf(buffer, "%llu %llu %lu\n",
(unsigned long long)task->se.sum_exec_runtime,
(unsigned long long)task->sched_info.run_delay,
task->sched_info.pcount);
}
| 322,519,601,333,912,200,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,893 | 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_pid_stack(struct seq_file *m, struct pid_namespace *ns,
struct pid *pid, struct task_struct *task)
{
struct stack_trace trace;
unsigned long *entries;
int err;
int i;
entries = kmalloc(MAX_STACK_TRACE_DEPTH * sizeof(*entries), GFP_KERNEL);
if (!entries)
return -ENOMEM;
trace.nr_entries =... | 166,229,557,774,724,750,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,894 | 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_pid_syscall(struct task_struct *task, char *buffer)
{
long nr;
unsigned long args[6], sp, pc;
int res = lock_trace(task);
if (res)
return res;
if (task_current_syscall(task, &nr, args, 6, &sp, &pc))
res = sprintf(buffer, "running\n");
else if (nr < 0)
res = sprintf(buffer, "%ld 0x%lx 0x%lx\... | 115,018,060,213,134,980,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,895 | 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_pid_wchan(struct task_struct *task, char *buffer)
{
unsigned long wchan;
char symname[KSYM_NAME_LEN];
wchan = get_wchan(task);
if (lookup_symbol_name(wchan, symname) < 0)
if (!ptrace_may_access(task, PTRACE_MODE_READ))
return 0;
else
return sprintf(buffer, "%lu", wchan);
else
return s... | 249,661,143,843,192,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,896 | 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_pident_fill_cache(struct file *filp, void *dirent,
filldir_t filldir, struct task_struct *task, const struct pid_entry *p)
{
return proc_fill_cache(filp, dirent, filldir, p->name, p->len,
proc_pident_instantiate, task, p);
}
| 171,373,668,135,675,200,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,897 | 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_pident_lookup(struct inode *dir,
struct dentry *dentry,
const struct pid_entry *ents,
unsigned int nents)
{
struct dentry *error;
struct task_struct *task = get_proc_task(dir);
const struct pid_entry *p, *last;
error = ERR_PTR(-ENOENT);
if (!task)
goto out_no_task;... | 121,072,800,052,061,170,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,898 | 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_pident_readdir(struct file *filp,
void *dirent, filldir_t filldir,
const struct pid_entry *ents, unsigned int nents)
{
int i;
struct dentry *dentry = filp->f_path.dentry;
struct inode *inode = dentry->d_inode;
struct task_struct *task = get_proc_task(inode);
const struct pid_entry *p, *last;
i... | 305,389,003,824,251,200,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,899 | 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_readfd(struct file *filp, void *dirent, filldir_t filldir)
{
return proc_readfd_common(filp, dirent, filldir, proc_fd_instantiate);
}
| 219,488,556,658,884,900,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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.