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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
158,943 | linux | ea2bc483ff5caada7c4aa0d5fbf87d3a6590273d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ea2bc483ff5caada7c4aa0d5fbf87d3a6590273d | [SCTP]: Fix assertion (!atomic_read(&sk->sk_rmem_alloc)) failed message
In current implementation, LKSCTP does receive buffer accounting for
data in sctp_receive_queue and pd_lobby. However, LKSCTP don't do
accounting for data in frag_list when data is fragmented. In addition,
LKSCTP doesn't do accounting for data in ... | 0 | static void sctp_sock_migrate(struct sock *oldsk, struct sock *newsk,
struct sctp_association *assoc,
sctp_socket_type_t type)
{
struct sctp_sock *oldsp = sctp_sk(oldsk);
struct sctp_sock *newsp = sctp_sk(newsk);
struct sctp_bind_bucket *pp; /* hash list port iterator */
struct sctp_endpoint *newe... | 229,565,381,021,276,100,000,000,000,000,000,000,000 | socket.c | 276,551,155,803,624,500,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2011-2482 | A certain Red Hat patch to the sctp_sock_migrate function in net/sctp/socket.c in the Linux kernel before 2.6.21, as used in Red Hat Enterprise Linux (RHEL) 5, allows remote attackers to cause a denial of service (NULL pointer dereference and OOPS) via a crafted SCTP packet. | https://nvd.nist.gov/vuln/detail/CVE-2011-2482 |
1,176 | linux | d370af0ef7951188daeb15bae75db7ba57c67846 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d370af0ef7951188daeb15bae75db7ba57c67846 | irda: validate peer name and attribute lengths
Length fields provided by a peer for names and attributes may be longer
than the destination array sizes. Validate lengths to prevent stack
buffer overflows.
Signed-off-by: Dan Rosenberg <drosenberg@vsecurity.com>
Cc: stable@kernel.org
Signed-off-by: David S. Miller <da... | 1 | static void iriap_getvaluebyclass_indication(struct iriap_cb *self,
struct sk_buff *skb)
{
struct ias_object *obj;
struct ias_attrib *attrib;
int name_len;
int attr_len;
char name[IAS_MAX_CLASSNAME + 1]; /* 60 bytes */
char attr[IAS_MAX_ATTRIBNAME + 1]; /* 60 bytes */
__u8 *fp;
int n;
IRDA_DEBUG(4, ... | 289,039,370,717,523,300,000,000,000,000,000,000,000 | iriap.c | 294,293,270,431,801,740,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-1180 | Multiple stack-based buffer overflows in the iriap_getvaluebyclass_indication function in net/irda/iriap.c in the Linux kernel before 2.6.39 allow remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging connectivity to an IrDA infrared network and sendin... | https://nvd.nist.gov/vuln/detail/CVE-2011-1180 |
158,952 | linux | d370af0ef7951188daeb15bae75db7ba57c67846 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d370af0ef7951188daeb15bae75db7ba57c67846 | irda: validate peer name and attribute lengths
Length fields provided by a peer for names and attributes may be longer
than the destination array sizes. Validate lengths to prevent stack
buffer overflows.
Signed-off-by: Dan Rosenberg <drosenberg@vsecurity.com>
Cc: stable@kernel.org
Signed-off-by: David S. Miller <da... | 0 | static void iriap_getvaluebyclass_indication(struct iriap_cb *self,
struct sk_buff *skb)
{
struct ias_object *obj;
struct ias_attrib *attrib;
int name_len;
int attr_len;
char name[IAS_MAX_CLASSNAME + 1]; /* 60 bytes */
char attr[IAS_MAX_ATTRIBNAME + 1]; /* 60 bytes */
__u8 *fp;
int n;
IRDA_DEBUG(4, ... | 188,363,666,428,243,800,000,000,000,000,000,000,000 | iriap.c | 2,768,355,254,666,253,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-1180 | Multiple stack-based buffer overflows in the iriap_getvaluebyclass_indication function in net/irda/iriap.c in the Linux kernel before 2.6.39 allow remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging connectivity to an IrDA infrared network and sendin... | https://nvd.nist.gov/vuln/detail/CVE-2011-1180 |
1,177 | linux | 8909c9ad8ff03611c9c96c9a92656213e4bb495b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8909c9ad8ff03611c9c96c9a92656213e4bb495b | net: don't allow CAP_NET_ADMIN to load non-netdev kernel modules
Since a8f80e8ff94ecba629542d9b4b5f5a8ee3eb565c any process with
CAP_NET_ADMIN may load any module from /lib/modules/. This doesn't mean
that CAP_NET_ADMIN is a superset of CAP_SYS_MODULE as modules are
limited to /lib/modules/**. However, CAP_NET_ADMIN... | 1 | void dev_load(struct net *net, const char *name)
{
struct net_device *dev;
rcu_read_lock();
dev = dev_get_by_name_rcu(net, name);
rcu_read_unlock();
if (!dev && capable(CAP_NET_ADMIN))
request_module("%s", name);
}
| 265,834,847,794,592,050,000,000,000,000,000,000,000 | dev.c | 199,475,088,564,555,730,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-1019 | The dev_load function in net/core/dev.c in the Linux kernel before 2.6.38 allows local users to bypass an intended CAP_SYS_MODULE capability requirement and load arbitrary modules by leveraging the CAP_NET_ADMIN capability. | https://nvd.nist.gov/vuln/detail/CVE-2011-1019 |
158,953 | linux | 8909c9ad8ff03611c9c96c9a92656213e4bb495b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8909c9ad8ff03611c9c96c9a92656213e4bb495b | net: don't allow CAP_NET_ADMIN to load non-netdev kernel modules
Since a8f80e8ff94ecba629542d9b4b5f5a8ee3eb565c any process with
CAP_NET_ADMIN may load any module from /lib/modules/. This doesn't mean
that CAP_NET_ADMIN is a superset of CAP_SYS_MODULE as modules are
limited to /lib/modules/**. However, CAP_NET_ADMIN... | 0 | void dev_load(struct net *net, const char *name)
{
struct net_device *dev;
int no_module;
rcu_read_lock();
dev = dev_get_by_name_rcu(net, name);
rcu_read_unlock();
no_module = !dev;
if (no_module && capable(CAP_NET_ADMIN))
no_module = request_module("netdev-%s", name);
if (no_module && capable(CAP_S... | 188,319,060,539,423,120,000,000,000,000,000,000,000 | dev.c | 293,551,360,526,032,140,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-1019 | The dev_load function in net/core/dev.c in the Linux kernel before 2.6.38 allows local users to bypass an intended CAP_SYS_MODULE capability requirement and load arbitrary modules by leveraging the CAP_NET_ADMIN capability. | https://nvd.nist.gov/vuln/detail/CVE-2011-1019 |
1,178 | krb5 | cf1a0c411b2668c57c41e9c4efd15ba17b6b322c | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/cf1a0c411b2668c57c41e9c4efd15ba17b6b322c | Fix kpasswd UDP ping-pong [CVE-2002-2443]
The kpasswd service provided by kadmind was vulnerable to a UDP
"ping-pong" attack [CVE-2002-2443]. Don't respond to packets unless
they pass some basic validation, and don't respond to our own error
packets.
Some authors use CVE-1999-0103 to refer to the kpasswd UDP ping-po... | 1 | process_chpw_request(krb5_context context, void *server_handle, char *realm,
krb5_keytab keytab, const krb5_fulladdr *local_faddr,
const krb5_fulladdr *remote_faddr, krb5_data *req,
krb5_data *rep)
{
krb5_error_code ret;
char *ptr;
unsigned int ... | 151,952,841,528,932,100,000,000,000,000,000,000,000 | schpw.c | 303,446,096,086,926,720,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2002-2443 | schpw.c in the kpasswd service in kadmind in MIT Kerberos 5 (aka krb5) before 1.11.3 does not properly validate UDP packets before sending responses, which allows remote attackers to cause a denial of service (CPU and bandwidth consumption) via a forged packet that triggers a communication loop, as demonstrated by krb_... | https://nvd.nist.gov/vuln/detail/CVE-2002-2443 |
158,954 | krb5 | cf1a0c411b2668c57c41e9c4efd15ba17b6b322c | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/cf1a0c411b2668c57c41e9c4efd15ba17b6b322c | Fix kpasswd UDP ping-pong [CVE-2002-2443]
The kpasswd service provided by kadmind was vulnerable to a UDP
"ping-pong" attack [CVE-2002-2443]. Don't respond to packets unless
they pass some basic validation, and don't respond to our own error
packets.
Some authors use CVE-1999-0103 to refer to the kpasswd UDP ping-po... | 0 | process_chpw_request(krb5_context context, void *server_handle, char *realm,
krb5_keytab keytab, const krb5_fulladdr *local_faddr,
const krb5_fulladdr *remote_faddr, krb5_data *req,
krb5_data *rep)
{
krb5_error_code ret;
char *ptr;
unsigned int ... | 142,756,706,875,374,310,000,000,000,000,000,000,000 | schpw.c | 67,582,437,934,358,280,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2002-2443 | schpw.c in the kpasswd service in kadmind in MIT Kerberos 5 (aka krb5) before 1.11.3 does not properly validate UDP packets before sending responses, which allows remote attackers to cause a denial of service (CPU and bandwidth consumption) via a forged packet that triggers a communication loop, as demonstrated by krb_... | https://nvd.nist.gov/vuln/detail/CVE-2002-2443 |
1,179 | linux | f54e18f1b831c92f6512d2eedb224cd63d607d3d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f54e18f1b831c92f6512d2eedb224cd63d607d3d | isofs: Fix infinite looping over CE entries
Rock Ridge extensions define so called Continuation Entries (CE) which
define where is further space with Rock Ridge data. Corrupted isofs
image can contain arbitrarily long chain of these, including a one
containing loop and thus causing kernel to end in an infinite loop wh... | 1 | static int rock_continue(struct rock_state *rs)
{
int ret = 1;
int blocksize = 1 << rs->inode->i_blkbits;
const int min_de_size = offsetof(struct rock_ridge, u);
kfree(rs->buffer);
rs->buffer = NULL;
if ((unsigned)rs->cont_offset > blocksize - min_de_size ||
(unsigned)rs->cont_size > blocksize ||
(uns... | 37,972,843,024,361,270,000,000,000,000,000,000,000 | rock.c | 282,024,907,067,004,600,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-9420 | The rock_continue function in fs/isofs/rock.c in the Linux kernel through 3.18.1 does not restrict the number of Rock Ridge continuation entries, which allows local users to cause a denial of service (infinite loop, and system crash or hang) via a crafted iso9660 image. | https://nvd.nist.gov/vuln/detail/CVE-2014-9420 |
158,955 | linux | f54e18f1b831c92f6512d2eedb224cd63d607d3d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f54e18f1b831c92f6512d2eedb224cd63d607d3d | isofs: Fix infinite looping over CE entries
Rock Ridge extensions define so called Continuation Entries (CE) which
define where is further space with Rock Ridge data. Corrupted isofs
image can contain arbitrarily long chain of these, including a one
containing loop and thus causing kernel to end in an infinite loop wh... | 0 | static int rock_continue(struct rock_state *rs)
{
int ret = 1;
int blocksize = 1 << rs->inode->i_blkbits;
const int min_de_size = offsetof(struct rock_ridge, u);
kfree(rs->buffer);
rs->buffer = NULL;
if ((unsigned)rs->cont_offset > blocksize - min_de_size ||
(unsigned)rs->cont_size > blocksize ||
(uns... | 77,679,757,477,074,070,000,000,000,000,000,000,000 | rock.c | 147,266,935,016,042,520,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-9420 | The rock_continue function in fs/isofs/rock.c in the Linux kernel through 3.18.1 does not restrict the number of Rock Ridge continuation entries, which allows local users to cause a denial of service (infinite loop, and system crash or hang) via a crafted iso9660 image. | https://nvd.nist.gov/vuln/detail/CVE-2014-9420 |
1,180 | linux | f647d7c155f069c1a068030255c300663516420e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f647d7c155f069c1a068030255c300663516420e | x86_64, switch_to(): Load TLS descriptors before switching DS and ES
Otherwise, if buggy user code points DS or ES into the TLS
array, they would be corrupted after a context switch.
This also significantly improves the comments and documents some
gotchas in the code.
Before this patch, the both tests below failed. ... | 1 | __switch_to(struct task_struct *prev_p, struct task_struct *next_p)
{
struct thread_struct *prev = &prev_p->thread;
struct thread_struct *next = &next_p->thread;
int cpu = smp_processor_id();
struct tss_struct *tss = &per_cpu(init_tss, cpu);
unsigned fsindex, gsindex;
fpu_switch_t fpu;
fpu = switch_fpu_prepar... | 205,391,279,388,742,040,000,000,000,000,000,000,000 | process_64.c | 81,668,502,972,952,200,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-9419 | The __switch_to function in arch/x86/kernel/process_64.c in the Linux kernel through 3.18.1 does not ensure that Thread Local Storage (TLS) descriptors are loaded before proceeding with other steps, which makes it easier for local users to bypass the ASLR protection mechanism via a crafted application that reads a TLS ... | https://nvd.nist.gov/vuln/detail/CVE-2014-9419 |
158,956 | linux | f647d7c155f069c1a068030255c300663516420e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f647d7c155f069c1a068030255c300663516420e | x86_64, switch_to(): Load TLS descriptors before switching DS and ES
Otherwise, if buggy user code points DS or ES into the TLS
array, they would be corrupted after a context switch.
This also significantly improves the comments and documents some
gotchas in the code.
Before this patch, the both tests below failed. ... | 0 | __switch_to(struct task_struct *prev_p, struct task_struct *next_p)
{
struct thread_struct *prev = &prev_p->thread;
struct thread_struct *next = &next_p->thread;
int cpu = smp_processor_id();
struct tss_struct *tss = &per_cpu(init_tss, cpu);
unsigned fsindex, gsindex;
fpu_switch_t fpu;
fpu = switch_fpu_prepar... | 330,795,244,157,893,600,000,000,000,000,000,000,000 | process_64.c | 183,843,207,748,752,320,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-9419 | The __switch_to function in arch/x86/kernel/process_64.c in the Linux kernel through 3.18.1 does not ensure that Thread Local Storage (TLS) descriptors are loaded before proceeding with other steps, which makes it easier for local users to bypass the ASLR protection mechanism via a crafted application that reads a TLS ... | https://nvd.nist.gov/vuln/detail/CVE-2014-9419 |
1,184 | linux | f2e323ec96077642d397bb1c355def536d489d16 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f2e323ec96077642d397bb1c355def536d489d16 | [media] ttusb-dec: buffer overflow in ioctl
We need to add a limit check here so we don't overflow the buffer.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com> | 1 | static int ttusbdecfe_dvbs_diseqc_send_master_cmd(struct dvb_frontend* fe, struct dvb_diseqc_master_cmd *cmd)
{
struct ttusbdecfe_state* state = (struct ttusbdecfe_state*) fe->demodulator_priv;
u8 b[] = { 0x00, 0xff, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00,
0x00, 0x00 };
memcpy(&b[4], cmd->msg, cmd->msg_le... | 192,608,949,045,328,570,000,000,000,000,000,000,000 | ttusbdecfe.c | 24,169,251,397,313,176,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-8884 | Stack-based buffer overflow in the ttusbdecfe_dvbs_diseqc_send_master_cmd function in drivers/media/usb/ttusb-dec/ttusbdecfe.c in the Linux kernel before 3.17.4 allows local users to cause a denial of service (system crash) or possibly gain privileges via a large message length in an ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-8884 |
158,959 | linux | f2e323ec96077642d397bb1c355def536d489d16 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f2e323ec96077642d397bb1c355def536d489d16 | [media] ttusb-dec: buffer overflow in ioctl
We need to add a limit check here so we don't overflow the buffer.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com> | 0 | static int ttusbdecfe_dvbs_diseqc_send_master_cmd(struct dvb_frontend* fe, struct dvb_diseqc_master_cmd *cmd)
{
struct ttusbdecfe_state* state = (struct ttusbdecfe_state*) fe->demodulator_priv;
u8 b[] = { 0x00, 0xff, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00,
0x00, 0x00 };
if (cmd->msg_len > sizeof(b) - 4)
... | 152,213,072,998,875,340,000,000,000,000,000,000,000 | ttusbdecfe.c | 218,785,497,703,789,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-8884 | Stack-based buffer overflow in the ttusbdecfe_dvbs_diseqc_send_master_cmd function in drivers/media/usb/ttusb-dec/ttusbdecfe.c in the Linux kernel before 3.17.4 allows local users to cause a denial of service (system crash) or possibly gain privileges via a large message length in an ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-8884 |
1,199 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 1 | xfs_da3_fixhashpath(
struct xfs_da_state *state,
struct xfs_da_state_path *path)
{
struct xfs_da_state_blk *blk;
struct xfs_da_intnode *node;
struct xfs_da_node_entry *btree;
xfs_dahash_t lasthash=0;
int level;
int count;
struct xfs_inode *dp = state->args->dp;
trace_xfs_da_fixhashpath(state->args);
l... | 190,462,110,703,120,600,000,000,000,000,000,000,000 | xfs_da_btree.c | 36,126,382,876,200,700,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
158,972 | linux | c88547a8119e3b581318ab65e9b72f27f23e641d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c88547a8119e3b581318ab65e9b72f27f23e641d | xfs: fix directory hash ordering bug
Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced
in 3.10 incorrectly converted the btree hash index array pointer in
xfs_da3_fixhashpath(). It resulted in the the current hash always
being compared against the first entry in the btree rather than the
current bloc... | 0 | xfs_da3_fixhashpath(
struct xfs_da_state *state,
struct xfs_da_state_path *path)
{
struct xfs_da_state_blk *blk;
struct xfs_da_intnode *node;
struct xfs_da_node_entry *btree;
xfs_dahash_t lasthash=0;
int level;
int count;
struct xfs_inode *dp = state->args->dp;
trace_xfs_da_fixhashpath(state->args);
l... | 89,073,314,904,855,200,000,000,000,000,000,000,000 | xfs_da_btree.c | 212,739,972,269,253,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7283 | The xfs_da3_fixhashpath function in fs/xfs/xfs_da_btree.c in the xfs implementation in the Linux kernel before 3.14.2 does not properly compare btree hash values, which allows local users to cause a denial of service (filesystem corruption, and OOPS or panic) via operations on directories that have hash collisions, as ... | https://nvd.nist.gov/vuln/detail/CVE-2014-7283 |
1,200 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 1 | SMB2_tcon(const unsigned int xid, struct cifs_ses *ses, const char *tree,
struct cifs_tcon *tcon, const struct nls_table *cp)
{
struct smb2_tree_connect_req *req;
struct smb2_tree_connect_rsp *rsp = NULL;
struct kvec iov[2];
int rc = 0;
int resp_buftype;
int unc_path_len;
struct TCP_Server_Info *server;
__le... | 60,644,300,295,276,330,000,000,000,000,000,000,000 | smb2pdu.c | 338,425,991,842,107,300,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
158,973 | linux | 18f39e7be0121317550d03e267e3ebd4dbfbb3ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/18f39e7be0121317550d03e267e3ebd4dbfbb3ce | [CIFS] Possible null ptr deref in SMB2_tcon
As Raphael Geissert pointed out, tcon_error_exit can dereference tcon
and there is one path in which tcon can be null.
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org> # v3.7+
Reported-by: Raphael Geissert <geissert@debian.org> | 0 | SMB2_tcon(const unsigned int xid, struct cifs_ses *ses, const char *tree,
struct cifs_tcon *tcon, const struct nls_table *cp)
{
struct smb2_tree_connect_req *req;
struct smb2_tree_connect_rsp *rsp = NULL;
struct kvec iov[2];
int rc = 0;
int resp_buftype;
int unc_path_len;
struct TCP_Server_Info *server;
__le... | 242,141,687,509,613,200,000,000,000,000,000,000,000 | smb2pdu.c | 55,575,034,826,269,910,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7145 | The SMB2_tcon function in fs/cifs/smb2pdu.c in the Linux kernel before 3.16.3 allows remote CIFS servers to cause a denial of service (NULL pointer dereference and client system crash) or possibly have unspecified other impact by deleting the IPC$ share during resolution of DFS referrals. | https://nvd.nist.gov/vuln/detail/CVE-2014-7145 |
1,204 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 1 | static void __udf_read_inode(struct inode *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);
unsigned int link_count;
/*
* Set defaults, but the inod... | 121,718,855,555,196,310,000,000,000,000,000,000,000 | inode.c | 339,312,702,252,410,520,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
158,977 | linux | c03aa9f6e1f938618e6db2e23afef0574efeeb65 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c03aa9f6e1f938618e6db2e23afef0574efeeb65 | udf: Avoid infinite loop when processing indirect ICBs
We did not implement any bound on number of indirect ICBs we follow when
loading inode. Thus corrupted medium could cause kernel to go into an
infinite loop, possibly causing a stack overflow.
Fix the possible stack overflow by removing recursion from
__udf_read_... | 0 | static void __udf_read_inode(struct inode *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);
unsigned int link_count;
unsigned int indirections = 0;
rere... | 136,960,620,832,889,900,000,000,000,000,000,000,000 | inode.c | 233,698,405,973,444,620,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-6410 | The __udf_read_inode function in fs/udf/inode.c in the Linux kernel through 3.16.3 does not restrict the amount of ICB indirection, which allows physically proximate attackers to cause a denial of service (infinite loop or stack consumption) via a UDF filesystem with a crafted inode. | https://nvd.nist.gov/vuln/detail/CVE-2014-6410 |
1,205 | ettercap | e3abe7d7585ecc420a7cab73313216613aadad5a | https://github.com/Ettercap/ettercap | https://github.com/Ettercap/ettercap/commit/e3abe7d7585ecc420a7cab73313216613aadad5a | Fixed heap overflow caused by length | 1 | FUNC_DECODER(dissector_postgresql)
{
DECLARE_DISP_PTR(ptr);
struct ec_session *s = NULL;
void *ident = NULL;
char tmp[MAX_ASCII_ADDR_LEN];
struct postgresql_status *conn_status;
/* don't complain about unused var */
(void) DECODE_DATA;
(void) DECODE_DATALEN;
(void) DECODED_LEN;
if (F... | 113,723,108,844,572,020,000,000,000,000,000,000,000 | ec_postgresql.c | 75,203,240,410,363,380,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-6395 | Heap-based buffer overflow in the dissector_postgresql function in dissectors/ec_postgresql.c in Ettercap before 0.8.1 allows remote attackers to cause a denial of service or possibly execute arbitrary code via a crafted password length value that is inconsistent with the actual length of the password. | https://nvd.nist.gov/vuln/detail/CVE-2014-6395 |
158,978 | ettercap | e3abe7d7585ecc420a7cab73313216613aadad5a | https://github.com/Ettercap/ettercap | https://github.com/Ettercap/ettercap/commit/e3abe7d7585ecc420a7cab73313216613aadad5a | Fixed heap overflow caused by length | 0 | FUNC_DECODER(dissector_postgresql)
{
DECLARE_DISP_PTR(ptr);
struct ec_session *s = NULL;
void *ident = NULL;
char tmp[MAX_ASCII_ADDR_LEN];
struct postgresql_status *conn_status;
/* don't complain about unused var */
(void) DECODE_DATA;
(void) DECODE_DATALEN;
(void) DECODED_LEN;
if (F... | 235,532,748,321,397,000,000,000,000,000,000,000,000 | ec_postgresql.c | 284,688,323,983,812,370,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-6395 | Heap-based buffer overflow in the dissector_postgresql function in dissectors/ec_postgresql.c in Ettercap before 0.8.1 allows remote attackers to cause a denial of service or possibly execute arbitrary code via a crafted password length value that is inconsistent with the actual length of the password. | https://nvd.nist.gov/vuln/detail/CVE-2014-6395 |
1,218 | linux | a6138db815df5ee542d848318e5dae681590fccd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a6138db815df5ee542d848318e5dae681590fccd | mnt: Only change user settable mount flags in remount
Kenton Varda <kenton@sandstorm.io> discovered that by remounting a
read-only bind mount read-only in a user namespace the
MNT_LOCK_READONLY bit would be cleared, allowing an unprivileged user
to the remount a read-only mount read-write.
Correct this by replacing t... | 1 | static int do_remount(struct path *path, int flags, int mnt_flags,
void *data)
{
int err;
struct super_block *sb = path->mnt->mnt_sb;
struct mount *mnt = real_mount(path->mnt);
if (!check_mnt(mnt))
return -EINVAL;
if (path->dentry != path->mnt->mnt_root)
return -EINVAL;
err = security_sb_remount(sb... | 251,245,953,508,821,370,000,000,000,000,000,000,000 | namespace.c | 87,954,754,859,779,580,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-5206 | The do_remount function in fs/namespace.c in the Linux kernel through 3.16.1 does not maintain the MNT_LOCK_READONLY bit across a remount of a bind mount, which allows local users to bypass an intended read-only restriction and defeat certain sandbox protection mechanisms via a "mount -o remount" command within a user ... | https://nvd.nist.gov/vuln/detail/CVE-2014-5206 |
158,987 | linux | a6138db815df5ee542d848318e5dae681590fccd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a6138db815df5ee542d848318e5dae681590fccd | mnt: Only change user settable mount flags in remount
Kenton Varda <kenton@sandstorm.io> discovered that by remounting a
read-only bind mount read-only in a user namespace the
MNT_LOCK_READONLY bit would be cleared, allowing an unprivileged user
to the remount a read-only mount read-write.
Correct this by replacing t... | 0 | static int do_remount(struct path *path, int flags, int mnt_flags,
void *data)
{
int err;
struct super_block *sb = path->mnt->mnt_sb;
struct mount *mnt = real_mount(path->mnt);
if (!check_mnt(mnt))
return -EINVAL;
if (path->dentry != path->mnt->mnt_root)
return -EINVAL;
err = security_sb_remount(sb... | 240,645,178,847,818,240,000,000,000,000,000,000,000 | namespace.c | 325,359,660,145,165,160,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-5206 | The do_remount function in fs/namespace.c in the Linux kernel through 3.16.1 does not maintain the MNT_LOCK_READONLY bit across a remount of a bind mount, which allows local users to bypass an intended read-only restriction and defeat certain sandbox protection mechanisms via a "mount -o remount" command within a user ... | https://nvd.nist.gov/vuln/detail/CVE-2014-5206 |
1,220 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 1 | mountpoint_last(struct nameidata *nd, struct path *path)
{
int error = 0;
struct dentry *dentry;
struct dentry *dir = nd->path.dentry;
/* If we're in rcuwalk, drop out of it to handle last component */
if (nd->flags & LOOKUP_RCU) {
if (unlazy_walk(nd, NULL)) {
error = -ECHILD;
goto out;
}
}
nd->flags... | 289,527,718,022,341,300,000,000,000,000,000,000,000 | namei.c | 135,878,708,536,746,050,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
158,988 | linux | 295dc39d941dc2ae53d5c170365af4c9d5c16212 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/295dc39d941dc2ae53d5c170365af4c9d5c16212 | fs: umount on symlink leaks mnt count
Currently umount on symlink blocks following umount:
/vz is separate mount
# ls /vz/ -al | grep test
drwxr-xr-x. 2 root root 4096 Jul 19 01:14 testdir
lrwxrwxrwx. 1 root root 11 Jul 19 01:16 testlink -> /vz/testdir
# umount -l /vz/testlink
umount: /vz/testlink: n... | 0 | mountpoint_last(struct nameidata *nd, struct path *path)
{
int error = 0;
struct dentry *dentry;
struct dentry *dir = nd->path.dentry;
/* If we're in rcuwalk, drop out of it to handle last component */
if (nd->flags & LOOKUP_RCU) {
if (unlazy_walk(nd, NULL)) {
error = -ECHILD;
goto out;
}
}
nd->flags... | 74,756,489,007,236,380,000,000,000,000,000,000,000 | namei.c | 101,999,130,454,170,320,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2014-5045 | The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-5045 |
1,233 | linux | 206204a1162b995e2185275167b22468c00d6b36 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/206204a1162b995e2185275167b22468c00d6b36 | lz4: ensure length does not wrap
Given some pathologically compressed data, lz4 could possibly decide to
wrap a few internal variables, causing unknown things to happen. Catch
this before the wrapping happens and abort the decompression.
Reported-by: "Don A. Bailey" <donb@securitymouse.com>
Cc: stable <stable@vger.k... | 1 | static int lz4_uncompress(const char *source, char *dest, int osize)
{
const BYTE *ip = (const BYTE *) source;
const BYTE *ref;
BYTE *op = (BYTE *) dest;
BYTE * const oend = op + osize;
BYTE *cpy;
unsigned token;
size_t length;
size_t dec32table[] = {0, 3, 2, 3, 0, 0, 0, 0};
#if LZ4_ARCH64
size_t dec64table[] ... | 88,608,013,649,608,300,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2014-4611 | Integer overflow in the LZ4 algorithm implementation, as used in Yann Collet LZ4 before r118 and in the lz4_uncompress function in lib/lz4/lz4_decompress.c in the Linux kernel before 3.15.2, on 32-bit platforms might allow context-dependent attackers to cause a denial of service (memory corruption) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-4611 |
158,992 | linux | 206204a1162b995e2185275167b22468c00d6b36 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/206204a1162b995e2185275167b22468c00d6b36 | lz4: ensure length does not wrap
Given some pathologically compressed data, lz4 could possibly decide to
wrap a few internal variables, causing unknown things to happen. Catch
this before the wrapping happens and abort the decompression.
Reported-by: "Don A. Bailey" <donb@securitymouse.com>
Cc: stable <stable@vger.k... | 0 | static int lz4_uncompress(const char *source, char *dest, int osize)
{
const BYTE *ip = (const BYTE *) source;
const BYTE *ref;
BYTE *op = (BYTE *) dest;
BYTE * const oend = op + osize;
BYTE *cpy;
unsigned token;
size_t length;
size_t dec32table[] = {0, 3, 2, 3, 0, 0, 0, 0};
#if LZ4_ARCH64
size_t dec64table[] ... | 218,823,319,514,216,050,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2014-4611 | Integer overflow in the LZ4 algorithm implementation, as used in Yann Collet LZ4 before r118 and in the lz4_uncompress function in lib/lz4/lz4_decompress.c in the Linux kernel before 3.15.2, on 32-bit platforms might allow context-dependent attackers to cause a denial of service (memory corruption) or possibly have uns... | https://nvd.nist.gov/vuln/detail/CVE-2014-4611 |
1,234 | linux | 206a81c18401c0cde6e579164f752c4b147324ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/206a81c18401c0cde6e579164f752c4b147324ce | lzo: properly check for overruns
The lzo decompressor can, if given some really crazy data, possibly
overrun some variable types. Modify the checking logic to properly
detect overruns before they happen.
Reported-by: "Don A. Bailey" <donb@securitymouse.com>
Tested-by: "Don A. Bailey" <donb@securitymouse.com>
Cc: sta... | 1 | int lzo1x_decompress_safe(const unsigned char *in, size_t in_len,
unsigned char *out, size_t *out_len)
{
unsigned char *op;
const unsigned char *ip;
size_t t, next;
size_t state = 0;
const unsigned char *m_pos;
const unsigned char * const ip_end = in + in_len;
unsigned char * const op_end = out + *out_len... | 274,406,254,790,435,130,000,000,000,000,000,000,000 | lzo1x_decompress_safe.c | 59,242,432,641,946,220,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-4608 | Multiple integer overflows in the lzo1x_decompress_safe function in lib/lzo/lzo1x_decompress_safe.c in the LZO decompressor in the Linux kernel before 3.15.2 allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Literal Run. NOTE: the author of the LZO algorithms says "the Li... | https://nvd.nist.gov/vuln/detail/CVE-2014-4608 |
158,993 | linux | 206a81c18401c0cde6e579164f752c4b147324ce | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/206a81c18401c0cde6e579164f752c4b147324ce | lzo: properly check for overruns
The lzo decompressor can, if given some really crazy data, possibly
overrun some variable types. Modify the checking logic to properly
detect overruns before they happen.
Reported-by: "Don A. Bailey" <donb@securitymouse.com>
Tested-by: "Don A. Bailey" <donb@securitymouse.com>
Cc: sta... | 0 | int lzo1x_decompress_safe(const unsigned char *in, size_t in_len,
unsigned char *out, size_t *out_len)
{
unsigned char *op;
const unsigned char *ip;
size_t t, next;
size_t state = 0;
const unsigned char *m_pos;
const unsigned char * const ip_end = in + in_len;
unsigned char * const op_end = out + *out_len... | 174,542,836,292,707,050,000,000,000,000,000,000,000 | lzo1x_decompress_safe.c | 52,351,594,738,285,980,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-4608 | Multiple integer overflows in the lzo1x_decompress_safe function in lib/lzo/lzo1x_decompress_safe.c in the LZO decompressor in the Linux kernel before 3.15.2 allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Literal Run. NOTE: the author of the LZO algorithms says "the Li... | https://nvd.nist.gov/vuln/detail/CVE-2014-4608 |
1,235 | sgminer | 910c36089940e81fb85c65b8e63dcd2fac71470c | https://github.com/sgminer-dev/sgminer | https://github.com/sgminer-dev/sgminer/commit/910c36089940e81fb85c65b8e63dcd2fac71470c | stratum: parse_notify(): Don't die on malformed bbversion/prev_hash/nbit/ntime.
Might have introduced a memory leak, don't have time to check. :(
Should the other hex2bin()'s be checked?
Thanks to Mick Ayzenberg <mick.dejavusecurity.com> for finding this. | 1 | static bool parse_notify(struct pool *pool, json_t *val)
{
char *job_id, *prev_hash, *coinbase1, *coinbase2, *bbversion, *nbit,
*ntime, *header;
size_t cb1_len, cb2_len, alloc_len;
unsigned char *cb1, *cb2;
bool clean, ret = false;
int merkles, i;
json_t *arr;
arr = json_array_get(val, 4);
if (!arr || !j... | 317,403,549,402,048,870,000,000,000,000,000,000,000 | util.c | 165,475,851,610,177,230,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-4503 | The parse_notify function in util.c in sgminer before 4.2.2 and cgminer 3.3.0 through 4.0.1 allows man-in-the-middle attackers to cause a denial of service (application exit) via a crafted (1) bbversion, (2) prev_hash, (3) nbit, or (4) ntime parameter in a mining.notify action stratum message. | https://nvd.nist.gov/vuln/detail/CVE-2014-4503 |
158,994 | sgminer | 910c36089940e81fb85c65b8e63dcd2fac71470c | https://github.com/sgminer-dev/sgminer | https://github.com/sgminer-dev/sgminer/commit/910c36089940e81fb85c65b8e63dcd2fac71470c | stratum: parse_notify(): Don't die on malformed bbversion/prev_hash/nbit/ntime.
Might have introduced a memory leak, don't have time to check. :(
Should the other hex2bin()'s be checked?
Thanks to Mick Ayzenberg <mick.dejavusecurity.com> for finding this. | 0 | static bool parse_notify(struct pool *pool, json_t *val)
{
char *job_id, *prev_hash, *coinbase1, *coinbase2, *bbversion, *nbit,
*ntime, *header;
size_t cb1_len, cb2_len, alloc_len;
unsigned char *cb1, *cb2;
bool clean, ret = false;
int merkles, i;
json_t *arr;
arr = json_array_get(val, 4);
if (!arr || !j... | 8,419,252,984,356,720,000,000,000,000,000,000,000 | util.c | 79,021,405,279,685,970,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-4503 | The parse_notify function in util.c in sgminer before 4.2.2 and cgminer 3.3.0 through 4.0.1 allows man-in-the-middle attackers to cause a denial of service (application exit) via a crafted (1) bbversion, (2) prev_hash, (3) nbit, or (4) ntime parameter in a mining.notify action stratum message. | https://nvd.nist.gov/vuln/detail/CVE-2014-4503 |
1,236 | cgminer | e1c5050734123973b99d181c45e74b2cbb00272e | https://github.com/ckolivas/cgminer | https://github.com/ckolivas/cgminer/commit/e1c5050734123973b99d181c45e74b2cbb00272e | Do some random sanity checking for stratum message parsing | 1 | bool extract_sockaddr(char *url, char **sockaddr_url, char **sockaddr_port)
{
char *url_begin, *url_end, *ipv6_begin, *ipv6_end, *port_start = NULL;
char url_address[256], port[6];
int url_len, port_len = 0;
*sockaddr_url = url;
url_begin = strstr(url, "//");
if (!url_begin)
url_begin = url;
else
url_begin ... | 268,425,937,881,460,200,000,000,000,000,000,000,000 | util.c | 312,757,577,260,077,530,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-4502 | Multiple heap-based buffer overflows in the parse_notify function in sgminer before 4.2.2, cgminer before 4.3.5, and BFGMiner before 4.1.0 allow remote pool servers to have unspecified impact via a (1) large or (2) negative value in the Extranonc2_size parameter in a mining.subscribe response and a crafted mining.notif... | https://nvd.nist.gov/vuln/detail/CVE-2014-4502 |
158,995 | cgminer | e1c5050734123973b99d181c45e74b2cbb00272e | https://github.com/ckolivas/cgminer | https://github.com/ckolivas/cgminer/commit/e1c5050734123973b99d181c45e74b2cbb00272e | Do some random sanity checking for stratum message parsing | 0 | bool extract_sockaddr(char *url, char **sockaddr_url, char **sockaddr_port)
{
char *url_begin, *url_end, *ipv6_begin, *ipv6_end, *port_start = NULL;
char url_address[256], port[6];
int url_len, port_len = 0;
*sockaddr_url = url;
url_begin = strstr(url, "//");
if (!url_begin)
url_begin = url;
else
url_begin ... | 278,891,602,713,911,520,000,000,000,000,000,000,000 | util.c | 129,321,568,267,466,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-4502 | Multiple heap-based buffer overflows in the parse_notify function in sgminer before 4.2.2, cgminer before 4.3.5, and BFGMiner before 4.1.0 allow remote pool servers to have unspecified impact via a (1) large or (2) negative value in the Extranonc2_size parameter in a mining.subscribe response and a crafted mining.notif... | https://nvd.nist.gov/vuln/detail/CVE-2014-4502 |
1,237 | cgminer | e1c5050734123973b99d181c45e74b2cbb00272e | https://github.com/ckolivas/cgminer | https://github.com/ckolivas/cgminer/commit/e1c5050734123973b99d181c45e74b2cbb00272e | Do some random sanity checking for stratum message parsing | 1 | static bool parse_notify(struct pool *pool, json_t *val)
{
char *job_id, *prev_hash, *coinbase1, *coinbase2, *bbversion, *nbit,
*ntime, header[228];
unsigned char *cb1 = NULL, *cb2 = NULL;
size_t cb1_len, cb2_len, alloc_len;
bool clean, ret = false;
int merkles, i;
json_t *arr;
arr = json_array_get(val, 4... | 84,334,959,585,750,240,000,000,000,000,000,000,000 | util.c | 206,367,765,513,721,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-4502 | Multiple heap-based buffer overflows in the parse_notify function in sgminer before 4.2.2, cgminer before 4.3.5, and BFGMiner before 4.1.0 allow remote pool servers to have unspecified impact via a (1) large or (2) negative value in the Extranonc2_size parameter in a mining.subscribe response and a crafted mining.notif... | https://nvd.nist.gov/vuln/detail/CVE-2014-4502 |
158,996 | cgminer | e1c5050734123973b99d181c45e74b2cbb00272e | https://github.com/ckolivas/cgminer | https://github.com/ckolivas/cgminer/commit/e1c5050734123973b99d181c45e74b2cbb00272e | Do some random sanity checking for stratum message parsing | 0 | static bool parse_notify(struct pool *pool, json_t *val)
{
char *job_id, *prev_hash, *coinbase1, *coinbase2, *bbversion, *nbit,
*ntime, header[228];
unsigned char *cb1 = NULL, *cb2 = NULL;
size_t cb1_len, cb2_len, alloc_len;
bool clean, ret = false;
int merkles, i;
json_t *arr;
arr = json_array_get(val, 4... | 31,220,049,300,174,420,000,000,000,000,000,000,000 | util.c | 129,321,568,267,466,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-4502 | Multiple heap-based buffer overflows in the parse_notify function in sgminer before 4.2.2, cgminer before 4.3.5, and BFGMiner before 4.1.0 allow remote pool servers to have unspecified impact via a (1) large or (2) negative value in the Extranonc2_size parameter in a mining.subscribe response and a crafted mining.notif... | https://nvd.nist.gov/vuln/detail/CVE-2014-4502 |
1,238 | cgminer | e1c5050734123973b99d181c45e74b2cbb00272e | https://github.com/ckolivas/cgminer | https://github.com/ckolivas/cgminer/commit/e1c5050734123973b99d181c45e74b2cbb00272e | Do some random sanity checking for stratum message parsing | 1 | static bool parse_reconnect(struct pool *pool, json_t *val)
{
char *sockaddr_url, *stratum_port, *tmp;
char *url, *port, address[256];
memset(address, 0, 255);
url = (char *)json_string_value(json_array_get(val, 0));
if (!url)
url = pool->sockaddr_url;
else {
char *dot_pool, *dot_reconnect;
dot_pool = strc... | 137,361,347,459,447,410,000,000,000,000,000,000,000 | util.c | 206,367,765,513,721,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-4502 | Multiple heap-based buffer overflows in the parse_notify function in sgminer before 4.2.2, cgminer before 4.3.5, and BFGMiner before 4.1.0 allow remote pool servers to have unspecified impact via a (1) large or (2) negative value in the Extranonc2_size parameter in a mining.subscribe response and a crafted mining.notif... | https://nvd.nist.gov/vuln/detail/CVE-2014-4502 |
158,997 | cgminer | e1c5050734123973b99d181c45e74b2cbb00272e | https://github.com/ckolivas/cgminer | https://github.com/ckolivas/cgminer/commit/e1c5050734123973b99d181c45e74b2cbb00272e | Do some random sanity checking for stratum message parsing | 0 | static bool parse_reconnect(struct pool *pool, json_t *val)
{
char *sockaddr_url, *stratum_port, *tmp;
char *url, *port, address[256];
memset(address, 0, 255);
url = (char *)json_string_value(json_array_get(val, 0));
if (!url)
url = pool->sockaddr_url;
else {
char *dot_pool, *dot_reconnect;
dot_pool = strc... | 279,622,017,893,359,280,000,000,000,000,000,000,000 | util.c | 129,321,568,267,466,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-4502 | Multiple heap-based buffer overflows in the parse_notify function in sgminer before 4.2.2, cgminer before 4.3.5, and BFGMiner before 4.1.0 allow remote pool servers to have unspecified impact via a (1) large or (2) negative value in the Extranonc2_size parameter in a mining.subscribe response and a crafted mining.notif... | https://nvd.nist.gov/vuln/detail/CVE-2014-4502 |
1,242 | php-src | b34d7849ed90ced9345f8ea1c59bc8d101c18468 | https://github.com/php/php-src | https://github.com/php/php-src/commit/b34d7849ed90ced9345f8ea1c59bc8d101c18468 | Merge branch 'PHP-5.6'
* PHP-5.6:
Fix potential segfault in dns_get_record() | 1 | static u_char *php_parserr(u_char *cp, querybuf *answer, int type_to_fetch, int store, int raw, zval **subarray)
{
u_short type, class, dlen;
u_long ttl;
long n, i;
u_short s;
u_char *tp, *p;
char name[MAXHOSTNAMELEN];
int have_v6_break = 0, in_v6_break = 0;
*subarray = NULL;
n = dn_expand(answer->qb2, answe... | 61,555,348,514,619,220,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-4049 | Heap-based buffer overflow in the php_parserr function in ext/standard/dns.c in PHP 5.6.0beta4 and earlier allows remote servers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted DNS TXT record, related to the dns_get_record function. | https://nvd.nist.gov/vuln/detail/CVE-2014-4049 |
158,999 | php-src | b34d7849ed90ced9345f8ea1c59bc8d101c18468 | https://github.com/php/php-src | https://github.com/php/php-src/commit/b34d7849ed90ced9345f8ea1c59bc8d101c18468 | Merge branch 'PHP-5.6'
* PHP-5.6:
Fix potential segfault in dns_get_record() | 0 | static u_char *php_parserr(u_char *cp, querybuf *answer, int type_to_fetch, int store, int raw, zval **subarray)
{
u_short type, class, dlen;
u_long ttl;
long n, i;
u_short s;
u_char *tp, *p;
char name[MAXHOSTNAMELEN];
int have_v6_break = 0, in_v6_break = 0;
*subarray = NULL;
n = dn_expand(answer->qb2, answe... | 42,082,954,493,828,007,000,000,000,000,000,000,000 | dns.c | 226,180,146,173,155,600,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-4049 | Heap-based buffer overflow in the php_parserr function in ext/standard/dns.c in PHP 5.6.0beta4 and earlier allows remote servers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted DNS TXT record, related to the dns_get_record function. | https://nvd.nist.gov/vuln/detail/CVE-2014-4049 |
1,243 | linux | 4442dc8a92b8f9ad8ee9e7f8438f4c04c03a22dc | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4442dc8a92b8f9ad8ee9e7f8438f4c04c03a22dc | target/rd: Refactor rd_build_device_space + rd_release_device_space
This patch refactors rd_build_device_space() + rd_release_device_space()
into rd_allocate_sgl_table() + rd_release_device_space() so that they
may be used seperatly for setup + release of protection information
scatterlists.
Also add explicit memset ... | 1 | static int rd_build_device_space(struct rd_dev *rd_dev)
{
u32 i = 0, j, page_offset = 0, sg_per_table, sg_tables, total_sg_needed;
u32 max_sg_per_table = (RD_MAX_ALLOCATION_SIZE /
sizeof(struct scatterlist));
struct rd_dev_sg_table *sg_table;
struct page *pg;
struct scatterlist *sg;
if (rd_dev->rd_page_c... | 231,707,640,209,773,850,000,000,000,000,000,000,000 | target_core_rd.c | 229,492,553,967,661,880,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-4027 | The rd_build_device_space function in drivers/target/target_core_rd.c in the Linux kernel before 3.14 does not properly initialize a certain data structure, which allows local users to obtain sensitive information from ramdisk_mcp memory by leveraging access to a SCSI initiator. | https://nvd.nist.gov/vuln/detail/CVE-2014-4027 |
159,000 | linux | 4442dc8a92b8f9ad8ee9e7f8438f4c04c03a22dc | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4442dc8a92b8f9ad8ee9e7f8438f4c04c03a22dc | target/rd: Refactor rd_build_device_space + rd_release_device_space
This patch refactors rd_build_device_space() + rd_release_device_space()
into rd_allocate_sgl_table() + rd_release_device_space() so that they
may be used seperatly for setup + release of protection information
scatterlists.
Also add explicit memset ... | 0 | static int rd_build_device_space(struct rd_dev *rd_dev)
static int rd_allocate_sgl_table(struct rd_dev *rd_dev, struct rd_dev_sg_table *sg_table,
u32 total_sg_needed, unsigned char init_payload)
{
u32 i = 0, j, page_offset = 0, sg_per_table;
u32 max_sg_per_table = (RD_MAX_ALLOCATION_SIZE /
sizeof(struct s... | 68,646,230,986,012,440,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2014-4027 | The rd_build_device_space function in drivers/target/target_core_rd.c in the Linux kernel before 3.14 does not properly initialize a certain data structure, which allows local users to obtain sensitive information from ramdisk_mcp memory by leveraging access to a SCSI initiator. | https://nvd.nist.gov/vuln/detail/CVE-2014-4027 |
1,251 | miniupnp | 3a87aa2f10bd7f1408e1849bdb59c41dd63a9fe9 | https://github.com/miniupnp/miniupnp | https://github.com/miniupnp/miniupnp/commit/3a87aa2f10bd7f1408e1849bdb59c41dd63a9fe9 | miniwget.c: fixed potential buffer overrun | 1 | getHTTPResponse(int s, int * size)
{
char buf[2048];
int n;
int endofheaders = 0;
int chunked = 0;
int content_length = -1;
unsigned int chunksize = 0;
unsigned int bytestocopy = 0;
/* buffers : */
char * header_buf;
unsigned int header_buf_len = 2048;
unsigned int header_buf_used = 0;
char * content_buf;
... | 306,297,354,977,511,100,000,000,000,000,000,000,000 | miniwget.c | 99,482,104,209,569,080,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3985 | The getHTTPResponse function in miniwget.c in MiniUPnP 1.9 allows remote attackers to cause a denial of service (crash) via crafted headers that trigger an out-of-bounds read. | https://nvd.nist.gov/vuln/detail/CVE-2014-3985 |
159,007 | miniupnp | 3a87aa2f10bd7f1408e1849bdb59c41dd63a9fe9 | https://github.com/miniupnp/miniupnp | https://github.com/miniupnp/miniupnp/commit/3a87aa2f10bd7f1408e1849bdb59c41dd63a9fe9 | miniwget.c: fixed potential buffer overrun | 0 | getHTTPResponse(int s, int * size)
{
char buf[2048];
int n;
int endofheaders = 0;
int chunked = 0;
int content_length = -1;
unsigned int chunksize = 0;
unsigned int bytestocopy = 0;
/* buffers : */
char * header_buf;
unsigned int header_buf_len = 2048;
unsigned int header_buf_used = 0;
char * content_buf;
... | 331,237,893,839,884,760,000,000,000,000,000,000,000 | miniwget.c | 168,853,020,666,456,580,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3985 | The getHTTPResponse function in miniwget.c in MiniUPnP 1.9 allows remote attackers to cause a denial of service (crash) via crafted headers that trigger an out-of-bounds read. | https://nvd.nist.gov/vuln/detail/CVE-2014-3985 |
1,257 | linux | 26b87c7881006311828bb0ab271a551a62dcceb4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/26b87c7881006311828bb0ab271a551a62dcceb4 | net: sctp: fix remote memory pressure from excessive queueing
This scenario is not limited to ASCONF, just taken as one
example triggering the issue. When receiving ASCONF probes
in the form of ...
-------------- INIT[ASCONF; ASCONF_ACK] ------------->
<----------- INIT-ACK[ASCONF; ASCONF_ACK] ------------
----... | 1 | struct sctp_chunk *sctp_inq_pop(struct sctp_inq *queue)
{
struct sctp_chunk *chunk;
sctp_chunkhdr_t *ch = NULL;
/* The assumption is that we are safe to process the chunks
* at this time.
*/
if ((chunk = queue->in_progress)) {
/* There is a packet that we have been working on.
* Any post processing work ... | 146,497,261,003,956,660,000,000,000,000,000,000,000 | inqueue.c | 183,685,648,427,300,330,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-3688 | The SCTP implementation in the Linux kernel before 3.17.4 allows remote attackers to cause a denial of service (memory consumption) by triggering a large number of chunks in an association's output queue, as demonstrated by ASCONF probes, related to net/sctp/inqueue.c and net/sctp/sm_statefuns.c. | https://nvd.nist.gov/vuln/detail/CVE-2014-3688 |
159,011 | linux | 26b87c7881006311828bb0ab271a551a62dcceb4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/26b87c7881006311828bb0ab271a551a62dcceb4 | net: sctp: fix remote memory pressure from excessive queueing
This scenario is not limited to ASCONF, just taken as one
example triggering the issue. When receiving ASCONF probes
in the form of ...
-------------- INIT[ASCONF; ASCONF_ACK] ------------->
<----------- INIT-ACK[ASCONF; ASCONF_ACK] ------------
----... | 0 | struct sctp_chunk *sctp_inq_pop(struct sctp_inq *queue)
{
struct sctp_chunk *chunk;
sctp_chunkhdr_t *ch = NULL;
/* The assumption is that we are safe to process the chunks
* at this time.
*/
if ((chunk = queue->in_progress)) {
/* There is a packet that we have been working on.
* Any post processing work ... | 59,689,607,597,111,770,000,000,000,000,000,000,000 | inqueue.c | 11,503,476,439,811,367,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-3688 | The SCTP implementation in the Linux kernel before 3.17.4 allows remote attackers to cause a denial of service (memory consumption) by triggering a large number of chunks in an association's output queue, as demonstrated by ASCONF probes, related to net/sctp/inqueue.c and net/sctp/sm_statefuns.c. | https://nvd.nist.gov/vuln/detail/CVE-2014-3688 |
1,269 | linux | bfd0a56b90005f8c8a004baf407ad90045c2b11e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/bfd0a56b90005f8c8a004baf407ad90045c2b11e | nEPT: Nested INVEPT
If we let L1 use EPT, we should probably also support the INVEPT instruction.
In our current nested EPT implementation, when L1 changes its EPT table
for L2 (i.e., EPT12), L0 modifies the shadow EPT table (EPT02), and in
the course of this modification already calls INVEPT. But if last level
of sh... | 1 | static bool nested_vmx_exit_handled(struct kvm_vcpu *vcpu)
{
u32 intr_info = vmcs_read32(VM_EXIT_INTR_INFO);
struct vcpu_vmx *vmx = to_vmx(vcpu);
struct vmcs12 *vmcs12 = get_vmcs12(vcpu);
u32 exit_reason = vmx->exit_reason;
if (vmx->nested.nested_run_pending)
return 0;
if (unlikely(vmx->fail)) {
pr_info_rat... | 74,454,302,223,687,580,000,000,000,000,000,000,000 | vmx.c | 251,867,498,831,949,350,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-3645 | arch/x86/kvm/vmx.c in the KVM subsystem in the Linux kernel before 3.12 does not have an exit handler for the INVEPT instruction, which allows guest OS users to cause a denial of service (guest OS crash) via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2014-3645 |
159,014 | linux | bfd0a56b90005f8c8a004baf407ad90045c2b11e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/bfd0a56b90005f8c8a004baf407ad90045c2b11e | nEPT: Nested INVEPT
If we let L1 use EPT, we should probably also support the INVEPT instruction.
In our current nested EPT implementation, when L1 changes its EPT table
for L2 (i.e., EPT12), L0 modifies the shadow EPT table (EPT02), and in
the course of this modification already calls INVEPT. But if last level
of sh... | 0 | static bool nested_vmx_exit_handled(struct kvm_vcpu *vcpu)
{
u32 intr_info = vmcs_read32(VM_EXIT_INTR_INFO);
struct vcpu_vmx *vmx = to_vmx(vcpu);
struct vmcs12 *vmcs12 = get_vmcs12(vcpu);
u32 exit_reason = vmx->exit_reason;
if (vmx->nested.nested_run_pending)
return 0;
if (unlikely(vmx->fail)) {
pr_info_rat... | 13,466,802,830,649,507,000,000,000,000,000,000,000 | vmx.c | 77,404,791,920,628,900,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-3645 | arch/x86/kvm/vmx.c in the KVM subsystem in the Linux kernel before 3.12 does not have an exit handler for the INVEPT instruction, which allows guest OS users to cause a denial of service (guest OS crash) via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2014-3645 |
1,277 | php-src | 2fefae47716d501aec41c1102f3fd4531f070b05 | https://github.com/php/php-src | https://github.com/php/php-src/commit/2fefae47716d501aec41c1102f3fd4531f070b05 | Fixed Sec Bug #67717 segfault in dns_get_record CVE-2014-3597
Incomplete fix for CVE-2014-4049
Check possible buffer overflow
- pass real buffer end to dn_expand calls
- check buffer len before each read | 1 | static u_char *php_parserr(u_char *cp, querybuf *answer, int type_to_fetch, int store, int raw, zval **subarray)
{
u_short type, class, dlen;
u_long ttl;
long n, i;
u_short s;
u_char *tp, *p;
char name[MAXHOSTNAMELEN];
int have_v6_break = 0, in_v6_break = 0;
*subarray = NULL;
n = dn_expand(answer->qb2,... | 192,550,270,728,735,170,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3597 | Multiple buffer overflows in the php_parserr function in ext/standard/dns.c in PHP before 5.4.32 and 5.5.x before 5.5.16 allow remote DNS servers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted DNS record, related to the dns_get_record function and the dn_expand functio... | https://nvd.nist.gov/vuln/detail/CVE-2014-3597 |
159,018 | php-src | 2fefae47716d501aec41c1102f3fd4531f070b05 | https://github.com/php/php-src | https://github.com/php/php-src/commit/2fefae47716d501aec41c1102f3fd4531f070b05 | Fixed Sec Bug #67717 segfault in dns_get_record CVE-2014-3597
Incomplete fix for CVE-2014-4049
Check possible buffer overflow
- pass real buffer end to dn_expand calls
- check buffer len before each read | 0 | static u_char *php_parserr(u_char *cp, querybuf *answer, int type_to_fetch, int store, int raw, zval **subarray)
static u_char *php_parserr(u_char *cp, u_char *end, querybuf *answer, int type_to_fetch, int store, int raw, zval **subarray)
{
u_short type, class, dlen;
u_long ttl;
long n, i;
u_short s;
u_char *tp... | 192,548,275,441,720,800,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3597 | Multiple buffer overflows in the php_parserr function in ext/standard/dns.c in PHP before 5.4.32 and 5.5.x before 5.5.16 allow remote DNS servers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted DNS record, related to the dns_get_record function and the dn_expand functio... | https://nvd.nist.gov/vuln/detail/CVE-2014-3597 |
1,288 | linux | 844817e47eef14141cf59b8d5ac08dd11c0a9189 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/844817e47eef14141cf59b8d5ac08dd11c0a9189 | HID: picolcd: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that raw_data
that we hold in picolcd_pending structure are always kept within proper
bounds.
Cc: stable@vger.kernel.org
Reported-... | 1 | static int picolcd_raw_event(struct hid_device *hdev,
struct hid_report *report, u8 *raw_data, int size)
{
struct picolcd_data *data = hid_get_drvdata(hdev);
unsigned long flags;
int ret = 0;
if (!data)
return 1;
if (report->id == REPORT_KEY_STATE) {
if (data->input_keys)
ret = picolcd_raw_keypad(... | 336,846,250,312,050,030,000,000,000,000,000,000,000 | hid-picolcd_core.c | 186,782,659,027,372,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3186 | Buffer overflow in the picolcd_raw_event function in devices/hid/hid-picolcd_core.c in the PicoLCD HID device driver in the Linux kernel through 3.16.3, as used in Android on Nexus 7 devices, allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a craft... | https://nvd.nist.gov/vuln/detail/CVE-2014-3186 |
159,024 | linux | 844817e47eef14141cf59b8d5ac08dd11c0a9189 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/844817e47eef14141cf59b8d5ac08dd11c0a9189 | HID: picolcd: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that raw_data
that we hold in picolcd_pending structure are always kept within proper
bounds.
Cc: stable@vger.kernel.org
Reported-... | 0 | static int picolcd_raw_event(struct hid_device *hdev,
struct hid_report *report, u8 *raw_data, int size)
{
struct picolcd_data *data = hid_get_drvdata(hdev);
unsigned long flags;
int ret = 0;
if (!data)
return 1;
if (size > 64) {
hid_warn(hdev, "invalid size value (%d) for picolcd raw event\n",
size... | 88,186,924,224,606,900,000,000,000,000,000,000,000 | hid-picolcd_core.c | 54,398,981,253,658,970,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3186 | Buffer overflow in the picolcd_raw_event function in devices/hid/hid-picolcd_core.c in the PicoLCD HID device driver in the Linux kernel through 3.16.3, as used in Android on Nexus 7 devices, allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a craft... | https://nvd.nist.gov/vuln/detail/CVE-2014-3186 |
1,290 | linux | 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | HID: fix a couple of off-by-ones
There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing fixup. Fix those.
Cc: stable@vger.kernel.org
Reported-by: Ben Hawkes <hawkes@google.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jir... | 1 | static __u8 *ch_report_fixup(struct hid_device *hdev, __u8 *rdesc,
unsigned int *rsize)
{
if (*rsize >= 17 && rdesc[11] == 0x3c && rdesc[12] == 0x02) {
hid_info(hdev, "fixing up Cherry Cymotion report descriptor\n");
rdesc[11] = rdesc[16] = 0xff;
rdesc[12] = rdesc[17] = 0x03;
}
return rdesc;
}
| 45,538,586,871,323,170,000,000,000,000,000,000,000 | hid-cherry.c | 187,455,207,934,208,830,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3184 | The report_fixup functions in the HID subsystem in the Linux kernel before 3.16.2 might allow physically proximate attackers to cause a denial of service (out-of-bounds write) via a crafted device that provides a small report descriptor, related to (1) drivers/hid/hid-cherry.c, (2) drivers/hid/hid-kye.c, (3) drivers/hi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3184 |
159,025 | linux | 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | HID: fix a couple of off-by-ones
There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing fixup. Fix those.
Cc: stable@vger.kernel.org
Reported-by: Ben Hawkes <hawkes@google.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jir... | 0 | static __u8 *ch_report_fixup(struct hid_device *hdev, __u8 *rdesc,
unsigned int *rsize)
{
if (*rsize >= 18 && rdesc[11] == 0x3c && rdesc[12] == 0x02) {
hid_info(hdev, "fixing up Cherry Cymotion report descriptor\n");
rdesc[11] = rdesc[16] = 0xff;
rdesc[12] = rdesc[17] = 0x03;
}
return rdesc;
}
| 256,834,588,490,855,440,000,000,000,000,000,000,000 | hid-cherry.c | 95,105,781,901,221,440,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3184 | The report_fixup functions in the HID subsystem in the Linux kernel before 3.16.2 might allow physically proximate attackers to cause a denial of service (out-of-bounds write) via a crafted device that provides a small report descriptor, related to (1) drivers/hid/hid-cherry.c, (2) drivers/hid/hid-kye.c, (3) drivers/hi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3184 |
1,291 | linux | 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | HID: fix a couple of off-by-ones
There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing fixup. Fix those.
Cc: stable@vger.kernel.org
Reported-by: Ben Hawkes <hawkes@google.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jir... | 1 | static __u8 *kye_report_fixup(struct hid_device *hdev, __u8 *rdesc,
unsigned int *rsize)
{
switch (hdev->product) {
case USB_DEVICE_ID_KYE_ERGO_525V:
/* the fixups that need to be done:
* - change led usage page to button for extra buttons
* - report size 8 count 1 must be size 1 count 8 for button
*... | 61,701,421,720,071,810,000,000,000,000,000,000,000 | hid-kye.c | 236,592,989,497,276,160,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3184 | The report_fixup functions in the HID subsystem in the Linux kernel before 3.16.2 might allow physically proximate attackers to cause a denial of service (out-of-bounds write) via a crafted device that provides a small report descriptor, related to (1) drivers/hid/hid-cherry.c, (2) drivers/hid/hid-kye.c, (3) drivers/hi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3184 |
159,026 | linux | 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | HID: fix a couple of off-by-ones
There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing fixup. Fix those.
Cc: stable@vger.kernel.org
Reported-by: Ben Hawkes <hawkes@google.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jir... | 0 | static __u8 *kye_report_fixup(struct hid_device *hdev, __u8 *rdesc,
unsigned int *rsize)
{
switch (hdev->product) {
case USB_DEVICE_ID_KYE_ERGO_525V:
/* the fixups that need to be done:
* - change led usage page to button for extra buttons
* - report size 8 count 1 must be size 1 count 8 for button
*... | 10,461,272,926,352,127,000,000,000,000,000,000,000 | hid-kye.c | 203,442,816,039,038,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3184 | The report_fixup functions in the HID subsystem in the Linux kernel before 3.16.2 might allow physically proximate attackers to cause a denial of service (out-of-bounds write) via a crafted device that provides a small report descriptor, related to (1) drivers/hid/hid-cherry.c, (2) drivers/hid/hid-kye.c, (3) drivers/hi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3184 |
1,292 | linux | 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | HID: fix a couple of off-by-ones
There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing fixup. Fix those.
Cc: stable@vger.kernel.org
Reported-by: Ben Hawkes <hawkes@google.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jir... | 1 | static __u8 *lg_report_fixup(struct hid_device *hdev, __u8 *rdesc,
unsigned int *rsize)
{
struct lg_drv_data *drv_data = hid_get_drvdata(hdev);
struct usb_device_descriptor *udesc;
__u16 bcdDevice, rev_maj, rev_min;
if ((drv_data->quirks & LG_RDESC) && *rsize >= 90 && rdesc[83] == 0x26 &&
rdesc[84] == 0x8... | 279,704,939,167,865,600,000,000,000,000,000,000,000 | hid-lg.c | 90,537,780,722,919,720,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3184 | The report_fixup functions in the HID subsystem in the Linux kernel before 3.16.2 might allow physically proximate attackers to cause a denial of service (out-of-bounds write) via a crafted device that provides a small report descriptor, related to (1) drivers/hid/hid-cherry.c, (2) drivers/hid/hid-kye.c, (3) drivers/hi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3184 |
159,027 | linux | 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | HID: fix a couple of off-by-ones
There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing fixup. Fix those.
Cc: stable@vger.kernel.org
Reported-by: Ben Hawkes <hawkes@google.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jir... | 0 | static __u8 *lg_report_fixup(struct hid_device *hdev, __u8 *rdesc,
unsigned int *rsize)
{
struct lg_drv_data *drv_data = hid_get_drvdata(hdev);
struct usb_device_descriptor *udesc;
__u16 bcdDevice, rev_maj, rev_min;
if ((drv_data->quirks & LG_RDESC) && *rsize >= 91 && rdesc[83] == 0x26 &&
rdesc[84] == 0x8... | 332,754,560,908,671,200,000,000,000,000,000,000,000 | hid-lg.c | 208,620,246,657,498,000,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3184 | The report_fixup functions in the HID subsystem in the Linux kernel before 3.16.2 might allow physically proximate attackers to cause a denial of service (out-of-bounds write) via a crafted device that provides a small report descriptor, related to (1) drivers/hid/hid-cherry.c, (2) drivers/hid/hid-kye.c, (3) drivers/hi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3184 |
1,293 | linux | 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | HID: fix a couple of off-by-ones
There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing fixup. Fix those.
Cc: stable@vger.kernel.org
Reported-by: Ben Hawkes <hawkes@google.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jir... | 1 | static __u8 *mr_report_fixup(struct hid_device *hdev, __u8 *rdesc,
unsigned int *rsize)
{
if (*rsize >= 30 && rdesc[29] == 0x05 && rdesc[30] == 0x09) {
hid_info(hdev, "fixing up button/consumer in HID report descriptor\n");
rdesc[30] = 0x0c;
}
return rdesc;
}
| 85,432,680,744,687,480,000,000,000,000,000,000,000 | hid-monterey.c | 41,416,622,423,334,174,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3184 | The report_fixup functions in the HID subsystem in the Linux kernel before 3.16.2 might allow physically proximate attackers to cause a denial of service (out-of-bounds write) via a crafted device that provides a small report descriptor, related to (1) drivers/hid/hid-cherry.c, (2) drivers/hid/hid-kye.c, (3) drivers/hi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3184 |
159,028 | linux | 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | HID: fix a couple of off-by-ones
There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing fixup. Fix those.
Cc: stable@vger.kernel.org
Reported-by: Ben Hawkes <hawkes@google.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jir... | 0 | static __u8 *mr_report_fixup(struct hid_device *hdev, __u8 *rdesc,
unsigned int *rsize)
{
if (*rsize >= 31 && rdesc[29] == 0x05 && rdesc[30] == 0x09) {
hid_info(hdev, "fixing up button/consumer in HID report descriptor\n");
rdesc[30] = 0x0c;
}
return rdesc;
}
| 306,209,230,722,426,340,000,000,000,000,000,000,000 | hid-monterey.c | 73,908,707,322,200,200,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3184 | The report_fixup functions in the HID subsystem in the Linux kernel before 3.16.2 might allow physically proximate attackers to cause a denial of service (out-of-bounds write) via a crafted device that provides a small report descriptor, related to (1) drivers/hid/hid-cherry.c, (2) drivers/hid/hid-kye.c, (3) drivers/hi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3184 |
1,294 | linux | 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | HID: fix a couple of off-by-ones
There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing fixup. Fix those.
Cc: stable@vger.kernel.org
Reported-by: Ben Hawkes <hawkes@google.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jir... | 1 | static __u8 *pl_report_fixup(struct hid_device *hdev, __u8 *rdesc,
unsigned int *rsize)
{
if (*rsize >= 60 && rdesc[39] == 0x2a && rdesc[40] == 0xf5 &&
rdesc[41] == 0x00 && rdesc[59] == 0x26 &&
rdesc[60] == 0xf9 && rdesc[61] == 0x00) {
hid_info(hdev, "fixing up Petalynx Maxter Remote report descriptor\... | 284,095,831,257,846,900,000,000,000,000,000,000,000 | hid-petalynx.c | 174,245,996,495,446,770,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3184 | The report_fixup functions in the HID subsystem in the Linux kernel before 3.16.2 might allow physically proximate attackers to cause a denial of service (out-of-bounds write) via a crafted device that provides a small report descriptor, related to (1) drivers/hid/hid-cherry.c, (2) drivers/hid/hid-kye.c, (3) drivers/hi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3184 |
159,029 | linux | 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | HID: fix a couple of off-by-ones
There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing fixup. Fix those.
Cc: stable@vger.kernel.org
Reported-by: Ben Hawkes <hawkes@google.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jir... | 0 | static __u8 *pl_report_fixup(struct hid_device *hdev, __u8 *rdesc,
unsigned int *rsize)
{
if (*rsize >= 62 && rdesc[39] == 0x2a && rdesc[40] == 0xf5 &&
rdesc[41] == 0x00 && rdesc[59] == 0x26 &&
rdesc[60] == 0xf9 && rdesc[61] == 0x00) {
hid_info(hdev, "fixing up Petalynx Maxter Remote report descriptor\... | 320,643,472,641,519,640,000,000,000,000,000,000,000 | hid-petalynx.c | 198,495,724,561,306,000,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3184 | The report_fixup functions in the HID subsystem in the Linux kernel before 3.16.2 might allow physically proximate attackers to cause a denial of service (out-of-bounds write) via a crafted device that provides a small report descriptor, related to (1) drivers/hid/hid-cherry.c, (2) drivers/hid/hid-kye.c, (3) drivers/hi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3184 |
1,295 | linux | 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | HID: fix a couple of off-by-ones
There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing fixup. Fix those.
Cc: stable@vger.kernel.org
Reported-by: Ben Hawkes <hawkes@google.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jir... | 1 | static __u8 *sp_report_fixup(struct hid_device *hdev, __u8 *rdesc,
unsigned int *rsize)
{
if (*rsize >= 107 && rdesc[104] == 0x26 && rdesc[105] == 0x80 &&
rdesc[106] == 0x03) {
hid_info(hdev, "fixing up Sunplus Wireless Desktop report descriptor\n");
rdesc[105] = rdesc[110] = 0x03;
rdesc[106] = rdesc[... | 187,317,300,382,672,400,000,000,000,000,000,000,000 | hid-sunplus.c | 175,340,908,370,041,700,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3184 | The report_fixup functions in the HID subsystem in the Linux kernel before 3.16.2 might allow physically proximate attackers to cause a denial of service (out-of-bounds write) via a crafted device that provides a small report descriptor, related to (1) drivers/hid/hid-cherry.c, (2) drivers/hid/hid-kye.c, (3) drivers/hi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3184 |
159,030 | linux | 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ab25786c87eb20857bbb715c3ae34ec8fd6a214 | HID: fix a couple of off-by-ones
There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing fixup. Fix those.
Cc: stable@vger.kernel.org
Reported-by: Ben Hawkes <hawkes@google.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jir... | 0 | static __u8 *sp_report_fixup(struct hid_device *hdev, __u8 *rdesc,
unsigned int *rsize)
{
if (*rsize >= 112 && rdesc[104] == 0x26 && rdesc[105] == 0x80 &&
rdesc[106] == 0x03) {
hid_info(hdev, "fixing up Sunplus Wireless Desktop report descriptor\n");
rdesc[105] = rdesc[110] = 0x03;
rdesc[106] = rdesc[... | 112,667,349,109,587,650,000,000,000,000,000,000,000 | hid-sunplus.c | 218,029,391,092,850,470,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3184 | The report_fixup functions in the HID subsystem in the Linux kernel before 3.16.2 might allow physically proximate attackers to cause a denial of service (out-of-bounds write) via a crafted device that provides a small report descriptor, related to (1) drivers/hid/hid-cherry.c, (2) drivers/hid/hid-kye.c, (3) drivers/hi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3184 |
1,297 | linux | ad3e14d7c5268c2e24477c6ef54bbdf88add5d36 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ad3e14d7c5268c2e24477c6ef54bbdf88add5d36 | HID: logitech: perform bounds checking on device_id early enough
device_index is a char type and the size of paired_dj_deivces is 7
elements, therefore proper bounds checking has to be applied to
device_index before it is used.
We are currently performing the bounds checking in
logi_dj_recv_add_djhid_device(), which ... | 1 | static int logi_dj_raw_event(struct hid_device *hdev,
struct hid_report *report, u8 *data,
int size)
{
struct dj_receiver_dev *djrcv_dev = hid_get_drvdata(hdev);
struct dj_report *dj_report = (struct dj_report *) data;
unsigned long flags;
bool report_processed = false;
dbg_hid("%s, size:%d\n", __... | 260,936,126,132,763,400,000,000,000,000,000,000,000 | hid-logitech-dj.c | 139,550,206,137,274,650,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3182 | Array index error in the logi_dj_raw_event function in drivers/hid/hid-logitech-dj.c in the Linux kernel before 3.16.2 allows physically proximate attackers to execute arbitrary code or cause a denial of service (invalid kfree) via a crafted device that provides a malformed REPORT_TYPE_NOTIF_DEVICE_UNPAIRED value. | https://nvd.nist.gov/vuln/detail/CVE-2014-3182 |
159,031 | linux | ad3e14d7c5268c2e24477c6ef54bbdf88add5d36 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ad3e14d7c5268c2e24477c6ef54bbdf88add5d36 | HID: logitech: perform bounds checking on device_id early enough
device_index is a char type and the size of paired_dj_deivces is 7
elements, therefore proper bounds checking has to be applied to
device_index before it is used.
We are currently performing the bounds checking in
logi_dj_recv_add_djhid_device(), which ... | 0 | static int logi_dj_raw_event(struct hid_device *hdev,
struct hid_report *report, u8 *data,
int size)
{
struct dj_receiver_dev *djrcv_dev = hid_get_drvdata(hdev);
struct dj_report *dj_report = (struct dj_report *) data;
unsigned long flags;
bool report_processed = false;
dbg_hid("%s, size:%d\n", __... | 287,545,158,993,420,740,000,000,000,000,000,000,000 | hid-logitech-dj.c | 286,797,026,497,837,260,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3182 | Array index error in the logi_dj_raw_event function in drivers/hid/hid-logitech-dj.c in the Linux kernel before 3.16.2 allows physically proximate attackers to execute arbitrary code or cause a denial of service (invalid kfree) via a crafted device that provides a malformed REPORT_TYPE_NOTIF_DEVICE_UNPAIRED value. | https://nvd.nist.gov/vuln/detail/CVE-2014-3182 |
1,299 | linux | c54def7bd64d7c0b6993336abcffb8444795bf38 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c54def7bd64d7c0b6993336abcffb8444795bf38 | HID: magicmouse: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that
magicmouse_emit_touch() gets only valid values of raw_id.
Cc: stable@vger.kernel.org
Reported-by: Steven Vittitoe <scvitti... | 1 | static int magicmouse_raw_event(struct hid_device *hdev,
struct hid_report *report, u8 *data, int size)
{
struct magicmouse_sc *msc = hid_get_drvdata(hdev);
struct input_dev *input = msc->input;
int x = 0, y = 0, ii, clicks = 0, npoints;
switch (data[0]) {
case TRACKPAD_REPORT_ID:
/* Expect four bytes of pref... | 281,911,557,577,455,930,000,000,000,000,000,000,000 | hid-magicmouse.c | 134,181,979,015,041,700,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3181 | Multiple stack-based buffer overflows in the magicmouse_raw_event function in drivers/hid/hid-magicmouse.c in the Magic Mouse HID driver in the Linux kernel through 3.16.3 allow physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that provid... | https://nvd.nist.gov/vuln/detail/CVE-2014-3181 |
159,033 | linux | c54def7bd64d7c0b6993336abcffb8444795bf38 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c54def7bd64d7c0b6993336abcffb8444795bf38 | HID: magicmouse: sanity check report size in raw_event() callback
The report passed to us from transport driver could potentially be
arbitrarily large, therefore we better sanity-check it so that
magicmouse_emit_touch() gets only valid values of raw_id.
Cc: stable@vger.kernel.org
Reported-by: Steven Vittitoe <scvitti... | 0 | static int magicmouse_raw_event(struct hid_device *hdev,
struct hid_report *report, u8 *data, int size)
{
struct magicmouse_sc *msc = hid_get_drvdata(hdev);
struct input_dev *input = msc->input;
int x = 0, y = 0, ii, clicks = 0, npoints;
switch (data[0]) {
case TRACKPAD_REPORT_ID:
/* Expect four bytes of pref... | 27,035,854,668,166,610,000,000,000,000,000,000,000 | hid-magicmouse.c | 2,593,342,493,104,003,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3181 | Multiple stack-based buffer overflows in the magicmouse_raw_event function in drivers/hid/hid-magicmouse.c in the Magic Mouse HID driver in the Linux kernel through 3.16.3 allow physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that provid... | https://nvd.nist.gov/vuln/detail/CVE-2014-3181 |
1,300 | ppp | 7658e8257183f062dc01f87969c140707c7e52cb | https://github.com/paulusmack/ppp | https://github.com/paulusmack/ppp/commit/7658e8257183f062dc01f87969c140707c7e52cb | pppd: Eliminate potential integer overflow in option parsing
When we are reading in a word from an options file, we maintain a count
of the length we have seen so far in 'len', which is an int. When len
exceeds MAXWORDLEN - 1 (i.e. 1023) we cease storing characters in the
buffer but we continue to increment len. Sin... | 1 | getword(f, word, newlinep, filename)
FILE *f;
char *word;
int *newlinep;
char *filename;
{
int c, len, escape;
int quoted, comment;
int value, digit, got, n;
#define isoctal(c) ((c) >= '0' && (c) < '8')
*newlinep = 0;
len = 0;
escape = 0;
comment = 0;
quoted = 0;
/... | 136,171,222,581,299,580,000,000,000,000,000,000,000 | options.c | 280,913,819,064,269,670,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3158 | Integer overflow in the getword function in options.c in pppd in Paul's PPP Package (ppp) before 2.4.7 allows attackers to "access privileged options" via a long word in an options file, which triggers a heap-based buffer overflow that "[corrupts] security-relevant variables." | https://nvd.nist.gov/vuln/detail/CVE-2014-3158 |
159,034 | ppp | 7658e8257183f062dc01f87969c140707c7e52cb | https://github.com/paulusmack/ppp | https://github.com/paulusmack/ppp/commit/7658e8257183f062dc01f87969c140707c7e52cb | pppd: Eliminate potential integer overflow in option parsing
When we are reading in a word from an options file, we maintain a count
of the length we have seen so far in 'len', which is an int. When len
exceeds MAXWORDLEN - 1 (i.e. 1023) we cease storing characters in the
buffer but we continue to increment len. Sin... | 0 | getword(f, word, newlinep, filename)
FILE *f;
char *word;
int *newlinep;
char *filename;
{
int c, len, escape;
int quoted, comment;
int value, digit, got, n;
#define isoctal(c) ((c) >= '0' && (c) < '8')
*newlinep = 0;
len = 0;
escape = 0;
comment = 0;
quoted = 0;
/... | 159,772,156,127,277,370,000,000,000,000,000,000,000 | options.c | 308,269,249,332,257,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3158 | Integer overflow in the getword function in options.c in pppd in Paul's PPP Package (ppp) before 2.4.7 allows attackers to "access privileged options" via a long word in an options file, which triggers a heap-based buffer overflow that "[corrupts] security-relevant variables." | https://nvd.nist.gov/vuln/detail/CVE-2014-3158 |
1,301 | linux | e9c243a5a6de0be8e584c604d353412584b592f8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e9c243a5a6de0be8e584c604d353412584b592f8 | futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr == uaddr2 in futex_requeue(..., requeue_pi=1)
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, then
dangling pointers may be left for rt_waiter resulting in an expl... | 1 | static int futex_requeue(u32 __user *uaddr1, unsigned int flags,
u32 __user *uaddr2, int nr_wake, int nr_requeue,
u32 *cmpval, int requeue_pi)
{
union futex_key key1 = FUTEX_KEY_INIT, key2 = FUTEX_KEY_INIT;
int drop_count = 0, task_count = 0, ret;
struct futex_pi_state *pi_state = NULL;
struct futex_hash_bu... | 17,926,925,629,239,018,000,000,000,000,000,000,000 | futex.c | 242,837,931,013,533,500,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3153 | The futex_requeue function in kernel/futex.c in the Linux kernel through 3.14.5 does not ensure that calls have two different futex addresses, which allows local users to gain privileges via a crafted FUTEX_REQUEUE command that facilitates unsafe waiter modification. | https://nvd.nist.gov/vuln/detail/CVE-2014-3153 |
159,035 | linux | e9c243a5a6de0be8e584c604d353412584b592f8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e9c243a5a6de0be8e584c604d353412584b592f8 | futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr == uaddr2 in futex_requeue(..., requeue_pi=1)
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, then
dangling pointers may be left for rt_waiter resulting in an expl... | 0 | static int futex_requeue(u32 __user *uaddr1, unsigned int flags,
u32 __user *uaddr2, int nr_wake, int nr_requeue,
u32 *cmpval, int requeue_pi)
{
union futex_key key1 = FUTEX_KEY_INIT, key2 = FUTEX_KEY_INIT;
int drop_count = 0, task_count = 0, ret;
struct futex_pi_state *pi_state = NULL;
struct futex_hash_bu... | 260,267,407,366,516,340,000,000,000,000,000,000,000 | futex.c | 213,479,601,755,205,720,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3153 | The futex_requeue function in kernel/futex.c in the Linux kernel through 3.14.5 does not ensure that calls have two different futex addresses, which allows local users to gain privileges via a crafted FUTEX_REQUEUE command that facilitates unsafe waiter modification. | https://nvd.nist.gov/vuln/detail/CVE-2014-3153 |
1,303 | linux | 05ab8f2647e4221cbdb3856dd7d32bd5407316b3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/05ab8f2647e4221cbdb3856dd7d32bd5407316b3 | filter: prevent nla extensions to peek beyond the end of the message
The BPF_S_ANC_NLATTR and BPF_S_ANC_NLATTR_NEST extensions fail to check
for a minimal message length before testing the supplied offset to be
within the bounds of the message. This allows the subtraction of the nla
header to underflow and therefore -... | 1 | static u64 __skb_get_nlattr_nest(u64 ctx, u64 A, u64 X, u64 r4, u64 r5)
{
struct sk_buff *skb = (struct sk_buff *)(long) ctx;
struct nlattr *nla;
if (skb_is_nonlinear(skb))
return 0;
if (A > skb->len - sizeof(struct nlattr))
return 0;
nla = (struct nlattr *) &skb->data[A];
if (nla->nla_len > A - skb... | 282,497,948,287,924,030,000,000,000,000,000,000,000 | filter.c | 228,552,301,451,129,950,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-3144 | The (1) BPF_S_ANC_NLATTR and (2) BPF_S_ANC_NLATTR_NEST extension implementations in the sk_run_filter function in net/core/filter.c in the Linux kernel through 3.14.3 do not check whether a certain length value is sufficiently large, which allows local users to cause a denial of service (integer underflow and system cr... | https://nvd.nist.gov/vuln/detail/CVE-2014-3144 |
159,037 | linux | 05ab8f2647e4221cbdb3856dd7d32bd5407316b3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/05ab8f2647e4221cbdb3856dd7d32bd5407316b3 | filter: prevent nla extensions to peek beyond the end of the message
The BPF_S_ANC_NLATTR and BPF_S_ANC_NLATTR_NEST extensions fail to check
for a minimal message length before testing the supplied offset to be
within the bounds of the message. This allows the subtraction of the nla
header to underflow and therefore -... | 0 | static u64 __skb_get_nlattr_nest(u64 ctx, u64 A, u64 X, u64 r4, u64 r5)
{
struct sk_buff *skb = (struct sk_buff *)(long) ctx;
struct nlattr *nla;
if (skb_is_nonlinear(skb))
return 0;
if (skb->len < sizeof(struct nlattr))
return 0;
if (A > skb->len - sizeof(struct nlattr))
return 0;
nla = (struct ... | 238,463,992,730,366,800,000,000,000,000,000,000,000 | filter.c | 293,672,119,478,249,640,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-3144 | The (1) BPF_S_ANC_NLATTR and (2) BPF_S_ANC_NLATTR_NEST extension implementations in the sk_run_filter function in net/core/filter.c in the Linux kernel through 3.14.3 do not check whether a certain length value is sufficiently large, which allows local users to cause a denial of service (integer underflow and system cr... | https://nvd.nist.gov/vuln/detail/CVE-2014-3144 |
9,271 | linux | 05ab8f2647e4221cbdb3856dd7d32bd5407316b3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/05ab8f2647e4221cbdb3856dd7d32bd5407316b3 | filter: prevent nla extensions to peek beyond the end of the message
The BPF_S_ANC_NLATTR and BPF_S_ANC_NLATTR_NEST extensions fail to check
for a minimal message length before testing the supplied offset to be
within the bounds of the message. This allows the subtraction of the nla
header to underflow and therefore -... | 1 | static u64 __skb_get_nlattr(u64 ctx, u64 A, u64 X, u64 r4, u64 r5)
{
struct sk_buff *skb = (struct sk_buff *)(long) ctx;
struct nlattr *nla;
if (skb_is_nonlinear(skb))
return 0;
if (A > skb->len - sizeof(struct nlattr))
return 0;
nla = nla_find((struct nlattr *) &skb->data[A], skb->len - A, X);
if (n... | 257,641,762,135,738,580,000,000,000,000,000,000,000 | filter.c | 228,552,301,451,129,950,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-3144 | The (1) BPF_S_ANC_NLATTR and (2) BPF_S_ANC_NLATTR_NEST extension implementations in the sk_run_filter function in net/core/filter.c in the Linux kernel through 3.14.3 do not check whether a certain length value is sufficiently large, which allows local users to cause a denial of service (integer underflow and system cr... | https://nvd.nist.gov/vuln/detail/CVE-2014-3144 |
184,406 | linux | 05ab8f2647e4221cbdb3856dd7d32bd5407316b3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/05ab8f2647e4221cbdb3856dd7d32bd5407316b3 | filter: prevent nla extensions to peek beyond the end of the message
The BPF_S_ANC_NLATTR and BPF_S_ANC_NLATTR_NEST extensions fail to check
for a minimal message length before testing the supplied offset to be
within the bounds of the message. This allows the subtraction of the nla
header to underflow and therefore -... | 0 | static u64 __skb_get_nlattr(u64 ctx, u64 A, u64 X, u64 r4, u64 r5)
{
struct sk_buff *skb = (struct sk_buff *)(long) ctx;
struct nlattr *nla;
if (skb_is_nonlinear(skb))
return 0;
if (skb->len < sizeof(struct nlattr))
return 0;
if (A > skb->len - sizeof(struct nlattr))
return 0;
nla = nla_find((stru... | 77,719,296,777,876,180,000,000,000,000,000,000,000 | filter.c | 293,672,119,478,249,640,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-3144 | The (1) BPF_S_ANC_NLATTR and (2) BPF_S_ANC_NLATTR_NEST extension implementations in the sk_run_filter function in net/core/filter.c in the Linux kernel through 3.14.3 do not check whether a certain length value is sufficiently large, which allows local users to cause a denial of service (integer underflow and system cr... | https://nvd.nist.gov/vuln/detail/CVE-2014-3144 |
1,305 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 1 | static int try_to_unmap_cluster(unsigned long cursor, unsigned int *mapcount,
struct vm_area_struct *vma, struct page *check_page)
{
struct mm_struct *mm = vma->vm_mm;
pmd_t *pmd;
pte_t *pte;
pte_t pteval;
spinlock_t *ptl;
struct page *page;
unsigned long address;
unsigned long mmun_start; /* For mmu_notifier... | 1,665,666,048,709,289,200,000,000,000,000,000,000 | rmap.c | 257,810,476,724,514,140,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
159,039 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static int try_to_unmap_cluster(unsigned long cursor, unsigned int *mapcount,
struct vm_area_struct *vma, struct page *check_page)
{
struct mm_struct *mm = vma->vm_mm;
pmd_t *pmd;
pte_t *pte;
pte_t pteval;
spinlock_t *ptl;
struct page *page;
unsigned long address;
unsigned long mmun_start; /* For mmu_notifier... | 110,655,981,381,747,470,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
1,306 | linux | a03ffcf873fe0f2565386ca8ef832144c42e67fa | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a03ffcf873fe0f2565386ca8ef832144c42e67fa | net: bpf_jit: fix an off-one bug in x86_64 cond jump target
x86 jump instruction size is 2 or 5 bytes (near/long jump), not 2 or 6
bytes.
In case a conditional jump is followed by a long jump, conditional jump
target is one byte past the start of target instruction.
Signed-off-by: Markus Kötter <nepenthesdev@gmail.c... | 1 | void bpf_jit_compile(struct sk_filter *fp)
{
u8 temp[64];
u8 *prog;
unsigned int proglen, oldproglen = 0;
int ilen, i;
int t_offset, f_offset;
u8 t_op, f_op, seen = 0, pass;
u8 *image = NULL;
u8 *func;
int pc_ret0 = -1; /* bpf index of first RET #0 instruction (if any) */
unsigned int cleanup_addr; /* epilogu... | 197,306,910,127,583,670,000,000,000,000,000,000,000 | bpf_jit_comp.c | 118,916,419,377,068,630,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-2889 | Off-by-one error in the bpf_jit_compile function in arch/x86/net/bpf_jit_comp.c in the Linux kernel before 3.1.8, when BPF JIT is enabled, allows local users to cause a denial of service (system crash) or possibly gain privileges via a long jump after a conditional jump. | https://nvd.nist.gov/vuln/detail/CVE-2014-2889 |
159,040 | linux | a03ffcf873fe0f2565386ca8ef832144c42e67fa | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a03ffcf873fe0f2565386ca8ef832144c42e67fa | net: bpf_jit: fix an off-one bug in x86_64 cond jump target
x86 jump instruction size is 2 or 5 bytes (near/long jump), not 2 or 6
bytes.
In case a conditional jump is followed by a long jump, conditional jump
target is one byte past the start of target instruction.
Signed-off-by: Markus Kötter <nepenthesdev@gmail.c... | 0 | void bpf_jit_compile(struct sk_filter *fp)
{
u8 temp[64];
u8 *prog;
unsigned int proglen, oldproglen = 0;
int ilen, i;
int t_offset, f_offset;
u8 t_op, f_op, seen = 0, pass;
u8 *image = NULL;
u8 *func;
int pc_ret0 = -1; /* bpf index of first RET #0 instruction (if any) */
unsigned int cleanup_addr; /* epilogu... | 67,387,289,507,214,140,000,000,000,000,000,000,000 | bpf_jit_comp.c | 114,327,817,519,201,570,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-2889 | Off-by-one error in the bpf_jit_compile function in arch/x86/net/bpf_jit_comp.c in the Linux kernel before 3.1.8, when BPF JIT is enabled, allows local users to cause a denial of service (system crash) or possibly gain privileges via a long jump after a conditional jump. | https://nvd.nist.gov/vuln/detail/CVE-2014-2889 |
1,308 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 1 | static int cma_req_handler(struct ib_cm_id *cm_id, struct ib_cm_event *ib_event)
{
struct rdma_id_private *listen_id, *conn_id;
struct rdma_cm_event event;
int offset, ret;
u8 smac[ETH_ALEN];
u8 alt_smac[ETH_ALEN];
u8 *psmac = smac;
u8 *palt_smac = alt_smac;
int is_iboe = ((rdma_node_get_transport(cm_id->dev... | 47,485,012,312,962,950,000,000,000,000,000,000,000 | cma.c | 19,353,323,018,740,810,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
159,042 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static int cma_req_handler(struct ib_cm_id *cm_id, struct ib_cm_event *ib_event)
{
struct rdma_id_private *listen_id, *conn_id;
struct rdma_cm_event event;
int offset, ret;
listen_id = cm_id->context;
if (!cma_check_req_qp_type(&listen_id->id, ib_event))
return -EINVAL;
if (cma_disable_callback(listen_i... | 214,600,362,712,127,200,000,000,000,000,000,000,000 | cma.c | 99,207,925,578,879,960,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
1,310 | linux | 1d147bfa64293b2723c4fec50922168658e613ba | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1d147bfa64293b2723c4fec50922168658e613ba | mac80211: fix AP powersave TX vs. wakeup race
There is a race between the TX path and the STA wakeup: while
a station is sleeping, mac80211 buffers frames until it wakes
up, then the frames are transmitted. However, the RX and TX
path are concurrent, so the packet indicating wakeup can be
processed while a packet is b... | 1 | ieee80211_tx_h_unicast_ps_buf(struct ieee80211_tx_data *tx)
{
struct sta_info *sta = tx->sta;
struct ieee80211_tx_info *info = IEEE80211_SKB_CB(tx->skb);
struct ieee80211_local *local = tx->local;
if (unlikely(!sta))
return TX_CONTINUE;
if (unlikely((test_sta_flag(sta, WLAN_STA_PS_STA) ||
test_sta_flag... | 293,546,470,110,660,300,000,000,000,000,000,000,000 | tx.c | 290,987,740,570,977,330,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2014-2706 | Race condition in the mac80211 subsystem in the Linux kernel before 3.13.7 allows remote attackers to cause a denial of service (system crash) via network traffic that improperly interacts with the WLAN_STA_PS_STA state (aka power-save mode), related to sta_info.c and tx.c. | https://nvd.nist.gov/vuln/detail/CVE-2014-2706 |
159,044 | linux | 1d147bfa64293b2723c4fec50922168658e613ba | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1d147bfa64293b2723c4fec50922168658e613ba | mac80211: fix AP powersave TX vs. wakeup race
There is a race between the TX path and the STA wakeup: while
a station is sleeping, mac80211 buffers frames until it wakes
up, then the frames are transmitted. However, the RX and TX
path are concurrent, so the packet indicating wakeup can be
processed while a packet is b... | 0 | ieee80211_tx_h_unicast_ps_buf(struct ieee80211_tx_data *tx)
{
struct sta_info *sta = tx->sta;
struct ieee80211_tx_info *info = IEEE80211_SKB_CB(tx->skb);
struct ieee80211_local *local = tx->local;
if (unlikely(!sta))
return TX_CONTINUE;
if (unlikely((test_sta_flag(sta, WLAN_STA_PS_STA) ||
test_sta_flag... | 78,487,512,655,196,430,000,000,000,000,000,000,000 | tx.c | 44,689,972,293,708,320,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2014-2706 | Race condition in the mac80211 subsystem in the Linux kernel before 3.13.7 allows remote attackers to cause a denial of service (system crash) via network traffic that improperly interacts with the WLAN_STA_PS_STA state (aka power-save mode), related to sta_info.c and tx.c. | https://nvd.nist.gov/vuln/detail/CVE-2014-2706 |
1,311 | linux | 621b5060e823301d0cba4cb52a7ee3491922d291 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/621b5060e823301d0cba4cb52a7ee3491922d291 | powerpc/tm: Fix crash when forking inside a transaction
When we fork/clone we currently don't copy any of the TM state to the new
thread. This results in a TM bad thing (program check) when the new process is
switched in as the kernel does a tmrechkpt with TEXASR FS not set. Also, since
R1 is from userspace, we trig... | 1 | int arch_dup_task_struct(struct task_struct *dst, struct task_struct *src)
{
flush_fp_to_thread(src);
flush_altivec_to_thread(src);
flush_vsx_to_thread(src);
flush_spe_to_thread(src);
*dst = *src;
clear_task_ebb(dst);
return 0;
}
| 5,326,801,381,502,656,000,000,000,000,000,000,000 | process.c | 319,797,184,082,093,000,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2673 | The arch_dup_task_struct function in the Transactional Memory (TM) implementation in arch/powerpc/kernel/process.c in the Linux kernel before 3.13.7 on the powerpc platform does not properly interact with the clone and fork system calls, which allows local users to cause a denial of service (Program Check and system cr... | https://nvd.nist.gov/vuln/detail/CVE-2014-2673 |
159,045 | linux | 621b5060e823301d0cba4cb52a7ee3491922d291 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/621b5060e823301d0cba4cb52a7ee3491922d291 | powerpc/tm: Fix crash when forking inside a transaction
When we fork/clone we currently don't copy any of the TM state to the new
thread. This results in a TM bad thing (program check) when the new process is
switched in as the kernel does a tmrechkpt with TEXASR FS not set. Also, since
R1 is from userspace, we trig... | 0 | int arch_dup_task_struct(struct task_struct *dst, struct task_struct *src)
{
flush_fp_to_thread(src);
flush_altivec_to_thread(src);
flush_vsx_to_thread(src);
flush_spe_to_thread(src);
/*
* Flush TM state out so we can copy it. __switch_to_tm() does this
* flush but it removes the checkpointed state from th... | 91,749,587,929,645,170,000,000,000,000,000,000,000 | process.c | 179,484,035,131,390,370,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2673 | The arch_dup_task_struct function in the Transactional Memory (TM) implementation in arch/powerpc/kernel/process.c in the Linux kernel before 3.13.7 on the powerpc platform does not properly interact with the clone and fork system calls, which allows local users to cause a denial of service (Program Check and system cr... | https://nvd.nist.gov/vuln/detail/CVE-2014-2673 |
1,312 | linux | 21f8aaee0c62708654988ce092838aa7df4d25d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/21f8aaee0c62708654988ce092838aa7df4d25d8 | ath9k: protect tid->sched check
We check tid->sched without a lock taken on ath_tx_aggr_sleep(). That
is race condition which can result of doing list_del(&tid->list) twice
(second time with poisoned list node) and cause crash like shown below:
[424271.637220] BUG: unable to handle kernel paging request at 00100104
[... | 1 | void ath_tx_aggr_sleep(struct ieee80211_sta *sta, struct ath_softc *sc,
struct ath_node *an)
{
struct ath_atx_tid *tid;
struct ath_atx_ac *ac;
struct ath_txq *txq;
bool buffered;
int tidno;
for (tidno = 0, tid = &an->tid[tidno];
tidno < IEEE80211_NUM_TIDS; tidno++, tid++) {
if (!tid->sched)
... | 27,558,184,441,602,360,000,000,000,000,000,000,000 | xmit.c | 52,409,064,949,040,600,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2014-2672 | Race condition in the ath_tx_aggr_sleep function in drivers/net/wireless/ath/ath9k/xmit.c in the Linux kernel before 3.13.7 allows remote attackers to cause a denial of service (system crash) via a large amount of network traffic that triggers certain list deletions. | https://nvd.nist.gov/vuln/detail/CVE-2014-2672 |
159,046 | linux | 21f8aaee0c62708654988ce092838aa7df4d25d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/21f8aaee0c62708654988ce092838aa7df4d25d8 | ath9k: protect tid->sched check
We check tid->sched without a lock taken on ath_tx_aggr_sleep(). That
is race condition which can result of doing list_del(&tid->list) twice
(second time with poisoned list node) and cause crash like shown below:
[424271.637220] BUG: unable to handle kernel paging request at 00100104
[... | 0 | void ath_tx_aggr_sleep(struct ieee80211_sta *sta, struct ath_softc *sc,
struct ath_node *an)
{
struct ath_atx_tid *tid;
struct ath_atx_ac *ac;
struct ath_txq *txq;
bool buffered;
int tidno;
for (tidno = 0, tid = &an->tid[tidno];
tidno < IEEE80211_NUM_TIDS; tidno++, tid++) {
ac = tid->ac;
... | 124,058,114,962,541,250,000,000,000,000,000,000,000 | xmit.c | 4,027,104,484,541,684,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2014-2672 | Race condition in the ath_tx_aggr_sleep function in drivers/net/wireless/ath/ath9k/xmit.c in the Linux kernel before 3.13.7 allows remote attackers to cause a denial of service (system crash) via a large amount of network traffic that triggers certain list deletions. | https://nvd.nist.gov/vuln/detail/CVE-2014-2672 |
1,313 | linux | b22f5126a24b3b2f15448c3f2a254fc10cbc2b92 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b22f5126a24b3b2f15448c3f2a254fc10cbc2b92 | netfilter: nf_conntrack_dccp: fix skb_header_pointer API usages
Some occurences in the netfilter tree use skb_header_pointer() in
the following way ...
struct dccp_hdr _dh, *dh;
...
skb_header_pointer(skb, dataoff, sizeof(_dh), &dh);
... where dh itself is a pointer that is being passed as the copy
buffer. Ins... | 1 | static int dccp_error(struct net *net, struct nf_conn *tmpl,
struct sk_buff *skb, unsigned int dataoff,
enum ip_conntrack_info *ctinfo,
u_int8_t pf, unsigned int hooknum)
{
struct dccp_hdr _dh, *dh;
unsigned int dccp_len = skb->len - dataoff;
unsigned int cscov;
const char *msg;
dh = sk... | 324,117,670,837,559,900,000,000,000,000,000,000,000 | nf_conntrack_proto_dccp.c | 173,212,850,459,003,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2523 | net/netfilter/nf_conntrack_proto_dccp.c in the Linux kernel through 3.13.6 uses a DCCP header pointer incorrectly, which allows remote attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a DCCP packet that triggers a call to the (1) dccp_new, (2) dccp_packet, or (3) dccp_error f... | https://nvd.nist.gov/vuln/detail/CVE-2014-2523 |
159,047 | linux | b22f5126a24b3b2f15448c3f2a254fc10cbc2b92 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b22f5126a24b3b2f15448c3f2a254fc10cbc2b92 | netfilter: nf_conntrack_dccp: fix skb_header_pointer API usages
Some occurences in the netfilter tree use skb_header_pointer() in
the following way ...
struct dccp_hdr _dh, *dh;
...
skb_header_pointer(skb, dataoff, sizeof(_dh), &dh);
... where dh itself is a pointer that is being passed as the copy
buffer. Ins... | 0 | static int dccp_error(struct net *net, struct nf_conn *tmpl,
struct sk_buff *skb, unsigned int dataoff,
enum ip_conntrack_info *ctinfo,
u_int8_t pf, unsigned int hooknum)
{
struct dccp_hdr _dh, *dh;
unsigned int dccp_len = skb->len - dataoff;
unsigned int cscov;
const char *msg;
dh = sk... | 162,789,376,161,169,150,000,000,000,000,000,000,000 | nf_conntrack_proto_dccp.c | 265,751,526,435,664,000,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2523 | net/netfilter/nf_conntrack_proto_dccp.c in the Linux kernel through 3.13.6 uses a DCCP header pointer incorrectly, which allows remote attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a DCCP packet that triggers a call to the (1) dccp_new, (2) dccp_packet, or (3) dccp_error f... | https://nvd.nist.gov/vuln/detail/CVE-2014-2523 |
1,314 | linux | b22f5126a24b3b2f15448c3f2a254fc10cbc2b92 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b22f5126a24b3b2f15448c3f2a254fc10cbc2b92 | netfilter: nf_conntrack_dccp: fix skb_header_pointer API usages
Some occurences in the netfilter tree use skb_header_pointer() in
the following way ...
struct dccp_hdr _dh, *dh;
...
skb_header_pointer(skb, dataoff, sizeof(_dh), &dh);
... where dh itself is a pointer that is being passed as the copy
buffer. Ins... | 1 | static bool dccp_new(struct nf_conn *ct, const struct sk_buff *skb,
unsigned int dataoff, unsigned int *timeouts)
{
struct net *net = nf_ct_net(ct);
struct dccp_net *dn;
struct dccp_hdr _dh, *dh;
const char *msg;
u_int8_t state;
dh = skb_header_pointer(skb, dataoff, sizeof(_dh), &dh);
BUG_ON(dh == NU... | 71,271,037,971,402,570,000,000,000,000,000,000,000 | nf_conntrack_proto_dccp.c | 173,212,850,459,003,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2523 | net/netfilter/nf_conntrack_proto_dccp.c in the Linux kernel through 3.13.6 uses a DCCP header pointer incorrectly, which allows remote attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a DCCP packet that triggers a call to the (1) dccp_new, (2) dccp_packet, or (3) dccp_error f... | https://nvd.nist.gov/vuln/detail/CVE-2014-2523 |
159,048 | linux | b22f5126a24b3b2f15448c3f2a254fc10cbc2b92 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b22f5126a24b3b2f15448c3f2a254fc10cbc2b92 | netfilter: nf_conntrack_dccp: fix skb_header_pointer API usages
Some occurences in the netfilter tree use skb_header_pointer() in
the following way ...
struct dccp_hdr _dh, *dh;
...
skb_header_pointer(skb, dataoff, sizeof(_dh), &dh);
... where dh itself is a pointer that is being passed as the copy
buffer. Ins... | 0 | static bool dccp_new(struct nf_conn *ct, const struct sk_buff *skb,
unsigned int dataoff, unsigned int *timeouts)
{
struct net *net = nf_ct_net(ct);
struct dccp_net *dn;
struct dccp_hdr _dh, *dh;
const char *msg;
u_int8_t state;
dh = skb_header_pointer(skb, dataoff, sizeof(_dh), &_dh);
BUG_ON(dh == N... | 261,118,217,964,775,700,000,000,000,000,000,000,000 | nf_conntrack_proto_dccp.c | 265,751,526,435,664,000,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2523 | net/netfilter/nf_conntrack_proto_dccp.c in the Linux kernel through 3.13.6 uses a DCCP header pointer incorrectly, which allows remote attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a DCCP packet that triggers a call to the (1) dccp_new, (2) dccp_packet, or (3) dccp_error f... | https://nvd.nist.gov/vuln/detail/CVE-2014-2523 |
1,315 | linux | b22f5126a24b3b2f15448c3f2a254fc10cbc2b92 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b22f5126a24b3b2f15448c3f2a254fc10cbc2b92 | netfilter: nf_conntrack_dccp: fix skb_header_pointer API usages
Some occurences in the netfilter tree use skb_header_pointer() in
the following way ...
struct dccp_hdr _dh, *dh;
...
skb_header_pointer(skb, dataoff, sizeof(_dh), &dh);
... where dh itself is a pointer that is being passed as the copy
buffer. Ins... | 1 | static int dccp_packet(struct nf_conn *ct, const struct sk_buff *skb,
unsigned int dataoff, enum ip_conntrack_info ctinfo,
u_int8_t pf, unsigned int hooknum,
unsigned int *timeouts)
{
struct net *net = nf_ct_net(ct);
enum ip_conntrack_dir dir = CTINFO2DIR(ctinfo);
struct dccp_hdr _dh, *dh;... | 192,674,082,710,633,720,000,000,000,000,000,000,000 | nf_conntrack_proto_dccp.c | 173,212,850,459,003,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2523 | net/netfilter/nf_conntrack_proto_dccp.c in the Linux kernel through 3.13.6 uses a DCCP header pointer incorrectly, which allows remote attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a DCCP packet that triggers a call to the (1) dccp_new, (2) dccp_packet, or (3) dccp_error f... | https://nvd.nist.gov/vuln/detail/CVE-2014-2523 |
159,049 | linux | b22f5126a24b3b2f15448c3f2a254fc10cbc2b92 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b22f5126a24b3b2f15448c3f2a254fc10cbc2b92 | netfilter: nf_conntrack_dccp: fix skb_header_pointer API usages
Some occurences in the netfilter tree use skb_header_pointer() in
the following way ...
struct dccp_hdr _dh, *dh;
...
skb_header_pointer(skb, dataoff, sizeof(_dh), &dh);
... where dh itself is a pointer that is being passed as the copy
buffer. Ins... | 0 | static int dccp_packet(struct nf_conn *ct, const struct sk_buff *skb,
unsigned int dataoff, enum ip_conntrack_info ctinfo,
u_int8_t pf, unsigned int hooknum,
unsigned int *timeouts)
{
struct net *net = nf_ct_net(ct);
enum ip_conntrack_dir dir = CTINFO2DIR(ctinfo);
struct dccp_hdr _dh, *dh;... | 213,073,327,134,337,870,000,000,000,000,000,000,000 | nf_conntrack_proto_dccp.c | 265,751,526,435,664,000,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2523 | net/netfilter/nf_conntrack_proto_dccp.c in the Linux kernel through 3.13.6 uses a DCCP header pointer incorrectly, which allows remote attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a DCCP packet that triggers a call to the (1) dccp_new, (2) dccp_packet, or (3) dccp_error f... | https://nvd.nist.gov/vuln/detail/CVE-2014-2523 |
1,316 | linux | 263b4509ec4d47e0da3e753f85a39ea12d1eff24 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/263b4509ec4d47e0da3e753f85a39ea12d1eff24 | nfs: always make sure page is up-to-date before extending a write to cover the entire page
We should always make sure the cached page is up-to-date when we're
determining whether we can extend a write to cover the full page -- even
if we've received a write delegation from the server.
Commit c7559663 added logic to s... | 1 | static int nfs_can_extend_write(struct file *file, struct page *page, struct inode *inode)
{
if (file->f_flags & O_DSYNC)
return 0;
if (NFS_PROTO(inode)->have_delegation(inode, FMODE_WRITE))
return 1;
if (nfs_write_pageuptodate(page, inode) && (inode->i_flock == NULL ||
(inode->i_flock->fl_start == 0 &&... | 289,835,272,320,192,980,000,000,000,000,000,000,000 | write.c | 168,110,051,995,489,260,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2038 | The nfs_can_extend_write function in fs/nfs/write.c in the Linux kernel before 3.13.3 relies on a write delegation to extend a write operation without a certain up-to-date verification, which allows local users to obtain sensitive information from kernel memory in opportunistic circumstances by writing to a file in an ... | https://nvd.nist.gov/vuln/detail/CVE-2014-2038 |
159,051 | linux | 263b4509ec4d47e0da3e753f85a39ea12d1eff24 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/263b4509ec4d47e0da3e753f85a39ea12d1eff24 | nfs: always make sure page is up-to-date before extending a write to cover the entire page
We should always make sure the cached page is up-to-date when we're
determining whether we can extend a write to cover the full page -- even
if we've received a write delegation from the server.
Commit c7559663 added logic to s... | 0 | static int nfs_can_extend_write(struct file *file, struct page *page, struct inode *inode)
{
if (file->f_flags & O_DSYNC)
return 0;
if (!nfs_write_pageuptodate(page, inode))
return 0;
if (NFS_PROTO(inode)->have_delegation(inode, FMODE_WRITE))
return 1;
if (inode->i_flock == NULL || (inode->i_flock->fl_s... | 166,033,578,111,799,400,000,000,000,000,000,000,000 | write.c | 327,431,323,848,181,060,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2038 | The nfs_can_extend_write function in fs/nfs/write.c in the Linux kernel before 3.13.3 relies on a write delegation to extend a write operation without a certain up-to-date verification, which allows local users to obtain sensitive information from kernel memory in opportunistic circumstances by writing to a file in an ... | https://nvd.nist.gov/vuln/detail/CVE-2014-2038 |
1,323 | linux | e6a623460e5fc960ac3ee9f946d3106233fd28d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e6a623460e5fc960ac3ee9f946d3106233fd28d8 | [media] media-device: fix infoleak in ioctl media_enum_entities()
This fixes CVE-2014-1739.
Signed-off-by: Salva Peiró <speiro@ai2.upv.es>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: stable@vger.kernel.org
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com> | 1 | static long media_device_enum_entities(struct media_device *mdev,
struct media_entity_desc __user *uent)
{
struct media_entity *ent;
struct media_entity_desc u_ent;
if (copy_from_user(&u_ent.id, &uent->id, sizeof(u_ent.id)))
return -EFAULT;
ent = find_entity(mdev, u_ent.id);
if (ent == NULL)
... | 291,851,125,023,156,100,000,000,000,000,000,000,000 | media-device.c | 35,810,193,786,496,604,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-1739 | The media_device_enum_entities function in drivers/media/media-device.c in the Linux kernel before 3.14.6 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory by leveraging /dev/media0 read access for a MEDIA_IOC_ENUM_ENTITIES ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-1739 |
159,055 | linux | e6a623460e5fc960ac3ee9f946d3106233fd28d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e6a623460e5fc960ac3ee9f946d3106233fd28d8 | [media] media-device: fix infoleak in ioctl media_enum_entities()
This fixes CVE-2014-1739.
Signed-off-by: Salva Peiró <speiro@ai2.upv.es>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: stable@vger.kernel.org
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com> | 0 | static long media_device_enum_entities(struct media_device *mdev,
struct media_entity_desc __user *uent)
{
struct media_entity *ent;
struct media_entity_desc u_ent;
memset(&u_ent, 0, sizeof(u_ent));
if (copy_from_user(&u_ent.id, &uent->id, sizeof(u_ent.id)))
return -EFAULT;
ent = find_entity(m... | 22,729,091,552,887,673,000,000,000,000,000,000,000 | media-device.c | 161,668,849,815,765,700,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-1739 | The media_device_enum_entities function in drivers/media/media-device.c in the Linux kernel before 3.14.6 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory by leveraging /dev/media0 read access for a MEDIA_IOC_ENUM_ENTITIES ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-1739 |
1,325 | linux | 2690d97ade05c5325cbf7c72b94b90d265659886 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2690d97ade05c5325cbf7c72b94b90d265659886 | netfilter: nf_nat: fix access to uninitialized buffer in IRC NAT helper
Commit 5901b6be885e attempted to introduce IPv6 support into
IRC NAT helper. By doing so, the following code seemed to be removed
by accident:
ip = ntohl(exp->master->tuplehash[IP_CT_DIR_REPLY].tuple.dst.u3.ip);
sprintf(buffer, "%u %u", ip, p... | 1 | static unsigned int help(struct sk_buff *skb,
enum ip_conntrack_info ctinfo,
unsigned int protoff,
unsigned int matchoff,
unsigned int matchlen,
struct nf_conntrack_expect *exp)
{
char buffer[sizeof("4294967296 65635")];
u_int16_t port;
unsigned int ret;
/* Reply comes from server. */
... | 59,351,750,141,192,130,000,000,000,000,000,000,000 | nf_nat_irc.c | 209,901,964,006,613,200,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-1690 | The help function in net/netfilter/nf_nat_irc.c in the Linux kernel before 3.12.8 allows remote attackers to obtain sensitive information from kernel memory by establishing an IRC DCC session in which incorrect packet data is transmitted during use of the NAT mangle feature. | https://nvd.nist.gov/vuln/detail/CVE-2014-1690 |
159,056 | linux | 2690d97ade05c5325cbf7c72b94b90d265659886 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2690d97ade05c5325cbf7c72b94b90d265659886 | netfilter: nf_nat: fix access to uninitialized buffer in IRC NAT helper
Commit 5901b6be885e attempted to introduce IPv6 support into
IRC NAT helper. By doing so, the following code seemed to be removed
by accident:
ip = ntohl(exp->master->tuplehash[IP_CT_DIR_REPLY].tuple.dst.u3.ip);
sprintf(buffer, "%u %u", ip, p... | 0 | static unsigned int help(struct sk_buff *skb,
enum ip_conntrack_info ctinfo,
unsigned int protoff,
unsigned int matchoff,
unsigned int matchlen,
struct nf_conntrack_expect *exp)
{
char buffer[sizeof("4294967296 65635")];
struct nf_conn *ct = exp->master;
union nf_inet_addr newaddr;
u_int16_t... | 205,622,336,331,491,650,000,000,000,000,000,000,000 | nf_nat_irc.c | 329,896,800,439,923,450,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-1690 | The help function in net/netfilter/nf_nat_irc.c in the Linux kernel before 3.12.8 allows remote attackers to obtain sensitive information from kernel memory by establishing an IRC DCC session in which incorrect packet data is transmitted during use of the NAT mangle feature. | https://nvd.nist.gov/vuln/detail/CVE-2014-1690 |
1,326 | 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> | 1 | 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;
... | 11,306,301,792,634,982,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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.