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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1,129 | linux | e15ca9a0ef9a86f0477530b0f44a725d67f889ee | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e15ca9a0ef9a86f0477530b0f44a725d67f889ee | Bluetooth: HCI - Fix info leak in getsockopt(HCI_FILTER)
The HCI code fails to initialize the two padding bytes of struct
hci_ufilter before copying it to userland -- that for leaking two
bytes kernel stack. Add an explicit memset(0) before filling the
structure to avoid the info leak.
Signed-off-by: Mathias Krause <... | 1 | static int hci_sock_getsockopt(struct socket *sock, int level, int optname,
char __user *optval, int __user *optlen)
{
struct hci_ufilter uf;
struct sock *sk = sock->sk;
int len, opt, err = 0;
BT_DBG("sk %p, opt %d", sk, optname);
if (get_user(len, optlen))
return -EFAULT;
lock_sock(sk);
if (hci_... | 274,243,474,172,140,940,000,000,000,000,000,000,000 | hci_sock.c | 222,649,962,349,762,240,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2012-6544 | The Bluetooth protocol stack in the Linux kernel before 3.6 does not properly initialize certain structures, which allows local users to obtain sensitive information from kernel stack memory via a crafted application that targets the (1) L2CAP or (2) HCI implementation. | https://nvd.nist.gov/vuln/detail/CVE-2012-6544 |
1,130 | linux | 04d4fbca1017c11381e7d82acea21dd741e748bc | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/04d4fbca1017c11381e7d82acea21dd741e748bc | l2tp: fix info leak via getsockname()
The L2TP code for IPv6 fails to initialize the l2tp_unused member of
struct sockaddr_l2tpip6 and that for leaks two bytes kernel stack via
the getsockname() syscall. Initialize l2tp_unused with 0 to avoid the
info leak.
Signed-off-by: Mathias Krause <minipli@googlemail.com>
Cc: J... | 1 | static int l2tp_ip6_getname(struct socket *sock, struct sockaddr *uaddr,
int *uaddr_len, int peer)
{
struct sockaddr_l2tpip6 *lsa = (struct sockaddr_l2tpip6 *)uaddr;
struct sock *sk = sock->sk;
struct ipv6_pinfo *np = inet6_sk(sk);
struct l2tp_ip6_sock *lsk = l2tp_ip6_sk(sk);
lsa->l2tp_family = AF_INET6;
... | 85,210,193,838,679,960,000,000,000,000,000,000,000 | l2tp_ip6.c | 37,086,785,037,095,373,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2012-6543 | The l2tp_ip6_getname function in net/l2tp/l2tp_ip6.c in the Linux kernel before 3.6 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2012-6543 |
1,131 | linux | 3592aaeb80290bda0f2cf0b5456c97bfc638b192 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/3592aaeb80290bda0f2cf0b5456c97bfc638b192 | llc: fix info leak via getsockname()
The LLC code wrongly returns 0, i.e. "success", when the socket is
zapped. Together with the uninitialized uaddrlen pointer argument from
sys_getsockname this leads to an arbitrary memory leak of up to 128
bytes kernel stack via the getsockname() syscall.
Return an error instead w... | 1 | static int llc_ui_getname(struct socket *sock, struct sockaddr *uaddr,
int *uaddrlen, int peer)
{
struct sockaddr_llc sllc;
struct sock *sk = sock->sk;
struct llc_sock *llc = llc_sk(sk);
int rc = 0;
memset(&sllc, 0, sizeof(sllc));
lock_sock(sk);
if (sock_flag(sk, SOCK_ZAPPED))
goto out;
*uaddrl... | 39,906,440,321,854,090,000,000,000,000,000,000,000 | af_llc.c | 121,753,272,392,455,930,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2012-6542 | The llc_ui_getname function in net/llc/af_llc.c in the Linux kernel before 3.6 has an incorrect return value in certain circumstances, which allows local users to obtain sensitive information from kernel stack memory via a crafted application that leverages an uninitialized pointer argument. | https://nvd.nist.gov/vuln/detail/CVE-2012-6542 |
1,132 | linux | 7b07f8eb75aa3097cdfd4f6eac3da49db787381d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7b07f8eb75aa3097cdfd4f6eac3da49db787381d | dccp: fix info leak via getsockopt(DCCP_SOCKOPT_CCID_TX_INFO)
The CCID3 code fails to initialize the trailing padding bytes of struct
tfrc_tx_info added for alignment on 64 bit architectures. It that for
potentially leaks four bytes kernel stack via the getsockopt() syscall.
Add an explicit memset(0) before filling th... | 1 | static int ccid3_hc_tx_getsockopt(struct sock *sk, const int optname, int len,
u32 __user *optval, int __user *optlen)
{
const struct ccid3_hc_tx_sock *hc = ccid3_hc_tx_sk(sk);
struct tfrc_tx_info tfrc;
const void *val;
switch (optname) {
case DCCP_SOCKOPT_CCID_TX_INFO:
if (len < sizeof(tfrc))
retur... | 8,536,137,024,975,475,000,000,000,000,000,000,000 | ccid3.c | 160,351,560,622,096,350,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2012-6541 | The ccid3_hc_tx_getsockopt function in net/dccp/ccids/ccid3.c in the Linux kernel before 3.6 does not initialize a certain structure, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2012-6541 |
1,133 | linux | 2d8a041b7bfe1097af21441cb77d6af95f4f4680 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2d8a041b7bfe1097af21441cb77d6af95f4f4680 | ipvs: fix info leak in getsockopt(IP_VS_SO_GET_TIMEOUT)
If at least one of CONFIG_IP_VS_PROTO_TCP or CONFIG_IP_VS_PROTO_UDP is
not set, __ip_vs_get_timeouts() does not fully initialize the structure
that gets copied to userland and that for leaks up to 12 bytes of kernel
stack. Add an explicit memset(0) before passing... | 1 | do_ip_vs_get_ctl(struct sock *sk, int cmd, void __user *user, int *len)
{
unsigned char arg[128];
int ret = 0;
unsigned int copylen;
struct net *net = sock_net(sk);
struct netns_ipvs *ipvs = net_ipvs(net);
BUG_ON(!net);
if (!capable(CAP_NET_ADMIN))
return -EPERM;
if (cmd < IP_VS_BASE_CTL || cmd > IP_VS_SO_G... | 267,941,661,112,975,060,000,000,000,000,000,000,000 | ip_vs_ctl.c | 289,258,931,771,187,420,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2012-6540 | The do_ip_vs_get_ctl function in net/netfilter/ipvs/ip_vs_ctl.c in the Linux kernel before 3.6 does not initialize a certain structure for IP_VS_SO_GET_TIMEOUT commands, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2012-6540 |
1,134 | linux | f778a636713a435d3a922c60b1622a91136560c1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f778a636713a435d3a922c60b1622a91136560c1 | xfrm_user: fix info leak in copy_to_user_state()
The memory reserved to dump the xfrm state includes the padding bytes of
struct xfrm_usersa_info added by the compiler for alignment (7 for
amd64, 3 for i386). Add an explicit memset(0) before filling the buffer
to avoid the info leak.
Signed-off-by: Mathias Krause <mi... | 1 | static void copy_to_user_state(struct xfrm_state *x, struct xfrm_usersa_info *p)
{
memcpy(&p->id, &x->id, sizeof(p->id));
memcpy(&p->sel, &x->sel, sizeof(p->sel));
memcpy(&p->lft, &x->lft, sizeof(p->lft));
memcpy(&p->curlft, &x->curlft, sizeof(p->curlft));
memcpy(&p->stats, &x->stats, sizeof(p->stats));
memc... | 144,112,786,017,541,910,000,000,000,000,000,000,000 | xfrm_user.c | 38,362,585,315,635,697,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2012-6537 | net/xfrm/xfrm_user.c in the Linux kernel before 3.6 does not initialize certain structures, which allows local users to obtain sensitive information from kernel memory by leveraging the CAP_NET_ADMIN capability. | https://nvd.nist.gov/vuln/detail/CVE-2012-6537 |
1,142 | linux | b66c5984017533316fd1951770302649baf1aa33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b66c5984017533316fd1951770302649baf1aa33 | exec: do not leave bprm->interp on stack
If a series of scripts are executed, each triggering module loading via
unprintable bytes in the script header, kernel stack contents can leak
into the command line.
Normally execution of binfmt_script and binfmt_misc happens recursively.
However, when modules are enabled, and... | 1 | static int load_script(struct linux_binprm *bprm)
{
const char *i_arg, *i_name;
char *cp;
struct file *file;
char interp[BINPRM_BUF_SIZE];
int retval;
if ((bprm->buf[0] != '#') || (bprm->buf[1] != '!'))
return -ENOEXEC;
/*
* This section does the #! interpretation.
* Sorta complicated, but hopefully it wi... | 328,383,916,190,717,060,000,000,000,000,000,000,000 | None | null | [
"CWE-200"
] | CVE-2012-4530 | The load_script function in fs/binfmt_script.c in the Linux kernel before 3.7.2 does not properly handle recursion, which allows local users to obtain sensitive information from kernel stack memory via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2012-4530 |
1,150 | krb5 | db64ca25d661a47b996b4e2645998b5d7f0eb52c | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/db64ca25d661a47b996b4e2645998b5d7f0eb52c | PKINIT (draft9) null ptr deref [CVE-2012-1016]
Don't check for an agility KDF identifier in the non-draft9 reply
structure when we're building a draft9 reply, because it'll be NULL.
The KDC plugin for PKINIT can dereference a null pointer when handling
a draft9 request, leading to a crash of the KDC process. An atta... | 1 | pkinit_server_return_padata(krb5_context context,
krb5_pa_data * padata,
krb5_data *req_pkt,
krb5_kdc_req * request,
krb5_kdc_rep * reply,
krb5_keyblock * encrypting_key,
... | 76,503,992,088,312,030,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2012-1016 | The pkinit_server_return_padata function in plugins/preauth/pkinit/pkinit_srv.c in the PKINIT implementation in the Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.10.4 attempts to find an agility KDF identifier in inappropriate circumstances, which allows remote attackers to cause a denial of servi... | https://nvd.nist.gov/vuln/detail/CVE-2012-1016 |
1,151 | linux | b5a1eeef04cc7859f34dec9b72ea1b28e4aba07c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b5a1eeef04cc7859f34dec9b72ea1b28e4aba07c | batman-adv: Only write requested number of byte to user buffer
Don't write more than the requested number of bytes of an batman-adv icmp
packet to the userspace buffer. Otherwise unrelated userspace memory might get
overridden by the kernel.
Signed-off-by: Sven Eckelmann <sven@narfation.org>
Signed-off-by: Marek Lind... | 1 | static ssize_t bat_socket_read(struct file *file, char __user *buf,
size_t count, loff_t *ppos)
{
struct socket_client *socket_client = file->private_data;
struct socket_packet *socket_packet;
size_t packet_len;
int error;
if ((file->f_flags & O_NONBLOCK) && (socket_client->queue_len == 0))
return -EA... | 85,869,577,016,758,350,000,000,000,000,000,000,000 | icmp_socket.c | 220,335,110,825,043,840,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4604 | The bat_socket_read function in net/batman-adv/icmp_socket.c in the Linux kernel before 3.3 allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via a crafted batman-adv ICMP packet. | https://nvd.nist.gov/vuln/detail/CVE-2011-4604 |
1,152 | linux | ae53b5bd77719fed58086c5be60ce4f22bffe1c6 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ae53b5bd77719fed58086c5be60ce4f22bffe1c6 | sctp: Fix another socket race during accept/peeloff
There is a race between sctp_rcv() and sctp_accept() where we
have moved the association from the listening socket to the
accepted socket, but sctp_rcv() processing cached the old
socket and continues to use it.
The easy solution is to check for the socket mismatch ... | 1 | int sctp_rcv(struct sk_buff *skb)
{
struct sock *sk;
struct sctp_association *asoc;
struct sctp_endpoint *ep = NULL;
struct sctp_ep_common *rcvr;
struct sctp_transport *transport = NULL;
struct sctp_chunk *chunk;
struct sctphdr *sh;
union sctp_addr src;
union sctp_addr dest;
int family;
struct sctp_af *af;
... | 173,020,335,186,799,700,000,000,000,000,000,000,000 | input.c | 44,064,972,847,145,270,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2011-4348 | Race condition in the sctp_rcv function in net/sctp/input.c in the Linux kernel before 2.6.29 allows remote attackers to cause a denial of service (system hang) via SCTP packets. NOTE: in some environments, this issue exists because of an incomplete fix for CVE-2011-2482. | https://nvd.nist.gov/vuln/detail/CVE-2011-4348 |
1,153 | linux | c4e7f9022e506c6635a5037713c37118e23193e4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c4e7f9022e506c6635a5037713c37118e23193e4 | None | 1 | static int kvm_vm_ioctl_assign_device(struct kvm *kvm,
struct kvm_assigned_pci_dev *assigned_dev)
{
int r = 0, idx;
struct kvm_assigned_dev_kernel *match;
struct pci_dev *dev;
if (!(assigned_dev->flags & KVM_DEV_ASSIGN_ENABLE_IOMMU))
return -EINVAL;
mutex_lock(&kvm->lock);
idx = srcu_read_l... | 272,600,557,570,379,850,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2011-4347 | The kvm_vm_ioctl_assign_device function in virt/kvm/assigned-dev.c in the KVM subsystem in the Linux kernel before 3.1.10 does not verify permission to access PCI configuration space and BAR resources, which allows host OS users to assign PCI devices and cause a denial of service (host OS crash) via a KVM_ASSIGN_PCI_DE... | https://nvd.nist.gov/vuln/detail/CVE-2011-4347 |
1,160 | linux | f8e9881c2aef1e982e5abc25c046820cd0b7cf64 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f8e9881c2aef1e982e5abc25c046820cd0b7cf64 | bridge: reset IPCB in br_parse_ip_options
Commit 462fb2af9788a82 (bridge : Sanitize skb before it enters the IP
stack), missed one IPCB init before calling ip_options_compile()
Thanks to Scot Doyle for his tests and bug reports.
Reported-by: Scot Doyle <lkml@scotdoyle.com>
Signed-off-by: Eric Dumazet <eric.dumazet@g... | 1 | static int br_parse_ip_options(struct sk_buff *skb)
{
struct ip_options *opt;
struct iphdr *iph;
struct net_device *dev = skb->dev;
u32 len;
iph = ip_hdr(skb);
opt = &(IPCB(skb)->opt);
/* Basic sanity checks */
if (iph->ihl < 5 || iph->version != 4)
goto inhdr_error;
if (!pskb_may_pull(skb, iph->ihl*4))
... | 126,955,592,485,195,450,000,000,000,000,000,000,000 | br_netfilter.c | 318,634,080,555,349,820,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2011-4087 | The br_parse_ip_options function in net/bridge/br_netfilter.c in the Linux kernel before 2.6.39 does not properly initialize a certain data structure, which allows remote attackers to cause a denial of service by leveraging connectivity to a network interface that uses an Ethernet bridge device. | https://nvd.nist.gov/vuln/detail/CVE-2011-4087 |
1,163 | linux | a5b2c5b2ad5853591a6cac6134cd0f599a720865 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a5b2c5b2ad5853591a6cac6134cd0f599a720865 | AppArmor: fix oops in apparmor_setprocattr
When invalid parameters are passed to apparmor_setprocattr a NULL deref
oops occurs when it tries to record an audit message. This is because
it is passing NULL for the profile parameter for aa_audit. But aa_audit
now requires that the profile passed is not NULL.
Fix this by... | 1 | static int apparmor_setprocattr(struct task_struct *task, char *name,
void *value, size_t size)
{
char *command, *args = value;
size_t arg_size;
int error;
if (size == 0)
return -EINVAL;
/* args points to a PAGE_SIZE buffer, AppArmor requires that
* the buffer must be null terminated or have size <= PAGE_... | 198,478,101,125,261,500,000,000,000,000,000,000,000 | lsm.c | 86,780,604,940,296,660,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3619 | The apparmor_setprocattr function in security/apparmor/lsm.c in the Linux kernel before 3.0 does not properly handle invalid parameters, which allows local users to cause a denial of service (NULL pointer dereference and OOPS) or possibly have unspecified other impact by writing to a /proc/#####/attr/current file. | https://nvd.nist.gov/vuln/detail/CVE-2011-3619 |
1,164 | linux | aba8d056078e47350d85b06a9cabd5afcc4b72ea | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/aba8d056078e47350d85b06a9cabd5afcc4b72ea | perf tools: do not look at ./config for configuration
In addition to /etc/perfconfig and $HOME/.perfconfig, perf looks for
configuration in the file ./config, imitating git which looks at
$GIT_DIR/config. If ./config is not a perf configuration file, it
fails, or worse, treats it as a configuration file and changes b... | 1 | int perf_config(config_fn_t fn, void *data)
{
int ret = 0, found = 0;
char *repo_config = NULL;
const char *home = NULL;
/* Setting $PERF_CONFIG makes perf read _only_ the given config file. */
if (config_exclusive_filename)
return perf_config_from_file(fn, config_exclusive_filename, data);
if (perf_conf... | 291,567,066,678,415,750,000,000,000,000,000,000,000 | config.c | 300,265,789,152,003,100,000,000,000,000,000,000,000 | [
"CWE-94"
] | CVE-2011-2905 | Untrusted search path vulnerability in the perf_config function in tools/perf/util/config.c in perf, as distributed in the Linux kernel before 3.1, allows local users to overwrite arbitrary files via a crafted config file in the current working directory. | https://nvd.nist.gov/vuln/detail/CVE-2011-2905 |
1,167 | 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 ... | 1 | 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... | 245,295,386,150,735,570,000,000,000,000,000,000,000 | socket.c | 237,855,478,219,647,640,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,172 | linux | 4ff67b720c02c36e54d55b88c2931879b7db1cd2 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4ff67b720c02c36e54d55b88c2931879b7db1cd2 | cifs: clean up cifs_find_smb_ses (try #2)
This patch replaces the earlier patch by the same name. The only
difference is that MAX_PASSWORD_SIZE has been increased to attempt to
match the limits that windows enforces.
Do a better job of matching sessions by authtype. Matching by username
for a Kerberos session is inco... | 1 | cifs_find_smb_ses(struct TCP_Server_Info *server, char *username)
{
struct list_head *tmp;
struct cifsSesInfo *ses;
write_lock(&cifs_tcp_ses_lock);
list_for_each(tmp, &server->smb_ses_list) {
ses = list_entry(tmp, struct cifsSesInfo, smb_ses_list);
if (strncmp(ses->userName, username, MAX_USERNAME_SIZE))
... | 174,415,870,851,944,500,000,000,000,000,000,000,000 | connect.c | 326,028,216,122,812,540,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-1585 | The cifs_find_smb_ses function in fs/cifs/connect.c in the Linux kernel before 2.6.36 does not properly determine the associations between users and sessions, which allows local users to bypass CIFS share authentication by leveraging a mount of a share by a different user. | https://nvd.nist.gov/vuln/detail/CVE-2011-1585 |
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 |
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 |
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 |
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 |
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 |
1,183 | tcpdump | 0f95d441e4b5d7512cc5c326c8668a120e048eda | https://github.com/the-tcpdump-group/tcpdump | https://github.com/the-tcpdump-group/tcpdump/commit/0f95d441e4b5d7512cc5c326c8668a120e048eda | Do bounds checking when unescaping PPP.
Clean up a const issue while we're at it. | 1 | ppp_hdlc(netdissect_options *ndo,
const u_char *p, int length)
{
u_char *b, *s, *t, c;
int i, proto;
const void *se;
if (length <= 0)
return;
b = (uint8_t *)malloc(length);
if (b == NULL)
return;
/*
* Unescape all the data into a temporary, private, buffer.
*... | 163,830,884,355,634,390,000,000,000,000,000,000,000 | print-ppp.c | 89,533,130,049,478,180,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-9140 | Buffer overflow in the ppp_hdlc function in print-ppp.c in tcpdump 4.6.2 and earlier allows remote attackers to cause a denial of service (crash) cia a crafted PPP packet. | https://nvd.nist.gov/vuln/detail/CVE-2014-9140 |
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 |
1,185 | linux | 338f977f4eb441e69bb9a46eaa0ac715c931a67f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/338f977f4eb441e69bb9a46eaa0ac715c931a67f | mac80211: fix fragmentation code, particularly for encryption
The "new" fragmentation code (since my rewrite almost 5 years ago)
erroneously sets skb->len rather than using skb_trim() to adjust
the length of the first fragment after copying out all the others.
This leaves the skb tail pointer pointing to after where t... | 1 | static int ieee80211_fragment(struct ieee80211_tx_data *tx,
struct sk_buff *skb, int hdrlen,
int frag_threshold)
{
struct ieee80211_local *local = tx->local;
struct ieee80211_tx_info *info;
struct sk_buff *tmp;
int per_fragm = frag_threshold - hdrlen - FCS_LEN;
int pos = hdrlen + per_fragm;
int ... | 252,627,261,483,521,550,000,000,000,000,000,000,000 | tx.c | 187,323,276,197,443,400,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-8709 | The ieee80211_fragment function in net/mac80211/tx.c in the Linux kernel before 3.13.5 does not properly maintain a certain tail pointer, which allows remote attackers to obtain sensitive cleartext information by reading packets. | https://nvd.nist.gov/vuln/detail/CVE-2014-8709 |
1,186 | linux | a430c9166312e1aa3d80bce32374233bdbfeba32 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a430c9166312e1aa3d80bce32374233bdbfeba32 | KVM: emulate: avoid accessing NULL ctxt->memopp
A failure to decode the instruction can cause a NULL pointer access.
This is fixed simply by moving the "done" label as close as possible
to the return.
This fixes CVE-2014-8481.
Reported-by: Andy Lutomirski <luto@amacapital.net>
Cc: stable@vger.kernel.org
Fixes: 41061... | 1 | int x86_decode_insn(struct x86_emulate_ctxt *ctxt, void *insn, int insn_len)
{
int rc = X86EMUL_CONTINUE;
int mode = ctxt->mode;
int def_op_bytes, def_ad_bytes, goffset, simd_prefix;
bool op_prefix = false;
bool has_seg_override = false;
struct opcode opcode;
ctxt->memop.type = OP_NONE;
ctxt->memopp = NULL;
c... | 201,743,535,793,806,920,000,000,000,000,000,000,000 | emulate.c | 284,934,346,528,550,170,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-8481 | The instruction decoder in arch/x86/kvm/emulate.c in the KVM subsystem in the Linux kernel before 3.18-rc2 does not properly handle invalid instructions, which allows guest OS users to cause a denial of service (NULL pointer dereference and host OS crash) via a crafted application that triggers (1) an improperly fetche... | https://nvd.nist.gov/vuln/detail/CVE-2014-8481 |
1,187 | linux | 3d32e4dbe71374a6780eaf51d719d76f9a9bf22f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/3d32e4dbe71374a6780eaf51d719d76f9a9bf22f | kvm: fix excessive pages un-pinning in kvm_iommu_map error path.
The third parameter of kvm_unpin_pages() when called from
kvm_iommu_map_pages() is wrong, it should be the number of pages to un-pin
and not the page size.
This error was facilitated with an inconsistent API: kvm_pin_pages() takes
a size, but kvn_unpin_... | 1 | int kvm_iommu_map_pages(struct kvm *kvm, struct kvm_memory_slot *slot)
{
gfn_t gfn, end_gfn;
pfn_t pfn;
int r = 0;
struct iommu_domain *domain = kvm->arch.iommu_domain;
int flags;
/* check if iommu exists and in use */
if (!domain)
return 0;
gfn = slot->base_gfn;
end_gfn = gfn + slot->npages;
flags =... | 40,650,788,508,994,537,000,000,000,000,000,000,000 | iommu.c | 293,495,940,641,321,050,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-8369 | The kvm_iommu_map_pages function in virt/kvm/iommu.c in the Linux kernel through 3.17.2 miscalculates the number of pages during the handling of a mapping failure, which allows guest OS users to cause a denial of service (host OS page unpinning) or possibly have unspecified other impact by leveraging guest OS privilege... | https://nvd.nist.gov/vuln/detail/CVE-2014-8369 |
1,191 | linux | a2b9e6c1a35afcc0973acb72e591c714e78885ff | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a2b9e6c1a35afcc0973acb72e591c714e78885ff | KVM: x86: Don't report guest userspace emulation error to userspace
Commit fc3a9157d314 ("KVM: X86: Don't report L2 emulation failures to
user-space") disabled the reporting of L2 (nested guest) emulation failures to
userspace due to race-condition between a vmexit and the instruction emulator.
The same rational appli... | 1 | static int handle_emulation_failure(struct kvm_vcpu *vcpu)
{
int r = EMULATE_DONE;
++vcpu->stat.insn_emulation_fail;
trace_kvm_emulate_insn_failed(vcpu);
if (!is_guest_mode(vcpu)) {
vcpu->run->exit_reason = KVM_EXIT_INTERNAL_ERROR;
vcpu->run->internal.suberror = KVM_INTERNAL_ERROR_EMULATION;
vcpu->run-... | 44,326,647,696,150,180,000,000,000,000,000,000,000 | x86.c | 92,946,483,395,699,820,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2014-7842 | Race condition in arch/x86/kvm/x86.c in the Linux kernel before 3.17.4 allows guest OS users to cause a denial of service (guest OS crash) via a crafted application that performs an MMIO transaction or a PIO transaction to trigger a guest userspace emulation error report, a similar issue to CVE-2010-5313. | https://nvd.nist.gov/vuln/detail/CVE-2014-7842 |
1,192 | linux | e40607cbe270a9e8360907cb1e62ddf0736e4864 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e40607cbe270a9e8360907cb1e62ddf0736e4864 | net: sctp: fix NULL pointer dereference in af->from_addr_param on malformed packet
An SCTP server doing ASCONF will panic on malformed INIT ping-of-death
in the form of:
------------ INIT[PARAM: SET_PRIMARY_IP] ------------>
While the INIT chunk parameter verification dissects through many things
in order to detec... | 1 | static int sctp_process_param(struct sctp_association *asoc,
union sctp_params param,
const union sctp_addr *peer_addr,
gfp_t gfp)
{
struct net *net = sock_net(asoc->base.sk);
union sctp_addr addr;
int i;
__u16 sat;
int retval = 1;
sctp_scope_t scope;
time_t stale;
struct sctp_af *af;... | 233,310,274,121,482,150,000,000,000,000,000,000,000 | sm_make_chunk.c | 336,027,494,887,991,000,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-7841 | The sctp_process_param function in net/sctp/sm_make_chunk.c in the SCTP implementation in the Linux kernel before 3.17.4, when ASCONF is used, allows remote attackers to cause a denial of service (NULL pointer dereference and system crash) via a malformed INIT chunk. | https://nvd.nist.gov/vuln/detail/CVE-2014-7841 |
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 |
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 |
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 |
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 |
1,209 | linux | 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 | isofs: Fix unbounded recursion when processing relocated directories
We did not check relocated directory in any way when processing Rock
Ridge 'CL' tag. Thus a corrupted isofs image can possibly have a CL
entry pointing to another CL entry leading to possibly unbounded
recursion in kernel code and thus stack overflow... | 1 | parse_rock_ridge_inode_internal(struct iso_directory_record *de,
struct inode *inode, int regard_xa)
{
int symlink_len = 0;
int cnt, sig;
struct inode *reloc;
struct rock_ridge *rr;
int rootflag;
struct rock_state rs;
int ret = 0;
if (!ISOFS_SB(inode->i_sb)->s_rock)
return 0;
init_rock_state(&... | 46,643,672,205,519,710,000,000,000,000,000,000,000 | rock.c | 131,672,781,682,898,080,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-5472 | The parse_rock_ridge_inode_internal function in fs/isofs/rock.c in the Linux kernel through 3.16.1 allows local users to cause a denial of service (unkillable mount process) via a crafted iso9660 image with a self-referential CL entry. | https://nvd.nist.gov/vuln/detail/CVE-2014-5472 |
1,211 | krb5 | af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/af0ed4df4dfae762ab5fb605f5a0c8f59cb4f6ca | Return only new keys in randkey [CVE-2014-5351]
In kadmind's randkey operation, if a client specifies the keepold
flag, do not include the preserved old keys in the response.
CVE-2014-5351:
An authenticated remote attacker can retrieve the current keys for a
service principal when generating a new set of keys for th... | 1 | kadm5_randkey_principal_3(void *server_handle,
krb5_principal principal,
krb5_boolean keepold,
int n_ks_tuple, krb5_key_salt_tuple *ks_tuple,
krb5_keyblock **keyblocks,
int *n_keys)
{
kr... | 147,608,648,129,973,760,000,000,000,000,000,000,000 | svr_principal.c | 212,802,498,518,670,500,000,000,000,000,000,000,000 | [
"CWE-255"
] | CVE-2014-5351 | The kadm5_randkey_principal_3 function in lib/kadm5/srv/svr_principal.c in kadmind in MIT Kerberos 5 (aka krb5) before 1.13 sends old keys in a response to a -randkey -keepold request, which allows remote authenticated users to forge tickets by leveraging administrative access. | https://nvd.nist.gov/vuln/detail/CVE-2014-5351 |
1,217 | linux | 9566d6742852c527bf5af38af5cbb878dad75705 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9566d6742852c527bf5af38af5cbb878dad75705 | mnt: Correct permission checks in do_remount
While invesgiating the issue where in "mount --bind -oremount,ro ..."
would result in later "mount --bind -oremount,rw" succeeding even if
the mount started off locked I realized that there are several
additional mount flags that should be locked and are not.
In particular... | 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;
/* Don't allow changing of l... | 67,643,344,520,913,290,000,000,000,000,000,000,000 | namespace.c | 248,678,835,224,379,800,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-5207 | fs/namespace.c in the Linux kernel through 3.16.1 does not properly restrict clearing MNT_NODEV, MNT_NOSUID, and MNT_NOEXEC and changing MNT_ATIME_MASK during a remount of a bind mount, which allows local users to gain privileges, interfere with backups and auditing on systems that had atime enabled, or cause a denial ... | https://nvd.nist.gov/vuln/detail/CVE-2014-5207 |
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 |
1,219 | linux | 1be9a950c646c9092fb3618197f7b6bfb50e82aa | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1be9a950c646c9092fb3618197f7b6bfb50e82aa | net: sctp: inherit auth_capable on INIT collisions
Jason reported an oops caused by SCTP on his ARM machine with
SCTP authentication enabled:
Internal error: Oops: 17 [#1] ARM
CPU: 0 PID: 104 Comm: sctp-test Not tainted 3.13.0-68744-g3632f30c9b20-dirty #1
task: c6eefa40 ti: c6f52000 task.ti: c6f52000
PC is at sctp_au... | 1 | void sctp_assoc_update(struct sctp_association *asoc,
struct sctp_association *new)
{
struct sctp_transport *trans;
struct list_head *pos, *temp;
/* Copy in new parameters of peer. */
asoc->c = new->c;
asoc->peer.rwnd = new->peer.rwnd;
asoc->peer.sack_needed = new->peer.sack_needed;
asoc->peer.i = ... | 268,873,015,146,939,470,000,000,000,000,000,000,000 | associola.c | 290,607,751,015,410,100,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2014-5077 | The sctp_assoc_update function in net/sctp/associola.c in the Linux kernel through 3.15.8, when SCTP authentication is enabled, allows remote attackers to cause a denial of service (NULL pointer dereference and OOPS) by starting to establish an association between two endpoints immediately after an exchange of INIT and... | https://nvd.nist.gov/vuln/detail/CVE-2014-5077 |
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 |
1,223 | linux | d3217b15a19a4779c39b212358a5c71d725822ee | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d3217b15a19a4779c39b212358a5c71d725822ee | sctp: Fix sk_ack_backlog wrap-around problem
Consider the scenario:
For a TCP-style socket, while processing the COOKIE_ECHO chunk in
sctp_sf_do_5_1D_ce(), after it has passed a series of sanity check,
a new association would be created in sctp_unpack_cookie(), but afterwards,
some processing maybe failed, and sctp_as... | 1 | void sctp_association_free(struct sctp_association *asoc)
{
struct sock *sk = asoc->base.sk;
struct sctp_transport *transport;
struct list_head *pos, *temp;
int i;
/* Only real associations count against the endpoint, so
* don't bother for if this is a temporary association.
*/
if (!asoc->temp) {
list_... | 307,155,962,389,758,070,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2014-4667 | The sctp_association_free function in net/sctp/associola.c in the Linux kernel before 3.15.2 does not properly manage a certain backlog value, which allows remote attackers to cause a denial of service (socket outage) via a crafted SCTP packet. | https://nvd.nist.gov/vuln/detail/CVE-2014-4667 |
1,224 | linux | ac902c112d90a89e59916f751c2745f4dbdbb4bd | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac902c112d90a89e59916f751c2745f4dbdbb4bd | ALSA: control: Handle numid overflow
Each control gets automatically assigned its numids when the control is created.
The allocation is done by incrementing the numid by the amount of allocated
numids per allocation. This means that excessive creation and destruction of
controls (e.g. via SNDRV_CTL_IOCTL_ELEM_ADD/REMO... | 1 | static bool snd_ctl_remove_numid_conflict(struct snd_card *card,
unsigned int count)
{
struct snd_kcontrol *kctl;
list_for_each_entry(kctl, &card->controls, list) {
if (kctl->id.numid < card->last_numid + 1 + count &&
kctl->id.numid + kctl->count > card->last_numid + 1) {
card->last_numid... | 82,969,020,191,262,430,000,000,000,000,000,000,000 | control.c | 65,123,648,022,085,850,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4656 | Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflic... | https://nvd.nist.gov/vuln/detail/CVE-2014-4656 |
1,225 | linux | 82262a46627bebb0febcc26664746c25cef08563 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/82262a46627bebb0febcc26664746c25cef08563 | ALSA: control: Fix replacing user controls
There are two issues with the current implementation for replacing user
controls. The first is that the code does not check if the control is actually a
user control and neither does it check if the control is owned by the process
that tries to remove it. That allows userspac... | 1 | static int snd_ctl_elem_add(struct snd_ctl_file *file,
struct snd_ctl_elem_info *info, int replace)
{
struct snd_card *card = file->card;
struct snd_kcontrol kctl, *_kctl;
unsigned int access;
long private_size;
struct user_element *ue;
int idx, err;
if (!replace && card->user_ctl_count >= MAX_USER_CO... | 104,448,511,318,866,040,000,000,000,000,000,000,000 | control.c | 234,091,425,417,038,060,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-4654 | The snd_ctl_elem_add function in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 does not check authorization for SNDRV_CTL_IOCTL_ELEM_REPLACE commands, which allows local users to remove kernel controls and cause a denial of service (use-after-free and system crash) by leverag... | https://nvd.nist.gov/vuln/detail/CVE-2014-4654 |
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 |
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 |
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 |
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 |
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 |
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 |
1,239 | krb5 | a7886f0ed1277c69142b14a2c6629175a6331edc | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/a7886f0ed1277c69142b14a2c6629175a6331edc | Fix null deref in SPNEGO acceptor [CVE-2014-4344]
When processing a continuation token, acc_ctx_cont was dereferencing
the initial byte of the token without checking the length. This could
result in a null dereference.
CVE-2014-4344:
In MIT krb5 1.5 and newer, an unauthenticated or partially
authenticated remote at... | 1 | acc_ctx_cont(OM_uint32 *minstat,
gss_buffer_t buf,
gss_ctx_id_t *ctx,
gss_buffer_t *responseToken,
gss_buffer_t *mechListMIC,
OM_uint32 *negState,
send_token_flag *return_token)
{
OM_uint32 ret, tmpmin;
gss_OID supportedMech;
spnego_gss_ctx_id_t sc;
unsigned int len;
unsigned ch... | 111,177,546,391,845,930,000,000,000,000,000,000,000 | spnego_mech.c | 290,065,421,106,050,240,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2014-4344 | The acc_ctx_cont function in the SPNEGO acceptor in lib/gssapi/spnego/spnego_mech.c in MIT Kerberos 5 (aka krb5) 1.5.x through 1.12.x before 1.12.2 allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via an empty continuation token at a certain point during a SPNEGO neg... | https://nvd.nist.gov/vuln/detail/CVE-2014-4344 |
1,240 | krb5 | f18ddf5d82de0ab7591a36e465bc24225776940f | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/f18ddf5d82de0ab7591a36e465bc24225776940f | Fix double-free in SPNEGO [CVE-2014-4343]
In commit cd7d6b08 ("Verify acceptor's mech in SPNEGO initiator") the
pointer sc->internal_mech became an alias into sc->mech_set->elements,
which should be considered constant for the duration of the SPNEGO
context. So don't free it.
CVE-2014-4343:
In MIT krb5 releases 1.1... | 1 | init_ctx_reselect(OM_uint32 *minor_status, spnego_gss_ctx_id_t sc,
OM_uint32 acc_negState, gss_OID supportedMech,
gss_buffer_t *responseToken, gss_buffer_t *mechListMIC,
OM_uint32 *negState, send_token_flag *tokflag)
{
OM_uint32 tmpmin;
size_t i;
generic_gss_release_oid(&tmpmin, &sc->internal_mech);
... | 116,847,216,199,976,580,000,000,000,000,000,000,000 | spnego_mech.c | 145,186,693,848,278,750,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2014-4343 | Double free vulnerability in the init_ctx_reselect function in the SPNEGO initiator in lib/gssapi/spnego/spnego_mech.c in MIT Kerberos 5 (aka krb5) 1.10.x through 1.12.x before 1.12.2 allows remote attackers to cause a denial of service (memory corruption) or possibly execute arbitrary code via network traffic that app... | https://nvd.nist.gov/vuln/detail/CVE-2014-4343 |
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 |
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 |
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 |
1,254 | file | 39c7ac1106be844a5296d3eb5971946cc09ffda0 | https://github.com/file/file | https://github.com/file/file/commit/39c7ac1106be844a5296d3eb5971946cc09ffda0 | Fix note bounds reading, Francisco Alonso / Red Hat | 1 | donote(struct magic_set *ms, void *vbuf, size_t offset, size_t size,
int clazz, int swap, size_t align, int *flags)
{
Elf32_Nhdr nh32;
Elf64_Nhdr nh64;
size_t noff, doff;
#ifdef ELFCORE
int os_style = -1;
#endif
uint32_t namesz, descsz;
unsigned char *nbuf = CAST(unsigned char *, vbuf);
(void)memcpy(xnh... | 134,716,201,177,067,830,000,000,000,000,000,000,000 | readelf.c | 6,375,476,860,511,039,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-3710 | The donote function in readelf.c in file through 5.20, as used in the Fileinfo component in PHP 5.4.34, does not ensure that sufficient note headers are present, which allows remote attackers to cause a denial of service (out-of-bounds read and application crash) via a crafted ELF file. | https://nvd.nist.gov/vuln/detail/CVE-2014-3710 |
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 |
1,258 | 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 | sctp_chunk_length_valid(struct sctp_chunk *chunk,
__u16 required_length)
{
__u16 chunk_length = ntohs(chunk->chunk_hdr->length);
if (unlikely(chunk_length < required_length))
return 0;
return 1;
}
| 256,102,226,120,872,380,000,000,000,000,000,000,000 | sm_statefuns.c | 238,370,719,693,466,800,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,259 | linux | b69040d8e39f20d5215a03502a8e8b4c6ab78395 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b69040d8e39f20d5215a03502a8e8b4c6ab78395 | net: sctp: fix panic on duplicate ASCONF chunks
When receiving a e.g. semi-good formed connection scan in the
form of ...
-------------- INIT[ASCONF; ASCONF_ACK] ------------->
<----------- INIT-ACK[ASCONF; ASCONF_ACK] ------------
-------------------- COOKIE-ECHO -------------------->
<-------------------- C... | 1 | struct sctp_chunk *sctp_assoc_lookup_asconf_ack(
const struct sctp_association *asoc,
__be32 serial)
{
struct sctp_chunk *ack;
/* Walk through the list of cached ASCONF-ACKs and find the
* ack chunk whose serial number matches that of the request.
*/
list_for_each_entry(ack, &asoc->asconf_ack_list,... | 285,652,383,158,838,000,000,000,000,000,000,000,000 | associola.c | 116,881,181,770,839,720,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-3687 | The sctp_assoc_lookup_asconf_ack function in net/sctp/associola.c in the SCTP implementation in the Linux kernel through 3.17.2 allows remote attackers to cause a denial of service (panic) via duplicate ASCONF chunks that trigger an incorrect uncork within the side-effect interpreter. | https://nvd.nist.gov/vuln/detail/CVE-2014-3687 |
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 |
1,270 | linux | 95389b08d93d5c06ec63ab49bd732b0069b7c35e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/95389b08d93d5c06ec63ab49bd732b0069b7c35e | KEYS: Fix termination condition in assoc array garbage collection
This fixes CVE-2014-3631.
It is possible for an associative array to end up with a shortcut node at the
root of the tree if there are more than fan-out leaves in the tree, but they
all crowd into the same slot in the lowest level (ie. they all have the... | 1 | int assoc_array_gc(struct assoc_array *array,
const struct assoc_array_ops *ops,
bool (*iterator)(void *object, void *iterator_data),
void *iterator_data)
{
struct assoc_array_shortcut *shortcut, *new_s;
struct assoc_array_node *node, *new_n;
struct assoc_array_edit *edit;
struct assoc_array_ptr *cur... | 32,773,475,763,762,925,000,000,000,000,000,000,000 | assoc_array.c | 80,273,721,649,681,460,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-3631 | The assoc_array_gc function in the associative-array implementation in lib/assoc_array.c in the Linux kernel before 3.16.3 does not properly implement garbage collection, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via multi... | https://nvd.nist.gov/vuln/detail/CVE-2014-3631 |
1,271 | linux | 2febc839133280d5a5e8e1179c94ea674489dae2 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2febc839133280d5a5e8e1179c94ea674489dae2 | KVM: x86: Improve thread safety in pit
There's a race condition in the PIT emulation code in KVM. In
__kvm_migrate_pit_timer the pit_timer object is accessed without
synchronization. If the race condition occurs at the wrong time this
can crash the host kernel.
This fixes CVE-2014-3611.
Cc: stable@vger.kernel.org
... | 1 | void __kvm_migrate_pit_timer(struct kvm_vcpu *vcpu)
{
struct kvm_pit *pit = vcpu->kvm->arch.vpit;
struct hrtimer *timer;
if (!kvm_vcpu_is_bsp(vcpu) || !pit)
return;
timer = &pit->pit_state.timer;
if (hrtimer_cancel(timer))
hrtimer_start_expires(timer, HRTIMER_MODE_ABS);
}
| 119,883,143,059,227,320,000,000,000,000,000,000,000 | i8254.c | 104,037,544,635,274,550,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2014-3611 | Race condition in the __kvm_migrate_pit_timer function in arch/x86/kvm/i8254.c in the KVM subsystem in the Linux kernel through 3.17.2 allows guest OS users to cause a denial of service (host OS crash) by leveraging incorrect PIT emulation. | https://nvd.nist.gov/vuln/detail/CVE-2014-3611 |
1,272 | linux | 854e8bb1aa06c578c2c9145fa6bfe3680ef63b23 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/854e8bb1aa06c578c2c9145fa6bfe3680ef63b23 | KVM: x86: Check non-canonical addresses upon WRMSR
Upon WRMSR, the CPU should inject #GP if a non-canonical value (address) is
written to certain MSRs. The behavior is "almost" identical for AMD and Intel
(ignoring MSRs that are not implemented in either architecture since they would
anyhow #GP). However, IA32_SYSENTE... | 1 | static int handle_wrmsr(struct kvm_vcpu *vcpu)
{
struct msr_data msr;
u32 ecx = vcpu->arch.regs[VCPU_REGS_RCX];
u64 data = (vcpu->arch.regs[VCPU_REGS_RAX] & -1u)
| ((u64)(vcpu->arch.regs[VCPU_REGS_RDX] & -1u) << 32);
msr.data = data;
msr.index = ecx;
msr.host_initiated = false;
if (vmx_set_msr(vcpu, &msr) ... | 236,270,974,209,097,240,000,000,000,000,000,000,000 | vmx.c | 77,404,791,920,628,900,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3610 | The WRMSR processing functionality in the KVM subsystem in the Linux kernel through 3.17.2 does not properly handle the writing of a non-canonical address to a model-specific register, which allows guest OS users to cause a denial of service (host OS crash) by leveraging guest OS privileges, related to the wrmsr_interc... | https://nvd.nist.gov/vuln/detail/CVE-2014-3610 |
1,274 | linux | 350b8bdd689cd2ab2c67c8a86a0be86cfa0751a7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/350b8bdd689cd2ab2c67c8a86a0be86cfa0751a7 | kvm: iommu: fix the third parameter of kvm_iommu_put_pages (CVE-2014-3601)
The third parameter of kvm_iommu_put_pages is wrong,
It should be 'gfn - slot->base_gfn'.
By making gfn very large, malicious guest or userspace can cause kvm to
go to this error path, and subsequently to pass a huge value as size.
Alternative... | 1 | int kvm_iommu_map_pages(struct kvm *kvm, struct kvm_memory_slot *slot)
{
gfn_t gfn, end_gfn;
pfn_t pfn;
int r = 0;
struct iommu_domain *domain = kvm->arch.iommu_domain;
int flags;
/* check if iommu exists and in use */
if (!domain)
return 0;
gfn = slot->base_gfn;
end_gfn = gfn + slot->npages;
flag... | 150,168,140,098,793,640,000,000,000,000,000,000,000 | iommu.c | 222,325,957,747,450,100,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-3601 | The kvm_iommu_map_pages function in virt/kvm/iommu.c in the Linux kernel through 3.16.1 miscalculates the number of pages during the handling of a mapping failure, which allows guest OS users to (1) cause a denial of service (host OS memory corruption) or possibly have unspecified other impact by triggering a large gfn... | https://nvd.nist.gov/vuln/detail/CVE-2014-3601 |
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 |
1,285 | file | 93e063ee374b6a75729df9e7201fb511e47e259d | https://github.com/file/file | https://github.com/file/file/commit/93e063ee374b6a75729df9e7201fb511e47e259d | Add missing check offset test (Francisco Alonso, Jan Kaluza at RedHat) | 1 | cdf_read_property_info(const cdf_stream_t *sst, const cdf_header_t *h,
uint32_t offs, cdf_property_info_t **info, size_t *count, size_t *maxcount)
{
const cdf_section_header_t *shp;
cdf_section_header_t sh;
const uint8_t *p, *q, *e;
int16_t s16;
int32_t s32;
uint32_t u32;
int64_t s64;
uint64_t u64;
cdf_tim... | 39,554,699,879,590,963,000,000,000,000,000,000,000 | cdf.c | 38,142,421,459,194,790,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-3487 | The cdf_read_property_info function in file before 5.19, as used in the Fileinfo component in PHP before 5.4.30 and 5.5.x before 5.5.14, does not properly validate a stream offset, which allows remote attackers to cause a denial of service (application crash) via a crafted CDF file. | https://nvd.nist.gov/vuln/detail/CVE-2014-3487 |
1,286 | file | 40bade80cbe2af1d0b2cd0420cebd5d5905a2382 | https://github.com/file/file | https://github.com/file/file/commit/40bade80cbe2af1d0b2cd0420cebd5d5905a2382 | Fix incorrect bounds check for sector count. (Francisco Alonso and Jan Kaluza
at RedHat) | 1 | cdf_count_chain(const cdf_sat_t *sat, cdf_secid_t sid, size_t size)
{
size_t i, j;
cdf_secid_t maxsector = (cdf_secid_t)(sat->sat_len * size);
DPRINTF(("Chain:"));
for (j = i = 0; sid >= 0; i++, j++) {
DPRINTF((" %d", sid));
if (j >= CDF_LOOP_LIMIT) {
DPRINTF(("Counting chain loop limit"));
errno ... | 128,863,893,313,877,960,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2014-3480 | The cdf_count_chain function in cdf.c in file before 5.19, as used in the Fileinfo component in PHP before 5.4.30 and 5.5.x before 5.5.14, does not properly validate sector-count data, which allows remote attackers to cause a denial of service (application crash) via a crafted CDF file. | https://nvd.nist.gov/vuln/detail/CVE-2014-3480 |
1,287 | file | 36fadd29849b8087af9f4586f89dbf74ea45be67 | https://github.com/file/file | https://github.com/file/file/commit/36fadd29849b8087af9f4586f89dbf74ea45be67 | Use the proper sector size when checking stream offsets (Francisco Alonso and
Jan Kaluza at RedHat) | 1 | cdf_check_stream_offset(const cdf_stream_t *sst, const cdf_header_t *h,
const void *p, size_t tail, int line)
{
const char *b = (const char *)sst->sst_tab;
const char *e = ((const char *)p) + tail;
(void)&line;
if (e >= b && (size_t)(e - b) <= CDF_SEC_SIZE(h) * sst->sst_len)
return 0;
DPRINTF(("%d: off... | 126,331,237,157,471,830,000,000,000,000,000,000,000 | cdf.c | 252,409,831,567,122,700,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-3479 | The cdf_check_stream_offset function in cdf.c in file before 5.19, as used in the Fileinfo component in PHP before 5.4.30 and 5.5.x before 5.5.14, relies on incorrect sector-size data, which allows remote attackers to cause a denial of service (application crash) via a crafted stream offset in a CDF file. | https://nvd.nist.gov/vuln/detail/CVE-2014-3479 |
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 |
1,289 | linux | 6817ae225cd650fb1c3295d769298c38b1eba818 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6817ae225cd650fb1c3295d769298c38b1eba818 | USB: whiteheat: Added bounds checking for bulk command response
This patch fixes a potential security issue in the whiteheat USB driver
which might allow a local attacker to cause kernel memory corrpution. This
is due to an unchecked memcpy into a fixed size buffer (of 64 bytes). On
EHCI and XHCI busses it's possible ... | 1 | static void command_port_read_callback(struct urb *urb)
{
struct usb_serial_port *command_port = urb->context;
struct whiteheat_command_private *command_info;
int status = urb->status;
unsigned char *data = urb->transfer_buffer;
int result;
command_info = usb_get_serial_port_data(command_port);
if (!command_inf... | 11,995,144,287,059,040,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-3185 | Multiple buffer overflows in the command_port_read_callback function in drivers/usb/serial/whiteheat.c in the Whiteheat USB Serial Driver in the Linux kernel before 3.16.2 allow physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption and system crash) via a crafted devic... | https://nvd.nist.gov/vuln/detail/CVE-2014-3185 |
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 |
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 |
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 |
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 |
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 |
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 |
1,296 | linux | 51217e69697fba92a06e07e16f55c9a52d8e8945 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/51217e69697fba92a06e07e16f55c9a52d8e8945 | HID: logitech: fix bounds checking on LED report size
The check on report size for REPORT_TYPE_LEDS in logi_dj_ll_raw_request()
is wrong; the current check doesn't make any sense -- the report allocated
by HID core in hid_hw_raw_request() can be much larger than
DJREPORT_SHORT_LENGTH, and currently logi_dj_ll_raw_requ... | 1 | static int logi_dj_ll_raw_request(struct hid_device *hid,
unsigned char reportnum, __u8 *buf,
size_t count, unsigned char report_type,
int reqtype)
{
struct dj_device *djdev = hid->driver_data;
struct dj_receiver_dev *djrcv_dev = djdev->dj_receiver_dev;
u8 *out_buf;
int ret;
if (buf[0] != REPORT... | 256,114,427,603,892,440,000,000,000,000,000,000,000 | hid-logitech-dj.c | 259,749,799,322,006,870,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-3183 | Heap-based buffer overflow in the logi_dj_ll_raw_request function in drivers/hid/hid-logitech-dj.c in the Linux kernel before 3.16.2 allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that specifies a large report size for an LED rep... | https://nvd.nist.gov/vuln/detail/CVE-2014-3183 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
1,324 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 1 | static int raw_cmd_copyout(int cmd, void __user *param,
struct floppy_raw_cmd *ptr)
{
int ret;
while (ptr) {
ret = copy_to_user(param, ptr, sizeof(*ptr));
if (ret)
return -EFAULT;
param += sizeof(struct floppy_raw_cmd);
if ((ptr->flags & FD_RAW_READ) && ptr->buffer_length) {
if (ptr->length... | 339,071,363,535,589,500,000,000,000,000,000,000,000 | floppy.c | 32,077,231,849,682,140,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
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 |
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 |
1,327 | linux | 2b13d06c9584b4eb773f1e80bbaedab9a1c344e1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2b13d06c9584b4eb773f1e80bbaedab9a1c344e1 | wanxl: fix info leak in ioctl
The wanxl_ioctl() code fails to initialize the two padding bytes of
struct sync_serial_settings after the ->loopback member. Add an explicit
memset(0) before filling the structure to avoid the info leak.
Signed-off-by: Salva Peiró <speiro@ai2.upv.es>
Signed-off-by: David S. Miller <davem... | 1 | static int wanxl_ioctl(struct net_device *dev, struct ifreq *ifr, int cmd)
{
const size_t size = sizeof(sync_serial_settings);
sync_serial_settings line;
port_t *port = dev_to_port(dev);
if (cmd != SIOCWANDEV)
return hdlc_ioctl(dev, ifr, cmd);
switch (ifr->ifr_settings.type) {
case IF_GET_IFACE:
ifr->ifr_se... | 289,977,000,113,180,630,000,000,000,000,000,000,000 | wanxl.c | 1,534,528,475,873,357,800,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-1445 | The wanxl_ioctl function in drivers/net/wan/wanxl.c in the Linux kernel before 3.11.7 does not properly initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory via an ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-1445 |
1,328 | linux | 96b340406724d87e4621284ebac5e059d67b2194 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/96b340406724d87e4621284ebac5e059d67b2194 | farsync: fix info leak in ioctl
The fst_get_iface() code fails to initialize the two padding bytes of
struct sync_serial_settings after the ->loopback member. Add an explicit
memset(0) before filling the structure to avoid the info leak.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: David S. ... | 1 | fst_get_iface(struct fst_card_info *card, struct fst_port_info *port,
struct ifreq *ifr)
{
sync_serial_settings sync;
int i;
/* First check what line type is set, we'll default to reporting X.21
* if nothing is set as IF_IFACE_SYNC_SERIAL implies it can't be
* changed
*/
switch (port->hwif) {
case E1... | 123,961,501,830,758,970,000,000,000,000,000,000,000 | None | null | [
"CWE-399"
] | CVE-2014-1444 | The fst_get_iface function in drivers/net/wan/farsync.c in the Linux kernel before 3.11.7 does not properly initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory by leveraging the CAP_NET_ADMIN capability for an SIOCWANDEV ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-1444 |
1,329 | FreeRDP | e2745807c4c3e0a590c0f69a9b655dc74ebaa03e | https://github.com/FreeRDP/FreeRDP | https://github.com/sidhpurwala-huzaifa/FreeRDP/commit/e2745807c4c3e0a590c0f69a9b655dc74ebaa03e | None | 1 | BOOL license_read_scope_list(wStream* s, SCOPE_LIST* scopeList)
{
UINT32 i;
UINT32 scopeCount;
if (Stream_GetRemainingLength(s) < 4)
return FALSE;
Stream_Read_UINT32(s, scopeCount); /* ScopeCount (4 bytes) */
scopeList->count = scopeCount;
scopeList->array = (LICENSE_BLOB*) malloc(sizeof(LICENSE_BLOB) *... | 136,158,675,070,583,430,000,000,000,000,000,000,000 | None | null | [
"CWE-189"
] | CVE-2014-0791 | Integer overflow in the license_read_scope_list function in libfreerdp/core/license.c in FreeRDP through 1.0.2 allows remote RDP servers to cause a denial of service (application crash) or possibly have unspecified other impact via a large ScopeCount value in a Scope List in a Server License Request packet. | https://nvd.nist.gov/vuln/detail/CVE-2014-0791 |
1,330 | file | f97486ef5dc3e8735440edc4fc8808c63e1a3ef0 | https://github.com/file/file | https://github.com/file/file/commit/f97486ef5dc3e8735440edc4fc8808c63e1a3ef0 | CVE-2014-0207: Prevent 0 element vectors and vectors longer than the number
of properties from accessing random memory. | 1 | cdf_read_property_info(const cdf_stream_t *sst, const cdf_header_t *h,
uint32_t offs, cdf_property_info_t **info, size_t *count, size_t *maxcount)
{
const cdf_section_header_t *shp;
cdf_section_header_t sh;
const uint8_t *p, *q, *e;
int16_t s16;
int32_t s32;
uint32_t u32;
int64_t s64;
uint64_t u64;
cdf_tim... | 203,768,158,432,833,200,000,000,000,000,000,000,000 | cdf.c | 252,409,831,567,122,700,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0238 | The cdf_read_property_info function in cdf.c in the Fileinfo component in PHP before 5.4.29 and 5.5.x before 5.5.13 allows remote attackers to cause a denial of service (infinite loop or out-of-bounds memory access) via a vector that (1) has zero length or (2) is too long. | https://nvd.nist.gov/vuln/detail/CVE-2014-0238 |
1,331 | file | b8acc83781d5a24cc5101e525d15efe0482c280d | https://github.com/file/file | https://github.com/file/file/commit/b8acc83781d5a24cc5101e525d15efe0482c280d | Remove loop that kept reading the same offset (Jan Kaluza) | 1 | cdf_unpack_summary_info(const cdf_stream_t *sst, const cdf_header_t *h,
cdf_summary_info_header_t *ssi, cdf_property_info_t **info, size_t *count)
{
size_t i, maxcount;
const cdf_summary_info_header_t *si =
CAST(const cdf_summary_info_header_t *, sst->sst_tab);
const cdf_section_declaration_t *sd =
... | 256,057,506,035,934,500,000,000,000,000,000,000,000 | cdf.c | 252,409,831,567,122,700,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-0237 | The cdf_unpack_summary_info function in cdf.c in the Fileinfo component in PHP before 5.4.29 and 5.5.x before 5.5.13 allows remote attackers to cause a denial of service (performance degradation) by triggering many file_printf calls. | https://nvd.nist.gov/vuln/detail/CVE-2014-0237 |
1,332 | file | 6d209c1c489457397a5763bca4b28e43aac90391 | https://github.com/file/file | https://github.com/file/file/commit/6d209c1c489457397a5763bca4b28e43aac90391 | Apply patches from file-CVE-2012-1571.patch
From Francisco Alonso Espejo:
file < 5.18/git version can be made to crash when checking some
corrupt CDF files (Using an invalid cdf_read_short_sector size)
The problem I found here, is that in most situations (if
h_short_sec_size_p2 > 8) because the blocksiz... | 1 | cdf_read_short_sector(const cdf_stream_t *sst, void *buf, size_t offs,
size_t len, const cdf_header_t *h, cdf_secid_t id)
{
size_t ss = CDF_SHORT_SEC_SIZE(h);
size_t pos = CDF_SHORT_SEC_POS(h, id);
assert(ss == len);
if (pos > CDF_SEC_SIZE(h) * sst->sst_len) {
DPRINTF(("Out of bounds read %" SIZE_T_FORMAT... | 17,449,660,697,413,268,000,000,000,000,000,000,000 | cdf.c | 252,409,831,567,122,700,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0207 | The cdf_read_short_sector function in cdf.c in file before 5.19, as used in the Fileinfo component in PHP before 5.4.30 and 5.5.x before 5.5.14, allows remote attackers to cause a denial of service (assertion failure and application exit) via a crafted CDF file. | https://nvd.nist.gov/vuln/detail/CVE-2014-0207 |
1,335 | linux | 7ada876a8703f23befbb20a7465a702ee39b1704 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ada876a8703f23befbb20a7465a702ee39b1704 | futex: Fix errors in nested key ref-counting
futex_wait() is leaking key references due to futex_wait_setup()
acquiring an additional reference via the queue_lock() routine. The
nested key ref-counting has been masking bugs and complicating code
analysis. queue_lock() is only called with a previously ref-counted
key, ... | 1 | static int futex_wait(u32 __user *uaddr, int fshared,
u32 val, ktime_t *abs_time, u32 bitset, int clockrt)
{
struct hrtimer_sleeper timeout, *to = NULL;
struct restart_block *restart;
struct futex_hash_bucket *hb;
struct futex_q q;
int ret;
if (!bitset)
return -EINVAL;
q.pi_state = NULL;
q.bitset = ... | 173,721,295,716,039,500,000,000,000,000,000,000,000 | futex.c | 310,482,782,767,060,830,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-0205 | The futex_wait function in kernel/futex.c in the Linux kernel before 2.6.37 does not properly maintain a certain reference count during requeue operations, which allows local users to cause a denial of service (use-after-free and system crash) or possibly gain privileges via a crafted application that triggers a zero c... | https://nvd.nist.gov/vuln/detail/CVE-2014-0205 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.