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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
38,284 | linux | bfd0a56b90005f8c8a004baf407ad90045c2b11e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/bfd0a56b90005f8c8a004baf407ad90045c2b11e | nEPT: Nested INVEPT
If we let L1 use EPT, we should probably also support the INVEPT instruction.
In our current nested EPT implementation, when L1 changes its EPT table
for L2 (i.e., EPT12), L0 modifies the shadow EPT table (EPT02), and in
the course of this modification already calls INVEPT. But if last level
of sh... | 0 | static void vmx_set_efer(struct kvm_vcpu *vcpu, u64 efer)
{
struct vcpu_vmx *vmx = to_vmx(vcpu);
struct shared_msr_entry *msr = find_msr_entry(vmx, MSR_EFER);
if (!msr)
return;
/*
* Force kernel_gs_base reloading before EFER changes, as control
* of this msr depends on is_long_mode().
*/
vmx_load_host_st... | 266,275,278,356,541,500,000,000,000,000,000,000,000 | vmx.c | 77,404,791,920,628,900,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-3645 | arch/x86/kvm/vmx.c in the KVM subsystem in the Linux kernel before 3.12 does not have an exit handler for the INVEPT instruction, which allows guest OS users to cause a denial of service (guest OS crash) via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2014-3645 |
38,285 | linux | bfd0a56b90005f8c8a004baf407ad90045c2b11e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/bfd0a56b90005f8c8a004baf407ad90045c2b11e | nEPT: Nested INVEPT
If we let L1 use EPT, we should probably also support the INVEPT instruction.
In our current nested EPT implementation, when L1 changes its EPT table
for L2 (i.e., EPT12), L0 modifies the shadow EPT table (EPT02), and in
the course of this modification already calls INVEPT. But if last level
of sh... | 0 | static int vmx_set_msr(struct kvm_vcpu *vcpu, struct msr_data *msr_info)
{
struct vcpu_vmx *vmx = to_vmx(vcpu);
struct shared_msr_entry *msr;
int ret = 0;
u32 msr_index = msr_info->index;
u64 data = msr_info->data;
switch (msr_index) {
case MSR_EFER:
ret = kvm_set_msr_common(vcpu, msr_info);
break;
#ifdef C... | 291,271,909,621,173,600,000,000,000,000,000,000,000 | vmx.c | 77,404,791,920,628,900,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-3645 | arch/x86/kvm/vmx.c in the KVM subsystem in the Linux kernel before 3.12 does not have an exit handler for the INVEPT instruction, which allows guest OS users to cause a denial of service (guest OS crash) via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2014-3645 |
38,286 | linux | bfd0a56b90005f8c8a004baf407ad90045c2b11e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/bfd0a56b90005f8c8a004baf407ad90045c2b11e | nEPT: Nested INVEPT
If we let L1 use EPT, we should probably also support the INVEPT instruction.
In our current nested EPT implementation, when L1 changes its EPT table
for L2 (i.e., EPT12), L0 modifies the shadow EPT table (EPT02), and in
the course of this modification already calls INVEPT. But if last level
of sh... | 0 | static void vmx_set_segment(struct kvm_vcpu *vcpu,
struct kvm_segment *var, int seg)
{
struct vcpu_vmx *vmx = to_vmx(vcpu);
const struct kvm_vmx_segment_field *sf = &kvm_vmx_segment_fields[seg];
vmx_segment_cache_clear(vmx);
if (seg == VCPU_SREG_CS)
__clear_bit(VCPU_EXREG_CPL, (ulong *)&vcpu->arch.regs_av... | 32,936,599,572,937,537,000,000,000,000,000,000,000 | vmx.c | 77,404,791,920,628,900,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-3645 | arch/x86/kvm/vmx.c in the KVM subsystem in the Linux kernel before 3.12 does not have an exit handler for the INVEPT instruction, which allows guest OS users to cause a denial of service (guest OS crash) via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2014-3645 |
38,287 | linux | bfd0a56b90005f8c8a004baf407ad90045c2b11e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/bfd0a56b90005f8c8a004baf407ad90045c2b11e | nEPT: Nested INVEPT
If we let L1 use EPT, we should probably also support the INVEPT instruction.
In our current nested EPT implementation, when L1 changes its EPT table
for L2 (i.e., EPT12), L0 modifies the shadow EPT table (EPT02), and in
the course of this modification already calls INVEPT. But if last level
of sh... | 0 | static int vmx_set_vmx_msr(struct kvm_vcpu *vcpu, struct msr_data *msr_info)
{
u32 msr_index = msr_info->index;
u64 data = msr_info->data;
bool host_initialized = msr_info->host_initiated;
if (!nested_vmx_allowed(vcpu))
return 0;
if (msr_index == MSR_IA32_FEATURE_CONTROL) {
if (!host_initialized &&
to_vm... | 34,235,315,688,993,693,000,000,000,000,000,000,000 | vmx.c | 77,404,791,920,628,900,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-3645 | arch/x86/kvm/vmx.c in the KVM subsystem in the Linux kernel before 3.12 does not have an exit handler for the INVEPT instruction, which allows guest OS users to cause a denial of service (guest OS crash) via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2014-3645 |
38,288 | linux | bfd0a56b90005f8c8a004baf407ad90045c2b11e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/bfd0a56b90005f8c8a004baf407ad90045c2b11e | nEPT: Nested INVEPT
If we let L1 use EPT, we should probably also support the INVEPT instruction.
In our current nested EPT implementation, when L1 changes its EPT table
for L2 (i.e., EPT12), L0 modifies the shadow EPT table (EPT02), and in
the course of this modification already calls INVEPT. But if last level
of sh... | 0 | static void vmx_vcpu_load(struct kvm_vcpu *vcpu, int cpu)
{
struct vcpu_vmx *vmx = to_vmx(vcpu);
u64 phys_addr = __pa(per_cpu(vmxarea, cpu));
if (!vmm_exclusive)
kvm_cpu_vmxon(phys_addr);
else if (vmx->loaded_vmcs->cpu != cpu)
loaded_vmcs_clear(vmx->loaded_vmcs);
if (per_cpu(current_vmcs, cpu) != vmx->loaded... | 258,267,443,139,583,400,000,000,000,000,000,000,000 | vmx.c | 77,404,791,920,628,900,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-3645 | arch/x86/kvm/vmx.c in the KVM subsystem in the Linux kernel before 3.12 does not have an exit handler for the INVEPT instruction, which allows guest OS users to cause a denial of service (guest OS crash) via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2014-3645 |
38,289 | linux | bfd0a56b90005f8c8a004baf407ad90045c2b11e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/bfd0a56b90005f8c8a004baf407ad90045c2b11e | nEPT: Nested INVEPT
If we let L1 use EPT, we should probably also support the INVEPT instruction.
In our current nested EPT implementation, when L1 changes its EPT table
for L2 (i.e., EPT12), L0 modifies the shadow EPT table (EPT02), and in
the course of this modification already calls INVEPT. But if last level
of sh... | 0 | static void vmx_vcpu_reset(struct kvm_vcpu *vcpu)
{
struct vcpu_vmx *vmx = to_vmx(vcpu);
u64 msr;
vmx->rmode.vm86_active = 0;
vmx->soft_vnmi_blocked = 0;
vmx->vcpu.arch.regs[VCPU_REGS_RDX] = get_rdx_init_val();
kvm_set_cr8(&vmx->vcpu, 0);
msr = 0xfee00000 | MSR_IA32_APICBASE_ENABLE;
if (kvm_vcpu_is_bsp(&vmx-... | 178,452,184,991,821,000,000,000,000,000,000,000,000 | vmx.c | 77,404,791,920,628,900,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-3645 | arch/x86/kvm/vmx.c in the KVM subsystem in the Linux kernel before 3.12 does not have an exit handler for the INVEPT instruction, which allows guest OS users to cause a denial of service (guest OS crash) via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2014-3645 |
38,290 | linux | bfd0a56b90005f8c8a004baf407ad90045c2b11e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/bfd0a56b90005f8c8a004baf407ad90045c2b11e | nEPT: Nested INVEPT
If we let L1 use EPT, we should probably also support the INVEPT instruction.
In our current nested EPT implementation, when L1 changes its EPT table
for L2 (i.e., EPT12), L0 modifies the shadow EPT table (EPT02), and in
the course of this modification already calls INVEPT. But if last level
of sh... | 0 | static void __noclone vmx_vcpu_run(struct kvm_vcpu *vcpu)
{
struct vcpu_vmx *vmx = to_vmx(vcpu);
unsigned long debugctlmsr;
/* Record the guest's net vcpu time for enforced NMI injections. */
if (unlikely(!cpu_has_virtual_nmis() && vmx->soft_vnmi_blocked))
vmx->entry_time = ktime_get();
/* Don't enter VMX if g... | 118,098,767,680,970,220,000,000,000,000,000,000,000 | vmx.c | 77,404,791,920,628,900,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-3645 | arch/x86/kvm/vmx.c in the KVM subsystem in the Linux kernel before 3.12 does not have an exit handler for the INVEPT instruction, which allows guest OS users to cause a denial of service (guest OS crash) via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2014-3645 |
38,291 | linux | bfd0a56b90005f8c8a004baf407ad90045c2b11e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/bfd0a56b90005f8c8a004baf407ad90045c2b11e | nEPT: Nested INVEPT
If we let L1 use EPT, we should probably also support the INVEPT instruction.
In our current nested EPT implementation, when L1 changes its EPT table
for L2 (i.e., EPT12), L0 modifies the shadow EPT table (EPT02), and in
the course of this modification already calls INVEPT. But if last level
of sh... | 0 | static int vmx_vcpu_setup(struct vcpu_vmx *vmx)
{
#ifdef CONFIG_X86_64
unsigned long a;
#endif
int i;
/* I/O */
vmcs_write64(IO_BITMAP_A, __pa(vmx_io_bitmap_a));
vmcs_write64(IO_BITMAP_B, __pa(vmx_io_bitmap_b));
if (enable_shadow_vmcs) {
vmcs_write64(VMREAD_BITMAP, __pa(vmx_vmread_bitmap));
vmcs_write64(VMW... | 82,003,897,633,669,590,000,000,000,000,000,000,000 | vmx.c | 77,404,791,920,628,900,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-3645 | arch/x86/kvm/vmx.c in the KVM subsystem in the Linux kernel before 3.12 does not have an exit handler for the INVEPT instruction, which allows guest OS users to cause a denial of service (guest OS crash) via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2014-3645 |
38,292 | linux | 95389b08d93d5c06ec63ab49bd732b0069b7c35e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/95389b08d93d5c06ec63ab49bd732b0069b7c35e | KEYS: Fix termination condition in assoc array garbage collection
This fixes CVE-2014-3631.
It is possible for an associative array to end up with a shortcut node at the
root of the tree if there are more than fan-out leaves in the tree, but they
all crowd into the same slot in the lowest level (ie. they all have the... | 0 | void assoc_array_apply_edit(struct assoc_array_edit *edit)
{
struct assoc_array_shortcut *shortcut;
struct assoc_array_node *node;
struct assoc_array_ptr *ptr;
int i;
pr_devel("-->%s()\n", __func__);
smp_wmb();
if (edit->leaf_p)
*edit->leaf_p = edit->leaf;
smp_wmb();
for (i = 0; i < ARRAY_SIZE(edit->set_p... | 205,903,209,574,171,000,000,000,000,000,000,000,000 | assoc_array.c | 22,003,643,060,369,240,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-3631 | The assoc_array_gc function in the associative-array implementation in lib/assoc_array.c in the Linux kernel before 3.16.3 does not properly implement garbage collection, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via multi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3631 |
38,293 | linux | 95389b08d93d5c06ec63ab49bd732b0069b7c35e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/95389b08d93d5c06ec63ab49bd732b0069b7c35e | KEYS: Fix termination condition in assoc array garbage collection
This fixes CVE-2014-3631.
It is possible for an associative array to end up with a shortcut node at the
root of the tree if there are more than fan-out leaves in the tree, but they
all crowd into the same slot in the lowest level (ie. they all have the... | 0 | void assoc_array_cancel_edit(struct assoc_array_edit *edit)
{
struct assoc_array_ptr *ptr;
int i;
pr_devel("-->%s()\n", __func__);
/* Clean up after an out of memory error */
for (i = 0; i < ARRAY_SIZE(edit->new_meta); i++) {
ptr = edit->new_meta[i];
if (ptr) {
if (assoc_array_ptr_is_node(ptr))
kfree(... | 273,715,230,059,329,100,000,000,000,000,000,000,000 | assoc_array.c | 22,003,643,060,369,240,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-3631 | The assoc_array_gc function in the associative-array implementation in lib/assoc_array.c in the Linux kernel before 3.16.3 does not properly implement garbage collection, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via multi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3631 |
38,294 | linux | 95389b08d93d5c06ec63ab49bd732b0069b7c35e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/95389b08d93d5c06ec63ab49bd732b0069b7c35e | KEYS: Fix termination condition in assoc array garbage collection
This fixes CVE-2014-3631.
It is possible for an associative array to end up with a shortcut node at the
root of the tree if there are more than fan-out leaves in the tree, but they
all crowd into the same slot in the lowest level (ie. they all have the... | 0 | struct assoc_array_edit *assoc_array_clear(struct assoc_array *array,
const struct assoc_array_ops *ops)
{
struct assoc_array_edit *edit;
pr_devel("-->%s()\n", __func__);
if (!array->root)
return NULL;
edit = kzalloc(sizeof(struct assoc_array_edit), GFP_KERNEL);
if (!edit)
return ERR_PTR(-ENOMEM);
... | 65,957,452,207,953,200,000,000,000,000,000,000,000 | assoc_array.c | 22,003,643,060,369,240,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-3631 | The assoc_array_gc function in the associative-array implementation in lib/assoc_array.c in the Linux kernel before 3.16.3 does not properly implement garbage collection, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via multi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3631 |
38,295 | linux | 95389b08d93d5c06ec63ab49bd732b0069b7c35e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/95389b08d93d5c06ec63ab49bd732b0069b7c35e | KEYS: Fix termination condition in assoc array garbage collection
This fixes CVE-2014-3631.
It is possible for an associative array to end up with a shortcut node at the
root of the tree if there are more than fan-out leaves in the tree, but they
all crowd into the same slot in the lowest level (ie. they all have the... | 0 | struct assoc_array_edit *assoc_array_delete(struct assoc_array *array,
const struct assoc_array_ops *ops,
const void *index_key)
{
struct assoc_array_delete_collapse_context collapse;
struct assoc_array_walk_result result;
struct assoc_array_node *node, *new_n0;
struct assoc_array_edit *edit;
str... | 241,168,449,921,534,850,000,000,000,000,000,000,000 | assoc_array.c | 22,003,643,060,369,240,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-3631 | The assoc_array_gc function in the associative-array implementation in lib/assoc_array.c in the Linux kernel before 3.16.3 does not properly implement garbage collection, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via multi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3631 |
38,296 | linux | 95389b08d93d5c06ec63ab49bd732b0069b7c35e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/95389b08d93d5c06ec63ab49bd732b0069b7c35e | KEYS: Fix termination condition in assoc array garbage collection
This fixes CVE-2014-3631.
It is possible for an associative array to end up with a shortcut node at the
root of the tree if there are more than fan-out leaves in the tree, but they
all crowd into the same slot in the lowest level (ie. they all have the... | 0 | static int assoc_array_delete_collapse_iterator(const void *leaf,
void *iterator_data)
{
struct assoc_array_delete_collapse_context *collapse = iterator_data;
if (leaf == collapse->skip_leaf)
return 0;
BUG_ON(collapse->slot >= ASSOC_ARRAY_FAN_OUT);
collapse->node->slots[collapse->slot++] = assoc_array_le... | 76,394,451,465,831,820,000,000,000,000,000,000,000 | assoc_array.c | 22,003,643,060,369,240,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-3631 | The assoc_array_gc function in the associative-array implementation in lib/assoc_array.c in the Linux kernel before 3.16.3 does not properly implement garbage collection, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via multi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3631 |
38,297 | linux | 95389b08d93d5c06ec63ab49bd732b0069b7c35e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/95389b08d93d5c06ec63ab49bd732b0069b7c35e | KEYS: Fix termination condition in assoc array garbage collection
This fixes CVE-2014-3631.
It is possible for an associative array to end up with a shortcut node at the
root of the tree if there are more than fan-out leaves in the tree, but they
all crowd into the same slot in the lowest level (ie. they all have the... | 0 | static void assoc_array_destroy_subtree(struct assoc_array_ptr *root,
const struct assoc_array_ops *ops)
{
struct assoc_array_shortcut *shortcut;
struct assoc_array_node *node;
struct assoc_array_ptr *cursor, *parent = NULL;
int slot = -1;
pr_devel("-->%s()\n", __func__);
cursor = root;
if (!cursor) {
p... | 261,241,993,762,549,130,000,000,000,000,000,000,000 | assoc_array.c | 22,003,643,060,369,240,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-3631 | The assoc_array_gc function in the associative-array implementation in lib/assoc_array.c in the Linux kernel before 3.16.3 does not properly implement garbage collection, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via multi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3631 |
38,298 | linux | 95389b08d93d5c06ec63ab49bd732b0069b7c35e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/95389b08d93d5c06ec63ab49bd732b0069b7c35e | KEYS: Fix termination condition in assoc array garbage collection
This fixes CVE-2014-3631.
It is possible for an associative array to end up with a shortcut node at the
root of the tree if there are more than fan-out leaves in the tree, but they
all crowd into the same slot in the lowest level (ie. they all have the... | 0 | void *assoc_array_find(const struct assoc_array *array,
const struct assoc_array_ops *ops,
const void *index_key)
{
struct assoc_array_walk_result result;
const struct assoc_array_node *node;
const struct assoc_array_ptr *ptr;
const void *leaf;
int slot;
if (assoc_array_walk(array, ops, index_k... | 281,989,777,365,997,960,000,000,000,000,000,000,000 | assoc_array.c | 22,003,643,060,369,240,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-3631 | The assoc_array_gc function in the associative-array implementation in lib/assoc_array.c in the Linux kernel before 3.16.3 does not properly implement garbage collection, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via multi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3631 |
38,299 | linux | 95389b08d93d5c06ec63ab49bd732b0069b7c35e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/95389b08d93d5c06ec63ab49bd732b0069b7c35e | KEYS: Fix termination condition in assoc array garbage collection
This fixes CVE-2014-3631.
It is possible for an associative array to end up with a shortcut node at the
root of the tree if there are more than fan-out leaves in the tree, but they
all crowd into the same slot in the lowest level (ie. they all have the... | 0 | struct assoc_array_edit *assoc_array_insert(struct assoc_array *array,
const struct assoc_array_ops *ops,
const void *index_key,
void *object)
{
struct assoc_array_walk_result result;
struct assoc_array_edit *edit;
pr_devel("-->%s()\n", __func__);
/* The leaf pointer we're given must no... | 68,231,880,811,983,560,000,000,000,000,000,000,000 | assoc_array.c | 22,003,643,060,369,240,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-3631 | The assoc_array_gc function in the associative-array implementation in lib/assoc_array.c in the Linux kernel before 3.16.3 does not properly implement garbage collection, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via multi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3631 |
38,300 | linux | 95389b08d93d5c06ec63ab49bd732b0069b7c35e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/95389b08d93d5c06ec63ab49bd732b0069b7c35e | KEYS: Fix termination condition in assoc array garbage collection
This fixes CVE-2014-3631.
It is possible for an associative array to end up with a shortcut node at the
root of the tree if there are more than fan-out leaves in the tree, but they
all crowd into the same slot in the lowest level (ie. they all have the... | 0 | static bool assoc_array_insert_in_empty_tree(struct assoc_array_edit *edit)
{
struct assoc_array_node *new_n0;
pr_devel("-->%s()\n", __func__);
new_n0 = kzalloc(sizeof(struct assoc_array_node), GFP_KERNEL);
if (!new_n0)
return false;
edit->new_meta[0] = assoc_array_node_to_ptr(new_n0);
edit->leaf_p = &new_n0... | 157,173,820,411,171,300,000,000,000,000,000,000,000 | assoc_array.c | 22,003,643,060,369,240,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-3631 | The assoc_array_gc function in the associative-array implementation in lib/assoc_array.c in the Linux kernel before 3.16.3 does not properly implement garbage collection, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via multi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3631 |
38,301 | linux | 95389b08d93d5c06ec63ab49bd732b0069b7c35e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/95389b08d93d5c06ec63ab49bd732b0069b7c35e | KEYS: Fix termination condition in assoc array garbage collection
This fixes CVE-2014-3631.
It is possible for an associative array to end up with a shortcut node at the
root of the tree if there are more than fan-out leaves in the tree, but they
all crowd into the same slot in the lowest level (ie. they all have the... | 0 | static bool assoc_array_insert_mid_shortcut(struct assoc_array_edit *edit,
const struct assoc_array_ops *ops,
struct assoc_array_walk_result *result)
{
struct assoc_array_shortcut *shortcut, *new_s0, *new_s1;
struct assoc_array_node *node, *new_n0, *side;
unsigned long sc_segments, dissimilarity, b... | 8,917,516,748,304,851,000,000,000,000,000,000,000 | assoc_array.c | 22,003,643,060,369,240,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-3631 | The assoc_array_gc function in the associative-array implementation in lib/assoc_array.c in the Linux kernel before 3.16.3 does not properly implement garbage collection, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via multi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3631 |
38,302 | linux | 95389b08d93d5c06ec63ab49bd732b0069b7c35e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/95389b08d93d5c06ec63ab49bd732b0069b7c35e | KEYS: Fix termination condition in assoc array garbage collection
This fixes CVE-2014-3631.
It is possible for an associative array to end up with a shortcut node at the
root of the tree if there are more than fan-out leaves in the tree, but they
all crowd into the same slot in the lowest level (ie. they all have the... | 0 | void assoc_array_insert_set_object(struct assoc_array_edit *edit, void *object)
{
BUG_ON(!object);
edit->leaf = assoc_array_leaf_to_ptr(object);
}
| 25,542,774,882,632,050,000,000,000,000,000,000,000 | assoc_array.c | 22,003,643,060,369,240,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-3631 | The assoc_array_gc function in the associative-array implementation in lib/assoc_array.c in the Linux kernel before 3.16.3 does not properly implement garbage collection, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via multi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3631 |
38,303 | linux | 95389b08d93d5c06ec63ab49bd732b0069b7c35e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/95389b08d93d5c06ec63ab49bd732b0069b7c35e | KEYS: Fix termination condition in assoc array garbage collection
This fixes CVE-2014-3631.
It is possible for an associative array to end up with a shortcut node at the
root of the tree if there are more than fan-out leaves in the tree, but they
all crowd into the same slot in the lowest level (ie. they all have the... | 0 | int assoc_array_iterate(const struct assoc_array *array,
int (*iterator)(const void *object,
void *iterator_data),
void *iterator_data)
{
struct assoc_array_ptr *root = ACCESS_ONCE(array->root);
if (!root)
return 0;
return assoc_array_subtree_iterate(root, NULL, iterator, iterator_data);
}
| 65,913,094,134,144,240,000,000,000,000,000,000,000 | assoc_array.c | 22,003,643,060,369,240,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-3631 | The assoc_array_gc function in the associative-array implementation in lib/assoc_array.c in the Linux kernel before 3.16.3 does not properly implement garbage collection, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via multi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3631 |
38,304 | linux | 95389b08d93d5c06ec63ab49bd732b0069b7c35e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/95389b08d93d5c06ec63ab49bd732b0069b7c35e | KEYS: Fix termination condition in assoc array garbage collection
This fixes CVE-2014-3631.
It is possible for an associative array to end up with a shortcut node at the
root of the tree if there are more than fan-out leaves in the tree, but they
all crowd into the same slot in the lowest level (ie. they all have the... | 0 | static void assoc_array_rcu_cleanup(struct rcu_head *head)
{
struct assoc_array_edit *edit =
container_of(head, struct assoc_array_edit, rcu);
int i;
pr_devel("-->%s()\n", __func__);
if (edit->dead_leaf)
edit->ops->free_object(assoc_array_ptr_to_leaf(edit->dead_leaf));
for (i = 0; i < ARRAY_SIZE(edit->excise... | 220,698,114,997,733,000,000,000,000,000,000,000,000 | assoc_array.c | 22,003,643,060,369,240,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-3631 | The assoc_array_gc function in the associative-array implementation in lib/assoc_array.c in the Linux kernel before 3.16.3 does not properly implement garbage collection, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via multi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3631 |
38,305 | linux | 95389b08d93d5c06ec63ab49bd732b0069b7c35e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/95389b08d93d5c06ec63ab49bd732b0069b7c35e | KEYS: Fix termination condition in assoc array garbage collection
This fixes CVE-2014-3631.
It is possible for an associative array to end up with a shortcut node at the
root of the tree if there are more than fan-out leaves in the tree, but they
all crowd into the same slot in the lowest level (ie. they all have the... | 0 | static int assoc_array_subtree_iterate(const struct assoc_array_ptr *root,
const struct assoc_array_ptr *stop,
int (*iterator)(const void *leaf,
void *iterator_data),
void *iterator_data)
{
const struct assoc_array_shortcut *shortcut;
const struct assoc_array_node *node;
... | 38,689,415,242,630,930,000,000,000,000,000,000,000 | assoc_array.c | 22,003,643,060,369,240,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-3631 | The assoc_array_gc function in the associative-array implementation in lib/assoc_array.c in the Linux kernel before 3.16.3 does not properly implement garbage collection, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via multi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3631 |
38,605 | file | 27a14bc7ba285a0a5ebfdb55e54001aa11932b08 | https://github.com/file/file | https://github.com/file/file/commit/27a14bc7ba285a0a5ebfdb55e54001aa11932b08 | Correctly compute the truncated pascal string size (Francisco Alonso and
Jan Kaluza at RedHat) | 0 | magiccheck(struct magic_set *ms, struct magic *m)
{
uint64_t l = m->value.q;
uint64_t v;
float fl, fv;
double dl, dv;
int matched;
union VALUETYPE *p = &ms->ms_value;
switch (m->type) {
case FILE_BYTE:
v = p->b;
break;
case FILE_SHORT:
case FILE_BESHORT:
case FILE_LESHORT:
v = p->h;
break;
case F... | 130,140,622,129,894,170,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3478 | Buffer overflow in the mconvert function in softmagic.c in file before 5.19, as used in the Fileinfo component in PHP before 5.4.30 and 5.5.x before 5.5.14, allows remote attackers to cause a denial of service (application crash) via a crafted Pascal string in a FILE_PSTRING conversion. | https://nvd.nist.gov/vuln/detail/CVE-2014-3478 |
38,606 | linux | 844817e47eef14141cf59b8d5ac08dd11c0a9189 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/844817e47eef14141cf59b8d5ac08dd11c0a9189 | HID: picolcd: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that raw_data
that we hold in picolcd_pending structure are always kept within proper
bounds.
Cc: stable@vger.kernel.org
Reported-... | 0 | static int picolcd_check_version(struct hid_device *hdev)
{
struct picolcd_data *data = hid_get_drvdata(hdev);
struct picolcd_pending *verinfo;
int ret = 0;
if (!data)
return -ENODEV;
verinfo = picolcd_send_and_wait(hdev, REPORT_VERSION, NULL, 0);
if (!verinfo) {
hid_err(hdev, "no version response from Pico... | 26,528,051,567,212,985,000,000,000,000,000,000,000 | hid-picolcd_core.c | 54,398,981,253,658,970,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3186 | Buffer overflow in the picolcd_raw_event function in devices/hid/hid-picolcd_core.c in the PicoLCD HID device driver in the Linux kernel through 3.16.3, as used in Android on Nexus 7 devices, allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a craft... | https://nvd.nist.gov/vuln/detail/CVE-2014-3186 |
38,607 | linux | 844817e47eef14141cf59b8d5ac08dd11c0a9189 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/844817e47eef14141cf59b8d5ac08dd11c0a9189 | HID: picolcd: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that raw_data
that we hold in picolcd_pending structure are always kept within proper
bounds.
Cc: stable@vger.kernel.org
Reported-... | 0 | static void picolcd_exit_keys(struct picolcd_data *data)
{
struct input_dev *idev = data->input_keys;
data->input_keys = NULL;
if (idev)
input_unregister_device(idev);
}
| 104,150,490,767,521,300,000,000,000,000,000,000,000 | hid-picolcd_core.c | 54,398,981,253,658,970,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3186 | Buffer overflow in the picolcd_raw_event function in devices/hid/hid-picolcd_core.c in the PicoLCD HID device driver in the Linux kernel through 3.16.3, as used in Android on Nexus 7 devices, allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a craft... | https://nvd.nist.gov/vuln/detail/CVE-2014-3186 |
38,608 | linux | 844817e47eef14141cf59b8d5ac08dd11c0a9189 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/844817e47eef14141cf59b8d5ac08dd11c0a9189 | HID: picolcd: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that raw_data
that we hold in picolcd_pending structure are always kept within proper
bounds.
Cc: stable@vger.kernel.org
Reported-... | 0 | static int picolcd_init_keys(struct picolcd_data *data,
struct hid_report *report)
{
struct hid_device *hdev = data->hdev;
struct input_dev *idev;
int error, i;
if (!report)
return -ENODEV;
if (report->maxfield != 1 || report->field[0]->report_count != 2 ||
report->field[0]->report_size != 8) {
hid_err(h... | 43,438,240,413,302,020,000,000,000,000,000,000,000 | hid-picolcd_core.c | 54,398,981,253,658,970,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3186 | Buffer overflow in the picolcd_raw_event function in devices/hid/hid-picolcd_core.c in the PicoLCD HID device driver in the Linux kernel through 3.16.3, as used in Android on Nexus 7 devices, allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a craft... | https://nvd.nist.gov/vuln/detail/CVE-2014-3186 |
38,609 | linux | 844817e47eef14141cf59b8d5ac08dd11c0a9189 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/844817e47eef14141cf59b8d5ac08dd11c0a9189 | HID: picolcd: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that raw_data
that we hold in picolcd_pending structure are always kept within proper
bounds.
Cc: stable@vger.kernel.org
Reported-... | 0 | static ssize_t picolcd_operation_mode_delay_show(struct device *dev,
struct device_attribute *attr, char *buf)
{
struct picolcd_data *data = dev_get_drvdata(dev);
return snprintf(buf, PAGE_SIZE, "%hu\n", data->opmode_delay);
}
| 159,861,184,953,178,540,000,000,000,000,000,000,000 | hid-picolcd_core.c | 54,398,981,253,658,970,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3186 | Buffer overflow in the picolcd_raw_event function in devices/hid/hid-picolcd_core.c in the PicoLCD HID device driver in the Linux kernel through 3.16.3, as used in Android on Nexus 7 devices, allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a craft... | https://nvd.nist.gov/vuln/detail/CVE-2014-3186 |
38,610 | linux | 844817e47eef14141cf59b8d5ac08dd11c0a9189 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/844817e47eef14141cf59b8d5ac08dd11c0a9189 | HID: picolcd: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that raw_data
that we hold in picolcd_pending structure are always kept within proper
bounds.
Cc: stable@vger.kernel.org
Reported-... | 0 | static ssize_t picolcd_operation_mode_delay_store(struct device *dev,
struct device_attribute *attr, const char *buf, size_t count)
{
struct picolcd_data *data = dev_get_drvdata(dev);
unsigned u;
if (sscanf(buf, "%u", &u) != 1)
return -EINVAL;
if (u > 30000)
return -EINVAL;
else
data->opmode_delay = u;
re... | 81,116,298,563,340,040,000,000,000,000,000,000,000 | hid-picolcd_core.c | 54,398,981,253,658,970,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3186 | Buffer overflow in the picolcd_raw_event function in devices/hid/hid-picolcd_core.c in the PicoLCD HID device driver in the Linux kernel through 3.16.3, as used in Android on Nexus 7 devices, allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a craft... | https://nvd.nist.gov/vuln/detail/CVE-2014-3186 |
38,611 | linux | 844817e47eef14141cf59b8d5ac08dd11c0a9189 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/844817e47eef14141cf59b8d5ac08dd11c0a9189 | HID: picolcd: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that raw_data
that we hold in picolcd_pending structure are always kept within proper
bounds.
Cc: stable@vger.kernel.org
Reported-... | 0 | static ssize_t picolcd_operation_mode_show(struct device *dev,
struct device_attribute *attr, char *buf)
{
struct picolcd_data *data = dev_get_drvdata(dev);
if (data->status & PICOLCD_BOOTLOADER)
return snprintf(buf, PAGE_SIZE, "[bootloader] lcd\n");
else
return snprintf(buf, PAGE_SIZE, "bootloader [lcd]\n");... | 25,176,159,491,093,790,000,000,000,000,000,000,000 | hid-picolcd_core.c | 54,398,981,253,658,970,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3186 | Buffer overflow in the picolcd_raw_event function in devices/hid/hid-picolcd_core.c in the PicoLCD HID device driver in the Linux kernel through 3.16.3, as used in Android on Nexus 7 devices, allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a craft... | https://nvd.nist.gov/vuln/detail/CVE-2014-3186 |
38,612 | linux | 844817e47eef14141cf59b8d5ac08dd11c0a9189 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/844817e47eef14141cf59b8d5ac08dd11c0a9189 | HID: picolcd: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that raw_data
that we hold in picolcd_pending structure are always kept within proper
bounds.
Cc: stable@vger.kernel.org
Reported-... | 0 | static ssize_t picolcd_operation_mode_store(struct device *dev,
struct device_attribute *attr, const char *buf, size_t count)
{
struct picolcd_data *data = dev_get_drvdata(dev);
struct hid_report *report = NULL;
size_t cnt = count;
int timeout = data->opmode_delay;
unsigned long flags;
if (cnt >= 3 && strncmp(... | 172,971,477,839,186,960,000,000,000,000,000,000,000 | hid-picolcd_core.c | 54,398,981,253,658,970,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3186 | Buffer overflow in the picolcd_raw_event function in devices/hid/hid-picolcd_core.c in the PicoLCD HID device driver in the Linux kernel through 3.16.3, as used in Android on Nexus 7 devices, allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a craft... | https://nvd.nist.gov/vuln/detail/CVE-2014-3186 |
38,613 | linux | 844817e47eef14141cf59b8d5ac08dd11c0a9189 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/844817e47eef14141cf59b8d5ac08dd11c0a9189 | HID: picolcd: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that raw_data
that we hold in picolcd_pending structure are always kept within proper
bounds.
Cc: stable@vger.kernel.org
Reported-... | 0 | static int picolcd_probe(struct hid_device *hdev,
const struct hid_device_id *id)
{
struct picolcd_data *data;
int error = -ENOMEM;
dbg_hid(PICOLCD_NAME " hardware probe...\n");
/*
* Let's allocate the picolcd data structure, set some reasonable
* defaults, and associate it with the device
*/
data =... | 236,630,699,567,681,280,000,000,000,000,000,000,000 | hid-picolcd_core.c | 54,398,981,253,658,970,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3186 | Buffer overflow in the picolcd_raw_event function in devices/hid/hid-picolcd_core.c in the PicoLCD HID device driver in the Linux kernel through 3.16.3, as used in Android on Nexus 7 devices, allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a craft... | https://nvd.nist.gov/vuln/detail/CVE-2014-3186 |
38,614 | linux | 844817e47eef14141cf59b8d5ac08dd11c0a9189 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/844817e47eef14141cf59b8d5ac08dd11c0a9189 | HID: picolcd: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that raw_data
that we hold in picolcd_pending structure are always kept within proper
bounds.
Cc: stable@vger.kernel.org
Reported-... | 0 | static int picolcd_probe_bootloader(struct hid_device *hdev, struct picolcd_data *data)
{
picolcd_init_devfs(data, NULL, NULL,
picolcd_out_report(REPORT_BL_READ_MEMORY, hdev),
picolcd_out_report(REPORT_BL_WRITE_MEMORY, hdev), NULL);
return 0;
}
| 75,022,878,143,434,840,000,000,000,000,000,000,000 | hid-picolcd_core.c | 54,398,981,253,658,970,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3186 | Buffer overflow in the picolcd_raw_event function in devices/hid/hid-picolcd_core.c in the PicoLCD HID device driver in the Linux kernel through 3.16.3, as used in Android on Nexus 7 devices, allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a craft... | https://nvd.nist.gov/vuln/detail/CVE-2014-3186 |
38,615 | linux | 844817e47eef14141cf59b8d5ac08dd11c0a9189 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/844817e47eef14141cf59b8d5ac08dd11c0a9189 | HID: picolcd: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that raw_data
that we hold in picolcd_pending structure are always kept within proper
bounds.
Cc: stable@vger.kernel.org
Reported-... | 0 | static int picolcd_probe_lcd(struct hid_device *hdev, struct picolcd_data *data)
{
int error;
/* Setup keypad input device */
error = picolcd_init_keys(data, picolcd_in_report(REPORT_KEY_STATE, hdev));
if (error)
goto err;
/* Setup CIR input device */
error = picolcd_init_cir(data, picolcd_in_report(REPORT_IR... | 5,709,565,355,276,326,000,000,000,000,000,000,000 | hid-picolcd_core.c | 54,398,981,253,658,970,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3186 | Buffer overflow in the picolcd_raw_event function in devices/hid/hid-picolcd_core.c in the PicoLCD HID device driver in the Linux kernel through 3.16.3, as used in Android on Nexus 7 devices, allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a craft... | https://nvd.nist.gov/vuln/detail/CVE-2014-3186 |
38,616 | linux | 844817e47eef14141cf59b8d5ac08dd11c0a9189 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/844817e47eef14141cf59b8d5ac08dd11c0a9189 | HID: picolcd: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that raw_data
that we hold in picolcd_pending structure are always kept within proper
bounds.
Cc: stable@vger.kernel.org
Reported-... | 0 | static int picolcd_raw_keypad(struct picolcd_data *data,
struct hid_report *report, u8 *raw_data, int size)
{
/*
* Keypad event
* First and second data bytes list currently pressed keys,
* 0x00 means no key and at most 2 keys may be pressed at same time
*/
int i, j;
/* determine newly pressed keys */
for... | 238,538,552,886,116,260,000,000,000,000,000,000,000 | hid-picolcd_core.c | 54,398,981,253,658,970,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3186 | Buffer overflow in the picolcd_raw_event function in devices/hid/hid-picolcd_core.c in the PicoLCD HID device driver in the Linux kernel through 3.16.3, as used in Android on Nexus 7 devices, allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a craft... | https://nvd.nist.gov/vuln/detail/CVE-2014-3186 |
38,617 | linux | 844817e47eef14141cf59b8d5ac08dd11c0a9189 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/844817e47eef14141cf59b8d5ac08dd11c0a9189 | HID: picolcd: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that raw_data
that we hold in picolcd_pending structure are always kept within proper
bounds.
Cc: stable@vger.kernel.org
Reported-... | 0 | struct hid_report *picolcd_report(int id, struct hid_device *hdev, int dir)
{
struct list_head *feature_report_list = &hdev->report_enum[dir].report_list;
struct hid_report *report = NULL;
list_for_each_entry(report, feature_report_list, list) {
if (report->id == id)
return report;
}
hid_warn(hdev, "No repor... | 268,411,273,444,631,200,000,000,000,000,000,000,000 | hid-picolcd_core.c | 54,398,981,253,658,970,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3186 | Buffer overflow in the picolcd_raw_event function in devices/hid/hid-picolcd_core.c in the PicoLCD HID device driver in the Linux kernel through 3.16.3, as used in Android on Nexus 7 devices, allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a craft... | https://nvd.nist.gov/vuln/detail/CVE-2014-3186 |
38,618 | linux | 844817e47eef14141cf59b8d5ac08dd11c0a9189 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/844817e47eef14141cf59b8d5ac08dd11c0a9189 | HID: picolcd: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that raw_data
that we hold in picolcd_pending structure are always kept within proper
bounds.
Cc: stable@vger.kernel.org
Reported-... | 0 | int picolcd_reset(struct hid_device *hdev)
{
struct picolcd_data *data = hid_get_drvdata(hdev);
struct hid_report *report = picolcd_out_report(REPORT_RESET, hdev);
unsigned long flags;
int error;
if (!data || !report || report->maxfield != 1)
return -ENODEV;
spin_lock_irqsave(&data->lock, flags);
if (hdev->p... | 97,417,280,112,773,630,000,000,000,000,000,000,000 | hid-picolcd_core.c | 54,398,981,253,658,970,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3186 | Buffer overflow in the picolcd_raw_event function in devices/hid/hid-picolcd_core.c in the PicoLCD HID device driver in the Linux kernel through 3.16.3, as used in Android on Nexus 7 devices, allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a craft... | https://nvd.nist.gov/vuln/detail/CVE-2014-3186 |
38,619 | linux | 844817e47eef14141cf59b8d5ac08dd11c0a9189 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/844817e47eef14141cf59b8d5ac08dd11c0a9189 | HID: picolcd: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that raw_data
that we hold in picolcd_pending structure are always kept within proper
bounds.
Cc: stable@vger.kernel.org
Reported-... | 0 | static int picolcd_reset_resume(struct hid_device *hdev)
{
int ret;
ret = picolcd_reset(hdev);
if (ret)
dbg_hid(PICOLCD_NAME " resetting our device failed: %d\n", ret);
ret = picolcd_fb_reset(hid_get_drvdata(hdev), 0);
if (ret)
dbg_hid(PICOLCD_NAME " restoring framebuffer content failed: %d\n", ret);
ret = pi... | 43,112,218,717,284,660,000,000,000,000,000,000,000 | hid-picolcd_core.c | 54,398,981,253,658,970,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3186 | Buffer overflow in the picolcd_raw_event function in devices/hid/hid-picolcd_core.c in the PicoLCD HID device driver in the Linux kernel through 3.16.3, as used in Android on Nexus 7 devices, allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a craft... | https://nvd.nist.gov/vuln/detail/CVE-2014-3186 |
38,620 | linux | 844817e47eef14141cf59b8d5ac08dd11c0a9189 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/844817e47eef14141cf59b8d5ac08dd11c0a9189 | HID: picolcd: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that raw_data
that we hold in picolcd_pending structure are always kept within proper
bounds.
Cc: stable@vger.kernel.org
Reported-... | 0 | struct picolcd_pending *picolcd_send_and_wait(struct hid_device *hdev,
int report_id, const u8 *raw_data, int size)
{
struct picolcd_data *data = hid_get_drvdata(hdev);
struct picolcd_pending *work;
struct hid_report *report = picolcd_out_report(report_id, hdev);
unsigned long flags;
int i, j, k;
if (!report |... | 184,205,163,341,149,580,000,000,000,000,000,000,000 | hid-picolcd_core.c | 54,398,981,253,658,970,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3186 | Buffer overflow in the picolcd_raw_event function in devices/hid/hid-picolcd_core.c in the PicoLCD HID device driver in the Linux kernel through 3.16.3, as used in Android on Nexus 7 devices, allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a craft... | https://nvd.nist.gov/vuln/detail/CVE-2014-3186 |
38,621 | linux | 844817e47eef14141cf59b8d5ac08dd11c0a9189 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/844817e47eef14141cf59b8d5ac08dd11c0a9189 | HID: picolcd: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that raw_data
that we hold in picolcd_pending structure are always kept within proper
bounds.
Cc: stable@vger.kernel.org
Reported-... | 0 | static int picolcd_suspend(struct hid_device *hdev, pm_message_t message)
{
if (PMSG_IS_AUTO(message))
return 0;
picolcd_suspend_backlight(hid_get_drvdata(hdev));
dbg_hid(PICOLCD_NAME " device ready for suspend\n");
return 0;
}
| 259,482,958,348,009,750,000,000,000,000,000,000,000 | hid-picolcd_core.c | 54,398,981,253,658,970,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3186 | Buffer overflow in the picolcd_raw_event function in devices/hid/hid-picolcd_core.c in the PicoLCD HID device driver in the Linux kernel through 3.16.3, as used in Android on Nexus 7 devices, allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a craft... | https://nvd.nist.gov/vuln/detail/CVE-2014-3186 |
38,622 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 0 | static void command_port_write_callback(struct urb *urb)
{
int status = urb->status;
if (status) {
dev_dbg(&urb->dev->dev, "nonzero urb status: %d\n", status);
return;
}
}
| 141,073,277,494,933,060,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
38,623 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 0 | static int firm_close(struct usb_serial_port *port)
{
struct whiteheat_simple close_command;
close_command.port = port->port_number + 1;
return firm_send_command(port, WHITEHEAT_CLOSE,
(__u8 *)&close_command, sizeof(close_command));
}
| 89,241,202,770,054,890,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
38,624 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 0 | static int firm_get_dtr_rts(struct usb_serial_port *port)
{
struct whiteheat_simple get_dr_command;
get_dr_command.port = port->port_number + 1;
return firm_send_command(port, WHITEHEAT_GET_DTR_RTS,
(__u8 *)&get_dr_command, sizeof(get_dr_command));
}
| 225,449,735,290,916,300,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
38,625 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 0 | static int firm_open(struct usb_serial_port *port)
{
struct whiteheat_simple open_command;
open_command.port = port->port_number + 1;
return firm_send_command(port, WHITEHEAT_OPEN,
(__u8 *)&open_command, sizeof(open_command));
}
| 229,898,537,661,245,400,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
38,626 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 0 | static int firm_purge(struct usb_serial_port *port, __u8 rxtx)
{
struct whiteheat_purge purge_command;
purge_command.port = port->port_number + 1;
purge_command.what = rxtx;
return firm_send_command(port, WHITEHEAT_PURGE,
(__u8 *)&purge_command, sizeof(purge_command));
}
| 180,199,895,380,452,970,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
38,627 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 0 | static int firm_report_tx_done(struct usb_serial_port *port)
{
struct whiteheat_simple close_command;
close_command.port = port->port_number + 1;
return firm_send_command(port, WHITEHEAT_REPORT_TX_DONE,
(__u8 *)&close_command, sizeof(close_command));
}
| 329,515,410,823,742,560,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
38,628 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 0 | static int firm_send_command(struct usb_serial_port *port, __u8 command,
__u8 *data, __u8 datasize)
{
struct usb_serial_port *command_port;
struct whiteheat_command_private *command_info;
struct whiteheat_private *info;
struct device *dev = &port->dev;
__u8 *transfer_buffer;
int retval = 0;
int t;
dev_db... | 209,174,352,609,658,150,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
38,629 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 0 | static int firm_set_break(struct usb_serial_port *port, __u8 onoff)
{
struct whiteheat_set_rdb break_command;
break_command.port = port->port_number + 1;
break_command.state = onoff;
return firm_send_command(port, WHITEHEAT_SET_BREAK,
(__u8 *)&break_command, sizeof(break_command));
}
| 6,546,286,417,409,772,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
38,630 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 0 | static int firm_set_dtr(struct usb_serial_port *port, __u8 onoff)
{
struct whiteheat_set_rdb dtr_command;
dtr_command.port = port->port_number + 1;
dtr_command.state = onoff;
return firm_send_command(port, WHITEHEAT_SET_DTR,
(__u8 *)&dtr_command, sizeof(dtr_command));
}
| 169,475,046,659,808,120,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
38,631 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 0 | static int firm_set_rts(struct usb_serial_port *port, __u8 onoff)
{
struct whiteheat_set_rdb rts_command;
rts_command.port = port->port_number + 1;
rts_command.state = onoff;
return firm_send_command(port, WHITEHEAT_SET_RTS,
(__u8 *)&rts_command, sizeof(rts_command));
}
| 338,943,039,717,303,900,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
38,632 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 0 | static void firm_setup_port(struct tty_struct *tty)
{
struct usb_serial_port *port = tty->driver_data;
struct device *dev = &port->dev;
struct whiteheat_port_settings port_settings;
unsigned int cflag = tty->termios.c_cflag;
port_settings.port = port->port_number + 1;
/* get the byte size */
switch (cflag & CS... | 99,765,547,276,070,680,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
38,633 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 0 | static int start_command_port(struct usb_serial *serial)
{
struct usb_serial_port *command_port;
struct whiteheat_command_private *command_info;
int retval = 0;
command_port = serial->port[COMMAND_PORT];
command_info = usb_get_serial_port_data(command_port);
mutex_lock(&command_info->mutex);
if (!command_info->... | 182,001,225,958,667,400,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
38,634 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 0 | static void stop_command_port(struct usb_serial *serial)
{
struct usb_serial_port *command_port;
struct whiteheat_command_private *command_info;
command_port = serial->port[COMMAND_PORT];
command_info = usb_get_serial_port_data(command_port);
mutex_lock(&command_info->mutex);
command_info->port_running--;
if (!... | 2,877,795,018,080,407,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
38,635 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 0 | static int whiteheat_attach(struct usb_serial *serial)
{
struct usb_serial_port *command_port;
struct whiteheat_command_private *command_info;
struct whiteheat_hw_info *hw_info;
int pipe;
int ret;
int alen;
__u8 *command;
__u8 *result;
command_port = serial->port[COMMAND_PORT];
pipe = usb_sndbulkpipe(serial... | 313,199,698,449,220,970,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
38,636 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 0 | static void whiteheat_break_ctl(struct tty_struct *tty, int break_state)
{
struct usb_serial_port *port = tty->driver_data;
firm_set_break(port, break_state);
}
| 74,088,890,312,827,280,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
38,637 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 0 | static void whiteheat_close(struct usb_serial_port *port)
{
firm_report_tx_done(port);
firm_close(port);
usb_serial_generic_close(port);
stop_command_port(port->serial);
}
| 181,426,316,825,385,480,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
38,638 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 0 | static int whiteheat_firmware_attach(struct usb_serial *serial)
{
/* We want this device to fail to have a driver assigned to it */
return 1;
}
| 164,752,139,162,054,370,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
38,639 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 0 | static int whiteheat_firmware_download(struct usb_serial *serial,
const struct usb_device_id *id)
{
int response;
response = ezusb_fx1_ihex_firmware_download(serial->dev, "whiteheat_loader.fw");
if (response >= 0) {
response = ezusb_fx1_ihex_firmware_download(serial->dev, "whiteheat.fw");
if (response >= 0... | 124,082,019,699,778,700,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
38,640 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 0 | static int whiteheat_ioctl(struct tty_struct *tty,
unsigned int cmd, unsigned long arg)
{
struct usb_serial_port *port = tty->driver_data;
struct serial_struct serstruct;
void __user *user_arg = (void __user *)arg;
switch (cmd) {
case TIOCGSERIAL:
memset(&serstruct, 0, sizeof(serstruct));
serstruct.type ... | 262,688,316,751,253,200,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
38,641 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 0 | static int whiteheat_port_probe(struct usb_serial_port *port)
{
struct whiteheat_private *info;
info = kzalloc(sizeof(*info), GFP_KERNEL);
if (!info)
return -ENOMEM;
usb_set_serial_port_data(port, info);
return 0;
}
| 262,381,323,217,004,800,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
38,642 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 0 | static int whiteheat_port_remove(struct usb_serial_port *port)
{
struct whiteheat_private *info;
info = usb_get_serial_port_data(port);
kfree(info);
return 0;
}
| 309,693,539,187,744,140,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
38,643 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 0 | static void whiteheat_release(struct usb_serial *serial)
{
struct usb_serial_port *command_port;
/* free up our private data for our command port */
command_port = serial->port[COMMAND_PORT];
kfree(usb_get_serial_port_data(command_port));
}
| 270,198,274,448,135,280,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
38,644 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 0 | static void whiteheat_set_termios(struct tty_struct *tty,
struct usb_serial_port *port, struct ktermios *old_termios)
{
firm_setup_port(tty);
}
| 231,822,411,390,127,000,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
38,645 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 0 | static int whiteheat_tiocmget(struct tty_struct *tty)
{
struct usb_serial_port *port = tty->driver_data;
struct whiteheat_private *info = usb_get_serial_port_data(port);
unsigned int modem_signals = 0;
firm_get_dtr_rts(port);
if (info->mcr & UART_MCR_DTR)
modem_signals |= TIOCM_DTR;
if (info->mcr & UART_MCR_RT... | 278,834,688,827,756,820,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
38,646 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 0 | static int whiteheat_tiocmset(struct tty_struct *tty,
unsigned int set, unsigned int clear)
{
struct usb_serial_port *port = tty->driver_data;
struct whiteheat_private *info = usb_get_serial_port_data(port);
if (set & TIOCM_RTS)
info->mcr |= UART_MCR_RTS;
if (set & TIOCM_DTR)
info->mcr |= UART_MCR_DT... | 312,802,514,562,072,600,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
38,647 | linux | 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | HID: fix a couple of off-by-ones
There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing fixup. Fix those.
Cc: stable@vger.kernel.org
Reported-by: Ben Hawkes <hawkes@google.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jir... | 0 | static int ch_input_mapping(struct hid_device *hdev, struct hid_input *hi,
struct hid_field *field, struct hid_usage *usage,
unsigned long **bit, int *max)
{
if ((usage->hid & HID_USAGE_PAGE) != HID_UP_CONSUMER)
return 0;
switch (usage->hid & HID_USAGE) {
case 0x301: ch_map_key_clear(KEY_PROG1); break;
case ... | 102,097,538,560,917,830,000,000,000,000,000,000,000 | hid-cherry.c | 95,105,781,901,221,440,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3184 | The report_fixup functions in the HID subsystem in the Linux kernel before 3.16.2 might allow physically proximate attackers to cause a denial of service (out-of-bounds write) via a crafted device that provides a small report descriptor, related to (1) drivers/hid/hid-cherry.c, (2) drivers/hid/hid-kye.c, (3) drivers/hi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3184 |
38,648 | linux | 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | HID: fix a couple of off-by-ones
There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing fixup. Fix those.
Cc: stable@vger.kernel.org
Reported-by: Ben Hawkes <hawkes@google.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jir... | 0 | static __u8 *kye_consumer_control_fixup(struct hid_device *hdev, __u8 *rdesc,
unsigned int *rsize, int offset, const char *device_name) {
/*
* the fixup that need to be done:
* - change Usage Maximum in the Comsumer Control
* (report ID 3) to a reasonable value
*/
if (*rsize >= offset + 31 &&
/* ... | 271,554,957,569,145,350,000,000,000,000,000,000,000 | hid-kye.c | 203,442,816,039,038,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3184 | The report_fixup functions in the HID subsystem in the Linux kernel before 3.16.2 might allow physically proximate attackers to cause a denial of service (out-of-bounds write) via a crafted device that provides a small report descriptor, related to (1) drivers/hid/hid-cherry.c, (2) drivers/hid/hid-kye.c, (3) drivers/hi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3184 |
38,649 | linux | 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | HID: fix a couple of off-by-ones
There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing fixup. Fix those.
Cc: stable@vger.kernel.org
Reported-by: Ben Hawkes <hawkes@google.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jir... | 0 | static int kye_probe(struct hid_device *hdev, const struct hid_device_id *id)
{
int ret;
ret = hid_parse(hdev);
if (ret) {
hid_err(hdev, "parse failed\n");
goto err;
}
ret = hid_hw_start(hdev, HID_CONNECT_DEFAULT);
if (ret) {
hid_err(hdev, "hw start failed\n");
goto err;
}
switch (id->product) {
cas... | 334,185,202,728,012,900,000,000,000,000,000,000,000 | hid-kye.c | 203,442,816,039,038,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3184 | The report_fixup functions in the HID subsystem in the Linux kernel before 3.16.2 might allow physically proximate attackers to cause a denial of service (out-of-bounds write) via a crafted device that provides a small report descriptor, related to (1) drivers/hid/hid-cherry.c, (2) drivers/hid/hid-kye.c, (3) drivers/hi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3184 |
38,650 | linux | 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | HID: fix a couple of off-by-ones
There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing fixup. Fix those.
Cc: stable@vger.kernel.org
Reported-by: Ben Hawkes <hawkes@google.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jir... | 0 | static int kye_tablet_enable(struct hid_device *hdev)
{
struct list_head *list;
struct list_head *head;
struct hid_report *report;
__s32 *value;
list = &hdev->report_enum[HID_FEATURE_REPORT].report_list;
list_for_each(head, list) {
report = list_entry(head, struct hid_report, list);
if (report->id == 5)
b... | 268,861,528,969,284,760,000,000,000,000,000,000,000 | hid-kye.c | 203,442,816,039,038,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3184 | The report_fixup functions in the HID subsystem in the Linux kernel before 3.16.2 might allow physically proximate attackers to cause a denial of service (out-of-bounds write) via a crafted device that provides a small report descriptor, related to (1) drivers/hid/hid-cherry.c, (2) drivers/hid/hid-kye.c, (3) drivers/hi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3184 |
38,651 | linux | 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | HID: fix a couple of off-by-ones
There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing fixup. Fix those.
Cc: stable@vger.kernel.org
Reported-by: Ben Hawkes <hawkes@google.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jir... | 0 | static int lg_dinovo_mapping(struct hid_input *hi, struct hid_usage *usage,
unsigned long **bit, int *max)
{
if ((usage->hid & HID_USAGE_PAGE) != HID_UP_LOGIVENDOR)
return 0;
switch (usage->hid & HID_USAGE) {
case 0x00d: lg_map_key_clear(KEY_MEDIA); break;
default:
return 0;
}
return 1;
}
| 79,884,003,040,166,540,000,000,000,000,000,000,000 | hid-lg.c | 208,620,246,657,498,000,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3184 | The report_fixup functions in the HID subsystem in the Linux kernel before 3.16.2 might allow physically proximate attackers to cause a denial of service (out-of-bounds write) via a crafted device that provides a small report descriptor, related to (1) drivers/hid/hid-cherry.c, (2) drivers/hid/hid-kye.c, (3) drivers/hi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3184 |
38,652 | linux | 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | HID: fix a couple of off-by-ones
There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing fixup. Fix those.
Cc: stable@vger.kernel.org
Reported-by: Ben Hawkes <hawkes@google.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jir... | 0 | static int lg_event(struct hid_device *hdev, struct hid_field *field,
struct hid_usage *usage, __s32 value)
{
struct lg_drv_data *drv_data = hid_get_drvdata(hdev);
if ((drv_data->quirks & LG_INVERT_HWHEEL) && usage->code == REL_HWHEEL) {
input_event(field->hidinput->input, usage->type, usage->code,
-value);
... | 307,612,626,334,718,950,000,000,000,000,000,000,000 | hid-lg.c | 208,620,246,657,498,000,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3184 | The report_fixup functions in the HID subsystem in the Linux kernel before 3.16.2 might allow physically proximate attackers to cause a denial of service (out-of-bounds write) via a crafted device that provides a small report descriptor, related to (1) drivers/hid/hid-cherry.c, (2) drivers/hid/hid-kye.c, (3) drivers/hi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3184 |
38,653 | linux | 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | HID: fix a couple of off-by-ones
There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing fixup. Fix those.
Cc: stable@vger.kernel.org
Reported-by: Ben Hawkes <hawkes@google.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jir... | 0 | static int lg_input_mapped(struct hid_device *hdev, struct hid_input *hi,
struct hid_field *field, struct hid_usage *usage,
unsigned long **bit, int *max)
{
struct lg_drv_data *drv_data = hid_get_drvdata(hdev);
if ((drv_data->quirks & LG_BAD_RELATIVE_KEYS) && usage->type == EV_KEY &&
(field->flags & HID_MAIN_... | 209,234,584,538,811,830,000,000,000,000,000,000,000 | hid-lg.c | 208,620,246,657,498,000,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3184 | The report_fixup functions in the HID subsystem in the Linux kernel before 3.16.2 might allow physically proximate attackers to cause a denial of service (out-of-bounds write) via a crafted device that provides a small report descriptor, related to (1) drivers/hid/hid-cherry.c, (2) drivers/hid/hid-kye.c, (3) drivers/hi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3184 |
38,654 | linux | 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | HID: fix a couple of off-by-ones
There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing fixup. Fix those.
Cc: stable@vger.kernel.org
Reported-by: Ben Hawkes <hawkes@google.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jir... | 0 | static void lg_remove(struct hid_device *hdev)
{
struct lg_drv_data *drv_data = hid_get_drvdata(hdev);
if (drv_data->quirks & LG_FF4)
lg4ff_deinit(hdev);
hid_hw_stop(hdev);
kfree(drv_data);
}
| 264,982,849,589,098,220,000,000,000,000,000,000,000 | hid-lg.c | 208,620,246,657,498,000,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3184 | The report_fixup functions in the HID subsystem in the Linux kernel before 3.16.2 might allow physically proximate attackers to cause a denial of service (out-of-bounds write) via a crafted device that provides a small report descriptor, related to (1) drivers/hid/hid-cherry.c, (2) drivers/hid/hid-kye.c, (3) drivers/hi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3184 |
38,655 | linux | 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | HID: fix a couple of off-by-ones
There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing fixup. Fix those.
Cc: stable@vger.kernel.org
Reported-by: Ben Hawkes <hawkes@google.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jir... | 0 | static int lg_ultrax_remote_mapping(struct hid_input *hi,
struct hid_usage *usage, unsigned long **bit, int *max)
{
if ((usage->hid & HID_USAGE_PAGE) != HID_UP_LOGIVENDOR)
return 0;
set_bit(EV_REP, hi->input->evbit);
switch (usage->hid & HID_USAGE) {
/* Reported on Logitech Ultra X Media Remote */
case 0x004:... | 183,937,830,665,222,330,000,000,000,000,000,000,000 | hid-lg.c | 208,620,246,657,498,000,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3184 | The report_fixup functions in the HID subsystem in the Linux kernel before 3.16.2 might allow physically proximate attackers to cause a denial of service (out-of-bounds write) via a crafted device that provides a small report descriptor, related to (1) drivers/hid/hid-cherry.c, (2) drivers/hid/hid-kye.c, (3) drivers/hi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3184 |
38,656 | linux | 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | HID: fix a couple of off-by-ones
There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing fixup. Fix those.
Cc: stable@vger.kernel.org
Reported-by: Ben Hawkes <hawkes@google.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jir... | 0 | static int lg_wireless_mapping(struct hid_input *hi, struct hid_usage *usage,
unsigned long **bit, int *max)
{
if ((usage->hid & HID_USAGE_PAGE) != HID_UP_CONSUMER)
return 0;
switch (usage->hid & HID_USAGE) {
case 0x1001: lg_map_key_clear(KEY_MESSENGER); break;
case 0x1003: lg_map_key_clear(KEY_SOUND); break... | 1,498,971,952,675,268,000,000,000,000,000,000,000 | hid-lg.c | 208,620,246,657,498,000,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3184 | The report_fixup functions in the HID subsystem in the Linux kernel before 3.16.2 might allow physically proximate attackers to cause a denial of service (out-of-bounds write) via a crafted device that provides a small report descriptor, related to (1) drivers/hid/hid-cherry.c, (2) drivers/hid/hid-kye.c, (3) drivers/hi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3184 |
38,657 | linux | 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | HID: fix a couple of off-by-ones
There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing fixup. Fix those.
Cc: stable@vger.kernel.org
Reported-by: Ben Hawkes <hawkes@google.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jir... | 0 | static int pl_input_mapping(struct hid_device *hdev, struct hid_input *hi,
struct hid_field *field, struct hid_usage *usage,
unsigned long **bit, int *max)
{
if ((usage->hid & HID_USAGE_PAGE) == HID_UP_LOGIVENDOR) {
switch (usage->hid & HID_USAGE) {
case 0x05a: pl_map_key_clear(KEY_TEXT); break;
case 0x05b:... | 274,443,530,790,004,260,000,000,000,000,000,000,000 | hid-petalynx.c | 198,495,724,561,306,000,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3184 | The report_fixup functions in the HID subsystem in the Linux kernel before 3.16.2 might allow physically proximate attackers to cause a denial of service (out-of-bounds write) via a crafted device that provides a small report descriptor, related to (1) drivers/hid/hid-cherry.c, (2) drivers/hid/hid-kye.c, (3) drivers/hi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3184 |
38,658 | linux | 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | HID: fix a couple of off-by-ones
There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing fixup. Fix those.
Cc: stable@vger.kernel.org
Reported-by: Ben Hawkes <hawkes@google.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jir... | 0 | static int sp_input_mapping(struct hid_device *hdev, struct hid_input *hi,
struct hid_field *field, struct hid_usage *usage,
unsigned long **bit, int *max)
{
if ((usage->hid & HID_USAGE_PAGE) != HID_UP_CONSUMER)
return 0;
switch (usage->hid & HID_USAGE) {
case 0x2003: sp_map_key_clear(KEY_ZOOMIN); break;
ca... | 38,261,245,527,434,870,000,000,000,000,000,000,000 | hid-sunplus.c | 218,029,391,092,850,470,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3184 | The report_fixup functions in the HID subsystem in the Linux kernel before 3.16.2 might allow physically proximate attackers to cause a denial of service (out-of-bounds write) via a crafted device that provides a small report descriptor, related to (1) drivers/hid/hid-cherry.c, (2) drivers/hid/hid-kye.c, (3) drivers/hi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3184 |
38,659 | linux | 51217e69697fba92a06e07e16f55c9a52d8e8945 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/51217e69697fba92a06e07e16f55c9a52d8e8945 | HID: logitech: fix bounds checking on LED report size
The check on report size for REPORT_TYPE_LEDS in logi_dj_ll_raw_request()
is wrong; the current check doesn't make any sense -- the report allocated
by HID core in hid_hw_raw_request() can be much larger than
DJREPORT_SHORT_LENGTH, and currently logi_dj_ll_raw_requ... | 0 | static void delayedwork_callback(struct work_struct *work)
{
struct dj_receiver_dev *djrcv_dev =
container_of(work, struct dj_receiver_dev, work);
struct dj_report dj_report;
unsigned long flags;
int count;
int retval;
dbg_hid("%s\n", __func__);
spin_lock_irqsave(&djrcv_dev->lock, flags);
count = kfifo_ou... | 177,416,945,380,085,250,000,000,000,000,000,000,000 | hid-logitech-dj.c | 286,797,026,497,837,260,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3183 | Heap-based buffer overflow in the logi_dj_ll_raw_request function in drivers/hid/hid-logitech-dj.c in the Linux kernel before 3.16.2 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that specifies a large report size for an LED rep... | https://nvd.nist.gov/vuln/detail/CVE-2014-3183 |
38,660 | linux | 51217e69697fba92a06e07e16f55c9a52d8e8945 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/51217e69697fba92a06e07e16f55c9a52d8e8945 | HID: logitech: fix bounds checking on LED report size
The check on report size for REPORT_TYPE_LEDS in logi_dj_ll_raw_request()
is wrong; the current check doesn't make any sense -- the report allocated
by HID core in hid_hw_raw_request() can be much larger than
DJREPORT_SHORT_LENGTH, and currently logi_dj_ll_raw_requ... | 0 | static void __exit logi_dj_exit(void)
{
dbg_hid("Logitech-DJ:%s\n", __func__);
hid_unregister_driver(&logi_djdevice_driver);
hid_unregister_driver(&logi_djreceiver_driver);
}
| 17,573,848,099,879,747,000,000,000,000,000,000,000 | hid-logitech-dj.c | 286,797,026,497,837,260,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3183 | Heap-based buffer overflow in the logi_dj_ll_raw_request function in drivers/hid/hid-logitech-dj.c in the Linux kernel before 3.16.2 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that specifies a large report size for an LED rep... | https://nvd.nist.gov/vuln/detail/CVE-2014-3183 |
38,661 | linux | 51217e69697fba92a06e07e16f55c9a52d8e8945 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/51217e69697fba92a06e07e16f55c9a52d8e8945 | HID: logitech: fix bounds checking on LED report size
The check on report size for REPORT_TYPE_LEDS in logi_dj_ll_raw_request()
is wrong; the current check doesn't make any sense -- the report allocated
by HID core in hid_hw_raw_request() can be much larger than
DJREPORT_SHORT_LENGTH, and currently logi_dj_ll_raw_requ... | 0 | static int __init logi_dj_init(void)
{
int retval;
dbg_hid("Logitech-DJ:%s\n", __func__);
retval = hid_register_driver(&logi_djreceiver_driver);
if (retval)
return retval;
retval = hid_register_driver(&logi_djdevice_driver);
if (retval)
hid_unregister_driver(&logi_djreceiver_driver);
return retval;
}
| 86,477,403,150,689,750,000,000,000,000,000,000,000 | hid-logitech-dj.c | 286,797,026,497,837,260,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3183 | Heap-based buffer overflow in the logi_dj_ll_raw_request function in drivers/hid/hid-logitech-dj.c in the Linux kernel before 3.16.2 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that specifies a large report size for an LED rep... | https://nvd.nist.gov/vuln/detail/CVE-2014-3183 |
38,662 | linux | 51217e69697fba92a06e07e16f55c9a52d8e8945 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/51217e69697fba92a06e07e16f55c9a52d8e8945 | HID: logitech: fix bounds checking on LED report size
The check on report size for REPORT_TYPE_LEDS in logi_dj_ll_raw_request()
is wrong; the current check doesn't make any sense -- the report allocated
by HID core in hid_hw_raw_request() can be much larger than
DJREPORT_SHORT_LENGTH, and currently logi_dj_ll_raw_requ... | 0 | static void logi_dj_ll_close(struct hid_device *hid)
{
dbg_hid("%s:%s\n", __func__, hid->phys);
}
| 282,009,588,716,175,940,000,000,000,000,000,000,000 | hid-logitech-dj.c | 286,797,026,497,837,260,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3183 | Heap-based buffer overflow in the logi_dj_ll_raw_request function in drivers/hid/hid-logitech-dj.c in the Linux kernel before 3.16.2 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that specifies a large report size for an LED rep... | https://nvd.nist.gov/vuln/detail/CVE-2014-3183 |
38,663 | linux | 51217e69697fba92a06e07e16f55c9a52d8e8945 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/51217e69697fba92a06e07e16f55c9a52d8e8945 | HID: logitech: fix bounds checking on LED report size
The check on report size for REPORT_TYPE_LEDS in logi_dj_ll_raw_request()
is wrong; the current check doesn't make any sense -- the report allocated
by HID core in hid_hw_raw_request() can be much larger than
DJREPORT_SHORT_LENGTH, and currently logi_dj_ll_raw_requ... | 0 | static int logi_dj_ll_open(struct hid_device *hid)
{
dbg_hid("%s:%s\n", __func__, hid->phys);
return 0;
}
| 199,459,213,825,527,200,000,000,000,000,000,000,000 | hid-logitech-dj.c | 286,797,026,497,837,260,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3183 | Heap-based buffer overflow in the logi_dj_ll_raw_request function in drivers/hid/hid-logitech-dj.c in the Linux kernel before 3.16.2 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that specifies a large report size for an LED rep... | https://nvd.nist.gov/vuln/detail/CVE-2014-3183 |
38,664 | linux | 51217e69697fba92a06e07e16f55c9a52d8e8945 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/51217e69697fba92a06e07e16f55c9a52d8e8945 | HID: logitech: fix bounds checking on LED report size
The check on report size for REPORT_TYPE_LEDS in logi_dj_ll_raw_request()
is wrong; the current check doesn't make any sense -- the report allocated
by HID core in hid_hw_raw_request() can be much larger than
DJREPORT_SHORT_LENGTH, and currently logi_dj_ll_raw_requ... | 0 | static int logi_dj_ll_parse(struct hid_device *hid)
{
struct dj_device *djdev = hid->driver_data;
unsigned int rsize = 0;
char *rdesc;
int retval;
dbg_hid("%s\n", __func__);
djdev->hdev->version = 0x0111;
djdev->hdev->country = 0x00;
rdesc = kmalloc(MAX_RDESC_SIZE, GFP_KERNEL);
if (!rdesc)
return -ENOMEM;... | 246,361,234,771,343,060,000,000,000,000,000,000,000 | hid-logitech-dj.c | 286,797,026,497,837,260,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3183 | Heap-based buffer overflow in the logi_dj_ll_raw_request function in drivers/hid/hid-logitech-dj.c in the Linux kernel before 3.16.2 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that specifies a large report size for an LED rep... | https://nvd.nist.gov/vuln/detail/CVE-2014-3183 |
38,665 | linux | 51217e69697fba92a06e07e16f55c9a52d8e8945 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/51217e69697fba92a06e07e16f55c9a52d8e8945 | HID: logitech: fix bounds checking on LED report size
The check on report size for REPORT_TYPE_LEDS in logi_dj_ll_raw_request()
is wrong; the current check doesn't make any sense -- the report allocated
by HID core in hid_hw_raw_request() can be much larger than
DJREPORT_SHORT_LENGTH, and currently logi_dj_ll_raw_requ... | 0 | static int logi_dj_ll_start(struct hid_device *hid)
{
dbg_hid("%s\n", __func__);
return 0;
}
| 283,068,144,288,328,250,000,000,000,000,000,000,000 | hid-logitech-dj.c | 286,797,026,497,837,260,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3183 | Heap-based buffer overflow in the logi_dj_ll_raw_request function in drivers/hid/hid-logitech-dj.c in the Linux kernel before 3.16.2 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that specifies a large report size for an LED rep... | https://nvd.nist.gov/vuln/detail/CVE-2014-3183 |
38,666 | linux | 51217e69697fba92a06e07e16f55c9a52d8e8945 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/51217e69697fba92a06e07e16f55c9a52d8e8945 | HID: logitech: fix bounds checking on LED report size
The check on report size for REPORT_TYPE_LEDS in logi_dj_ll_raw_request()
is wrong; the current check doesn't make any sense -- the report allocated
by HID core in hid_hw_raw_request() can be much larger than
DJREPORT_SHORT_LENGTH, and currently logi_dj_ll_raw_requ... | 0 | static void logi_dj_ll_stop(struct hid_device *hid)
{
dbg_hid("%s\n", __func__);
}
| 208,103,118,936,902,930,000,000,000,000,000,000,000 | hid-logitech-dj.c | 286,797,026,497,837,260,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3183 | Heap-based buffer overflow in the logi_dj_ll_raw_request function in drivers/hid/hid-logitech-dj.c in the Linux kernel before 3.16.2 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that specifies a large report size for an LED rep... | https://nvd.nist.gov/vuln/detail/CVE-2014-3183 |
38,667 | linux | 51217e69697fba92a06e07e16f55c9a52d8e8945 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/51217e69697fba92a06e07e16f55c9a52d8e8945 | HID: logitech: fix bounds checking on LED report size
The check on report size for REPORT_TYPE_LEDS in logi_dj_ll_raw_request()
is wrong; the current check doesn't make any sense -- the report allocated
by HID core in hid_hw_raw_request() can be much larger than
DJREPORT_SHORT_LENGTH, and currently logi_dj_ll_raw_requ... | 0 | static int logi_dj_probe(struct hid_device *hdev,
const struct hid_device_id *id)
{
struct usb_interface *intf = to_usb_interface(hdev->dev.parent);
struct dj_receiver_dev *djrcv_dev;
int retval;
if (is_dj_device((struct dj_device *)hdev->driver_data))
return -ENODEV;
dbg_hid("%s called for ifnum %d\n", __... | 165,760,926,246,242,950,000,000,000,000,000,000,000 | hid-logitech-dj.c | 286,797,026,497,837,260,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3183 | Heap-based buffer overflow in the logi_dj_ll_raw_request function in drivers/hid/hid-logitech-dj.c in the Linux kernel before 3.16.2 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that specifies a large report size for an LED rep... | https://nvd.nist.gov/vuln/detail/CVE-2014-3183 |
38,668 | linux | 51217e69697fba92a06e07e16f55c9a52d8e8945 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/51217e69697fba92a06e07e16f55c9a52d8e8945 | HID: logitech: fix bounds checking on LED report size
The check on report size for REPORT_TYPE_LEDS in logi_dj_ll_raw_request()
is wrong; the current check doesn't make any sense -- the report allocated
by HID core in hid_hw_raw_request() can be much larger than
DJREPORT_SHORT_LENGTH, and currently logi_dj_ll_raw_requ... | 0 | static void logi_dj_recv_destroy_djhid_device(struct dj_receiver_dev *djrcv_dev,
struct dj_report *dj_report)
{
/* Called in delayed work context */
struct dj_device *dj_dev;
unsigned long flags;
spin_lock_irqsave(&djrcv_dev->lock, flags);
dj_dev = djrcv_dev->paired_dj_devices[dj_report->device_index];
djr... | 205,498,249,855,783,420,000,000,000,000,000,000,000 | hid-logitech-dj.c | 286,797,026,497,837,260,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3183 | Heap-based buffer overflow in the logi_dj_ll_raw_request function in drivers/hid/hid-logitech-dj.c in the Linux kernel before 3.16.2 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that specifies a large report size for an LED rep... | https://nvd.nist.gov/vuln/detail/CVE-2014-3183 |
38,669 | linux | 51217e69697fba92a06e07e16f55c9a52d8e8945 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/51217e69697fba92a06e07e16f55c9a52d8e8945 | HID: logitech: fix bounds checking on LED report size
The check on report size for REPORT_TYPE_LEDS in logi_dj_ll_raw_request()
is wrong; the current check doesn't make any sense -- the report allocated
by HID core in hid_hw_raw_request() can be much larger than
DJREPORT_SHORT_LENGTH, and currently logi_dj_ll_raw_requ... | 0 | static void logi_dj_recv_forward_null_report(struct dj_receiver_dev *djrcv_dev,
struct dj_report *dj_report)
{
/* We are called from atomic context (tasklet && djrcv->lock held) */
unsigned int i;
u8 reportbuffer[MAX_REPORT_SIZE];
struct dj_device *djdev;
djdev = djrcv_dev->paired_dj_devices[dj_report->... | 225,577,866,554,059,870,000,000,000,000,000,000,000 | hid-logitech-dj.c | 286,797,026,497,837,260,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3183 | Heap-based buffer overflow in the logi_dj_ll_raw_request function in drivers/hid/hid-logitech-dj.c in the Linux kernel before 3.16.2 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that specifies a large report size for an LED rep... | https://nvd.nist.gov/vuln/detail/CVE-2014-3183 |
38,670 | linux | 51217e69697fba92a06e07e16f55c9a52d8e8945 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/51217e69697fba92a06e07e16f55c9a52d8e8945 | HID: logitech: fix bounds checking on LED report size
The check on report size for REPORT_TYPE_LEDS in logi_dj_ll_raw_request()
is wrong; the current check doesn't make any sense -- the report allocated
by HID core in hid_hw_raw_request() can be much larger than
DJREPORT_SHORT_LENGTH, and currently logi_dj_ll_raw_requ... | 0 | static void logi_dj_recv_forward_report(struct dj_receiver_dev *djrcv_dev,
struct dj_report *dj_report)
{
/* We are called from atomic context (tasklet && djrcv->lock held) */
struct dj_device *dj_device;
dj_device = djrcv_dev->paired_dj_devices[dj_report->device_index];
if (dj_device == NULL) {
dbg_hid("d... | 318,836,606,083,718,350,000,000,000,000,000,000,000 | hid-logitech-dj.c | 286,797,026,497,837,260,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3183 | Heap-based buffer overflow in the logi_dj_ll_raw_request function in drivers/hid/hid-logitech-dj.c in the Linux kernel before 3.16.2 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that specifies a large report size for an LED rep... | https://nvd.nist.gov/vuln/detail/CVE-2014-3183 |
38,671 | linux | 51217e69697fba92a06e07e16f55c9a52d8e8945 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/51217e69697fba92a06e07e16f55c9a52d8e8945 | HID: logitech: fix bounds checking on LED report size
The check on report size for REPORT_TYPE_LEDS in logi_dj_ll_raw_request()
is wrong; the current check doesn't make any sense -- the report allocated
by HID core in hid_hw_raw_request() can be much larger than
DJREPORT_SHORT_LENGTH, and currently logi_dj_ll_raw_requ... | 0 | static int logi_dj_recv_query_paired_devices(struct dj_receiver_dev *djrcv_dev)
{
struct dj_report *dj_report;
int retval;
/* no need to protect djrcv_dev->querying_devices */
if (djrcv_dev->querying_devices)
return 0;
dj_report = kzalloc(sizeof(struct dj_report), GFP_KERNEL);
if (!dj_report)
return -ENOMEM... | 332,068,476,834,861,930,000,000,000,000,000,000,000 | hid-logitech-dj.c | 286,797,026,497,837,260,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3183 | Heap-based buffer overflow in the logi_dj_ll_raw_request function in drivers/hid/hid-logitech-dj.c in the Linux kernel before 3.16.2 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that specifies a large report size for an LED rep... | https://nvd.nist.gov/vuln/detail/CVE-2014-3183 |
38,672 | linux | 51217e69697fba92a06e07e16f55c9a52d8e8945 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/51217e69697fba92a06e07e16f55c9a52d8e8945 | HID: logitech: fix bounds checking on LED report size
The check on report size for REPORT_TYPE_LEDS in logi_dj_ll_raw_request()
is wrong; the current check doesn't make any sense -- the report allocated
by HID core in hid_hw_raw_request() can be much larger than
DJREPORT_SHORT_LENGTH, and currently logi_dj_ll_raw_requ... | 0 | static void logi_dj_recv_queue_notification(struct dj_receiver_dev *djrcv_dev,
struct dj_report *dj_report)
{
/* We are called from atomic context (tasklet && djrcv->lock held) */
kfifo_in(&djrcv_dev->notif_fifo, dj_report, sizeof(struct dj_report));
if (schedule_work(&djrcv_dev->work) == 0) {
dbg_hid("%... | 160,774,487,082,644,370,000,000,000,000,000,000,000 | hid-logitech-dj.c | 286,797,026,497,837,260,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3183 | Heap-based buffer overflow in the logi_dj_ll_raw_request function in drivers/hid/hid-logitech-dj.c in the Linux kernel before 3.16.2 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that specifies a large report size for an LED rep... | https://nvd.nist.gov/vuln/detail/CVE-2014-3183 |
38,673 | linux | 51217e69697fba92a06e07e16f55c9a52d8e8945 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/51217e69697fba92a06e07e16f55c9a52d8e8945 | HID: logitech: fix bounds checking on LED report size
The check on report size for REPORT_TYPE_LEDS in logi_dj_ll_raw_request()
is wrong; the current check doesn't make any sense -- the report allocated
by HID core in hid_hw_raw_request() can be much larger than
DJREPORT_SHORT_LENGTH, and currently logi_dj_ll_raw_requ... | 0 | static int logi_dj_recv_send_report(struct dj_receiver_dev *djrcv_dev,
struct dj_report *dj_report)
{
struct hid_device *hdev = djrcv_dev->hdev;
struct hid_report *report;
struct hid_report_enum *output_report_enum;
u8 *data = (u8 *)(&dj_report->device_index);
unsigned int i;
output_report_enum = &hdev->... | 16,755,959,976,289,300,000,000,000,000,000,000,000 | hid-logitech-dj.c | 286,797,026,497,837,260,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3183 | Heap-based buffer overflow in the logi_dj_ll_raw_request function in drivers/hid/hid-logitech-dj.c in the Linux kernel before 3.16.2 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that specifies a large report size for an LED rep... | https://nvd.nist.gov/vuln/detail/CVE-2014-3183 |
38,674 | linux | 51217e69697fba92a06e07e16f55c9a52d8e8945 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/51217e69697fba92a06e07e16f55c9a52d8e8945 | HID: logitech: fix bounds checking on LED report size
The check on report size for REPORT_TYPE_LEDS in logi_dj_ll_raw_request()
is wrong; the current check doesn't make any sense -- the report allocated
by HID core in hid_hw_raw_request() can be much larger than
DJREPORT_SHORT_LENGTH, and currently logi_dj_ll_raw_requ... | 0 | static void logi_dj_remove(struct hid_device *hdev)
{
struct dj_receiver_dev *djrcv_dev = hid_get_drvdata(hdev);
struct dj_device *dj_dev;
int i;
dbg_hid("%s\n", __func__);
cancel_work_sync(&djrcv_dev->work);
hid_hw_close(hdev);
hid_hw_stop(hdev);
/* I suppose that at this point the only context that can ac... | 252,803,437,834,031,550,000,000,000,000,000,000,000 | hid-logitech-dj.c | 286,797,026,497,837,260,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3183 | Heap-based buffer overflow in the logi_dj_ll_raw_request function in drivers/hid/hid-logitech-dj.c in the Linux kernel before 3.16.2 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that specifies a large report size for an LED rep... | https://nvd.nist.gov/vuln/detail/CVE-2014-3183 |
38,675 | linux | 51217e69697fba92a06e07e16f55c9a52d8e8945 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/51217e69697fba92a06e07e16f55c9a52d8e8945 | HID: logitech: fix bounds checking on LED report size
The check on report size for REPORT_TYPE_LEDS in logi_dj_ll_raw_request()
is wrong; the current check doesn't make any sense -- the report allocated
by HID core in hid_hw_raw_request() can be much larger than
DJREPORT_SHORT_LENGTH, and currently logi_dj_ll_raw_requ... | 0 | static int logi_djdevice_probe(struct hid_device *hdev,
const struct hid_device_id *id)
{
int ret;
struct dj_device *dj_dev = hdev->driver_data;
if (!is_dj_device(dj_dev))
return -ENODEV;
ret = hid_parse(hdev);
if (!ret)
ret = hid_hw_start(hdev, HID_CONNECT_DEFAULT);
return ret;
}
| 323,962,059,544,722,600,000,000,000,000,000,000,000 | hid-logitech-dj.c | 286,797,026,497,837,260,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3183 | Heap-based buffer overflow in the logi_dj_ll_raw_request function in drivers/hid/hid-logitech-dj.c in the Linux kernel before 3.16.2 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that specifies a large report size for an LED rep... | https://nvd.nist.gov/vuln/detail/CVE-2014-3183 |
38,676 | linux | ad3e14d7c5268c2e24477c6ef54bbdf88add5d36 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ad3e14d7c5268c2e24477c6ef54bbdf88add5d36 | HID: logitech: perform bounds checking on device_id early enough
device_index is a char type and the size of paired_dj_deivces is 7
elements, therefore proper bounds checking has to be applied to
device_index before it is used.
We are currently performing the bounds checking in
logi_dj_recv_add_djhid_device(), which ... | 0 | static int logi_dj_ll_raw_request(struct hid_device *hid,
unsigned char reportnum, __u8 *buf,
size_t count, unsigned char report_type,
int reqtype)
{
struct dj_device *djdev = hid->driver_data;
struct dj_receiver_dev *djrcv_dev = djdev->dj_receiver_dev;
u8 *out_buf;
int ret;
if (buf[0] != REPORT... | 114,738,344,567,700,010,000,000,000,000,000,000,000 | hid-logitech-dj.c | 286,797,026,497,837,260,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3182 | Array index error in the logi_dj_raw_event function in drivers/hid/hid-logitech-dj.c in the Linux kernel before 3.16.2 allows physically proximate attackers to execute arbitrary code or cause a denial of service (invalid kfree) via a crafted device that provides a malformed REPORT_TYPE_NOTIF_DEVICE_UNPAIRED value. | https://nvd.nist.gov/vuln/detail/CVE-2014-3182 |
38,677 | linux | c54def7bd64d7c0b6993336abcffb8444795bf38 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c54def7bd64d7c0b6993336abcffb8444795bf38 | HID: magicmouse: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that
magicmouse_emit_touch() gets only valid values of raw_id.
Cc: stable@vger.kernel.org
Reported-by: Steven Vittitoe <scvitti... | 0 | static void magicmouse_emit_buttons(struct magicmouse_sc *msc, int state)
{
int last_state = test_bit(BTN_LEFT, msc->input->key) << 0 |
test_bit(BTN_RIGHT, msc->input->key) << 1 |
test_bit(BTN_MIDDLE, msc->input->key) << 2;
if (emulate_3button) {
int id;
/* If some button was pressed before, keep it held
... | 6,170,163,191,731,677,000,000,000,000,000,000,000 | hid-magicmouse.c | 2,593,342,493,104,003,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3181 | Multiple stack-based buffer overflows in the magicmouse_raw_event function in drivers/hid/hid-magicmouse.c in the Magic Mouse HID driver in the Linux kernel through 3.16.3 allow physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that provid... | https://nvd.nist.gov/vuln/detail/CVE-2014-3181 |
38,678 | linux | c54def7bd64d7c0b6993336abcffb8444795bf38 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c54def7bd64d7c0b6993336abcffb8444795bf38 | HID: magicmouse: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that
magicmouse_emit_touch() gets only valid values of raw_id.
Cc: stable@vger.kernel.org
Reported-by: Steven Vittitoe <scvitti... | 0 | static void magicmouse_emit_touch(struct magicmouse_sc *msc, int raw_id, u8 *tdata)
{
struct input_dev *input = msc->input;
int id, x, y, size, orientation, touch_major, touch_minor, state, down;
if (input->id.product == USB_DEVICE_ID_APPLE_MAGICMOUSE) {
id = (tdata[6] << 2 | tdata[5] >> 6) & 0xf;
x = (tdata[1]... | 317,982,504,569,324,900,000,000,000,000,000,000,000 | hid-magicmouse.c | 2,593,342,493,104,003,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3181 | Multiple stack-based buffer overflows in the magicmouse_raw_event function in drivers/hid/hid-magicmouse.c in the Magic Mouse HID driver in the Linux kernel through 3.16.3 allow physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that provid... | https://nvd.nist.gov/vuln/detail/CVE-2014-3181 |
38,679 | linux | c54def7bd64d7c0b6993336abcffb8444795bf38 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c54def7bd64d7c0b6993336abcffb8444795bf38 | HID: magicmouse: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that
magicmouse_emit_touch() gets only valid values of raw_id.
Cc: stable@vger.kernel.org
Reported-by: Steven Vittitoe <scvitti... | 0 | static int magicmouse_firm_touch(struct magicmouse_sc *msc)
{
int touch = -1;
int ii;
/* If there is only one "firm" touch, set touch to its
* tracking ID.
*/
for (ii = 0; ii < msc->ntouches; ii++) {
int idx = msc->tracking_ids[ii];
if (msc->touches[idx].size < 8) {
/* Ignore this touch. */
} else if ... | 205,195,496,399,055,540,000,000,000,000,000,000,000 | hid-magicmouse.c | 2,593,342,493,104,003,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3181 | Multiple stack-based buffer overflows in the magicmouse_raw_event function in drivers/hid/hid-magicmouse.c in the Magic Mouse HID driver in the Linux kernel through 3.16.3 allow physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that provid... | https://nvd.nist.gov/vuln/detail/CVE-2014-3181 |
38,680 | linux | c54def7bd64d7c0b6993336abcffb8444795bf38 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c54def7bd64d7c0b6993336abcffb8444795bf38 | HID: magicmouse: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that
magicmouse_emit_touch() gets only valid values of raw_id.
Cc: stable@vger.kernel.org
Reported-by: Steven Vittitoe <scvitti... | 0 | static int magicmouse_probe(struct hid_device *hdev,
const struct hid_device_id *id)
{
__u8 feature[] = { 0xd7, 0x01 };
struct magicmouse_sc *msc;
struct hid_report *report;
int ret;
msc = devm_kzalloc(&hdev->dev, sizeof(*msc), GFP_KERNEL);
if (msc == NULL) {
hid_err(hdev, "can't alloc magicmouse descriptor\n... | 93,575,522,530,074,180,000,000,000,000,000,000,000 | hid-magicmouse.c | 2,593,342,493,104,003,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3181 | Multiple stack-based buffer overflows in the magicmouse_raw_event function in drivers/hid/hid-magicmouse.c in the Magic Mouse HID driver in the Linux kernel through 3.16.3 allow physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that provid... | https://nvd.nist.gov/vuln/detail/CVE-2014-3181 |
38,681 | linux | c54def7bd64d7c0b6993336abcffb8444795bf38 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c54def7bd64d7c0b6993336abcffb8444795bf38 | HID: magicmouse: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that
magicmouse_emit_touch() gets only valid values of raw_id.
Cc: stable@vger.kernel.org
Reported-by: Steven Vittitoe <scvitti... | 0 | static int magicmouse_setup_input(struct input_dev *input, struct hid_device *hdev)
{
int error;
__set_bit(EV_KEY, input->evbit);
if (input->id.product == USB_DEVICE_ID_APPLE_MAGICMOUSE) {
__set_bit(BTN_LEFT, input->keybit);
__set_bit(BTN_RIGHT, input->keybit);
if (emulate_3button)
__set_bit(BTN_MIDDLE, i... | 179,794,059,871,313,700,000,000,000,000,000,000,000 | hid-magicmouse.c | 2,593,342,493,104,003,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3181 | Multiple stack-based buffer overflows in the magicmouse_raw_event function in drivers/hid/hid-magicmouse.c in the Magic Mouse HID driver in the Linux kernel through 3.16.3 allow physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that provid... | https://nvd.nist.gov/vuln/detail/CVE-2014-3181 |
38,682 | linux | c54def7bd64d7c0b6993336abcffb8444795bf38 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c54def7bd64d7c0b6993336abcffb8444795bf38 | HID: magicmouse: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that
magicmouse_emit_touch() gets only valid values of raw_id.
Cc: stable@vger.kernel.org
Reported-by: Steven Vittitoe <scvitti... | 0 | static int param_set_scroll_speed(const char *val, struct kernel_param *kp) {
unsigned long speed;
if (!val || kstrtoul(val, 0, &speed) || speed > 63)
return -EINVAL;
scroll_speed = speed;
return 0;
}
| 312,853,413,658,024,800,000,000,000,000,000,000,000 | hid-magicmouse.c | 2,593,342,493,104,003,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3181 | Multiple stack-based buffer overflows in the magicmouse_raw_event function in drivers/hid/hid-magicmouse.c in the Magic Mouse HID driver in the Linux kernel through 3.16.3 allow physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that provid... | https://nvd.nist.gov/vuln/detail/CVE-2014-3181 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.