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,583 | linux | 4d06dd537f95683aba3651098ae288b7cbff8274 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4d06dd537f95683aba3651098ae288b7cbff8274 | cdc_ncm: do not call usbnet_link_change from cdc_ncm_bind
usbnet_link_change will call schedule_work and should be
avoided if bind is failing. Otherwise we will end up with
scheduled work referring to a netdev which has gone away.
Instead of making the call conditional, we can just defer
it to usbnet_probe, using the... | 0 | static int cdc_ncm_bind(struct usbnet *dev, struct usb_interface *intf)
{
/* MBIM backwards compatible function? */
if (cdc_ncm_select_altsetting(intf) != CDC_NCM_COMM_ALTSETTING_NCM)
return -ENODEV;
/* The NCM data altsetting is fixed, so we hard-coded it.
* Additionally, generic NCM devices are assumed ... | 234,001,887,689,879,900,000,000,000,000,000,000,000 | cdc_ncm.c | 266,799,510,454,463,430,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-3951 | Double free vulnerability in drivers/net/usb/cdc_ncm.c in the Linux kernel before 4.5 allows physically proximate attackers to cause a denial of service (system crash) or possibly have unspecified other impact by inserting a USB device with an invalid USB descriptor. | https://nvd.nist.gov/vuln/detail/CVE-2016-3951 |
2,100 | linux | 9842df62004f366b9fed2423e24df10542ee0dc5 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9842df62004f366b9fed2423e24df10542ee0dc5 | KVM: MTRR: remove MSR 0x2f8
MSR 0x2f8 accessed the 124th Variable Range MTRR ever since MTRR support
was introduced by 9ba075a664df ("KVM: MTRR support").
0x2f8 became harmful when 910a6aae4e2e ("KVM: MTRR: exactly define the
size of variable MTRRs") shrinked the array of VR MTRRs from 256 to 8,
which made access to ... | 1 | static bool msr_mtrr_valid(unsigned msr)
{
switch (msr) {
case 0x200 ... 0x200 + 2 * KVM_NR_VAR_MTRR - 1:
case MSR_MTRRfix64K_00000:
case MSR_MTRRfix16K_80000:
case MSR_MTRRfix16K_A0000:
case MSR_MTRRfix4K_C0000:
case MSR_MTRRfix4K_C8000:
case MSR_MTRRfix4K_D0000:
case MSR_MTRRfix4K_D8000:
case MSR_MTRRfix4K_... | 102,963,413,536,679,700,000,000,000,000,000,000,000 | mtrr.c | 76,338,732,130,362,965,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2016-3713 | The msr_mtrr_valid function in arch/x86/kvm/mtrr.c in the Linux kernel before 4.6.1 supports MSR 0x2f8, which allows guest OS users to read or write to the kvm_arch_vcpu data structure, and consequently obtain sensitive information or cause a denial of service (system crash), via a crafted ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2016-3713 |
159,602 | linux | 9842df62004f366b9fed2423e24df10542ee0dc5 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9842df62004f366b9fed2423e24df10542ee0dc5 | KVM: MTRR: remove MSR 0x2f8
MSR 0x2f8 accessed the 124th Variable Range MTRR ever since MTRR support
was introduced by 9ba075a664df ("KVM: MTRR support").
0x2f8 became harmful when 910a6aae4e2e ("KVM: MTRR: exactly define the
size of variable MTRRs") shrinked the array of VR MTRRs from 256 to 8,
which made access to ... | 0 | static bool msr_mtrr_valid(unsigned msr)
{
switch (msr) {
case 0x200 ... 0x200 + 2 * KVM_NR_VAR_MTRR - 1:
case MSR_MTRRfix64K_00000:
case MSR_MTRRfix16K_80000:
case MSR_MTRRfix16K_A0000:
case MSR_MTRRfix4K_C0000:
case MSR_MTRRfix4K_C8000:
case MSR_MTRRfix4K_D0000:
case MSR_MTRRfix4K_D8000:
case MSR_MTRRfix4K_... | 93,369,372,264,771,250,000,000,000,000,000,000,000 | mtrr.c | 321,107,133,986,052,150,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2016-3713 | The msr_mtrr_valid function in arch/x86/kvm/mtrr.c in the Linux kernel before 4.6.1 supports MSR 0x2f8, which allows guest OS users to read or write to the kvm_arch_vcpu data structure, and consequently obtain sensitive information or cause a denial of service (system crash), via a crafted ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2016-3713 |
2,111 | linux | 5a07975ad0a36708c6b0a5b9fea1ff811d0b0c1f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/5a07975ad0a36708c6b0a5b9fea1ff811d0b0c1f | USB: digi_acceleport: do sanity checking for the number of ports
The driver can be crashed with devices that expose crafted descriptors
with too few endpoints.
See: http://seclists.org/bugtraq/2016/Mar/61
Signed-off-by: Oliver Neukum <ONeukum@suse.com>
[johan: fix OOB endpoint check and add error messages ]
Cc: stab... | 1 | static int digi_startup(struct usb_serial *serial)
{
struct digi_serial *serial_priv;
int ret;
serial_priv = kzalloc(sizeof(*serial_priv), GFP_KERNEL);
if (!serial_priv)
return -ENOMEM;
spin_lock_init(&serial_priv->ds_serial_lock);
serial_priv->ds_oob_port_num = serial->type->num_ports;
serial_priv->d... | 92,921,252,960,895,370,000,000,000,000,000,000,000 | digi_acceleport.c | 48,588,831,952,256,350,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-3140 | The digi_port_init function in drivers/usb/serial/digi_acceleport.c in the Linux kernel before 4.5.1 allows physically proximate attackers to cause a denial of service (NULL pointer dereference and system crash) via a crafted endpoints value in a USB device descriptor. | https://nvd.nist.gov/vuln/detail/CVE-2016-3140 |
159,612 | linux | 5a07975ad0a36708c6b0a5b9fea1ff811d0b0c1f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/5a07975ad0a36708c6b0a5b9fea1ff811d0b0c1f | USB: digi_acceleport: do sanity checking for the number of ports
The driver can be crashed with devices that expose crafted descriptors
with too few endpoints.
See: http://seclists.org/bugtraq/2016/Mar/61
Signed-off-by: Oliver Neukum <ONeukum@suse.com>
[johan: fix OOB endpoint check and add error messages ]
Cc: stab... | 0 | static int digi_startup(struct usb_serial *serial)
{
struct device *dev = &serial->interface->dev;
struct digi_serial *serial_priv;
int ret;
int i;
/* check whether the device has the expected number of endpoints */
if (serial->num_port_pointers < serial->type->num_ports + 1) {
dev_err(dev, "OOB endpoints ... | 56,067,208,320,204,650,000,000,000,000,000,000,000 | digi_acceleport.c | 105,169,063,198,823,750,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-3140 | The digi_port_init function in drivers/usb/serial/digi_acceleport.c in the Linux kernel before 4.5.1 allows physically proximate attackers to cause a denial of service (NULL pointer dereference and system crash) via a crafted endpoints value in a USB device descriptor. | https://nvd.nist.gov/vuln/detail/CVE-2016-3140 |
2,112 | linux | 8835ba4a39cf53f705417b3b3a94eb067673f2c9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8835ba4a39cf53f705417b3b3a94eb067673f2c9 | USB: cdc-acm: more sanity checking
An attack has become available which pretends to be a quirky
device circumventing normal sanity checks and crashes the kernel
by an insufficient number of interfaces. This patch adds a check
to the code path for quirky devices.
Signed-off-by: Oliver Neukum <ONeukum@suse.com>
CC: sta... | 1 | static int acm_probe(struct usb_interface *intf,
const struct usb_device_id *id)
{
struct usb_cdc_union_desc *union_header = NULL;
struct usb_cdc_country_functional_desc *cfd = NULL;
unsigned char *buffer = intf->altsetting->extra;
int buflen = intf->altsetting->extralen;
struct usb_interface *control_inter... | 335,035,965,676,808,180,000,000,000,000,000,000,000 | cdc-acm.c | 196,077,235,851,485,950,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-3138 | The acm_probe function in drivers/usb/class/cdc-acm.c in the Linux kernel before 4.5.1 allows physically proximate attackers to cause a denial of service (NULL pointer dereference and system crash) via a USB device without both a control and a data endpoint descriptor. | https://nvd.nist.gov/vuln/detail/CVE-2016-3138 |
159,613 | linux | 8835ba4a39cf53f705417b3b3a94eb067673f2c9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8835ba4a39cf53f705417b3b3a94eb067673f2c9 | USB: cdc-acm: more sanity checking
An attack has become available which pretends to be a quirky
device circumventing normal sanity checks and crashes the kernel
by an insufficient number of interfaces. This patch adds a check
to the code path for quirky devices.
Signed-off-by: Oliver Neukum <ONeukum@suse.com>
CC: sta... | 0 | static int acm_probe(struct usb_interface *intf,
const struct usb_device_id *id)
{
struct usb_cdc_union_desc *union_header = NULL;
struct usb_cdc_country_functional_desc *cfd = NULL;
unsigned char *buffer = intf->altsetting->extra;
int buflen = intf->altsetting->extralen;
struct usb_interface *control_inter... | 246,535,794,857,782,150,000,000,000,000,000,000,000 | cdc-acm.c | 268,186,993,404,963,650,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-3138 | The acm_probe function in drivers/usb/class/cdc-acm.c in the Linux kernel before 4.5.1 allows physically proximate attackers to cause a denial of service (NULL pointer dereference and system crash) via a USB device without both a control and a data endpoint descriptor. | https://nvd.nist.gov/vuln/detail/CVE-2016-3138 |
2,113 | linux | c55aee1bf0e6b6feec8b2927b43f7a09a6d5f754 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c55aee1bf0e6b6feec8b2927b43f7a09a6d5f754 | USB: cypress_m8: add endpoint sanity check
An attack using missing endpoints exists.
CVE-2016-3137
Signed-off-by: Oliver Neukum <ONeukum@suse.com>
CC: stable@vger.kernel.org
Signed-off-by: Johan Hovold <johan@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 1 | static int cypress_generic_port_probe(struct usb_serial_port *port)
{
struct usb_serial *serial = port->serial;
struct cypress_private *priv;
priv = kzalloc(sizeof(struct cypress_private), GFP_KERNEL);
if (!priv)
return -ENOMEM;
priv->comm_is_ok = !0;
spin_lock_init(&priv->lock);
if (kfifo_alloc(&priv-... | 117,115,164,139,605,750,000,000,000,000,000,000,000 | cypress_m8.c | 185,821,559,057,352,680,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-3137 | drivers/usb/serial/cypress_m8.c in the Linux kernel before 4.5.1 allows physically proximate attackers to cause a denial of service (NULL pointer dereference and system crash) via a USB device without both an interrupt-in and an interrupt-out endpoint descriptor, related to the cypress_generic_port_probe and cypress_op... | https://nvd.nist.gov/vuln/detail/CVE-2016-3137 |
159,614 | linux | c55aee1bf0e6b6feec8b2927b43f7a09a6d5f754 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c55aee1bf0e6b6feec8b2927b43f7a09a6d5f754 | USB: cypress_m8: add endpoint sanity check
An attack using missing endpoints exists.
CVE-2016-3137
Signed-off-by: Oliver Neukum <ONeukum@suse.com>
CC: stable@vger.kernel.org
Signed-off-by: Johan Hovold <johan@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 0 | static int cypress_generic_port_probe(struct usb_serial_port *port)
{
struct usb_serial *serial = port->serial;
struct cypress_private *priv;
if (!port->interrupt_out_urb || !port->interrupt_in_urb) {
dev_err(&port->dev, "required endpoint is missing\n");
return -ENODEV;
}
priv = kzalloc(sizeof(struct cy... | 294,758,859,505,833,850,000,000,000,000,000,000,000 | cypress_m8.c | 171,222,433,674,711,220,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-3137 | drivers/usb/serial/cypress_m8.c in the Linux kernel before 4.5.1 allows physically proximate attackers to cause a denial of service (NULL pointer dereference and system crash) via a USB device without both an interrupt-in and an interrupt-out endpoint descriptor, related to the cypress_generic_port_probe and cypress_op... | https://nvd.nist.gov/vuln/detail/CVE-2016-3137 |
2,114 | linux | c55aee1bf0e6b6feec8b2927b43f7a09a6d5f754 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c55aee1bf0e6b6feec8b2927b43f7a09a6d5f754 | USB: cypress_m8: add endpoint sanity check
An attack using missing endpoints exists.
CVE-2016-3137
Signed-off-by: Oliver Neukum <ONeukum@suse.com>
CC: stable@vger.kernel.org
Signed-off-by: Johan Hovold <johan@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 1 | static int cypress_open(struct tty_struct *tty, struct usb_serial_port *port)
{
struct cypress_private *priv = usb_get_serial_port_data(port);
struct usb_serial *serial = port->serial;
unsigned long flags;
int result = 0;
if (!priv->comm_is_ok)
return -EIO;
/* clear halts before open */
usb_clear_halt(serial... | 24,933,462,448,207,740,000,000,000,000,000,000,000 | cypress_m8.c | 185,821,559,057,352,680,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-3137 | drivers/usb/serial/cypress_m8.c in the Linux kernel before 4.5.1 allows physically proximate attackers to cause a denial of service (NULL pointer dereference and system crash) via a USB device without both an interrupt-in and an interrupt-out endpoint descriptor, related to the cypress_generic_port_probe and cypress_op... | https://nvd.nist.gov/vuln/detail/CVE-2016-3137 |
159,615 | linux | c55aee1bf0e6b6feec8b2927b43f7a09a6d5f754 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c55aee1bf0e6b6feec8b2927b43f7a09a6d5f754 | USB: cypress_m8: add endpoint sanity check
An attack using missing endpoints exists.
CVE-2016-3137
Signed-off-by: Oliver Neukum <ONeukum@suse.com>
CC: stable@vger.kernel.org
Signed-off-by: Johan Hovold <johan@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 0 | static int cypress_open(struct tty_struct *tty, struct usb_serial_port *port)
{
struct cypress_private *priv = usb_get_serial_port_data(port);
struct usb_serial *serial = port->serial;
unsigned long flags;
int result = 0;
if (!priv->comm_is_ok)
return -EIO;
/* clear halts before open */
usb_clear_halt(serial... | 339,271,353,418,338,900,000,000,000,000,000,000,000 | cypress_m8.c | 171,222,433,674,711,220,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-3137 | drivers/usb/serial/cypress_m8.c in the Linux kernel before 4.5.1 allows physically proximate attackers to cause a denial of service (NULL pointer dereference and system crash) via a USB device without both an interrupt-in and an interrupt-out endpoint descriptor, related to the cypress_generic_port_probe and cypress_op... | https://nvd.nist.gov/vuln/detail/CVE-2016-3137 |
2,115 | linux | 4e9a0b05257f29cf4b75f3209243ed71614d062e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4e9a0b05257f29cf4b75f3209243ed71614d062e | USB: mct_u232: add sanity checking in probe
An attack using the lack of sanity checking in probe is known. This
patch checks for the existence of a second port.
CVE-2016-3136
Signed-off-by: Oliver Neukum <ONeukum@suse.com>
CC: stable@vger.kernel.org
[johan: add error message ]
Signed-off-by: Johan Hovold <johan@kern... | 1 | static int mct_u232_port_probe(struct usb_serial_port *port)
{
struct mct_u232_private *priv;
priv = kzalloc(sizeof(*priv), GFP_KERNEL);
if (!priv)
return -ENOMEM;
/* Use second interrupt-in endpoint for reading. */
priv->read_urb = port->serial->port[1]->interrupt_in_urb;
priv->read_urb->context = ... | 198,666,769,052,711,000,000,000,000,000,000,000,000 | mct_u232.c | 126,483,507,316,033,960,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-3136 | The mct_u232_msr_to_state function in drivers/usb/serial/mct_u232.c in the Linux kernel before 4.5.1 allows physically proximate attackers to cause a denial of service (NULL pointer dereference and system crash) via a crafted USB device without two interrupt-in endpoint descriptors. | https://nvd.nist.gov/vuln/detail/CVE-2016-3136 |
159,616 | linux | 4e9a0b05257f29cf4b75f3209243ed71614d062e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4e9a0b05257f29cf4b75f3209243ed71614d062e | USB: mct_u232: add sanity checking in probe
An attack using the lack of sanity checking in probe is known. This
patch checks for the existence of a second port.
CVE-2016-3136
Signed-off-by: Oliver Neukum <ONeukum@suse.com>
CC: stable@vger.kernel.org
[johan: add error message ]
Signed-off-by: Johan Hovold <johan@kern... | 0 | static int mct_u232_port_probe(struct usb_serial_port *port)
{
struct usb_serial *serial = port->serial;
struct mct_u232_private *priv;
/* check first to simplify error handling */
if (!serial->port[1] || !serial->port[1]->interrupt_in_urb) {
dev_err(&port->dev, "expected endpoint missing\n");
return -ENOD... | 293,402,256,324,937,930,000,000,000,000,000,000,000 | mct_u232.c | 90,841,458,884,258,440,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-3136 | The mct_u232_msr_to_state function in drivers/usb/serial/mct_u232.c in the Linux kernel before 4.5.1 allows physically proximate attackers to cause a denial of service (NULL pointer dereference and system crash) via a crafted USB device without two interrupt-in endpoint descriptors. | https://nvd.nist.gov/vuln/detail/CVE-2016-3136 |
2,116 | linux | d157bd761585605b7882935ffb86286919f62ea1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d157bd761585605b7882935ffb86286919f62ea1 | netfilter: x_tables: check for size overflow
Ben Hawkes says:
integer overflow in xt_alloc_table_info, which on 32-bit systems can
lead to small structure allocation and a copy_from_user based heap
corruption.
Reported-by: Ben Hawkes <hawkes@google.com>
Signed-off-by: Florian Westphal <fw@strlen.de>
Signed-off-by:... | 1 | struct xt_table_info *xt_alloc_table_info(unsigned int size)
{
struct xt_table_info *info = NULL;
size_t sz = sizeof(*info) + size;
/* Pedantry: prevent them from hitting BUG() in vmalloc.c --RR */
if ((SMP_ALIGN(size) >> PAGE_SHIFT) + 2 > totalram_pages)
return NULL;
if (sz <= (PAGE_SIZE << PAGE_ALLOC_C... | 123,369,081,460,672,790,000,000,000,000,000,000,000 | x_tables.c | 15,814,788,980,344,083,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2016-3135 | Integer overflow in the xt_alloc_table_info function in net/netfilter/x_tables.c in the Linux kernel through 4.5.2 on 32-bit platforms allows local users to gain privileges or cause a denial of service (heap memory corruption) via an IPT_SO_SET_REPLACE setsockopt call. | https://nvd.nist.gov/vuln/detail/CVE-2016-3135 |
159,617 | linux | d157bd761585605b7882935ffb86286919f62ea1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d157bd761585605b7882935ffb86286919f62ea1 | netfilter: x_tables: check for size overflow
Ben Hawkes says:
integer overflow in xt_alloc_table_info, which on 32-bit systems can
lead to small structure allocation and a copy_from_user based heap
corruption.
Reported-by: Ben Hawkes <hawkes@google.com>
Signed-off-by: Florian Westphal <fw@strlen.de>
Signed-off-by:... | 0 | struct xt_table_info *xt_alloc_table_info(unsigned int size)
{
struct xt_table_info *info = NULL;
size_t sz = sizeof(*info) + size;
if (sz < sizeof(*info))
return NULL;
/* Pedantry: prevent them from hitting BUG() in vmalloc.c --RR */
if ((SMP_ALIGN(size) >> PAGE_SHIFT) + 2 > totalram_pages)
return NUL... | 12,723,810,103,301,770,000,000,000,000,000,000,000 | x_tables.c | 235,525,317,983,388,930,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2016-3135 | Integer overflow in the xt_alloc_table_info function in net/netfilter/x_tables.c in the Linux kernel through 4.5.2 on 32-bit platforms allows local users to gain privileges or cause a denial of service (heap memory corruption) via an IPT_SO_SET_REPLACE setsockopt call. | https://nvd.nist.gov/vuln/detail/CVE-2016-3135 |
2,130 | php-src | 28a6ed9f9a36b9c517e4a8a429baf4dd382fc5d5 | https://github.com/php/php-src | http://github.com/php/php-src/commit/28a6ed9f9a36b9c517e4a8a429baf4dd382fc5d5?w=1 | Fix bug #71735: Double-free in SplDoublyLinkedList::offsetSet | 1 | SPL_METHOD(SplDoublyLinkedList, offsetSet)
{
zval *zindex, *value;
spl_dllist_object *intern;
if (zend_parse_parameters(ZEND_NUM_ARGS(), "zz", &zindex, &value) == FAILURE) {
return;
}
intern = Z_SPLDLLIST_P(getThis());
if (Z_TYPE_P(zindex) == IS_NULL) {
/* $obj[] = ... */
spl_ptr_lli... | 324,100,465,917,832,940,000,000,000,000,000,000,000 | None | null | [
"CWE-415"
] | CVE-2016-3132 | Double free vulnerability in the SplDoublyLinkedList::offsetSet function in ext/spl/spl_dllist.c in PHP 7.x before 7.0.6 allows remote attackers to execute arbitrary code via a crafted index. | https://nvd.nist.gov/vuln/detail/CVE-2016-3132 |
159,628 | php-src | 28a6ed9f9a36b9c517e4a8a429baf4dd382fc5d5 | https://github.com/php/php-src | http://github.com/php/php-src/commit/28a6ed9f9a36b9c517e4a8a429baf4dd382fc5d5?w=1 | Fix bug #71735: Double-free in SplDoublyLinkedList::offsetSet | 0 | SPL_METHOD(SplDoublyLinkedList, offsetSet)
{
zval *zindex, *value;
spl_dllist_object *intern;
if (zend_parse_parameters(ZEND_NUM_ARGS(), "zz", &zindex, &value) == FAILURE) {
return;
}
intern = Z_SPLDLLIST_P(getThis());
if (Z_TYPE_P(zindex) == IS_NULL) {
/* $obj[] = ... */
spl_ptr_lli... | 332,081,952,717,475,250,000,000,000,000,000,000,000 | None | null | [
"CWE-415"
] | CVE-2016-3132 | Double free vulnerability in the SplDoublyLinkedList::offsetSet function in ext/spl/spl_dllist.c in PHP 7.x before 7.0.6 allows remote attackers to execute arbitrary code via a crafted index. | https://nvd.nist.gov/vuln/detail/CVE-2016-3132 |
2,131 | krb5 | 93b4a6306a0026cf1cc31ac4bd8a49ba5d034ba7 | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/93b4a6306a0026cf1cc31ac4bd8a49ba5d034ba7 | Fix S4U2Self KDC crash when anon is restricted
In validate_as_request(), when enforcing restrict_anonymous_to_tgt,
use client.princ instead of request->client; the latter is NULL when
validating S4U2Self requests.
CVE-2016-3120:
In MIT krb5 1.9 and later, an authenticated attacker can cause krb5kdc
to dereference a ... | 1 | validate_as_request(kdc_realm_t *kdc_active_realm,
register krb5_kdc_req *request, krb5_db_entry client,
krb5_db_entry server, krb5_timestamp kdc_time,
const char **status, krb5_pa_data ***e_data)
{
int errcode;
krb5_error_code ret;
/*
* If a... | 67,017,454,586,486,290,000,000,000,000,000,000,000 | kdc_util.c | 132,323,104,047,921,250,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2016-3120 | The validate_as_request function in kdc_util.c in the Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.13.6 and 1.4.x before 1.14.3, when restrict_anonymous_to_tgt is enabled, uses an incorrect client data structure, which allows remote authenticated users to cause a denial of service (NULL pointer d... | https://nvd.nist.gov/vuln/detail/CVE-2016-3120 |
159,629 | krb5 | 93b4a6306a0026cf1cc31ac4bd8a49ba5d034ba7 | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/93b4a6306a0026cf1cc31ac4bd8a49ba5d034ba7 | Fix S4U2Self KDC crash when anon is restricted
In validate_as_request(), when enforcing restrict_anonymous_to_tgt,
use client.princ instead of request->client; the latter is NULL when
validating S4U2Self requests.
CVE-2016-3120:
In MIT krb5 1.9 and later, an authenticated attacker can cause krb5kdc
to dereference a ... | 0 | validate_as_request(kdc_realm_t *kdc_active_realm,
register krb5_kdc_req *request, krb5_db_entry client,
krb5_db_entry server, krb5_timestamp kdc_time,
const char **status, krb5_pa_data ***e_data)
{
int errcode;
krb5_error_code ret;
/*
* If a... | 136,032,537,230,883,080,000,000,000,000,000,000,000 | kdc_util.c | 172,188,382,554,751,230,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2016-3120 | The validate_as_request function in kdc_util.c in the Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.13.6 and 1.4.x before 1.14.3, when restrict_anonymous_to_tgt is enabled, uses an incorrect client data structure, which allows remote authenticated users to cause a denial of service (NULL pointer d... | https://nvd.nist.gov/vuln/detail/CVE-2016-3120 |
2,134 | libgd | 2bb97f407c1145c850416a3bfbcc8cf124e68a19 | https://github.com/libgd/libgd | https://github.com/libgd/libgd/commit/2bb97f407c1145c850416a3bfbcc8cf124e68a19 | gd2: handle corrupt images better (CVE-2016-3074)
Make sure we do some range checking on corrupted chunks.
Thanks to Hans Jerry Illikainen <hji@dyntopia.com> for indepth report
and reproducer information. Made for easy test case writing :). | 1 | _gd2GetHeader (gdIOCtxPtr in, int *sx, int *sy,
int *cs, int *vers, int *fmt, int *ncx, int *ncy,
t_chunk_info ** chunkIdx)
{
int i;
int ch;
char id[5];
t_chunk_info *cidx;
int sidx;
int nc;
GD2_DBG (printf ("Reading gd2 header info\n"));
for (i = 0; i < 4; i++) {
ch = gdGetC (... | 166,042,292,574,051,100,000,000,000,000,000,000,000 | None | null | [
"CWE-189"
] | CVE-2016-3074 | Integer signedness error in GD Graphics Library 2.1.1 (aka libgd or libgd2) allows remote attackers to cause a denial of service (crash) or potentially execute arbitrary code via crafted compressed gd2 data, which triggers a heap-based buffer overflow. | https://nvd.nist.gov/vuln/detail/CVE-2016-3074 |
159,631 | libgd | 2bb97f407c1145c850416a3bfbcc8cf124e68a19 | https://github.com/libgd/libgd | https://github.com/libgd/libgd/commit/2bb97f407c1145c850416a3bfbcc8cf124e68a19 | gd2: handle corrupt images better (CVE-2016-3074)
Make sure we do some range checking on corrupted chunks.
Thanks to Hans Jerry Illikainen <hji@dyntopia.com> for indepth report
and reproducer information. Made for easy test case writing :). | 0 | _gd2GetHeader (gdIOCtxPtr in, int *sx, int *sy,
int *cs, int *vers, int *fmt, int *ncx, int *ncy,
t_chunk_info ** chunkIdx)
{
int i;
int ch;
char id[5];
t_chunk_info *cidx;
int sidx;
int nc;
GD2_DBG (printf ("Reading gd2 header info\n"));
for (i = 0; i < 4; i++) {
ch = gdGetC (... | 63,300,892,053,731,820,000,000,000,000,000,000,000 | None | null | [
"CWE-189"
] | CVE-2016-3074 | Integer signedness error in GD Graphics Library 2.1.1 (aka libgd or libgd2) allows remote attackers to cause a denial of service (crash) or potentially execute arbitrary code via crafted compressed gd2 data, which triggers a heap-based buffer overflow. | https://nvd.nist.gov/vuln/detail/CVE-2016-3074 |
2,137 | FFmpeg | 689e59b7ffed34eba6159dcc78e87133862e3746 | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/689e59b7ffed34eba6159dcc78e87133862e3746 | mov: reset dref_count on realloc to keep values consistent.
This fixes a potential crash.
Signed-off-by: Michael Niedermayer <michaelni@gmx.at> | 1 | static int mov_read_dref(MOVContext *c, AVIOContext *pb, MOVAtom atom)
{
AVStream *st;
MOVStreamContext *sc;
int entries, i, j;
if (c->fc->nb_streams < 1)
return 0;
st = c->fc->streams[c->fc->nb_streams-1];
sc = st->priv_data;
avio_rb32(pb); // version + flags
entries = avio_rb... | 79,747,855,433,813,770,000,000,000,000,000,000,000 | mov.c | 89,945,014,034,723,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-3062 | The mov_read_dref function in libavformat/mov.c in Libav before 11.7 and FFmpeg before 0.11 allows remote attackers to cause a denial of service (memory corruption) or execute arbitrary code via the entries value in a dref box in an MP4 file. | https://nvd.nist.gov/vuln/detail/CVE-2016-3062 |
159,634 | FFmpeg | 689e59b7ffed34eba6159dcc78e87133862e3746 | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/689e59b7ffed34eba6159dcc78e87133862e3746 | mov: reset dref_count on realloc to keep values consistent.
This fixes a potential crash.
Signed-off-by: Michael Niedermayer <michaelni@gmx.at> | 0 | static int mov_read_dref(MOVContext *c, AVIOContext *pb, MOVAtom atom)
{
AVStream *st;
MOVStreamContext *sc;
int entries, i, j;
if (c->fc->nb_streams < 1)
return 0;
st = c->fc->streams[c->fc->nb_streams-1];
sc = st->priv_data;
avio_rb32(pb); // version + flags
entries = avio_rb... | 40,198,410,941,915,520,000,000,000,000,000,000,000 | mov.c | 196,923,887,100,272,520,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-3062 | The mov_read_dref function in libavformat/mov.c in Libav before 11.7 and FFmpeg before 0.11 allows remote attackers to cause a denial of service (memory corruption) or execute arbitrary code via the entries value in a dref box in an MP4 file. | https://nvd.nist.gov/vuln/detail/CVE-2016-3062 |
2,141 | linux | cac9b50b0d75a1d50d6c056ff65c005f3224c8e0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cac9b50b0d75a1d50d6c056ff65c005f3224c8e0 | USB: visor: fix null-deref at probe
Fix null-pointer dereference at probe should a (malicious) Treo device
lack the expected endpoints.
Specifically, the Treo port-setup hack was dereferencing the bulk-in and
interrupt-in urbs without first making sure they had been allocated by
core.
Fixes: 1da177e4c3f4 ("Linux-2.6... | 1 | static int treo_attach(struct usb_serial *serial)
{
struct usb_serial_port *swap_port;
/* Only do this endpoint hack for the Handspring devices with
* interrupt in endpoints, which for now are the Treo devices. */
if (!((le16_to_cpu(serial->dev->descriptor.idVendor)
== HANDSPRING_VENDOR_ID) ||
(le16_to_cp... | 198,842,744,337,888,960,000,000,000,000,000,000,000 | visor.c | 261,946,761,120,480,700,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-2782 | The treo_attach function in drivers/usb/serial/visor.c in the Linux kernel before 4.5 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 (1) bulk-in or (2) interrupt-in endpoint. | https://nvd.nist.gov/vuln/detail/CVE-2016-2782 |
159,638 | linux | cac9b50b0d75a1d50d6c056ff65c005f3224c8e0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cac9b50b0d75a1d50d6c056ff65c005f3224c8e0 | USB: visor: fix null-deref at probe
Fix null-pointer dereference at probe should a (malicious) Treo device
lack the expected endpoints.
Specifically, the Treo port-setup hack was dereferencing the bulk-in and
interrupt-in urbs without first making sure they had been allocated by
core.
Fixes: 1da177e4c3f4 ("Linux-2.6... | 0 | static int treo_attach(struct usb_serial *serial)
{
struct usb_serial_port *swap_port;
/* Only do this endpoint hack for the Handspring devices with
* interrupt in endpoints, which for now are the Treo devices. */
if (!((le16_to_cpu(serial->dev->descriptor.idVendor)
== HANDSPRING_VENDOR_ID) ||
(le16_to_cp... | 91,495,436,828,283,460,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-2016-2782 | The treo_attach function in drivers/usb/serial/visor.c in the Linux kernel before 4.5 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 (1) bulk-in or (2) interrupt-in endpoint. | https://nvd.nist.gov/vuln/detail/CVE-2016-2782 |
2,149 | linux | b5a663aa426f4884c71cd8580adae73f33570f0d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b5a663aa426f4884c71cd8580adae73f33570f0d | ALSA: timer: Harden slave timer list handling
A slave timer instance might be still accessible in a racy way while
operating the master instance as it lacks of locking. Since the
master operation is mostly protected with timer->lock, we should cope
with it while changing the slave instance, too. Also, some linked
li... | 1 | static int _snd_timer_stop(struct snd_timer_instance * timeri,
int keep_flag, int event)
{
struct snd_timer *timer;
unsigned long flags;
if (snd_BUG_ON(!timeri))
return -ENXIO;
if (timeri->flags & SNDRV_TIMER_IFLG_SLAVE) {
if (!keep_flag) {
spin_lock_irqsave(&slave_active_lock, flags);
timeri->... | 198,967,134,467,265,500,000,000,000,000,000,000,000 | timer.c | 233,862,501,943,978,640,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-2548 | sound/core/timer.c in the Linux kernel before 4.4.1 retains certain linked lists after a close or stop action, which allows local users to cause a denial of service (system crash) via a crafted ioctl call, related to the (1) snd_timer_close and (2) _snd_timer_stop functions. | https://nvd.nist.gov/vuln/detail/CVE-2016-2548 |
159,646 | linux | b5a663aa426f4884c71cd8580adae73f33570f0d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b5a663aa426f4884c71cd8580adae73f33570f0d | ALSA: timer: Harden slave timer list handling
A slave timer instance might be still accessible in a racy way while
operating the master instance as it lacks of locking. Since the
master operation is mostly protected with timer->lock, we should cope
with it while changing the slave instance, too. Also, some linked
li... | 0 | static int _snd_timer_stop(struct snd_timer_instance * timeri,
int keep_flag, int event)
{
struct snd_timer *timer;
unsigned long flags;
if (snd_BUG_ON(!timeri))
return -ENXIO;
if (timeri->flags & SNDRV_TIMER_IFLG_SLAVE) {
if (!keep_flag) {
spin_lock_irqsave(&slave_active_lock, flags);
timeri->... | 35,689,428,361,418,034,000,000,000,000,000,000,000 | timer.c | 247,006,264,354,514,070,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-2548 | sound/core/timer.c in the Linux kernel before 4.4.1 retains certain linked lists after a close or stop action, which allows local users to cause a denial of service (system crash) via a crafted ioctl call, related to the (1) snd_timer_close and (2) _snd_timer_stop functions. | https://nvd.nist.gov/vuln/detail/CVE-2016-2548 |
2,151 | linux | b5a663aa426f4884c71cd8580adae73f33570f0d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b5a663aa426f4884c71cd8580adae73f33570f0d | ALSA: timer: Harden slave timer list handling
A slave timer instance might be still accessible in a racy way while
operating the master instance as it lacks of locking. Since the
master operation is mostly protected with timer->lock, we should cope
with it while changing the slave instance, too. Also, some linked
li... | 1 | int snd_timer_close(struct snd_timer_instance *timeri)
{
struct snd_timer *timer = NULL;
struct snd_timer_instance *slave, *tmp;
if (snd_BUG_ON(!timeri))
return -ENXIO;
/* force to stop the timer */
snd_timer_stop(timeri);
if (timeri->flags & SNDRV_TIMER_IFLG_SLAVE) {
/* wait, until the active callback is ... | 191,662,303,613,238,740,000,000,000,000,000,000,000 | timer.c | 233,862,501,943,978,640,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-2548 | sound/core/timer.c in the Linux kernel before 4.4.1 retains certain linked lists after a close or stop action, which allows local users to cause a denial of service (system crash) via a crafted ioctl call, related to the (1) snd_timer_close and (2) _snd_timer_stop functions. | https://nvd.nist.gov/vuln/detail/CVE-2016-2548 |
159,647 | linux | b5a663aa426f4884c71cd8580adae73f33570f0d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b5a663aa426f4884c71cd8580adae73f33570f0d | ALSA: timer: Harden slave timer list handling
A slave timer instance might be still accessible in a racy way while
operating the master instance as it lacks of locking. Since the
master operation is mostly protected with timer->lock, we should cope
with it while changing the slave instance, too. Also, some linked
li... | 0 | int snd_timer_close(struct snd_timer_instance *timeri)
{
struct snd_timer *timer = NULL;
struct snd_timer_instance *slave, *tmp;
if (snd_BUG_ON(!timeri))
return -ENXIO;
/* force to stop the timer */
snd_timer_stop(timeri);
if (timeri->flags & SNDRV_TIMER_IFLG_SLAVE) {
/* wait, until the active callback is ... | 16,805,717,596,228,090,000,000,000,000,000,000,000 | timer.c | 247,006,264,354,514,070,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-2548 | sound/core/timer.c in the Linux kernel before 4.4.1 retains certain linked lists after a close or stop action, which allows local users to cause a denial of service (system crash) via a crafted ioctl call, related to the (1) snd_timer_close and (2) _snd_timer_stop functions. | https://nvd.nist.gov/vuln/detail/CVE-2016-2548 |
2,158 | linux | 3567eb6af614dac436c4b16a8d426f9faed639b3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/3567eb6af614dac436c4b16a8d426f9faed639b3 | ALSA: seq: Fix race at timer setup and close
ALSA sequencer code has an open race between the timer setup ioctl and
the close of the client. This was triggered by syzkaller fuzzer, and
a use-after-free was caught there as a result.
This patch papers over it by adding a proper queue->timer_mutex lock
around the timer... | 1 | static void queue_delete(struct snd_seq_queue *q)
{
/* stop and release the timer */
snd_seq_timer_stop(q->timer);
snd_seq_timer_close(q);
/* wait until access free */
snd_use_lock_sync(&q->use_lock);
/* release resources... */
snd_seq_prioq_delete(&q->tickq);
snd_seq_prioq_delete(&q->timeq);
snd_seq_t... | 178,529,605,273,024,480,000,000,000,000,000,000,000 | seq_queue.c | 75,888,079,069,082,210,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2016-2544 | Race condition in the queue_delete function in sound/core/seq/seq_queue.c in the Linux kernel before 4.4.1 allows local users to cause a denial of service (use-after-free and system crash) by making an ioctl call at a certain time. | https://nvd.nist.gov/vuln/detail/CVE-2016-2544 |
159,651 | linux | 3567eb6af614dac436c4b16a8d426f9faed639b3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/3567eb6af614dac436c4b16a8d426f9faed639b3 | ALSA: seq: Fix race at timer setup and close
ALSA sequencer code has an open race between the timer setup ioctl and
the close of the client. This was triggered by syzkaller fuzzer, and
a use-after-free was caught there as a result.
This patch papers over it by adding a proper queue->timer_mutex lock
around the timer... | 0 | static void queue_delete(struct snd_seq_queue *q)
{
/* stop and release the timer */
mutex_lock(&q->timer_mutex);
snd_seq_timer_stop(q->timer);
snd_seq_timer_close(q);
mutex_unlock(&q->timer_mutex);
/* wait until access free */
snd_use_lock_sync(&q->use_lock);
/* release resources... */
snd_seq_prioq_d... | 166,001,549,822,479,900,000,000,000,000,000,000,000 | seq_queue.c | 333,921,399,315,852,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2016-2544 | Race condition in the queue_delete function in sound/core/seq/seq_queue.c in the Linux kernel before 4.4.1 allows local users to cause a denial of service (use-after-free and system crash) by making an ioctl call at a certain time. | https://nvd.nist.gov/vuln/detail/CVE-2016-2544 |
2,159 | linux | 030e2c78d3a91dd0d27fef37e91950dde333eba1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/030e2c78d3a91dd0d27fef37e91950dde333eba1 | ALSA: seq: Fix missing NULL check at remove_events ioctl
snd_seq_ioctl_remove_events() calls snd_seq_fifo_clear()
unconditionally even if there is no FIFO assigned, and this leads to
an Oops due to NULL dereference. The fix is just to add a proper NULL
check.
Reported-by: Dmitry Vyukov <dvyukov@google.com>
Tested-by... | 1 | static int snd_seq_ioctl_remove_events(struct snd_seq_client *client,
void __user *arg)
{
struct snd_seq_remove_events info;
if (copy_from_user(&info, arg, sizeof(info)))
return -EFAULT;
/*
* Input mostly not implemented XXX.
*/
if (info.remove_mode & SNDRV_SEQ_REMOVE_INPUT) {
/*
* No restr... | 154,168,597,763,000,470,000,000,000,000,000,000,000 | None | null | [
"CWE-703"
] | CVE-2016-2543 | The snd_seq_ioctl_remove_events function in sound/core/seq/seq_clientmgr.c in the Linux kernel before 4.4.1 does not verify FIFO assignment before proceeding with FIFO clearing, which allows local users to cause a denial of service (NULL pointer dereference and OOPS) via a crafted ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2016-2543 |
159,652 | linux | 030e2c78d3a91dd0d27fef37e91950dde333eba1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/030e2c78d3a91dd0d27fef37e91950dde333eba1 | ALSA: seq: Fix missing NULL check at remove_events ioctl
snd_seq_ioctl_remove_events() calls snd_seq_fifo_clear()
unconditionally even if there is no FIFO assigned, and this leads to
an Oops due to NULL dereference. The fix is just to add a proper NULL
check.
Reported-by: Dmitry Vyukov <dvyukov@google.com>
Tested-by... | 0 | static int snd_seq_ioctl_remove_events(struct snd_seq_client *client,
void __user *arg)
{
struct snd_seq_remove_events info;
if (copy_from_user(&info, arg, sizeof(info)))
return -EFAULT;
/*
* Input mostly not implemented XXX.
*/
if (info.remove_mode & SNDRV_SEQ_REMOVE_INPUT) {
/*
* No restr... | 245,959,306,467,153,740,000,000,000,000,000,000,000 | None | null | [
"CWE-703"
] | CVE-2016-2543 | The snd_seq_ioctl_remove_events function in sound/core/seq/seq_clientmgr.c in the Linux kernel before 4.4.1 does not verify FIFO assignment before proceeding with FIFO clearing, which allows local users to cause a denial of service (NULL pointer dereference and OOPS) via a crafted ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2016-2543 |
2,160 | kamailio | f50c9c853e7809810099c970780c30b0765b0643 | https://github.com/kamailio/kamailio | https://github.com/kamailio/kamailio/commit/f50c9c853e7809810099c970780c30b0765b0643 | seas: safety check for target buffer size before copying message in encode_msg()
- avoid buffer overflow for large SIP messages
- reported by Stelios Tsampas | 1 | int encode_msg(struct sip_msg *msg,char *payload,int len)
{
int i,j,k,u,request;
unsigned short int h;
struct hdr_field* hf;
struct msg_start* ms;
struct sip_uri miuri;
char *myerror=NULL;
ptrdiff_t diff;
if(len < MAX_ENCODED_MSG + MAX_MESSAGE_LEN)
return -1;
if(parse_headers(msg,H... | 307,752,200,007,300,920,000,000,000,000,000,000,000 | encode_msg.c | 134,975,203,358,462,500,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-2385 | Heap-based buffer overflow in the encode_msg function in encode_msg.c in the SEAS module in Kamailio (formerly OpenSER and SER) before 4.3.5 allows remote attackers to cause a denial of service (memory corruption and process crash) or possibly execute arbitrary code via a large SIP packet. | https://nvd.nist.gov/vuln/detail/CVE-2016-2385 |
159,653 | kamailio | f50c9c853e7809810099c970780c30b0765b0643 | https://github.com/kamailio/kamailio | https://github.com/kamailio/kamailio/commit/f50c9c853e7809810099c970780c30b0765b0643 | seas: safety check for target buffer size before copying message in encode_msg()
- avoid buffer overflow for large SIP messages
- reported by Stelios Tsampas | 0 | int encode_msg(struct sip_msg *msg,char *payload,int len)
{
int i,j,k,u,request;
unsigned short int h;
struct hdr_field* hf;
struct msg_start* ms;
struct sip_uri miuri;
char *myerror=NULL;
ptrdiff_t diff;
if(len < MAX_ENCODED_MSG + MAX_MESSAGE_LEN)
return -1;
if(parse_headers(msg,... | 243,412,572,696,751,650,000,000,000,000,000,000,000 | encode_msg.c | 99,439,776,749,378,700,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-2385 | Heap-based buffer overflow in the encode_msg function in encode_msg.c in the SEAS module in Kamailio (formerly OpenSER and SER) before 4.3.5 allows remote attackers to cause a denial of service (memory corruption and process crash) or possibly execute arbitrary code via a large SIP packet. | https://nvd.nist.gov/vuln/detail/CVE-2016-2385 |
2,161 | linux | 07d86ca93db7e5cdf4743564d98292042ec21af7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/07d86ca93db7e5cdf4743564d98292042ec21af7 | ALSA: usb-audio: avoid freeing umidi object twice
The 'umidi' object will be free'd on the error path by snd_usbmidi_free()
when tearing down the rawmidi interface. So we shouldn't try to free it
in snd_usbmidi_create() after having registered the rawmidi interface.
Found by KASAN.
Signed-off-by: Andrey Konovalov <a... | 1 | int snd_usbmidi_create(struct snd_card *card,
struct usb_interface *iface,
struct list_head *midi_list,
const struct snd_usb_audio_quirk *quirk)
{
struct snd_usb_midi *umidi;
struct snd_usb_midi_endpoint_info endpoints[MIDI_MAX_ENDPOINTS];
int out_ports, in_ports;
int i, err;
umidi = kz... | 186,007,020,350,234,550,000,000,000,000,000,000,000 | midi.c | 58,837,838,038,525,350,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-2384 | Double free vulnerability in the snd_usbmidi_create function in sound/usb/midi.c in the Linux kernel before 4.5 allows physically proximate attackers to cause a denial of service (panic) or possibly have unspecified other impact via vectors involving an invalid USB descriptor. | https://nvd.nist.gov/vuln/detail/CVE-2016-2384 |
159,654 | linux | 07d86ca93db7e5cdf4743564d98292042ec21af7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/07d86ca93db7e5cdf4743564d98292042ec21af7 | ALSA: usb-audio: avoid freeing umidi object twice
The 'umidi' object will be free'd on the error path by snd_usbmidi_free()
when tearing down the rawmidi interface. So we shouldn't try to free it
in snd_usbmidi_create() after having registered the rawmidi interface.
Found by KASAN.
Signed-off-by: Andrey Konovalov <a... | 0 | int snd_usbmidi_create(struct snd_card *card,
struct usb_interface *iface,
struct list_head *midi_list,
const struct snd_usb_audio_quirk *quirk)
{
struct snd_usb_midi *umidi;
struct snd_usb_midi_endpoint_info endpoints[MIDI_MAX_ENDPOINTS];
int out_ports, in_ports;
int i, err;
umidi = kz... | 122,656,442,923,828,220,000,000,000,000,000,000,000 | midi.c | 262,686,818,783,103,940,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-2384 | Double free vulnerability in the snd_usbmidi_create function in sound/usb/midi.c in the Linux kernel before 4.5 allows physically proximate attackers to cause a denial of service (panic) or possibly have unspecified other impact via vectors involving an invalid USB descriptor. | https://nvd.nist.gov/vuln/detail/CVE-2016-2384 |
2,178 | git | 34fa79a6cde56d6d428ab0d3160cb094ebad3305 | https://github.com/git/git | https://github.com/git/git/commit/34fa79a6cde56d6d428ab0d3160cb094ebad3305 | prefer memcpy to strcpy
When we already know the length of a string (e.g., because
we just malloc'd to fit it), it's nicer to use memcpy than
strcpy, as it makes it more obvious that we are not going to
overflow the buffer (because the size we pass matches the
size in the allocation).
This also eliminates calls to st... | 1 | char *path_name(const struct name_path *path, const char *name)
{
const struct name_path *p;
char *n, *m;
int nlen = strlen(name);
int len = nlen + 1;
for (p = path; p; p = p->up) {
if (p->elem_len)
len += p->elem_len + 1;
}
n = xmalloc(len);
m = n + len - (nlen + 1);
strcpy(m, name);
for (p = path;... | 244,617,430,946,765,540,000,000,000,000,000,000,000 | revision.c | 139,882,901,556,130,910,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-2315 | revision.c in git before 2.7.4 uses an incorrect integer data type, which allows remote attackers to execute arbitrary code via a (1) long filename or (2) many nested trees, leading to a heap-based buffer overflow. | https://nvd.nist.gov/vuln/detail/CVE-2016-2315 |
159,670 | git | 34fa79a6cde56d6d428ab0d3160cb094ebad3305 | https://github.com/git/git | https://github.com/git/git/commit/34fa79a6cde56d6d428ab0d3160cb094ebad3305 | prefer memcpy to strcpy
When we already know the length of a string (e.g., because
we just malloc'd to fit it), it's nicer to use memcpy than
strcpy, as it makes it more obvious that we are not going to
overflow the buffer (because the size we pass matches the
size in the allocation).
This also eliminates calls to st... | 0 | char *path_name(const struct name_path *path, const char *name)
{
const struct name_path *p;
char *n, *m;
int nlen = strlen(name);
int len = nlen + 1;
for (p = path; p; p = p->up) {
if (p->elem_len)
len += p->elem_len + 1;
}
n = xmalloc(len);
m = n + len - (nlen + 1);
memcpy(m, name, nlen + 1);
for ... | 250,868,471,674,759,730,000,000,000,000,000,000,000 | revision.c | 72,196,619,765,747,870,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-2315 | revision.c in git before 2.7.4 uses an incorrect integer data type, which allows remote attackers to execute arbitrary code via a (1) long filename or (2) many nested trees, leading to a heap-based buffer overflow. | https://nvd.nist.gov/vuln/detail/CVE-2016-2315 |
2,179 | linux | 4ec0ef3a82125efc36173062a50624550a900ae0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ec0ef3a82125efc36173062a50624550a900ae0 | USB: iowarrior: fix oops with malicious USB descriptors
The iowarrior driver expects at least one valid endpoint. If given
malicious descriptors that specify 0 for the number of endpoints,
it will crash in the probe function. Ensure there is at least
one endpoint on the interface before using it.
The full report of... | 1 | static int iowarrior_probe(struct usb_interface *interface,
const struct usb_device_id *id)
{
struct usb_device *udev = interface_to_usbdev(interface);
struct iowarrior *dev = NULL;
struct usb_host_interface *iface_desc;
struct usb_endpoint_descriptor *endpoint;
int i;
int retval = -ENOMEM;
/* allocate me... | 184,277,450,702,665,200,000,000,000,000,000,000,000 | iowarrior.c | 43,223,000,391,687,380,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-2188 | The iowarrior_probe function in drivers/usb/misc/iowarrior.c in the Linux kernel before 4.5.1 allows physically proximate attackers to cause a denial of service (NULL pointer dereference and system crash) via a crafted endpoints value in a USB device descriptor. | https://nvd.nist.gov/vuln/detail/CVE-2016-2188 |
159,671 | linux | 4ec0ef3a82125efc36173062a50624550a900ae0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ec0ef3a82125efc36173062a50624550a900ae0 | USB: iowarrior: fix oops with malicious USB descriptors
The iowarrior driver expects at least one valid endpoint. If given
malicious descriptors that specify 0 for the number of endpoints,
it will crash in the probe function. Ensure there is at least
one endpoint on the interface before using it.
The full report of... | 0 | static int iowarrior_probe(struct usb_interface *interface,
const struct usb_device_id *id)
{
struct usb_device *udev = interface_to_usbdev(interface);
struct iowarrior *dev = NULL;
struct usb_host_interface *iface_desc;
struct usb_endpoint_descriptor *endpoint;
int i;
int retval = -ENOMEM;
/* allocate me... | 130,849,813,135,000,820,000,000,000,000,000,000,000 | iowarrior.c | 320,424,186,194,007,860,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-2188 | The iowarrior_probe function in drivers/usb/misc/iowarrior.c in the Linux kernel before 4.5.1 allows physically proximate attackers to cause a denial of service (NULL pointer dereference and system crash) via a crafted endpoints value in a USB device descriptor. | https://nvd.nist.gov/vuln/detail/CVE-2016-2188 |
2,180 | linux | 162f98dea487206d9ab79fc12ed64700667a894d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/162f98dea487206d9ab79fc12ed64700667a894d | Input: gtco - fix crash on detecting device without endpoints
The gtco driver expects at least one valid endpoint. If given malicious
descriptors that specify 0 for the number of endpoints, it will crash in
the probe function. Ensure there is at least one endpoint on the interface
before using it.
Also let's fix a mi... | 1 | static int gtco_probe(struct usb_interface *usbinterface,
const struct usb_device_id *id)
{
struct gtco *gtco;
struct input_dev *input_dev;
struct hid_descriptor *hid_desc;
char *report;
int result = 0, retry;
int error;
struct usb_endpoint_d... | 91,802,595,213,563,340,000,000,000,000,000,000,000 | gtco.c | 272,997,561,883,214,830,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-2187 | The gtco_probe function in drivers/input/tablet/gtco.c in the Linux kernel through 4.5.2 allows physically proximate attackers to cause a denial of service (NULL pointer dereference and system crash) via a crafted endpoints value in a USB device descriptor. | https://nvd.nist.gov/vuln/detail/CVE-2016-2187 |
159,672 | linux | 162f98dea487206d9ab79fc12ed64700667a894d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/162f98dea487206d9ab79fc12ed64700667a894d | Input: gtco - fix crash on detecting device without endpoints
The gtco driver expects at least one valid endpoint. If given malicious
descriptors that specify 0 for the number of endpoints, it will crash in
the probe function. Ensure there is at least one endpoint on the interface
before using it.
Also let's fix a mi... | 0 | static int gtco_probe(struct usb_interface *usbinterface,
const struct usb_device_id *id)
{
struct gtco *gtco;
struct input_dev *input_dev;
struct hid_descriptor *hid_desc;
char *report;
int result = 0, retry;
int error;
struct usb_endpoint_d... | 268,170,377,540,835,600,000,000,000,000,000,000,000 | gtco.c | 60,041,017,887,989,290,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-2187 | The gtco_probe function in drivers/input/tablet/gtco.c in the Linux kernel through 4.5.2 allows physically proximate attackers to cause a denial of service (NULL pointer dereference and system crash) via a crafted endpoints value in a USB device descriptor. | https://nvd.nist.gov/vuln/detail/CVE-2016-2187 |
2,181 | linux | 9c6ba456711687b794dcf285856fc14e2c76074f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9c6ba456711687b794dcf285856fc14e2c76074f | Input: powermate - fix oops with malicious USB descriptors
The powermate driver expects at least one valid USB endpoint in its
probe function. If given malicious descriptors that specify 0 for
the number of endpoints, it will crash. Validate the number of
endpoints on the interface before using them.
The full repor... | 1 | static int powermate_probe(struct usb_interface *intf, const struct usb_device_id *id)
{
struct usb_device *udev = interface_to_usbdev (intf);
struct usb_host_interface *interface;
struct usb_endpoint_descriptor *endpoint;
struct powermate_device *pm;
struct input_dev *input_dev;
int pipe, maxp;
int error = -EN... | 222,563,563,219,301,300,000,000,000,000,000,000,000 | powermate.c | 76,926,132,104,944,360,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-2186 | The powermate_probe function in drivers/input/misc/powermate.c in the Linux kernel before 4.5.1 allows physically proximate attackers to cause a denial of service (NULL pointer dereference and system crash) via a crafted endpoints value in a USB device descriptor. | https://nvd.nist.gov/vuln/detail/CVE-2016-2186 |
159,673 | linux | 9c6ba456711687b794dcf285856fc14e2c76074f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9c6ba456711687b794dcf285856fc14e2c76074f | Input: powermate - fix oops with malicious USB descriptors
The powermate driver expects at least one valid USB endpoint in its
probe function. If given malicious descriptors that specify 0 for
the number of endpoints, it will crash. Validate the number of
endpoints on the interface before using them.
The full repor... | 0 | static int powermate_probe(struct usb_interface *intf, const struct usb_device_id *id)
{
struct usb_device *udev = interface_to_usbdev (intf);
struct usb_host_interface *interface;
struct usb_endpoint_descriptor *endpoint;
struct powermate_device *pm;
struct input_dev *input_dev;
int pipe, maxp;
int error = -EN... | 109,757,361,103,811,190,000,000,000,000,000,000,000 | powermate.c | 73,799,594,822,362,585,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-2186 | The powermate_probe function in drivers/input/misc/powermate.c in the Linux kernel before 4.5.1 allows physically proximate attackers to cause a denial of service (NULL pointer dereference and system crash) via a crafted endpoints value in a USB device descriptor. | https://nvd.nist.gov/vuln/detail/CVE-2016-2186 |
2,182 | linux | 950336ba3e4a1ffd2ca60d29f6ef386dd2c7351d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/950336ba3e4a1ffd2ca60d29f6ef386dd2c7351d | Input: ati_remote2 - fix crashes on detecting device with invalid descriptor
The ati_remote2 driver expects at least two interfaces with one
endpoint each. If given malicious descriptor that specify one
interface or no endpoints, it will crash in the probe function.
Ensure there is at least two interfaces and one endp... | 1 | static int ati_remote2_probe(struct usb_interface *interface, const struct usb_device_id *id)
{
struct usb_device *udev = interface_to_usbdev(interface);
struct usb_host_interface *alt = interface->cur_altsetting;
struct ati_remote2 *ar2;
int r;
if (alt->desc.bInterfaceNumber)
return -ENODEV;
ar2 = kzalloc(si... | 67,491,629,253,766,480,000,000,000,000,000,000,000 | ati_remote2.c | 263,372,229,415,855,000,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-2185 | The ati_remote2_probe function in drivers/input/misc/ati_remote2.c in the Linux kernel before 4.5.1 allows physically proximate attackers to cause a denial of service (NULL pointer dereference and system crash) via a crafted endpoints value in a USB device descriptor. | https://nvd.nist.gov/vuln/detail/CVE-2016-2185 |
159,674 | linux | 950336ba3e4a1ffd2ca60d29f6ef386dd2c7351d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/950336ba3e4a1ffd2ca60d29f6ef386dd2c7351d | Input: ati_remote2 - fix crashes on detecting device with invalid descriptor
The ati_remote2 driver expects at least two interfaces with one
endpoint each. If given malicious descriptor that specify one
interface or no endpoints, it will crash in the probe function.
Ensure there is at least two interfaces and one endp... | 0 | static int ati_remote2_probe(struct usb_interface *interface, const struct usb_device_id *id)
{
struct usb_device *udev = interface_to_usbdev(interface);
struct usb_host_interface *alt = interface->cur_altsetting;
struct ati_remote2 *ar2;
int r;
if (alt->desc.bInterfaceNumber)
return -ENODEV;
ar2 = kzalloc(si... | 251,002,752,843,474,100,000,000,000,000,000,000,000 | ati_remote2.c | 140,547,979,155,858,030,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-2185 | The ati_remote2_probe function in drivers/input/misc/ati_remote2.c in the Linux kernel before 4.5.1 allows physically proximate attackers to cause a denial of service (NULL pointer dereference and system crash) via a crafted endpoints value in a USB device descriptor. | https://nvd.nist.gov/vuln/detail/CVE-2016-2185 |
2,184 | linux | f43bfaeddc79effbf3d0fcb53ca477cca66f3db8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f43bfaeddc79effbf3d0fcb53ca477cca66f3db8 | atl2: Disable unimplemented scatter/gather feature
atl2 includes NETIF_F_SG in hw_features even though it has no support
for non-linear skbs. This bug was originally harmless since the
driver does not claim to implement checksum offload and that used to
be a requirement for SG.
Now that SG and checksum offload are i... | 1 | static int atl2_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
{
struct net_device *netdev;
struct atl2_adapter *adapter;
static int cards_found;
unsigned long mmio_start;
int mmio_len;
int err;
cards_found = 0;
err = pci_enable_device(pdev);
if (err)
return err;
/*
* atl2 is a shared-hig... | 15,763,019,659,237,995,000,000,000,000,000,000,000 | atl2.c | 62,900,487,325,653,490,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2016-2117 | The atl2_probe function in drivers/net/ethernet/atheros/atlx/atl2.c in the Linux kernel through 4.5.2 incorrectly enables scatter/gather I/O, which allows remote attackers to obtain sensitive information from kernel memory by reading packet data. | https://nvd.nist.gov/vuln/detail/CVE-2016-2117 |
159,676 | linux | f43bfaeddc79effbf3d0fcb53ca477cca66f3db8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f43bfaeddc79effbf3d0fcb53ca477cca66f3db8 | atl2: Disable unimplemented scatter/gather feature
atl2 includes NETIF_F_SG in hw_features even though it has no support
for non-linear skbs. This bug was originally harmless since the
driver does not claim to implement checksum offload and that used to
be a requirement for SG.
Now that SG and checksum offload are i... | 0 | static int atl2_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
{
struct net_device *netdev;
struct atl2_adapter *adapter;
static int cards_found;
unsigned long mmio_start;
int mmio_len;
int err;
cards_found = 0;
err = pci_enable_device(pdev);
if (err)
return err;
/*
* atl2 is a shared-hig... | 199,122,215,362,073,750,000,000,000,000,000,000,000 | atl2.c | 188,519,427,135,697,900,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2016-2117 | The atl2_probe function in drivers/net/ethernet/atheros/atlx/atl2.c in the Linux kernel through 4.5.2 incorrectly enables scatter/gather I/O, which allows remote attackers to obtain sensitive information from kernel memory by reading packet data. | https://nvd.nist.gov/vuln/detail/CVE-2016-2117 |
2,185 | linux | 613317bd212c585c20796c10afe5daaa95d4b0a1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/613317bd212c585c20796c10afe5daaa95d4b0a1 | EVM: Use crypto_memneq() for digest comparisons
This patch fixes vulnerability CVE-2016-2085. The problem exists
because the vm_verify_hmac() function includes a use of memcmp().
Unfortunately, this allows timing side channel attacks; specifically
a MAC forgery complexity drop from 2^128 to 2^12. This patch changes
... | 1 | static enum integrity_status evm_verify_hmac(struct dentry *dentry,
const char *xattr_name,
char *xattr_value,
size_t xattr_value_len,
struct integrity_iint_cache *iint)
{
struct evm_ima_xattr_data *xattr_data = NULL;
struct evm_ima_xattr_data calc;
enum integrity_status evm_s... | 88,333,432,303,897,410,000,000,000,000,000,000,000 | evm_main.c | 81,031,715,794,005,370,000,000,000,000,000,000,000 | [
"CWE-19"
] | CVE-2016-2085 | The evm_verify_hmac function in security/integrity/evm/evm_main.c in the Linux kernel before 4.5 does not properly copy data, which makes it easier for local users to forge MAC values via a timing side-channel attack. | https://nvd.nist.gov/vuln/detail/CVE-2016-2085 |
159,677 | linux | 613317bd212c585c20796c10afe5daaa95d4b0a1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/613317bd212c585c20796c10afe5daaa95d4b0a1 | EVM: Use crypto_memneq() for digest comparisons
This patch fixes vulnerability CVE-2016-2085. The problem exists
because the vm_verify_hmac() function includes a use of memcmp().
Unfortunately, this allows timing side channel attacks; specifically
a MAC forgery complexity drop from 2^128 to 2^12. This patch changes
... | 0 | static enum integrity_status evm_verify_hmac(struct dentry *dentry,
const char *xattr_name,
char *xattr_value,
size_t xattr_value_len,
struct integrity_iint_cache *iint)
{
struct evm_ima_xattr_data *xattr_data = NULL;
struct evm_ima_xattr_data calc;
enum integrity_status evm_s... | 278,529,231,907,618,860,000,000,000,000,000,000,000 | evm_main.c | 225,556,217,404,410,230,000,000,000,000,000,000,000 | [
"CWE-19"
] | CVE-2016-2085 | The evm_verify_hmac function in security/integrity/evm/evm_main.c in the Linux kernel before 4.5 does not properly copy data, which makes it easier for local users to forge MAC values via a timing side-channel attack. | https://nvd.nist.gov/vuln/detail/CVE-2016-2085 |
2,186 | linux | 8b8a321ff72c785ed5e8b4cf6eda20b35d427390 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8b8a321ff72c785ed5e8b4cf6eda20b35d427390 | tcp: fix zero cwnd in tcp_cwnd_reduction
Patch 3759824da87b ("tcp: PRR uses CRB mode by default and SS mode
conditionally") introduced a bug that cwnd may become 0 when both
inflight and sndcnt are 0 (cwnd = inflight + sndcnt). This may lead
to a div-by-zero if the connection starts another cwnd reduction
phase by set... | 1 | static void tcp_cwnd_reduction(struct sock *sk, const int prior_unsacked,
int fast_rexmit, int flag)
{
struct tcp_sock *tp = tcp_sk(sk);
int sndcnt = 0;
int delta = tp->snd_ssthresh - tcp_packets_in_flight(tp);
int newly_acked_sacked = prior_unsacked -
(tp->packets_out - tp->sacked_out);
tp->pr... | 136,149,861,517,984,150,000,000,000,000,000,000,000 | tcp_input.c | 150,702,089,358,866,060,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2016-2070 | The tcp_cwnd_reduction function in net/ipv4/tcp_input.c in the Linux kernel before 4.3.5 allows remote attackers to cause a denial of service (divide-by-zero error and system crash) via crafted TCP traffic. | https://nvd.nist.gov/vuln/detail/CVE-2016-2070 |
159,678 | linux | 8b8a321ff72c785ed5e8b4cf6eda20b35d427390 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8b8a321ff72c785ed5e8b4cf6eda20b35d427390 | tcp: fix zero cwnd in tcp_cwnd_reduction
Patch 3759824da87b ("tcp: PRR uses CRB mode by default and SS mode
conditionally") introduced a bug that cwnd may become 0 when both
inflight and sndcnt are 0 (cwnd = inflight + sndcnt). This may lead
to a div-by-zero if the connection starts another cwnd reduction
phase by set... | 0 | static void tcp_cwnd_reduction(struct sock *sk, const int prior_unsacked,
int fast_rexmit, int flag)
{
struct tcp_sock *tp = tcp_sk(sk);
int sndcnt = 0;
int delta = tp->snd_ssthresh - tcp_packets_in_flight(tp);
int newly_acked_sacked = prior_unsacked -
(tp->packets_out - tp->sacked_out);
if (new... | 312,634,999,703,865,660,000,000,000,000,000,000,000 | tcp_input.c | 217,590,060,409,483,670,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2016-2070 | The tcp_cwnd_reduction function in net/ipv4/tcp_input.c in the Linux kernel before 4.3.5 allows remote attackers to cause a denial of service (divide-by-zero error and system crash) via crafted TCP traffic. | https://nvd.nist.gov/vuln/detail/CVE-2016-2070 |
2,190 | linux | 0d62e9dd6da45bbf0f33a8617afc5fe774c8f45f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0d62e9dd6da45bbf0f33a8617afc5fe774c8f45f | ASN.1: Fix non-match detection failure on data overrun
If the ASN.1 decoder is asked to parse a sequence of objects, non-optional
matches get skipped if there's no more data to be had rather than a
data-overrun error being reported.
This is due to the code segment that decides whether to skip optional
matches (ie. ma... | 1 | int asn1_ber_decoder(const struct asn1_decoder *decoder,
void *context,
const unsigned char *data,
size_t datalen)
{
const unsigned char *machine = decoder->machine;
const asn1_action_t *actions = decoder->actions;
size_t machlen = decoder->machlen;
enum asn1_opcode op;
unsigned char tag = 0, ... | 281,485,108,536,962,730,000,000,000,000,000,000,000 | asn1_decoder.c | 60,105,720,755,512,370,000,000,000,000,000,000,000 | [
"CWE-310"
] | CVE-2016-2053 | The asn1_ber_decoder function in lib/asn1_decoder.c in the Linux kernel before 4.3 allows attackers to cause a denial of service (panic) via an ASN.1 BER file that lacks a public key, leading to mishandling by the public_key_verify_signature function in crypto/asymmetric_keys/public_key.c. | https://nvd.nist.gov/vuln/detail/CVE-2016-2053 |
159,682 | linux | 0d62e9dd6da45bbf0f33a8617afc5fe774c8f45f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0d62e9dd6da45bbf0f33a8617afc5fe774c8f45f | ASN.1: Fix non-match detection failure on data overrun
If the ASN.1 decoder is asked to parse a sequence of objects, non-optional
matches get skipped if there's no more data to be had rather than a
data-overrun error being reported.
This is due to the code segment that decides whether to skip optional
matches (ie. ma... | 0 | int asn1_ber_decoder(const struct asn1_decoder *decoder,
void *context,
const unsigned char *data,
size_t datalen)
{
const unsigned char *machine = decoder->machine;
const asn1_action_t *actions = decoder->actions;
size_t machlen = decoder->machlen;
enum asn1_opcode op;
unsigned char tag = 0, ... | 167,878,700,181,200,660,000,000,000,000,000,000,000 | asn1_decoder.c | 203,504,448,955,945,940,000,000,000,000,000,000,000 | [
"CWE-310"
] | CVE-2016-2053 | The asn1_ber_decoder function in lib/asn1_decoder.c in the Linux kernel before 4.3 allows attackers to cause a denial of service (panic) via an ASN.1 BER file that lacks a public key, leading to mishandling by the public_key_verify_signature function in crypto/asymmetric_keys/public_key.c. | https://nvd.nist.gov/vuln/detail/CVE-2016-2053 |
2,195 | linux | 999653786df6954a31044528ac3f7a5dadca08f4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/999653786df6954a31044528ac3f7a5dadca08f4 | nfsd: check permissions when setting ACLs
Use set_posix_acl, which includes proper permission checks, instead of
calling ->set_acl directly. Without this anyone may be able to grant
themselves permissions to a file by setting the ACL.
Lock the inode to make the new checks atomic with respect to set_acl.
(Also, nfsd ... | 1 | static __be32 nfsacld_proc_setacl(struct svc_rqst * rqstp,
struct nfsd3_setaclargs *argp,
struct nfsd_attrstat *resp)
{
struct inode *inode;
svc_fh *fh;
__be32 nfserr = 0;
int error;
dprintk("nfsd: SETACL(2acl) %s\n", SVCFH_fmt(&argp->fh));
fh = fh_copy(&resp->fh, &argp->fh);
nfserr = fh_verify(rqstp, &r... | 273,153,740,180,211,870,000,000,000,000,000,000,000 | nfs2acl.c | 71,480,567,602,086,585,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2016-1237 | nfsd in the Linux kernel through 4.6.3 allows local users to bypass intended file-permission restrictions by setting a POSIX ACL, related to nfs2acl.c, nfs3acl.c, and nfs4acl.c. | https://nvd.nist.gov/vuln/detail/CVE-2016-1237 |
159,686 | linux | 999653786df6954a31044528ac3f7a5dadca08f4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/999653786df6954a31044528ac3f7a5dadca08f4 | nfsd: check permissions when setting ACLs
Use set_posix_acl, which includes proper permission checks, instead of
calling ->set_acl directly. Without this anyone may be able to grant
themselves permissions to a file by setting the ACL.
Lock the inode to make the new checks atomic with respect to set_acl.
(Also, nfsd ... | 0 | static __be32 nfsacld_proc_setacl(struct svc_rqst * rqstp,
struct nfsd3_setaclargs *argp,
struct nfsd_attrstat *resp)
{
struct inode *inode;
svc_fh *fh;
__be32 nfserr = 0;
int error;
dprintk("nfsd: SETACL(2acl) %s\n", SVCFH_fmt(&argp->fh));
fh = fh_copy(&resp->fh, &argp->fh);
nfserr = fh_verify(rqstp, &r... | 91,992,294,699,831,350,000,000,000,000,000,000,000 | nfs2acl.c | 33,196,919,084,196,936,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2016-1237 | nfsd in the Linux kernel through 4.6.3 allows local users to bypass intended file-permission restrictions by setting a POSIX ACL, related to nfs2acl.c, nfs3acl.c, and nfs4acl.c. | https://nvd.nist.gov/vuln/detail/CVE-2016-1237 |
2,196 | linux | 999653786df6954a31044528ac3f7a5dadca08f4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/999653786df6954a31044528ac3f7a5dadca08f4 | nfsd: check permissions when setting ACLs
Use set_posix_acl, which includes proper permission checks, instead of
calling ->set_acl directly. Without this anyone may be able to grant
themselves permissions to a file by setting the ACL.
Lock the inode to make the new checks atomic with respect to set_acl.
(Also, nfsd ... | 1 | static __be32 nfsd3_proc_setacl(struct svc_rqst * rqstp,
struct nfsd3_setaclargs *argp,
struct nfsd3_attrstat *resp)
{
struct inode *inode;
svc_fh *fh;
__be32 nfserr = 0;
int error;
fh = fh_copy(&resp->fh, &argp->fh);
nfserr = fh_verify(rqstp, &resp->fh, 0, NFSD_MAY_SATTR);
if (nfserr)
goto out;
inod... | 90,832,810,491,214,460,000,000,000,000,000,000,000 | nfs3acl.c | 39,223,685,366,412,307,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2016-1237 | nfsd in the Linux kernel through 4.6.3 allows local users to bypass intended file-permission restrictions by setting a POSIX ACL, related to nfs2acl.c, nfs3acl.c, and nfs4acl.c. | https://nvd.nist.gov/vuln/detail/CVE-2016-1237 |
159,687 | linux | 999653786df6954a31044528ac3f7a5dadca08f4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/999653786df6954a31044528ac3f7a5dadca08f4 | nfsd: check permissions when setting ACLs
Use set_posix_acl, which includes proper permission checks, instead of
calling ->set_acl directly. Without this anyone may be able to grant
themselves permissions to a file by setting the ACL.
Lock the inode to make the new checks atomic with respect to set_acl.
(Also, nfsd ... | 0 | static __be32 nfsd3_proc_setacl(struct svc_rqst * rqstp,
struct nfsd3_setaclargs *argp,
struct nfsd3_attrstat *resp)
{
struct inode *inode;
svc_fh *fh;
__be32 nfserr = 0;
int error;
fh = fh_copy(&resp->fh, &argp->fh);
nfserr = fh_verify(rqstp, &resp->fh, 0, NFSD_MAY_SATTR);
if (nfserr)
goto out;
inod... | 193,216,416,307,438,000,000,000,000,000,000,000,000 | nfs3acl.c | 141,049,602,978,980,410,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2016-1237 | nfsd in the Linux kernel through 4.6.3 allows local users to bypass intended file-permission restrictions by setting a POSIX ACL, related to nfs2acl.c, nfs3acl.c, and nfs4acl.c. | https://nvd.nist.gov/vuln/detail/CVE-2016-1237 |
2,197 | linux | 999653786df6954a31044528ac3f7a5dadca08f4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/999653786df6954a31044528ac3f7a5dadca08f4 | nfsd: check permissions when setting ACLs
Use set_posix_acl, which includes proper permission checks, instead of
calling ->set_acl directly. Without this anyone may be able to grant
themselves permissions to a file by setting the ACL.
Lock the inode to make the new checks atomic with respect to set_acl.
(Also, nfsd ... | 1 | nfsd4_set_nfs4_acl(struct svc_rqst *rqstp, struct svc_fh *fhp,
struct nfs4_acl *acl)
{
__be32 error;
int host_error;
struct dentry *dentry;
struct inode *inode;
struct posix_acl *pacl = NULL, *dpacl = NULL;
unsigned int flags = 0;
/* Get inode */
error = fh_verify(rqstp, fhp, 0, NFSD_MAY_SATTR);
if (error)
... | 214,645,545,890,968,060,000,000,000,000,000,000,000 | nfs4acl.c | 268,799,433,190,121,900,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2016-1237 | nfsd in the Linux kernel through 4.6.3 allows local users to bypass intended file-permission restrictions by setting a POSIX ACL, related to nfs2acl.c, nfs3acl.c, and nfs4acl.c. | https://nvd.nist.gov/vuln/detail/CVE-2016-1237 |
159,688 | linux | 999653786df6954a31044528ac3f7a5dadca08f4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/999653786df6954a31044528ac3f7a5dadca08f4 | nfsd: check permissions when setting ACLs
Use set_posix_acl, which includes proper permission checks, instead of
calling ->set_acl directly. Without this anyone may be able to grant
themselves permissions to a file by setting the ACL.
Lock the inode to make the new checks atomic with respect to set_acl.
(Also, nfsd ... | 0 | nfsd4_set_nfs4_acl(struct svc_rqst *rqstp, struct svc_fh *fhp,
struct nfs4_acl *acl)
{
__be32 error;
int host_error;
struct dentry *dentry;
struct inode *inode;
struct posix_acl *pacl = NULL, *dpacl = NULL;
unsigned int flags = 0;
/* Get inode */
error = fh_verify(rqstp, fhp, 0, NFSD_MAY_SATTR);
if (error)
... | 89,413,195,335,990,630,000,000,000,000,000,000,000 | nfs4acl.c | 75,939,589,835,473,650,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2016-1237 | nfsd in the Linux kernel through 4.6.3 allows local users to bypass intended file-permission restrictions by setting a POSIX ACL, related to nfs2acl.c, nfs3acl.c, and nfs4acl.c. | https://nvd.nist.gov/vuln/detail/CVE-2016-1237 |
2,198 | linux | ab676b7d6fbf4b294bf198fb27ade5b0e865c7ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ab676b7d6fbf4b294bf198fb27ade5b0e865c7ce | pagemap: do not leak physical addresses to non-privileged userspace
As pointed by recent post[1] on exploiting DRAM physical imperfection,
/proc/PID/pagemap exposes sensitive information which can be used to do
attacks.
This disallows anybody without CAP_SYS_ADMIN to read the pagemap.
[1] http://googleprojectzero.bl... | 1 | static int pagemap_open(struct inode *inode, struct file *file)
{
pr_warn_once("Bits 55-60 of /proc/PID/pagemap entries are about "
"to stop being page-shift some time soon. See the "
"linux/Documentation/vm/pagemap.txt for details.\n");
return 0;
}
| 103,258,194,490,197,500,000,000,000,000,000,000,000 | task_mmu.c | 251,899,587,674,851,180,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2016-0823 | The pagemap_open function in fs/proc/task_mmu.c in the Linux kernel before 3.19.3, as used in Android 6.0.1 before 2016-03-01, allows local users to obtain sensitive physical-address information by reading a pagemap file, aka Android internal bug 25739721. | https://nvd.nist.gov/vuln/detail/CVE-2016-0823 |
159,689 | linux | ab676b7d6fbf4b294bf198fb27ade5b0e865c7ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ab676b7d6fbf4b294bf198fb27ade5b0e865c7ce | pagemap: do not leak physical addresses to non-privileged userspace
As pointed by recent post[1] on exploiting DRAM physical imperfection,
/proc/PID/pagemap exposes sensitive information which can be used to do
attacks.
This disallows anybody without CAP_SYS_ADMIN to read the pagemap.
[1] http://googleprojectzero.bl... | 0 | static int pagemap_open(struct inode *inode, struct file *file)
{
/* do not disclose physical addresses: attack vector */
if (!capable(CAP_SYS_ADMIN))
return -EPERM;
pr_warn_once("Bits 55-60 of /proc/PID/pagemap entries are about "
"to stop being page-shift some time soon. See the "
"linux/Documentation... | 96,527,853,225,163,960,000,000,000,000,000,000,000 | task_mmu.c | 92,412,772,823,384,010,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2016-0823 | The pagemap_open function in fs/proc/task_mmu.c in the Linux kernel before 3.19.3, as used in Android 6.0.1 before 2016-03-01, allows local users to obtain sensitive physical-address information by reading a pagemap file, aka Android internal bug 25739721. | https://nvd.nist.gov/vuln/detail/CVE-2016-0823 |
2,199 | linux | 23567fd052a9abb6d67fe8e7a9ccdd9800a540f2 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/23567fd052a9abb6d67fe8e7a9ccdd9800a540f2 | KEYS: Fix keyring ref leak in join_session_keyring()
This fixes CVE-2016-0728.
If a thread is asked to join as a session keyring the keyring that's already
set as its session, we leak a keyring reference.
This can be tested with the following program:
#include <stddef.h>
#include <stdio.h>
#include <sys/types.h>... | 1 | long join_session_keyring(const char *name)
{
const struct cred *old;
struct cred *new;
struct key *keyring;
long ret, serial;
new = prepare_creds();
if (!new)
return -ENOMEM;
old = current_cred();
/* if no name is provided, install an anonymous keyring */
if (!name) {
ret = install_session_keyring_to_cr... | 40,169,950,584,792,017,000,000,000,000,000,000,000 | process_keys.c | 217,210,212,436,007,030,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-0728 | The join_session_keyring function in security/keys/process_keys.c in the Linux kernel before 4.4.1 mishandles object references in a certain error case, which allows local users to gain privileges or cause a denial of service (integer overflow and use-after-free) via crafted keyctl commands. | https://nvd.nist.gov/vuln/detail/CVE-2016-0728 |
159,690 | linux | 23567fd052a9abb6d67fe8e7a9ccdd9800a540f2 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/23567fd052a9abb6d67fe8e7a9ccdd9800a540f2 | KEYS: Fix keyring ref leak in join_session_keyring()
This fixes CVE-2016-0728.
If a thread is asked to join as a session keyring the keyring that's already
set as its session, we leak a keyring reference.
This can be tested with the following program:
#include <stddef.h>
#include <stdio.h>
#include <sys/types.h>... | 0 | long join_session_keyring(const char *name)
{
const struct cred *old;
struct cred *new;
struct key *keyring;
long ret, serial;
new = prepare_creds();
if (!new)
return -ENOMEM;
old = current_cred();
/* if no name is provided, install an anonymous keyring */
if (!name) {
ret = install_session_keyring_to_cr... | 121,494,217,265,655,820,000,000,000,000,000,000,000 | process_keys.c | 65,965,327,138,857,070,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-0728 | The join_session_keyring function in security/keys/process_keys.c in the Linux kernel before 4.4.1 mishandles object references in a certain error case, which allows local users to gain privileges or cause a denial of service (integer overflow and use-after-free) via crafted keyctl commands. | https://nvd.nist.gov/vuln/detail/CVE-2016-0728 |
2,204 | linux | 76cc404bfdc0d419c720de4daaf2584542734f42 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/76cc404bfdc0d419c720de4daaf2584542734f42 | [PATCH] arm: fix handling of F_OFD_... in oabi_fcntl64()
Cc: stable@vger.kernel.org # 3.15+
Reviewed-by: Jeff Layton <jeff.layton@primarydata.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> | 1 | asmlinkage long sys_oabi_fcntl64(unsigned int fd, unsigned int cmd,
unsigned long arg)
{
struct oabi_flock64 user;
struct flock64 kernel;
mm_segment_t fs = USER_DS; /* initialized to kill a warning */
unsigned long local_arg = arg;
int ret;
switch (cmd) {
case F_OFD_GETLK:
case F_OFD_SETLK:
case ... | 329,184,014,551,991,750,000,000,000,000,000,000,000 | sys_oabi-compat.c | 13,795,461,115,047,124,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2015-8966 | arch/arm/kernel/sys_oabi-compat.c in the Linux kernel before 4.4 allows local users to gain privileges via a crafted (1) F_OFD_GETLK, (2) F_OFD_SETLK, or (3) F_OFD_SETLKW command in an fcntl64 system call. | https://nvd.nist.gov/vuln/detail/CVE-2015-8966 |
159,695 | linux | 76cc404bfdc0d419c720de4daaf2584542734f42 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/76cc404bfdc0d419c720de4daaf2584542734f42 | [PATCH] arm: fix handling of F_OFD_... in oabi_fcntl64()
Cc: stable@vger.kernel.org # 3.15+
Reviewed-by: Jeff Layton <jeff.layton@primarydata.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> | 0 | asmlinkage long sys_oabi_fcntl64(unsigned int fd, unsigned int cmd,
static long do_locks(unsigned int fd, unsigned int cmd,
unsigned long arg)
{
struct flock64 kernel;
struct oabi_flock64 user;
mm_segment_t fs;
long ret;
if (copy_from_user(&user, (struct oabi_flock64 __user *)arg,
sizeof(user)))
r... | 129,705,276,082,726,320,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2015-8966 | arch/arm/kernel/sys_oabi-compat.c in the Linux kernel before 4.4 allows local users to gain privileges via a crafted (1) F_OFD_GETLK, (2) F_OFD_SETLK, or (3) F_OFD_SETLKW command in an fcntl64 system call. | https://nvd.nist.gov/vuln/detail/CVE-2015-8966 |
2,210 | linux | 6934da9238da947628be83635e365df41064b09b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6934da9238da947628be83635e365df41064b09b | ext4: fix potential use after free in __ext4_journal_stop
There is a use-after-free possibility in __ext4_journal_stop() in the
case that we free the handle in the first jbd2_journal_stop() because
we're referencing handle->h_err afterwards. This was introduced in
9705acd63b125dee8b15c705216d7186daea4625 and it is wro... | 1 | int __ext4_journal_stop(const char *where, unsigned int line, handle_t *handle)
{
struct super_block *sb;
int err;
int rc;
if (!ext4_handle_valid(handle)) {
ext4_put_nojournal(handle);
return 0;
}
if (!handle->h_transaction) {
err = jbd2_journal_stop(handle);
return handle->h_err ? handle->h_err : e... | 309,442,467,316,867,250,000,000,000,000,000,000,000 | ext4_jbd2.c | 21,107,129,184,008,160,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2015-8961 | The __ext4_journal_stop function in fs/ext4/ext4_jbd2.c in the Linux kernel before 4.3.3 allows local users to gain privileges or cause a denial of service (use-after-free) by leveraging improper access to a certain error field. | https://nvd.nist.gov/vuln/detail/CVE-2015-8961 |
159,699 | linux | 6934da9238da947628be83635e365df41064b09b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6934da9238da947628be83635e365df41064b09b | ext4: fix potential use after free in __ext4_journal_stop
There is a use-after-free possibility in __ext4_journal_stop() in the
case that we free the handle in the first jbd2_journal_stop() because
we're referencing handle->h_err afterwards. This was introduced in
9705acd63b125dee8b15c705216d7186daea4625 and it is wro... | 0 | int __ext4_journal_stop(const char *where, unsigned int line, handle_t *handle)
{
struct super_block *sb;
int err;
int rc;
if (!ext4_handle_valid(handle)) {
ext4_put_nojournal(handle);
return 0;
}
err = handle->h_err;
if (!handle->h_transaction) {
rc = jbd2_journal_stop(handle);
return err ? err : ... | 225,714,431,304,765,360,000,000,000,000,000,000,000 | ext4_jbd2.c | 96,099,892,552,996,080,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2015-8961 | The __ext4_journal_stop function in fs/ext4/ext4_jbd2.c in the Linux kernel before 4.3.3 allows local users to gain privileges or cause a denial of service (use-after-free) by leveraging improper access to a certain error field. | https://nvd.nist.gov/vuln/detail/CVE-2015-8961 |
2,211 | linux | 951b6a0717db97ce420547222647bcc40bf1eacd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/951b6a0717db97ce420547222647bcc40bf1eacd | Bluetooth: Fix potential NULL dereference in RFCOMM bind callback
addr can be NULL and it should not be dereferenced before NULL checking.
Signed-off-by: Jaganath Kanakkassery <jaganath.k@samsung.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org> | 1 | static int rfcomm_sock_bind(struct socket *sock, struct sockaddr *addr, int addr_len)
{
struct sockaddr_rc *sa = (struct sockaddr_rc *) addr;
struct sock *sk = sock->sk;
int chan = sa->rc_channel;
int err = 0;
BT_DBG("sk %p %pMR", sk, &sa->rc_bdaddr);
if (!addr || addr->sa_family != AF_BLUETOOTH)
return ... | 31,335,887,280,867,650,000,000,000,000,000,000,000 | sock.c | 262,646,104,353,259,580,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2015-8956 | The rfcomm_sock_bind function in net/bluetooth/rfcomm/sock.c in the Linux kernel before 4.2 allows local users to obtain sensitive information or cause a denial of service (NULL pointer dereference) via vectors involving a bind system call on a Bluetooth RFCOMM socket. | https://nvd.nist.gov/vuln/detail/CVE-2015-8956 |
159,700 | linux | 951b6a0717db97ce420547222647bcc40bf1eacd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/951b6a0717db97ce420547222647bcc40bf1eacd | Bluetooth: Fix potential NULL dereference in RFCOMM bind callback
addr can be NULL and it should not be dereferenced before NULL checking.
Signed-off-by: Jaganath Kanakkassery <jaganath.k@samsung.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org> | 0 | static int rfcomm_sock_bind(struct socket *sock, struct sockaddr *addr, int addr_len)
{
struct sockaddr_rc sa;
struct sock *sk = sock->sk;
int len, err = 0;
if (!addr || addr->sa_family != AF_BLUETOOTH)
return -EINVAL;
memset(&sa, 0, sizeof(sa));
len = min_t(unsigned int, sizeof(sa), addr_len);
memcpy... | 12,834,457,401,814,280,000,000,000,000,000,000,000 | sock.c | 331,786,115,828,217,430,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2015-8956 | The rfcomm_sock_bind function in net/bluetooth/rfcomm/sock.c in the Linux kernel before 4.2 allows local users to obtain sensitive information or cause a denial of service (NULL pointer dereference) via vectors involving a bind system call on a Bluetooth RFCOMM socket. | https://nvd.nist.gov/vuln/detail/CVE-2015-8956 |
2,214 | linux | ab79efab0a0ba01a74df782eb7fa44b044dae8b5 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ab79efab0a0ba01a74df782eb7fa44b044dae8b5 | ovl: fix dentry reference leak
In ovl_copy_up_locked(), newdentry is leaked if the function exits through
out_cleanup as this just to out after calling ovl_cleanup() - which doesn't
actually release the ref on newdentry.
The out_cleanup segment should instead exit through out2 as certainly
newdentry leaks - and possi... | 1 | static int ovl_copy_up_locked(struct dentry *workdir, struct dentry *upperdir,
struct dentry *dentry, struct path *lowerpath,
struct kstat *stat, struct iattr *attr,
const char *link)
{
struct inode *wdir = workdir->d_inode;
struct inode *udir = upperdir->d_inode;
struct dentry *newdentry ... | 101,790,856,959,696,370,000,000,000,000,000,000,000 | copy_up.c | 148,213,014,245,758,890,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2015-8953 | fs/overlayfs/copy_up.c in the Linux kernel before 4.2.6 uses an incorrect cleanup code path, which allows local users to cause a denial of service (dentry reference leak) via filesystem operations on a large file in a lower overlayfs layer. | https://nvd.nist.gov/vuln/detail/CVE-2015-8953 |
159,703 | linux | ab79efab0a0ba01a74df782eb7fa44b044dae8b5 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ab79efab0a0ba01a74df782eb7fa44b044dae8b5 | ovl: fix dentry reference leak
In ovl_copy_up_locked(), newdentry is leaked if the function exits through
out_cleanup as this just to out after calling ovl_cleanup() - which doesn't
actually release the ref on newdentry.
The out_cleanup segment should instead exit through out2 as certainly
newdentry leaks - and possi... | 0 | static int ovl_copy_up_locked(struct dentry *workdir, struct dentry *upperdir,
struct dentry *dentry, struct path *lowerpath,
struct kstat *stat, struct iattr *attr,
const char *link)
{
struct inode *wdir = workdir->d_inode;
struct inode *udir = upperdir->d_inode;
struct dentry *newdentry ... | 306,942,844,156,181,720,000,000,000,000,000,000,000 | copy_up.c | 337,768,321,828,032,630,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2015-8953 | fs/overlayfs/copy_up.c in the Linux kernel before 4.2.6 uses an incorrect cleanup code path, which allows local users to cause a denial of service (dentry reference leak) via filesystem operations on a large file in a lower overlayfs layer. | https://nvd.nist.gov/vuln/detail/CVE-2015-8953 |
2,218 | libgd | 4751b606fa38edc456d627140898a7ec679fcc24 | https://github.com/libgd/libgd | https://github.com/libgd/libgd/commit/4751b606fa38edc456d627140898a7ec679fcc24 | gdImageScaleTwoPass memory leak fix
Fixing memory leak in gdImageScaleTwoPass, as reported by @cmb69 and
confirmed by @vapier. This bug actually bit me in production and I'm
very thankful that it was reported with an easy fix.
Fixes #173. | 1 | gdImageScaleTwoPass(const gdImagePtr src, const unsigned int new_width,
const unsigned int new_height)
{
const unsigned int src_width = src->sx;
const unsigned int src_height = src->sy;
gdImagePtr tmp_im = NULL;
gdImagePtr dst = NULL;
/* First, handle the trivial case. */
if (src_... | 239,805,181,915,502,050,000,000,000,000,000,000,000 | gd_interpolation.c | 4,848,383,815,680,541,500,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2015-8877 | The gdImageScaleTwoPass function in gd_interpolation.c in the GD Graphics Library (aka libgd) before 2.2.0, as used in PHP before 5.6.12, uses inconsistent allocate and free approaches, which allows remote attackers to cause a denial of service (memory consumption) via a crafted call, as demonstrated by a call to the P... | https://nvd.nist.gov/vuln/detail/CVE-2015-8877 |
159,707 | libgd | 4751b606fa38edc456d627140898a7ec679fcc24 | https://github.com/libgd/libgd | https://github.com/libgd/libgd/commit/4751b606fa38edc456d627140898a7ec679fcc24 | gdImageScaleTwoPass memory leak fix
Fixing memory leak in gdImageScaleTwoPass, as reported by @cmb69 and
confirmed by @vapier. This bug actually bit me in production and I'm
very thankful that it was reported with an easy fix.
Fixes #173. | 0 | gdImageScaleTwoPass(const gdImagePtr src, const unsigned int new_width,
const unsigned int new_height)
{
const unsigned int src_width = src->sx;
const unsigned int src_height = src->sy;
gdImagePtr tmp_im = NULL;
gdImagePtr dst = NULL;
/* First, handle the trivial case. */
if (src_... | 35,372,154,903,276,470,000,000,000,000,000,000,000 | gd_interpolation.c | 237,729,470,601,478,230,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2015-8877 | The gdImageScaleTwoPass function in gd_interpolation.c in the GD Graphics Library (aka libgd) before 2.2.0, as used in PHP before 5.6.12, uses inconsistent allocate and free approaches, which allows remote attackers to cause a denial of service (memory consumption) via a crafted call, as demonstrated by a call to the P... | https://nvd.nist.gov/vuln/detail/CVE-2015-8877 |
2,219 | file | 6713ca45e7757297381f4b4cdb9cf5e624a9ad36 | https://github.com/file/file | https://github.com/file/file/commit/6713ca45e7757297381f4b4cdb9cf5e624a9ad36 | PR/454: Fix memory corruption when the continuation level jumps by more than
20 in a single step. | 1 | file_check_mem(struct magic_set *ms, unsigned int level)
{
size_t len;
if (level >= ms->c.len) {
len = (ms->c.len += 20) * sizeof(*ms->c.li);
ms->c.li = CAST(struct level_info *, (ms->c.li == NULL) ?
malloc(len) :
realloc(ms->c.li, len));
if (ms->c.li == NULL) {
file_oomem(ms, len);
ret... | 37,015,776,179,791,950,000,000,000,000,000,000,000 | funcs.c | 247,884,554,659,100,300,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-8865 | The file_check_mem function in funcs.c in file before 5.23, as used in the Fileinfo component in PHP before 5.5.34, 5.6.x before 5.6.20, and 7.x before 7.0.5, mishandles continuation-level jumps, which allows context-dependent attackers to cause a denial of service (buffer overflow and application crash) or possibly ex... | https://nvd.nist.gov/vuln/detail/CVE-2015-8865 |
159,708 | file | 6713ca45e7757297381f4b4cdb9cf5e624a9ad36 | https://github.com/file/file | https://github.com/file/file/commit/6713ca45e7757297381f4b4cdb9cf5e624a9ad36 | PR/454: Fix memory corruption when the continuation level jumps by more than
20 in a single step. | 0 | file_check_mem(struct magic_set *ms, unsigned int level)
{
size_t len;
if (level >= ms->c.len) {
len = (ms->c.len = 20 + level) * sizeof(*ms->c.li);
ms->c.li = CAST(struct level_info *, (ms->c.li == NULL) ?
malloc(len) :
realloc(ms->c.li, len));
if (ms->c.li == NULL) {
file_oomem(ms, len);... | 253,761,133,211,485,100,000,000,000,000,000,000,000 | funcs.c | 140,314,818,615,611,380,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-8865 | The file_check_mem function in funcs.c in file before 5.23, as used in the Fileinfo component in PHP before 5.5.34, 5.6.x before 5.6.20, and 7.x before 7.0.5, mishandles continuation-level jumps, which allows context-dependent attackers to cause a denial of service (buffer overflow and application crash) or possibly ex... | https://nvd.nist.gov/vuln/detail/CVE-2015-8865 |
2,221 | jq | 8eb1367ca44e772963e704a700ef72ae2e12babd | https://github.com/stedolan/jq | https://github.com/stedolan/jq/commit/8eb1367ca44e772963e704a700ef72ae2e12babd | Heap buffer overflow in tokenadd() (fix #105)
This was an off-by one: the NUL terminator byte was not allocated on
resize. This was triggered by JSON-encoded numbers longer than 256
bytes. | 1 | static void tokenadd(struct jv_parser* p, char c) {
assert(p->tokenpos <= p->tokenlen);
if (p->tokenpos == p->tokenlen) {
p->tokenlen = p->tokenlen*2 + 256;
p->tokenbuf = jv_mem_realloc(p->tokenbuf, p->tokenlen);
}
assert(p->tokenpos < p->tokenlen);
p->tokenbuf[p->tokenpos++] = c;
}
| 102,885,964,769,614,870,000,000,000,000,000,000,000 | jv_parse.c | 175,409,213,026,670,600,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-8863 | Off-by-one error in the tokenadd function in jv_parse.c in jq allows remote attackers to cause a denial of service (crash) via a long JSON-encoded number, which triggers a heap-based buffer overflow. | https://nvd.nist.gov/vuln/detail/CVE-2015-8863 |
159,710 | jq | 8eb1367ca44e772963e704a700ef72ae2e12babd | https://github.com/stedolan/jq | https://github.com/stedolan/jq/commit/8eb1367ca44e772963e704a700ef72ae2e12babd | Heap buffer overflow in tokenadd() (fix #105)
This was an off-by one: the NUL terminator byte was not allocated on
resize. This was triggered by JSON-encoded numbers longer than 256
bytes. | 0 | static void tokenadd(struct jv_parser* p, char c) {
assert(p->tokenpos <= p->tokenlen);
if (p->tokenpos >= (p->tokenlen - 1)) {
p->tokenlen = p->tokenlen*2 + 256;
p->tokenbuf = jv_mem_realloc(p->tokenbuf, p->tokenlen);
}
assert(p->tokenpos < p->tokenlen);
p->tokenbuf[p->tokenpos++] = c;
}
| 82,675,174,159,625,030,000,000,000,000,000,000,000 | jv_parse.c | 41,188,596,103,790,180,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-8863 | Off-by-one error in the tokenadd function in jv_parse.c in jq allows remote attackers to cause a denial of service (crash) via a long JSON-encoded number, which triggers a heap-based buffer overflow. | https://nvd.nist.gov/vuln/detail/CVE-2015-8863 |
2,224 | linux | 7f821fc9c77a9b01fe7b1d6e72717b33d8d64142 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7f821fc9c77a9b01fe7b1d6e72717b33d8d64142 | powerpc/tm: Check for already reclaimed tasks
Currently we can hit a scenario where we'll tm_reclaim() twice. This
results in a TM bad thing exception because the second reclaim occurs
when not in suspend mode.
The scenario in which this can happen is the following. We attempt to
deliver a signal to userspace. To ... | 1 | static void tm_reclaim_thread(struct thread_struct *thr,
struct thread_info *ti, uint8_t cause)
{
unsigned long msr_diff = 0;
/*
* If FP/VSX registers have been already saved to the
* thread_struct, move them to the transact_fp array.
* We clear the TIF_RESTORE_TM bit since after the reclaim
* the t... | 100,255,729,192,226,000,000,000,000,000,000,000,000 | process.c | 205,611,454,501,543,500,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2015-8845 | The tm_reclaim_thread function in arch/powerpc/kernel/process.c in the Linux kernel before 4.4.1 on powerpc platforms does not ensure that TM suspend mode exists before proceeding with a tm_reclaim call, which allows local users to cause a denial of service (TM Bad Thing exception and panic) via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2015-8845 |
159,713 | linux | 7f821fc9c77a9b01fe7b1d6e72717b33d8d64142 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7f821fc9c77a9b01fe7b1d6e72717b33d8d64142 | powerpc/tm: Check for already reclaimed tasks
Currently we can hit a scenario where we'll tm_reclaim() twice. This
results in a TM bad thing exception because the second reclaim occurs
when not in suspend mode.
The scenario in which this can happen is the following. We attempt to
deliver a signal to userspace. To ... | 0 | static void tm_reclaim_thread(struct thread_struct *thr,
struct thread_info *ti, uint8_t cause)
{
unsigned long msr_diff = 0;
/*
* If FP/VSX registers have been already saved to the
* thread_struct, move them to the transact_fp array.
* We clear the TIF_RESTORE_TM bit since after the reclaim
* the t... | 222,794,564,364,077,800,000,000,000,000,000,000,000 | process.c | 266,918,020,283,023,350,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2015-8845 | The tm_reclaim_thread function in arch/powerpc/kernel/process.c in the Linux kernel before 4.4.1 on powerpc platforms does not ensure that TM suspend mode exists before proceeding with a tm_reclaim call, which allows local users to cause a denial of service (TM Bad Thing exception and panic) via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2015-8845 |
2,239 | linux | 94f9cd81436c85d8c3a318ba92e236ede73752fc | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/94f9cd81436c85d8c3a318ba92e236ede73752fc | netfilter: nf_nat_redirect: add missing NULL pointer check
Commit 8b13eddfdf04cbfa561725cfc42d6868fe896f56 ("netfilter: refactor NAT
redirect IPv4 to use it from nf_tables") has introduced a trivial logic
change which can result in the following crash.
BUG: unable to handle kernel NULL pointer dereference at 00000000... | 1 | nf_nat_redirect_ipv4(struct sk_buff *skb,
const struct nf_nat_ipv4_multi_range_compat *mr,
unsigned int hooknum)
{
struct nf_conn *ct;
enum ip_conntrack_info ctinfo;
__be32 newdst;
struct nf_nat_range newrange;
NF_CT_ASSERT(hooknum == NF_INET_PRE_ROUTING ||
hooknum == NF_INET_LOCAL_OUT);
ct... | 63,053,819,853,057,460,000,000,000,000,000,000,000 | nf_nat_redirect.c | 273,058,852,035,029,880,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2015-8787 | The nf_nat_redirect_ipv4 function in net/netfilter/nf_nat_redirect.c in the Linux kernel before 4.4 allows remote attackers to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact by sending certain IPv4 packets to an incompletely configured interface, a relate... | https://nvd.nist.gov/vuln/detail/CVE-2015-8787 |
159,727 | linux | 94f9cd81436c85d8c3a318ba92e236ede73752fc | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/94f9cd81436c85d8c3a318ba92e236ede73752fc | netfilter: nf_nat_redirect: add missing NULL pointer check
Commit 8b13eddfdf04cbfa561725cfc42d6868fe896f56 ("netfilter: refactor NAT
redirect IPv4 to use it from nf_tables") has introduced a trivial logic
change which can result in the following crash.
BUG: unable to handle kernel NULL pointer dereference at 00000000... | 0 | nf_nat_redirect_ipv4(struct sk_buff *skb,
const struct nf_nat_ipv4_multi_range_compat *mr,
unsigned int hooknum)
{
struct nf_conn *ct;
enum ip_conntrack_info ctinfo;
__be32 newdst;
struct nf_nat_range newrange;
NF_CT_ASSERT(hooknum == NF_INET_PRE_ROUTING ||
hooknum == NF_INET_LOCAL_OUT);
ct... | 154,560,251,003,696,250,000,000,000,000,000,000,000 | nf_nat_redirect.c | 92,930,170,415,980,100,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2015-8787 | The nf_nat_redirect_ipv4 function in net/netfilter/nf_nat_redirect.c in the Linux kernel before 4.4 allows remote attackers to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact by sending certain IPv4 packets to an incompletely configured interface, a relate... | https://nvd.nist.gov/vuln/detail/CVE-2015-8787 |
2,240 | linux | 3ca8138f014a913f98e6ef40e939868e1e9ea876 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/3ca8138f014a913f98e6ef40e939868e1e9ea876 | fuse: break infinite loop in fuse_fill_write_pages()
I got a report about unkillable task eating CPU. Further
investigation shows, that the problem is in the fuse_fill_write_pages()
function. If iov's first segment has zero length, we get an infinite
loop, because we never reach iov_iter_advance() call.
Fix this by c... | 1 | static ssize_t fuse_fill_write_pages(struct fuse_req *req,
struct address_space *mapping,
struct iov_iter *ii, loff_t pos)
{
struct fuse_conn *fc = get_fuse_conn(mapping->host);
unsigned offset = pos & (PAGE_CACHE_SIZE - 1);
size_t count = 0;
int err;
req->in.argpages = 1;
req->page_descs[0].... | 294,235,460,800,861,680,000,000,000,000,000,000,000 | file.c | 211,377,916,038,697,840,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2015-8785 | The fuse_fill_write_pages function in fs/fuse/file.c in the Linux kernel before 4.4 allows local users to cause a denial of service (infinite loop) via a writev system call that triggers a zero length for the first segment of an iov. | https://nvd.nist.gov/vuln/detail/CVE-2015-8785 |
159,728 | linux | 3ca8138f014a913f98e6ef40e939868e1e9ea876 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/3ca8138f014a913f98e6ef40e939868e1e9ea876 | fuse: break infinite loop in fuse_fill_write_pages()
I got a report about unkillable task eating CPU. Further
investigation shows, that the problem is in the fuse_fill_write_pages()
function. If iov's first segment has zero length, we get an infinite
loop, because we never reach iov_iter_advance() call.
Fix this by c... | 0 | static ssize_t fuse_fill_write_pages(struct fuse_req *req,
struct address_space *mapping,
struct iov_iter *ii, loff_t pos)
{
struct fuse_conn *fc = get_fuse_conn(mapping->host);
unsigned offset = pos & (PAGE_CACHE_SIZE - 1);
size_t count = 0;
int err;
req->in.argpages = 1;
req->page_descs[0].... | 168,209,042,959,476,270,000,000,000,000,000,000,000 | file.c | 232,709,947,421,444,030,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2015-8785 | The fuse_fill_write_pages function in fs/fuse/file.c in the Linux kernel before 4.4 allows local users to cause a denial of service (infinite loop) via a writev system call that triggers a zero length for the first segment of an iov. | https://nvd.nist.gov/vuln/detail/CVE-2015-8785 |
2,241 | libtiff | b18012dae552f85dcc5c57d3bf4e997a15b1cc1c | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/b18012dae552f85dcc5c57d3bf4e997a15b1cc1c | * libtiff/tif_next.c: fix potential out-of-bound write in NeXTDecode()
triggered by http://lcamtuf.coredump.cx/afl/vulns/libtiff5.tif
(bugzilla #2508) | 1 | NeXTDecode(TIFF* tif, uint8* buf, tmsize_t occ, uint16 s)
{
static const char module[] = "NeXTDecode";
unsigned char *bp, *op;
tmsize_t cc;
uint8* row;
tmsize_t scanline, n;
(void) s;
/*
* Each scanline is assumed to start off as all
* white (we assume a PhotometricInterpretation
* of ``min-is-black'').
... | 79,488,190,277,959,365,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2015-8784 | The NeXTDecode function in tif_next.c in LibTIFF allows remote attackers to cause a denial of service (out-of-bounds write) via a crafted TIFF image, as demonstrated by libtiff5.tif. | https://nvd.nist.gov/vuln/detail/CVE-2015-8784 |
159,729 | libtiff | b18012dae552f85dcc5c57d3bf4e997a15b1cc1c | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/b18012dae552f85dcc5c57d3bf4e997a15b1cc1c | * libtiff/tif_next.c: fix potential out-of-bound write in NeXTDecode()
triggered by http://lcamtuf.coredump.cx/afl/vulns/libtiff5.tif
(bugzilla #2508) | 0 | NeXTDecode(TIFF* tif, uint8* buf, tmsize_t occ, uint16 s)
{
static const char module[] = "NeXTDecode";
unsigned char *bp, *op;
tmsize_t cc;
uint8* row;
tmsize_t scanline, n;
(void) s;
/*
* Each scanline is assumed to start off as all
* white (we assume a PhotometricInterpretation
* of ``min-is-black'').
... | 68,707,752,571,943,770,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2015-8784 | The NeXTDecode function in tif_next.c in LibTIFF allows remote attackers to cause a denial of service (out-of-bounds write) via a crafted TIFF image, as demonstrated by libtiff5.tif. | https://nvd.nist.gov/vuln/detail/CVE-2015-8784 |
2,268 | krb5 | b863de7fbf080b15e347a736fdda0a82d42f4f6b | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/b863de7fbf080b15e347a736fdda0a82d42f4f6b | Check for null kadm5 policy name [CVE-2015-8630]
In kadm5_create_principal_3() and kadm5_modify_principal(), check for
entry->policy being null when KADM5_POLICY is included in the mask.
CVE-2015-8630:
In MIT krb5 1.12 and later, an authenticated attacker with permission
to modify a principal entry can cause kadmind... | 1 | kadm5_create_principal_3(void *server_handle,
kadm5_principal_ent_t entry, long mask,
int n_ks_tuple, krb5_key_salt_tuple *ks_tuple,
char *password)
{
krb5_db_entry *kdb;
osa_princ_ent_rec adb;
kadm5_policy_en... | 241,581,982,310,294,040,000,000,000,000,000,000,000 | svr_principal.c | 220,412,209,520,526,820,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2015-8630 | The (1) kadm5_create_principal_3 and (2) kadm5_modify_principal functions in lib/kadm5/srv/svr_principal.c in kadmind in MIT Kerberos 5 (aka krb5) 1.12.x and 1.13.x before 1.13.4 and 1.14.x before 1.14.1 allow remote authenticated users to cause a denial of service (NULL pointer dereference and daemon crash) by specify... | https://nvd.nist.gov/vuln/detail/CVE-2015-8630 |
159,756 | krb5 | b863de7fbf080b15e347a736fdda0a82d42f4f6b | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/b863de7fbf080b15e347a736fdda0a82d42f4f6b | Check for null kadm5 policy name [CVE-2015-8630]
In kadm5_create_principal_3() and kadm5_modify_principal(), check for
entry->policy being null when KADM5_POLICY is included in the mask.
CVE-2015-8630:
In MIT krb5 1.12 and later, an authenticated attacker with permission
to modify a principal entry can cause kadmind... | 0 | kadm5_create_principal_3(void *server_handle,
kadm5_principal_ent_t entry, long mask,
int n_ks_tuple, krb5_key_salt_tuple *ks_tuple,
char *password)
{
krb5_db_entry *kdb;
osa_princ_ent_rec adb;
kadm5_policy_en... | 72,680,052,210,742,260,000,000,000,000,000,000,000 | svr_principal.c | 254,658,728,888,016,480,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2015-8630 | The (1) kadm5_create_principal_3 and (2) kadm5_modify_principal functions in lib/kadm5/srv/svr_principal.c in kadmind in MIT Kerberos 5 (aka krb5) 1.12.x and 1.13.x before 1.13.4 and 1.14.x before 1.14.1 allow remote authenticated users to cause a denial of service (NULL pointer dereference and daemon crash) by specify... | https://nvd.nist.gov/vuln/detail/CVE-2015-8630 |
2,269 | krb5 | b863de7fbf080b15e347a736fdda0a82d42f4f6b | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/b863de7fbf080b15e347a736fdda0a82d42f4f6b | Check for null kadm5 policy name [CVE-2015-8630]
In kadm5_create_principal_3() and kadm5_modify_principal(), check for
entry->policy being null when KADM5_POLICY is included in the mask.
CVE-2015-8630:
In MIT krb5 1.12 and later, an authenticated attacker with permission
to modify a principal entry can cause kadmind... | 1 | kadm5_modify_principal(void *server_handle,
kadm5_principal_ent_t entry, long mask)
{
int ret, ret2, i;
kadm5_policy_ent_rec pol;
krb5_boolean have_pol = FALSE;
krb5_db_entry *kdb;
krb5_tl_data *tl_data_orig;
osa_princ... | 273,531,622,744,848,060,000,000,000,000,000,000,000 | svr_principal.c | 220,412,209,520,526,820,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2015-8630 | The (1) kadm5_create_principal_3 and (2) kadm5_modify_principal functions in lib/kadm5/srv/svr_principal.c in kadmind in MIT Kerberos 5 (aka krb5) 1.12.x and 1.13.x before 1.13.4 and 1.14.x before 1.14.1 allow remote authenticated users to cause a denial of service (NULL pointer dereference and daemon crash) by specify... | https://nvd.nist.gov/vuln/detail/CVE-2015-8630 |
159,757 | krb5 | b863de7fbf080b15e347a736fdda0a82d42f4f6b | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/b863de7fbf080b15e347a736fdda0a82d42f4f6b | Check for null kadm5 policy name [CVE-2015-8630]
In kadm5_create_principal_3() and kadm5_modify_principal(), check for
entry->policy being null when KADM5_POLICY is included in the mask.
CVE-2015-8630:
In MIT krb5 1.12 and later, an authenticated attacker with permission
to modify a principal entry can cause kadmind... | 0 | kadm5_modify_principal(void *server_handle,
kadm5_principal_ent_t entry, long mask)
{
int ret, ret2, i;
kadm5_policy_ent_rec pol;
krb5_boolean have_pol = FALSE;
krb5_db_entry *kdb;
krb5_tl_data *tl_data_orig;
osa_princ... | 28,668,422,403,298,300,000,000,000,000,000,000,000 | svr_principal.c | 254,658,728,888,016,480,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2015-8630 | The (1) kadm5_create_principal_3 and (2) kadm5_modify_principal functions in lib/kadm5/srv/svr_principal.c in kadmind in MIT Kerberos 5 (aka krb5) 1.12.x and 1.13.x before 1.13.4 and 1.14.x before 1.14.1 allow remote authenticated users to cause a denial of service (NULL pointer dereference and daemon crash) by specify... | https://nvd.nist.gov/vuln/detail/CVE-2015-8630 |
2,270 | krb5 | df17a1224a3406f57477bcd372c61e04c0e5a5bb | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/df17a1224a3406f57477bcd372c61e04c0e5a5bb | Verify decoded kadmin C strings [CVE-2015-8629]
In xdr_nullstring(), check that the decoded string is terminated with
a zero byte and does not contain any internal zero bytes.
CVE-2015-8629:
In all versions of MIT krb5, an authenticated attacker can cause
kadmind to read beyond the end of allocated memory by sending... | 1 | bool_t xdr_nullstring(XDR *xdrs, char **objp)
{
u_int size;
if (xdrs->x_op == XDR_ENCODE) {
if (*objp == NULL)
size = 0;
else
size = strlen(*objp) + 1;
}
if (! xdr_u_int(xdrs, &size)) {
return FALSE;
}
switch (xdrs->x_op) {
case XDR_DECODE:
if (size == 0) {
... | 312,213,523,298,414,670,000,000,000,000,000,000,000 | kadm_rpc_xdr.c | 286,240,059,814,617,800,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-8629 | The xdr_nullstring function in lib/kadm5/kadm_rpc_xdr.c in kadmind in MIT Kerberos 5 (aka krb5) before 1.13.4 and 1.14.x before 1.14.1 does not verify whether '\0' characters exist as expected, which allows remote authenticated users to obtain sensitive information or cause a denial of service (out-of-bounds read) via ... | https://nvd.nist.gov/vuln/detail/CVE-2015-8629 |
159,758 | krb5 | df17a1224a3406f57477bcd372c61e04c0e5a5bb | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/df17a1224a3406f57477bcd372c61e04c0e5a5bb | Verify decoded kadmin C strings [CVE-2015-8629]
In xdr_nullstring(), check that the decoded string is terminated with
a zero byte and does not contain any internal zero bytes.
CVE-2015-8629:
In all versions of MIT krb5, an authenticated attacker can cause
kadmind to read beyond the end of allocated memory by sending... | 0 | bool_t xdr_nullstring(XDR *xdrs, char **objp)
{
u_int size;
if (xdrs->x_op == XDR_ENCODE) {
if (*objp == NULL)
size = 0;
else
size = strlen(*objp) + 1;
}
if (! xdr_u_int(xdrs, &size)) {
return FALSE;
}
switch (xdrs->x_op) {
case XDR_DECODE:
if (size == 0) {
... | 127,532,311,097,575,020,000,000,000,000,000,000,000 | kadm_rpc_xdr.c | 156,889,314,551,984,680,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-8629 | The xdr_nullstring function in lib/kadm5/kadm_rpc_xdr.c in kadmind in MIT Kerberos 5 (aka krb5) before 1.13.4 and 1.14.x before 1.14.1 does not verify whether '\0' characters exist as expected, which allows remote authenticated users to obtain sensitive information or cause a denial of service (out-of-bounds read) via ... | https://nvd.nist.gov/vuln/detail/CVE-2015-8629 |
2,272 | linux | 096fe9eaea40a17e125569f9e657e34cdb6d73bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/096fe9eaea40a17e125569f9e657e34cdb6d73bd | KEYS: Fix handling of stored error in a negatively instantiated user key
If a user key gets negatively instantiated, an error code is cached in the
payload area. A negatively instantiated key may be then be positively
instantiated by updating it with valid data. However, the ->update key
type method must be aware th... | 1 | static int encrypted_update(struct key *key, struct key_preparsed_payload *prep)
{
struct encrypted_key_payload *epayload = key->payload.data[0];
struct encrypted_key_payload *new_epayload;
char *buf;
char *new_master_desc = NULL;
const char *format = NULL;
size_t datalen = prep->datalen;
int ret = 0;
if (... | 273,212,551,994,244,770,000,000,000,000,000,000,000 | encrypted.c | 54,525,955,971,976,580,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2015-8539 | The KEYS subsystem in the Linux kernel before 4.4 allows local users to gain privileges or cause a denial of service (BUG) via crafted keyctl commands that negatively instantiate a key, related to security/keys/encrypted-keys/encrypted.c, security/keys/trusted.c, and security/keys/user_defined.c. | https://nvd.nist.gov/vuln/detail/CVE-2015-8539 |
159,760 | linux | 096fe9eaea40a17e125569f9e657e34cdb6d73bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/096fe9eaea40a17e125569f9e657e34cdb6d73bd | KEYS: Fix handling of stored error in a negatively instantiated user key
If a user key gets negatively instantiated, an error code is cached in the
payload area. A negatively instantiated key may be then be positively
instantiated by updating it with valid data. However, the ->update key
type method must be aware th... | 0 | static int encrypted_update(struct key *key, struct key_preparsed_payload *prep)
{
struct encrypted_key_payload *epayload = key->payload.data[0];
struct encrypted_key_payload *new_epayload;
char *buf;
char *new_master_desc = NULL;
const char *format = NULL;
size_t datalen = prep->datalen;
int ret = 0;
if (t... | 221,462,791,637,635,240,000,000,000,000,000,000,000 | encrypted.c | 177,370,115,835,983,100,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2015-8539 | The KEYS subsystem in the Linux kernel before 4.4 allows local users to gain privileges or cause a denial of service (BUG) via crafted keyctl commands that negatively instantiate a key, related to security/keys/encrypted-keys/encrypted.c, security/keys/trusted.c, and security/keys/user_defined.c. | https://nvd.nist.gov/vuln/detail/CVE-2015-8539 |
2,273 | linux | 096fe9eaea40a17e125569f9e657e34cdb6d73bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/096fe9eaea40a17e125569f9e657e34cdb6d73bd | KEYS: Fix handling of stored error in a negatively instantiated user key
If a user key gets negatively instantiated, an error code is cached in the
payload area. A negatively instantiated key may be then be positively
instantiated by updating it with valid data. However, the ->update key
type method must be aware th... | 1 | static int trusted_update(struct key *key, struct key_preparsed_payload *prep)
{
struct trusted_key_payload *p = key->payload.data[0];
struct trusted_key_payload *new_p;
struct trusted_key_options *new_o;
size_t datalen = prep->datalen;
char *datablob;
int ret = 0;
if (!p->migratable)
return -EPERM;... | 295,894,163,410,544,320,000,000,000,000,000,000,000 | trusted.c | 221,061,637,993,863,750,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2015-8539 | The KEYS subsystem in the Linux kernel before 4.4 allows local users to gain privileges or cause a denial of service (BUG) via crafted keyctl commands that negatively instantiate a key, related to security/keys/encrypted-keys/encrypted.c, security/keys/trusted.c, and security/keys/user_defined.c. | https://nvd.nist.gov/vuln/detail/CVE-2015-8539 |
159,761 | linux | 096fe9eaea40a17e125569f9e657e34cdb6d73bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/096fe9eaea40a17e125569f9e657e34cdb6d73bd | KEYS: Fix handling of stored error in a negatively instantiated user key
If a user key gets negatively instantiated, an error code is cached in the
payload area. A negatively instantiated key may be then be positively
instantiated by updating it with valid data. However, the ->update key
type method must be aware th... | 0 | static int trusted_update(struct key *key, struct key_preparsed_payload *prep)
{
struct trusted_key_payload *p;
struct trusted_key_payload *new_p;
struct trusted_key_options *new_o;
size_t datalen = prep->datalen;
char *datablob;
int ret = 0;
if (test_bit(KEY_FLAG_NEGATIVE, &key->flags))
return -ENOKE... | 254,499,908,932,089,320,000,000,000,000,000,000,000 | trusted.c | 230,132,572,009,428,870,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2015-8539 | The KEYS subsystem in the Linux kernel before 4.4 allows local users to gain privileges or cause a denial of service (BUG) via crafted keyctl commands that negatively instantiate a key, related to security/keys/encrypted-keys/encrypted.c, security/keys/trusted.c, and security/keys/user_defined.c. | https://nvd.nist.gov/vuln/detail/CVE-2015-8539 |
2,274 | linux | 096fe9eaea40a17e125569f9e657e34cdb6d73bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/096fe9eaea40a17e125569f9e657e34cdb6d73bd | KEYS: Fix handling of stored error in a negatively instantiated user key
If a user key gets negatively instantiated, an error code is cached in the
payload area. A negatively instantiated key may be then be positively
instantiated by updating it with valid data. However, the ->update key
type method must be aware th... | 1 | int user_update(struct key *key, struct key_preparsed_payload *prep)
{
struct user_key_payload *upayload, *zap;
size_t datalen = prep->datalen;
int ret;
ret = -EINVAL;
if (datalen <= 0 || datalen > 32767 || !prep->data)
goto error;
/* construct a replacement payload */
ret = -ENOMEM;
upayload = kmalloc(size... | 150,125,670,513,652,380,000,000,000,000,000,000,000 | user_defined.c | 334,071,985,264,321,620,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2015-8539 | The KEYS subsystem in the Linux kernel before 4.4 allows local users to gain privileges or cause a denial of service (BUG) via crafted keyctl commands that negatively instantiate a key, related to security/keys/encrypted-keys/encrypted.c, security/keys/trusted.c, and security/keys/user_defined.c. | https://nvd.nist.gov/vuln/detail/CVE-2015-8539 |
159,762 | linux | 096fe9eaea40a17e125569f9e657e34cdb6d73bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/096fe9eaea40a17e125569f9e657e34cdb6d73bd | KEYS: Fix handling of stored error in a negatively instantiated user key
If a user key gets negatively instantiated, an error code is cached in the
payload area. A negatively instantiated key may be then be positively
instantiated by updating it with valid data. However, the ->update key
type method must be aware th... | 0 | int user_update(struct key *key, struct key_preparsed_payload *prep)
{
struct user_key_payload *upayload, *zap;
size_t datalen = prep->datalen;
int ret;
ret = -EINVAL;
if (datalen <= 0 || datalen > 32767 || !prep->data)
goto error;
/* construct a replacement payload */
ret = -ENOMEM;
upayload = kmalloc(size... | 70,048,715,110,696,030,000,000,000,000,000,000,000 | user_defined.c | 289,171,460,529,613,140,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2015-8539 | The KEYS subsystem in the Linux kernel before 4.4 allows local users to gain privileges or cause a denial of service (BUG) via crafted keyctl commands that negatively instantiate a key, related to security/keys/encrypted-keys/encrypted.c, security/keys/trusted.c, and security/keys/user_defined.c. | https://nvd.nist.gov/vuln/detail/CVE-2015-8539 |
2,296 | 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... | 1 | 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... | 302,546,870,172,646,940,000,000,000,000,000,000,000 | visor.c | 330,059,420,467,391,720,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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.