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,057 | linux | 8e3fbf870481eb53b2d3a322d1fc395ad8b367ed | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8e3fbf870481eb53b2d3a322d1fc395ad8b367ed | hamradio/yam: fix info leak in ioctl
The yam_ioctl() code fails to initialise the cmd field
of the struct yamdrv_ioctl_cfg. Add an explicit memset(0)
before filling the structure to avoid the 4-byte info leak.
Signed-off-by: Salva Peiró <speiro@ai2.upv.es>
Signed-off-by: David S. Miller <davem@davemloft.net> | 0 | static int yam_ioctl(struct net_device *dev, struct ifreq *ifr, int cmd)
{
struct yam_port *yp = netdev_priv(dev);
struct yamdrv_ioctl_cfg yi;
struct yamdrv_ioctl_mcs *ym;
int ioctl_cmd;
if (copy_from_user(&ioctl_cmd, ifr->ifr_data, sizeof(int)))
return -EFAULT;
if (yp->magic != YAM_MAGIC)
return -EINVAL;
... | 187,239,089,074,124,350,000,000,000,000,000,000,000 | None | null | [
"CWE-399"
] | CVE-2014-1446 | The yam_ioctl function in drivers/net/hamradio/yam.c in the Linux kernel before 3.12.8 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel memory by leveraging the CAP_NET_ADMIN capability for an SIOCYAMGCFG ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-1446 |
1,327 | linux | 2b13d06c9584b4eb773f1e80bbaedab9a1c344e1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b13d06c9584b4eb773f1e80bbaedab9a1c344e1 | wanxl: fix info leak in ioctl
The wanxl_ioctl() code fails to initialize the two padding bytes of
struct sync_serial_settings after the ->loopback member. Add an explicit
memset(0) before filling the structure to avoid the info leak.
Signed-off-by: Salva Peiró <speiro@ai2.upv.es>
Signed-off-by: David S. Miller <davem... | 1 | static int wanxl_ioctl(struct net_device *dev, struct ifreq *ifr, int cmd)
{
const size_t size = sizeof(sync_serial_settings);
sync_serial_settings line;
port_t *port = dev_to_port(dev);
if (cmd != SIOCWANDEV)
return hdlc_ioctl(dev, ifr, cmd);
switch (ifr->ifr_settings.type) {
case IF_GET_IFACE:
ifr->ifr_se... | 289,977,000,113,180,630,000,000,000,000,000,000,000 | wanxl.c | 1,534,528,475,873,357,800,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-1445 | The wanxl_ioctl function in drivers/net/wan/wanxl.c in the Linux kernel before 3.11.7 does not properly initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory via an ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-1445 |
159,058 | linux | 2b13d06c9584b4eb773f1e80bbaedab9a1c344e1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b13d06c9584b4eb773f1e80bbaedab9a1c344e1 | wanxl: fix info leak in ioctl
The wanxl_ioctl() code fails to initialize the two padding bytes of
struct sync_serial_settings after the ->loopback member. Add an explicit
memset(0) before filling the structure to avoid the info leak.
Signed-off-by: Salva Peiró <speiro@ai2.upv.es>
Signed-off-by: David S. Miller <davem... | 0 | static int wanxl_ioctl(struct net_device *dev, struct ifreq *ifr, int cmd)
{
const size_t size = sizeof(sync_serial_settings);
sync_serial_settings line;
port_t *port = dev_to_port(dev);
if (cmd != SIOCWANDEV)
return hdlc_ioctl(dev, ifr, cmd);
switch (ifr->ifr_settings.type) {
case IF_GET_IFACE:
ifr->ifr_se... | 86,676,060,490,746,650,000,000,000,000,000,000,000 | wanxl.c | 316,013,096,835,404,300,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-1445 | The wanxl_ioctl function in drivers/net/wan/wanxl.c in the Linux kernel before 3.11.7 does not properly initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory via an ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-1445 |
1,328 | linux | 96b340406724d87e4621284ebac5e059d67b2194 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/96b340406724d87e4621284ebac5e059d67b2194 | farsync: fix info leak in ioctl
The fst_get_iface() code fails to initialize the two padding bytes of
struct sync_serial_settings after the ->loopback member. Add an explicit
memset(0) before filling the structure to avoid the info leak.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: David S. ... | 1 | fst_get_iface(struct fst_card_info *card, struct fst_port_info *port,
struct ifreq *ifr)
{
sync_serial_settings sync;
int i;
/* First check what line type is set, we'll default to reporting X.21
* if nothing is set as IF_IFACE_SYNC_SERIAL implies it can't be
* changed
*/
switch (port->hwif) {
case E1... | 123,961,501,830,758,970,000,000,000,000,000,000,000 | None | null | [
"CWE-399"
] | CVE-2014-1444 | The fst_get_iface function in drivers/net/wan/farsync.c in the Linux kernel before 3.11.7 does not properly initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory by leveraging the CAP_NET_ADMIN capability for an SIOCWANDEV ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-1444 |
159,059 | linux | 96b340406724d87e4621284ebac5e059d67b2194 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/96b340406724d87e4621284ebac5e059d67b2194 | farsync: fix info leak in ioctl
The fst_get_iface() code fails to initialize the two padding bytes of
struct sync_serial_settings after the ->loopback member. Add an explicit
memset(0) before filling the structure to avoid the info leak.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: David S. ... | 0 | fst_get_iface(struct fst_card_info *card, struct fst_port_info *port,
struct ifreq *ifr)
{
sync_serial_settings sync;
int i;
/* First check what line type is set, we'll default to reporting X.21
* if nothing is set as IF_IFACE_SYNC_SERIAL implies it can't be
* changed
*/
switch (port->hwif) {
case E1... | 135,157,837,950,152,400,000,000,000,000,000,000,000 | None | null | [
"CWE-399"
] | CVE-2014-1444 | The fst_get_iface function in drivers/net/wan/farsync.c in the Linux kernel before 3.11.7 does not properly initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory by leveraging the CAP_NET_ADMIN capability for an SIOCWANDEV ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-1444 |
1,335 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 1 | static int futex_wait(u32 __user *uaddr, int fshared,
u32 val, ktime_t *abs_time, u32 bitset, int clockrt)
{
struct hrtimer_sleeper timeout, *to = NULL;
struct restart_block *restart;
struct futex_hash_bucket *hb;
struct futex_q q;
int ret;
if (!bitset)
return -EINVAL;
q.pi_state = NULL;
q.bitset = ... | 173,721,295,716,039,500,000,000,000,000,000,000,000 | futex.c | 310,482,782,767,060,830,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
159,064 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 0 | static int futex_wait(u32 __user *uaddr, int fshared,
u32 val, ktime_t *abs_time, u32 bitset, int clockrt)
{
struct hrtimer_sleeper timeout, *to = NULL;
struct restart_block *restart;
struct futex_hash_bucket *hb;
struct futex_q q;
int ret;
if (!bitset)
return -EINVAL;
q.pi_state = NULL;
q.bitset = ... | 77,081,148,455,405,300,000,000,000,000,000,000,000 | futex.c | 161,006,216,331,975,570,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
1,339 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 1 | static __always_inline int __do_follow_link(struct path *path, struct nameidata *nd)
{
int error;
void *cookie;
struct dentry *dentry = path->dentry;
touch_atime(path->mnt, dentry);
nd_set_link(nd, NULL);
if (path->mnt != nd->path.mnt) {
path_to_nameidata(path, nd);
dget(dentry);
}
mntget(path->mnt);
... | 256,736,984,301,789,380,000,000,000,000,000,000,000 | namei.c | 213,658,505,254,054,250,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
159,068 | linux | 86acdca1b63e6890540fa19495cfc708beff3d8b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/86acdca1b63e6890540fa19495cfc708beff3d8b | fix autofs/afs/etc. magic mountpoint breakage
We end up trying to kfree() nd.last.name on open("/mnt/tmp", O_CREAT)
if /mnt/tmp is an autofs direct mount. The reason is that nd.last_type
is bogus here; we want LAST_BIND for everything of that kind and we
get LAST_NORM left over from finding parent directory.
So make... | 0 | static __always_inline int __do_follow_link(struct path *path, struct nameidata *nd)
{
int error;
void *cookie;
struct dentry *dentry = path->dentry;
touch_atime(path->mnt, dentry);
nd_set_link(nd, NULL);
if (path->mnt != nd->path.mnt) {
path_to_nameidata(path, nd);
dget(dentry);
}
mntget(path->mnt);
... | 283,501,022,424,318,080,000,000,000,000,000,000,000 | namei.c | 218,929,829,656,010,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0203 | The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. | https://nvd.nist.gov/vuln/detail/CVE-2014-0203 |
1,342 | linux | d8316f3991d207fe32881a9ac20241be8fa2bad0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d8316f3991d207fe32881a9ac20241be8fa2bad0 | vhost: fix total length when packets are too short
When mergeable buffers are disabled, and the
incoming packet is too large for the rx buffer,
get_rx_bufs returns success.
This was intentional in order for make recvmsg
truncate the packet and then handle_rx would
detect err != sock_len and drop it.
Unfortunately we... | 1 | static void handle_rx(struct vhost_net *net)
{
struct vhost_net_virtqueue *nvq = &net->vqs[VHOST_NET_VQ_RX];
struct vhost_virtqueue *vq = &nvq->vq;
unsigned uninitialized_var(in), log;
struct vhost_log *vq_log;
struct msghdr msg = {
.msg_name = NULL,
.msg_namelen = 0,
.msg_control = NULL, /* FIXME: get and h... | 327,050,017,452,533,930,000,000,000,000,000,000,000 | net.c | 84,928,519,751,752,360,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0077 | drivers/vhost/net.c in the Linux kernel before 3.13.10, when mergeable buffers are disabled, does not properly validate packet lengths, which allows guest OS users to cause a denial of service (memory corruption and host OS crash) or possibly gain privileges on the host OS via crafted packets, related to the handle_rx ... | https://nvd.nist.gov/vuln/detail/CVE-2014-0077 |
159,072 | linux | d8316f3991d207fe32881a9ac20241be8fa2bad0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d8316f3991d207fe32881a9ac20241be8fa2bad0 | vhost: fix total length when packets are too short
When mergeable buffers are disabled, and the
incoming packet is too large for the rx buffer,
get_rx_bufs returns success.
This was intentional in order for make recvmsg
truncate the packet and then handle_rx would
detect err != sock_len and drop it.
Unfortunately we... | 0 | static void handle_rx(struct vhost_net *net)
{
struct vhost_net_virtqueue *nvq = &net->vqs[VHOST_NET_VQ_RX];
struct vhost_virtqueue *vq = &nvq->vq;
unsigned uninitialized_var(in), log;
struct vhost_log *vq_log;
struct msghdr msg = {
.msg_name = NULL,
.msg_namelen = 0,
.msg_control = NULL, /* FIXME: get and h... | 19,470,146,897,570,945,000,000,000,000,000,000,000 | net.c | 236,351,763,781,669,720,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0077 | drivers/vhost/net.c in the Linux kernel before 3.13.10, when mergeable buffers are disabled, does not properly validate packet lengths, which allows guest OS users to cause a denial of service (memory corruption and host OS crash) or possibly gain privileges on the host OS via crafted packets, related to the handle_rx ... | https://nvd.nist.gov/vuln/detail/CVE-2014-0077 |
9,283 | linux | d8316f3991d207fe32881a9ac20241be8fa2bad0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d8316f3991d207fe32881a9ac20241be8fa2bad0 | vhost: fix total length when packets are too short
When mergeable buffers are disabled, and the
incoming packet is too large for the rx buffer,
get_rx_bufs returns success.
This was intentional in order for make recvmsg
truncate the packet and then handle_rx would
detect err != sock_len and drop it.
Unfortunately we... | 1 | static int get_rx_bufs(struct vhost_virtqueue *vq,
struct vring_used_elem *heads,
int datalen,
unsigned *iovcount,
struct vhost_log *log,
unsigned *log_num,
unsigned int quota)
{
unsigned int out, in;
int seg = 0;
int headcount = 0;
unsigned d;
int r, nlogs = 0... | 91,983,981,836,047,390,000,000,000,000,000,000,000 | net.c | 340,076,013,592,583,200,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0077 | drivers/vhost/net.c in the Linux kernel before 3.13.10, when mergeable buffers are disabled, does not properly validate packet lengths, which allows guest OS users to cause a denial of service (memory corruption and host OS crash) or possibly gain privileges on the host OS via crafted packets, related to the handle_rx ... | https://nvd.nist.gov/vuln/detail/CVE-2014-0077 |
184,416 | linux | d8316f3991d207fe32881a9ac20241be8fa2bad0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d8316f3991d207fe32881a9ac20241be8fa2bad0 | vhost: fix total length when packets are too short
When mergeable buffers are disabled, and the
incoming packet is too large for the rx buffer,
get_rx_bufs returns success.
This was intentional in order for make recvmsg
truncate the packet and then handle_rx would
detect err != sock_len and drop it.
Unfortunately we... | 0 | static int get_rx_bufs(struct vhost_virtqueue *vq,
struct vring_used_elem *heads,
int datalen,
unsigned *iovcount,
struct vhost_log *log,
unsigned *log_num,
unsigned int quota)
{
unsigned int out, in;
int seg = 0;
int headcount = 0;
unsigned d;
int r, nlogs = 0... | 149,353,274,673,277,750,000,000,000,000,000,000,000 | net.c | 236,351,763,781,669,720,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0077 | drivers/vhost/net.c in the Linux kernel before 3.13.10, when mergeable buffers are disabled, does not properly validate packet lengths, which allows guest OS users to cause a denial of service (memory corruption and host OS crash) or possibly gain privileges on the host OS via crafted packets, related to the handle_rx ... | https://nvd.nist.gov/vuln/detail/CVE-2014-0077 |
1,343 | linux | 5d81de8e8667da7135d3a32a964087c0faf5483f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/5d81de8e8667da7135d3a32a964087c0faf5483f | cifs: ensure that uncached writes handle unmapped areas correctly
It's possible for userland to pass down an iovec via writev() that has a
bogus user pointer in it. If that happens and we're doing an uncached
write, then we can end up getting less bytes than we expect from the
call to iov_iter_copy_from_user. This is ... | 1 | cifs_iovec_write(struct file *file, const struct iovec *iov,
unsigned long nr_segs, loff_t *poffset)
{
unsigned long nr_pages, i;
size_t copied, len, cur_len;
ssize_t total_written = 0;
loff_t offset;
struct iov_iter it;
struct cifsFileInfo *open_file;
struct cifs_tcon *tcon;
struct cifs_sb_info *cifs_... | 82,332,909,522,185,400,000,000,000,000,000,000,000 | file.c | 284,112,246,344,305,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0069 | The cifs_iovec_write function in fs/cifs/file.c in the Linux kernel through 3.13.5 does not properly handle uncached write operations that copy fewer than the requested number of bytes, which allows local users to obtain sensitive information from kernel memory, cause a denial of service (memory corruption and system c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0069 |
159,073 | linux | 5d81de8e8667da7135d3a32a964087c0faf5483f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/5d81de8e8667da7135d3a32a964087c0faf5483f | cifs: ensure that uncached writes handle unmapped areas correctly
It's possible for userland to pass down an iovec via writev() that has a
bogus user pointer in it. If that happens and we're doing an uncached
write, then we can end up getting less bytes than we expect from the
call to iov_iter_copy_from_user. This is ... | 0 | cifs_iovec_write(struct file *file, const struct iovec *iov,
unsigned long nr_segs, loff_t *poffset)
{
unsigned long nr_pages, i;
size_t bytes, copied, len, cur_len;
ssize_t total_written = 0;
loff_t offset;
struct iov_iter it;
struct cifsFileInfo *open_file;
struct cifs_tcon *tcon;
struct cifs_sb_info... | 174,355,598,946,351,240,000,000,000,000,000,000,000 | file.c | 173,681,901,170,196,700,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0069 | The cifs_iovec_write function in fs/cifs/file.c in the Linux kernel through 3.13.5 does not properly handle uncached write operations that copy fewer than the requested number of bytes, which allows local users to obtain sensitive information from kernel memory, cause a denial of service (memory corruption and system c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0069 |
1,345 | linux | 2def2ef2ae5f3990aabdbe8a755911902707d268 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2def2ef2ae5f3990aabdbe8a755911902707d268 | x86, x32: Correct invalid use of user timespec in the kernel
The x32 case for the recvmsg() timout handling is broken:
asmlinkage long compat_sys_recvmmsg(int fd, struct compat_mmsghdr __user *mmsg,
unsigned int vlen, unsigned int flags,
st... | 1 | asmlinkage long compat_sys_recvmmsg(int fd, struct compat_mmsghdr __user *mmsg,
unsigned int vlen, unsigned int flags,
struct compat_timespec __user *timeout)
{
int datagrams;
struct timespec ktspec;
if (flags & MSG_CMSG_COMPAT)
return -EINVAL;
if (COMPAT_USE_64BIT_TIME)
return __sys_recvmm... | 89,530,709,225,040,190,000,000,000,000,000,000,000 | compat.c | 107,634,465,611,674,530,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0038 | The compat_sys_recvmmsg function in net/compat.c in the Linux kernel before 3.13.2, when CONFIG_X86_X32 is enabled, allows local users to gain privileges via a recvmmsg system call with a crafted timeout pointer parameter. | https://nvd.nist.gov/vuln/detail/CVE-2014-0038 |
159,074 | linux | 2def2ef2ae5f3990aabdbe8a755911902707d268 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2def2ef2ae5f3990aabdbe8a755911902707d268 | x86, x32: Correct invalid use of user timespec in the kernel
The x32 case for the recvmsg() timout handling is broken:
asmlinkage long compat_sys_recvmmsg(int fd, struct compat_mmsghdr __user *mmsg,
unsigned int vlen, unsigned int flags,
st... | 0 | asmlinkage long compat_sys_recvmmsg(int fd, struct compat_mmsghdr __user *mmsg,
unsigned int vlen, unsigned int flags,
struct compat_timespec __user *timeout)
{
int datagrams;
struct timespec ktspec;
if (flags & MSG_CMSG_COMPAT)
return -EINVAL;
if (timeout == NULL)
return __sys_recvmmsg(f... | 337,307,036,240,340,000,000,000,000,000,000,000,000 | compat.c | 74,541,694,394,596,630,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0038 | The compat_sys_recvmmsg function in net/compat.c in the Linux kernel before 3.13.2, when CONFIG_X86_X32 is enabled, allows local users to gain privileges via a recvmmsg system call with a crafted timeout pointer parameter. | https://nvd.nist.gov/vuln/detail/CVE-2014-0038 |
1,346 | linux | d558023207e008a4476a3b7bb8706b2a2bf5d84f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d558023207e008a4476a3b7bb8706b2a2bf5d84f | aio: prevent double free in ioctx_alloc
ioctx_alloc() calls aio_setup_ring() to allocate a ring. If aio_setup_ring()
fails to do so it would call aio_free_ring() before returning, but
ioctx_alloc() would call aio_free_ring() again causing a double free of
the ring.
This is easily reproducible from userspace.
Signed-... | 1 | static struct kioctx *ioctx_alloc(unsigned nr_events)
{
struct mm_struct *mm = current->mm;
struct kioctx *ctx;
int err = -ENOMEM;
/*
* We keep track of the number of available ringbuffer slots, to prevent
* overflow (reqs_available), and we also use percpu counters for this.
*
* So since up to half the sl... | 338,752,304,203,713,800,000,000,000,000,000,000,000 | aio.c | 50,064,682,128,123,810,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-7348 | Double free vulnerability in the ioctx_alloc function in fs/aio.c in the Linux kernel before 3.12.4 allows local users to cause a denial of service (system crash) or possibly have unspecified other impact via vectors involving an error condition in the aio_setup_ring function. | https://nvd.nist.gov/vuln/detail/CVE-2013-7348 |
159,075 | linux | d558023207e008a4476a3b7bb8706b2a2bf5d84f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d558023207e008a4476a3b7bb8706b2a2bf5d84f | aio: prevent double free in ioctx_alloc
ioctx_alloc() calls aio_setup_ring() to allocate a ring. If aio_setup_ring()
fails to do so it would call aio_free_ring() before returning, but
ioctx_alloc() would call aio_free_ring() again causing a double free of
the ring.
This is easily reproducible from userspace.
Signed-... | 0 | static struct kioctx *ioctx_alloc(unsigned nr_events)
{
struct mm_struct *mm = current->mm;
struct kioctx *ctx;
int err = -ENOMEM;
/*
* We keep track of the number of available ringbuffer slots, to prevent
* overflow (reqs_available), and we also use percpu counters for this.
*
* So since up to half the sl... | 276,190,195,367,712,840,000,000,000,000,000,000,000 | aio.c | 45,773,526,278,059,400,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-7348 | Double free vulnerability in the ioctx_alloc function in fs/aio.c in the Linux kernel before 3.12.4 allows local users to cause a denial of service (system crash) or possibly have unspecified other impact via vectors involving an error condition in the aio_setup_ring function. | https://nvd.nist.gov/vuln/detail/CVE-2013-7348 |
1,347 | linux | c2349758acf1874e4c2b93fe41d072336f1a31d0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c2349758acf1874e4c2b93fe41d072336f1a31d0 | rds: prevent dereference of a NULL device
Binding might result in a NULL device, which is dereferenced
causing this BUG:
[ 1317.260548] BUG: unable to handle kernel NULL pointer dereference at 000000000000097
4
[ 1317.261847] IP: [<ffffffff84225f52>] rds_ib_laddr_check+0x82/0x110
[ 1317.263315] PGD 418bcb067 PUD 3ceb... | 1 | static int rds_ib_laddr_check(__be32 addr)
{
int ret;
struct rdma_cm_id *cm_id;
struct sockaddr_in sin;
/* Create a CMA ID and try to bind it. This catches both
* IB and iWARP capable NICs.
*/
cm_id = rdma_create_id(NULL, NULL, RDMA_PS_TCP, IB_QPT_RC);
if (IS_ERR(cm_id))
return PTR_ERR(cm_id);
memset(&si... | 264,896,393,456,312,270,000,000,000,000,000,000,000 | ib.c | 188,272,071,066,765,100,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-7339 | The rds_ib_laddr_check function in net/rds/ib.c in the Linux kernel before 3.12.8 allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via a bind system call for an RDS socket on a system that lacks RDS transports. | https://nvd.nist.gov/vuln/detail/CVE-2013-7339 |
159,076 | linux | c2349758acf1874e4c2b93fe41d072336f1a31d0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c2349758acf1874e4c2b93fe41d072336f1a31d0 | rds: prevent dereference of a NULL device
Binding might result in a NULL device, which is dereferenced
causing this BUG:
[ 1317.260548] BUG: unable to handle kernel NULL pointer dereference at 000000000000097
4
[ 1317.261847] IP: [<ffffffff84225f52>] rds_ib_laddr_check+0x82/0x110
[ 1317.263315] PGD 418bcb067 PUD 3ceb... | 0 | static int rds_ib_laddr_check(__be32 addr)
{
int ret;
struct rdma_cm_id *cm_id;
struct sockaddr_in sin;
/* Create a CMA ID and try to bind it. This catches both
* IB and iWARP capable NICs.
*/
cm_id = rdma_create_id(NULL, NULL, RDMA_PS_TCP, IB_QPT_RC);
if (IS_ERR(cm_id))
return PTR_ERR(cm_id);
memset(&si... | 283,561,688,959,135,960,000,000,000,000,000,000,000 | ib.c | 319,722,308,852,302,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-7339 | The rds_ib_laddr_check function in net/rds/ib.c in the Linux kernel before 3.12.8 allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via a bind system call for an RDS socket on a system that lacks RDS transports. | https://nvd.nist.gov/vuln/detail/CVE-2013-7339 |
1,348 | linux | bceaa90240b6019ed73b49965eac7d167610be69 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/bceaa90240b6019ed73b49965eac7d167610be69 | inet: prevent leakage of uninitialized memory to user in recv syscalls
Only update *addr_len when we actually fill in sockaddr, otherwise we
can return uninitialized memory from the stack to the caller in the
recvfrom, recvmmsg and recvmsg syscalls. Drop the the (addr_len == NULL)
checks because we only get called wit... | 1 | static int dgram_recvmsg(struct kiocb *iocb, struct sock *sk,
struct msghdr *msg, size_t len, int noblock, int flags,
int *addr_len)
{
size_t copied = 0;
int err = -EOPNOTSUPP;
struct sk_buff *skb;
struct sockaddr_ieee802154 *saddr;
saddr = (struct sockaddr_ieee802154 *)msg->msg_name;
skb = skb_recv_datagra... | 189,468,429,727,011,170,000,000,000,000,000,000,000 | dgram.c | 336,326,295,596,065,970,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-7265 | The pn_recvmsg function in net/phonet/datagram.c in the Linux kernel before 3.12.4 updates a certain length value before ensuring that an associated data structure has been initialized, which allows local users to obtain sensitive information from kernel stack memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg sys... | https://nvd.nist.gov/vuln/detail/CVE-2013-7265 |
159,077 | linux | bceaa90240b6019ed73b49965eac7d167610be69 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/bceaa90240b6019ed73b49965eac7d167610be69 | inet: prevent leakage of uninitialized memory to user in recv syscalls
Only update *addr_len when we actually fill in sockaddr, otherwise we
can return uninitialized memory from the stack to the caller in the
recvfrom, recvmmsg and recvmsg syscalls. Drop the the (addr_len == NULL)
checks because we only get called wit... | 0 | static int dgram_recvmsg(struct kiocb *iocb, struct sock *sk,
struct msghdr *msg, size_t len, int noblock, int flags,
int *addr_len)
{
size_t copied = 0;
int err = -EOPNOTSUPP;
struct sk_buff *skb;
struct sockaddr_ieee802154 *saddr;
saddr = (struct sockaddr_ieee802154 *)msg->msg_name;
skb = skb_recv_datagra... | 100,384,920,917,171,250,000,000,000,000,000,000,000 | dgram.c | 139,592,560,465,788,050,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-7265 | The pn_recvmsg function in net/phonet/datagram.c in the Linux kernel before 3.12.4 updates a certain length value before ensuring that an associated data structure has been initialized, which allows local users to obtain sensitive information from kernel stack memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg sys... | https://nvd.nist.gov/vuln/detail/CVE-2013-7265 |
1,354 | linux | bceaa90240b6019ed73b49965eac7d167610be69 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/bceaa90240b6019ed73b49965eac7d167610be69 | inet: prevent leakage of uninitialized memory to user in recv syscalls
Only update *addr_len when we actually fill in sockaddr, otherwise we
can return uninitialized memory from the stack to the caller in the
recvfrom, recvmmsg and recvmsg syscalls. Drop the the (addr_len == NULL)
checks because we only get called wit... | 1 | static int l2tp_ip_recvmsg(struct kiocb *iocb, struct sock *sk, struct msghdr *msg,
size_t len, int noblock, int flags, int *addr_len)
{
struct inet_sock *inet = inet_sk(sk);
size_t copied = 0;
int err = -EOPNOTSUPP;
struct sockaddr_in *sin = (struct sockaddr_in *)msg->msg_name;
struct sk_buff *skb;
if (f... | 263,984,241,115,726,000,000,000,000,000,000,000,000 | l2tp_ip.c | 55,758,294,290,170,330,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-7265 | The pn_recvmsg function in net/phonet/datagram.c in the Linux kernel before 3.12.4 updates a certain length value before ensuring that an associated data structure has been initialized, which allows local users to obtain sensitive information from kernel stack memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg sys... | https://nvd.nist.gov/vuln/detail/CVE-2013-7265 |
159,082 | linux | bceaa90240b6019ed73b49965eac7d167610be69 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/bceaa90240b6019ed73b49965eac7d167610be69 | inet: prevent leakage of uninitialized memory to user in recv syscalls
Only update *addr_len when we actually fill in sockaddr, otherwise we
can return uninitialized memory from the stack to the caller in the
recvfrom, recvmmsg and recvmsg syscalls. Drop the the (addr_len == NULL)
checks because we only get called wit... | 0 | static int l2tp_ip_recvmsg(struct kiocb *iocb, struct sock *sk, struct msghdr *msg,
size_t len, int noblock, int flags, int *addr_len)
{
struct inet_sock *inet = inet_sk(sk);
size_t copied = 0;
int err = -EOPNOTSUPP;
struct sockaddr_in *sin = (struct sockaddr_in *)msg->msg_name;
struct sk_buff *skb;
if (f... | 163,720,789,019,024,250,000,000,000,000,000,000,000 | l2tp_ip.c | 100,777,512,744,391,060,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-7265 | The pn_recvmsg function in net/phonet/datagram.c in the Linux kernel before 3.12.4 updates a certain length value before ensuring that an associated data structure has been initialized, which allows local users to obtain sensitive information from kernel stack memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg sys... | https://nvd.nist.gov/vuln/detail/CVE-2013-7265 |
1,355 | linux | bceaa90240b6019ed73b49965eac7d167610be69 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/bceaa90240b6019ed73b49965eac7d167610be69 | inet: prevent leakage of uninitialized memory to user in recv syscalls
Only update *addr_len when we actually fill in sockaddr, otherwise we
can return uninitialized memory from the stack to the caller in the
recvfrom, recvmmsg and recvmsg syscalls. Drop the the (addr_len == NULL)
checks because we only get called wit... | 1 | static int pn_recvmsg(struct kiocb *iocb, struct sock *sk,
struct msghdr *msg, size_t len, int noblock,
int flags, int *addr_len)
{
struct sk_buff *skb = NULL;
struct sockaddr_pn sa;
int rval = -EOPNOTSUPP;
int copylen;
if (flags & ~(MSG_PEEK|MSG_TRUNC|MSG_DONTWAIT|MSG_NOSIGNAL|
MSG_CMSG_COMPAT))
got... | 225,152,650,498,232,850,000,000,000,000,000,000,000 | datagram.c | 134,059,696,568,289,560,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-7265 | The pn_recvmsg function in net/phonet/datagram.c in the Linux kernel before 3.12.4 updates a certain length value before ensuring that an associated data structure has been initialized, which allows local users to obtain sensitive information from kernel stack memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg sys... | https://nvd.nist.gov/vuln/detail/CVE-2013-7265 |
159,083 | linux | bceaa90240b6019ed73b49965eac7d167610be69 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/bceaa90240b6019ed73b49965eac7d167610be69 | inet: prevent leakage of uninitialized memory to user in recv syscalls
Only update *addr_len when we actually fill in sockaddr, otherwise we
can return uninitialized memory from the stack to the caller in the
recvfrom, recvmmsg and recvmsg syscalls. Drop the the (addr_len == NULL)
checks because we only get called wit... | 0 | static int pn_recvmsg(struct kiocb *iocb, struct sock *sk,
struct msghdr *msg, size_t len, int noblock,
int flags, int *addr_len)
{
struct sk_buff *skb = NULL;
struct sockaddr_pn sa;
int rval = -EOPNOTSUPP;
int copylen;
if (flags & ~(MSG_PEEK|MSG_TRUNC|MSG_DONTWAIT|MSG_NOSIGNAL|
MSG_CMSG_COMPAT))
got... | 15,189,874,320,084,298,000,000,000,000,000,000,000 | datagram.c | 177,809,756,297,280,000,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-7265 | The pn_recvmsg function in net/phonet/datagram.c in the Linux kernel before 3.12.4 updates a certain length value before ensuring that an associated data structure has been initialized, which allows local users to obtain sensitive information from kernel stack memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg sys... | https://nvd.nist.gov/vuln/detail/CVE-2013-7265 |
1,357 | linux | f3d3342602f8bcbf37d7c46641cb9bca7618eb1c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f3d3342602f8bcbf37d7c46641cb9bca7618eb1c | net: rework recvmsg handler msg_name and msg_namelen logic
This patch now always passes msg->msg_namelen as 0. recvmsg handlers must
set msg_namelen to the proper size <= sizeof(struct sockaddr_storage)
to return msg_name to the user.
This prevents numerous uninitialized memory leaks we had in the
recvmsg handlers an... | 1 | mISDN_sock_recvmsg(struct kiocb *iocb, struct socket *sock,
struct msghdr *msg, size_t len, int flags)
{
struct sk_buff *skb;
struct sock *sk = sock->sk;
struct sockaddr_mISDN *maddr;
int copied, err;
if (*debug & DEBUG_SOCKET)
printk(KERN_DEBUG "%s: len %d, flags %x ch.nr %d, proto %x\n",
... | 25,902,652,839,543,214,000,000,000,000,000,000,000 | socket.c | 259,087,261,855,917,000,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-7270 | The packet_recvmsg function in net/packet/af_packet.c in the Linux kernel before 3.12.4 updates a certain length value before ensuring that an associated data structure has been initialized, which allows local users to obtain sensitive information from kernel memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg syst... | https://nvd.nist.gov/vuln/detail/CVE-2013-7270 |
159,084 | linux | f3d3342602f8bcbf37d7c46641cb9bca7618eb1c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f3d3342602f8bcbf37d7c46641cb9bca7618eb1c | net: rework recvmsg handler msg_name and msg_namelen logic
This patch now always passes msg->msg_namelen as 0. recvmsg handlers must
set msg_namelen to the proper size <= sizeof(struct sockaddr_storage)
to return msg_name to the user.
This prevents numerous uninitialized memory leaks we had in the
recvmsg handlers an... | 0 | mISDN_sock_recvmsg(struct kiocb *iocb, struct socket *sock,
struct msghdr *msg, size_t len, int flags)
{
struct sk_buff *skb;
struct sock *sk = sock->sk;
int copied, err;
if (*debug & DEBUG_SOCKET)
printk(KERN_DEBUG "%s: len %d, flags %x ch.nr %d, proto %x\n",
__func__, (int)len, flags, _... | 61,596,991,397,244,970,000,000,000,000,000,000,000 | socket.c | 329,479,314,098,057,740,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-7270 | The packet_recvmsg function in net/packet/af_packet.c in the Linux kernel before 3.12.4 updates a certain length value before ensuring that an associated data structure has been initialized, which allows local users to obtain sensitive information from kernel memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg syst... | https://nvd.nist.gov/vuln/detail/CVE-2013-7270 |
1,359 | linux | f3d3342602f8bcbf37d7c46641cb9bca7618eb1c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f3d3342602f8bcbf37d7c46641cb9bca7618eb1c | net: rework recvmsg handler msg_name and msg_namelen logic
This patch now always passes msg->msg_namelen as 0. recvmsg handlers must
set msg_namelen to the proper size <= sizeof(struct sockaddr_storage)
to return msg_name to the user.
This prevents numerous uninitialized memory leaks we had in the
recvmsg handlers an... | 1 | static int atalk_recvmsg(struct kiocb *iocb, struct socket *sock, struct msghdr *msg,
size_t size, int flags)
{
struct sock *sk = sock->sk;
struct sockaddr_at *sat = (struct sockaddr_at *)msg->msg_name;
struct ddpehdr *ddp;
int copied = 0;
int offset = 0;
int err = 0;
struct sk_buff *skb;
skb = skb_r... | 30,146,679,912,109,750,000,000,000,000,000,000,000 | ddp.c | 206,398,089,062,534,550,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-7270 | The packet_recvmsg function in net/packet/af_packet.c in the Linux kernel before 3.12.4 updates a certain length value before ensuring that an associated data structure has been initialized, which allows local users to obtain sensitive information from kernel memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg syst... | https://nvd.nist.gov/vuln/detail/CVE-2013-7270 |
159,086 | linux | f3d3342602f8bcbf37d7c46641cb9bca7618eb1c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f3d3342602f8bcbf37d7c46641cb9bca7618eb1c | net: rework recvmsg handler msg_name and msg_namelen logic
This patch now always passes msg->msg_namelen as 0. recvmsg handlers must
set msg_namelen to the proper size <= sizeof(struct sockaddr_storage)
to return msg_name to the user.
This prevents numerous uninitialized memory leaks we had in the
recvmsg handlers an... | 0 | static int atalk_recvmsg(struct kiocb *iocb, struct socket *sock, struct msghdr *msg,
size_t size, int flags)
{
struct sock *sk = sock->sk;
struct ddpehdr *ddp;
int copied = 0;
int offset = 0;
int err = 0;
struct sk_buff *skb;
skb = skb_recv_datagram(sk, flags & ~MSG_DONTWAIT,
flags & MSG_DONTWA... | 301,533,245,137,500,640,000,000,000,000,000,000,000 | ddp.c | 337,507,981,176,008,570,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-7270 | The packet_recvmsg function in net/packet/af_packet.c in the Linux kernel before 3.12.4 updates a certain length value before ensuring that an associated data structure has been initialized, which allows local users to obtain sensitive information from kernel memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg syst... | https://nvd.nist.gov/vuln/detail/CVE-2013-7270 |
1,370 | linux | f3d3342602f8bcbf37d7c46641cb9bca7618eb1c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f3d3342602f8bcbf37d7c46641cb9bca7618eb1c | net: rework recvmsg handler msg_name and msg_namelen logic
This patch now always passes msg->msg_namelen as 0. recvmsg handlers must
set msg_namelen to the proper size <= sizeof(struct sockaddr_storage)
to return msg_name to the user.
This prevents numerous uninitialized memory leaks we had in the
recvmsg handlers an... | 1 | static int ipx_recvmsg(struct kiocb *iocb, struct socket *sock,
struct msghdr *msg, size_t size, int flags)
{
struct sock *sk = sock->sk;
struct ipx_sock *ipxs = ipx_sk(sk);
struct sockaddr_ipx *sipx = (struct sockaddr_ipx *)msg->msg_name;
struct ipxhdr *ipx = NULL;
struct sk_buff *skb;
int copied, rc;
lock_s... | 112,645,242,093,379,780,000,000,000,000,000,000,000 | af_ipx.c | 127,064,475,985,704,280,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-7270 | The packet_recvmsg function in net/packet/af_packet.c in the Linux kernel before 3.12.4 updates a certain length value before ensuring that an associated data structure has been initialized, which allows local users to obtain sensitive information from kernel memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg syst... | https://nvd.nist.gov/vuln/detail/CVE-2013-7270 |
159,094 | linux | f3d3342602f8bcbf37d7c46641cb9bca7618eb1c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f3d3342602f8bcbf37d7c46641cb9bca7618eb1c | net: rework recvmsg handler msg_name and msg_namelen logic
This patch now always passes msg->msg_namelen as 0. recvmsg handlers must
set msg_namelen to the proper size <= sizeof(struct sockaddr_storage)
to return msg_name to the user.
This prevents numerous uninitialized memory leaks we had in the
recvmsg handlers an... | 0 | static int ipx_recvmsg(struct kiocb *iocb, struct socket *sock,
struct msghdr *msg, size_t size, int flags)
{
struct sock *sk = sock->sk;
struct ipx_sock *ipxs = ipx_sk(sk);
struct sockaddr_ipx *sipx = (struct sockaddr_ipx *)msg->msg_name;
struct ipxhdr *ipx = NULL;
struct sk_buff *skb;
int copied, rc;
lock_s... | 253,355,445,957,566,800,000,000,000,000,000,000,000 | af_ipx.c | 45,846,410,308,896,070,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-7270 | The packet_recvmsg function in net/packet/af_packet.c in the Linux kernel before 3.12.4 updates a certain length value before ensuring that an associated data structure has been initialized, which allows local users to obtain sensitive information from kernel memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg syst... | https://nvd.nist.gov/vuln/detail/CVE-2013-7270 |
1,378 | linux | f3d3342602f8bcbf37d7c46641cb9bca7618eb1c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f3d3342602f8bcbf37d7c46641cb9bca7618eb1c | net: rework recvmsg handler msg_name and msg_namelen logic
This patch now always passes msg->msg_namelen as 0. recvmsg handlers must
set msg_namelen to the proper size <= sizeof(struct sockaddr_storage)
to return msg_name to the user.
This prevents numerous uninitialized memory leaks we had in the
recvmsg handlers an... | 1 | static int nr_recvmsg(struct kiocb *iocb, struct socket *sock,
struct msghdr *msg, size_t size, int flags)
{
struct sock *sk = sock->sk;
struct sockaddr_ax25 *sax = (struct sockaddr_ax25 *)msg->msg_name;
size_t copied;
struct sk_buff *skb;
int er;
/*
* This works for seqpacket too. The receiver has ord... | 122,095,893,171,554,320,000,000,000,000,000,000,000 | af_netrom.c | 227,993,719,544,841,100,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-7270 | The packet_recvmsg function in net/packet/af_packet.c in the Linux kernel before 3.12.4 updates a certain length value before ensuring that an associated data structure has been initialized, which allows local users to obtain sensitive information from kernel memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg syst... | https://nvd.nist.gov/vuln/detail/CVE-2013-7270 |
159,099 | linux | f3d3342602f8bcbf37d7c46641cb9bca7618eb1c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f3d3342602f8bcbf37d7c46641cb9bca7618eb1c | net: rework recvmsg handler msg_name and msg_namelen logic
This patch now always passes msg->msg_namelen as 0. recvmsg handlers must
set msg_namelen to the proper size <= sizeof(struct sockaddr_storage)
to return msg_name to the user.
This prevents numerous uninitialized memory leaks we had in the
recvmsg handlers an... | 0 | static int nr_recvmsg(struct kiocb *iocb, struct socket *sock,
struct msghdr *msg, size_t size, int flags)
{
struct sock *sk = sock->sk;
struct sockaddr_ax25 *sax = (struct sockaddr_ax25 *)msg->msg_name;
size_t copied;
struct sk_buff *skb;
int er;
/*
* This works for seqpacket too. The receiver has ord... | 676,887,041,028,333,700,000,000,000,000,000,000 | af_netrom.c | 121,724,623,326,117,200,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-7270 | The packet_recvmsg function in net/packet/af_packet.c in the Linux kernel before 3.12.4 updates a certain length value before ensuring that an associated data structure has been initialized, which allows local users to obtain sensitive information from kernel memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg syst... | https://nvd.nist.gov/vuln/detail/CVE-2013-7270 |
1,381 | linux | f3d3342602f8bcbf37d7c46641cb9bca7618eb1c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f3d3342602f8bcbf37d7c46641cb9bca7618eb1c | net: rework recvmsg handler msg_name and msg_namelen logic
This patch now always passes msg->msg_namelen as 0. recvmsg handlers must
set msg_namelen to the proper size <= sizeof(struct sockaddr_storage)
to return msg_name to the user.
This prevents numerous uninitialized memory leaks we had in the
recvmsg handlers an... | 1 | static int packet_recvmsg(struct kiocb *iocb, struct socket *sock,
struct msghdr *msg, size_t len, int flags)
{
struct sock *sk = sock->sk;
struct sk_buff *skb;
int copied, err;
struct sockaddr_ll *sll;
int vnet_hdr_len = 0;
err = -EINVAL;
if (flags & ~(MSG_PEEK|MSG_DONTWAIT|MSG_TRUNC|MSG_CMSG_COMPAT... | 264,606,051,361,135,500,000,000,000,000,000,000,000 | af_packet.c | 336,820,861,216,337,700,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-7270 | The packet_recvmsg function in net/packet/af_packet.c in the Linux kernel before 3.12.4 updates a certain length value before ensuring that an associated data structure has been initialized, which allows local users to obtain sensitive information from kernel memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg syst... | https://nvd.nist.gov/vuln/detail/CVE-2013-7270 |
159,102 | linux | f3d3342602f8bcbf37d7c46641cb9bca7618eb1c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f3d3342602f8bcbf37d7c46641cb9bca7618eb1c | net: rework recvmsg handler msg_name and msg_namelen logic
This patch now always passes msg->msg_namelen as 0. recvmsg handlers must
set msg_namelen to the proper size <= sizeof(struct sockaddr_storage)
to return msg_name to the user.
This prevents numerous uninitialized memory leaks we had in the
recvmsg handlers an... | 0 | static int packet_recvmsg(struct kiocb *iocb, struct socket *sock,
struct msghdr *msg, size_t len, int flags)
{
struct sock *sk = sock->sk;
struct sk_buff *skb;
int copied, err;
int vnet_hdr_len = 0;
err = -EINVAL;
if (flags & ~(MSG_PEEK|MSG_DONTWAIT|MSG_TRUNC|MSG_CMSG_COMPAT|MSG_ERRQUEUE))
goto out... | 32,641,932,534,113,580,000,000,000,000,000,000,000 | af_packet.c | 129,730,475,145,871,230,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-7270 | The packet_recvmsg function in net/packet/af_packet.c in the Linux kernel before 3.12.4 updates a certain length value before ensuring that an associated data structure has been initialized, which allows local users to obtain sensitive information from kernel memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg syst... | https://nvd.nist.gov/vuln/detail/CVE-2013-7270 |
1,394 | linux | f3d3342602f8bcbf37d7c46641cb9bca7618eb1c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f3d3342602f8bcbf37d7c46641cb9bca7618eb1c | net: rework recvmsg handler msg_name and msg_namelen logic
This patch now always passes msg->msg_namelen as 0. recvmsg handlers must
set msg_namelen to the proper size <= sizeof(struct sockaddr_storage)
to return msg_name to the user.
This prevents numerous uninitialized memory leaks we had in the
recvmsg handlers an... | 1 | static int x25_recvmsg(struct kiocb *iocb, struct socket *sock,
struct msghdr *msg, size_t size,
int flags)
{
struct sock *sk = sock->sk;
struct x25_sock *x25 = x25_sk(sk);
struct sockaddr_x25 *sx25 = (struct sockaddr_x25 *)msg->msg_name;
size_t copied;
int qbit, header_len;
struct sk_buff *skb;... | 87,996,953,335,419,640,000,000,000,000,000,000,000 | af_x25.c | 108,395,192,628,085,570,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-7270 | The packet_recvmsg function in net/packet/af_packet.c in the Linux kernel before 3.12.4 updates a certain length value before ensuring that an associated data structure has been initialized, which allows local users to obtain sensitive information from kernel memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg syst... | https://nvd.nist.gov/vuln/detail/CVE-2013-7270 |
159,113 | linux | f3d3342602f8bcbf37d7c46641cb9bca7618eb1c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f3d3342602f8bcbf37d7c46641cb9bca7618eb1c | net: rework recvmsg handler msg_name and msg_namelen logic
This patch now always passes msg->msg_namelen as 0. recvmsg handlers must
set msg_namelen to the proper size <= sizeof(struct sockaddr_storage)
to return msg_name to the user.
This prevents numerous uninitialized memory leaks we had in the
recvmsg handlers an... | 0 | static int x25_recvmsg(struct kiocb *iocb, struct socket *sock,
struct msghdr *msg, size_t size,
int flags)
{
struct sock *sk = sock->sk;
struct x25_sock *x25 = x25_sk(sk);
struct sockaddr_x25 *sx25 = (struct sockaddr_x25 *)msg->msg_name;
size_t copied;
int qbit, header_len;
struct sk_buff *skb;... | 74,684,187,989,440,510,000,000,000,000,000,000,000 | af_x25.c | 266,825,946,934,924,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-7270 | The packet_recvmsg function in net/packet/af_packet.c in the Linux kernel before 3.12.4 updates a certain length value before ensuring that an associated data structure has been initialized, which allows local users to obtain sensitive information from kernel memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg syst... | https://nvd.nist.gov/vuln/detail/CVE-2013-7270 |
1,395 | mapserver | 3a10f6b829297dae63492a8c63385044bc6953ed | https://github.com/mapserver/mapserver | https://github.com/mapserver/mapserver/commit/3a10f6b829297dae63492a8c63385044bc6953ed | Fix potential SQL Injection with postgis TIME filters (#4834) | 1 | int msPostGISLayerSetTimeFilter(layerObj *lp, const char *timestring, const char *timefield)
{
char **atimes, **aranges = NULL;
int numtimes=0,i=0,numranges=0;
size_t buffer_size = 512;
char buffer[512], bufferTmp[512];
buffer[0] = '\0';
bufferTmp[0] = '\0';
if (!lp || !timestring || !timefield)
r... | 92,160,701,703,090,280,000,000,000,000,000,000,000 | mappostgis.c | 273,968,548,871,858,860,000,000,000,000,000,000,000 | [
"CWE-89"
] | CVE-2013-7262 | SQL injection vulnerability in the msPostGISLayerSetTimeFilter function in mappostgis.c in MapServer before 6.4.1, when a WMS-Time service is used, allows remote attackers to execute arbitrary SQL commands via a crafted string in a PostGIS TIME filter. | https://nvd.nist.gov/vuln/detail/CVE-2013-7262 |
159,114 | mapserver | 3a10f6b829297dae63492a8c63385044bc6953ed | https://github.com/mapserver/mapserver | https://github.com/mapserver/mapserver/commit/3a10f6b829297dae63492a8c63385044bc6953ed | Fix potential SQL Injection with postgis TIME filters (#4834) | 0 | int msPostGISLayerSetTimeFilter(layerObj *lp, const char *timestring, const char *timefield)
{
char **atimes, **aranges = NULL;
int numtimes=0,i=0,numranges=0;
size_t buffer_size = 512;
char buffer[512], bufferTmp[512];
buffer[0] = '\0';
bufferTmp[0] = '\0';
if (!lp || !timestring || !timefield)
r... | 276,142,830,574,984,400,000,000,000,000,000,000,000 | mappostgis.c | 27,807,219,993,849,040,000,000,000,000,000,000,000 | [
"CWE-89"
] | CVE-2013-7262 | SQL injection vulnerability in the msPostGISLayerSetTimeFilter function in mappostgis.c in MapServer before 6.4.1, when a WMS-Time service is used, allows remote attackers to execute arbitrary SQL commands via a crafted string in a PostGIS TIME filter. | https://nvd.nist.gov/vuln/detail/CVE-2013-7262 |
1,412 | Little-CMS | 91c2db7f2559be504211b283bc3a2c631d6f06d9 | https://github.com/mm2/Little-CMS | https://github.com/mm2/Little-CMS/commit/91c2db7f2559be504211b283bc3a2c631d6f06d9 | Non happy-path fixes | 1 | Curves16Data* CurvesAlloc(cmsContext ContextID, int nCurves, int nElements, cmsToneCurve** G)
{
int i, j;
Curves16Data* c16;
c16 = _cmsMallocZero(ContextID, sizeof(Curves16Data));
if (c16 == NULL) return NULL;
c16 ->nCurves = nCurves;
c16 ->nElements = nElements;
c16 ->Curves = _cmsCalloc... | 147,209,237,771,980,330,000,000,000,000,000,000,000 | cmsopt.c | 290,419,189,479,580,550,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-4160 | Little CMS (lcms2) before 2.5, as used in OpenJDK 7 and possibly other products, allows remote attackers to cause a denial of service (NULL pointer dereference and crash) via vectors related to (1) cmsStageAllocLabV2ToV4curves, (2) cmsPipelineDup, (3) cmsAllocProfileSequenceDescription, (4) CurvesAlloc, and (5) cmsname... | https://nvd.nist.gov/vuln/detail/CVE-2013-4160 |
159,131 | Little-CMS | 91c2db7f2559be504211b283bc3a2c631d6f06d9 | https://github.com/mm2/Little-CMS | https://github.com/mm2/Little-CMS/commit/91c2db7f2559be504211b283bc3a2c631d6f06d9 | Non happy-path fixes | 0 | Curves16Data* CurvesAlloc(cmsContext ContextID, int nCurves, int nElements, cmsToneCurve** G)
{
int i, j;
Curves16Data* c16;
c16 = _cmsMallocZero(ContextID, sizeof(Curves16Data));
if (c16 == NULL) return NULL;
c16 ->nCurves = nCurves;
c16 ->nElements = nElements;
c16 ->Curves = _cmsCalloc... | 132,387,710,894,691,170,000,000,000,000,000,000,000 | None | null | [
"CWE-703"
] | CVE-2013-4160 | Little CMS (lcms2) before 2.5, as used in OpenJDK 7 and possibly other products, allows remote attackers to cause a denial of service (NULL pointer dereference and crash) via vectors related to (1) cmsStageAllocLabV2ToV4curves, (2) cmsPipelineDup, (3) cmsAllocProfileSequenceDescription, (4) CurvesAlloc, and (5) cmsname... | https://nvd.nist.gov/vuln/detail/CVE-2013-4160 |
1,413 | monkey | 15f72c1ee5e0afad20232bdf0fcecab8d62a5d89 | https://github.com/monkey/monkey | https://github.com/monkey/monkey/commit/15f72c1ee5e0afad20232bdf0fcecab8d62a5d89 | Mandril: check decoded URI (fix #92)
Signed-off-by: Eduardo Silva <eduardo@monkey.io> | 1 | int _mkp_stage_30(struct plugin *p,
struct client_session *cs,
struct session_request *sr)
{
mk_ptr_t referer;
(void) p;
(void) cs;
PLUGIN_TRACE("[FD %i] Mandril validating URL", cs->socket);
if (mk_security_check_url(sr->uri) < 0) {
PLUGIN_TRACE("[FD %i] Close connectio... | 131,927,884,398,444,160,000,000,000,000,000,000,000 | mandril.c | 309,060,299,715,844,330,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2182 | The Mandril security plugin in Monkey HTTP Daemon (monkeyd) before 1.5.0 allows remote attackers to bypass access restrictions via a crafted URI, as demonstrated by an encoded forward slash. | https://nvd.nist.gov/vuln/detail/CVE-2013-2182 |
159,132 | monkey | 15f72c1ee5e0afad20232bdf0fcecab8d62a5d89 | https://github.com/monkey/monkey | https://github.com/monkey/monkey/commit/15f72c1ee5e0afad20232bdf0fcecab8d62a5d89 | Mandril: check decoded URI (fix #92)
Signed-off-by: Eduardo Silva <eduardo@monkey.io> | 0 | int _mkp_stage_30(struct plugin *p,
struct client_session *cs,
struct session_request *sr)
{
mk_ptr_t referer;
(void) p;
(void) cs;
PLUGIN_TRACE("[FD %i] Mandril validating URL", cs->socket);
if (mk_security_check_url(sr->uri_processed) < 0) {
PLUGIN_TRACE("[FD %i] Clos... | 187,644,993,211,632,480,000,000,000,000,000,000,000 | mandril.c | 131,134,452,289,846,580,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-2182 | The Mandril security plugin in Monkey HTTP Daemon (monkeyd) before 1.5.0 allows remote attackers to bypass access restrictions via a crafted URI, as demonstrated by an encoded forward slash. | https://nvd.nist.gov/vuln/detail/CVE-2013-2182 |
1,414 | corosync | b3f456a8ceefac6e9f2e9acc2ea0c159d412b595 | https://github.com/corosync/corosync | https://github.com/corosync/corosync/commit/b3f456a8ceefac6e9f2e9acc2ea0c159d412b595 | totemcrypto: fix hmac key initialization
Signed-off-by: Fabio M. Di Nitto <fdinitto@redhat.com>
Reviewed-by: Jan Friesse <jfriesse@redhat.com> | 1 | static int init_nss_hash(struct crypto_instance *instance)
{
PK11SlotInfo* hash_slot = NULL;
SECItem hash_param;
if (!hash_to_nss[instance->crypto_hash_type]) {
return 0;
}
hash_param.type = siBuffer;
hash_param.data = 0;
hash_param.len = 0;
hash_slot = PK11_GetBestSlot(hash_to_nss[instance->crypto_h... | 114,430,622,650,469,530,000,000,000,000,000,000,000 | totemcrypto.c | 276,803,209,648,777,200,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-0250 | The init_nss_hash function in exec/totemcrypto.c in Corosync 2.0 before 2.3 does not properly initialize the HMAC key, which allows remote attackers to cause a denial of service (crash) via a crafted packet. | https://nvd.nist.gov/vuln/detail/CVE-2013-0250 |
159,133 | corosync | b3f456a8ceefac6e9f2e9acc2ea0c159d412b595 | https://github.com/corosync/corosync | https://github.com/corosync/corosync/commit/b3f456a8ceefac6e9f2e9acc2ea0c159d412b595 | totemcrypto: fix hmac key initialization
Signed-off-by: Fabio M. Di Nitto <fdinitto@redhat.com>
Reviewed-by: Jan Friesse <jfriesse@redhat.com> | 0 | static int init_nss_hash(struct crypto_instance *instance)
{
PK11SlotInfo* hash_slot = NULL;
SECItem hash_param;
if (!hash_to_nss[instance->crypto_hash_type]) {
return 0;
}
hash_param.type = siBuffer;
hash_param.data = instance->private_key;
hash_param.len = instance->private_key_len;
hash_slot = PK1... | 331,342,191,064,277,740,000,000,000,000,000,000,000 | totemcrypto.c | 117,685,291,046,935,050,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-0250 | The init_nss_hash function in exec/totemcrypto.c in Corosync 2.0 before 2.3 does not properly initialize the HMAC key, which allows remote attackers to cause a denial of service (crash) via a crafted packet. | https://nvd.nist.gov/vuln/detail/CVE-2013-0250 |
1,415 | linux | 3e10986d1d698140747fcfc2761ec9cb64c1d582 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/3e10986d1d698140747fcfc2761ec9cb64c1d582 | net: guard tcp_set_keepalive() to tcp sockets
Its possible to use RAW sockets to get a crash in
tcp_set_keepalive() / sk_reset_timer()
Fix is to make sure socket is a SOCK_STREAM one.
Reported-by: Dave Jones <davej@redhat.com>
Signed-off-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@da... | 1 | int sock_setsockopt(struct socket *sock, int level, int optname,
char __user *optval, unsigned int optlen)
{
struct sock *sk = sock->sk;
int val;
int valbool;
struct linger ling;
int ret = 0;
/*
* Options without arguments
*/
if (optname == SO_BINDTODEVICE)
return sock_bindtodevice(sk, optval, optl... | 34,524,812,571,381,987,000,000,000,000,000,000,000 | sock.c | 200,974,059,219,055,230,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2012-6657 | The sock_setsockopt function in net/core/sock.c in the Linux kernel before 3.5.7 does not ensure that a keepalive action is associated with a stream socket, which allows local users to cause a denial of service (system crash) by leveraging the ability to create a raw socket. | https://nvd.nist.gov/vuln/detail/CVE-2012-6657 |
159,134 | linux | 3e10986d1d698140747fcfc2761ec9cb64c1d582 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/3e10986d1d698140747fcfc2761ec9cb64c1d582 | net: guard tcp_set_keepalive() to tcp sockets
Its possible to use RAW sockets to get a crash in
tcp_set_keepalive() / sk_reset_timer()
Fix is to make sure socket is a SOCK_STREAM one.
Reported-by: Dave Jones <davej@redhat.com>
Signed-off-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@da... | 0 | int sock_setsockopt(struct socket *sock, int level, int optname,
char __user *optval, unsigned int optlen)
{
struct sock *sk = sock->sk;
int val;
int valbool;
struct linger ling;
int ret = 0;
/*
* Options without arguments
*/
if (optname == SO_BINDTODEVICE)
return sock_bindtodevice(sk, optval, optl... | 329,920,688,017,410,030,000,000,000,000,000,000,000 | sock.c | 263,250,588,183,211,000,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2012-6657 | The sock_setsockopt function in net/core/sock.c in the Linux kernel before 3.5.7 does not ensure that a keepalive action is associated with a stream socket, which allows local users to cause a denial of service (system crash) by leveraging the ability to create a raw socket. | https://nvd.nist.gov/vuln/detail/CVE-2012-6657 |
1,416 | linux | 6f7b0a2a5c0fb03be7c25bd1745baa50582348ef | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6f7b0a2a5c0fb03be7c25bd1745baa50582348ef | futex: Forbid uaddr == uaddr2 in futex_wait_requeue_pi()
If uaddr == uaddr2, then we have broken the rule of only requeueing
from a non-pi futex to a pi futex with this call. If we attempt this,
as the trinity test suite manages to do, we miss early wakeups as
q.key is equal to key2 (because they are the same uaddr). ... | 1 | static int futex_wait_requeue_pi(u32 __user *uaddr, unsigned int flags,
u32 val, ktime_t *abs_time, u32 bitset,
u32 __user *uaddr2)
{
struct hrtimer_sleeper timeout, *to = NULL;
struct rt_mutex_waiter rt_waiter;
struct rt_mutex *pi_mutex = NULL;
struct futex_hash_bucket *hb;
union futex_key key2 = FUTEX_... | 97,517,838,480,806,140,000,000,000,000,000,000,000 | futex.c | 161,971,375,377,535,860,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2012-6647 | The futex_wait_requeue_pi function in kernel/futex.c in the Linux kernel before 3.5.1 does not ensure that calls have two different futex addresses, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via a crafted FUTEX_WAIT_REQUEU... | https://nvd.nist.gov/vuln/detail/CVE-2012-6647 |
159,135 | linux | 6f7b0a2a5c0fb03be7c25bd1745baa50582348ef | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6f7b0a2a5c0fb03be7c25bd1745baa50582348ef | futex: Forbid uaddr == uaddr2 in futex_wait_requeue_pi()
If uaddr == uaddr2, then we have broken the rule of only requeueing
from a non-pi futex to a pi futex with this call. If we attempt this,
as the trinity test suite manages to do, we miss early wakeups as
q.key is equal to key2 (because they are the same uaddr). ... | 0 | static int futex_wait_requeue_pi(u32 __user *uaddr, unsigned int flags,
u32 val, ktime_t *abs_time, u32 bitset,
u32 __user *uaddr2)
{
struct hrtimer_sleeper timeout, *to = NULL;
struct rt_mutex_waiter rt_waiter;
struct rt_mutex *pi_mutex = NULL;
struct futex_hash_bucket *hb;
union futex_key key2 = FUTEX_... | 308,924,688,374,167,840,000,000,000,000,000,000,000 | futex.c | 324,690,632,907,545,300,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2012-6647 | The futex_wait_requeue_pi function in kernel/futex.c in the Linux kernel before 3.5.1 does not ensure that calls have two different futex addresses, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via a crafted FUTEX_WAIT_REQUEU... | https://nvd.nist.gov/vuln/detail/CVE-2012-6647 |
1,418 | radvd | 92e22ca23e52066da2258df8c76a2dca8a428bcc | https://github.com/reubenhwk/radvd | https://github.com/reubenhwk/radvd/commit/92e22ca23e52066da2258df8c76a2dca8a428bcc | set_interface_var() doesn't check interface name and blindly does
fopen(path "/" ifname, "w") on it. As "ifname" is an untrusted input, it
should be checked for ".." and/or "/" in it. Otherwise, an infected
unprivileged daemon may overwrite contents of file named "mtu",
"hoplimit", etc. in arbitrary location with arb... | 1 | set_interface_var(const char *iface,
const char *var, const char *name,
uint32_t val)
{
FILE *fp;
char spath[64+IFNAMSIZ]; /* XXX: magic constant */
if (snprintf(spath, sizeof(spath), var, iface) >= sizeof(spath))
return -1;
if (access(spath, F_OK) != 0)
return -1;
fp = fopen(spath, "w");
if (... | 281,398,530,467,193,600,000,000,000,000,000,000,000 | device-linux.c | 290,895,116,251,977,450,000,000,000,000,000,000,000 | [
"CWE-22"
] | CVE-2011-3602 | Directory traversal vulnerability in device-linux.c in the router advertisement daemon (radvd) before 1.8.2 allows local users to overwrite arbitrary files, and remote attackers to overwrite certain files, via a .. (dot dot) in an interface name. NOTE: this can be leveraged with a symlink to overwrite arbitrary files. | https://nvd.nist.gov/vuln/detail/CVE-2011-3602 |
159,137 | radvd | 92e22ca23e52066da2258df8c76a2dca8a428bcc | https://github.com/reubenhwk/radvd | https://github.com/reubenhwk/radvd/commit/92e22ca23e52066da2258df8c76a2dca8a428bcc | set_interface_var() doesn't check interface name and blindly does
fopen(path "/" ifname, "w") on it. As "ifname" is an untrusted input, it
should be checked for ".." and/or "/" in it. Otherwise, an infected
unprivileged daemon may overwrite contents of file named "mtu",
"hoplimit", etc. in arbitrary location with arb... | 0 | set_interface_var(const char *iface,
const char *var, const char *name,
uint32_t val)
{
FILE *fp;
char spath[64+IFNAMSIZ]; /* XXX: magic constant */
if (snprintf(spath, sizeof(spath), var, iface) >= sizeof(spath))
return -1;
/* No path traversal */
if (strstr(name, "..") || strchr(name, '/'))
retur... | 234,526,254,127,295,000,000,000,000,000,000,000,000 | device-linux.c | 2,524,414,676,181,208,800,000,000,000,000,000,000 | [
"CWE-22"
] | CVE-2011-3602 | Directory traversal vulnerability in device-linux.c in the router advertisement daemon (radvd) before 1.8.2 allows local users to overwrite arbitrary files, and remote attackers to overwrite certain files, via a .. (dot dot) in an interface name. NOTE: this can be leveraged with a symlink to overwrite arbitrary files. | https://nvd.nist.gov/vuln/detail/CVE-2011-3602 |
1,419 | linux | 819cbb120eaec7e014e5abd029260db1ca8c5735 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/819cbb120eaec7e014e5abd029260db1ca8c5735 | staging: comedi: fix infoleak to userspace
driver_name and board_name are pointers to strings, not buffers of size
COMEDI_NAMELEN. Copying COMEDI_NAMELEN bytes of a string containing
less than COMEDI_NAMELEN-1 bytes would leak some unrelated bytes.
Signed-off-by: Vasiliy Kulikov <segoon@openwall.com>
Cc: stable <sta... | 1 | static int do_devinfo_ioctl(struct comedi_device *dev,
struct comedi_devinfo __user *arg,
struct file *file)
{
struct comedi_devinfo devinfo;
const unsigned minor = iminor(file->f_dentry->d_inode);
struct comedi_device_file_info *dev_file_info =
comedi_get_device_file_info(minor);
struct comedi_s... | 274,220,629,135,533,150,000,000,000,000,000,000,000 | comedi_fops.c | 50,834,563,733,571,210,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2011-2909 | The do_devinfo_ioctl function in drivers/staging/comedi/comedi_fops.c in the Linux kernel before 3.1 allows local users to obtain sensitive information from kernel memory via a copy of a short string. | https://nvd.nist.gov/vuln/detail/CVE-2011-2909 |
159,138 | linux | 819cbb120eaec7e014e5abd029260db1ca8c5735 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/819cbb120eaec7e014e5abd029260db1ca8c5735 | staging: comedi: fix infoleak to userspace
driver_name and board_name are pointers to strings, not buffers of size
COMEDI_NAMELEN. Copying COMEDI_NAMELEN bytes of a string containing
less than COMEDI_NAMELEN-1 bytes would leak some unrelated bytes.
Signed-off-by: Vasiliy Kulikov <segoon@openwall.com>
Cc: stable <sta... | 0 | static int do_devinfo_ioctl(struct comedi_device *dev,
struct comedi_devinfo __user *arg,
struct file *file)
{
struct comedi_devinfo devinfo;
const unsigned minor = iminor(file->f_dentry->d_inode);
struct comedi_device_file_info *dev_file_info =
comedi_get_device_file_info(minor);
struct comedi_s... | 77,485,383,042,073,850,000,000,000,000,000,000,000 | comedi_fops.c | 176,383,155,632,752,800,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2011-2909 | The do_devinfo_ioctl function in drivers/staging/comedi/comedi_fops.c in the Linux kernel before 3.1 allows local users to obtain sensitive information from kernel memory via a copy of a short string. | https://nvd.nist.gov/vuln/detail/CVE-2011-2909 |
1,421 | linux | acff81ec2c79492b180fade3c2894425cd35a545 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/acff81ec2c79492b180fade3c2894425cd35a545 | ovl: fix permission checking for setattr
[Al Viro] The bug is in being too enthusiastic about optimizing ->setattr()
away - instead of "copy verbatim with metadata" + "chmod/chown/utimes"
(with the former being always safe and the latter failing in case of
insufficient permissions) it tries to combine these two. Note... | 1 | int ovl_setattr(struct dentry *dentry, struct iattr *attr)
{
int err;
struct dentry *upperdentry;
err = ovl_want_write(dentry);
if (err)
goto out;
upperdentry = ovl_dentry_upper(dentry);
if (upperdentry) {
mutex_lock(&upperdentry->d_inode->i_mutex);
err = notify_change(upperdentry, attr, NULL);
mu... | 126,591,340,298,897,650,000,000,000,000,000,000,000 | inode.c | 334,612,864,203,734,400,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2015-8660 | The ovl_setattr function in fs/overlayfs/inode.c in the Linux kernel through 4.3.3 attempts to merge distinct setattr operations, which allows local users to bypass intended access restrictions and modify the attributes of arbitrary overlay files via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2015-8660 |
159,139 | linux | acff81ec2c79492b180fade3c2894425cd35a545 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/acff81ec2c79492b180fade3c2894425cd35a545 | ovl: fix permission checking for setattr
[Al Viro] The bug is in being too enthusiastic about optimizing ->setattr()
away - instead of "copy verbatim with metadata" + "chmod/chown/utimes"
(with the former being always safe and the latter failing in case of
insufficient permissions) it tries to combine these two. Note... | 0 | int ovl_setattr(struct dentry *dentry, struct iattr *attr)
{
int err;
struct dentry *upperdentry;
err = ovl_want_write(dentry);
if (err)
goto out;
err = ovl_copy_up(dentry);
if (!err) {
upperdentry = ovl_dentry_upper(dentry);
mutex_lock(&upperdentry->d_inode->i_mutex);
err = notify_change(upperden... | 173,545,193,019,712,930,000,000,000,000,000,000,000 | inode.c | 238,499,371,548,774,600,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2015-8660 | The ovl_setattr function in fs/overlayfs/inode.c in the Linux kernel through 4.3.3 attempts to merge distinct setattr operations, which allows local users to bypass intended access restrictions and modify the attributes of arbitrary overlay files via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2015-8660 |
1,433 | linux | 8c7188b23474cca017b3ef354c4a58456f68303a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8c7188b23474cca017b3ef354c4a58456f68303a | RDS: fix race condition when sending a message on unbound socket
Sasha's found a NULL pointer dereference in the RDS connection code when
sending a message to an apparently unbound socket. The problem is caused
by the code checking if the socket is bound in rds_sendmsg(), which checks
the rs_bound_addr field without ... | 1 | int rds_sendmsg(struct socket *sock, struct msghdr *msg, size_t payload_len)
{
struct sock *sk = sock->sk;
struct rds_sock *rs = rds_sk_to_rs(sk);
DECLARE_SOCKADDR(struct sockaddr_in *, usin, msg->msg_name);
__be32 daddr;
__be16 dport;
struct rds_message *rm = NULL;
struct rds_connection *conn;
int ret = 0;
in... | 63,125,872,970,388,840,000,000,000,000,000,000,000 | send.c | 261,842,697,984,098,440,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2015-7990 | Race condition in the rds_sendmsg function in net/rds/sendmsg.c in the Linux kernel before 4.3.3 allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact by using a socket that was not properly bound. NOTE: this vulnerability exists because o... | https://nvd.nist.gov/vuln/detail/CVE-2015-7990 |
159,151 | linux | 8c7188b23474cca017b3ef354c4a58456f68303a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8c7188b23474cca017b3ef354c4a58456f68303a | RDS: fix race condition when sending a message on unbound socket
Sasha's found a NULL pointer dereference in the RDS connection code when
sending a message to an apparently unbound socket. The problem is caused
by the code checking if the socket is bound in rds_sendmsg(), which checks
the rs_bound_addr field without ... | 0 | int rds_sendmsg(struct socket *sock, struct msghdr *msg, size_t payload_len)
{
struct sock *sk = sock->sk;
struct rds_sock *rs = rds_sk_to_rs(sk);
DECLARE_SOCKADDR(struct sockaddr_in *, usin, msg->msg_name);
__be32 daddr;
__be16 dport;
struct rds_message *rm = NULL;
struct rds_connection *conn;
int ret = 0;
in... | 115,968,539,110,625,770,000,000,000,000,000,000,000 | send.c | 203,394,193,812,442,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2015-7990 | Race condition in the rds_sendmsg function in net/rds/sendmsg.c in the Linux kernel before 4.3.3 allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact by using a socket that was not properly bound. NOTE: this vulnerability exists because o... | https://nvd.nist.gov/vuln/detail/CVE-2015-7990 |
1,434 | linux | 4b6184336ebb5c8dc1eae7f7ab46ee608a748b05 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4b6184336ebb5c8dc1eae7f7ab46ee608a748b05 | staging/dgnc: fix info leak in ioctl
The dgnc_mgmt_ioctl() code fails to initialize the 16 _reserved bytes of
struct digi_dinfo after the ->dinfo_nboards member. Add an explicit
memset(0) before filling the structure to avoid the info leak.
Signed-off-by: Salva Peiró <speirofr@gmail.com>
Signed-off-by: Greg Kroah-Har... | 1 | long dgnc_mgmt_ioctl(struct file *file, unsigned int cmd, unsigned long arg)
{
unsigned long flags;
void __user *uarg = (void __user *)arg;
switch (cmd) {
case DIGI_GETDD:
{
/*
* This returns the total number of boards
* in the system, as well as driver version
* and has space for a reserved entry
*... | 193,364,450,923,515,900,000,000,000,000,000,000,000 | dgnc_mgmt.c | 195,319,938,365,409,150,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2015-7885 | The dgnc_mgmt_ioctl function in drivers/staging/dgnc/dgnc_mgmt.c in the Linux kernel through 4.3.3 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2015-7885 |
159,152 | linux | 4b6184336ebb5c8dc1eae7f7ab46ee608a748b05 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4b6184336ebb5c8dc1eae7f7ab46ee608a748b05 | staging/dgnc: fix info leak in ioctl
The dgnc_mgmt_ioctl() code fails to initialize the 16 _reserved bytes of
struct digi_dinfo after the ->dinfo_nboards member. Add an explicit
memset(0) before filling the structure to avoid the info leak.
Signed-off-by: Salva Peiró <speirofr@gmail.com>
Signed-off-by: Greg Kroah-Har... | 0 | long dgnc_mgmt_ioctl(struct file *file, unsigned int cmd, unsigned long arg)
{
unsigned long flags;
void __user *uarg = (void __user *)arg;
switch (cmd) {
case DIGI_GETDD:
{
/*
* This returns the total number of boards
* in the system, as well as driver version
* and has space for a reserved entry
*... | 95,456,831,347,047,410,000,000,000,000,000,000,000 | dgnc_mgmt.c | 13,280,457,984,737,096,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2015-7885 | The dgnc_mgmt_ioctl function in drivers/staging/dgnc/dgnc_mgmt.c in the Linux kernel through 4.3.3 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2015-7885 |
1,435 | linux | eda98796aff0d9bf41094b06811f5def3b4c333c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/eda98796aff0d9bf41094b06811f5def3b4c333c | [media] media/vivid-osd: fix info leak in ioctl
The vivid_fb_ioctl() code fails to initialize the 16 _reserved bytes of
struct fb_vblank after the ->hcount member. Add an explicit
memset(0) before filling the structure to avoid the info leak.
Signed-off-by: Salva Peiró <speirofr@gmail.com>
Signed-off-by: Hans Verkuil... | 1 | static int vivid_fb_ioctl(struct fb_info *info, unsigned cmd, unsigned long arg)
{
struct vivid_dev *dev = (struct vivid_dev *)info->par;
switch (cmd) {
case FBIOGET_VBLANK: {
struct fb_vblank vblank;
vblank.flags = FB_VBLANK_HAVE_COUNT | FB_VBLANK_HAVE_VCOUNT |
FB_VBLANK_HAVE_VSYNC;
vblank.count = ... | 326,103,382,253,395,940,000,000,000,000,000,000,000 | vivid-osd.c | 31,449,737,973,003,174,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2015-7884 | The vivid_fb_ioctl function in drivers/media/platform/vivid/vivid-osd.c in the Linux kernel through 4.3.3 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2015-7884 |
159,153 | linux | eda98796aff0d9bf41094b06811f5def3b4c333c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/eda98796aff0d9bf41094b06811f5def3b4c333c | [media] media/vivid-osd: fix info leak in ioctl
The vivid_fb_ioctl() code fails to initialize the 16 _reserved bytes of
struct fb_vblank after the ->hcount member. Add an explicit
memset(0) before filling the structure to avoid the info leak.
Signed-off-by: Salva Peiró <speirofr@gmail.com>
Signed-off-by: Hans Verkuil... | 0 | static int vivid_fb_ioctl(struct fb_info *info, unsigned cmd, unsigned long arg)
{
struct vivid_dev *dev = (struct vivid_dev *)info->par;
switch (cmd) {
case FBIOGET_VBLANK: {
struct fb_vblank vblank;
memset(&vblank, 0, sizeof(vblank));
vblank.flags = FB_VBLANK_HAVE_COUNT | FB_VBLANK_HAVE_VCOUNT |
FB... | 123,747,704,383,727,260,000,000,000,000,000,000,000 | vivid-osd.c | 260,196,250,403,358,200,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2015-7884 | The vivid_fb_ioctl function in drivers/media/platform/vivid/vivid-osd.c in the Linux kernel through 4.3.3 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2015-7884 |
1,437 | linux | b9a532277938798b53178d5a66af6e2915cb27cf | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b9a532277938798b53178d5a66af6e2915cb27cf | Initialize msg/shm IPC objects before doing ipc_addid()
As reported by Dmitry Vyukov, we really shouldn't do ipc_addid() before
having initialized the IPC object state. Yes, we initialize the IPC
object in a locked state, but with all the lockless RCU lookup work,
that IPC object lock no longer means that the state c... | 1 | static int newque(struct ipc_namespace *ns, struct ipc_params *params)
{
struct msg_queue *msq;
int id, retval;
key_t key = params->key;
int msgflg = params->flg;
msq = ipc_rcu_alloc(sizeof(*msq));
if (!msq)
return -ENOMEM;
msq->q_perm.mode = msgflg & S_IRWXUGO;
msq->q_perm.key = key;
msq->q_perm.security... | 145,137,506,070,763,420,000,000,000,000,000,000,000 | msg.c | 137,063,545,741,306,320,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2015-7613 | Race condition in the IPC object implementation in the Linux kernel through 4.2.3 allows local users to gain privileges by triggering an ipc_addid call that leads to uid and gid comparisons against uninitialized data, related to msg.c, shm.c, and util.c. | https://nvd.nist.gov/vuln/detail/CVE-2015-7613 |
159,155 | linux | b9a532277938798b53178d5a66af6e2915cb27cf | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b9a532277938798b53178d5a66af6e2915cb27cf | Initialize msg/shm IPC objects before doing ipc_addid()
As reported by Dmitry Vyukov, we really shouldn't do ipc_addid() before
having initialized the IPC object state. Yes, we initialize the IPC
object in a locked state, but with all the lockless RCU lookup work,
that IPC object lock no longer means that the state c... | 0 | static int newque(struct ipc_namespace *ns, struct ipc_params *params)
{
struct msg_queue *msq;
int id, retval;
key_t key = params->key;
int msgflg = params->flg;
msq = ipc_rcu_alloc(sizeof(*msq));
if (!msq)
return -ENOMEM;
msq->q_perm.mode = msgflg & S_IRWXUGO;
msq->q_perm.key = key;
msq->q_perm.security... | 98,982,363,477,451,780,000,000,000,000,000,000,000 | msg.c | 277,126,981,187,777,700,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2015-7613 | Race condition in the IPC object implementation in the Linux kernel through 4.2.3 allows local users to gain privileges by triggering an ipc_addid call that leads to uid and gid comparisons against uninitialized data, related to msg.c, shm.c, and util.c. | https://nvd.nist.gov/vuln/detail/CVE-2015-7613 |
1,439 | linux | b9a532277938798b53178d5a66af6e2915cb27cf | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b9a532277938798b53178d5a66af6e2915cb27cf | Initialize msg/shm IPC objects before doing ipc_addid()
As reported by Dmitry Vyukov, we really shouldn't do ipc_addid() before
having initialized the IPC object state. Yes, we initialize the IPC
object in a locked state, but with all the lockless RCU lookup work,
that IPC object lock no longer means that the state c... | 1 | int ipc_addid(struct ipc_ids *ids, struct kern_ipc_perm *new, int size)
{
kuid_t euid;
kgid_t egid;
int id;
int next_id = ids->next_id;
if (size > IPCMNI)
size = IPCMNI;
if (ids->in_use >= size)
return -ENOSPC;
idr_preload(GFP_KERNEL);
spin_lock_init(&new->lock);
new->deleted = false;
rcu_read_lock()... | 260,213,467,137,768,860,000,000,000,000,000,000,000 | util.c | 249,665,259,441,201,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2015-7613 | Race condition in the IPC object implementation in the Linux kernel through 4.2.3 allows local users to gain privileges by triggering an ipc_addid call that leads to uid and gid comparisons against uninitialized data, related to msg.c, shm.c, and util.c. | https://nvd.nist.gov/vuln/detail/CVE-2015-7613 |
159,156 | linux | b9a532277938798b53178d5a66af6e2915cb27cf | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b9a532277938798b53178d5a66af6e2915cb27cf | Initialize msg/shm IPC objects before doing ipc_addid()
As reported by Dmitry Vyukov, we really shouldn't do ipc_addid() before
having initialized the IPC object state. Yes, we initialize the IPC
object in a locked state, but with all the lockless RCU lookup work,
that IPC object lock no longer means that the state c... | 0 | int ipc_addid(struct ipc_ids *ids, struct kern_ipc_perm *new, int size)
{
kuid_t euid;
kgid_t egid;
int id;
int next_id = ids->next_id;
if (size > IPCMNI)
size = IPCMNI;
if (ids->in_use >= size)
return -ENOSPC;
idr_preload(GFP_KERNEL);
spin_lock_init(&new->lock);
new->deleted = false;
rcu_read_lock()... | 293,914,223,638,511,940,000,000,000,000,000,000,000 | util.c | 196,626,097,394,739,130,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2015-7613 | Race condition in the IPC object implementation in the Linux kernel through 4.2.3 allows local users to gain privileges by triggering an ipc_addid call that leads to uid and gid comparisons against uninitialized data, related to msg.c, shm.c, and util.c. | https://nvd.nist.gov/vuln/detail/CVE-2015-7613 |
1,441 | linux | 74e98eb085889b0d2d4908f59f6e00026063014f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/74e98eb085889b0d2d4908f59f6e00026063014f | RDS: verify the underlying transport exists before creating a connection
There was no verification that an underlying transport exists when creating
a connection, this would cause dereferencing a NULL ptr.
It might happen on sockets that weren't properly bound before attempting to
send a message, which will cause a N... | 1 | static struct rds_connection *__rds_conn_create(struct net *net,
__be32 laddr, __be32 faddr,
struct rds_transport *trans, gfp_t gfp,
int is_outgoing)
{
struct rds_connection *conn, *parent = NULL;
struct hlist_head *head = rds_conn_bucket(laddr, faddr);
struct rds_transport *loop_trans;
... | 192,605,127,811,959,800,000,000,000,000,000,000,000 | connection.c | 228,446,343,956,843,780,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2015-6937 | The __rds_conn_create function in net/rds/connection.c in the Linux kernel through 4.2.3 allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact by using a socket that was not properly bound. | https://nvd.nist.gov/vuln/detail/CVE-2015-6937 |
159,157 | linux | 74e98eb085889b0d2d4908f59f6e00026063014f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/74e98eb085889b0d2d4908f59f6e00026063014f | RDS: verify the underlying transport exists before creating a connection
There was no verification that an underlying transport exists when creating
a connection, this would cause dereferencing a NULL ptr.
It might happen on sockets that weren't properly bound before attempting to
send a message, which will cause a N... | 0 | static struct rds_connection *__rds_conn_create(struct net *net,
__be32 laddr, __be32 faddr,
struct rds_transport *trans, gfp_t gfp,
int is_outgoing)
{
struct rds_connection *conn, *parent = NULL;
struct hlist_head *head = rds_conn_bucket(laddr, faddr);
struct rds_transport *loop_trans;
... | 319,028,511,053,587,130,000,000,000,000,000,000,000 | connection.c | 265,543,710,805,754,870,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2015-6937 | The __rds_conn_create function in net/rds/connection.c in the Linux kernel through 4.2.3 allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact by using a socket that was not properly bound. | https://nvd.nist.gov/vuln/detail/CVE-2015-6937 |
1,442 | openssh-portable | 5e75f5198769056089fb06c4d738ab0e5abc66f7 | https://github.com/openssh/openssh-portable | https://github.com/openssh/openssh-portable/commit/5e75f5198769056089fb06c4d738ab0e5abc66f7 | set sshpam_ctxt to NULL after free
Avoids use-after-free in monitor when privsep child is compromised.
Reported by Moritz Jodeit; ok dtucker@ | 1 | mm_answer_pam_free_ctx(int sock, Buffer *m)
{
debug3("%s", __func__);
(sshpam_device.free_ctx)(sshpam_ctxt);
buffer_clear(m);
mm_request_send(sock, MONITOR_ANS_PAM_FREE_CTX, m);
auth_method = "keyboard-interactive";
auth_submethod = "pam";
return (sshpam_authok == sshpam_ctxt);
}
| 205,096,995,958,077,860,000,000,000,000,000,000,000 | monitor.c | 314,905,608,812,230,500,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2015-6564 | Use-after-free vulnerability in the mm_answer_pam_free_ctx function in monitor.c in sshd in OpenSSH before 7.0 on non-OpenBSD platforms might allow local users to gain privileges by leveraging control of the sshd uid to send an unexpectedly early MONITOR_REQ_PAM_FREE_CTX request. | https://nvd.nist.gov/vuln/detail/CVE-2015-6564 |
159,158 | openssh-portable | 5e75f5198769056089fb06c4d738ab0e5abc66f7 | https://github.com/openssh/openssh-portable | https://github.com/openssh/openssh-portable/commit/5e75f5198769056089fb06c4d738ab0e5abc66f7 | set sshpam_ctxt to NULL after free
Avoids use-after-free in monitor when privsep child is compromised.
Reported by Moritz Jodeit; ok dtucker@ | 0 | mm_answer_pam_free_ctx(int sock, Buffer *m)
{
int r = sshpam_authok != NULL && sshpam_authok == sshpam_ctxt;
debug3("%s", __func__);
(sshpam_device.free_ctx)(sshpam_ctxt);
sshpam_ctxt = sshpam_authok = NULL;
buffer_clear(m);
mm_request_send(sock, MONITOR_ANS_PAM_FREE_CTX, m);
auth_method = "keyboard-int... | 258,159,222,298,852,630,000,000,000,000,000,000,000 | monitor.c | 308,195,266,415,961,300,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2015-6564 | Use-after-free vulnerability in the mm_answer_pam_free_ctx function in monitor.c in sshd in OpenSSH before 7.0 on non-OpenBSD platforms might allow local users to gain privileges by leveraging control of the sshd uid to send an unexpectedly early MONITOR_REQ_PAM_FREE_CTX request. | https://nvd.nist.gov/vuln/detail/CVE-2015-6564 |
1,444 | openssh-portable | d4697fe9a28dab7255c60433e4dd23cf7fce8a8b | https://github.com/openssh/openssh-portable | https://github.com/openssh/openssh-portable/commit/d4697fe9a28dab7255c60433e4dd23cf7fce8a8b | Don't resend username to PAM; it already has it.
Pointed out by Moritz Jodeit; ok dtucker@ | 1 | mm_sshpam_init_ctx(Authctxt *authctxt)
{
Buffer m;
int success;
debug3("%s", __func__);
buffer_init(&m);
buffer_put_cstring(&m, authctxt->user);
mm_request_send(pmonitor->m_recvfd, MONITOR_REQ_PAM_INIT_CTX, &m);
debug3("%s: waiting for MONITOR_ANS_PAM_INIT_CTX", __func__);
mm_request_receive_expect(pmoni... | 6,266,967,114,205,273,000,000,000,000,000,000,000 | monitor_wrap.c | 201,186,186,210,011,480,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2015-6563 | The monitor component in sshd in OpenSSH before 7.0 on non-OpenBSD platforms accepts extraneous username data in MONITOR_REQ_PAM_INIT_CTX requests, which allows local users to conduct impersonation attacks by leveraging any SSH login access in conjunction with control of the sshd uid to send a crafted MONITOR_REQ_PWNAM... | https://nvd.nist.gov/vuln/detail/CVE-2015-6563 |
159,159 | openssh-portable | d4697fe9a28dab7255c60433e4dd23cf7fce8a8b | https://github.com/openssh/openssh-portable | https://github.com/openssh/openssh-portable/commit/d4697fe9a28dab7255c60433e4dd23cf7fce8a8b | Don't resend username to PAM; it already has it.
Pointed out by Moritz Jodeit; ok dtucker@ | 0 | mm_sshpam_init_ctx(Authctxt *authctxt)
{
Buffer m;
int success;
debug3("%s", __func__);
buffer_init(&m);
mm_request_send(pmonitor->m_recvfd, MONITOR_REQ_PAM_INIT_CTX, &m);
debug3("%s: waiting for MONITOR_ANS_PAM_INIT_CTX", __func__);
mm_request_receive_expect(pmonitor->m_recvfd, MONITOR_ANS_PAM_INIT_CTX, ... | 70,015,800,832,300,520,000,000,000,000,000,000,000 | monitor_wrap.c | 265,315,564,572,997,160,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2015-6563 | The monitor component in sshd in OpenSSH before 7.0 on non-OpenBSD platforms accepts extraneous username data in MONITOR_REQ_PAM_INIT_CTX requests, which allows local users to conduct impersonation attacks by leveraging any SSH login access in conjunction with control of the sshd uid to send a crafted MONITOR_REQ_PWNAM... | https://nvd.nist.gov/vuln/detail/CVE-2015-6563 |
1,445 | linux | 9a5cbce421a283e6aea3c4007f141735bf9da8c3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9a5cbce421a283e6aea3c4007f141735bf9da8c3 | powerpc/perf: Cap 64bit userspace backtraces to PERF_MAX_STACK_DEPTH
We cap 32bit userspace backtraces to PERF_MAX_STACK_DEPTH
(currently 127), but we forgot to do the same for 64bit backtraces.
Cc: stable@vger.kernel.org
Signed-off-by: Anton Blanchard <anton@samba.org>
Signed-off-by: Michael Ellerman <mpe@ellerman.i... | 1 | static void perf_callchain_user_64(struct perf_callchain_entry *entry,
struct pt_regs *regs)
{
unsigned long sp, next_sp;
unsigned long next_ip;
unsigned long lr;
long level = 0;
struct signal_frame_64 __user *sigframe;
unsigned long __user *fp, *uregs;
next_ip = perf_instruction_pointer(regs);
lr = reg... | 223,862,452,787,017,050,000,000,000,000,000,000,000 | callchain.c | 29,252,321,502,543,094,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2015-6526 | The perf_callchain_user_64 function in arch/powerpc/perf/callchain.c in the Linux kernel before 4.0.2 on ppc64 platforms allows local users to cause a denial of service (infinite loop) via a deep 64-bit userspace backtrace. | https://nvd.nist.gov/vuln/detail/CVE-2015-6526 |
159,160 | linux | 9a5cbce421a283e6aea3c4007f141735bf9da8c3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9a5cbce421a283e6aea3c4007f141735bf9da8c3 | powerpc/perf: Cap 64bit userspace backtraces to PERF_MAX_STACK_DEPTH
We cap 32bit userspace backtraces to PERF_MAX_STACK_DEPTH
(currently 127), but we forgot to do the same for 64bit backtraces.
Cc: stable@vger.kernel.org
Signed-off-by: Anton Blanchard <anton@samba.org>
Signed-off-by: Michael Ellerman <mpe@ellerman.i... | 0 | static void perf_callchain_user_64(struct perf_callchain_entry *entry,
struct pt_regs *regs)
{
unsigned long sp, next_sp;
unsigned long next_ip;
unsigned long lr;
long level = 0;
struct signal_frame_64 __user *sigframe;
unsigned long __user *fp, *uregs;
next_ip = perf_instruction_pointer(regs);
lr = reg... | 51,915,718,280,773,700,000,000,000,000,000,000,000 | callchain.c | 109,509,042,437,136,110,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2015-6526 | The perf_callchain_user_64 function in arch/powerpc/perf/callchain.c in the Linux kernel before 4.0.2 on ppc64 platforms allows local users to cause a denial of service (infinite loop) via a deep 64-bit userspace backtrace. | https://nvd.nist.gov/vuln/detail/CVE-2015-6526 |
1,449 | linux | 7932c0bd7740f4cd2aa168d3ce0199e7af7d72d5 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7932c0bd7740f4cd2aa168d3ce0199e7af7d72d5 | vhost: actually track log eventfd file
While reviewing vhost log code, I found out that log_file is never
set. Note: I haven't tested the change (QEMU doesn't use LOG_FD yet).
Cc: stable@vger.kernel.org
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com> | 1 | long vhost_dev_ioctl(struct vhost_dev *d, unsigned int ioctl, void __user *argp)
{
struct file *eventfp, *filep = NULL;
struct eventfd_ctx *ctx = NULL;
u64 p;
long r;
int i, fd;
/* If you are not the owner, you can become one */
if (ioctl == VHOST_SET_OWNER) {
r = vhost_dev_set_owner(d);
goto done;
}
/* ... | 259,350,127,464,630,780,000,000,000,000,000,000,000 | vhost.c | 299,385,267,607,711,380,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2015-6252 | The vhost_dev_ioctl function in drivers/vhost/vhost.c in the Linux kernel before 4.1.5 allows local users to cause a denial of service (memory consumption) via a VHOST_SET_LOG_FD ioctl call that triggers permanent file-descriptor allocation. | https://nvd.nist.gov/vuln/detail/CVE-2015-6252 |
159,164 | linux | 7932c0bd7740f4cd2aa168d3ce0199e7af7d72d5 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7932c0bd7740f4cd2aa168d3ce0199e7af7d72d5 | vhost: actually track log eventfd file
While reviewing vhost log code, I found out that log_file is never
set. Note: I haven't tested the change (QEMU doesn't use LOG_FD yet).
Cc: stable@vger.kernel.org
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com> | 0 | long vhost_dev_ioctl(struct vhost_dev *d, unsigned int ioctl, void __user *argp)
{
struct file *eventfp, *filep = NULL;
struct eventfd_ctx *ctx = NULL;
u64 p;
long r;
int i, fd;
/* If you are not the owner, you can become one */
if (ioctl == VHOST_SET_OWNER) {
r = vhost_dev_set_owner(d);
goto done;
}
/* ... | 205,836,242,087,737,570,000,000,000,000,000,000,000 | vhost.c | 264,009,302,892,557,900,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2015-6252 | The vhost_dev_ioctl function in drivers/vhost/vhost.c in the Linux kernel before 4.1.5 allows local users to cause a denial of service (memory consumption) via a VHOST_SET_LOG_FD ioctl call that triggers permanent file-descriptor allocation. | https://nvd.nist.gov/vuln/detail/CVE-2015-6252 |
1,450 | miniupnp | 79cca974a4c2ab1199786732a67ff6d898051b78 | https://github.com/miniupnp/miniupnp | https://github.com/miniupnp/miniupnp/commit/79cca974a4c2ab1199786732a67ff6d898051b78 | igd_desc_parse.c: fix buffer overflow | 1 | void IGDstartelt(void * d, const char * name, int l)
{
struct IGDdatas * datas = (struct IGDdatas *)d;
memcpy( datas->cureltname, name, l);
datas->cureltname[l] = '\0';
datas->level++;
if( (l==7) && !memcmp(name, "service", l) ) {
datas->tmp.controlurl[0] = '\0';
datas->tmp.eventsuburl[0] = '\0';
datas... | 81,376,760,744,966,150,000,000,000,000,000,000,000 | igd_desc_parse.c | 340,208,766,696,793,100,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-6031 | Buffer overflow in the IGDstartelt function in igd_desc_parse.c in the MiniUPnP client (aka MiniUPnPc) before 1.9.20150917 allows remote UPNP servers to cause a denial of service (application crash) and possibly execute arbitrary code via an "oversized" XML element name. | https://nvd.nist.gov/vuln/detail/CVE-2015-6031 |
159,165 | miniupnp | 79cca974a4c2ab1199786732a67ff6d898051b78 | https://github.com/miniupnp/miniupnp | https://github.com/miniupnp/miniupnp/commit/79cca974a4c2ab1199786732a67ff6d898051b78 | igd_desc_parse.c: fix buffer overflow | 0 | void IGDstartelt(void * d, const char * name, int l)
{
struct IGDdatas * datas = (struct IGDdatas *)d;
if(l >= MINIUPNPC_URL_MAXSIZE)
l = MINIUPNPC_URL_MAXSIZE-1;
memcpy(datas->cureltname, name, l);
datas->cureltname[l] = '\0';
datas->level++;
if( (l==7) && !memcmp(name, "service", l) ) {
datas->tmp.con... | 214,139,005,921,978,270,000,000,000,000,000,000,000 | igd_desc_parse.c | 200,098,817,148,872,830,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-6031 | Buffer overflow in the IGDstartelt function in igd_desc_parse.c in the MiniUPnP client (aka MiniUPnPc) before 1.9.20150917 allows remote UPNP servers to cause a denial of service (application crash) and possibly execute arbitrary code via an "oversized" XML element name. | https://nvd.nist.gov/vuln/detail/CVE-2015-6031 |
1,451 | linux | f15133df088ecadd141ea1907f2c96df67c729f0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f15133df088ecadd141ea1907f2c96df67c729f0 | path_openat(): fix double fput()
path_openat() jumps to the wrong place after do_tmpfile() - it has
already done path_cleanup() (as part of path_lookupat() called by
do_tmpfile()), so doing that again can lead to double fput().
Cc: stable@vger.kernel.org # v3.11+
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> | 1 | static struct file *path_openat(int dfd, struct filename *pathname,
struct nameidata *nd, const struct open_flags *op, int flags)
{
struct file *file;
struct path path;
int opened = 0;
int error;
file = get_empty_filp();
if (IS_ERR(file))
return file;
file->f_flags = op->open_flag;
if (unlikely(file->f... | 75,770,052,784,686,880,000,000,000,000,000,000,000 | namei.c | 323,949,164,317,720,170,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2015-5706 | Use-after-free vulnerability in the path_openat function in fs/namei.c in the Linux kernel 3.x and 4.x before 4.0.4 allows local users to cause a denial of service or possibly have unspecified other impact via O_TMPFILE filesystem operations that leverage a duplicate cleanup operation. | https://nvd.nist.gov/vuln/detail/CVE-2015-5706 |
159,166 | linux | f15133df088ecadd141ea1907f2c96df67c729f0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f15133df088ecadd141ea1907f2c96df67c729f0 | path_openat(): fix double fput()
path_openat() jumps to the wrong place after do_tmpfile() - it has
already done path_cleanup() (as part of path_lookupat() called by
do_tmpfile()), so doing that again can lead to double fput().
Cc: stable@vger.kernel.org # v3.11+
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> | 0 | static struct file *path_openat(int dfd, struct filename *pathname,
struct nameidata *nd, const struct open_flags *op, int flags)
{
struct file *file;
struct path path;
int opened = 0;
int error;
file = get_empty_filp();
if (IS_ERR(file))
return file;
file->f_flags = op->open_flag;
if (unlikely(file->f... | 47,110,058,767,801,050,000,000,000,000,000,000,000 | namei.c | 172,714,152,611,612,400,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2015-5706 | Use-after-free vulnerability in the path_openat function in fs/namei.c in the Linux kernel 3.x and 4.x before 4.0.4 allows local users to cause a denial of service or possibly have unspecified other impact via O_TMPFILE filesystem operations that leverage a duplicate cleanup operation. | https://nvd.nist.gov/vuln/detail/CVE-2015-5706 |
1,452 | linux | b6878d9e03043695dbf3fa1caa6dfc09db225b16 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b6878d9e03043695dbf3fa1caa6dfc09db225b16 | md: use kzalloc() when bitmap is disabled
In drivers/md/md.c get_bitmap_file() uses kmalloc() for creating a
mdu_bitmap_file_t called "file".
5769 file = kmalloc(sizeof(*file), GFP_NOIO);
5770 if (!file)
5771 return -ENOMEM;
This structure is copied to user space at the end of the fun... | 1 | static int get_bitmap_file(struct mddev *mddev, void __user * arg)
{
mdu_bitmap_file_t *file = NULL; /* too big for stack allocation */
char *ptr;
int err;
file = kmalloc(sizeof(*file), GFP_NOIO);
if (!file)
return -ENOMEM;
err = 0;
spin_lock(&mddev->lock);
/* bitmap disabled, zero the first byte and ... | 233,692,859,281,768,060,000,000,000,000,000,000,000 | md.c | 31,073,914,606,817,860,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2015-5697 | The get_bitmap_file function in drivers/md/md.c in the Linux kernel before 4.1.6 does not initialize a certain bitmap data structure, which allows local users to obtain sensitive information from kernel memory via a GET_BITMAP_FILE ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2015-5697 |
159,167 | linux | b6878d9e03043695dbf3fa1caa6dfc09db225b16 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b6878d9e03043695dbf3fa1caa6dfc09db225b16 | md: use kzalloc() when bitmap is disabled
In drivers/md/md.c get_bitmap_file() uses kmalloc() for creating a
mdu_bitmap_file_t called "file".
5769 file = kmalloc(sizeof(*file), GFP_NOIO);
5770 if (!file)
5771 return -ENOMEM;
This structure is copied to user space at the end of the fun... | 0 | static int get_bitmap_file(struct mddev *mddev, void __user * arg)
{
mdu_bitmap_file_t *file = NULL; /* too big for stack allocation */
char *ptr;
int err;
file = kzalloc(sizeof(*file), GFP_NOIO);
if (!file)
return -ENOMEM;
err = 0;
spin_lock(&mddev->lock);
/* bitmap disabled, zero the first byte and ... | 255,571,174,383,150,770,000,000,000,000,000,000,000 | md.c | 36,136,546,277,666,100,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2015-5697 | The get_bitmap_file function in drivers/md/md.c in the Linux kernel before 4.1.6 does not initialize a certain bitmap data structure, which allows local users to obtain sensitive information from kernel memory via a GET_BITMAP_FILE ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2015-5697 |
1,461 | abrt | 3c1b60cfa62d39e5fff5a53a5bc53dae189e740e | https://github.com/abrt/abrt | https://github.com/abrt/abrt/commit/3c1b60cfa62d39e5fff5a53a5bc53dae189e740e | ccpp: save abrt core files only to new files
Prior this commit abrt-hook-ccpp saved a core file generated by a
process running a program whose name starts with "abrt" in
DUMP_LOCATION/$(basename program)-coredump. If the file was a symlink,
the hook followed and wrote core file to the symlink's target.
Addresses CVE-... | 1 | int main(int argc, char** argv)
{
/* Kernel starts us with all fd's closed.
* But it's dangerous:
* fprintf(stderr) can dump messages into random fds, etc.
* Ensure that if any of fd 0,1,2 is closed, we open it to /dev/null.
*/
int fd = xopen("/dev/null", O_RDWR);
while (fd < 2)
... | 287,347,886,890,565,600,000,000,000,000,000,000,000 | None | null | [
"CWE-59"
] | CVE-2015-5287 | The abrt-hook-ccpp help program in Automatic Bug Reporting Tool (ABRT) before 2.7.1 allows local users with certain permissions to gain privileges via a symlink attack on a file with a predictable name, as demonstrated by /var/tmp/abrt/abrt-hax-coredump or /var/spool/abrt/abrt-hax-coredump. | https://nvd.nist.gov/vuln/detail/CVE-2015-5287 |
159,171 | abrt | 3c1b60cfa62d39e5fff5a53a5bc53dae189e740e | https://github.com/abrt/abrt | https://github.com/abrt/abrt/commit/3c1b60cfa62d39e5fff5a53a5bc53dae189e740e | ccpp: save abrt core files only to new files
Prior this commit abrt-hook-ccpp saved a core file generated by a
process running a program whose name starts with "abrt" in
DUMP_LOCATION/$(basename program)-coredump. If the file was a symlink,
the hook followed and wrote core file to the symlink's target.
Addresses CVE-... | 0 | int main(int argc, char** argv)
{
/* Kernel starts us with all fd's closed.
* But it's dangerous:
* fprintf(stderr) can dump messages into random fds, etc.
* Ensure that if any of fd 0,1,2 is closed, we open it to /dev/null.
*/
int fd = xopen("/dev/null", O_RDWR);
while (fd < 2)
... | 259,214,787,507,265,050,000,000,000,000,000,000,000 | None | null | [
"CWE-59"
] | CVE-2015-5287 | The abrt-hook-ccpp help program in Automatic Bug Reporting Tool (ABRT) before 2.7.1 allows local users with certain permissions to gain privileges via a symlink attack on a file with a predictable name, as demonstrated by /var/tmp/abrt/abrt-hax-coredump or /var/spool/abrt/abrt-hax-coredump. | https://nvd.nist.gov/vuln/detail/CVE-2015-5287 |
1,463 | linux | 8e2d61e0aed2b7c4ecb35844fe07e0b2b762dee4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8e2d61e0aed2b7c4ecb35844fe07e0b2b762dee4 | sctp: fix race on protocol/netns initialization
Consider sctp module is unloaded and is being requested because an user
is creating a sctp socket.
During initialization, sctp will add the new protocol type and then
initialize pernet subsys:
status = sctp_v4_protosw_init();
if (status)
... | 1 | static __init int sctp_init(void)
{
int i;
int status = -EINVAL;
unsigned long goal;
unsigned long limit;
int max_share;
int order;
sock_skb_cb_check_size(sizeof(struct sctp_ulpevent));
/* Allocate bind_bucket and chunk caches. */
status = -ENOBUFS;
sctp_bucket_cachep = kmem_cache_create("sctp_bind_bucket",... | 167,189,804,297,399,060,000,000,000,000,000,000,000 | protocol.c | 19,924,814,074,907,472,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-5283 | The sctp_init function in net/sctp/protocol.c in the Linux kernel before 4.2.3 has an incorrect sequence of protocol-initialization steps, which allows local users to cause a denial of service (panic or memory corruption) by creating SCTP sockets before all of the steps have finished. | https://nvd.nist.gov/vuln/detail/CVE-2015-5283 |
159,173 | linux | 8e2d61e0aed2b7c4ecb35844fe07e0b2b762dee4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8e2d61e0aed2b7c4ecb35844fe07e0b2b762dee4 | sctp: fix race on protocol/netns initialization
Consider sctp module is unloaded and is being requested because an user
is creating a sctp socket.
During initialization, sctp will add the new protocol type and then
initialize pernet subsys:
status = sctp_v4_protosw_init();
if (status)
... | 0 | static __init int sctp_init(void)
{
int i;
int status = -EINVAL;
unsigned long goal;
unsigned long limit;
int max_share;
int order;
sock_skb_cb_check_size(sizeof(struct sctp_ulpevent));
/* Allocate bind_bucket and chunk caches. */
status = -ENOBUFS;
sctp_bucket_cachep = kmem_cache_create("sctp_bind_bucket",... | 256,431,513,243,984,970,000,000,000,000,000,000,000 | protocol.c | 94,028,047,180,364,870,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-5283 | The sctp_init function in net/sctp/protocol.c in the Linux kernel before 4.2.3 has an incorrect sequence of protocol-initialization steps, which allows local users to cause a denial of service (panic or memory corruption) by creating SCTP sockets before all of the steps have finished. | https://nvd.nist.gov/vuln/detail/CVE-2015-5283 |
1,466 | abrt | 50ee8130fb4cd4ef1af7682a2c85dd99cb99424e | https://github.com/abrt/abrt | https://github.com/abrt/abrt/commit/50ee8130fb4cd4ef1af7682a2c85dd99cb99424e | a-a-i-d-to-abrt-cache: make own random temporary directory
The set-user-ID wrapper must use own new temporary directory in order to
avoid security issues with unpacking specially crafted debuginfo
packages that might be used to create files or symlinks anywhere on the
file system as the abrt user.
Withot the forking ... | 1 | int main(int argc, char **argv)
{
/* I18n */
setlocale(LC_ALL, "");
#if ENABLE_NLS
bindtextdomain(PACKAGE, LOCALEDIR);
textdomain(PACKAGE);
#endif
abrt_init(argv);
/* Can't keep these strings/structs static: _() doesn't support that */
const char *program_usage_string = _(
"& [-y] ... | 92,934,402,516,180,260,000,000,000,000,000,000,000 | None | null | [
"CWE-59"
] | CVE-2015-5273 | The abrt-action-install-debuginfo-to-abrt-cache help program in Automatic Bug Reporting Tool (ABRT) before 2.7.1 allows local users to write to arbitrary files via a symlink attack on unpacked.cpio in a pre-created directory with a predictable name in /var/tmp. | https://nvd.nist.gov/vuln/detail/CVE-2015-5273 |
159,176 | abrt | 50ee8130fb4cd4ef1af7682a2c85dd99cb99424e | https://github.com/abrt/abrt | https://github.com/abrt/abrt/commit/50ee8130fb4cd4ef1af7682a2c85dd99cb99424e | a-a-i-d-to-abrt-cache: make own random temporary directory
The set-user-ID wrapper must use own new temporary directory in order to
avoid security issues with unpacking specially crafted debuginfo
packages that might be used to create files or symlinks anywhere on the
file system as the abrt user.
Withot the forking ... | 0 | int main(int argc, char **argv)
{
/* I18n */
setlocale(LC_ALL, "");
#if ENABLE_NLS
bindtextdomain(PACKAGE, LOCALEDIR);
textdomain(PACKAGE);
#endif
abrt_init(argv);
/* Can't keep these strings/structs static: _() doesn't support that */
const char *program_usage_string = _(
"& [-y] ... | 246,817,441,065,481,750,000,000,000,000,000,000,000 | None | null | [
"CWE-59"
] | CVE-2015-5273 | The abrt-action-install-debuginfo-to-abrt-cache help program in Automatic Bug Reporting Tool (ABRT) before 2.7.1 allows local users to write to arbitrary files via a symlink attack on unpacked.cpio in a pre-created directory with a predictable name in /var/tmp. | https://nvd.nist.gov/vuln/detail/CVE-2015-5273 |
1,467 | linux | 48900cb6af4282fa0fb6ff4d72a81aa3dadb5c39 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/48900cb6af4282fa0fb6ff4d72a81aa3dadb5c39 | virtio-net: drop NETIF_F_FRAGLIST
virtio declares support for NETIF_F_FRAGLIST, but assumes
that there are at most MAX_SKB_FRAGS + 2 fragments which isn't
always true with a fraglist.
A longer fraglist in the skb will make the call to skb_to_sgvec overflow
the sg array, leading to memory corruption.
Drop NETIF_F_FRA... | 1 | static int virtnet_probe(struct virtio_device *vdev)
{
int i, err;
struct net_device *dev;
struct virtnet_info *vi;
u16 max_queue_pairs;
if (!vdev->config->get) {
dev_err(&vdev->dev, "%s failure: config access disabled\n",
__func__);
return -EINVAL;
}
if (!virtnet_validate_features(vdev))
return -EINV... | 286,743,572,691,752,180,000,000,000,000,000,000,000 | virtio_net.c | 226,259,448,298,505,000,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-5156 | The virtnet_probe function in drivers/net/virtio_net.c in the Linux kernel before 4.2 attempts to support a FRAGLIST feature without proper memory allocation, which allows guest OS users to cause a denial of service (buffer overflow and memory corruption) via a crafted sequence of fragmented packets. | https://nvd.nist.gov/vuln/detail/CVE-2015-5156 |
159,177 | linux | 48900cb6af4282fa0fb6ff4d72a81aa3dadb5c39 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/48900cb6af4282fa0fb6ff4d72a81aa3dadb5c39 | virtio-net: drop NETIF_F_FRAGLIST
virtio declares support for NETIF_F_FRAGLIST, but assumes
that there are at most MAX_SKB_FRAGS + 2 fragments which isn't
always true with a fraglist.
A longer fraglist in the skb will make the call to skb_to_sgvec overflow
the sg array, leading to memory corruption.
Drop NETIF_F_FRA... | 0 | static int virtnet_probe(struct virtio_device *vdev)
{
int i, err;
struct net_device *dev;
struct virtnet_info *vi;
u16 max_queue_pairs;
if (!vdev->config->get) {
dev_err(&vdev->dev, "%s failure: config access disabled\n",
__func__);
return -EINVAL;
}
if (!virtnet_validate_features(vdev))
return -EINV... | 337,903,787,973,559,850,000,000,000,000,000,000,000 | virtio_net.c | 233,518,906,966,851,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-5156 | The virtnet_probe function in drivers/net/virtio_net.c in the Linux kernel before 4.2 attempts to support a FRAGLIST feature without proper memory allocation, which allows guest OS users to cause a denial of service (buffer overflow and memory corruption) via a crafted sequence of fragmented packets. | https://nvd.nist.gov/vuln/detail/CVE-2015-5156 |
1,469 | libmspack | 18b6a2cc0b87536015bedd4f7763e6b02d5aa4f3 | https://github.com/kyz/libmspack | https://github.com/kyz/libmspack/commit/18b6a2cc0b87536015bedd4f7763e6b02d5aa4f3 | Prevent a 1-byte underread of the input buffer if an odd-sized data block comes just before an uncompressed block header | 1 | int lzxd_decompress(struct lzxd_stream *lzx, off_t out_bytes) {
/* bitstream and huffman reading variables */
register unsigned int bit_buffer;
register int bits_left, i=0;
unsigned char *i_ptr, *i_end;
register unsigned short sym;
int match_length, length_footer, extra, verbatim_bits, bytes_todo;
int th... | 301,703,386,296,293,370,000,000,000,000,000,000,000 | lzxd.c | 337,003,730,914,340,000,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2015-4471 | Off-by-one error in the lzxd_decompress function in lzxd.c in libmspack before 0.5 allows remote attackers to cause a denial of service (buffer under-read and application crash) via a crafted CAB archive. | https://nvd.nist.gov/vuln/detail/CVE-2015-4471 |
159,179 | libmspack | 18b6a2cc0b87536015bedd4f7763e6b02d5aa4f3 | https://github.com/kyz/libmspack | https://github.com/kyz/libmspack/commit/18b6a2cc0b87536015bedd4f7763e6b02d5aa4f3 | Prevent a 1-byte underread of the input buffer if an odd-sized data block comes just before an uncompressed block header | 0 | int lzxd_decompress(struct lzxd_stream *lzx, off_t out_bytes) {
/* bitstream and huffman reading variables */
register unsigned int bit_buffer;
register int bits_left, i=0;
unsigned char *i_ptr, *i_end;
register unsigned short sym;
int match_length, length_footer, extra, verbatim_bits, bytes_todo;
int th... | 38,707,763,100,156,243,000,000,000,000,000,000,000 | lzxd.c | 195,696,769,726,294,100,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2015-4471 | Off-by-one error in the lzxd_decompress function in lzxd.c in libmspack before 0.5 allows remote attackers to cause a denial of service (buffer under-read and application crash) via a crafted CAB archive. | https://nvd.nist.gov/vuln/detail/CVE-2015-4471 |
1,470 | linux | 23b133bdc452aa441fcb9b82cbf6dd05cfd342d0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/23b133bdc452aa441fcb9b82cbf6dd05cfd342d0 | udf: Check length of extended attributes and allocation descriptors
Check length of extended attributes and allocation descriptors when
loading inodes from disk. Otherwise corrupted filesystems could confuse
the code and make the kernel oops.
Reported-by: Carl Henrik Lunde <chlunde@ping.uio.no>
CC: stable@vger.kernel... | 1 | static int udf_read_inode(struct inode *inode, bool hidden_inode)
{
struct buffer_head *bh = NULL;
struct fileEntry *fe;
struct extendedFileEntry *efe;
uint16_t ident;
struct udf_inode_info *iinfo = UDF_I(inode);
struct udf_sb_info *sbi = UDF_SB(inode->i_sb);
struct kernel_lb_addr *iloc = &iinfo->i_location;
un... | 154,377,499,296,836,300,000,000,000,000,000,000,000 | None | null | [
"CWE-189"
] | CVE-2015-4167 | The udf_read_inode function in fs/udf/inode.c in the Linux kernel before 3.19.1 does not validate certain length values, which allows local users to cause a denial of service (incorrect data representation or integer overflow, and OOPS) via a crafted UDF filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2015-4167 |
159,180 | linux | 23b133bdc452aa441fcb9b82cbf6dd05cfd342d0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/23b133bdc452aa441fcb9b82cbf6dd05cfd342d0 | udf: Check length of extended attributes and allocation descriptors
Check length of extended attributes and allocation descriptors when
loading inodes from disk. Otherwise corrupted filesystems could confuse
the code and make the kernel oops.
Reported-by: Carl Henrik Lunde <chlunde@ping.uio.no>
CC: stable@vger.kernel... | 0 | static int udf_read_inode(struct inode *inode, bool hidden_inode)
{
struct buffer_head *bh = NULL;
struct fileEntry *fe;
struct extendedFileEntry *efe;
uint16_t ident;
struct udf_inode_info *iinfo = UDF_I(inode);
struct udf_sb_info *sbi = UDF_SB(inode->i_sb);
struct kernel_lb_addr *iloc = &iinfo->i_location;
un... | 268,421,128,721,178,170,000,000,000,000,000,000,000 | None | null | [
"CWE-189"
] | CVE-2015-4167 | The udf_read_inode function in fs/udf/inode.c in the Linux kernel before 3.19.1 does not validate certain length values, which allows local users to cause a denial of service (incorrect data representation or integer overflow, and OOPS) via a crafted UDF filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2015-4167 |
1,474 | linux | b1bb5b49373b61bf9d2c73a4d30058ba6f069e4c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b1bb5b49373b61bf9d2c73a4d30058ba6f069e4c | ozwpan: Use unsigned ints to prevent heap overflow
Using signed integers, the subtraction between required_size and offset
could wind up being negative, resulting in a memcpy into a heap buffer
with a negative length, resulting in huge amounts of network-supplied
data being copied into the heap, which could potentiall... | 1 | void oz_hcd_get_desc_cnf(void *hport, u8 req_id, int status, const u8 *desc,
int length, int offset, int total_size)
{
struct oz_port *port = hport;
struct urb *urb;
int err = 0;
oz_dbg(ON, "oz_hcd_get_desc_cnf length = %d offs = %d tot_size = %d\n",
length, offset, total_size);
urb = oz_find_urb_by... | 320,708,195,163,871,100,000,000,000,000,000,000,000 | ozhcd.c | 306,747,271,140,156,940,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2015-4001 | Integer signedness error in the oz_hcd_get_desc_cnf function in drivers/staging/ozwpan/ozhcd.c in the OZWPAN driver in the Linux kernel through 4.0.5 allows remote attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted packet. | https://nvd.nist.gov/vuln/detail/CVE-2015-4001 |
159,182 | linux | b1bb5b49373b61bf9d2c73a4d30058ba6f069e4c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b1bb5b49373b61bf9d2c73a4d30058ba6f069e4c | ozwpan: Use unsigned ints to prevent heap overflow
Using signed integers, the subtraction between required_size and offset
could wind up being negative, resulting in a memcpy into a heap buffer
with a negative length, resulting in huge amounts of network-supplied
data being copied into the heap, which could potentiall... | 0 | void oz_hcd_get_desc_cnf(void *hport, u8 req_id, int status, const u8 *desc,
void oz_hcd_get_desc_cnf(void *hport, u8 req_id, u8 status, const u8 *desc,
u8 length, u16 offset, u16 total_size)
{
struct oz_port *port = hport;
struct urb *urb;
int err = 0;
oz_dbg(ON, "oz_hcd_get_desc_cnf length = %d offs = %d t... | 338,033,345,113,830,530,000,000,000,000,000,000,000 | None | null | [
"CWE-189"
] | CVE-2015-4001 | Integer signedness error in the oz_hcd_get_desc_cnf function in drivers/staging/ozwpan/ozhcd.c in the OZWPAN driver in the Linux kernel through 4.0.5 allows remote attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted packet. | https://nvd.nist.gov/vuln/detail/CVE-2015-4001 |
1,477 | rawstudio | 983bda1f0fa5fa86884381208274198a620f006e | https://github.com/rawstudio/rawstudio | https://github.com/rawstudio/rawstudio/commit/983bda1f0fa5fa86884381208274198a620f006e | Avoid overflow in ljpeg_start(). | 1 | int CLASS ljpeg_start (struct jhead *jh, int info_only)
{
int c, tag, len;
uchar data[0x10000];
const uchar *dp;
memset (jh, 0, sizeof *jh);
jh->restart = INT_MAX;
fread (data, 2, 1, ifp);
if (data[1] != 0xd8) return 0;
do {
fread (data, 2, 2, ifp);
tag = data[0] << 8 | data[1];
len =... | 291,937,476,956,930,900,000,000,000,000,000,000,000 | dcraw.cc | 297,550,824,630,771,470,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2015-3885 | Integer overflow in the ljpeg_start function in dcraw 7.00 and earlier allows remote attackers to cause a denial of service (crash) via a crafted image, which triggers a buffer overflow, related to the len variable. | https://nvd.nist.gov/vuln/detail/CVE-2015-3885 |
159,185 | rawstudio | 983bda1f0fa5fa86884381208274198a620f006e | https://github.com/rawstudio/rawstudio | https://github.com/rawstudio/rawstudio/commit/983bda1f0fa5fa86884381208274198a620f006e | Avoid overflow in ljpeg_start(). | 0 | int CLASS ljpeg_start (struct jhead *jh, int info_only)
{
int c, tag;
ushort len;
uchar data[0x10000];
const uchar *dp;
memset (jh, 0, sizeof *jh);
jh->restart = INT_MAX;
fread (data, 2, 1, ifp);
if (data[1] != 0xd8) return 0;
do {
fread (data, 2, 2, ifp);
tag = data[0] << 8 | data[1];
... | 288,581,977,157,350,250,000,000,000,000,000,000 | dcraw.cc | 257,159,519,755,338,450,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2015-3885 | Integer overflow in the ljpeg_start function in dcraw 7.00 and earlier allows remote attackers to cause a denial of service (crash) via a crafted image, which triggers a buffer overflow, related to the len variable. | https://nvd.nist.gov/vuln/detail/CVE-2015-3885 |
1,479 | FFmpeg | e8714f6f93d1a32f4e4655209960afcf4c185214 | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/e8714f6f93d1a32f4e4655209960afcf4c185214 | avcodec/h264: Clear delayed_pic on deallocation
Fixes use of freed memory
Fixes: case5_av_frame_copy_props.mp4
Found-by: Michal Zalewski <lcamtuf@coredump.cx>
Signed-off-by: Michael Niedermayer <michaelni@gmx.at> | 1 | void ff_h264_free_tables(H264Context *h, int free_rbsp)
{
int i;
H264Context *hx;
av_freep(&h->intra4x4_pred_mode);
av_freep(&h->chroma_pred_mode_table);
av_freep(&h->cbp_table);
av_freep(&h->mvd_table[0]);
av_freep(&h->mvd_table[1]);
av_freep(&h->direct_table);
av_freep(&h->non_zer... | 160,444,303,816,193,310,000,000,000,000,000,000,000 | h264.c | 130,045,572,076,372,200,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2015-3417 | Use-after-free vulnerability in the ff_h264_free_tables function in libavcodec/h264.c in FFmpeg before 2.3.6 allows remote attackers to cause a denial of service or possibly have unspecified other impact via crafted H.264 data in an MP4 file, as demonstrated by an HTML VIDEO element that references H.264 data. | https://nvd.nist.gov/vuln/detail/CVE-2015-3417 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.