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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
159,784 | linux | cb3232138e37129e88240a98a1d2aba2187ff57c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cb3232138e37129e88240a98a1d2aba2187ff57c | USB: serial: visor: fix crash on detecting device without write_urbs
The visor driver crashes in clie_5_attach() when a specially crafted USB
device without bulk-out endpoint is detected. This fix adds a check that
the device has proper configuration expected by the driver.
Reported-by: Ralf Spenneberg <ralf@spennebe... | 0 | static int clie_5_attach(struct usb_serial *serial)
{
struct usb_serial_port *port;
unsigned int pipe;
int j;
/* TH55 registers 2 ports.
Communication in from the UX50/TH55 uses bulk_in_endpointAddress
from port 0. Communication out to the UX50/TH55 uses
bulk_out_endpointAddress from port 1
Lets d... | 83,038,867,242,978,260,000,000,000,000,000,000,000 | visor.c | 303,527,774,898,140,330,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2015-7566 | The clie_5_attach function in drivers/usb/serial/visor.c in the Linux kernel through 4.4.1 allows physically proximate attackers to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact by inserting a USB device that lacks a bulk-out endpoint. | https://nvd.nist.gov/vuln/detail/CVE-2015-7566 |
2,298 | linux | 8e20cf2bce122ce9262d6034ee5d5b76fbb92f96 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8e20cf2bce122ce9262d6034ee5d5b76fbb92f96 | Input: aiptek - fix crash on detecting device without endpoints
The aiptek driver crashes in aiptek_probe() when a specially crafted USB
device without endpoints is detected. This fix adds a check that the device
has proper configuration expected by the driver. Also an error return value
is changed to more matching on... | 1 | aiptek_probe(struct usb_interface *intf, const struct usb_device_id *id)
{
struct usb_device *usbdev = interface_to_usbdev(intf);
struct usb_endpoint_descriptor *endpoint;
struct aiptek *aiptek;
struct input_dev *inputdev;
int i;
int speeds[] = { 0,
AIPTEK_PROGRAMMABLE_DELAY_50,
AIPTEK_PROGRAMMABLE_DELAY_400,... | 116,279,422,032,136,150,000,000,000,000,000,000,000 | None | null | [
"CWE-401"
] | CVE-2015-7515 | The aiptek_probe function in drivers/input/tablet/aiptek.c in the Linux kernel before 4.4 allows physically proximate attackers to cause a denial of service (NULL pointer dereference and system crash) via a crafted USB device that lacks endpoints. | https://nvd.nist.gov/vuln/detail/CVE-2015-7515 |
159,785 | linux | 8e20cf2bce122ce9262d6034ee5d5b76fbb92f96 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8e20cf2bce122ce9262d6034ee5d5b76fbb92f96 | Input: aiptek - fix crash on detecting device without endpoints
The aiptek driver crashes in aiptek_probe() when a specially crafted USB
device without endpoints is detected. This fix adds a check that the device
has proper configuration expected by the driver. Also an error return value
is changed to more matching on... | 0 | aiptek_probe(struct usb_interface *intf, const struct usb_device_id *id)
{
struct usb_device *usbdev = interface_to_usbdev(intf);
struct usb_endpoint_descriptor *endpoint;
struct aiptek *aiptek;
struct input_dev *inputdev;
int i;
int speeds[] = { 0,
AIPTEK_PROGRAMMABLE_DELAY_50,
AIPTEK_PROGRAMMABLE_DELAY_400,... | 44,403,462,937,737,210,000,000,000,000,000,000,000 | None | null | [
"CWE-401"
] | CVE-2015-7515 | The aiptek_probe function in drivers/input/tablet/aiptek.c in the Linux kernel before 4.4 allows physically proximate attackers to cause a denial of service (NULL pointer dereference and system crash) via a crafted USB device that lacks endpoints. | https://nvd.nist.gov/vuln/detail/CVE-2015-7515 |
2,299 | linux | 0185604c2d82c560dab2f2933a18f797e74ab5a8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0185604c2d82c560dab2f2933a18f797e74ab5a8 | KVM: x86: Reload pit counters for all channels when restoring state
Currently if userspace restores the pit counters with a count of 0
on channels 1 or 2 and the guest attempts to read the count on those
channels, then KVM will perform a mod of 0 and crash. This will ensure
that 0 values are converted to 65536 as per... | 1 | static int kvm_vm_ioctl_set_pit(struct kvm *kvm, struct kvm_pit_state *ps)
{
mutex_lock(&kvm->arch.vpit->pit_state.lock);
memcpy(&kvm->arch.vpit->pit_state, ps, sizeof(struct kvm_pit_state));
kvm_pit_load_count(kvm, 0, ps->channels[0].count, 0);
mutex_unlock(&kvm->arch.vpit->pit_state.lock);
return 0;
}
| 208,694,431,467,498,260,000,000,000,000,000,000,000 | x86.c | 35,499,916,013,815,720,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2015-7513 | arch/x86/kvm/x86.c in the Linux kernel before 4.4 does not reset the PIT counter values during state restoration, which allows guest OS users to cause a denial of service (divide-by-zero error and host OS crash) via a zero value, related to the kvm_vm_ioctl_set_pit and kvm_vm_ioctl_set_pit2 functions. | https://nvd.nist.gov/vuln/detail/CVE-2015-7513 |
159,786 | linux | 0185604c2d82c560dab2f2933a18f797e74ab5a8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0185604c2d82c560dab2f2933a18f797e74ab5a8 | KVM: x86: Reload pit counters for all channels when restoring state
Currently if userspace restores the pit counters with a count of 0
on channels 1 or 2 and the guest attempts to read the count on those
channels, then KVM will perform a mod of 0 and crash. This will ensure
that 0 values are converted to 65536 as per... | 0 | static int kvm_vm_ioctl_set_pit(struct kvm *kvm, struct kvm_pit_state *ps)
{
int i;
mutex_lock(&kvm->arch.vpit->pit_state.lock);
memcpy(&kvm->arch.vpit->pit_state, ps, sizeof(struct kvm_pit_state));
for (i = 0; i < 3; i++)
kvm_pit_load_count(kvm, i, ps->channels[i].count, 0);
mutex_unlock(&kvm->arch.vpit->p... | 151,058,841,976,899,500,000,000,000,000,000,000,000 | x86.c | 231,743,638,953,840,650,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2015-7513 | arch/x86/kvm/x86.c in the Linux kernel before 4.4 does not reset the PIT counter values during state restoration, which allows guest OS users to cause a denial of service (divide-by-zero error and host OS crash) via a zero value, related to the kvm_vm_ioctl_set_pit and kvm_vm_ioctl_set_pit2 functions. | https://nvd.nist.gov/vuln/detail/CVE-2015-7513 |
2,300 | linux | 0185604c2d82c560dab2f2933a18f797e74ab5a8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0185604c2d82c560dab2f2933a18f797e74ab5a8 | KVM: x86: Reload pit counters for all channels when restoring state
Currently if userspace restores the pit counters with a count of 0
on channels 1 or 2 and the guest attempts to read the count on those
channels, then KVM will perform a mod of 0 and crash. This will ensure
that 0 values are converted to 65536 as per... | 1 | static int kvm_vm_ioctl_set_pit2(struct kvm *kvm, struct kvm_pit_state2 *ps)
{
int start = 0;
u32 prev_legacy, cur_legacy;
mutex_lock(&kvm->arch.vpit->pit_state.lock);
prev_legacy = kvm->arch.vpit->pit_state.flags & KVM_PIT_FLAGS_HPET_LEGACY;
cur_legacy = ps->flags & KVM_PIT_FLAGS_HPET_LEGACY;
if (!prev_leg... | 246,557,586,103,248,000,000,000,000,000,000,000,000 | x86.c | 35,499,916,013,815,720,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2015-7513 | arch/x86/kvm/x86.c in the Linux kernel before 4.4 does not reset the PIT counter values during state restoration, which allows guest OS users to cause a denial of service (divide-by-zero error and host OS crash) via a zero value, related to the kvm_vm_ioctl_set_pit and kvm_vm_ioctl_set_pit2 functions. | https://nvd.nist.gov/vuln/detail/CVE-2015-7513 |
159,787 | linux | 0185604c2d82c560dab2f2933a18f797e74ab5a8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0185604c2d82c560dab2f2933a18f797e74ab5a8 | KVM: x86: Reload pit counters for all channels when restoring state
Currently if userspace restores the pit counters with a count of 0
on channels 1 or 2 and the guest attempts to read the count on those
channels, then KVM will perform a mod of 0 and crash. This will ensure
that 0 values are converted to 65536 as per... | 0 | static int kvm_vm_ioctl_set_pit2(struct kvm *kvm, struct kvm_pit_state2 *ps)
{
int start = 0;
int i;
u32 prev_legacy, cur_legacy;
mutex_lock(&kvm->arch.vpit->pit_state.lock);
prev_legacy = kvm->arch.vpit->pit_state.flags & KVM_PIT_FLAGS_HPET_LEGACY;
cur_legacy = ps->flags & KVM_PIT_FLAGS_HPET_LEGACY;
if (!... | 14,499,416,964,145,364,000,000,000,000,000,000,000 | x86.c | 231,743,638,953,840,650,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2015-7513 | arch/x86/kvm/x86.c in the Linux kernel before 4.4 does not reset the PIT counter values during state restoration, which allows guest OS users to cause a denial of service (divide-by-zero error and host OS crash) via a zero value, related to the kvm_vm_ioctl_set_pit and kvm_vm_ioctl_set_pit2 functions. | https://nvd.nist.gov/vuln/detail/CVE-2015-7513 |
2,301 | linux | cd4a40174b71acd021877341684d8bb1dc8ea4ae | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cd4a40174b71acd021877341684d8bb1dc8ea4ae | mnt: Fail collect_mounts when applied to unmounted mounts
The only users of collect_mounts are in audit_tree.c
In audit_trim_trees and audit_add_tree_rule the path passed into
collect_mounts is generated from kern_path passed an audit_tree
pathname which is guaranteed to be an absolute path. In those cases
collect_... | 1 | struct vfsmount *collect_mounts(struct path *path)
{
struct mount *tree;
namespace_lock();
tree = copy_tree(real_mount(path->mnt), path->dentry,
CL_COPY_ALL | CL_PRIVATE);
namespace_unlock();
if (IS_ERR(tree))
return ERR_CAST(tree);
return &tree->mnt;
}
| 19,334,538,589,789,937,000,000,000,000,000,000,000 | namespace.c | 291,925,216,484,681,430,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2015-4177 | The collect_mounts function in fs/namespace.c in the Linux kernel before 4.0.5 does not properly consider that it may execute after a path has been unmounted, which allows local users to cause a denial of service (system crash) by leveraging user-namespace root access for an MNT_DETACH umount2 system call. | https://nvd.nist.gov/vuln/detail/CVE-2015-4177 |
159,788 | linux | cd4a40174b71acd021877341684d8bb1dc8ea4ae | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cd4a40174b71acd021877341684d8bb1dc8ea4ae | mnt: Fail collect_mounts when applied to unmounted mounts
The only users of collect_mounts are in audit_tree.c
In audit_trim_trees and audit_add_tree_rule the path passed into
collect_mounts is generated from kern_path passed an audit_tree
pathname which is guaranteed to be an absolute path. In those cases
collect_... | 0 | struct vfsmount *collect_mounts(struct path *path)
{
struct mount *tree;
namespace_lock();
if (!check_mnt(real_mount(path->mnt)))
tree = ERR_PTR(-EINVAL);
else
tree = copy_tree(real_mount(path->mnt), path->dentry,
CL_COPY_ALL | CL_PRIVATE);
namespace_unlock();
if (IS_ERR(tree))
return ERR_CAST(tr... | 288,013,393,649,799,300,000,000,000,000,000,000,000 | namespace.c | 11,074,591,805,538,522,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2015-4177 | The collect_mounts function in fs/namespace.c in the Linux kernel before 4.0.5 does not properly consider that it may execute after a path has been unmounted, which allows local users to cause a denial of service (system crash) by leveraging user-namespace root access for an MNT_DETACH umount2 system call. | https://nvd.nist.gov/vuln/detail/CVE-2015-4177 |
2,303 | linux | cf872776fc84128bb779ce2b83a37c884c3203ae | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cf872776fc84128bb779ce2b83a37c884c3203ae | tty: Fix hang at ldsem_down_read()
When a controlling tty is being hung up and the hang up is
waiting for a just-signalled tty reader or writer to exit, and a new tty
reader/writer tries to acquire an ldisc reference concurrently with the
ldisc reference release from the signalled reader/writer, the hangup
can hang. T... | 1 | static inline int ldsem_cmpxchg(long *old, long new, struct ld_semaphore *sem)
{
long tmp = *old;
*old = atomic_long_cmpxchg(&sem->count, *old, new);
return *old == tmp;
}
| 228,392,180,986,723,300,000,000,000,000,000,000,000 | tty_ldsem.c | 229,283,372,989,827,300,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2015-4170 | Race condition in the ldsem_cmpxchg function in drivers/tty/tty_ldsem.c in the Linux kernel before 3.13-rc4-next-20131218 allows local users to cause a denial of service (ldsem_down_read and ldsem_down_write deadlock) by establishing a new tty thread during shutdown of a previous tty thread. | https://nvd.nist.gov/vuln/detail/CVE-2015-4170 |
159,790 | linux | cf872776fc84128bb779ce2b83a37c884c3203ae | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cf872776fc84128bb779ce2b83a37c884c3203ae | tty: Fix hang at ldsem_down_read()
When a controlling tty is being hung up and the hang up is
waiting for a just-signalled tty reader or writer to exit, and a new tty
reader/writer tries to acquire an ldisc reference concurrently with the
ldisc reference release from the signalled reader/writer, the hangup
can hang. T... | 0 | static inline int ldsem_cmpxchg(long *old, long new, struct ld_semaphore *sem)
{
long tmp = atomic_long_cmpxchg(&sem->count, *old, new);
if (tmp == *old) {
*old = new;
return 1;
} else {
*old = tmp;
return 0;
}
}
| 106,232,458,264,685,430,000,000,000,000,000,000,000 | tty_ldsem.c | 277,514,752,989,494,370,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2015-4170 | Race condition in the ldsem_cmpxchg function in drivers/tty/tty_ldsem.c in the Linux kernel before 3.13-rc4-next-20131218 allows local users to cause a denial of service (ldsem_down_read and ldsem_down_write deadlock) by establishing a new tty thread during shutdown of a previous tty thread. | https://nvd.nist.gov/vuln/detail/CVE-2015-4170 |
2,309 | linux | 2c5816b4beccc8ba709144539f6fdd764f8fa49c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2c5816b4beccc8ba709144539f6fdd764f8fa49c | cuse: fix memory leak
The problem is that fuse_dev_alloc() acquires an extra reference to cc.fc,
and the original ref count is never dropped.
Reported-by: Colin Ian King <colin.king@canonical.com>
Signed-off-by: Miklos Szeredi <miklos@szeredi.hu>
Fixes: cc080e9e9be1 ("fuse: introduce per-instance fuse_dev structure")... | 1 | static int cuse_channel_release(struct inode *inode, struct file *file)
{
struct fuse_dev *fud = file->private_data;
struct cuse_conn *cc = fc_to_cc(fud->fc);
int rc;
/* remove from the conntbl, no more access from this point on */
mutex_lock(&cuse_lock);
list_del_init(&cc->list);
mutex_unlock(&cuse_lock);
/*... | 206,651,427,646,572,480,000,000,000,000,000,000,000 | None | null | [
"CWE-399"
] | CVE-2015-1339 | Memory leak in the cuse_channel_release function in fs/fuse/cuse.c in the Linux kernel before 4.4 allows local users to cause a denial of service (memory consumption) or possibly have unspecified other impact by opening /dev/cuse many times. | https://nvd.nist.gov/vuln/detail/CVE-2015-1339 |
159,796 | linux | 2c5816b4beccc8ba709144539f6fdd764f8fa49c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2c5816b4beccc8ba709144539f6fdd764f8fa49c | cuse: fix memory leak
The problem is that fuse_dev_alloc() acquires an extra reference to cc.fc,
and the original ref count is never dropped.
Reported-by: Colin Ian King <colin.king@canonical.com>
Signed-off-by: Miklos Szeredi <miklos@szeredi.hu>
Fixes: cc080e9e9be1 ("fuse: introduce per-instance fuse_dev structure")... | 0 | static int cuse_channel_release(struct inode *inode, struct file *file)
{
struct fuse_dev *fud = file->private_data;
struct cuse_conn *cc = fc_to_cc(fud->fc);
int rc;
/* remove from the conntbl, no more access from this point on */
mutex_lock(&cuse_lock);
list_del_init(&cc->list);
mutex_unlock(&cuse_lock);
/*... | 150,411,779,012,918,280,000,000,000,000,000,000,000 | None | null | [
"CWE-399"
] | CVE-2015-1339 | Memory leak in the cuse_channel_release function in fs/fuse/cuse.c in the Linux kernel before 4.4 allows local users to cause a denial of service (memory consumption) or possibly have unspecified other impact by opening /dev/cuse many times. | https://nvd.nist.gov/vuln/detail/CVE-2015-1339 |
2,310 | linux | 6217e5ede23285ddfee10d2e4ba0cc2d4c046205 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6217e5ede23285ddfee10d2e4ba0cc2d4c046205 | ALSA: compress: fix an integer overflow check
I previously added an integer overflow check here but looking at it now,
it's still buggy.
The bug happens in snd_compr_allocate_buffer(). We multiply
".fragments" and ".fragment_size" and that doesn't overflow but then we
save it in an unsigned int so it truncates the h... | 1 | static int snd_compress_check_input(struct snd_compr_params *params)
{
/* first let's check the buffer parameter's */
if (params->buffer.fragment_size == 0 ||
params->buffer.fragments > SIZE_MAX / params->buffer.fragment_size)
return -EINVAL;
/* now codec parameters */
if (params->codec.id == 0 || param... | 77,147,876,717,907,740,000,000,000,000,000,000,000 | compress_offload.c | 155,400,925,010,501,580,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2014-9904 | The snd_compress_check_input function in sound/core/compress_offload.c in the ALSA subsystem in the Linux kernel before 3.17 does not properly check for an integer overflow, which allows local users to cause a denial of service (insufficient memory allocation) or possibly have unspecified other impact via a crafted SND... | https://nvd.nist.gov/vuln/detail/CVE-2014-9904 |
159,797 | linux | 6217e5ede23285ddfee10d2e4ba0cc2d4c046205 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6217e5ede23285ddfee10d2e4ba0cc2d4c046205 | ALSA: compress: fix an integer overflow check
I previously added an integer overflow check here but looking at it now,
it's still buggy.
The bug happens in snd_compr_allocate_buffer(). We multiply
".fragments" and ".fragment_size" and that doesn't overflow but then we
save it in an unsigned int so it truncates the h... | 0 | static int snd_compress_check_input(struct snd_compr_params *params)
{
/* first let's check the buffer parameter's */
if (params->buffer.fragment_size == 0 ||
params->buffer.fragments > INT_MAX / params->buffer.fragment_size)
return -EINVAL;
/* now codec parameters */
if (params->codec.id == 0 || para... | 239,953,446,957,668,340,000,000,000,000,000,000,000 | compress_offload.c | 6,046,478,889,246,839,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2014-9904 | The snd_compress_check_input function in sound/core/compress_offload.c in the ALSA subsystem in the Linux kernel before 3.17 does not properly check for an integer overflow, which allows local users to cause a denial of service (insufficient memory allocation) or possibly have unspecified other impact via a crafted SND... | https://nvd.nist.gov/vuln/detail/CVE-2014-9904 |
2,311 | linux | 4efbc454ba68def5ef285b26ebfcfdb605b52755 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4efbc454ba68def5ef285b26ebfcfdb605b52755 | sched: Fix information leak in sys_sched_getattr()
We're copying the on-stack structure to userspace, but forgot to give
the right number of bytes to copy. This allows the calling process to
obtain up to PAGE_SIZE bytes from the stack (and possibly adjacent
kernel memory).
This fix copies only as much as we actually ... | 1 | static int sched_read_attr(struct sched_attr __user *uattr,
struct sched_attr *attr,
unsigned int usize)
{
int ret;
if (!access_ok(VERIFY_WRITE, uattr, usize))
return -EFAULT;
/*
* If we're handed a smaller struct than we know of,
* ensure all the unknown bits are 0 - i.e. old
* user-space does... | 339,536,197,997,710,340,000,000,000,000,000,000,000 | core.c | 151,467,961,382,598,860,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-9903 | The sched_read_attr function in kernel/sched/core.c in the Linux kernel 3.14-rc before 3.14-rc4 uses an incorrect size, which allows local users to obtain sensitive information from kernel stack memory via a crafted sched_getattr system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-9903 |
159,798 | linux | 4efbc454ba68def5ef285b26ebfcfdb605b52755 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4efbc454ba68def5ef285b26ebfcfdb605b52755 | sched: Fix information leak in sys_sched_getattr()
We're copying the on-stack structure to userspace, but forgot to give
the right number of bytes to copy. This allows the calling process to
obtain up to PAGE_SIZE bytes from the stack (and possibly adjacent
kernel memory).
This fix copies only as much as we actually ... | 0 | static int sched_read_attr(struct sched_attr __user *uattr,
struct sched_attr *attr,
unsigned int usize)
{
int ret;
if (!access_ok(VERIFY_WRITE, uattr, usize))
return -EFAULT;
/*
* If we're handed a smaller struct than we know of,
* ensure all the unknown bits are 0 - i.e. old
* user-space does... | 302,288,470,479,010,640,000,000,000,000,000,000,000 | core.c | 295,515,292,188,481,970,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-9903 | The sched_read_attr function in kernel/sched/core.c in the Linux kernel 3.14-rc before 3.14-rc4 uses an incorrect size, which allows local users to obtain sensitive information from kernel stack memory via a crafted sched_getattr system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-9903 |
2,324 | Little-CMS | fefaaa43c382eee632ea3ad0cfa915335140e1db | https://github.com/mm2/Little-CMS | https://github.com/mm2/Little-CMS/commit/fefaaa43c382eee632ea3ad0cfa915335140e1db | Fix a double free on error recovering | 1 | cmsPipeline* DefaultICCintents(cmsContext ContextID,
cmsUInt32Number nProfiles,
cmsUInt32Number TheIntents[],
cmsHPROFILE hProfiles[],
cmsBool BPC[],
... | 120,973,636,847,525,110,000,000,000,000,000,000,000 | None | null | [
"CWE-94"
] | CVE-2013-7455 | Double free vulnerability in the DefaultICCintents function in cmscnvrt.c in liblcms2 in Little CMS 2.x before 2.6 allows remote attackers to execute arbitrary code via a malformed ICC profile that triggers an error in the default intent handler. | https://nvd.nist.gov/vuln/detail/CVE-2013-7455 |
159,809 | Little-CMS | fefaaa43c382eee632ea3ad0cfa915335140e1db | https://github.com/mm2/Little-CMS | https://github.com/mm2/Little-CMS/commit/fefaaa43c382eee632ea3ad0cfa915335140e1db | Fix a double free on error recovering | 0 | cmsPipeline* DefaultICCintents(cmsContext ContextID,
cmsUInt32Number nProfiles,
cmsUInt32Number TheIntents[],
cmsHPROFILE hProfiles[],
cmsBool BPC[],
... | 208,649,856,509,108,260,000,000,000,000,000,000,000 | None | null | [
"CWE-94"
] | CVE-2013-7455 | Double free vulnerability in the DefaultICCintents function in cmscnvrt.c in liblcms2 in Little CMS 2.x before 2.6 allows remote attackers to execute arbitrary code via a malformed ICC profile that triggers an error in the default intent handler. | https://nvd.nist.gov/vuln/detail/CVE-2013-7455 |
2,338 | linux | b35cc8225845112a616e3a2266d2fde5ab13d3ab | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b35cc8225845112a616e3a2266d2fde5ab13d3ab | ALSA: compress_core: integer overflow in snd_compr_allocate_buffer()
These are 32 bit values that come from the user, we need to check for
integer overflows or we could end up allocating a smaller buffer than
expected.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: Takashi Iwai <tiwai@suse.de> | 1 | static int snd_compr_allocate_buffer(struct snd_compr_stream *stream,
struct snd_compr_params *params)
{
unsigned int buffer_size;
void *buffer;
buffer_size = params->buffer.fragment_size * params->buffer.fragments;
if (stream->ops->copy) {
buffer = NULL;
/* if copy is defined the driver will be requir... | 320,223,001,183,825,300,000,000,000,000,000,000,000 | compress_offload.c | 5,078,957,457,841,432,600,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2012-6703 | Integer overflow in the snd_compr_allocate_buffer function in sound/core/compress_offload.c in the ALSA subsystem in the Linux kernel before 3.6-rc6-next-20120917 allows local users to cause a denial of service (insufficient memory allocation) or possibly have unspecified other impact via a crafted SNDRV_COMPRESS_SET_P... | https://nvd.nist.gov/vuln/detail/CVE-2012-6703 |
159,821 | linux | b35cc8225845112a616e3a2266d2fde5ab13d3ab | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b35cc8225845112a616e3a2266d2fde5ab13d3ab | ALSA: compress_core: integer overflow in snd_compr_allocate_buffer()
These are 32 bit values that come from the user, we need to check for
integer overflows or we could end up allocating a smaller buffer than
expected.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: Takashi Iwai <tiwai@suse.de> | 0 | static int snd_compr_allocate_buffer(struct snd_compr_stream *stream,
struct snd_compr_params *params)
{
unsigned int buffer_size;
void *buffer;
if (params->buffer.fragment_size == 0 ||
params->buffer.fragments > SIZE_MAX / params->buffer.fragment_size)
return -EINVAL;
buffer_size = params->buffer.fr... | 129,472,391,732,897,770,000,000,000,000,000,000,000 | compress_offload.c | 179,672,152,967,793,730,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2012-6703 | Integer overflow in the snd_compr_allocate_buffer function in sound/core/compress_offload.c in the ALSA subsystem in the Linux kernel before 3.6-rc6-next-20120917 allows local users to cause a denial of service (insufficient memory allocation) or possibly have unspecified other impact via a crafted SNDRV_COMPRESS_SET_P... | https://nvd.nist.gov/vuln/detail/CVE-2012-6703 |
2,342 | linux | 20e1db19db5d6b9e4e83021595eab0dc8f107bef | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/20e1db19db5d6b9e4e83021595eab0dc8f107bef | netlink: fix possible spoofing from non-root processes
Non-root user-space processes can send Netlink messages to other
processes that are well-known for being subscribed to Netlink
asynchronous notifications. This allows ilegitimate non-root
process to send forged messages to Netlink subscribers.
The userspace proce... | 1 | static int netlink_sendmsg(struct kiocb *kiocb, struct socket *sock,
struct msghdr *msg, size_t len)
{
struct sock_iocb *siocb = kiocb_to_siocb(kiocb);
struct sock *sk = sock->sk;
struct netlink_sock *nlk = nlk_sk(sk);
struct sockaddr_nl *addr = msg->msg_name;
u32 dst_pid;
u32 dst_group;
struct sk_buff *sk... | 169,493,009,832,141,550,000,000,000,000,000,000,000 | af_netlink.c | 222,021,278,280,246,500,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2012-6689 | The netlink_sendmsg function in net/netlink/af_netlink.c in the Linux kernel before 3.5.5 does not validate the dst_pid field, which allows local users to have an unspecified impact by spoofing Netlink messages. | https://nvd.nist.gov/vuln/detail/CVE-2012-6689 |
159,825 | linux | 20e1db19db5d6b9e4e83021595eab0dc8f107bef | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/20e1db19db5d6b9e4e83021595eab0dc8f107bef | netlink: fix possible spoofing from non-root processes
Non-root user-space processes can send Netlink messages to other
processes that are well-known for being subscribed to Netlink
asynchronous notifications. This allows ilegitimate non-root
process to send forged messages to Netlink subscribers.
The userspace proce... | 0 | static int netlink_sendmsg(struct kiocb *kiocb, struct socket *sock,
struct msghdr *msg, size_t len)
{
struct sock_iocb *siocb = kiocb_to_siocb(kiocb);
struct sock *sk = sock->sk;
struct netlink_sock *nlk = nlk_sk(sk);
struct sockaddr_nl *addr = msg->msg_name;
u32 dst_pid;
u32 dst_group;
struct sk_buff *sk... | 135,193,968,734,567,030,000,000,000,000,000,000,000 | af_netlink.c | 5,376,810,352,634,596,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2012-6689 | The netlink_sendmsg function in net/netlink/af_netlink.c in the Linux kernel before 3.5.5 does not validate the dst_pid field, which allows local users to have an unspecified impact by spoofing Netlink messages. | https://nvd.nist.gov/vuln/detail/CVE-2012-6689 |
2,343 | linux | c290f8358acaeffd8e0c551ddcc24d1206143376 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c290f8358acaeffd8e0c551ddcc24d1206143376 | TTY: drop driver reference in tty_open fail path
When tty_driver_lookup_tty fails in tty_open, we forget to drop a
reference to the tty driver. This was added by commit 4a2b5fddd5 (Move
tty lookup/reopen to caller).
Fix that by adding tty_driver_kref_put to the fail path.
I will refactor the code later. This is for ... | 1 | static int tty_open(struct inode *inode, struct file *filp)
{
struct tty_struct *tty = NULL;
int noctty, retval;
struct tty_driver *driver;
int index;
dev_t device = inode->i_rdev;
unsigned saved_flags = filp->f_flags;
nonseekable_open(inode, filp);
retry_open:
noctty = filp->f_flags & O_NOCTTY;
index = -1;... | 2,589,888,721,444,243,200,000,000,000,000,000,000 | tty_io.c | 285,070,847,913,278,200,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-5321 | The tty_open function in drivers/tty/tty_io.c in the Linux kernel before 3.1.1 mishandles a driver-lookup failure, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via crafted access to a device file under the /dev/pts directory. | https://nvd.nist.gov/vuln/detail/CVE-2011-5321 |
159,826 | linux | c290f8358acaeffd8e0c551ddcc24d1206143376 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c290f8358acaeffd8e0c551ddcc24d1206143376 | TTY: drop driver reference in tty_open fail path
When tty_driver_lookup_tty fails in tty_open, we forget to drop a
reference to the tty driver. This was added by commit 4a2b5fddd5 (Move
tty lookup/reopen to caller).
Fix that by adding tty_driver_kref_put to the fail path.
I will refactor the code later. This is for ... | 0 | static int tty_open(struct inode *inode, struct file *filp)
{
struct tty_struct *tty = NULL;
int noctty, retval;
struct tty_driver *driver;
int index;
dev_t device = inode->i_rdev;
unsigned saved_flags = filp->f_flags;
nonseekable_open(inode, filp);
retry_open:
noctty = filp->f_flags & O_NOCTTY;
index = -1;... | 136,737,386,115,227,410,000,000,000,000,000,000,000 | tty_io.c | 171,415,660,599,699,260,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-5321 | The tty_open function in drivers/tty/tty_io.c in the Linux kernel before 3.1.1 mishandles a driver-lookup failure, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via crafted access to a device file under the /dev/pts directory. | https://nvd.nist.gov/vuln/detail/CVE-2011-5321 |
2,346 | linux | ba3021b2c79b2fa9114f92790a99deb27a65b728 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ba3021b2c79b2fa9114f92790a99deb27a65b728 | ALSA: timer: Fix missing queue indices reset at SNDRV_TIMER_IOCTL_SELECT
snd_timer_user_tselect() reallocates the queue buffer dynamically, but
it forgot to reset its indices. Since the read may happen
concurrently with ioctl and snd_timer_user_tselect() allocates the
buffer via kmalloc(), this may lead to the leak o... | 1 | static int snd_timer_user_tselect(struct file *file,
struct snd_timer_select __user *_tselect)
{
struct snd_timer_user *tu;
struct snd_timer_select tselect;
char str[32];
int err = 0;
tu = file->private_data;
if (tu->timeri) {
snd_timer_close(tu->timeri);
tu->timeri = NULL;
}
if (copy_from_user(&tsel... | 18,027,996,916,287,280,000,000,000,000,000,000,000 | timer.c | 102,836,771,800,390,000,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2017-1000380 | sound/core/timer.c in the Linux kernel before 4.11.5 is vulnerable to a data race in the ALSA /dev/snd/timer driver resulting in local users being able to read information belonging to other users, i.e., uninitialized memory contents may be disclosed when a read and an ioctl happen at the same time. | https://nvd.nist.gov/vuln/detail/CVE-2017-1000380 |
159,829 | linux | ba3021b2c79b2fa9114f92790a99deb27a65b728 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ba3021b2c79b2fa9114f92790a99deb27a65b728 | ALSA: timer: Fix missing queue indices reset at SNDRV_TIMER_IOCTL_SELECT
snd_timer_user_tselect() reallocates the queue buffer dynamically, but
it forgot to reset its indices. Since the read may happen
concurrently with ioctl and snd_timer_user_tselect() allocates the
buffer via kmalloc(), this may lead to the leak o... | 0 | static int snd_timer_user_tselect(struct file *file,
struct snd_timer_select __user *_tselect)
{
struct snd_timer_user *tu;
struct snd_timer_select tselect;
char str[32];
int err = 0;
tu = file->private_data;
if (tu->timeri) {
snd_timer_close(tu->timeri);
tu->timeri = NULL;
}
if (copy_from_user(&tsel... | 177,277,773,550,949,130,000,000,000,000,000,000,000 | timer.c | 271,584,179,256,254,960,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2017-1000380 | sound/core/timer.c in the Linux kernel before 4.11.5 is vulnerable to a data race in the ALSA /dev/snd/timer driver resulting in local users being able to read information belonging to other users, i.e., uninitialized memory contents may be disclosed when a read and an ioctl happen at the same time. | https://nvd.nist.gov/vuln/detail/CVE-2017-1000380 |
2,347 | linux | 36ae3c0a36b7456432fedce38ae2f7bd3e01a563 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/36ae3c0a36b7456432fedce38ae2f7bd3e01a563 | KVM: Don't accept obviously wrong gsi values via KVM_IRQFD
We cannot add routes for gsi values >= KVM_MAX_IRQ_ROUTES -- see
kvm_set_irq_routing(). Hence, there is no sense in accepting them
via KVM_IRQFD. Prevent them from entering the system in the first
place.
Signed-off-by: Jan H. Schönherr <jschoenh@amazon.de>
Si... | 1 | kvm_irqfd(struct kvm *kvm, struct kvm_irqfd *args)
{
if (args->flags & ~(KVM_IRQFD_FLAG_DEASSIGN | KVM_IRQFD_FLAG_RESAMPLE))
return -EINVAL;
if (args->flags & KVM_IRQFD_FLAG_DEASSIGN)
return kvm_irqfd_deassign(kvm, args);
return kvm_irqfd_assign(kvm, args);
}
| 83,207,294,150,061,300,000,000,000,000,000,000,000 | eventfd.c | 202,797,016,146,185,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2017-1000252 | The KVM subsystem in the Linux kernel through 4.13.3 allows guest OS users to cause a denial of service (assertion failure, and hypervisor hang or crash) via an out-of bounds guest_irq value, related to arch/x86/kvm/vmx.c and virt/kvm/eventfd.c. | https://nvd.nist.gov/vuln/detail/CVE-2017-1000252 |
159,830 | linux | 36ae3c0a36b7456432fedce38ae2f7bd3e01a563 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/36ae3c0a36b7456432fedce38ae2f7bd3e01a563 | KVM: Don't accept obviously wrong gsi values via KVM_IRQFD
We cannot add routes for gsi values >= KVM_MAX_IRQ_ROUTES -- see
kvm_set_irq_routing(). Hence, there is no sense in accepting them
via KVM_IRQFD. Prevent them from entering the system in the first
place.
Signed-off-by: Jan H. Schönherr <jschoenh@amazon.de>
Si... | 0 | kvm_irqfd(struct kvm *kvm, struct kvm_irqfd *args)
{
if (args->flags & ~(KVM_IRQFD_FLAG_DEASSIGN | KVM_IRQFD_FLAG_RESAMPLE))
return -EINVAL;
if (args->gsi >= KVM_MAX_IRQ_ROUTES)
return -EINVAL;
if (args->flags & KVM_IRQFD_FLAG_DEASSIGN)
return kvm_irqfd_deassign(kvm, args);
return kvm_irqfd_assign(kvm... | 14,592,003,181,220,355,000,000,000,000,000,000,000 | eventfd.c | 29,775,361,372,366,876,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2017-1000252 | The KVM subsystem in the Linux kernel through 4.13.3 allows guest OS users to cause a denial of service (assertion failure, and hypervisor hang or crash) via an out-of bounds guest_irq value, related to arch/x86/kvm/vmx.c and virt/kvm/eventfd.c. | https://nvd.nist.gov/vuln/detail/CVE-2017-1000252 |
2,354 | file | 35c94dc6acc418f1ad7f6241a6680e5327495793 | https://github.com/file/file | https://github.com/file/file/commit/35c94dc6acc418f1ad7f6241a6680e5327495793 | Fix always true condition (Thomas Jarosch) | 1 | do_bid_note(struct magic_set *ms, unsigned char *nbuf, uint32_t type,
int swap __attribute__((__unused__)), uint32_t namesz, uint32_t descsz,
size_t noff, size_t doff, int *flags)
{
if (namesz == 4 && strcmp((char *)&nbuf[noff], "GNU") == 0 &&
type == NT_GNU_BUILD_ID && (descsz >= 4 || descsz <= 20)) {... | 125,277,570,129,377,140,000,000,000,000,000,000,000 | readelf.c | 30,360,017,589,846,504,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-1000249 | An issue in file() was introduced in commit 9611f31313a93aa036389c5f3b15eea53510d4d1 (Oct 2016) lets an attacker overwrite a fixed 20 bytes stack buffer with a specially crafted .notes section in an ELF binary. This was fixed in commit 35c94dc6acc418f1ad7f6241a6680e5327495793 (Aug 2017). | https://nvd.nist.gov/vuln/detail/CVE-2017-1000249 |
159,837 | file | 35c94dc6acc418f1ad7f6241a6680e5327495793 | https://github.com/file/file | https://github.com/file/file/commit/35c94dc6acc418f1ad7f6241a6680e5327495793 | Fix always true condition (Thomas Jarosch) | 0 | do_bid_note(struct magic_set *ms, unsigned char *nbuf, uint32_t type,
int swap __attribute__((__unused__)), uint32_t namesz, uint32_t descsz,
size_t noff, size_t doff, int *flags)
{
if (namesz == 4 && strcmp((char *)&nbuf[noff], "GNU") == 0 &&
type == NT_GNU_BUILD_ID && (descsz >= 4 && descsz <= 20)) {... | 143,682,702,177,533,960,000,000,000,000,000,000,000 | readelf.c | 179,983,539,722,355,470,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-1000249 | An issue in file() was introduced in commit 9611f31313a93aa036389c5f3b15eea53510d4d1 (Oct 2016) lets an attacker overwrite a fixed 20 bytes stack buffer with a specially crafted .notes section in an ELF binary. This was fixed in commit 35c94dc6acc418f1ad7f6241a6680e5327495793 (Aug 2017). | https://nvd.nist.gov/vuln/detail/CVE-2017-1000249 |
2,355 | lynx-snapshots | 280a61b300a1614f6037efc0902ff7ecf17146e9 | https://github.com/ThomasDickey/lynx-snapshots | https://github.com/ThomasDickey/lynx-snapshots/commit/280a61b300a1614f6037efc0902ff7ecf17146e9 | snapshot of project "lynx", label v2-8-9dev_15b | 1 | void HTML_put_string(HTStructured * me, const char *s)
{
#ifdef USE_PRETTYSRC
char *translated_string = NULL;
#endif
if (s == NULL || (LYMapsOnly && me->sp[0].tag_number != HTML_OBJECT))
return;
#ifdef USE_PRETTYSRC
if (psrc_convert_string) {
StrAllocCopy(translated_string, s);
TRANSLATE_AND_UNESCA... | 185,287,537,479,326,960,000,000,000,000,000,000,000 | HTML.c | 198,530,681,004,127,600,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-1000211 | Lynx before 2.8.9dev.16 is vulnerable to a use after free in the HTML parser resulting in memory disclosure, because HTML_put_string() can append a chunk onto itself. | https://nvd.nist.gov/vuln/detail/CVE-2017-1000211 |
159,838 | lynx-snapshots | 280a61b300a1614f6037efc0902ff7ecf17146e9 | https://github.com/ThomasDickey/lynx-snapshots | https://github.com/ThomasDickey/lynx-snapshots/commit/280a61b300a1614f6037efc0902ff7ecf17146e9 | snapshot of project "lynx", label v2-8-9dev_15b | 0 | void HTML_put_string(HTStructured * me, const char *s)
{
HTChunk *target = NULL;
#ifdef USE_PRETTYSRC
char *translated_string = NULL;
#endif
if (s == NULL || (LYMapsOnly && me->sp[0].tag_number != HTML_OBJECT))
return;
#ifdef USE_PRETTYSRC
if (psrc_convert_string) {
StrAllocCopy(translated_stri... | 313,565,020,280,596,500,000,000,000,000,000,000,000 | HTML.c | 230,048,742,678,978,130,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-1000211 | Lynx before 2.8.9dev.16 is vulnerable to a use after free in the HTML parser resulting in memory disclosure, because HTML_put_string() can append a chunk onto itself. | https://nvd.nist.gov/vuln/detail/CVE-2017-1000211 |
2,360 | tcmu-runner | bb80e9c7a798f035768260ebdadffb6eb0786178 | https://github.com/open-iscsi/tcmu-runner | https://github.com/open-iscsi/tcmu-runner/commit/bb80e9c7a798f035768260ebdadffb6eb0786178 | only allow dynamic UnregisterHandler for external handlers, thereby fixing DoS
Trying to unregister an internal handler ended up in a SEGFAULT, because
the tcmur_handler->opaque was NULL. Way to reproduce:
dbus-send --system --print-reply --dest=org.kernel.TCMUService1 /org/kernel/TCMUService1/HandlerManager1 org.ker... | 1 | on_unregister_handler(TCMUService1HandlerManager1 *interface,
GDBusMethodInvocation *invocation,
gchar *subtype,
gpointer user_data)
{
struct tcmur_handler *handler = find_handler_by_subtype(subtype);
struct dbus_info *info = handler ? handler->opaque : NULL;
if (!handler) {
g_dbus_method_... | 274,977,298,780,246,000,000,000,000,000,000,000,000 | main.c | 223,399,176,575,332,300,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-1000200 | tcmu-runner version 1.0.5 to 1.2.0 is vulnerable to a dbus triggered NULL pointer dereference in the tcmu-runner daemon's on_unregister_handler() function resulting in denial of service | https://nvd.nist.gov/vuln/detail/CVE-2017-1000200 |
159,842 | tcmu-runner | bb80e9c7a798f035768260ebdadffb6eb0786178 | https://github.com/open-iscsi/tcmu-runner | https://github.com/open-iscsi/tcmu-runner/commit/bb80e9c7a798f035768260ebdadffb6eb0786178 | only allow dynamic UnregisterHandler for external handlers, thereby fixing DoS
Trying to unregister an internal handler ended up in a SEGFAULT, because
the tcmur_handler->opaque was NULL. Way to reproduce:
dbus-send --system --print-reply --dest=org.kernel.TCMUService1 /org/kernel/TCMUService1/HandlerManager1 org.ker... | 0 | on_unregister_handler(TCMUService1HandlerManager1 *interface,
GDBusMethodInvocation *invocation,
gchar *subtype,
gpointer user_data)
{
struct tcmur_handler *handler = find_handler_by_subtype(subtype);
struct dbus_info *info = handler ? handler->opaque : NULL;
if (!handler) {
g_dbus_method_... | 83,492,717,642,476,910,000,000,000,000,000,000,000 | main.c | 201,881,436,655,674,360,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-1000200 | tcmu-runner version 1.0.5 to 1.2.0 is vulnerable to a dbus triggered NULL pointer dereference in the tcmu-runner daemon's on_unregister_handler() function resulting in denial of service | https://nvd.nist.gov/vuln/detail/CVE-2017-1000200 |
2,366 | linux | ea25f914dc164c8d56b36147ecc86bc65f83c469 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ea25f914dc164c8d56b36147ecc86bc65f83c469 | bpf: fix missing error return in check_stack_boundary()
Prevent indirect stack accesses at non-constant addresses, which would
permit reading and corrupting spilled pointers.
Fixes: f1174f77b50c ("bpf/verifier: rework value tracking")
Signed-off-by: Jann Horn <jannh@google.com>
Signed-off-by: Alexei Starovoitov <ast@... | 1 | static int check_stack_boundary(struct bpf_verifier_env *env, int regno,
int access_size, bool zero_size_allowed,
struct bpf_call_arg_meta *meta)
{
struct bpf_verifier_state *state = env->cur_state;
struct bpf_reg_state *regs = state->regs;
int off, i, slot, spi;
if (regs[regno].type != PTR_TO_STACK) {
/... | 100,968,769,887,024,980,000,000,000,000,000,000,000 | verifier.c | 226,370,249,483,327,000,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-17857 | The check_stack_boundary function in kernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging mishandling of invalid variable stack read operations. | https://nvd.nist.gov/vuln/detail/CVE-2017-17857 |
159,845 | linux | ea25f914dc164c8d56b36147ecc86bc65f83c469 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ea25f914dc164c8d56b36147ecc86bc65f83c469 | bpf: fix missing error return in check_stack_boundary()
Prevent indirect stack accesses at non-constant addresses, which would
permit reading and corrupting spilled pointers.
Fixes: f1174f77b50c ("bpf/verifier: rework value tracking")
Signed-off-by: Jann Horn <jannh@google.com>
Signed-off-by: Alexei Starovoitov <ast@... | 0 | static int check_stack_boundary(struct bpf_verifier_env *env, int regno,
int access_size, bool zero_size_allowed,
struct bpf_call_arg_meta *meta)
{
struct bpf_verifier_state *state = env->cur_state;
struct bpf_reg_state *regs = state->regs;
int off, i, slot, spi;
if (regs[regno].type != PTR_TO_STACK) {
/... | 44,908,374,998,882,750,000,000,000,000,000,000,000 | verifier.c | 152,543,817,106,161,600,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-17857 | The check_stack_boundary function in kernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging mishandling of invalid variable stack read operations. | https://nvd.nist.gov/vuln/detail/CVE-2017-17857 |
2,373 | linux | 4dca6ea1d9432052afb06baf2e3ae78188a4410b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4dca6ea1d9432052afb06baf2e3ae78188a4410b | KEYS: add missing permission check for request_key() destination
When the request_key() syscall is not passed a destination keyring, it
links the requested key (if constructed) into the "default" request-key
keyring. This should require Write permission to the keyring. However,
there is actually no permission check.... | 1 | static void construct_get_dest_keyring(struct key **_dest_keyring)
{
struct request_key_auth *rka;
const struct cred *cred = current_cred();
struct key *dest_keyring = *_dest_keyring, *authkey;
kenter("%p", dest_keyring);
/* find the appropriate keyring */
if (dest_keyring) {
/* the caller supplied on... | 275,435,868,270,037,720,000,000,000,000,000,000,000 | request_key.c | 97,996,113,605,534,320,000,000,000,000,000,000,000 | [
"CWE-862"
] | CVE-2017-17807 | The KEYS subsystem in the Linux kernel before 4.14.6 omitted an access-control check when adding a key to the current task's "default request-key keyring" via the request_key() system call, allowing a local user to use a sequence of crafted system calls to add keys to a keyring with only Search permission (not Write pe... | https://nvd.nist.gov/vuln/detail/CVE-2017-17807 |
159,848 | linux | 4dca6ea1d9432052afb06baf2e3ae78188a4410b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4dca6ea1d9432052afb06baf2e3ae78188a4410b | KEYS: add missing permission check for request_key() destination
When the request_key() syscall is not passed a destination keyring, it
links the requested key (if constructed) into the "default" request-key
keyring. This should require Write permission to the keyring. However,
there is actually no permission check.... | 0 | static void construct_get_dest_keyring(struct key **_dest_keyring)
static int construct_get_dest_keyring(struct key **_dest_keyring)
{
struct request_key_auth *rka;
const struct cred *cred = current_cred();
struct key *dest_keyring = *_dest_keyring, *authkey;
int ret;
kenter("%p", dest_keyring);
/* find ... | 209,856,464,496,681,800,000,000,000,000,000,000,000 | None | null | [
"CWE-862"
] | CVE-2017-17807 | The KEYS subsystem in the Linux kernel before 4.14.6 omitted an access-control check when adding a key to the current task's "default request-key keyring" via the request_key() system call, allowing a local user to use a sequence of crafted system calls to add keys to a keyring with only Search permission (not Write pe... | https://nvd.nist.gov/vuln/detail/CVE-2017-17807 |
2,375 | linux | af3ff8045bbf3e32f1a448542e73abb4c8ceb6f1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/af3ff8045bbf3e32f1a448542e73abb4c8ceb6f1 | crypto: hmac - require that the underlying hash algorithm is unkeyed
Because the HMAC template didn't check that its underlying hash
algorithm is unkeyed, trying to use "hmac(hmac(sha3-512-generic))"
through AF_ALG or through KEYCTL_DH_COMPUTE resulted in the inner HMAC
being used without having been keyed, resulting ... | 1 | static int hmac_create(struct crypto_template *tmpl, struct rtattr **tb)
{
struct shash_instance *inst;
struct crypto_alg *alg;
struct shash_alg *salg;
int err;
int ds;
int ss;
err = crypto_check_attr_type(tb, CRYPTO_ALG_TYPE_SHASH);
if (err)
return err;
salg = shash_attr_alg(tb[1], 0, 0);
if (IS_ERR(sa... | 288,299,611,161,677,800,000,000,000,000,000,000,000 | hmac.c | 108,333,954,641,339,710,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2017-17806 | The HMAC implementation (crypto/hmac.c) in the Linux kernel before 4.14.8 does not validate that the underlying cryptographic hash algorithm is unkeyed, allowing a local attacker able to use the AF_ALG-based hash interface (CONFIG_CRYPTO_USER_API_HASH) and the SHA-3 hash algorithm (CONFIG_CRYPTO_SHA3) to cause a kernel... | https://nvd.nist.gov/vuln/detail/CVE-2017-17806 |
159,850 | linux | af3ff8045bbf3e32f1a448542e73abb4c8ceb6f1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/af3ff8045bbf3e32f1a448542e73abb4c8ceb6f1 | crypto: hmac - require that the underlying hash algorithm is unkeyed
Because the HMAC template didn't check that its underlying hash
algorithm is unkeyed, trying to use "hmac(hmac(sha3-512-generic))"
through AF_ALG or through KEYCTL_DH_COMPUTE resulted in the inner HMAC
being used without having been keyed, resulting ... | 0 | static int hmac_create(struct crypto_template *tmpl, struct rtattr **tb)
{
struct shash_instance *inst;
struct crypto_alg *alg;
struct shash_alg *salg;
int err;
int ds;
int ss;
err = crypto_check_attr_type(tb, CRYPTO_ALG_TYPE_SHASH);
if (err)
return err;
salg = shash_attr_alg(tb[1], 0, 0);
if (IS_ERR(sa... | 13,401,941,788,777,935,000,000,000,000,000,000,000 | hmac.c | 190,204,366,444,155,600,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2017-17806 | The HMAC implementation (crypto/hmac.c) in the Linux kernel before 4.14.8 does not validate that the underlying cryptographic hash algorithm is unkeyed, allowing a local attacker able to use the AF_ALG-based hash interface (CONFIG_CRYPTO_USER_API_HASH) and the SHA-3 hash algorithm (CONFIG_CRYPTO_SHA3) to cause a kernel... | https://nvd.nist.gov/vuln/detail/CVE-2017-17806 |
2,377 | linux | ecaaab5649781c5a0effdaf298a925063020500e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ecaaab5649781c5a0effdaf298a925063020500e | crypto: salsa20 - fix blkcipher_walk API usage
When asked to encrypt or decrypt 0 bytes, both the generic and x86
implementations of Salsa20 crash in blkcipher_walk_done(), either when
doing 'kfree(walk->buffer)' or 'free_page((unsigned long)walk->page)',
because walk->buffer and walk->page have not been initialized.
... | 1 | static int encrypt(struct blkcipher_desc *desc,
struct scatterlist *dst, struct scatterlist *src,
unsigned int nbytes)
{
struct blkcipher_walk walk;
struct crypto_blkcipher *tfm = desc->tfm;
struct salsa20_ctx *ctx = crypto_blkcipher_ctx(tfm);
int err;
blkcipher_walk_init(&walk, dst, src, nbytes);
err ... | 328,829,554,120,722,250,000,000,000,000,000,000,000 | salsa20_glue.c | 200,266,005,959,158,550,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2017-17805 | The Salsa20 encryption algorithm in the Linux kernel before 4.14.8 does not correctly handle zero-length inputs, allowing a local attacker able to use the AF_ALG-based skcipher interface (CONFIG_CRYPTO_USER_API_SKCIPHER) to cause a denial of service (uninitialized-memory free and kernel crash) or have unspecified other... | https://nvd.nist.gov/vuln/detail/CVE-2017-17805 |
159,852 | linux | ecaaab5649781c5a0effdaf298a925063020500e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ecaaab5649781c5a0effdaf298a925063020500e | crypto: salsa20 - fix blkcipher_walk API usage
When asked to encrypt or decrypt 0 bytes, both the generic and x86
implementations of Salsa20 crash in blkcipher_walk_done(), either when
doing 'kfree(walk->buffer)' or 'free_page((unsigned long)walk->page)',
because walk->buffer and walk->page have not been initialized.
... | 0 | static int encrypt(struct blkcipher_desc *desc,
struct scatterlist *dst, struct scatterlist *src,
unsigned int nbytes)
{
struct blkcipher_walk walk;
struct crypto_blkcipher *tfm = desc->tfm;
struct salsa20_ctx *ctx = crypto_blkcipher_ctx(tfm);
int err;
blkcipher_walk_init(&walk, dst, src, nbytes);
err ... | 167,265,214,688,812,980,000,000,000,000,000,000,000 | salsa20_glue.c | 120,660,808,501,433,930,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2017-17805 | The Salsa20 encryption algorithm in the Linux kernel before 4.14.8 does not correctly handle zero-length inputs, allowing a local attacker able to use the AF_ALG-based skcipher interface (CONFIG_CRYPTO_USER_API_SKCIPHER) to cause a denial of service (uninitialized-memory free and kernel crash) or have unspecified other... | https://nvd.nist.gov/vuln/detail/CVE-2017-17805 |
2,378 | linux | ecaaab5649781c5a0effdaf298a925063020500e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ecaaab5649781c5a0effdaf298a925063020500e | crypto: salsa20 - fix blkcipher_walk API usage
When asked to encrypt or decrypt 0 bytes, both the generic and x86
implementations of Salsa20 crash in blkcipher_walk_done(), either when
doing 'kfree(walk->buffer)' or 'free_page((unsigned long)walk->page)',
because walk->buffer and walk->page have not been initialized.
... | 1 | static int encrypt(struct blkcipher_desc *desc,
struct scatterlist *dst, struct scatterlist *src,
unsigned int nbytes)
{
struct blkcipher_walk walk;
struct crypto_blkcipher *tfm = desc->tfm;
struct salsa20_ctx *ctx = crypto_blkcipher_ctx(tfm);
int err;
blkcipher_walk_init(&walk, dst, src, nbytes);
err ... | 38,637,576,161,082,234,000,000,000,000,000,000,000 | salsa20_generic.c | 88,388,879,794,122,190,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2017-17805 | The Salsa20 encryption algorithm in the Linux kernel before 4.14.8 does not correctly handle zero-length inputs, allowing a local attacker able to use the AF_ALG-based skcipher interface (CONFIG_CRYPTO_USER_API_SKCIPHER) to cause a denial of service (uninitialized-memory free and kernel crash) or have unspecified other... | https://nvd.nist.gov/vuln/detail/CVE-2017-17805 |
159,853 | linux | ecaaab5649781c5a0effdaf298a925063020500e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ecaaab5649781c5a0effdaf298a925063020500e | crypto: salsa20 - fix blkcipher_walk API usage
When asked to encrypt or decrypt 0 bytes, both the generic and x86
implementations of Salsa20 crash in blkcipher_walk_done(), either when
doing 'kfree(walk->buffer)' or 'free_page((unsigned long)walk->page)',
because walk->buffer and walk->page have not been initialized.
... | 0 | static int encrypt(struct blkcipher_desc *desc,
struct scatterlist *dst, struct scatterlist *src,
unsigned int nbytes)
{
struct blkcipher_walk walk;
struct crypto_blkcipher *tfm = desc->tfm;
struct salsa20_ctx *ctx = crypto_blkcipher_ctx(tfm);
int err;
blkcipher_walk_init(&walk, dst, src, nbytes);
err ... | 154,366,840,978,789,020,000,000,000,000,000,000,000 | salsa20_generic.c | 146,954,168,291,136,900,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2017-17805 | The Salsa20 encryption algorithm in the Linux kernel before 4.14.8 does not correctly handle zero-length inputs, allowing a local attacker able to use the AF_ALG-based skcipher interface (CONFIG_CRYPTO_USER_API_SKCIPHER) to cause a denial of service (uninitialized-memory free and kernel crash) or have unspecified other... | https://nvd.nist.gov/vuln/detail/CVE-2017-17805 |
2,379 | linux | 8f659a03a0ba9289b9aeb9b4470e6fb263d6f483 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8f659a03a0ba9289b9aeb9b4470e6fb263d6f483 | net: ipv4: fix for a race condition in raw_sendmsg
inet->hdrincl is racy, and could lead to uninitialized stack pointer
usage, so its value should be read only once.
Fixes: c008ba5bdc9f ("ipv4: Avoid reading user iov twice after raw_probe_proto_opt")
Signed-off-by: Mohamed Ghannam <simo.ghannam@gmail.com>
Reviewed-by... | 1 | static int raw_sendmsg(struct sock *sk, struct msghdr *msg, size_t len)
{
struct inet_sock *inet = inet_sk(sk);
struct net *net = sock_net(sk);
struct ipcm_cookie ipc;
struct rtable *rt = NULL;
struct flowi4 fl4;
int free = 0;
__be32 daddr;
__be32 saddr;
u8 tos;
int err;
struct ip_options_data opt_copy;
... | 148,099,251,020,650,170,000,000,000,000,000,000,000 | raw.c | 754,726,640,040,924,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2017-17712 | The raw_sendmsg() function in net/ipv4/raw.c in the Linux kernel through 4.14.6 has a race condition in inet->hdrincl that leads to uninitialized stack pointer usage; this allows a local user to execute code and gain privileges. | https://nvd.nist.gov/vuln/detail/CVE-2017-17712 |
159,854 | linux | 8f659a03a0ba9289b9aeb9b4470e6fb263d6f483 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8f659a03a0ba9289b9aeb9b4470e6fb263d6f483 | net: ipv4: fix for a race condition in raw_sendmsg
inet->hdrincl is racy, and could lead to uninitialized stack pointer
usage, so its value should be read only once.
Fixes: c008ba5bdc9f ("ipv4: Avoid reading user iov twice after raw_probe_proto_opt")
Signed-off-by: Mohamed Ghannam <simo.ghannam@gmail.com>
Reviewed-by... | 0 | static int raw_sendmsg(struct sock *sk, struct msghdr *msg, size_t len)
{
struct inet_sock *inet = inet_sk(sk);
struct net *net = sock_net(sk);
struct ipcm_cookie ipc;
struct rtable *rt = NULL;
struct flowi4 fl4;
int free = 0;
__be32 daddr;
__be32 saddr;
u8 tos;
int err;
struct ip_options_data opt_copy;
... | 127,590,365,554,809,240,000,000,000,000,000,000,000 | raw.c | 215,390,315,911,473,220,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2017-17712 | The raw_sendmsg() function in net/ipv4/raw.c in the Linux kernel through 4.14.6 has a race condition in inet->hdrincl that leads to uninitialized stack pointer usage; this allows a local user to execute code and gain privileges. | https://nvd.nist.gov/vuln/detail/CVE-2017-17712 |
2,380 | heimdal | 1a6a6e462dc2ac6111f9e02c6852ddec4849b887 | https://github.com/heimdal/heimdal | https://github.com/heimdal/heimdal/commit/1a6a6e462dc2ac6111f9e02c6852ddec4849b887 | Security: Avoid NULL structure pointer member dereference
This can happen in the error path when processing malformed AS
requests with a NULL client name. Bug originally introduced on
Fri Feb 13 09:26:01 2015 +0100 in commit:
a873e21d7c06f22943a90a41dc733ae76799390d
kdc: base _kdc_fast_mk_error() on krb5_mk... | 1 | _kdc_as_rep(kdc_request_t r,
krb5_data *reply,
const char *from,
struct sockaddr *from_addr,
int datagram_reply)
{
krb5_context context = r->context;
krb5_kdc_configuration *config = r->config;
KDC_REQ *req = &r->req;
KDC_REQ_BODY *b = NULL;
AS_REP rep;
KDCOptions f;
krb5... | 56,768,369,760,868,760,000,000,000,000,000,000,000 | kerberos5.c | 34,202,603,459,953,700,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-17439 | In Heimdal through 7.4, remote unauthenticated attackers are able to crash the KDC by sending a crafted UDP packet containing empty data fields for client name or realm. The parser would unconditionally dereference NULL pointers in that case, leading to a segmentation fault. This is related to the _kdc_as_rep function ... | https://nvd.nist.gov/vuln/detail/CVE-2017-17439 |
159,855 | heimdal | 1a6a6e462dc2ac6111f9e02c6852ddec4849b887 | https://github.com/heimdal/heimdal | https://github.com/heimdal/heimdal/commit/1a6a6e462dc2ac6111f9e02c6852ddec4849b887 | Security: Avoid NULL structure pointer member dereference
This can happen in the error path when processing malformed AS
requests with a NULL client name. Bug originally introduced on
Fri Feb 13 09:26:01 2015 +0100 in commit:
a873e21d7c06f22943a90a41dc733ae76799390d
kdc: base _kdc_fast_mk_error() on krb5_mk... | 0 | _kdc_as_rep(kdc_request_t r,
krb5_data *reply,
const char *from,
struct sockaddr *from_addr,
int datagram_reply)
{
krb5_context context = r->context;
krb5_kdc_configuration *config = r->config;
KDC_REQ *req = &r->req;
KDC_REQ_BODY *b = NULL;
AS_REP rep;
KDCOptions f;
krb5... | 297,562,828,868,585,020,000,000,000,000,000,000,000 | kerberos5.c | 84,947,840,765,583,905,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-17439 | In Heimdal through 7.4, remote unauthenticated attackers are able to crash the KDC by sending a crafted UDP packet containing empty data fields for client name or realm. The parser would unconditionally dereference NULL pointers in that case, leading to a segmentation fault. This is related to the _kdc_as_rep function ... | https://nvd.nist.gov/vuln/detail/CVE-2017-17439 |
2,381 | FFmpeg | 58cf31cee7a456057f337b3102a03206d833d5e8 | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/58cf31cee7a456057f337b3102a03206d833d5e8 | avcodec/x86/mpegvideodsp: Fix signedness bug in need_emu
Fixes: out of array read
Fixes: 3516/attachment-311488.dat
Found-by: Insu Yun, Georgia Tech.
Tested-by: wuninsu@gmail.com
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> | 1 | static void gmc_mmx(uint8_t *dst, uint8_t *src,
int stride, int h, int ox, int oy,
int dxx, int dxy, int dyx, int dyy,
int shift, int r, int width, int height)
{
const int w = 8;
const int ix = ox >> (16 + shift);
const int iy = oy >> (16 ... | 53,843,406,165,273,080,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-17081 | The gmc_mmx function in libavcodec/x86/mpegvideodsp.c in FFmpeg 2.3 and 3.4 does not properly validate widths and heights, which allows remote attackers to cause a denial of service (integer signedness error and out-of-array read) via a crafted MPEG file. | https://nvd.nist.gov/vuln/detail/CVE-2017-17081 |
159,856 | FFmpeg | 58cf31cee7a456057f337b3102a03206d833d5e8 | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/58cf31cee7a456057f337b3102a03206d833d5e8 | avcodec/x86/mpegvideodsp: Fix signedness bug in need_emu
Fixes: out of array read
Fixes: 3516/attachment-311488.dat
Found-by: Insu Yun, Georgia Tech.
Tested-by: wuninsu@gmail.com
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> | 0 | static void gmc_mmx(uint8_t *dst, uint8_t *src,
int stride, int h, int ox, int oy,
int dxx, int dxy, int dyx, int dyy,
int shift, int r, int width, int height)
{
const int w = 8;
const int ix = ox >> (16 + shift);
const int iy = oy >> (16 ... | 209,257,746,939,698,800,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-17081 | The gmc_mmx function in libavcodec/x86/mpegvideodsp.c in FFmpeg 2.3 and 3.4 does not properly validate widths and heights, which allows remote attackers to cause a denial of service (integer signedness error and out-of-array read) via a crafted MPEG file. | https://nvd.nist.gov/vuln/detail/CVE-2017-17081 |
2,386 | linux | 373c4557d2aa362702c4c2d41288fb1e54990b7c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/373c4557d2aa362702c4c2d41288fb1e54990b7c | mm/pagewalk.c: report holes in hugetlb ranges
This matters at least for the mincore syscall, which will otherwise copy
uninitialized memory from the page allocator to userspace. It is
probably also a correctness error for /proc/$pid/pagemap, but I haven't
tested that.
Removing the `walk->hugetlb_entry` condition in ... | 1 | static int walk_hugetlb_range(unsigned long addr, unsigned long end,
struct mm_walk *walk)
{
struct vm_area_struct *vma = walk->vma;
struct hstate *h = hstate_vma(vma);
unsigned long next;
unsigned long hmask = huge_page_mask(h);
unsigned long sz = huge_page_size(h);
pte_t *pte;
int err = 0;
do {
... | 27,644,966,037,369,066,000,000,000,000,000,000,000 | pagewalk.c | 34,507,566,426,524,797,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2017-16994 | The walk_hugetlb_range function in mm/pagewalk.c in the Linux kernel before 4.14.2 mishandles holes in hugetlb ranges, which allows local users to obtain sensitive information from uninitialized kernel memory via crafted use of the mincore() system call. | https://nvd.nist.gov/vuln/detail/CVE-2017-16994 |
159,857 | linux | 373c4557d2aa362702c4c2d41288fb1e54990b7c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/373c4557d2aa362702c4c2d41288fb1e54990b7c | mm/pagewalk.c: report holes in hugetlb ranges
This matters at least for the mincore syscall, which will otherwise copy
uninitialized memory from the page allocator to userspace. It is
probably also a correctness error for /proc/$pid/pagemap, but I haven't
tested that.
Removing the `walk->hugetlb_entry` condition in ... | 0 | static int walk_hugetlb_range(unsigned long addr, unsigned long end,
struct mm_walk *walk)
{
struct vm_area_struct *vma = walk->vma;
struct hstate *h = hstate_vma(vma);
unsigned long next;
unsigned long hmask = huge_page_mask(h);
unsigned long sz = huge_page_size(h);
pte_t *pte;
int err = 0;
do {
... | 7,379,111,644,242,995,000,000,000,000,000,000,000 | pagewalk.c | 188,109,403,780,752,200,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2017-16994 | The walk_hugetlb_range function in mm/pagewalk.c in the Linux kernel before 4.14.2 mishandles holes in hugetlb ranges, which allows local users to obtain sensitive information from uninitialized kernel memory via crafted use of the mincore() system call. | https://nvd.nist.gov/vuln/detail/CVE-2017-16994 |
2,392 | collectd | d16c24542b2f96a194d43a73c2e5778822b9cb47 | https://github.com/collectd/collectd | https://github.com/collectd/collectd/commit/d16c24542b2f96a194d43a73c2e5778822b9cb47 | snmp plugin: Fix double free of request PDU
snmp_sess_synch_response() always frees request PDU, in both case of request
error and success. If error condition occurs inside of `while (status == 0)`
loop, double free of `req` happens.
Issue: #2291
Signed-off-by: Florian Forster <octo@collectd.org> | 1 | static int csnmp_read_table(host_definition_t *host, data_definition_t *data) {
struct snmp_pdu *req;
struct snmp_pdu *res = NULL;
struct variable_list *vb;
const data_set_t *ds;
size_t oid_list_len = data->values_len + 1;
/* Holds the last OID returned by the device. We use this in the GETNEXT
* reque... | 218,389,400,164,176,200,000,000,000,000,000,000,000 | snmp.c | 37,805,710,159,185,360,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2017-16820 | The csnmp_read_table function in snmp.c in the SNMP plugin in collectd before 5.6.3 is susceptible to a double free in a certain error case, which could lead to a crash (or potentially have other impact). | https://nvd.nist.gov/vuln/detail/CVE-2017-16820 |
159,863 | collectd | d16c24542b2f96a194d43a73c2e5778822b9cb47 | https://github.com/collectd/collectd | https://github.com/collectd/collectd/commit/d16c24542b2f96a194d43a73c2e5778822b9cb47 | snmp plugin: Fix double free of request PDU
snmp_sess_synch_response() always frees request PDU, in both case of request
error and success. If error condition occurs inside of `while (status == 0)`
loop, double free of `req` happens.
Issue: #2291
Signed-off-by: Florian Forster <octo@collectd.org> | 0 | static int csnmp_read_table(host_definition_t *host, data_definition_t *data) {
struct snmp_pdu *req;
struct snmp_pdu *res = NULL;
struct variable_list *vb;
const data_set_t *ds;
size_t oid_list_len = data->values_len + 1;
/* Holds the last OID returned by the device. We use this in the GETNEXT
* reque... | 126,031,036,038,701,910,000,000,000,000,000,000,000 | snmp.c | 326,738,572,631,661,600,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2017-16820 | The csnmp_read_table function in snmp.c in the SNMP plugin in collectd before 5.6.3 is susceptible to a double free in a certain error case, which could lead to a crash (or potentially have other impact). | https://nvd.nist.gov/vuln/detail/CVE-2017-16820 |
2,396 | libav | cd4663dc80323ba64989d0c103d51ad3ee0e9c2f | https://github.com/libav/libav | https://github.com/libav/libav/commit/cd4663dc80323ba64989d0c103d51ad3ee0e9c2f | smacker: add sanity check for length in smacker_decode_tree()
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
Bug-Id: 1098
Cc: libav-stable@libav.org
Signed-off-by: Sean McGovern <gseanmcg@gmail.com> | 1 | static int smacker_decode_tree(BitstreamContext *bc, HuffContext *hc,
uint32_t prefix, int length)
{
if (!bitstream_read_bit(bc)) { // Leaf
if(hc->current >= 256){
av_log(NULL, AV_LOG_ERROR, "Tree size exceeded!\n");
return AVERROR_INVALIDDATA;
... | 123,413,656,536,164,610,000,000,000,000,000,000,000 | smacker.c | 256,567,352,689,102,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-16803 | In Libav through 11.11 and 12.x through 12.1, the smacker_decode_tree function in libavcodec/smacker.c does not properly restrict tree recursion, which allows remote attackers to cause a denial of service (bitstream.c:build_table() out-of-bounds read and application crash) via a crafted Smacker stream. | https://nvd.nist.gov/vuln/detail/CVE-2017-16803 |
159,865 | libav | cd4663dc80323ba64989d0c103d51ad3ee0e9c2f | https://github.com/libav/libav | https://github.com/libav/libav/commit/cd4663dc80323ba64989d0c103d51ad3ee0e9c2f | smacker: add sanity check for length in smacker_decode_tree()
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
Bug-Id: 1098
Cc: libav-stable@libav.org
Signed-off-by: Sean McGovern <gseanmcg@gmail.com> | 0 | static int smacker_decode_tree(BitstreamContext *bc, HuffContext *hc,
uint32_t prefix, int length)
{
if (length > SMKTREE_DECODE_MAX_RECURSION) {
av_log(NULL, AV_LOG_ERROR, "Maximum tree recursion level exceeded.\n");
return AVERROR_INVALIDDATA;
}
if (!bit... | 111,885,725,974,739,750,000,000,000,000,000,000,000 | smacker.c | 181,998,381,798,896,940,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-16803 | In Libav through 11.11 and 12.x through 12.1, the smacker_decode_tree function in libavcodec/smacker.c does not properly restrict tree recursion, which allows remote attackers to cause a denial of service (bitstream.c:build_table() out-of-bounds read and application crash) via a crafted Smacker stream. | https://nvd.nist.gov/vuln/detail/CVE-2017-16803 |
2,397 | linux | a50829479f58416a013a4ccca791336af3c584c7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a50829479f58416a013a4ccca791336af3c584c7 | Input: gtco - fix potential out-of-bound access
parse_hid_report_descriptor() has a while (i < length) loop, which
only guarantees that there's at least 1 byte in the buffer, but the
loop body can read multiple bytes which causes out-of-bounds access.
Reported-by: Andrey Konovalov <andreyknvl@google.com>
Reviewed-by:... | 1 | static void parse_hid_report_descriptor(struct gtco *device, char * report,
int length)
{
struct device *ddev = &device->intf->dev;
int x, i = 0;
/* Tag primitive vars */
__u8 prefix;
__u8 size;
__u8 tag;
__u8 type;
__u8 data = 0;
__u16 data16 = 0;
__u32 data32 = 0;
/* For parsing logi... | 179,175,241,032,229,640,000,000,000,000,000,000,000 | gtco.c | 44,965,940,214,388,830,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-16643 | The parse_hid_report_descriptor function in drivers/input/tablet/gtco.c in the Linux kernel before 4.13.11 allows local users to cause a denial of service (out-of-bounds read and system crash) or possibly have unspecified other impact via a crafted USB device. | https://nvd.nist.gov/vuln/detail/CVE-2017-16643 |
159,867 | linux | a50829479f58416a013a4ccca791336af3c584c7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a50829479f58416a013a4ccca791336af3c584c7 | Input: gtco - fix potential out-of-bound access
parse_hid_report_descriptor() has a while (i < length) loop, which
only guarantees that there's at least 1 byte in the buffer, but the
loop body can read multiple bytes which causes out-of-bounds access.
Reported-by: Andrey Konovalov <andreyknvl@google.com>
Reviewed-by:... | 0 | static void parse_hid_report_descriptor(struct gtco *device, char * report,
int length)
{
struct device *ddev = &device->intf->dev;
int x, i = 0;
/* Tag primitive vars */
__u8 prefix;
__u8 size;
__u8 tag;
__u8 type;
__u8 data = 0;
__u16 data16 = 0;
__u32 data32 = 0;
/* For parsing logi... | 276,005,118,287,738,930,000,000,000,000,000,000,000 | gtco.c | 288,356,986,229,759,850,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-16643 | The parse_hid_report_descriptor function in drivers/input/tablet/gtco.c in the Linux kernel before 4.13.11 allows local users to cause a denial of service (out-of-bounds read and system crash) or possibly have unspecified other impact via a crafted USB device. | https://nvd.nist.gov/vuln/detail/CVE-2017-16643 |
2,398 | ImageMagick | 2130bf6f89ded32ef0c88a11694f107c52566c53 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/2130bf6f89ded32ef0c88a11694f107c52566c53 | https://github.com/ImageMagick/ImageMagick/issues/85 | 1 | static Image *ReadWPGImage(const ImageInfo *image_info,
ExceptionInfo *exception)
{
typedef struct
{
size_t FileId;
MagickOffsetType DataOffset;
unsigned int ProductType;
unsigned int FileType;
unsigned char MajorVersion;
unsigned char MinorVersion;
unsigned int EncryptKey;
unsigne... | 159,163,992,560,882,620,000,000,000,000,000,000,000 | wpg.c | 21,386,277,562,852,665,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-16546 | The ReadWPGImage function in coders/wpg.c in ImageMagick 7.0.7-9 does not properly validate the colormap index in a WPG palette, which allows remote attackers to cause a denial of service (use of uninitialized data or invalid memory allocation) or possibly have unspecified other impact via a malformed WPG file. | https://nvd.nist.gov/vuln/detail/CVE-2017-16546 |
159,868 | ImageMagick | 2130bf6f89ded32ef0c88a11694f107c52566c53 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/2130bf6f89ded32ef0c88a11694f107c52566c53 | https://github.com/ImageMagick/ImageMagick/issues/85 | 0 | static Image *ReadWPGImage(const ImageInfo *image_info,
ExceptionInfo *exception)
{
typedef struct
{
size_t FileId;
MagickOffsetType DataOffset;
unsigned int ProductType;
unsigned int FileType;
unsigned char MajorVersion;
unsigned char MinorVersion;
unsigned int EncryptKey;
unsigne... | 260,682,318,150,162,040,000,000,000,000,000,000,000 | wpg.c | 28,991,499,355,064,067,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-16546 | The ReadWPGImage function in coders/wpg.c in ImageMagick 7.0.7-9 does not properly validate the colormap index in a WPG palette, which allows remote attackers to cause a denial of service (use of uninitialized data or invalid memory allocation) or possibly have unspecified other impact via a malformed WPG file. | https://nvd.nist.gov/vuln/detail/CVE-2017-16546 |
2,399 | linux | 1c0edc3633b56000e18d82fc241e3995ca18a69e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1c0edc3633b56000e18d82fc241e3995ca18a69e | USB: core: fix out-of-bounds access bug in usb_get_bos_descriptor()
Andrey used the syzkaller fuzzer to find an out-of-bounds memory
access in usb_get_bos_descriptor(). The code wasn't checking that the
next usb_dev_cap_header structure could fit into the remaining buffer
space.
This patch fixes the error and also r... | 1 | int usb_get_bos_descriptor(struct usb_device *dev)
{
struct device *ddev = &dev->dev;
struct usb_bos_descriptor *bos;
struct usb_dev_cap_header *cap;
unsigned char *buffer;
int length, total_len, num, i;
int ret;
bos = kzalloc(sizeof(struct usb_bos_descriptor), GFP_KERNEL);
if (!bos)
return -ENOMEM;
/* Get... | 326,295,248,605,660,370,000,000,000,000,000,000,000 | config.c | 207,673,244,129,416,860,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-16535 | The usb_get_bos_descriptor function in drivers/usb/core/config.c in the Linux kernel before 4.13.10 allows local users to cause a denial of service (out-of-bounds read and system crash) or possibly have unspecified other impact via a crafted USB device. | https://nvd.nist.gov/vuln/detail/CVE-2017-16535 |
159,869 | linux | 1c0edc3633b56000e18d82fc241e3995ca18a69e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1c0edc3633b56000e18d82fc241e3995ca18a69e | USB: core: fix out-of-bounds access bug in usb_get_bos_descriptor()
Andrey used the syzkaller fuzzer to find an out-of-bounds memory
access in usb_get_bos_descriptor(). The code wasn't checking that the
next usb_dev_cap_header structure could fit into the remaining buffer
space.
This patch fixes the error and also r... | 0 | int usb_get_bos_descriptor(struct usb_device *dev)
{
struct device *ddev = &dev->dev;
struct usb_bos_descriptor *bos;
struct usb_dev_cap_header *cap;
unsigned char *buffer;
int length, total_len, num, i;
int ret;
bos = kzalloc(sizeof(struct usb_bos_descriptor), GFP_KERNEL);
if (!bos)
return -ENOMEM;
/* Get... | 296,617,939,984,855,700,000,000,000,000,000,000,000 | config.c | 137,152,707,622,443,090,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-16535 | The usb_get_bos_descriptor function in drivers/usb/core/config.c in the Linux kernel before 4.13.10 allows local users to cause a denial of service (out-of-bounds read and system crash) or possibly have unspecified other impact via a crafted USB device. | https://nvd.nist.gov/vuln/detail/CVE-2017-16535 |
2,400 | linux | 2e1c42391ff2556387b3cb6308b24f6f65619feb | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2e1c42391ff2556387b3cb6308b24f6f65619feb | USB: core: harden cdc_parse_cdc_header
Andrey Konovalov reported a possible out-of-bounds problem for the
cdc_parse_cdc_header function. He writes:
It looks like cdc_parse_cdc_header() doesn't validate buflen
before accessing buffer[1], buffer[2] and so on. The only check
present is while (buflen > 0).
So fix thi... | 1 | int cdc_parse_cdc_header(struct usb_cdc_parsed_header *hdr,
struct usb_interface *intf,
u8 *buffer,
int buflen)
{
/* duplicates are ignored */
struct usb_cdc_union_desc *union_header = NULL;
/* duplicates are not tolerated */
struct usb_cdc_header_desc *header = NULL;
struct usb_cdc_ether_desc *ether ... | 126,505,036,785,122,100,000,000,000,000,000,000,000 | usbnet.c | 152,912,995,219,752,140,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-16534 | The cdc_parse_cdc_header function in drivers/usb/core/message.c in the Linux kernel before 4.13.6 allows local users to cause a denial of service (out-of-bounds read and system crash) or possibly have unspecified other impact via a crafted USB device. | https://nvd.nist.gov/vuln/detail/CVE-2017-16534 |
159,870 | linux | 2e1c42391ff2556387b3cb6308b24f6f65619feb | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2e1c42391ff2556387b3cb6308b24f6f65619feb | USB: core: harden cdc_parse_cdc_header
Andrey Konovalov reported a possible out-of-bounds problem for the
cdc_parse_cdc_header function. He writes:
It looks like cdc_parse_cdc_header() doesn't validate buflen
before accessing buffer[1], buffer[2] and so on. The only check
present is while (buflen > 0).
So fix thi... | 0 | int cdc_parse_cdc_header(struct usb_cdc_parsed_header *hdr,
struct usb_interface *intf,
u8 *buffer,
int buflen)
{
/* duplicates are ignored */
struct usb_cdc_union_desc *union_header = NULL;
/* duplicates are not tolerated */
struct usb_cdc_header_desc *header = NULL;
struct usb_cdc_ether_desc *ether ... | 197,948,552,108,266,000,000,000,000,000,000,000,000 | message.c | 50,746,547,023,387,070,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-16534 | The cdc_parse_cdc_header function in drivers/usb/core/message.c in the Linux kernel before 4.13.6 allows local users to cause a denial of service (out-of-bounds read and system crash) or possibly have unspecified other impact via a crafted USB device. | https://nvd.nist.gov/vuln/detail/CVE-2017-16534 |
2,401 | linux | f043bfc98c193c284e2cd768fefabe18ac2fed9b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f043bfc98c193c284e2cd768fefabe18ac2fed9b | HID: usbhid: fix out-of-bounds bug
The hid descriptor identifies the length and type of subordinate
descriptors for a device. If the received hid descriptor is smaller than
the size of the struct hid_descriptor, it is possible to cause
out-of-bounds.
In addition, if bNumDescriptors of the hid descriptor have an incor... | 1 | static int usbhid_parse(struct hid_device *hid)
{
struct usb_interface *intf = to_usb_interface(hid->dev.parent);
struct usb_host_interface *interface = intf->cur_altsetting;
struct usb_device *dev = interface_to_usbdev (intf);
struct hid_descriptor *hdesc;
u32 quirks = 0;
unsigned int rsize = 0;
char *rdesc;
... | 185,715,477,481,380,400,000,000,000,000,000,000,000 | hid-core.c | 269,991,493,491,351,670,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-16533 | The usbhid_parse function in drivers/hid/usbhid/hid-core.c in the Linux kernel before 4.13.8 allows local users to cause a denial of service (out-of-bounds read and system crash) or possibly have unspecified other impact via a crafted USB device. | https://nvd.nist.gov/vuln/detail/CVE-2017-16533 |
159,871 | linux | f043bfc98c193c284e2cd768fefabe18ac2fed9b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f043bfc98c193c284e2cd768fefabe18ac2fed9b | HID: usbhid: fix out-of-bounds bug
The hid descriptor identifies the length and type of subordinate
descriptors for a device. If the received hid descriptor is smaller than
the size of the struct hid_descriptor, it is possible to cause
out-of-bounds.
In addition, if bNumDescriptors of the hid descriptor have an incor... | 0 | static int usbhid_parse(struct hid_device *hid)
{
struct usb_interface *intf = to_usb_interface(hid->dev.parent);
struct usb_host_interface *interface = intf->cur_altsetting;
struct usb_device *dev = interface_to_usbdev (intf);
struct hid_descriptor *hdesc;
u32 quirks = 0;
unsigned int rsize = 0;
char *rdesc;
... | 93,651,354,144,858,760,000,000,000,000,000,000,000 | hid-core.c | 242,795,023,680,125,640,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-16533 | The usbhid_parse function in drivers/hid/usbhid/hid-core.c in the Linux kernel before 4.13.8 allows local users to cause a denial of service (out-of-bounds read and system crash) or possibly have unspecified other impact via a crafted USB device. | https://nvd.nist.gov/vuln/detail/CVE-2017-16533 |
2,403 | linux | bfc81a8bc18e3c4ba0cbaa7666ff76be2f998991 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/bfc81a8bc18e3c4ba0cbaa7666ff76be2f998991 | ALSA: usb-audio: Check out-of-bounds access by corrupted buffer descriptor
When a USB-audio device receives a maliciously adjusted or corrupted
buffer descriptor, the USB-audio driver may access an out-of-bounce
value at its parser. This was detected by syzkaller, something like:
BUG: KASAN: slab-out-of-bounds in ... | 1 | static int snd_usb_create_streams(struct snd_usb_audio *chip, int ctrlif)
{
struct usb_device *dev = chip->dev;
struct usb_host_interface *host_iface;
struct usb_interface_descriptor *altsd;
void *control_header;
int i, protocol;
/* find audiocontrol interface */
host_iface = &usb_ifnum_to_if(dev, ctrlif)... | 17,984,538,902,999,570,000,000,000,000,000,000,000 | card.c | 34,439,524,157,371,130,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-16529 | The snd_usb_create_streams function in sound/usb/card.c in the Linux kernel before 4.13.6 allows local users to cause a denial of service (out-of-bounds read and system crash) or possibly have unspecified other impact via a crafted USB device. | https://nvd.nist.gov/vuln/detail/CVE-2017-16529 |
159,872 | linux | bfc81a8bc18e3c4ba0cbaa7666ff76be2f998991 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/bfc81a8bc18e3c4ba0cbaa7666ff76be2f998991 | ALSA: usb-audio: Check out-of-bounds access by corrupted buffer descriptor
When a USB-audio device receives a maliciously adjusted or corrupted
buffer descriptor, the USB-audio driver may access an out-of-bounce
value at its parser. This was detected by syzkaller, something like:
BUG: KASAN: slab-out-of-bounds in ... | 0 | static int snd_usb_create_streams(struct snd_usb_audio *chip, int ctrlif)
{
struct usb_device *dev = chip->dev;
struct usb_host_interface *host_iface;
struct usb_interface_descriptor *altsd;
void *control_header;
int i, protocol;
int rest_bytes;
/* find audiocontrol interface */
host_iface = &usb_ifnum_t... | 331,711,688,182,095,300,000,000,000,000,000,000,000 | card.c | 52,985,470,395,593,900,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-16529 | The snd_usb_create_streams function in sound/usb/card.c in the Linux kernel before 4.13.6 allows local users to cause a denial of service (out-of-bounds read and system crash) or possibly have unspecified other impact via a crafted USB device. | https://nvd.nist.gov/vuln/detail/CVE-2017-16529 |
2,404 | linux | fc27fe7e8deef2f37cba3f2be2d52b6ca5eb9d57 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fc27fe7e8deef2f37cba3f2be2d52b6ca5eb9d57 | ALSA: seq: Cancel pending autoload work at unbinding device
ALSA sequencer core has a mechanism to load the enumerated devices
automatically, and it's performed in an off-load work. This seems
causing some race when a sequencer is removed while the pending
autoload work is running. As syzkaller spotted, it may lead ... | 1 | static int snd_seq_device_dev_free(struct snd_device *device)
{
struct snd_seq_device *dev = device->device_data;
put_device(&dev->dev);
return 0;
}
| 27,591,105,700,120,664,000,000,000,000,000,000,000 | seq_device.c | 141,577,229,654,057,000,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-16528 | sound/core/seq_device.c in the Linux kernel before 4.13.4 allows local users to cause a denial of service (snd_rawmidi_dev_seq_free use-after-free and system crash) or possibly have unspecified other impact via a crafted USB device. | https://nvd.nist.gov/vuln/detail/CVE-2017-16528 |
57,066 | linux | fc27fe7e8deef2f37cba3f2be2d52b6ca5eb9d57 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/fc27fe7e8deef2f37cba3f2be2d52b6ca5eb9d57 | ALSA: seq: Cancel pending autoload work at unbinding device
ALSA sequencer core has a mechanism to load the enumerated devices
automatically, and it's performed in an off-load work. This seems
causing some race when a sequencer is removed while the pending
autoload work is running. As syzkaller spotted, it may lead ... | 0 | static int snd_seq_device_dev_disconnect(struct snd_device *device)
{
struct snd_seq_device *dev = device->device_data;
device_del(&dev->dev);
return 0;
}
| 8,838,769,083,916,457,000,000,000,000,000,000,000 | seq_device.c | 219,804,966,289,572,060,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-16528 | sound/core/seq_device.c in the Linux kernel before 4.13.4 allows local users to cause a denial of service (snd_rawmidi_dev_seq_free use-after-free and system crash) or possibly have unspecified other impact via a crafted USB device. | https://nvd.nist.gov/vuln/detail/CVE-2017-16528 |
2,409 | linux | 299d7572e46f98534033a9e65973f13ad1ce9047 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/299d7572e46f98534033a9e65973f13ad1ce9047 | USB: serial: console: fix use-after-free after failed setup
Make sure to reset the USB-console port pointer when console setup fails
in order to avoid having the struct usb_serial be prematurely freed by
the console code when the device is later disconnected.
Fixes: 73e487fdb75f ("[PATCH] USB console: fix disconnecti... | 1 | static int usb_console_setup(struct console *co, char *options)
{
struct usbcons_info *info = &usbcons_info;
int baud = 9600;
int bits = 8;
int parity = 'n';
int doflow = 0;
int cflag = CREAD | HUPCL | CLOCAL;
char *s;
struct usb_serial *serial;
struct usb_serial_port *port;
int retval;
struct tty_struct *tt... | 315,797,150,859,318,100,000,000,000,000,000,000,000 | console.c | 325,898,431,350,988,400,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-16525 | The usb_serial_console_disconnect function in drivers/usb/serial/console.c in the Linux kernel before 4.13.8 allows local users to cause a denial of service (use-after-free and system crash) or possibly have unspecified other impact via a crafted USB device, related to disconnection and failed setup. | https://nvd.nist.gov/vuln/detail/CVE-2017-16525 |
159,878 | linux | 299d7572e46f98534033a9e65973f13ad1ce9047 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/299d7572e46f98534033a9e65973f13ad1ce9047 | USB: serial: console: fix use-after-free after failed setup
Make sure to reset the USB-console port pointer when console setup fails
in order to avoid having the struct usb_serial be prematurely freed by
the console code when the device is later disconnected.
Fixes: 73e487fdb75f ("[PATCH] USB console: fix disconnecti... | 0 | static int usb_console_setup(struct console *co, char *options)
{
struct usbcons_info *info = &usbcons_info;
int baud = 9600;
int bits = 8;
int parity = 'n';
int doflow = 0;
int cflag = CREAD | HUPCL | CLOCAL;
char *s;
struct usb_serial *serial;
struct usb_serial_port *port;
int retval;
struct tty_struct *tt... | 58,640,368,663,483,700,000,000,000,000,000,000,000 | console.c | 11,202,367,889,646,958,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-16525 | The usb_serial_console_disconnect function in drivers/usb/serial/console.c in the Linux kernel before 4.13.8 allows local users to cause a denial of service (use-after-free and system crash) or possibly have unspecified other impact via a crafted USB device, related to disconnection and failed setup. | https://nvd.nist.gov/vuln/detail/CVE-2017-16525 |
2,429 | shadowsocks-libev | c67d275803dc6ea22c558d06b1f7ba9f94cd8de3 | https://github.com/shadowsocks/shadowsocks-libev | https://github.com/shadowsocks/shadowsocks-libev/commit/c67d275803dc6ea22c558d06b1f7ba9f94cd8de3 | Fix #1734 | 1 | build_config(char *prefix, struct server *server)
{
char *path = NULL;
int path_size = strlen(prefix) + strlen(server->port) + 20;
path = ss_malloc(path_size);
snprintf(path, path_size, "%s/.shadowsocks_%s.conf", prefix, server->port);
FILE *f = fopen(path, "w+");
if (f == NULL) {
... | 329,376,205,814,019,100,000,000,000,000,000,000,000 | manager.c | 12,158,703,574,109,284,000,000,000,000,000,000,000 | [
"CWE-78"
] | CVE-2017-15924 | In manager.c in ss-manager in shadowsocks-libev 3.1.0, improper parsing allows command injection via shell metacharacters in a JSON configuration request received via 127.0.0.1 UDP traffic, related to the add_server, build_config, and construct_command_line functions. | https://nvd.nist.gov/vuln/detail/CVE-2017-15924 |
159,894 | shadowsocks-libev | c67d275803dc6ea22c558d06b1f7ba9f94cd8de3 | https://github.com/shadowsocks/shadowsocks-libev | https://github.com/shadowsocks/shadowsocks-libev/commit/c67d275803dc6ea22c558d06b1f7ba9f94cd8de3 | Fix #1734 | 0 | build_config(char *prefix, struct server *server)
build_config(char *prefix, struct manager_ctx *manager, struct server *server)
{
char *path = NULL;
int path_size = strlen(prefix) + strlen(server->port) + 20;
path = ss_malloc(path_size);
snprintf(path, path_size, "%s/.shadowsocks_%s.conf", prefi... | 111,469,816,066,172,590,000,000,000,000,000,000,000 | None | null | [
"CWE-78"
] | CVE-2017-15924 | In manager.c in ss-manager in shadowsocks-libev 3.1.0, improper parsing allows command injection via shell metacharacters in a JSON configuration request received via 127.0.0.1 UDP traffic, related to the add_server, build_config, and construct_command_line functions. | https://nvd.nist.gov/vuln/detail/CVE-2017-15924 |
2,430 | shadowsocks-libev | c67d275803dc6ea22c558d06b1f7ba9f94cd8de3 | https://github.com/shadowsocks/shadowsocks-libev | https://github.com/shadowsocks/shadowsocks-libev/commit/c67d275803dc6ea22c558d06b1f7ba9f94cd8de3 | Fix #1734 | 1 | construct_command_line(struct manager_ctx *manager, struct server *server)
{
static char cmd[BUF_SIZE];
char *method = manager->method;
int i;
build_config(working_dir, server);
if (server->method) method = server->method;
memset(cmd, 0, BUF_SIZE);
snprintf(cmd, BUF_SIZE,
... | 56,556,845,946,959,245,000,000,000,000,000,000,000 | None | null | [
"CWE-78"
] | CVE-2017-15924 | In manager.c in ss-manager in shadowsocks-libev 3.1.0, improper parsing allows command injection via shell metacharacters in a JSON configuration request received via 127.0.0.1 UDP traffic, related to the add_server, build_config, and construct_command_line functions. | https://nvd.nist.gov/vuln/detail/CVE-2017-15924 |
159,895 | shadowsocks-libev | c67d275803dc6ea22c558d06b1f7ba9f94cd8de3 | https://github.com/shadowsocks/shadowsocks-libev | https://github.com/shadowsocks/shadowsocks-libev/commit/c67d275803dc6ea22c558d06b1f7ba9f94cd8de3 | Fix #1734 | 0 | construct_command_line(struct manager_ctx *manager, struct server *server)
{
static char cmd[BUF_SIZE];
int i;
int port;
port = atoi(server->port);
build_config(working_dir, manager, server);
memset(cmd, 0, BUF_SIZE);
snprintf(cmd, BUF_SIZE,
"%s --manager-address %s -... | 216,937,687,591,227,380,000,000,000,000,000,000,000 | None | null | [
"CWE-78"
] | CVE-2017-15924 | In manager.c in ss-manager in shadowsocks-libev 3.1.0, improper parsing allows command injection via shell metacharacters in a JSON configuration request received via 127.0.0.1 UDP traffic, related to the add_server, build_config, and construct_command_line functions. | https://nvd.nist.gov/vuln/detail/CVE-2017-15924 |
2,431 | src | a6981567e8e215acc1ef690c8dbb30f2d9b00a19 | https://github.com/openbsd/src | https://github.com/openbsd/src/commit/a6981567e8e215acc1ef690c8dbb30f2d9b00a19 | disallow creation (of empty files) in read-only mode; reported by
Michal Zalewski, feedback & ok deraadt@ | 1 | process_open(u_int32_t id)
{
u_int32_t pflags;
Attrib a;
char *name;
int r, handle, fd, flags, mode, status = SSH2_FX_FAILURE;
if ((r = sshbuf_get_cstring(iqueue, &name, NULL)) != 0 ||
(r = sshbuf_get_u32(iqueue, &pflags)) != 0 || /* portable flags */
(r = decode_attrib(iqueue, &a)) != 0)
fatal("%s: b... | 7,430,065,301,267,818,000,000,000,000,000,000,000 | sftp-server.c | 80,709,009,585,823,290,000,000,000,000,000,000,000 | [
"CWE-269"
] | CVE-2017-15906 | The process_open function in sftp-server.c in OpenSSH before 7.6 does not properly prevent write operations in readonly mode, which allows attackers to create zero-length files. | https://nvd.nist.gov/vuln/detail/CVE-2017-15906 |
159,896 | src | a6981567e8e215acc1ef690c8dbb30f2d9b00a19 | https://github.com/openbsd/src | https://github.com/openbsd/src/commit/a6981567e8e215acc1ef690c8dbb30f2d9b00a19 | disallow creation (of empty files) in read-only mode; reported by
Michal Zalewski, feedback & ok deraadt@ | 0 | process_open(u_int32_t id)
{
u_int32_t pflags;
Attrib a;
char *name;
int r, handle, fd, flags, mode, status = SSH2_FX_FAILURE;
if ((r = sshbuf_get_cstring(iqueue, &name, NULL)) != 0 ||
(r = sshbuf_get_u32(iqueue, &pflags)) != 0 || /* portable flags */
(r = decode_attrib(iqueue, &a)) != 0)
fatal("%s: b... | 88,067,427,197,598,640,000,000,000,000,000,000,000 | sftp-server.c | 164,852,739,818,380,420,000,000,000,000,000,000,000 | [
"CWE-269"
] | CVE-2017-15906 | The process_open function in sftp-server.c in OpenSSH before 7.6 does not properly prevent write operations in readonly mode, which allows attackers to create zero-length files. | https://nvd.nist.gov/vuln/detail/CVE-2017-15906 |
2,432 | linux | 71bb99a02b32b4cc4265118e85f6035ca72923f0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/71bb99a02b32b4cc4265118e85f6035ca72923f0 | Bluetooth: bnep: bnep_add_connection() should verify that it's dealing with l2cap socket
same story as cmtp
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org> | 1 | int bnep_add_connection(struct bnep_connadd_req *req, struct socket *sock)
{
struct net_device *dev;
struct bnep_session *s, *ss;
u8 dst[ETH_ALEN], src[ETH_ALEN];
int err;
BT_DBG("");
baswap((void *) dst, &l2cap_pi(sock->sk)->chan->dst);
baswap((void *) src, &l2cap_pi(sock->sk)->chan->src);
/* session ... | 246,459,063,774,981,650,000,000,000,000,000,000,000 | core.c | 262,842,386,939,758,670,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2017-15868 | The bnep_add_connection function in net/bluetooth/bnep/core.c in the Linux kernel before 3.19 does not ensure that an l2cap socket is available, which allows local users to gain privileges via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2017-15868 |
159,897 | linux | 71bb99a02b32b4cc4265118e85f6035ca72923f0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/71bb99a02b32b4cc4265118e85f6035ca72923f0 | Bluetooth: bnep: bnep_add_connection() should verify that it's dealing with l2cap socket
same story as cmtp
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org> | 0 | int bnep_add_connection(struct bnep_connadd_req *req, struct socket *sock)
{
struct net_device *dev;
struct bnep_session *s, *ss;
u8 dst[ETH_ALEN], src[ETH_ALEN];
int err;
BT_DBG("");
if (!l2cap_is_socket(sock))
return -EBADFD;
baswap((void *) dst, &l2cap_pi(sock->sk)->chan->dst);
baswap((void *) src,... | 193,894,773,203,151,000,000,000,000,000,000,000,000 | core.c | 297,326,150,996,396,300,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2017-15868 | The bnep_add_connection function in net/bluetooth/bnep/core.c in the Linux kernel before 3.19 does not ensure that an l2cap socket is available, which allows local users to gain privileges via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2017-15868 |
2,433 | linux | 4971613c1639d8e5f102c4e797c3bf8f83a5a69e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4971613c1639d8e5f102c4e797c3bf8f83a5a69e | packet: in packet_do_bind, test fanout with bind_lock held
Once a socket has po->fanout set, it remains a member of the group
until it is destroyed. The prot_hook must be constant and identical
across sockets in the group.
If fanout_add races with packet_do_bind between the test of po->fanout
and taking the lock, the... | 1 | static int packet_do_bind(struct sock *sk, const char *name, int ifindex,
__be16 proto)
{
struct packet_sock *po = pkt_sk(sk);
struct net_device *dev_curr;
__be16 proto_curr;
bool need_rehook;
struct net_device *dev = NULL;
int ret = 0;
bool unlisted = false;
if (po->fanout)
return -EINVAL;
lock_so... | 113,256,036,162,153,370,000,000,000,000,000,000,000 | af_packet.c | 220,302,817,111,751,670,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2017-15649 | net/packet/af_packet.c in the Linux kernel before 4.13.6 allows local users to gain privileges via crafted system calls that trigger mishandling of packet_fanout data structures, because of a race condition (involving fanout_add and packet_do_bind) that leads to a use-after-free, a different vulnerability than CVE-2017... | https://nvd.nist.gov/vuln/detail/CVE-2017-15649 |
159,898 | linux | 4971613c1639d8e5f102c4e797c3bf8f83a5a69e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4971613c1639d8e5f102c4e797c3bf8f83a5a69e | packet: in packet_do_bind, test fanout with bind_lock held
Once a socket has po->fanout set, it remains a member of the group
until it is destroyed. The prot_hook must be constant and identical
across sockets in the group.
If fanout_add races with packet_do_bind between the test of po->fanout
and taking the lock, the... | 0 | static int packet_do_bind(struct sock *sk, const char *name, int ifindex,
__be16 proto)
{
struct packet_sock *po = pkt_sk(sk);
struct net_device *dev_curr;
__be16 proto_curr;
bool need_rehook;
struct net_device *dev = NULL;
int ret = 0;
bool unlisted = false;
lock_sock(sk);
spin_lock(&po->bind_lock)... | 274,470,350,671,509,000,000,000,000,000,000,000,000 | af_packet.c | 321,388,843,696,086,460,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2017-15649 | net/packet/af_packet.c in the Linux kernel before 4.13.6 allows local users to gain privileges via crafted system calls that trigger mishandling of packet_fanout data structures, because of a race condition (involving fanout_add and packet_do_bind) that leads to a use-after-free, a different vulnerability than CVE-2017... | https://nvd.nist.gov/vuln/detail/CVE-2017-15649 |
2,434 | linux | 814fb7bb7db5433757d76f4c4502c96fc53b0b5e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/814fb7bb7db5433757d76f4c4502c96fc53b0b5e | x86/fpu: Don't let userspace set bogus xcomp_bv
On x86, userspace can use the ptrace() or rt_sigreturn() system calls to
set a task's extended state (xstate) or "FPU" registers. ptrace() can
set them for another task using the PTRACE_SETREGSET request with
NT_X86_XSTATE, while rt_sigreturn() can set them for the curr... | 1 | int xstateregs_set(struct task_struct *target, const struct user_regset *regset,
unsigned int pos, unsigned int count,
const void *kbuf, const void __user *ubuf)
{
struct fpu *fpu = &target->thread.fpu;
struct xregs_state *xsave;
int ret;
if (!boot_cpu_has(X86_FEATURE_XSAVE))
return -ENODEV;
/*
* A w... | 29,945,451,952,694,290,000,000,000,000,000,000,000 | regset.c | 183,847,138,819,557,100,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2017-15537 | The x86/fpu (Floating Point Unit) subsystem in the Linux kernel before 4.13.5, when a processor supports the xsave feature but not the xsaves feature, does not correctly handle attempts to set reserved bits in the xstate header via the ptrace() or rt_sigreturn() system call, allowing local users to read the FPU registe... | https://nvd.nist.gov/vuln/detail/CVE-2017-15537 |
159,899 | linux | 814fb7bb7db5433757d76f4c4502c96fc53b0b5e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/814fb7bb7db5433757d76f4c4502c96fc53b0b5e | x86/fpu: Don't let userspace set bogus xcomp_bv
On x86, userspace can use the ptrace() or rt_sigreturn() system calls to
set a task's extended state (xstate) or "FPU" registers. ptrace() can
set them for another task using the PTRACE_SETREGSET request with
NT_X86_XSTATE, while rt_sigreturn() can set them for the curr... | 0 | int xstateregs_set(struct task_struct *target, const struct user_regset *regset,
unsigned int pos, unsigned int count,
const void *kbuf, const void __user *ubuf)
{
struct fpu *fpu = &target->thread.fpu;
struct xregs_state *xsave;
int ret;
if (!boot_cpu_has(X86_FEATURE_XSAVE))
return -ENODEV;
/*
* A w... | 299,520,998,669,887,650,000,000,000,000,000,000,000 | regset.c | 112,839,075,607,541,590,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2017-15537 | The x86/fpu (Floating Point Unit) subsystem in the Linux kernel before 4.13.5, when a processor supports the xsave feature but not the xsaves feature, does not correctly handle attempts to set reserved bits in the xstate header via the ptrace() or rt_sigreturn() system call, allowing local users to read the FPU registe... | https://nvd.nist.gov/vuln/detail/CVE-2017-15537 |
2,435 | linux | 814fb7bb7db5433757d76f4c4502c96fc53b0b5e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/814fb7bb7db5433757d76f4c4502c96fc53b0b5e | x86/fpu: Don't let userspace set bogus xcomp_bv
On x86, userspace can use the ptrace() or rt_sigreturn() system calls to
set a task's extended state (xstate) or "FPU" registers. ptrace() can
set them for another task using the PTRACE_SETREGSET request with
NT_X86_XSTATE, while rt_sigreturn() can set them for the curr... | 1 | static int __fpu__restore_sig(void __user *buf, void __user *buf_fx, int size)
{
int ia32_fxstate = (buf != buf_fx);
struct task_struct *tsk = current;
struct fpu *fpu = &tsk->thread.fpu;
int state_size = fpu_kernel_xstate_size;
u64 xfeatures = 0;
int fx_only = 0;
ia32_fxstate &= (IS_ENABLED(CONFIG_X86_32) ||
... | 182,906,564,625,953,420,000,000,000,000,000,000,000 | signal.c | 124,646,612,792,535,150,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2017-15537 | The x86/fpu (Floating Point Unit) subsystem in the Linux kernel before 4.13.5, when a processor supports the xsave feature but not the xsaves feature, does not correctly handle attempts to set reserved bits in the xstate header via the ptrace() or rt_sigreturn() system call, allowing local users to read the FPU registe... | https://nvd.nist.gov/vuln/detail/CVE-2017-15537 |
159,900 | linux | 814fb7bb7db5433757d76f4c4502c96fc53b0b5e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/814fb7bb7db5433757d76f4c4502c96fc53b0b5e | x86/fpu: Don't let userspace set bogus xcomp_bv
On x86, userspace can use the ptrace() or rt_sigreturn() system calls to
set a task's extended state (xstate) or "FPU" registers. ptrace() can
set them for another task using the PTRACE_SETREGSET request with
NT_X86_XSTATE, while rt_sigreturn() can set them for the curr... | 0 | static int __fpu__restore_sig(void __user *buf, void __user *buf_fx, int size)
{
int ia32_fxstate = (buf != buf_fx);
struct task_struct *tsk = current;
struct fpu *fpu = &tsk->thread.fpu;
int state_size = fpu_kernel_xstate_size;
u64 xfeatures = 0;
int fx_only = 0;
ia32_fxstate &= (IS_ENABLED(CONFIG_X86_32) ||
... | 268,742,358,235,233,620,000,000,000,000,000,000,000 | signal.c | 38,184,956,492,971,130,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2017-15537 | The x86/fpu (Floating Point Unit) subsystem in the Linux kernel before 4.13.5, when a processor supports the xsave feature but not the xsaves feature, does not correctly handle attempts to set reserved bits in the xstate header via the ptrace() or rt_sigreturn() system call, allowing local users to read the FPU registe... | https://nvd.nist.gov/vuln/detail/CVE-2017-15537 |
2,438 | linux | ac64115a66c18c01745bbd3c47a36b124e5fd8c0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac64115a66c18c01745bbd3c47a36b124e5fd8c0 | KVM: PPC: Fix oops when checking KVM_CAP_PPC_HTM
The following program causes a kernel oops:
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <sys/ioctl.h>
#include <linux/kvm.h>
main()
{
int fd = open("/dev/kvm", O_RDWR);
ioctl(fd, KVM_CHECK_EXTENSION, KVM_CAP_PPC_HTM);
}
This happe... | 1 | int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext)
{
int r;
/* Assume we're using HV mode when the HV module is loaded */
int hv_enabled = kvmppc_hv_ops ? 1 : 0;
if (kvm) {
/*
* Hooray - we know which VM type we're running on. Depend on
* that rather than the guess above.
*/
hv_enabled = is_k... | 78,468,150,303,237,020,000,000,000,000,000,000,000 | powerpc.c | 261,018,331,033,590,770,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-15306 | The kvm_vm_ioctl_check_extension function in arch/powerpc/kvm/powerpc.c in the Linux kernel before 4.13.11 allows local users to cause a denial of service (NULL pointer dereference and system crash) via a KVM_CHECK_EXTENSION KVM_CAP_PPC_HTM ioctl call to /dev/kvm. | https://nvd.nist.gov/vuln/detail/CVE-2017-15306 |
159,904 | linux | ac64115a66c18c01745bbd3c47a36b124e5fd8c0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac64115a66c18c01745bbd3c47a36b124e5fd8c0 | KVM: PPC: Fix oops when checking KVM_CAP_PPC_HTM
The following program causes a kernel oops:
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <sys/ioctl.h>
#include <linux/kvm.h>
main()
{
int fd = open("/dev/kvm", O_RDWR);
ioctl(fd, KVM_CHECK_EXTENSION, KVM_CAP_PPC_HTM);
}
This happe... | 0 | int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext)
{
int r;
/* Assume we're using HV mode when the HV module is loaded */
int hv_enabled = kvmppc_hv_ops ? 1 : 0;
if (kvm) {
/*
* Hooray - we know which VM type we're running on. Depend on
* that rather than the guess above.
*/
hv_enabled = is_k... | 283,547,472,272,319,650,000,000,000,000,000,000,000 | powerpc.c | 54,352,689,664,727,630,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-15306 | The kvm_vm_ioctl_check_extension function in arch/powerpc/kvm/powerpc.c in the Linux kernel before 4.13.11 allows local users to cause a denial of service (NULL pointer dereference and system crash) via a KVM_CHECK_EXTENSION KVM_CAP_PPC_HTM ioctl call to /dev/kvm. | https://nvd.nist.gov/vuln/detail/CVE-2017-15306 |
2,439 | ImageMagick | 9fd10cf630832b36a588c1545d8736539b2f1fb5 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/9fd10cf630832b36a588c1545d8736539b2f1fb5 | https://github.com/ImageMagick/ImageMagick/issues/592 | 1 | static Image *ReadGIFImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
#define BitSet(byte,bit) (((byte) & (bit)) == (bit))
#define LSBFirstOrder(x,y) (((y) << 8) | (x))
Image
*image,
*meta_image;
int
number_extensionss=0;
MagickBooleanType
status;
RectangleInfo
page;
re... | 49,173,632,362,171,760,000,000,000,000,000,000,000 | gif.c | 141,415,584,461,683,820,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2017-15277 | ReadGIFImage in coders/gif.c in ImageMagick 7.0.6-1 and GraphicsMagick 1.3.26 leaves the palette uninitialized when processing a GIF file that has neither a global nor local palette. If the affected product is used as a library loaded into a process that operates on interesting data, this data sometimes can be leaked v... | https://nvd.nist.gov/vuln/detail/CVE-2017-15277 |
159,905 | ImageMagick | 9fd10cf630832b36a588c1545d8736539b2f1fb5 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/9fd10cf630832b36a588c1545d8736539b2f1fb5 | https://github.com/ImageMagick/ImageMagick/issues/592 | 0 | static Image *ReadGIFImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
#define BitSet(byte,bit) (((byte) & (bit)) == (bit))
#define LSBFirstOrder(x,y) (((y) << 8) | (x))
Image
*image,
*meta_image;
int
number_extensionss=0;
MagickBooleanType
status;
RectangleInfo
page;
re... | 73,479,583,785,412,130,000,000,000,000,000,000,000 | gif.c | 251,101,221,767,455,020,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2017-15277 | ReadGIFImage in coders/gif.c in ImageMagick 7.0.6-1 and GraphicsMagick 1.3.26 leaves the palette uninitialized when processing a GIF file that has neither a global nor local palette. If the affected product is used as a library loaded into a process that operates on interesting data, this data sometimes can be leaked v... | https://nvd.nist.gov/vuln/detail/CVE-2017-15277 |
2,442 | linux | 71105998845fb012937332fe2e806d443c09e026 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/71105998845fb012937332fe2e806d443c09e026 | ALSA: seq: Fix use-after-free at creating a port
There is a potential race window opened at creating and deleting a
port via ioctl, as spotted by fuzzing. snd_seq_create_port() creates
a port object and returns its pointer, but it doesn't take the
refcount, thus it can be deleted immediately by another thread.
Meanwh... | 1 | static int snd_seq_ioctl_create_port(struct snd_seq_client *client, void *arg)
{
struct snd_seq_port_info *info = arg;
struct snd_seq_client_port *port;
struct snd_seq_port_callback *callback;
/* it is not allowed to create the port for an another client */
if (info->addr.client != client->number)
return ... | 335,970,720,208,132,700,000,000,000,000,000,000,000 | seq_clientmgr.c | 39,112,196,288,949,430,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-15265 | Race condition in the ALSA subsystem in the Linux kernel before 4.13.8 allows local users to cause a denial of service (use-after-free) or possibly have unspecified other impact via crafted /dev/snd/seq ioctl calls, related to sound/core/seq/seq_clientmgr.c and sound/core/seq/seq_ports.c. | https://nvd.nist.gov/vuln/detail/CVE-2017-15265 |
159,908 | linux | 71105998845fb012937332fe2e806d443c09e026 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/71105998845fb012937332fe2e806d443c09e026 | ALSA: seq: Fix use-after-free at creating a port
There is a potential race window opened at creating and deleting a
port via ioctl, as spotted by fuzzing. snd_seq_create_port() creates
a port object and returns its pointer, but it doesn't take the
refcount, thus it can be deleted immediately by another thread.
Meanwh... | 0 | static int snd_seq_ioctl_create_port(struct snd_seq_client *client, void *arg)
{
struct snd_seq_port_info *info = arg;
struct snd_seq_client_port *port;
struct snd_seq_port_callback *callback;
int port_idx;
/* it is not allowed to create the port for an another client */
if (info->addr.client != client->nu... | 44,290,091,024,576,670,000,000,000,000,000,000,000 | seq_clientmgr.c | 278,943,817,545,937,000,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-15265 | Race condition in the ALSA subsystem in the Linux kernel before 4.13.8 allows local users to cause a denial of service (use-after-free) or possibly have unspecified other impact via crafted /dev/snd/seq ioctl calls, related to sound/core/seq/seq_clientmgr.c and sound/core/seq/seq_ports.c. | https://nvd.nist.gov/vuln/detail/CVE-2017-15265 |
2,443 | linux | 71105998845fb012937332fe2e806d443c09e026 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/71105998845fb012937332fe2e806d443c09e026 | ALSA: seq: Fix use-after-free at creating a port
There is a potential race window opened at creating and deleting a
port via ioctl, as spotted by fuzzing. snd_seq_create_port() creates
a port object and returns its pointer, but it doesn't take the
refcount, thus it can be deleted immediately by another thread.
Meanwh... | 1 | struct snd_seq_client_port *snd_seq_create_port(struct snd_seq_client *client,
int port)
{
unsigned long flags;
struct snd_seq_client_port *new_port, *p;
int num = -1;
/* sanity check */
if (snd_BUG_ON(!client))
return NULL;
if (client->num_ports >= SNDRV_SEQ_MAX_PORTS) {
pr_warn("ALSA: seq: too m... | 153,601,357,183,929,500,000,000,000,000,000,000,000 | seq_ports.c | 324,717,315,064,208,880,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-15265 | Race condition in the ALSA subsystem in the Linux kernel before 4.13.8 allows local users to cause a denial of service (use-after-free) or possibly have unspecified other impact via crafted /dev/snd/seq ioctl calls, related to sound/core/seq/seq_clientmgr.c and sound/core/seq/seq_ports.c. | https://nvd.nist.gov/vuln/detail/CVE-2017-15265 |
159,909 | linux | 71105998845fb012937332fe2e806d443c09e026 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/71105998845fb012937332fe2e806d443c09e026 | ALSA: seq: Fix use-after-free at creating a port
There is a potential race window opened at creating and deleting a
port via ioctl, as spotted by fuzzing. snd_seq_create_port() creates
a port object and returns its pointer, but it doesn't take the
refcount, thus it can be deleted immediately by another thread.
Meanwh... | 0 | struct snd_seq_client_port *snd_seq_create_port(struct snd_seq_client *client,
int port)
{
unsigned long flags;
struct snd_seq_client_port *new_port, *p;
int num = -1;
/* sanity check */
if (snd_BUG_ON(!client))
return NULL;
if (client->num_ports >= SNDRV_SEQ_MAX_PORTS) {
pr_warn("ALSA: seq: too m... | 178,376,366,249,114,920,000,000,000,000,000,000,000 | seq_ports.c | 250,365,891,079,092,960,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-15265 | Race condition in the ALSA subsystem in the Linux kernel before 4.13.8 allows local users to cause a denial of service (use-after-free) or possibly have unspecified other impact via crafted /dev/snd/seq ioctl calls, related to sound/core/seq/seq_clientmgr.c and sound/core/seq/seq_ports.c. | https://nvd.nist.gov/vuln/detail/CVE-2017-15265 |
2,448 | linux | 94f1bb15bed84ad6c893916b7e7b9db6f1d7eec6 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/94f1bb15bed84ad6c893916b7e7b9db6f1d7eec6 | crypto: rng - Remove old low-level rng interface
Now that all rng implementations have switched over to the new
interface, we can remove the old low-level interface.
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> | 1 | static int rngapi_reset(struct crypto_rng *tfm, const u8 *seed,
unsigned int slen)
{
u8 *buf = NULL;
u8 *src = (u8 *)seed;
int err;
if (slen) {
buf = kmalloc(slen, GFP_KERNEL);
if (!buf)
return -ENOMEM;
memcpy(buf, seed, slen);
src = buf;
}
err = crypto_old_rng_alg(tfm)->rng_reset(tfm, src, slen);
... | 261,910,434,330,675,900,000,000,000,000,000,000,000 | rng.c | 69,958,027,888,044,070,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-15116 | The rngapi_reset function in crypto/rng.c in the Linux kernel before 4.2 allows attackers to cause a denial of service (NULL pointer dereference). | https://nvd.nist.gov/vuln/detail/CVE-2017-15116 |
159,912 | linux | 94f1bb15bed84ad6c893916b7e7b9db6f1d7eec6 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/94f1bb15bed84ad6c893916b7e7b9db6f1d7eec6 | crypto: rng - Remove old low-level rng interface
Now that all rng implementations have switched over to the new
interface, we can remove the old low-level interface.
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> | 0 | int crypto_rng_reset(struct crypto_rng *tfm, const u8 *seed, unsigned int slen)
{
u8 *buf = NULL;
int err;
if (!seed && slen) {
buf = kmalloc(slen, GFP_KERNEL);
if (!buf)
return -ENOMEM;
get_random_bytes(buf, slen);
seed = buf;
}
err = crypto_rng_alg(tfm)->seed(tfm, seed, slen);
kfree(buf);... | 219,672,799,958,391,920,000,000,000,000,000,000,000 | rng.c | 298,812,781,419,508,450,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-15116 | The rngapi_reset function in crypto/rng.c in the Linux kernel before 4.2 allows attackers to cause a denial of service (NULL pointer dereference). | https://nvd.nist.gov/vuln/detail/CVE-2017-15116 |
2,450 | linux | df80cd9b28b9ebaa284a41df611dbf3a2d05ca74 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/df80cd9b28b9ebaa284a41df611dbf3a2d05ca74 | sctp: do not peel off an assoc from one netns to another one
Now when peeling off an association to the sock in another netns, all
transports in this assoc are not to be rehashed and keep use the old
key in hashtable.
As a transport uses sk->net as the hash key to insert into hashtable,
it would miss removing these t... | 1 | int sctp_do_peeloff(struct sock *sk, sctp_assoc_t id, struct socket **sockp)
{
struct sctp_association *asoc = sctp_id2assoc(sk, id);
struct sctp_sock *sp = sctp_sk(sk);
struct socket *sock;
int err = 0;
if (!asoc)
return -EINVAL;
/* If there is a thread waiting on more sndbuf space for
* sending on t... | 74,326,315,358,449,760,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2017-15115 | The sctp_do_peeloff function in net/sctp/socket.c in the Linux kernel before 4.14 does not check whether the intended netns is used in a peel-off action, which allows local users to cause a denial of service (use-after-free and system crash) or possibly have unspecified other impact via crafted system calls. | https://nvd.nist.gov/vuln/detail/CVE-2017-15115 |
159,916 | linux | df80cd9b28b9ebaa284a41df611dbf3a2d05ca74 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/df80cd9b28b9ebaa284a41df611dbf3a2d05ca74 | sctp: do not peel off an assoc from one netns to another one
Now when peeling off an association to the sock in another netns, all
transports in this assoc are not to be rehashed and keep use the old
key in hashtable.
As a transport uses sk->net as the hash key to insert into hashtable,
it would miss removing these t... | 0 | int sctp_do_peeloff(struct sock *sk, sctp_assoc_t id, struct socket **sockp)
{
struct sctp_association *asoc = sctp_id2assoc(sk, id);
struct sctp_sock *sp = sctp_sk(sk);
struct socket *sock;
int err = 0;
/* Do not peel off from one netns to another one. */
if (!net_eq(current->nsproxy->net_ns, sock_net(sk)))
... | 265,211,569,756,228,280,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2017-15115 | The sctp_do_peeloff function in net/sctp/socket.c in the Linux kernel before 4.14 does not check whether the intended netns is used in a peel-off action, which allows local users to cause a denial of service (use-after-free and system crash) or possibly have unspecified other impact via crafted system calls. | https://nvd.nist.gov/vuln/detail/CVE-2017-15115 |
2,451 | linux | 2fae9e5a7babada041e2e161699ade2447a01989 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2fae9e5a7babada041e2e161699ade2447a01989 | usb: misc: legousbtower: Fix NULL pointer deference
This patch fixes a NULL pointer dereference caused by a race codition in
the probe function of the legousbtower driver. It re-structures the
probe function to only register the interface after successfully reading
the board's firmware ID.
The probe function does not... | 1 | static int tower_probe (struct usb_interface *interface, const struct usb_device_id *id)
{
struct device *idev = &interface->dev;
struct usb_device *udev = interface_to_usbdev(interface);
struct lego_usb_tower *dev = NULL;
struct usb_host_interface *iface_desc;
struct usb_endpoint_descriptor* endpoint;
struct tow... | 118,264,152,329,955,410,000,000,000,000,000,000,000 | legousbtower.c | 265,709,323,691,038,350,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-15102 | The tower_probe function in drivers/usb/misc/legousbtower.c in the Linux kernel before 4.8.1 allows local users (who are physically proximate for inserting a crafted USB device) to gain privileges by leveraging a write-what-where condition that occurs after a race condition and a NULL pointer dereference. | https://nvd.nist.gov/vuln/detail/CVE-2017-15102 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.