idx int64 | project string | commit_id string | project_url string | commit_url string | commit_message string | target int64 | func string | func_hash float64 | file_name string | file_hash float64 | cwe list | cve string | cve_desc string | nvd_url string |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
159,362 | linux | 9590232bb4f4cc824f3425a6e1349afbe6d6d2b7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9590232bb4f4cc824f3425a6e1349afbe6d6d2b7 | staging/android/ion : fix a race condition in the ion driver
There is a use-after-free problem in the ion driver.
This is caused by a race condition in the ion_ioctl()
function.
A handle has ref count of 1 and two tasks on different
cpus calls ION_IOC_FREE simultaneously.
cpu 0 cpu ... | 0 | static long ion_ioctl(struct file *filp, unsigned int cmd, unsigned long arg)
{
struct ion_client *client = filp->private_data;
struct ion_device *dev = client->dev;
struct ion_handle *cleanup_handle = NULL;
int ret = 0;
unsigned int dir;
union {
struct ion_fd_data fd;
struct ion_allocation_data allocation;
... | 112,570,386,299,949,190,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2016-9120 | Race condition in the ion_ioctl function in drivers/staging/android/ion/ion.c in the Linux kernel before 4.6 allows local users to gain privileges or cause a denial of service (use-after-free) by calling ION_IOC_FREE on two CPUs at the same time. | https://nvd.nist.gov/vuln/detail/CVE-2016-9120 |
1,711 | linux | 05692d7005a364add85c6e25a6c4447ce08f913a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/05692d7005a364add85c6e25a6c4447ce08f913a | vfio/pci: Fix integer overflows, bitmask check
The VFIO_DEVICE_SET_IRQS ioctl did not sufficiently sanitize
user-supplied integers, potentially allowing memory corruption. This
patch adds appropriate integer overflow checks, checks the range bounds
for VFIO_IRQ_SET_DATA_NONE, and also verifies that only single element... | 1 | static long vfio_pci_ioctl(void *device_data,
unsigned int cmd, unsigned long arg)
{
struct vfio_pci_device *vdev = device_data;
unsigned long minsz;
if (cmd == VFIO_DEVICE_GET_INFO) {
struct vfio_device_info info;
minsz = offsetofend(struct vfio_device_info, num_irqs);
if (copy_from_user(&info, (void... | 14,003,092,725,819,900,000,000,000,000,000,000,000 | vfio_pci.c | 50,249,264,138,078,830,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2016-9083 | drivers/vfio/pci/vfio_pci.c in the Linux kernel through 4.8.11 allows local users to bypass integer overflow checks, and cause a denial of service (memory corruption) or have unspecified other impact, by leveraging access to a vfio PCI device file for a VFIO_DEVICE_SET_IRQS ioctl call, aka a "state machine confusion bu... | https://nvd.nist.gov/vuln/detail/CVE-2016-9083 |
159,363 | linux | 05692d7005a364add85c6e25a6c4447ce08f913a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/05692d7005a364add85c6e25a6c4447ce08f913a | vfio/pci: Fix integer overflows, bitmask check
The VFIO_DEVICE_SET_IRQS ioctl did not sufficiently sanitize
user-supplied integers, potentially allowing memory corruption. This
patch adds appropriate integer overflow checks, checks the range bounds
for VFIO_IRQ_SET_DATA_NONE, and also verifies that only single element... | 0 | static long vfio_pci_ioctl(void *device_data,
unsigned int cmd, unsigned long arg)
{
struct vfio_pci_device *vdev = device_data;
unsigned long minsz;
if (cmd == VFIO_DEVICE_GET_INFO) {
struct vfio_device_info info;
minsz = offsetofend(struct vfio_device_info, num_irqs);
if (copy_from_user(&info, (void... | 293,176,314,062,606,000,000,000,000,000,000,000,000 | vfio_pci.c | 159,227,476,627,395,160,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2016-9083 | drivers/vfio/pci/vfio_pci.c in the Linux kernel through 4.8.11 allows local users to bypass integer overflow checks, and cause a denial of service (memory corruption) or have unspecified other impact, by leveraging access to a vfio PCI device file for a VFIO_DEVICE_SET_IRQS ioctl call, aka a "state machine confusion bu... | https://nvd.nist.gov/vuln/detail/CVE-2016-9083 |
9,330 | linux | 05692d7005a364add85c6e25a6c4447ce08f913a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/05692d7005a364add85c6e25a6c4447ce08f913a | vfio/pci: Fix integer overflows, bitmask check
The VFIO_DEVICE_SET_IRQS ioctl did not sufficiently sanitize
user-supplied integers, potentially allowing memory corruption. This
patch adds appropriate integer overflow checks, checks the range bounds
for VFIO_IRQ_SET_DATA_NONE, and also verifies that only single element... | 1 | static int vfio_msi_enable(struct vfio_pci_device *vdev, int nvec, bool msix)
{
struct pci_dev *pdev = vdev->pdev;
unsigned int flag = msix ? PCI_IRQ_MSIX : PCI_IRQ_MSI;
int ret;
if (!is_irq_none(vdev))
return -EINVAL;
vdev->ctx = kzalloc(nvec * sizeof(struct vfio_pci_irq_ctx), GFP_KERNEL);
if (!vdev->ctx... | 265,085,938,067,485,300,000,000,000,000,000,000,000 | vfio_pci_intrs.c | 317,782,573,120,508,840,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2016-9083 | drivers/vfio/pci/vfio_pci.c in the Linux kernel through 4.8.11 allows local users to bypass integer overflow checks, and cause a denial of service (memory corruption) or have unspecified other impact, by leveraging access to a vfio PCI device file for a VFIO_DEVICE_SET_IRQS ioctl call, aka a "state machine confusion bu... | https://nvd.nist.gov/vuln/detail/CVE-2016-9083 |
184,455 | linux | 05692d7005a364add85c6e25a6c4447ce08f913a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/05692d7005a364add85c6e25a6c4447ce08f913a | vfio/pci: Fix integer overflows, bitmask check
The VFIO_DEVICE_SET_IRQS ioctl did not sufficiently sanitize
user-supplied integers, potentially allowing memory corruption. This
patch adds appropriate integer overflow checks, checks the range bounds
for VFIO_IRQ_SET_DATA_NONE, and also verifies that only single element... | 0 | static int vfio_msi_enable(struct vfio_pci_device *vdev, int nvec, bool msix)
{
struct pci_dev *pdev = vdev->pdev;
unsigned int flag = msix ? PCI_IRQ_MSIX : PCI_IRQ_MSI;
int ret;
if (!is_irq_none(vdev))
return -EINVAL;
vdev->ctx = kcalloc(nvec, sizeof(struct vfio_pci_irq_ctx), GFP_KERNEL);
if (!vdev->ctx)... | 26,326,996,389,887,427,000,000,000,000,000,000,000 | vfio_pci_intrs.c | 117,428,172,435,715,760,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2016-9083 | drivers/vfio/pci/vfio_pci.c in the Linux kernel through 4.8.11 allows local users to bypass integer overflow checks, and cause a denial of service (memory corruption) or have unspecified other impact, by leveraging access to a vfio PCI device file for a VFIO_DEVICE_SET_IRQS ioctl call, aka a "state machine confusion bu... | https://nvd.nist.gov/vuln/detail/CVE-2016-9083 |
1,712 | openssh-portable | ec165c392ca54317dbe3064a8c200de6531e89ad | https://github.com/openssh/openssh-portable | https://github.com/openssh/openssh-portable/commit/ec165c392ca54317dbe3064a8c200de6531e89ad | upstream commit
Unregister the KEXINIT handler after message has been
received. Otherwise an unauthenticated peer can repeat the KEXINIT and cause
allocation of up to 128MB -- until the connection is closed. Reported by
shilei-c at 360.cn
Upstream-ID: 43649ae12a27ef94290db16d1a98294588b75c05 | 1 | kex_input_kexinit(int type, u_int32_t seq, void *ctxt)
{
struct ssh *ssh = ctxt;
struct kex *kex = ssh->kex;
const u_char *ptr;
u_int i;
size_t dlen;
int r;
debug("SSH2_MSG_KEXINIT received");
if (kex == NULL)
return SSH_ERR_INVALID_ARGUMENT;
ptr = sshpkt_ptr(ssh, &dlen);
if ((r = sshbuf_put(kex->pee... | 339,023,894,075,827,400,000,000,000,000,000,000,000 | kex.c | 228,822,789,731,076,200,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2016-8858 | The kex_input_kexinit function in kex.c in OpenSSH 6.x and 7.x through 7.3 allows remote attackers to cause a denial of service (memory consumption) by sending many duplicate KEXINIT requests. NOTE: a third party reports that "OpenSSH upstream does not consider this as a security issue." | https://nvd.nist.gov/vuln/detail/CVE-2016-8858 |
159,364 | openssh-portable | ec165c392ca54317dbe3064a8c200de6531e89ad | https://github.com/openssh/openssh-portable | https://github.com/openssh/openssh-portable/commit/ec165c392ca54317dbe3064a8c200de6531e89ad | upstream commit
Unregister the KEXINIT handler after message has been
received. Otherwise an unauthenticated peer can repeat the KEXINIT and cause
allocation of up to 128MB -- until the connection is closed. Reported by
shilei-c at 360.cn
Upstream-ID: 43649ae12a27ef94290db16d1a98294588b75c05 | 0 | kex_input_kexinit(int type, u_int32_t seq, void *ctxt)
{
struct ssh *ssh = ctxt;
struct kex *kex = ssh->kex;
const u_char *ptr;
u_int i;
size_t dlen;
int r;
debug("SSH2_MSG_KEXINIT received");
if (kex == NULL)
return SSH_ERR_INVALID_ARGUMENT;
ssh_dispatch_set(ssh, SSH2_MSG_KEXINIT, NULL);
ptr = sshpkt... | 315,750,281,441,489,820,000,000,000,000,000,000,000 | kex.c | 138,747,432,066,778,580,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2016-8858 | The kex_input_kexinit function in kex.c in OpenSSH 6.x and 7.x through 7.3 allows remote attackers to cause a denial of service (memory consumption) by sending many duplicate KEXINIT requests. NOTE: a third party reports that "OpenSSH upstream does not consider this as a security issue." | https://nvd.nist.gov/vuln/detail/CVE-2016-8858 |
1,715 | linux | ded89912156b1a47d940a0c954c43afbabd0c42c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ded89912156b1a47d940a0c954c43afbabd0c42c | brcmfmac: avoid potential stack overflow in brcmf_cfg80211_start_ap()
User-space can choose to omit NL80211_ATTR_SSID and only provide raw
IE TLV data. When doing so it can provide SSID IE with length exceeding
the allowed size. The driver further processes this IE copying it
into a local variable without checking the... | 1 | brcmf_cfg80211_start_ap(struct wiphy *wiphy, struct net_device *ndev,
struct cfg80211_ap_settings *settings)
{
s32 ie_offset;
struct brcmf_cfg80211_info *cfg = wiphy_to_cfg(wiphy);
struct brcmf_if *ifp = netdev_priv(ndev);
const struct brcmf_tlv *ssid_ie;
const struct brcmf_tlv *country_ie;
struct brcmf_ssid_l... | 107,596,959,318,646,240,000,000,000,000,000,000,000 | cfg80211.c | 239,830,303,826,032,670,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-8658 | Stack-based buffer overflow in the brcmf_cfg80211_start_ap function in drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c in the Linux kernel before 4.7.5 allows local users to cause a denial of service (system crash) or possibly have unspecified other impact via a long SSID Information Element in a command to... | https://nvd.nist.gov/vuln/detail/CVE-2016-8658 |
159,367 | linux | ded89912156b1a47d940a0c954c43afbabd0c42c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ded89912156b1a47d940a0c954c43afbabd0c42c | brcmfmac: avoid potential stack overflow in brcmf_cfg80211_start_ap()
User-space can choose to omit NL80211_ATTR_SSID and only provide raw
IE TLV data. When doing so it can provide SSID IE with length exceeding
the allowed size. The driver further processes this IE copying it
into a local variable without checking the... | 0 | brcmf_cfg80211_start_ap(struct wiphy *wiphy, struct net_device *ndev,
struct cfg80211_ap_settings *settings)
{
s32 ie_offset;
struct brcmf_cfg80211_info *cfg = wiphy_to_cfg(wiphy);
struct brcmf_if *ifp = netdev_priv(ndev);
const struct brcmf_tlv *ssid_ie;
const struct brcmf_tlv *country_ie;
struct brcmf_ssid_l... | 119,538,781,881,396,450,000,000,000,000,000,000,000 | cfg80211.c | 286,841,950,897,430,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-8658 | Stack-based buffer overflow in the brcmf_cfg80211_start_ap function in drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c in the Linux kernel before 4.7.5 allows local users to cause a denial of service (system crash) or possibly have unspecified other impact via a long SSID Information Element in a command to... | https://nvd.nist.gov/vuln/detail/CVE-2016-8658 |
1,718 | linux | 4afa5f9617927453ac04b24b584f6c718dfb4f45 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4afa5f9617927453ac04b24b584f6c718dfb4f45 | crypto: algif_hash - Only export and import on sockets with data
The hash_accept call fails to work on sockets that have not received
any data. For some algorithm implementations it may cause crashes.
This patch fixes this by ensuring that we only export and import on
sockets that have received data.
Cc: stable@vge... | 1 | static int hash_accept(struct socket *sock, struct socket *newsock, int flags)
{
struct sock *sk = sock->sk;
struct alg_sock *ask = alg_sk(sk);
struct hash_ctx *ctx = ask->private;
struct ahash_request *req = &ctx->req;
char state[crypto_ahash_statesize(crypto_ahash_reqtfm(req))];
struct sock *sk2;
struct alg_... | 855,501,647,450,820,300,000,000,000,000,000,000 | algif_hash.c | 274,659,569,534,280,800,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2016-8646 | The hash_accept function in crypto/algif_hash.c in the Linux kernel before 4.3.6 allows local users to cause a denial of service (OOPS) by attempting to trigger use of in-kernel hash algorithms for a socket that has received zero bytes of data. | https://nvd.nist.gov/vuln/detail/CVE-2016-8646 |
159,368 | linux | 4afa5f9617927453ac04b24b584f6c718dfb4f45 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4afa5f9617927453ac04b24b584f6c718dfb4f45 | crypto: algif_hash - Only export and import on sockets with data
The hash_accept call fails to work on sockets that have not received
any data. For some algorithm implementations it may cause crashes.
This patch fixes this by ensuring that we only export and import on
sockets that have received data.
Cc: stable@vge... | 0 | static int hash_accept(struct socket *sock, struct socket *newsock, int flags)
{
struct sock *sk = sock->sk;
struct alg_sock *ask = alg_sk(sk);
struct hash_ctx *ctx = ask->private;
struct ahash_request *req = &ctx->req;
char state[crypto_ahash_statesize(crypto_ahash_reqtfm(req))];
struct sock *sk2;
struct alg_... | 258,640,263,284,650,470,000,000,000,000,000,000,000 | algif_hash.c | 282,276,849,918,189,670,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2016-8646 | The hash_accept function in crypto/algif_hash.c in the Linux kernel before 4.3.6 allows local users to cause a denial of service (OOPS) by attempting to trigger use of in-kernel hash algorithms for a socket that has received zero bytes of data. | https://nvd.nist.gov/vuln/detail/CVE-2016-8646 |
1,719 | linux | ac6e780070e30e4c35bd395acfe9191e6268bdd3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac6e780070e30e4c35bd395acfe9191e6268bdd3 | tcp: take care of truncations done by sk_filter()
With syzkaller help, Marco Grassi found a bug in TCP stack,
crashing in tcp_collapse()
Root cause is that sk_filter() can truncate the incoming skb,
but TCP stack was not really expecting this to happen.
It probably was expecting a simple DROP or ACCEPT behavior.
We ... | 1 | int tcp_v4_rcv(struct sk_buff *skb)
{
struct net *net = dev_net(skb->dev);
const struct iphdr *iph;
const struct tcphdr *th;
bool refcounted;
struct sock *sk;
int ret;
if (skb->pkt_type != PACKET_HOST)
goto discard_it;
/* Count it even if it's bad */
__TCP_INC_STATS(net, TCP_MIB_INSEGS);
if (!pskb_may_pu... | 284,014,189,874,385,800,000,000,000,000,000,000,000 | tcp_ipv4.c | 172,691,742,001,660,820,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2016-8645 | The TCP stack in the Linux kernel before 4.8.10 mishandles skb truncation, which allows local users to cause a denial of service (system crash) via a crafted application that makes sendto system calls, related to net/ipv4/tcp_ipv4.c and net/ipv6/tcp_ipv6.c. | https://nvd.nist.gov/vuln/detail/CVE-2016-8645 |
159,369 | linux | ac6e780070e30e4c35bd395acfe9191e6268bdd3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ac6e780070e30e4c35bd395acfe9191e6268bdd3 | tcp: take care of truncations done by sk_filter()
With syzkaller help, Marco Grassi found a bug in TCP stack,
crashing in tcp_collapse()
Root cause is that sk_filter() can truncate the incoming skb,
but TCP stack was not really expecting this to happen.
It probably was expecting a simple DROP or ACCEPT behavior.
We ... | 0 | int tcp_v4_rcv(struct sk_buff *skb)
{
struct net *net = dev_net(skb->dev);
const struct iphdr *iph;
const struct tcphdr *th;
bool refcounted;
struct sock *sk;
int ret;
if (skb->pkt_type != PACKET_HOST)
goto discard_it;
/* Count it even if it's bad */
__TCP_INC_STATS(net, TCP_MIB_INSEGS);
if (!pskb_may_pu... | 273,930,640,090,995,960,000,000,000,000,000,000,000 | tcp_ipv4.c | 172,595,451,732,144,600,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2016-8645 | The TCP stack in the Linux kernel before 4.8.10 mishandles skb truncation, which allows local users to cause a denial of service (system crash) via a crafted application that makes sendto system calls, related to net/ipv4/tcp_ipv4.c and net/ipv6/tcp_ipv6.c. | https://nvd.nist.gov/vuln/detail/CVE-2016-8645 |
1,725 | linux | c58d6c93680f28ac58984af61d0a7ebf4319c241 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c58d6c93680f28ac58984af61d0a7ebf4319c241 | netfilter: nfnetlink: correctly validate length of batch messages
If nlh->nlmsg_len is zero then an infinite loop is triggered because
'skb_pull(skb, msglen);' pulls zero bytes.
The calculation in nlmsg_len() underflows if 'nlh->nlmsg_len <
NLMSG_HDRLEN' which bypasses the length validation and will later
trigger an ... | 1 | static void nfnetlink_rcv_batch(struct sk_buff *skb, struct nlmsghdr *nlh,
u_int16_t subsys_id)
{
struct sk_buff *oskb = skb;
struct net *net = sock_net(skb->sk);
const struct nfnetlink_subsystem *ss;
const struct nfnl_callback *nc;
static LIST_HEAD(err_list);
u32 status;
int err;
if (subsys_id >= NFNL_SUB... | 284,681,399,279,689,300,000,000,000,000,000,000,000 | nfnetlink.c | 266,157,007,856,312,750,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2016-7917 | The nfnetlink_rcv_batch function in net/netfilter/nfnetlink.c in the Linux kernel before 4.5 does not check whether a batch message's length field is large enough, which allows local users to obtain sensitive information from kernel memory or cause a denial of service (infinite loop or out-of-bounds read) by leveraging... | https://nvd.nist.gov/vuln/detail/CVE-2016-7917 |
159,373 | linux | c58d6c93680f28ac58984af61d0a7ebf4319c241 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c58d6c93680f28ac58984af61d0a7ebf4319c241 | netfilter: nfnetlink: correctly validate length of batch messages
If nlh->nlmsg_len is zero then an infinite loop is triggered because
'skb_pull(skb, msglen);' pulls zero bytes.
The calculation in nlmsg_len() underflows if 'nlh->nlmsg_len <
NLMSG_HDRLEN' which bypasses the length validation and will later
trigger an ... | 0 | static void nfnetlink_rcv_batch(struct sk_buff *skb, struct nlmsghdr *nlh,
u_int16_t subsys_id)
{
struct sk_buff *oskb = skb;
struct net *net = sock_net(skb->sk);
const struct nfnetlink_subsystem *ss;
const struct nfnl_callback *nc;
static LIST_HEAD(err_list);
u32 status;
int err;
if (subsys_id >= NFNL_SUB... | 320,739,279,747,289,060,000,000,000,000,000,000,000 | nfnetlink.c | 285,152,943,961,183,760,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2016-7917 | The nfnetlink_rcv_batch function in net/netfilter/nfnetlink.c in the Linux kernel before 4.5 does not check whether a batch message's length field is large enough, which allows local users to obtain sensitive information from kernel memory or cause a denial of service (infinite loop or out-of-bounds read) by leveraging... | https://nvd.nist.gov/vuln/detail/CVE-2016-7917 |
1,726 | linux | 50220dead1650609206efe91f0cc116132d59b3f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/50220dead1650609206efe91f0cc116132d59b3f | HID: core: prevent out-of-bound readings
Plugging a Logitech DJ receiver with KASAN activated raises a bunch of
out-of-bound readings.
The fields are allocated up to MAX_USAGE, meaning that potentially, we do
not have enough fields to fit the incoming values.
Add checks and silence KASAN.
Signed-off-by: Benjamin Tis... | 1 | static void hid_input_field(struct hid_device *hid, struct hid_field *field,
__u8 *data, int interrupt)
{
unsigned n;
unsigned count = field->report_count;
unsigned offset = field->report_offset;
unsigned size = field->report_size;
__s32 min = field->logical_minimum;
__s32 max = field->logical_maximum;
__... | 188,242,288,363,672,830,000,000,000,000,000,000,000 | hid-core.c | 315,690,708,720,987,600,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2016-7915 | The hid_input_field function in drivers/hid/hid-core.c in the Linux kernel before 4.6 allows physically proximate attackers to obtain sensitive information from kernel memory or cause a denial of service (out-of-bounds read) by connecting a device, as demonstrated by a Logitech DJ receiver. | https://nvd.nist.gov/vuln/detail/CVE-2016-7915 |
159,374 | linux | 50220dead1650609206efe91f0cc116132d59b3f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/50220dead1650609206efe91f0cc116132d59b3f | HID: core: prevent out-of-bound readings
Plugging a Logitech DJ receiver with KASAN activated raises a bunch of
out-of-bound readings.
The fields are allocated up to MAX_USAGE, meaning that potentially, we do
not have enough fields to fit the incoming values.
Add checks and silence KASAN.
Signed-off-by: Benjamin Tis... | 0 | static void hid_input_field(struct hid_device *hid, struct hid_field *field,
__u8 *data, int interrupt)
{
unsigned n;
unsigned count = field->report_count;
unsigned offset = field->report_offset;
unsigned size = field->report_size;
__s32 min = field->logical_minimum;
__s32 max = field->logical_maximum;
__... | 230,981,975,803,473,500,000,000,000,000,000,000,000 | hid-core.c | 311,002,751,498,489,920,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2016-7915 | The hid_input_field function in drivers/hid/hid-core.c in the Linux kernel before 4.6 allows physically proximate attackers to obtain sensitive information from kernel memory or cause a denial of service (out-of-bounds read) by connecting a device, as demonstrated by a Logitech DJ receiver. | https://nvd.nist.gov/vuln/detail/CVE-2016-7915 |
1,729 | linux | 38740a5b87d53ceb89eb2c970150f6e94e00373a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/38740a5b87d53ceb89eb2c970150f6e94e00373a | usb: gadget: f_fs: Fix use-after-free
When using asynchronous read or write operations on the USB endpoints the
issuer of the IO request is notified by calling the ki_complete() callback
of the submitted kiocb when the URB has been completed.
Calling this ki_complete() callback will free kiocb. Make sure that the
str... | 1 | static void ffs_user_copy_worker(struct work_struct *work)
{
struct ffs_io_data *io_data = container_of(work, struct ffs_io_data,
work);
int ret = io_data->req->status ? io_data->req->status :
io_data->req->actual;
if (io_data->read && ret > 0) {
use_mm(io_data->mm);
ret = copy_to_iter(io_d... | 325,805,134,765,406,900,000,000,000,000,000,000,000 | f_fs.c | 210,013,898,798,065,750,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2016-7912 | Use-after-free vulnerability in the ffs_user_copy_worker function in drivers/usb/gadget/function/f_fs.c in the Linux kernel before 4.5.3 allows local users to gain privileges by accessing an I/O data structure after a certain callback call. | https://nvd.nist.gov/vuln/detail/CVE-2016-7912 |
159,376 | linux | 38740a5b87d53ceb89eb2c970150f6e94e00373a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/38740a5b87d53ceb89eb2c970150f6e94e00373a | usb: gadget: f_fs: Fix use-after-free
When using asynchronous read or write operations on the USB endpoints the
issuer of the IO request is notified by calling the ki_complete() callback
of the submitted kiocb when the URB has been completed.
Calling this ki_complete() callback will free kiocb. Make sure that the
str... | 0 | static void ffs_user_copy_worker(struct work_struct *work)
{
struct ffs_io_data *io_data = container_of(work, struct ffs_io_data,
work);
int ret = io_data->req->status ? io_data->req->status :
io_data->req->actual;
bool kiocb_has_eventfd = io_data->kiocb->ki_flags & IOCB_EVENTFD;
if (io_data->r... | 236,297,660,084,698,250,000,000,000,000,000,000,000 | f_fs.c | 104,996,550,616,475,700,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2016-7912 | Use-after-free vulnerability in the ffs_user_copy_worker function in drivers/usb/gadget/function/f_fs.c in the Linux kernel before 4.5.3 allows local users to gain privileges by accessing an I/O data structure after a certain callback call. | https://nvd.nist.gov/vuln/detail/CVE-2016-7912 |
1,732 | libgd | 40bec0f38f50e8510f5bb71a82f516d46facde03 | https://github.com/libgd/libgd | https://github.com/libgd/libgd/commit/40bec0f38f50e8510f5bb71a82f516d46facde03 | Merge branch 'pull-request/296' | 1 | BGD_DECLARE(void) gdImageWebpCtx (gdImagePtr im, gdIOCtx * outfile, int quality)
{
uint8_t *argb;
int x, y;
uint8_t *p;
uint8_t *out;
size_t out_size;
if (im == NULL) {
return;
}
if (!gdImageTrueColor(im)) {
gd_error("Paletter image not supported by webp");
return;
}
if (quality == -1) {
quality =... | 134,338,295,145,600,240,000,000,000,000,000,000,000 | None | null | [
"CWE-190"
] | CVE-2016-7568 | Integer overflow in the gdImageWebpCtx function in gd_webp.c in the GD Graphics Library (aka libgd) through 2.2.3, as used in PHP through 7.0.11, allows remote attackers to cause a denial of service (heap-based buffer overflow) or possibly have unspecified other impact via crafted imagewebp and imagedestroy calls. | https://nvd.nist.gov/vuln/detail/CVE-2016-7568 |
48,119 | libgd | 40bec0f38f50e8510f5bb71a82f516d46facde03 | https://github.com/libgd/libgd | https://github.com/libgd/libgd/commit/40bec0f38f50e8510f5bb71a82f516d46facde03 | Merge branch 'pull-request/296' | 0 | BGD_DECLARE(gdImagePtr) gdImageCreateFromWebpCtx (gdIOCtx * infile)
{
int width, height;
uint8_t *filedata = NULL;
uint8_t *argb = NULL;
unsigned char *read, *temp;
size_t size = 0, n;
gdImagePtr im;
int x, y;
uint8_t *p;
do {
temp = gdRealloc(filedata, size+GD_WEBP_ALLOC_STEP);
if (temp) {
f... | 334,503,776,316,471,200,000,000,000,000,000,000,000 | None | null | [
"CWE-190"
] | CVE-2016-7568 | Integer overflow in the gdImageWebpCtx function in gd_webp.c in the GD Graphics Library (aka libgd) through 2.2.3, as used in PHP through 7.0.11, allows remote attackers to cause a denial of service (heap-based buffer overflow) or possibly have unspecified other impact via crafted imagewebp and imagedestroy calls. | https://nvd.nist.gov/vuln/detail/CVE-2016-7568 |
1,739 | php-src | 28f80baf3c53e267c9ce46a2a0fadbb981585132 | https://github.com/php/php-src | https://github.com/php/php-src/commit/28f80baf3c53e267c9ce46a2a0fadbb981585132?w=1 | Fix bug #72293 - Heap overflow in mysqlnd related to BIT fields | 1 | php_mysqlnd_rowp_read_text_protocol_aux(MYSQLND_MEMORY_POOL_CHUNK * row_buffer, zval ** fields,
unsigned int field_count, const MYSQLND_FIELD * fields_metadata,
zend_bool as_int_or_float, zend_bool copy_data, MYSQLND_STATS * stats TSRMLS_DC)
{
unsigned int i;
zend_bool last_field_was_string = FALS... | 190,243,804,462,372,060,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-7412 | ext/mysqlnd/mysqlnd_wireprotocol.c in PHP before 5.6.26 and 7.x before 7.0.11 does not verify that a BIT field has the UNSIGNED_FLAG flag, which allows remote MySQL servers to cause a denial of service (heap-based buffer overflow) or possibly have unspecified other impact via crafted field metadata. | https://nvd.nist.gov/vuln/detail/CVE-2016-7412 |
159,383 | php-src | 28f80baf3c53e267c9ce46a2a0fadbb981585132 | https://github.com/php/php-src | https://github.com/php/php-src/commit/28f80baf3c53e267c9ce46a2a0fadbb981585132?w=1 | Fix bug #72293 - Heap overflow in mysqlnd related to BIT fields | 0 | php_mysqlnd_rowp_read_text_protocol_aux(MYSQLND_MEMORY_POOL_CHUNK * row_buffer, zval ** fields,
unsigned int field_count, const MYSQLND_FIELD * fields_metadata,
zend_bool as_int_or_float, zend_bool copy_data, MYSQLND_STATS * stats TSRMLS_DC)
{
unsigned int i;
zend_bool last_field_was_string = FALS... | 308,351,466,432,035,150,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-7412 | ext/mysqlnd/mysqlnd_wireprotocol.c in PHP before 5.6.26 and 7.x before 7.0.11 does not verify that a BIT field has the UNSIGNED_FLAG flag, which allows remote MySQL servers to cause a denial of service (heap-based buffer overflow) or possibly have unspecified other impact via crafted field metadata. | https://nvd.nist.gov/vuln/detail/CVE-2016-7412 |
1,744 | libarchive | 6e06b1c89dd0d16f74894eac4cfc1327a06ee4a0 | https://github.com/libarchive/libarchive | https://github.com/libarchive/libarchive/commit/6e06b1c89dd0d16f74894eac4cfc1327a06ee4a0 | Fix a potential crash issue discovered by Alexander Cherepanov:
It seems bsdtar automatically handles stacked compression. This is a
nice feature but it could be problematic when it's completely
unlimited. Most clearly it's illustrated with quines:
$ curl -sRO http://www.maximumcompression.com/selfgz.gz
$ (ulimit -v... | 1 | choose_filters(struct archive_read *a)
{
int number_bidders, i, bid, best_bid;
struct archive_read_filter_bidder *bidder, *best_bidder;
struct archive_read_filter *filter;
ssize_t avail;
int r;
for (;;) {
number_bidders = sizeof(a->bidders) / sizeof(a->bidders[0]);
best_bid = 0;
best_bidder = NU... | 187,470,736,725,719,080,000,000,000,000,000,000,000 | None | null | [
"CWE-399"
] | CVE-2016-7166 | libarchive before 3.2.0 does not limit the number of recursive decompressions, which allows remote attackers to cause a denial of service (memory consumption and application crash) via a crafted gzip file. | https://nvd.nist.gov/vuln/detail/CVE-2016-7166 |
159,386 | libarchive | 6e06b1c89dd0d16f74894eac4cfc1327a06ee4a0 | https://github.com/libarchive/libarchive | https://github.com/libarchive/libarchive/commit/6e06b1c89dd0d16f74894eac4cfc1327a06ee4a0 | Fix a potential crash issue discovered by Alexander Cherepanov:
It seems bsdtar automatically handles stacked compression. This is a
nice feature but it could be problematic when it's completely
unlimited. Most clearly it's illustrated with quines:
$ curl -sRO http://www.maximumcompression.com/selfgz.gz
$ (ulimit -v... | 0 | choose_filters(struct archive_read *a)
{
int number_bidders, i, bid, best_bid, n;
struct archive_read_filter_bidder *bidder, *best_bidder;
struct archive_read_filter *filter;
ssize_t avail;
int r;
for (n = 0; n < 25; ++n) {
number_bidders = sizeof(a->bidders) / sizeof(a->bidders[0]);
best_bid = 0;... | 208,888,126,414,159,480,000,000,000,000,000,000,000 | archive_read.c | 56,291,700,790,894,850,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2016-7166 | libarchive before 3.2.0 does not limit the number of recursive decompressions, which allows remote attackers to cause a denial of service (memory consumption and application crash) via a crafted gzip file. | https://nvd.nist.gov/vuln/detail/CVE-2016-7166 |
1,745 | openjpeg | c16bc057ba3f125051c9966cf1f5b68a05681de4 | https://github.com/uclouvain/openjpeg | https://github.com/uclouvain/openjpeg/commit/c16bc057ba3f125051c9966cf1f5b68a05681de4 | Fix an integer overflow issue (#809)
Prevent an integer overflow issue in function opj_pi_create_decode of
pi.c. | 1 | opj_pi_iterator_t *opj_pi_create_decode(opj_image_t *p_image,
opj_cp_t *p_cp,
OPJ_UINT32 p_tile_no)
{
/* loop */
OPJ_UINT32 pino;
OPJ_UINT32 compno, resno;
/* to store w, h, dx and dy fro all components and resolutions */
OPJ_UINT32 * l_tmp_data;
OPJ_UINT32 ** l_tmp_ptr;
/* encoding pramete... | 331,884,484,169,803,600,000,000,000,000,000,000,000 | pi.c | 85,117,321,979,618,870,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2016-7163 | Integer overflow in the opj_pi_create_decode function in pi.c in OpenJPEG allows remote attackers to execute arbitrary code via a crafted JP2 file, which triggers an out-of-bounds read or write. | https://nvd.nist.gov/vuln/detail/CVE-2016-7163 |
48,407 | openjpeg | c16bc057ba3f125051c9966cf1f5b68a05681de4 | https://github.com/uclouvain/openjpeg | https://github.com/uclouvain/openjpeg/commit/c16bc057ba3f125051c9966cf1f5b68a05681de4 | Fix an integer overflow issue (#809)
Prevent an integer overflow issue in function opj_pi_create_decode of
pi.c. | 0 | opj_pi_iterator_t *opj_pi_initialise_encode(const opj_image_t *p_image,
opj_cp_t *p_cp,
OPJ_UINT32 p_tile_no,
J2K_T2_MODE p_t2_mode )
{
/* loop*/
OPJ_UINT32 pino;
OPJ_UINT32 compno, res... | 151,251,317,642,545,320,000,000,000,000,000,000,000 | pi.c | 315,094,855,754,080,930,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2016-7163 | Integer overflow in the opj_pi_create_decode function in pi.c in OpenJPEG allows remote attackers to execute arbitrary code via a crafted JP2 file, which triggers an out-of-bounds read or write. | https://nvd.nist.gov/vuln/detail/CVE-2016-7163 |
1,746 | curl | curl-7_50_2~32 | https://github.com/curl/curl | https://github.com/curl/curl/commit/curl-7_50_2~32 | nss: refuse previously loaded certificate from file
... when we are not asked to use a certificate from file | 1 | static SECStatus SelectClientCert(void *arg, PRFileDesc *sock,
struct CERTDistNamesStr *caNames,
struct CERTCertificateStr **pRetCert,
struct SECKEYPrivateKeyStr **pRetKey)
{
struct ssl_connect_data *connssl = (stru... | 183,626,236,930,701,920,000,000,000,000,000,000,000 | nss.c | 12,471,031,817,769,896,000,000,000,000,000,000,000 | [
"CWE-287"
] | CVE-2016-7141 | curl and libcurl before 7.50.2, when built with NSS and the libnsspem.so library is available at runtime, allow remote attackers to hijack the authentication of a TLS connection by leveraging reuse of a previously loaded client certificate from file for a connection for which no certificate has been set, a different vu... | https://nvd.nist.gov/vuln/detail/CVE-2016-7141 |
159,387 | curl | curl-7_50_2~32 | https://github.com/curl/curl | https://github.com/curl/curl/commit/curl-7_50_2~32 | nss: refuse previously loaded certificate from file
... when we are not asked to use a certificate from file | 0 | static SECStatus SelectClientCert(void *arg, PRFileDesc *sock,
struct CERTDistNamesStr *caNames,
struct CERTCertificateStr **pRetCert,
struct SECKEYPrivateKeyStr **pRetKey)
{
struct ssl_connect_data *connssl = (stru... | 330,444,781,977,515,030,000,000,000,000,000,000,000 | nss.c | 77,629,197,530,408,030,000,000,000,000,000,000,000 | [
"CWE-287"
] | CVE-2016-7141 | curl and libcurl before 7.50.2, when built with NSS and the libnsspem.so library is available at runtime, allow remote attackers to hijack the authentication of a TLS connection by leveraging reuse of a previously loaded client certificate from file for a connection for which no certificate has been set, a different vu... | https://nvd.nist.gov/vuln/detail/CVE-2016-7141 |
1,753 | php-src | b6f13a5ef9d6280cf984826a5de012a32c396cd4 | https://github.com/php/php-src | https://github.com/php/php-src/commit/b6f13a5ef9d6280cf984826a5de012a32c396cd4?w=1 | None | 1 | PHP_FUNCTION(imagetruecolortopalette)
{
zval *IM;
zend_bool dither;
long ncolors;
gdImagePtr im;
if (zend_parse_parameters(ZEND_NUM_ARGS() TSRMLS_CC, "rbl", &IM, &dither, &ncolors) == FAILURE) {
return;
}
ZEND_FETCH_RESOURCE(im, gdImagePtr, &IM, -1, "Image", le_gd);
if (ncolors <= 0) {
php_error_docr... | 181,878,688,249,174,300,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2016-7126 | The imagetruecolortopalette function in ext/gd/gd.c in PHP before 5.6.25 and 7.x before 7.0.10 does not properly validate the number of colors, which allows remote attackers to cause a denial of service (select_colors allocation error and out-of-bounds write) or possibly have unspecified other impact via a large value ... | https://nvd.nist.gov/vuln/detail/CVE-2016-7126 |
48,542 | php-src | b6f13a5ef9d6280cf984826a5de012a32c396cd4 | https://github.com/php/php-src | https://github.com/php/php-src/commit/b6f13a5ef9d6280cf984826a5de012a32c396cd4?w=1 | None | 0 | PHP_FUNCTION(imagesetstyle)
{
zval *IM, *styles;
gdImagePtr im;
int * stylearr;
int index;
HashPosition pos;
if (zend_parse_parameters(ZEND_NUM_ARGS() TSRMLS_CC, "ra", &IM, &styles) == FAILURE) {
return;
}
ZEND_FETCH_RESOURCE(im, gdImagePtr, &IM, -1, "Image", le_gd);
/* copy the style values in the style... | 307,437,650,167,470,400,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2016-7126 | The imagetruecolortopalette function in ext/gd/gd.c in PHP before 5.6.25 and 7.x before 7.0.10 does not properly validate the number of colors, which allows remote attackers to cause a denial of service (select_colors allocation error and out-of-bounds write) or possibly have unspecified other impact via a large value ... | https://nvd.nist.gov/vuln/detail/CVE-2016-7126 |
1,758 | linux | 34b88a68f26a75e4fded796f1a49c40f82234b7d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/34b88a68f26a75e4fded796f1a49c40f82234b7d | net: Fix use after free in the recvmmsg exit path
The syzkaller fuzzer hit the following use-after-free:
Call Trace:
[<ffffffff8175ea0e>] __asan_report_load8_noabort+0x3e/0x40 mm/kasan/report.c:295
[<ffffffff851cc31a>] __sys_recvmmsg+0x6fa/0x7f0 net/socket.c:2261
[< inline >] SYSC_recvmmsg net/sock... | 1 | int __sys_recvmmsg(int fd, struct mmsghdr __user *mmsg, unsigned int vlen,
unsigned int flags, struct timespec *timeout)
{
int fput_needed, err, datagrams;
struct socket *sock;
struct mmsghdr __user *entry;
struct compat_mmsghdr __user *compat_entry;
struct msghdr msg_sys;
struct timespec end_time;
if (tim... | 32,465,179,856,289,110,000,000,000,000,000,000,000 | socket.c | 323,406,668,974,979,600,000,000,000,000,000,000,000 | [
"CWE-19"
] | CVE-2016-7117 | Use-after-free vulnerability in the __sys_recvmmsg function in net/socket.c in the Linux kernel before 4.5.2 allows remote attackers to execute arbitrary code via vectors involving a recvmmsg system call that is mishandled during error processing. | https://nvd.nist.gov/vuln/detail/CVE-2016-7117 |
159,392 | linux | 34b88a68f26a75e4fded796f1a49c40f82234b7d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/34b88a68f26a75e4fded796f1a49c40f82234b7d | net: Fix use after free in the recvmmsg exit path
The syzkaller fuzzer hit the following use-after-free:
Call Trace:
[<ffffffff8175ea0e>] __asan_report_load8_noabort+0x3e/0x40 mm/kasan/report.c:295
[<ffffffff851cc31a>] __sys_recvmmsg+0x6fa/0x7f0 net/socket.c:2261
[< inline >] SYSC_recvmmsg net/sock... | 0 | int __sys_recvmmsg(int fd, struct mmsghdr __user *mmsg, unsigned int vlen,
unsigned int flags, struct timespec *timeout)
{
int fput_needed, err, datagrams;
struct socket *sock;
struct mmsghdr __user *entry;
struct compat_mmsghdr __user *compat_entry;
struct msghdr msg_sys;
struct timespec end_time;
if (tim... | 244,204,465,702,419,900,000,000,000,000,000,000,000 | socket.c | 135,393,890,616,510,580,000,000,000,000,000,000,000 | [
"CWE-19"
] | CVE-2016-7117 | Use-after-free vulnerability in the __sys_recvmmsg function in net/socket.c in the Linux kernel before 4.5.2 allows remote attackers to execute arbitrary code via vectors involving a recvmmsg system call that is mishandled during error processing. | https://nvd.nist.gov/vuln/detail/CVE-2016-7117 |
1,759 | MAC-Telnet | b69d11727d4f0f8cf719c79e3fb700f55ca03e9a | https://github.com/haakonnessjoen/MAC-Telnet | https://github.com/haakonnessjoen/MAC-Telnet/commit/b69d11727d4f0f8cf719c79e3fb700f55ca03e9a | Merge pull request #20 from eyalitki/master
2nd round security fixes from eyalitki | 1 | static int handle_packet(unsigned char *data, int data_len) {
struct mt_mactelnet_hdr pkthdr;
/* Minimal size checks (pings are not supported here) */
if (data_len < MT_HEADER_LEN){
return -1;
}
parse_packet(data, &pkthdr);
/* We only care about packets with correct sessionkey */
if (pkthdr.seskey != session... | 321,429,272,328,439,870,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-7115 | Buffer overflow in the handle_packet function in mactelnet.c in the client in MAC-Telnet 0.4.3 and earlier allows remote TELNET servers to execute arbitrary code via a long string in an MT_CPTYPE_PASSSALT control packet. | https://nvd.nist.gov/vuln/detail/CVE-2016-7115 |
159,393 | MAC-Telnet | b69d11727d4f0f8cf719c79e3fb700f55ca03e9a | https://github.com/haakonnessjoen/MAC-Telnet | https://github.com/haakonnessjoen/MAC-Telnet/commit/b69d11727d4f0f8cf719c79e3fb700f55ca03e9a | Merge pull request #20 from eyalitki/master
2nd round security fixes from eyalitki | 0 | static int handle_packet(unsigned char *data, int data_len) {
struct mt_mactelnet_hdr pkthdr;
/* Minimal size checks (pings are not supported here) */
if (data_len < MT_HEADER_LEN){
return -1;
}
parse_packet(data, &pkthdr);
/* We only care about packets with correct sessionkey */
if (pkthdr.seskey != session... | 335,075,861,911,373,660,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-7115 | Buffer overflow in the handle_packet function in mactelnet.c in the client in MAC-Telnet 0.4.3 and earlier allows remote TELNET servers to execute arbitrary code via a long string in an MT_CPTYPE_PASSSALT control packet. | https://nvd.nist.gov/vuln/detail/CVE-2016-7115 |
1,790 | linux | 10eec60ce79187686e052092e5383c99b4420a20 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/10eec60ce79187686e052092e5383c99b4420a20 | vfs: ioctl: prevent double-fetch in dedupe ioctl
This prevents a double-fetch from user space that can lead to to an
undersized allocation and heap overflow.
Fixes: 54dbc1517237 ("vfs: hoist the btrfs deduplication ioctl to the vfs")
Signed-off-by: Scott Bauer <sbauer@plzdonthack.me>
Signed-off-by: Linus Torvalds <to... | 1 | static long ioctl_file_dedupe_range(struct file *file, void __user *arg)
{
struct file_dedupe_range __user *argp = arg;
struct file_dedupe_range *same = NULL;
int ret;
unsigned long size;
u16 count;
if (get_user(count, &argp->dest_count)) {
ret = -EFAULT;
goto out;
}
size = offsetof(struct file_dedupe_ran... | 177,427,685,205,348,800,000,000,000,000,000,000,000 | ioctl.c | 238,069,660,354,633,780,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-6516 | Race condition in the ioctl_file_dedupe_range function in fs/ioctl.c in the Linux kernel through 4.7 allows local users to cause a denial of service (heap-based buffer overflow) or possibly gain privileges by changing a certain count value, aka a "double fetch" vulnerability. | https://nvd.nist.gov/vuln/detail/CVE-2016-6516 |
159,419 | linux | 10eec60ce79187686e052092e5383c99b4420a20 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/10eec60ce79187686e052092e5383c99b4420a20 | vfs: ioctl: prevent double-fetch in dedupe ioctl
This prevents a double-fetch from user space that can lead to to an
undersized allocation and heap overflow.
Fixes: 54dbc1517237 ("vfs: hoist the btrfs deduplication ioctl to the vfs")
Signed-off-by: Scott Bauer <sbauer@plzdonthack.me>
Signed-off-by: Linus Torvalds <to... | 0 | static long ioctl_file_dedupe_range(struct file *file, void __user *arg)
{
struct file_dedupe_range __user *argp = arg;
struct file_dedupe_range *same = NULL;
int ret;
unsigned long size;
u16 count;
if (get_user(count, &argp->dest_count)) {
ret = -EFAULT;
goto out;
}
size = offsetof(struct file_dedupe_ran... | 260,865,874,835,008,300,000,000,000,000,000,000,000 | ioctl.c | 271,128,527,647,450,980,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-6516 | Race condition in the ioctl_file_dedupe_range function in fs/ioctl.c in the Linux kernel through 4.7 allows local users to cause a denial of service (heap-based buffer overflow) or possibly gain privileges by changing a certain count value, aka a "double fetch" vulnerability. | https://nvd.nist.gov/vuln/detail/CVE-2016-6516 |
1,791 | openssh-portable | fcd135c9df440bcd2d5870405ad3311743d78d97 | https://github.com/openssh/openssh-portable | https://github.com/openssh/openssh-portable/commit/fcd135c9df440bcd2d5870405ad3311743d78d97 | upstream commit
Skip passwords longer than 1k in length so clients can't
easily DoS sshd by sending very long passwords, causing it to spend CPU
hashing them. feedback djm@, ok markus@.
Brought to our attention by tomas.kuthan at oracle.com, shilei-c at
360.cn and coredump at autistici.org
Upstream-ID: d0af7d4a2190b... | 1 | auth_password(Authctxt *authctxt, const char *password)
{
struct passwd * pw = authctxt->pw;
int result, ok = authctxt->valid;
#if defined(USE_SHADOW) && defined(HAS_SHADOW_EXPIRE)
static int expire_checked = 0;
#endif
#ifndef HAVE_CYGWIN
if (pw->pw_uid == 0 && options.permit_root_login != PERMIT_YES)
ok =... | 319,587,561,961,095,600,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-6515 | The auth_password function in auth-passwd.c in sshd in OpenSSH before 7.3 does not limit password lengths for password authentication, which allows remote attackers to cause a denial of service (crypt CPU consumption) via a long string. | https://nvd.nist.gov/vuln/detail/CVE-2016-6515 |
159,420 | openssh-portable | fcd135c9df440bcd2d5870405ad3311743d78d97 | https://github.com/openssh/openssh-portable | https://github.com/openssh/openssh-portable/commit/fcd135c9df440bcd2d5870405ad3311743d78d97 | upstream commit
Skip passwords longer than 1k in length so clients can't
easily DoS sshd by sending very long passwords, causing it to spend CPU
hashing them. feedback djm@, ok markus@.
Brought to our attention by tomas.kuthan at oracle.com, shilei-c at
360.cn and coredump at autistici.org
Upstream-ID: d0af7d4a2190b... | 0 | auth_password(Authctxt *authctxt, const char *password)
{
struct passwd * pw = authctxt->pw;
int result, ok = authctxt->valid;
#if defined(USE_SHADOW) && defined(HAS_SHADOW_EXPIRE)
static int expire_checked = 0;
#endif
if (strlen(password) > MAX_PASSWORD_LEN)
return 0;
#ifndef HAVE_CYGWIN
if (pw->pw_uid =... | 126,785,056,958,622,480,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-6515 | The auth_password function in auth-passwd.c in sshd in OpenSSH before 7.3 does not limit password lengths for password authentication, which allows remote attackers to cause a denial of service (crypt CPU consumption) via a long string. | https://nvd.nist.gov/vuln/detail/CVE-2016-6515 |
1,795 | collectd | b589096f907052b3a4da2b9ccc9b0e2e888dfc18 | https://github.com/collectd/collectd | https://github.com/collectd/collectd/commit/b589096f907052b3a4da2b9ccc9b0e2e888dfc18 | network plugin: Fix heap overflow in parse_packet().
Emilien Gaspar has identified a heap overflow in parse_packet(), the
function used by the network plugin to parse incoming network packets.
This is a vulnerability in collectd, though the scope is not clear at
this point. At the very least specially crafted network... | 1 | static int parse_packet (sockent_t *se, /* {{{ */
void *buffer, size_t buffer_size, int flags,
const char *username)
{
int status;
value_list_t vl = VALUE_LIST_INIT;
notification_t n;
#if HAVE_LIBGCRYPT
int packet_was_signed = (flags & PP_SIGNED);
int packet_was_encrypted = (flags & PP_ENCRYPTED);
in... | 268,201,944,099,933,340,000,000,000,000,000,000,000 | network.c | 301,004,326,594,565,760,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-6254 | Heap-based buffer overflow in the parse_packet function in network.c in collectd before 5.4.3 and 5.x before 5.5.2 allows remote attackers to cause a denial of service (daemon crash) or possibly execute arbitrary code via a crafted network packet. | https://nvd.nist.gov/vuln/detail/CVE-2016-6254 |
159,423 | collectd | b589096f907052b3a4da2b9ccc9b0e2e888dfc18 | https://github.com/collectd/collectd | https://github.com/collectd/collectd/commit/b589096f907052b3a4da2b9ccc9b0e2e888dfc18 | network plugin: Fix heap overflow in parse_packet().
Emilien Gaspar has identified a heap overflow in parse_packet(), the
function used by the network plugin to parse incoming network packets.
This is a vulnerability in collectd, though the scope is not clear at
this point. At the very least specially crafted network... | 0 | static int parse_packet (sockent_t *se, /* {{{ */
void *buffer, size_t buffer_size, int flags,
const char *username)
{
int status;
value_list_t vl = VALUE_LIST_INIT;
notification_t n;
#if HAVE_LIBGCRYPT
int packet_was_signed = (flags & PP_SIGNED);
int packet_was_encrypted = (flags & PP_ENCRYPTED);
in... | 242,899,437,312,944,020,000,000,000,000,000,000,000 | network.c | 305,685,284,444,773,730,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-6254 | Heap-based buffer overflow in the parse_packet function in network.c in collectd before 5.4.3 and 5.x before 5.5.2 allows remote attackers to cause a denial of service (daemon crash) or possibly execute arbitrary code via a crafted network packet. | https://nvd.nist.gov/vuln/detail/CVE-2016-6254 |
1,804 | linux | 9409e22acdfc9153f88d9b1ed2bd2a5b34d2d3ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9409e22acdfc9153f88d9b1ed2bd2a5b34d2d3ca | vfs: rename: check backing inode being equal
If a file is renamed to a hardlink of itself POSIX specifies that rename(2)
should do nothing and return success.
This condition is checked in vfs_rename(). However it won't detect hard
links on overlayfs where these are given separate inodes on the overlayfs
layer.
Over... | 1 | int vfs_rename(struct inode *old_dir, struct dentry *old_dentry,
struct inode *new_dir, struct dentry *new_dentry,
struct inode **delegated_inode, unsigned int flags)
{
int error;
bool is_dir = d_is_dir(old_dentry);
const unsigned char *old_name;
struct inode *source = old_dentry->d_inode;
struct i... | 125,343,890,223,537,840,000,000,000,000,000,000,000 | namei.c | 194,268,518,459,072,760,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2016-6198 | The filesystem layer in the Linux kernel before 4.5.5 proceeds with post-rename operations after an OverlayFS file is renamed to a self-hardlink, which allows local users to cause a denial of service (system crash) via a rename system call, related to fs/namei.c and fs/open.c. | https://nvd.nist.gov/vuln/detail/CVE-2016-6198 |
159,431 | linux | 9409e22acdfc9153f88d9b1ed2bd2a5b34d2d3ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9409e22acdfc9153f88d9b1ed2bd2a5b34d2d3ca | vfs: rename: check backing inode being equal
If a file is renamed to a hardlink of itself POSIX specifies that rename(2)
should do nothing and return success.
This condition is checked in vfs_rename(). However it won't detect hard
links on overlayfs where these are given separate inodes on the overlayfs
layer.
Over... | 0 | int vfs_rename(struct inode *old_dir, struct dentry *old_dentry,
struct inode *new_dir, struct dentry *new_dentry,
struct inode **delegated_inode, unsigned int flags)
{
int error;
bool is_dir = d_is_dir(old_dentry);
const unsigned char *old_name;
struct inode *source = old_dentry->d_inode;
struct i... | 231,311,519,190,706,250,000,000,000,000,000,000,000 | namei.c | 10,200,902,842,513,675,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2016-6198 | The filesystem layer in the Linux kernel before 4.5.5 proceeds with post-rename operations after an OverlayFS file is renamed to a self-hardlink, which allows local users to cause a denial of service (system crash) via a rename system call, related to fs/namei.c and fs/open.c. | https://nvd.nist.gov/vuln/detail/CVE-2016-6198 |
1,807 | linux | 30a46a4647fd1df9cf52e43bf467f0d9265096ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/30a46a4647fd1df9cf52e43bf467f0d9265096ca | apparmor: fix oops, validate buffer size in apparmor_setprocattr()
When proc_pid_attr_write() was changed to use memdup_user apparmor's
(interface violating) assumption that the setprocattr buffer was always
a single page was violated.
The size test is not strictly speaking needed as proc_pid_attr_write()
will reject... | 1 | static int apparmor_setprocattr(struct task_struct *task, char *name,
void *value, size_t size)
{
struct common_audit_data sa;
struct apparmor_audit_data aad = {0,};
char *command, *args = value;
size_t arg_size;
int error;
if (size == 0)
return -EINVAL;
/* args points to a PAGE_SIZE buffer, AppAr... | 94,069,181,006,806,240,000,000,000,000,000,000,000 | lsm.c | 292,105,851,096,993,260,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-6187 | The apparmor_setprocattr function in security/apparmor/lsm.c in the Linux kernel before 4.6.5 does not validate the buffer size, which allows local users to gain privileges by triggering an AppArmor setprocattr hook. | https://nvd.nist.gov/vuln/detail/CVE-2016-6187 |
159,434 | linux | 30a46a4647fd1df9cf52e43bf467f0d9265096ca | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/30a46a4647fd1df9cf52e43bf467f0d9265096ca | apparmor: fix oops, validate buffer size in apparmor_setprocattr()
When proc_pid_attr_write() was changed to use memdup_user apparmor's
(interface violating) assumption that the setprocattr buffer was always
a single page was violated.
The size test is not strictly speaking needed as proc_pid_attr_write()
will reject... | 0 | static int apparmor_setprocattr(struct task_struct *task, char *name,
void *value, size_t size)
{
struct common_audit_data sa;
struct apparmor_audit_data aad = {0,};
char *command, *largs = NULL, *args = value;
size_t arg_size;
int error;
if (size == 0)
return -EINVAL;
/* task can only write its ... | 316,278,662,210,682,900,000,000,000,000,000,000,000 | lsm.c | 151,796,176,699,647,540,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-6187 | The apparmor_setprocattr function in security/apparmor/lsm.c in the Linux kernel before 4.6.5 does not validate the buffer size, which allows local users to gain privileges by triggering an AppArmor setprocattr hook. | https://nvd.nist.gov/vuln/detail/CVE-2016-6187 |
1,808 | linux | 096cdc6f52225835ff503f987a0d68ef770bb78e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/096cdc6f52225835ff503f987a0d68ef770bb78e | platform/chrome: cros_ec_dev - double fetch bug in ioctl
We verify "u_cmd.outsize" and "u_cmd.insize" but we need to make sure
that those values have not changed between the two copy_from_user()
calls. Otherwise it could lead to a buffer overflow.
Additionally, cros_ec_cmd_xfer() can set s_cmd->insize to a lower val... | 1 | static long ec_device_ioctl_xcmd(struct cros_ec_dev *ec, void __user *arg)
{
long ret;
struct cros_ec_command u_cmd;
struct cros_ec_command *s_cmd;
if (copy_from_user(&u_cmd, arg, sizeof(u_cmd)))
return -EFAULT;
if ((u_cmd.outsize > EC_MAX_MSG_BYTES) ||
(u_cmd.insize > EC_MAX_MSG_BYTES))
return -EINVAL;... | 163,172,745,704,404,350,000,000,000,000,000,000,000 | cros_ec_dev.c | 103,010,045,391,424,050,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2016-6156 | Race condition in the ec_device_ioctl_xcmd function in drivers/platform/chrome/cros_ec_dev.c in the Linux kernel before 4.7 allows local users to cause a denial of service (out-of-bounds array access) by changing a certain size value, aka a "double fetch" vulnerability. | https://nvd.nist.gov/vuln/detail/CVE-2016-6156 |
159,435 | linux | 096cdc6f52225835ff503f987a0d68ef770bb78e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/096cdc6f52225835ff503f987a0d68ef770bb78e | platform/chrome: cros_ec_dev - double fetch bug in ioctl
We verify "u_cmd.outsize" and "u_cmd.insize" but we need to make sure
that those values have not changed between the two copy_from_user()
calls. Otherwise it could lead to a buffer overflow.
Additionally, cros_ec_cmd_xfer() can set s_cmd->insize to a lower val... | 0 | static long ec_device_ioctl_xcmd(struct cros_ec_dev *ec, void __user *arg)
{
long ret;
struct cros_ec_command u_cmd;
struct cros_ec_command *s_cmd;
if (copy_from_user(&u_cmd, arg, sizeof(u_cmd)))
return -EFAULT;
if ((u_cmd.outsize > EC_MAX_MSG_BYTES) ||
(u_cmd.insize > EC_MAX_MSG_BYTES))
return -EINVAL;... | 251,658,417,274,212,100,000,000,000,000,000,000,000 | cros_ec_dev.c | 73,154,653,493,163,460,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2016-6156 | Race condition in the ec_device_ioctl_xcmd function in drivers/platform/chrome/cros_ec_dev.c in the Linux kernel before 4.7 allows local users to cause a denial of service (out-of-bounds array access) by changing a certain size value, aka a "double fetch" vulnerability. | https://nvd.nist.gov/vuln/detail/CVE-2016-6156 |
1,810 | linux | 532c34b5fbf1687df63b3fcd5b2846312ac943c6 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/532c34b5fbf1687df63b3fcd5b2846312ac943c6 | s390/sclp_ctl: fix potential information leak with /dev/sclp
The sclp_ctl_ioctl_sccb function uses two copy_from_user calls to
retrieve the sclp request from user space. The first copy_from_user
fetches the length of the request which is stored in the first two
bytes of the request. The second copy_from_user gets the ... | 1 | static int sclp_ctl_ioctl_sccb(void __user *user_area)
{
struct sclp_ctl_sccb ctl_sccb;
struct sccb_header *sccb;
int rc;
if (copy_from_user(&ctl_sccb, user_area, sizeof(ctl_sccb)))
return -EFAULT;
if (!sclp_ctl_cmdw_supported(ctl_sccb.cmdw))
return -EOPNOTSUPP;
sccb = (void *) get_zeroed_page(GFP_KER... | 210,420,001,045,995,120,000,000,000,000,000,000,000 | sclp_ctl.c | 33,795,353,629,654,793,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2016-6130 | Race condition in the sclp_ctl_ioctl_sccb function in drivers/s390/char/sclp_ctl.c in the Linux kernel before 4.6 allows local users to obtain sensitive information from kernel memory by changing a certain length value, aka a "double fetch" vulnerability. | https://nvd.nist.gov/vuln/detail/CVE-2016-6130 |
159,437 | linux | 532c34b5fbf1687df63b3fcd5b2846312ac943c6 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/532c34b5fbf1687df63b3fcd5b2846312ac943c6 | s390/sclp_ctl: fix potential information leak with /dev/sclp
The sclp_ctl_ioctl_sccb function uses two copy_from_user calls to
retrieve the sclp request from user space. The first copy_from_user
fetches the length of the request which is stored in the first two
bytes of the request. The second copy_from_user gets the ... | 0 | static int sclp_ctl_ioctl_sccb(void __user *user_area)
{
struct sclp_ctl_sccb ctl_sccb;
struct sccb_header *sccb;
unsigned long copied;
int rc;
if (copy_from_user(&ctl_sccb, user_area, sizeof(ctl_sccb)))
return -EFAULT;
if (!sclp_ctl_cmdw_supported(ctl_sccb.cmdw))
return -EOPNOTSUPP;
sccb = (void *) ... | 274,213,129,587,470,750,000,000,000,000,000,000,000 | sclp_ctl.c | 153,754,560,306,271,560,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2016-6130 | Race condition in the sclp_ctl_ioctl_sccb function in drivers/s390/char/sclp_ctl.c in the Linux kernel before 4.6 allows local users to obtain sensitive information from kernel memory by changing a certain length value, aka a "double fetch" vulnerability. | https://nvd.nist.gov/vuln/detail/CVE-2016-6130 |
1,811 | libarchive | 3ad08e01b4d253c66ae56414886089684155af22 | https://github.com/libarchive/libarchive | https://github.com/libarchive/libarchive/commit/3ad08e01b4d253c66ae56414886089684155af22 | Issue 717: Fix integer overflow when computing location of volume descriptor
The multiplication here defaulted to 'int' but calculations
of file positions should always use int64_t. A simple cast
suffices to fix this since the base location is always 32 bits
for ISO, so multiplying by the sector size will never over... | 1 | choose_volume(struct archive_read *a, struct iso9660 *iso9660)
{
struct file_info *file;
int64_t skipsize;
struct vd *vd;
const void *block;
char seenJoliet;
vd = &(iso9660->primary);
if (!iso9660->opt_support_joliet)
iso9660->seenJoliet = 0;
if (iso9660->seenJoliet &&
vd->location > iso9660->joliet.locati... | 79,794,590,550,957,910,000,000,000,000,000,000,000 | archive_read_support_format_iso9660.c | 161,757,426,250,598,000,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2016-5844 | Integer overflow in the ISO parser in libarchive before 3.2.1 allows remote attackers to cause a denial of service (application crash) via a crafted ISO file. | https://nvd.nist.gov/vuln/detail/CVE-2016-5844 |
159,438 | libarchive | 3ad08e01b4d253c66ae56414886089684155af22 | https://github.com/libarchive/libarchive | https://github.com/libarchive/libarchive/commit/3ad08e01b4d253c66ae56414886089684155af22 | Issue 717: Fix integer overflow when computing location of volume descriptor
The multiplication here defaulted to 'int' but calculations
of file positions should always use int64_t. A simple cast
suffices to fix this since the base location is always 32 bits
for ISO, so multiplying by the sector size will never over... | 0 | choose_volume(struct archive_read *a, struct iso9660 *iso9660)
{
struct file_info *file;
int64_t skipsize;
struct vd *vd;
const void *block;
char seenJoliet;
vd = &(iso9660->primary);
if (!iso9660->opt_support_joliet)
iso9660->seenJoliet = 0;
if (iso9660->seenJoliet &&
vd->location > iso9660->joliet.locati... | 307,769,093,106,564,140,000,000,000,000,000,000,000 | archive_read_support_format_iso9660.c | 163,147,012,537,271,200,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2016-5844 | Integer overflow in the ISO parser in libarchive before 3.2.1 allows remote attackers to cause a denial of service (application crash) via a crafted ISO file. | https://nvd.nist.gov/vuln/detail/CVE-2016-5844 |
1,812 | linux | 93a2001bdfd5376c3dc2158653034c20392d15c5 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/93a2001bdfd5376c3dc2158653034c20392d15c5 | HID: hiddev: validate num_values for HIDIOCGUSAGES, HIDIOCSUSAGES commands
This patch validates the num_values parameter from userland during the
HIDIOCGUSAGES and HIDIOCSUSAGES commands. Previously, if the report id was set
to HID_REPORT_ID_UNKNOWN, we would fail to validate the num_values parameter
leading to a heap... | 1 | static noinline int hiddev_ioctl_usage(struct hiddev *hiddev, unsigned int cmd, void __user *user_arg)
{
struct hid_device *hid = hiddev->hid;
struct hiddev_report_info rinfo;
struct hiddev_usage_ref_multi *uref_multi = NULL;
struct hiddev_usage_ref *uref;
struct hid_report *report;
struct hid_field *field;
int ... | 48,668,317,957,594,940,000,000,000,000,000,000,000 | hiddev.c | 214,175,292,621,757,830,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-5829 | Multiple heap-based buffer overflows in the hiddev_ioctl_usage function in drivers/hid/usbhid/hiddev.c in the Linux kernel through 4.6.3 allow local users to cause a denial of service or possibly have unspecified other impact via a crafted (1) HIDIOCGUSAGES or (2) HIDIOCSUSAGES ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2016-5829 |
159,439 | linux | 93a2001bdfd5376c3dc2158653034c20392d15c5 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/93a2001bdfd5376c3dc2158653034c20392d15c5 | HID: hiddev: validate num_values for HIDIOCGUSAGES, HIDIOCSUSAGES commands
This patch validates the num_values parameter from userland during the
HIDIOCGUSAGES and HIDIOCSUSAGES commands. Previously, if the report id was set
to HID_REPORT_ID_UNKNOWN, we would fail to validate the num_values parameter
leading to a heap... | 0 | static noinline int hiddev_ioctl_usage(struct hiddev *hiddev, unsigned int cmd, void __user *user_arg)
{
struct hid_device *hid = hiddev->hid;
struct hiddev_report_info rinfo;
struct hiddev_usage_ref_multi *uref_multi = NULL;
struct hiddev_usage_ref *uref;
struct hid_report *report;
struct hid_field *field;
int ... | 319,564,447,442,161,730,000,000,000,000,000,000,000 | hiddev.c | 110,158,910,551,404,300,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-5829 | Multiple heap-based buffer overflows in the hiddev_ioctl_usage function in drivers/hid/usbhid/hiddev.c in the Linux kernel through 4.6.3 allow local users to cause a denial of service or possibly have unspecified other impact via a crafted (1) HIDIOCGUSAGES or (2) HIDIOCSUSAGES ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2016-5829 |
1,908 | linux | 9bf292bfca94694a721449e3fd752493856710f6 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9bf292bfca94694a721449e3fd752493856710f6 | misc: mic: Fix for double fetch security bug in VOP driver
The MIC VOP driver does two successive reads from user space to read a
variable length data structure. Kernel memory corruption can result if
the data structure changes between the two reads. This patch disallows
the chance of this happening.
Bugzilla: https:... | 1 | static long vop_ioctl(struct file *f, unsigned int cmd, unsigned long arg)
{
struct vop_vdev *vdev = f->private_data;
struct vop_info *vi = vdev->vi;
void __user *argp = (void __user *)arg;
int ret;
switch (cmd) {
case MIC_VIRTIO_ADD_DEVICE:
{
struct mic_device_desc dd, *dd_config;
if (copy_from_user(&dd, ... | 42,020,854,998,596,270,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-5728 | Race condition in the vop_ioctl function in drivers/misc/mic/vop/vop_vringh.c in the MIC VOP driver in the Linux kernel before 4.6.1 allows local users to obtain sensitive information from kernel memory or cause a denial of service (memory corruption and system crash) by changing a certain header, aka a "double fetch" ... | https://nvd.nist.gov/vuln/detail/CVE-2016-5728 |
159,450 | linux | 9bf292bfca94694a721449e3fd752493856710f6 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9bf292bfca94694a721449e3fd752493856710f6 | misc: mic: Fix for double fetch security bug in VOP driver
The MIC VOP driver does two successive reads from user space to read a
variable length data structure. Kernel memory corruption can result if
the data structure changes between the two reads. This patch disallows
the chance of this happening.
Bugzilla: https:... | 0 | static long vop_ioctl(struct file *f, unsigned int cmd, unsigned long arg)
{
struct vop_vdev *vdev = f->private_data;
struct vop_info *vi = vdev->vi;
void __user *argp = (void __user *)arg;
int ret;
switch (cmd) {
case MIC_VIRTIO_ADD_DEVICE:
{
struct mic_device_desc dd, *dd_config;
if (copy_from_user(&dd, ... | 159,108,060,909,284,840,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-5728 | Race condition in the vop_ioctl function in drivers/misc/mic/vop/vop_vringh.c in the MIC VOP driver in the Linux kernel before 4.6.1 allows local users to obtain sensitive information from kernel memory or cause a denial of service (memory corruption and system crash) by changing a certain header, aka a "double fetch" ... | https://nvd.nist.gov/vuln/detail/CVE-2016-5728 |
1,910 | ImageMagick | 5511ef530576ed18fd636baa3bb4eda3d667665d | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/5511ef530576ed18fd636baa3bb4eda3d667665d | Add additional checks to DCM reader to prevent data-driven faults (bug report from Hanno Böck | 1 | static Image *ReadDCMImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
char
explicit_vr[MagickPathExtent],
implicit_vr[MagickPathExtent],
magick[MagickPathExtent],
photometric[MagickPathExtent];
DCMStreamInfo
*stream_info;
Image
*image;
int
*bluemap,
datum,
*gr... | 40,219,157,448,116,547,000,000,000,000,000,000,000 | dcm.c | 282,395,254,250,022,830,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-5689 | The DCM reader in ImageMagick before 6.9.4-5 and 7.x before 7.0.1-7 allows remote attackers to have unspecified impact by leveraging lack of NULL pointer checks. | https://nvd.nist.gov/vuln/detail/CVE-2016-5689 |
159,452 | ImageMagick | 5511ef530576ed18fd636baa3bb4eda3d667665d | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/5511ef530576ed18fd636baa3bb4eda3d667665d | Add additional checks to DCM reader to prevent data-driven faults (bug report from Hanno Böck | 0 | static Image *ReadDCMImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
char
explicit_vr[MagickPathExtent],
implicit_vr[MagickPathExtent],
magick[MagickPathExtent],
photometric[MagickPathExtent];
DCMStreamInfo
*stream_info;
Image
*image;
int
*bluemap,
datum,
*gr... | 211,362,297,982,966,370,000,000,000,000,000,000,000 | dcm.c | 66,138,389,563,764,950,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-5689 | The DCM reader in ImageMagick before 6.9.4-5 and 7.x before 7.0.1-7 allows remote attackers to have unspecified impact by leveraging lack of NULL pointer checks. | https://nvd.nist.gov/vuln/detail/CVE-2016-5689 |
1,914 | linux | aa93d1fee85c890a34f2510a310e55ee76a27848 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/aa93d1fee85c890a34f2510a310e55ee76a27848 | media: fix airspy usb probe error path
Fix a memory leak on probe error of the airspy usb device driver.
The problem is triggered when more than 64 usb devices register with
v4l2 of type VFL_TYPE_SDR or VFL_TYPE_SUBDEV.
The memory leak is caused by the probe function of the airspy driver
mishandeling errors and not ... | 1 | static int airspy_probe(struct usb_interface *intf,
const struct usb_device_id *id)
{
struct airspy *s;
int ret;
u8 u8tmp, buf[BUF_SIZE];
s = kzalloc(sizeof(struct airspy), GFP_KERNEL);
if (s == NULL) {
dev_err(&intf->dev, "Could not allocate memory for state\n");
return -ENOMEM;
}
mutex_init(&s->v4l2_lo... | 201,482,838,855,407,340,000,000,000,000,000,000,000 | airspy.c | 271,094,106,681,489,230,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-5400 | Memory leak in the airspy_probe function in drivers/media/usb/airspy/airspy.c in the airspy USB driver in the Linux kernel before 4.7 allows local users to cause a denial of service (memory consumption) via a crafted USB device that emulates many VFL_TYPE_SDR or VFL_TYPE_SUBDEV devices and performs many connect and dis... | https://nvd.nist.gov/vuln/detail/CVE-2016-5400 |
159,456 | linux | aa93d1fee85c890a34f2510a310e55ee76a27848 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/aa93d1fee85c890a34f2510a310e55ee76a27848 | media: fix airspy usb probe error path
Fix a memory leak on probe error of the airspy usb device driver.
The problem is triggered when more than 64 usb devices register with
v4l2 of type VFL_TYPE_SDR or VFL_TYPE_SUBDEV.
The memory leak is caused by the probe function of the airspy driver
mishandeling errors and not ... | 0 | static int airspy_probe(struct usb_interface *intf,
const struct usb_device_id *id)
{
struct airspy *s;
int ret;
u8 u8tmp, buf[BUF_SIZE];
s = kzalloc(sizeof(struct airspy), GFP_KERNEL);
if (s == NULL) {
dev_err(&intf->dev, "Could not allocate memory for state\n");
return -ENOMEM;
}
mutex_init(&s->v4l2_lo... | 222,049,493,822,913,680,000,000,000,000,000,000,000 | airspy.c | 65,310,941,262,248,360,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-5400 | Memory leak in the airspy_probe function in drivers/media/usb/airspy/airspy.c in the airspy USB driver in the Linux kernel before 4.7 allows local users to cause a denial of service (memory consumption) via a crafted USB device that emulates many VFL_TYPE_SDR or VFL_TYPE_SUBDEV devices and performs many connect and dis... | https://nvd.nist.gov/vuln/detail/CVE-2016-5400 |
1,919 | wireshark | 2c13e97d656c1c0ac4d76eb9d307664aae0e0cf7 | https://github.com/wireshark/wireshark | https://github.com/wireshark/wireshark/commit/2c13e97d656c1c0ac4d76eb9d307664aae0e0cf7 | The WTAP_ENCAP_ETHERNET dissector needs to be passed a struct eth_phdr.
We now require that. Make it so.
Bug: 12440
Change-Id: Iffee520976b013800699bde3c6092a3e86be0d76
Reviewed-on: https://code.wireshark.org/review/15424
Reviewed-by: Guy Harris <guy@alum.mit.edu> | 1 | dissect_pktap(tvbuff_t *tvb, packet_info *pinfo, proto_tree *tree)
{
proto_tree *pktap_tree = NULL;
proto_item *ti = NULL;
tvbuff_t *next_tvb;
int offset = 0;
guint32 pkt_len, rectype, dlt;
col_set_str(pinfo->cinfo, COL_PROTOCOL, "PKTAP");
col_clear(pinfo->cinfo, COL_INFO);
pkt_len = tvb_get_letohl(tvb,... | 60,167,683,222,163,160,000,000,000,000,000,000,000 | packet-pktap.c | 74,355,000,406,750,550,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-5358 | epan/dissectors/packet-pktap.c in the Ethernet dissector in Wireshark 2.x before 2.0.4 mishandles the packet-header data type, which allows remote attackers to cause a denial of service (application crash) via a crafted packet. | https://nvd.nist.gov/vuln/detail/CVE-2016-5358 |
159,461 | wireshark | 2c13e97d656c1c0ac4d76eb9d307664aae0e0cf7 | https://github.com/wireshark/wireshark | https://github.com/wireshark/wireshark/commit/2c13e97d656c1c0ac4d76eb9d307664aae0e0cf7 | The WTAP_ENCAP_ETHERNET dissector needs to be passed a struct eth_phdr.
We now require that. Make it so.
Bug: 12440
Change-Id: Iffee520976b013800699bde3c6092a3e86be0d76
Reviewed-on: https://code.wireshark.org/review/15424
Reviewed-by: Guy Harris <guy@alum.mit.edu> | 0 | dissect_pktap(tvbuff_t *tvb, packet_info *pinfo, proto_tree *tree)
{
proto_tree *pktap_tree = NULL;
proto_item *ti = NULL;
tvbuff_t *next_tvb;
int offset = 0;
guint32 pkt_len, rectype, dlt;
int wtap_encap;
struct eth_phdr eth;
void *phdr;
col_set_str(pinfo->cinfo, COL_PROTOCOL, "PKTAP");
col_clear(pinf... | 184,632,519,693,692,680,000,000,000,000,000,000,000 | packet-pktap.c | 234,697,794,125,425,000,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-5358 | epan/dissectors/packet-pktap.c in the Ethernet dissector in Wireshark 2.x before 2.0.4 mishandles the packet-header data type, which allows remote attackers to cause a denial of service (application crash) via a crafted packet. | https://nvd.nist.gov/vuln/detail/CVE-2016-5358 |
1,925 | wireshark | a66628e425db725df1ac52a3c573a03357060ddd | https://github.com/wireshark/wireshark | https://github.com/wireshark/wireshark/commit/a66628e425db725df1ac52a3c573a03357060ddd | Don't treat the packet length as unsigned.
The scanf family of functions are as annoyingly bad at handling unsigned
numbers as strtoul() is - both of them are perfectly willing to accept a
value beginning with a negative sign as an unsigned value. When using
strtoul(), you can compensate for this by explicitly checki... | 1 | parse_cosine_packet(FILE_T fh, struct wtap_pkthdr *phdr, Buffer *buf,
char *line, int *err, gchar **err_info)
{
union wtap_pseudo_header *pseudo_header = &phdr->pseudo_header;
int num_items_scanned;
int yy, mm, dd, hr, min, sec, csec;
guint pkt_len;
int pro, off, pri, rm, error;
guint code1, code2;
cha... | 775,128,632,240,788,800,000,000,000,000,000,000 | cosine.c | 260,698,406,841,229,670,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-5356 | wiretap/cosine.c in the CoSine file parser in Wireshark 1.12.x before 1.12.12 and 2.x before 2.0.4 mishandles sscanf unsigned-integer processing, which allows remote attackers to cause a denial of service (application crash) via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2016-5356 |
159,467 | wireshark | a66628e425db725df1ac52a3c573a03357060ddd | https://github.com/wireshark/wireshark | https://github.com/wireshark/wireshark/commit/a66628e425db725df1ac52a3c573a03357060ddd | Don't treat the packet length as unsigned.
The scanf family of functions are as annoyingly bad at handling unsigned
numbers as strtoul() is - both of them are perfectly willing to accept a
value beginning with a negative sign as an unsigned value. When using
strtoul(), you can compensate for this by explicitly checki... | 0 | parse_cosine_packet(FILE_T fh, struct wtap_pkthdr *phdr, Buffer *buf,
char *line, int *err, gchar **err_info)
{
union wtap_pseudo_header *pseudo_header = &phdr->pseudo_header;
int num_items_scanned;
int yy, mm, dd, hr, min, sec, csec, pkt_len;
int pro, off, pri, rm, error;
guint code1, code2;
char if_na... | 66,218,469,160,880,965,000,000,000,000,000,000,000 | cosine.c | 212,860,206,589,001,240,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-5356 | wiretap/cosine.c in the CoSine file parser in Wireshark 1.12.x before 1.12.12 and 2.x before 2.0.4 mishandles sscanf unsigned-integer processing, which allows remote attackers to cause a denial of service (application crash) via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2016-5356 |
1,926 | wireshark | 3270dfac43da861c714df76513456b46765ff47f | https://github.com/wireshark/wireshark | https://github.com/wireshark/wireshark/commit/3270dfac43da861c714df76513456b46765ff47f | Don't treat the packet length as unsigned.
The scanf family of functions are as annoyingly bad at handling unsigned
numbers as strtoul() is - both of them are perfectly willing to accept a
value beginning with a negative sign as an unsigned value. When using
strtoul(), you can compensate for this by explicitly checki... | 1 | parse_toshiba_packet(FILE_T fh, struct wtap_pkthdr *phdr, Buffer *buf,
int *err, gchar **err_info)
{
union wtap_pseudo_header *pseudo_header = &phdr->pseudo_header;
char line[TOSHIBA_LINE_LENGTH];
int num_items_scanned;
guint pkt_len;
int pktnum, hr, min, sec, csec;
char channel[10], direction[10];
int ... | 46,587,021,802,752,220,000,000,000,000,000,000,000 | toshiba.c | 331,447,668,869,948,600,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-5355 | wiretap/toshiba.c in the Toshiba file parser in Wireshark 1.12.x before 1.12.12 and 2.x before 2.0.4 mishandles sscanf unsigned-integer processing, which allows remote attackers to cause a denial of service (application crash) via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2016-5355 |
159,468 | wireshark | 3270dfac43da861c714df76513456b46765ff47f | https://github.com/wireshark/wireshark | https://github.com/wireshark/wireshark/commit/3270dfac43da861c714df76513456b46765ff47f | Don't treat the packet length as unsigned.
The scanf family of functions are as annoyingly bad at handling unsigned
numbers as strtoul() is - both of them are perfectly willing to accept a
value beginning with a negative sign as an unsigned value. When using
strtoul(), you can compensate for this by explicitly checki... | 0 | parse_toshiba_packet(FILE_T fh, struct wtap_pkthdr *phdr, Buffer *buf,
int *err, gchar **err_info)
{
union wtap_pseudo_header *pseudo_header = &phdr->pseudo_header;
char line[TOSHIBA_LINE_LENGTH];
int num_items_scanned;
int pkt_len, pktnum, hr, min, sec, csec;
char channel[10], direction[10];
int i, hex_... | 208,980,443,731,351,900,000,000,000,000,000,000,000 | toshiba.c | 294,680,502,710,844,670,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-5355 | wiretap/toshiba.c in the Toshiba file parser in Wireshark 1.12.x before 1.12.12 and 2.x before 2.0.4 mishandles sscanf unsigned-integer processing, which allows remote attackers to cause a denial of service (application crash) via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2016-5355 |
1,930 | wireshark | 7d7190695ce2ff269fdffb04e87139995cde21f4 | https://github.com/wireshark/wireshark | https://github.com/wireshark/wireshark/commit/7d7190695ce2ff269fdffb04e87139995cde21f4 | UMTS_FP: fix handling reserved C/T value
The spec puts the reserved value at 0xf but our internal table has 'unknown' at
0; since all the other values seem to be offset-by-one, just take the modulus
0xf to avoid running off the end of the table.
Bug: 12191
Change-Id: I83c8fb66797bbdee52a2246fb1eea6e37cbc7eb0
Reviewed... | 1 | fp_set_per_packet_inf_from_conv(umts_fp_conversation_info_t *p_conv_data,
tvbuff_t *tvb, packet_info *pinfo,
proto_tree *tree _U_)
{
fp_info *fpi;
guint8 tfi, c_t;
int offset = 0, i=0, j=0, num_tbs, chan, tb_size, tb_bit_off;
gboo... | 193,271,014,369,532,400,000,000,000,000,000,000,000 | packet-umts_fp.c | 301,117,539,260,110,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-5353 | epan/dissectors/packet-umts_fp.c in the UMTS FP dissector in Wireshark 1.12.x before 1.12.12 and 2.x before 2.0.4 mishandles the reserved C/T value, which allows remote attackers to cause a denial of service (application crash) via a crafted packet. | https://nvd.nist.gov/vuln/detail/CVE-2016-5353 |
159,472 | wireshark | 7d7190695ce2ff269fdffb04e87139995cde21f4 | https://github.com/wireshark/wireshark | https://github.com/wireshark/wireshark/commit/7d7190695ce2ff269fdffb04e87139995cde21f4 | UMTS_FP: fix handling reserved C/T value
The spec puts the reserved value at 0xf but our internal table has 'unknown' at
0; since all the other values seem to be offset-by-one, just take the modulus
0xf to avoid running off the end of the table.
Bug: 12191
Change-Id: I83c8fb66797bbdee52a2246fb1eea6e37cbc7eb0
Reviewed... | 0 | fp_set_per_packet_inf_from_conv(umts_fp_conversation_info_t *p_conv_data,
tvbuff_t *tvb, packet_info *pinfo,
proto_tree *tree _U_)
{
fp_info *fpi;
guint8 tfi, c_t;
int offset = 0, i=0, j=0, num_tbs, chan, tb_size, tb_bit_off;
gboo... | 54,155,045,409,348,430,000,000,000,000,000,000,000 | packet-umts_fp.c | 10,019,824,056,058,134,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-5353 | epan/dissectors/packet-umts_fp.c in the UMTS FP dissector in Wireshark 1.12.x before 1.12.12 and 2.x before 2.0.4 mishandles the reserved C/T value, which allows remote attackers to cause a denial of service (application crash) via a crafted packet. | https://nvd.nist.gov/vuln/detail/CVE-2016-5353 |
1,932 | wireshark | 9b0b20b8d5f8c9f7839d58ff6c5900f7e19283b4 | https://github.com/wireshark/wireshark | https://github.com/wireshark/wireshark/commit/9b0b20b8d5f8c9f7839d58ff6c5900f7e19283b4 | Make sure EAPOL body is big enough for a EAPOL_RSN_KEY.
A pointer to a EAPOL_RSN_KEY is set on the packet presuming the
whole EAPOL_RSN_KEY is there. That's not always the case for
fuzzed/malicious captures.
Bug: 11585
Change-Id: Ib94b8aceef444c7820e43b969596efdb8dbecccd
Reviewed-on: https://code.wireshark.org/revie... | 1 | static INT AirPDcapScanForKeys(
PAIRPDCAP_CONTEXT ctx,
const guint8 *data,
const guint mac_header_len,
const guint tot_len,
AIRPDCAP_SEC_ASSOCIATION_ID id
)
{
const UCHAR *addr;
guint bodyLength;
PAIRPDCAP_SEC_ASSOCIATION sta_sa;
PAIRPDCAP_SEC_ASSOCIATION sa;
guint offset = 0;
... | 240,174,644,621,715,030,000,000,000,000,000,000,000 | airpdcap.c | 178,616,951,686,308,540,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-5351 | epan/crypt/airpdcap.c in the IEEE 802.11 dissector in Wireshark 1.12.x before 1.12.12 and 2.x before 2.0.4 mishandles the lack of an EAPOL_RSN_KEY, which allows remote attackers to cause a denial of service (application crash) via a crafted packet. | https://nvd.nist.gov/vuln/detail/CVE-2016-5351 |
159,473 | wireshark | 9b0b20b8d5f8c9f7839d58ff6c5900f7e19283b4 | https://github.com/wireshark/wireshark | https://github.com/wireshark/wireshark/commit/9b0b20b8d5f8c9f7839d58ff6c5900f7e19283b4 | Make sure EAPOL body is big enough for a EAPOL_RSN_KEY.
A pointer to a EAPOL_RSN_KEY is set on the packet presuming the
whole EAPOL_RSN_KEY is there. That's not always the case for
fuzzed/malicious captures.
Bug: 11585
Change-Id: Ib94b8aceef444c7820e43b969596efdb8dbecccd
Reviewed-on: https://code.wireshark.org/revie... | 0 | static INT AirPDcapScanForKeys(
PAIRPDCAP_CONTEXT ctx,
const guint8 *data,
const guint mac_header_len,
const guint tot_len,
AIRPDCAP_SEC_ASSOCIATION_ID id
)
{
const UCHAR *addr;
guint bodyLength;
PAIRPDCAP_SEC_ASSOCIATION sta_sa;
PAIRPDCAP_SEC_ASSOCIATION sa;
guint offset = 0;
... | 11,647,175,576,244,844,000,000,000,000,000,000,000 | airpdcap.c | 92,912,043,498,906,000,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-5351 | epan/crypt/airpdcap.c in the IEEE 802.11 dissector in Wireshark 1.12.x before 1.12.12 and 2.x before 2.0.4 mishandles the lack of an EAPOL_RSN_KEY, which allows remote attackers to cause a denial of service (application crash) via a crafted packet. | https://nvd.nist.gov/vuln/detail/CVE-2016-5351 |
1,940 | libimobiledevice | df1f5c4d70d0c19ad40072f5246ca457e7f9849e | https://github.com/libimobiledevice/libimobiledevice | https://github.com/libimobiledevice/libimobiledevice/commit/df1f5c4d70d0c19ad40072f5246ca457e7f9849e | common: [security fix] Make sure sockets only listen locally | 1 | int socket_create(uint16_t port)
{
int sfd = -1;
int yes = 1;
#ifdef WIN32
WSADATA wsa_data;
if (!wsa_init) {
if (WSAStartup(MAKEWORD(2,2), &wsa_data) != ERROR_SUCCESS) {
fprintf(stderr, "WSAStartup failed!\n");
ExitProcess(-1);
}
wsa_init = 1;
}
#endif
struct sockaddr_in saddr;
if (0 > (sfd = socke... | 174,992,331,678,357,600,000,000,000,000,000,000,000 | socket.c | 5,143,455,029,250,239,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2016-5104 | The socket_create function in common/socket.c in libimobiledevice and libusbmuxd allows remote attackers to bypass intended access restrictions and communicate with services on iOS devices by connecting to an IPv4 TCP socket. | https://nvd.nist.gov/vuln/detail/CVE-2016-5104 |
159,481 | libimobiledevice | df1f5c4d70d0c19ad40072f5246ca457e7f9849e | https://github.com/libimobiledevice/libimobiledevice | https://github.com/libimobiledevice/libimobiledevice/commit/df1f5c4d70d0c19ad40072f5246ca457e7f9849e | common: [security fix] Make sure sockets only listen locally | 0 | int socket_create(uint16_t port)
{
int sfd = -1;
int yes = 1;
#ifdef WIN32
WSADATA wsa_data;
if (!wsa_init) {
if (WSAStartup(MAKEWORD(2,2), &wsa_data) != ERROR_SUCCESS) {
fprintf(stderr, "WSAStartup failed!\n");
ExitProcess(-1);
}
wsa_init = 1;
}
#endif
struct sockaddr_in saddr;
if (0 > (sfd = socke... | 207,382,081,564,168,270,000,000,000,000,000,000,000 | socket.c | 277,488,412,435,158,000,000,000,000,000,000,000,000 | [
"CWE-284"
] | CVE-2016-5104 | The socket_create function in common/socket.c in libimobiledevice and libusbmuxd allows remote attackers to bypass intended access restrictions and communicate with services on iOS devices by connecting to an IPv4 TCP socket. | https://nvd.nist.gov/vuln/detail/CVE-2016-5104 |
1,991 | linux | 45e093ae2830cd1264677d47ff9a95a71f5d9f9c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/45e093ae2830cd1264677d47ff9a95a71f5d9f9c | tipc: check nl sock before parsing nested attributes
Make sure the socket for which the user is listing publication exists
before parsing the socket netlink attributes.
Prior to this patch a call without any socket caused a NULL pointer
dereference in tipc_nl_publ_dump().
Tested-and-reported-by: Baozeng Ding <splovi... | 1 | int tipc_nl_publ_dump(struct sk_buff *skb, struct netlink_callback *cb)
{
int err;
u32 tsk_portid = cb->args[0];
u32 last_publ = cb->args[1];
u32 done = cb->args[2];
struct net *net = sock_net(skb->sk);
struct tipc_sock *tsk;
if (!tsk_portid) {
struct nlattr **attrs;
struct nlattr *sock[TIPC_NLA_SOCK_MAX + ... | 109,108,179,952,697,830,000,000,000,000,000,000,000 | socket.c | 147,330,032,818,011,570,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-4951 | The tipc_nl_publ_dump function in net/tipc/socket.c in the Linux kernel through 4.6 does not verify socket existence, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via a dumpit operation. | https://nvd.nist.gov/vuln/detail/CVE-2016-4951 |
159,501 | linux | 45e093ae2830cd1264677d47ff9a95a71f5d9f9c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/45e093ae2830cd1264677d47ff9a95a71f5d9f9c | tipc: check nl sock before parsing nested attributes
Make sure the socket for which the user is listing publication exists
before parsing the socket netlink attributes.
Prior to this patch a call without any socket caused a NULL pointer
dereference in tipc_nl_publ_dump().
Tested-and-reported-by: Baozeng Ding <splovi... | 0 | int tipc_nl_publ_dump(struct sk_buff *skb, struct netlink_callback *cb)
{
int err;
u32 tsk_portid = cb->args[0];
u32 last_publ = cb->args[1];
u32 done = cb->args[2];
struct net *net = sock_net(skb->sk);
struct tipc_sock *tsk;
if (!tsk_portid) {
struct nlattr **attrs;
struct nlattr *sock[TIPC_NLA_SOCK_MAX + ... | 91,971,988,071,072,530,000,000,000,000,000,000,000 | socket.c | 239,572,743,579,676,820,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-4951 | The tipc_nl_publ_dump function in net/tipc/socket.c in the Linux kernel through 4.6 does not verify socket existence, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via a dumpit operation. | https://nvd.nist.gov/vuln/detail/CVE-2016-4951 |
1,992 | linux | 99d825822eade8d827a1817357cbf3f889a552d6 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/99d825822eade8d827a1817357cbf3f889a552d6 | get_rock_ridge_filename(): handle malformed NM entries
Payloads of NM entries are not supposed to contain NUL. When we run
into such, only the part prior to the first NUL goes into the
concatenation (i.e. the directory entry name being encoded by a bunch
of NM entries). We do stop when the amount collected so far + ... | 1 | int get_rock_ridge_filename(struct iso_directory_record *de,
char *retname, struct inode *inode)
{
struct rock_state rs;
struct rock_ridge *rr;
int sig;
int retnamlen = 0;
int truncate = 0;
int ret = 0;
if (!ISOFS_SB(inode->i_sb)->s_rock)
return 0;
*retname = 0;
init_rock_state(&rs, inode);
s... | 93,758,422,006,208,340,000,000,000,000,000,000,000 | rock.c | 282,024,907,067,004,600,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2016-4913 | The get_rock_ridge_filename function in fs/isofs/rock.c in the Linux kernel before 4.5.5 mishandles NM (aka alternate name) entries containing \0 characters, which allows local users to obtain sensitive information from kernel memory or possibly have unspecified other impact via a crafted isofs filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2016-4913 |
159,502 | linux | 99d825822eade8d827a1817357cbf3f889a552d6 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/99d825822eade8d827a1817357cbf3f889a552d6 | get_rock_ridge_filename(): handle malformed NM entries
Payloads of NM entries are not supposed to contain NUL. When we run
into such, only the part prior to the first NUL goes into the
concatenation (i.e. the directory entry name being encoded by a bunch
of NM entries). We do stop when the amount collected so far + ... | 0 | int get_rock_ridge_filename(struct iso_directory_record *de,
char *retname, struct inode *inode)
{
struct rock_state rs;
struct rock_ridge *rr;
int sig;
int retnamlen = 0;
int truncate = 0;
int ret = 0;
char *p;
int len;
if (!ISOFS_SB(inode->i_sb)->s_rock)
return 0;
*retname = 0;
init_rock_s... | 120,121,340,213,572,290,000,000,000,000,000,000,000 | rock.c | 211,336,850,948,325,520,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2016-4913 | The get_rock_ridge_filename function in fs/isofs/rock.c in the Linux kernel before 4.5.5 mishandles NM (aka alternate name) entries containing \0 characters, which allows local users to obtain sensitive information from kernel memory or possibly have unspecified other impact via a crafted isofs filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2016-4913 |
1,996 | linux | 1f461dcdd296eecedaffffc6bae2bfa90bd7eb89 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1f461dcdd296eecedaffffc6bae2bfa90bd7eb89 | ppp: take reference on channels netns
Let channels hold a reference on their network namespace.
Some channel types, like ppp_async and ppp_synctty, can have their
userspace controller running in a different namespace. Therefore they
can't rely on them to preclude their netns from being removed from
under them.
======... | 1 | int ppp_register_net_channel(struct net *net, struct ppp_channel *chan)
{
struct channel *pch;
struct ppp_net *pn;
pch = kzalloc(sizeof(struct channel), GFP_KERNEL);
if (!pch)
return -ENOMEM;
pn = ppp_pernet(net);
pch->ppp = NULL;
pch->chan = chan;
pch->chan_net = net;
chan->ppp = pch;
init_ppp_file... | 200,851,677,246,187,520,000,000,000,000,000,000,000 | ppp_generic.c | 33,074,513,998,217,310,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2016-4805 | Use-after-free vulnerability in drivers/net/ppp/ppp_generic.c in the Linux kernel before 4.5.2 allows local users to cause a denial of service (memory corruption and system crash, or spinlock) or possibly have unspecified other impact by removing a network namespace, related to the ppp_register_net_channel and ppp_unre... | https://nvd.nist.gov/vuln/detail/CVE-2016-4805 |
159,506 | linux | 1f461dcdd296eecedaffffc6bae2bfa90bd7eb89 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1f461dcdd296eecedaffffc6bae2bfa90bd7eb89 | ppp: take reference on channels netns
Let channels hold a reference on their network namespace.
Some channel types, like ppp_async and ppp_synctty, can have their
userspace controller running in a different namespace. Therefore they
can't rely on them to preclude their netns from being removed from
under them.
======... | 0 | int ppp_register_net_channel(struct net *net, struct ppp_channel *chan)
{
struct channel *pch;
struct ppp_net *pn;
pch = kzalloc(sizeof(struct channel), GFP_KERNEL);
if (!pch)
return -ENOMEM;
pn = ppp_pernet(net);
pch->ppp = NULL;
pch->chan = chan;
pch->chan_net = get_net(net);
chan->ppp = pch;
init... | 121,789,139,006,319,640,000,000,000,000,000,000,000 | ppp_generic.c | 10,681,796,957,529,726,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2016-4805 | Use-after-free vulnerability in drivers/net/ppp/ppp_generic.c in the Linux kernel before 4.5.2 allows local users to cause a denial of service (memory corruption and system crash, or spinlock) or possibly have unspecified other impact by removing a network namespace, related to the ppp_register_net_channel and ppp_unre... | https://nvd.nist.gov/vuln/detail/CVE-2016-4805 |
9,372 | linux | 1f461dcdd296eecedaffffc6bae2bfa90bd7eb89 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1f461dcdd296eecedaffffc6bae2bfa90bd7eb89 | ppp: take reference on channels netns
Let channels hold a reference on their network namespace.
Some channel types, like ppp_async and ppp_synctty, can have their
userspace controller running in a different namespace. Therefore they
can't rely on them to preclude their netns from being removed from
under them.
======... | 1 | ppp_unregister_channel(struct ppp_channel *chan)
{
struct channel *pch = chan->ppp;
struct ppp_net *pn;
if (!pch)
return; /* should never happen */
chan->ppp = NULL;
/*
* This ensures that we have returned from any calls into the
* the channel's start_xmit or ioctl routine before we proceed.
*/
down_w... | 219,099,927,735,173,400,000,000,000,000,000,000,000 | ppp_generic.c | 33,074,513,998,217,310,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2016-4805 | Use-after-free vulnerability in drivers/net/ppp/ppp_generic.c in the Linux kernel before 4.5.2 allows local users to cause a denial of service (memory corruption and system crash, or spinlock) or possibly have unspecified other impact by removing a network namespace, related to the ppp_register_net_channel and ppp_unre... | https://nvd.nist.gov/vuln/detail/CVE-2016-4805 |
184,477 | linux | 1f461dcdd296eecedaffffc6bae2bfa90bd7eb89 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1f461dcdd296eecedaffffc6bae2bfa90bd7eb89 | ppp: take reference on channels netns
Let channels hold a reference on their network namespace.
Some channel types, like ppp_async and ppp_synctty, can have their
userspace controller running in a different namespace. Therefore they
can't rely on them to preclude their netns from being removed from
under them.
======... | 0 | ppp_unregister_channel(struct ppp_channel *chan)
{
struct channel *pch = chan->ppp;
struct ppp_net *pn;
if (!pch)
return; /* should never happen */
chan->ppp = NULL;
/*
* This ensures that we have returned from any calls into the
* the channel's start_xmit or ioctl routine before we proceed.
*/
down_w... | 298,841,472,791,072,400,000,000,000,000,000,000,000 | ppp_generic.c | 10,681,796,957,529,726,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2016-4805 | Use-after-free vulnerability in drivers/net/ppp/ppp_generic.c in the Linux kernel before 4.5.2 allows local users to cause a denial of service (memory corruption and system crash, or spinlock) or possibly have unspecified other impact by removing a network namespace, related to the ppp_register_net_channel and ppp_unre... | https://nvd.nist.gov/vuln/detail/CVE-2016-4805 |
1,998 | dosfstools | e8eff147e9da1185f9afd5b25948153a3b97cf52 | https://github.com/dosfstools/dosfstools | https://github.com/dosfstools/dosfstools/commit/e8eff147e9da1185f9afd5b25948153a3b97cf52 | read_boot(): Handle excessive FAT size specifications
The variable used for storing the FAT size (in bytes) was an unsigned
int. Since the size in sectors read from the BPB was not sufficiently
checked, this could end up being zero after multiplying it with the
sector size while some offsets still stayed excessive. Ul... | 1 | void read_boot(DOS_FS * fs)
{
struct boot_sector b;
unsigned total_sectors;
unsigned short logical_sector_size, sectors;
unsigned fat_length;
unsigned total_fat_entries;
off_t data_size;
fs_read(0, sizeof(b), &b);
logical_sector_size = GET_UNALIGNED_W(b.sector_size);
if (!logi... | 186,977,352,067,923,180,000,000,000,000,000,000,000 | boot.c | 197,145,767,489,226,020,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-4804 | The read_boot function in boot.c in dosfstools before 4.0 allows attackers to cause a denial of service (crash) via a crafted filesystem, which triggers a heap-based buffer overflow in the (1) read_fat function or an out-of-bounds heap read in (2) get_fat function. | https://nvd.nist.gov/vuln/detail/CVE-2016-4804 |
159,508 | dosfstools | e8eff147e9da1185f9afd5b25948153a3b97cf52 | https://github.com/dosfstools/dosfstools | https://github.com/dosfstools/dosfstools/commit/e8eff147e9da1185f9afd5b25948153a3b97cf52 | read_boot(): Handle excessive FAT size specifications
The variable used for storing the FAT size (in bytes) was an unsigned
int. Since the size in sectors read from the BPB was not sufficiently
checked, this could end up being zero after multiplying it with the
sector size while some offsets still stayed excessive. Ul... | 0 | void read_boot(DOS_FS * fs)
{
struct boot_sector b;
unsigned total_sectors;
unsigned short logical_sector_size, sectors;
off_t fat_length;
unsigned total_fat_entries;
off_t data_size;
fs_read(0, sizeof(b), &b);
logical_sector_size = GET_UNALIGNED_W(b.sector_size);
if (!logical... | 219,388,838,320,668,530,000,000,000,000,000,000,000 | boot.c | 171,909,008,388,992,030,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-4804 | The read_boot function in boot.c in dosfstools before 4.0 allows attackers to cause a denial of service (crash) via a crafted filesystem, which triggers a heap-based buffer overflow in the (1) read_fat function or an out-of-bounds heap read in (2) get_fat function. | https://nvd.nist.gov/vuln/detail/CVE-2016-4804 |
2,001 | linux | 79e48650320e6fba48369fccf13fd045315b19b8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/79e48650320e6fba48369fccf13fd045315b19b8 | net: fix a kernel infoleak in x25 module
Stack object "dte_facilities" is allocated in x25_rx_call_request(),
which is supposed to be initialized in x25_negotiate_facilities.
However, 5 fields (8 bytes in total) are not initialized. This
object is then copied to userland via copy_to_user, thus infoleak
occurs.
Signed... | 1 | int x25_negotiate_facilities(struct sk_buff *skb, struct sock *sk,
struct x25_facilities *new, struct x25_dte_facilities *dte)
{
struct x25_sock *x25 = x25_sk(sk);
struct x25_facilities *ours = &x25->facilities;
struct x25_facilities theirs;
int len;
memset(&theirs, 0, sizeof(theirs));
memcpy(new, ours, siz... | 288,890,073,918,554,100,000,000,000,000,000,000,000 | x25_facilities.c | 175,536,494,937,069,540,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2016-4580 | The x25_negotiate_facilities function in net/x25/x25_facilities.c in the Linux kernel before 4.5.5 does not properly initialize a certain data structure, which allows attackers to obtain sensitive information from kernel stack memory via an X.25 Call Request. | https://nvd.nist.gov/vuln/detail/CVE-2016-4580 |
159,509 | linux | 79e48650320e6fba48369fccf13fd045315b19b8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/79e48650320e6fba48369fccf13fd045315b19b8 | net: fix a kernel infoleak in x25 module
Stack object "dte_facilities" is allocated in x25_rx_call_request(),
which is supposed to be initialized in x25_negotiate_facilities.
However, 5 fields (8 bytes in total) are not initialized. This
object is then copied to userland via copy_to_user, thus infoleak
occurs.
Signed... | 0 | int x25_negotiate_facilities(struct sk_buff *skb, struct sock *sk,
struct x25_facilities *new, struct x25_dte_facilities *dte)
{
struct x25_sock *x25 = x25_sk(sk);
struct x25_facilities *ours = &x25->facilities;
struct x25_facilities theirs;
int len;
memset(&theirs, 0, sizeof(theirs));
memcpy(new, ours, siz... | 23,683,212,855,450,430,000,000,000,000,000,000,000 | x25_facilities.c | 30,946,152,525,161,040,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2016-4580 | The x25_negotiate_facilities function in net/x25/x25_facilities.c in the Linux kernel before 4.5.5 does not properly initialize a certain data structure, which allows attackers to obtain sensitive information from kernel stack memory via an X.25 Call Request. | https://nvd.nist.gov/vuln/detail/CVE-2016-4580 |
2,010 | ImageMagick | 726812fa2fa7ce16bcf58f6e115f65427a1c0950 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/726812fa2fa7ce16bcf58f6e115f65427a1c0950 | Prevent buffer overflow in magick/draw.c | 1 | static MagickBooleanType DrawDashPolygon(const DrawInfo *draw_info,
const PrimitiveInfo *primitive_info,Image *image,ExceptionInfo *exception)
{
DrawInfo
*clone_info;
double
length,
maximum_length,
offset,
scale,
total_length;
MagickStatusType
status;
PrimitiveInfo
*dash_pol... | 278,418,562,021,844,360,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-4564 | The DrawImage function in MagickCore/draw.c in ImageMagick before 6.9.4-0 and 7.x before 7.0.1-2 makes an incorrect function call in attempting to locate the next token, which allows remote attackers to cause a denial of service (buffer overflow and application crash) or possibly have unspecified other impact via a cra... | https://nvd.nist.gov/vuln/detail/CVE-2016-4564 |
159,517 | ImageMagick | 726812fa2fa7ce16bcf58f6e115f65427a1c0950 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/726812fa2fa7ce16bcf58f6e115f65427a1c0950 | Prevent buffer overflow in magick/draw.c | 0 | static MagickBooleanType DrawDashPolygon(const DrawInfo *draw_info,
const PrimitiveInfo *primitive_info,Image *image,ExceptionInfo *exception)
{
DrawInfo
*clone_info;
double
length,
maximum_length,
offset,
scale,
total_length;
MagickStatusType
status;
PrimitiveInfo
*dash_pol... | 248,351,437,847,617,330,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-4564 | The DrawImage function in MagickCore/draw.c in ImageMagick before 6.9.4-0 and 7.x before 7.0.1-2 makes an incorrect function call in attempting to locate the next token, which allows remote attackers to cause a denial of service (buffer overflow and application crash) or possibly have unspecified other impact via a cra... | https://nvd.nist.gov/vuln/detail/CVE-2016-4564 |
2,011 | ImageMagick | 726812fa2fa7ce16bcf58f6e115f65427a1c0950 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/726812fa2fa7ce16bcf58f6e115f65427a1c0950 | Prevent buffer overflow in magick/draw.c | 1 | MagickExport MagickBooleanType DrawImage(Image *image,const DrawInfo *draw_info,
ExceptionInfo *exception)
{
#define RenderImageTag "Render/Image"
AffineMatrix
affine,
current;
char
keyword[MagickPathExtent],
geometry[MagickPathExtent],
pattern[MagickPathExtent],
*primitive,
*token;... | 214,572,375,985,539,270,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-4564 | The DrawImage function in MagickCore/draw.c in ImageMagick before 6.9.4-0 and 7.x before 7.0.1-2 makes an incorrect function call in attempting to locate the next token, which allows remote attackers to cause a denial of service (buffer overflow and application crash) or possibly have unspecified other impact via a cra... | https://nvd.nist.gov/vuln/detail/CVE-2016-4564 |
159,518 | ImageMagick | 726812fa2fa7ce16bcf58f6e115f65427a1c0950 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/726812fa2fa7ce16bcf58f6e115f65427a1c0950 | Prevent buffer overflow in magick/draw.c | 0 | MagickExport MagickBooleanType DrawImage(Image *image,const DrawInfo *draw_info,
ExceptionInfo *exception)
{
#define RenderImageTag "Render/Image"
AffineMatrix
affine,
current;
char
keyword[MagickPathExtent],
geometry[MagickPathExtent],
pattern[MagickPathExtent],
*primitive,
*token;... | 250,012,492,941,036,550,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-4564 | The DrawImage function in MagickCore/draw.c in ImageMagick before 6.9.4-0 and 7.x before 7.0.1-2 makes an incorrect function call in attempting to locate the next token, which allows remote attackers to cause a denial of service (buffer overflow and application crash) or possibly have unspecified other impact via a cra... | https://nvd.nist.gov/vuln/detail/CVE-2016-4564 |
2,014 | ImageMagick | 726812fa2fa7ce16bcf58f6e115f65427a1c0950 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/726812fa2fa7ce16bcf58f6e115f65427a1c0950 | Prevent buffer overflow in magick/draw.c | 1 | static PrimitiveInfo *TraceStrokePolygon(const DrawInfo *draw_info,
const PrimitiveInfo *primitive_info)
{
typedef struct _LineSegment
{
double
p,
q;
} LineSegment;
LineSegment
dx,
dy,
inverse_slope,
slope,
theta;
MagickBooleanType
closed_path;
double
delta_t... | 315,690,379,769,147,360,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-4564 | The DrawImage function in MagickCore/draw.c in ImageMagick before 6.9.4-0 and 7.x before 7.0.1-2 makes an incorrect function call in attempting to locate the next token, which allows remote attackers to cause a denial of service (buffer overflow and application crash) or possibly have unspecified other impact via a cra... | https://nvd.nist.gov/vuln/detail/CVE-2016-4564 |
159,521 | ImageMagick | 726812fa2fa7ce16bcf58f6e115f65427a1c0950 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/726812fa2fa7ce16bcf58f6e115f65427a1c0950 | Prevent buffer overflow in magick/draw.c | 0 | static PrimitiveInfo *TraceStrokePolygon(const DrawInfo *draw_info,
const PrimitiveInfo *primitive_info)
{
typedef struct _LineSegment
{
double
p,
q;
} LineSegment;
LineSegment
dx,
dy,
inverse_slope,
slope,
theta;
MagickBooleanType
closed_path;
double
delta_t... | 130,910,046,289,997,410,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-4564 | The DrawImage function in MagickCore/draw.c in ImageMagick before 6.9.4-0 and 7.x before 7.0.1-2 makes an incorrect function call in attempting to locate the next token, which allows remote attackers to cause a denial of service (buffer overflow and application crash) or possibly have unspecified other impact via a cra... | https://nvd.nist.gov/vuln/detail/CVE-2016-4564 |
2,023 | linux | 681fef8380eb818c0b845fca5d2ab1dcbab114ee | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/681fef8380eb818c0b845fca5d2ab1dcbab114ee | USB: usbfs: fix potential infoleak in devio
The stack object “ci” has a total size of 8 bytes. Its last 3 bytes
are padding bytes which are not initialized and leaked to userland
via “copy_to_user”.
Signed-off-by: Kangjie Lu <kjlu@gatech.edu>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 1 | static int proc_connectinfo(struct usb_dev_state *ps, void __user *arg)
{
struct usbdevfs_connectinfo ci = {
.devnum = ps->dev->devnum,
.slow = ps->dev->speed == USB_SPEED_LOW
};
if (copy_to_user(arg, &ci, sizeof(ci)))
return -EFAULT;
return 0;
}
| 94,713,218,675,784,140,000,000,000,000,000,000,000 | devio.c | 150,665,955,136,899,330,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2016-4482 | The proc_connectinfo function in drivers/usb/core/devio.c in the Linux kernel through 4.6 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel stack memory via a crafted USBDEVFS_CONNECTINFO ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2016-4482 |
159,529 | linux | 681fef8380eb818c0b845fca5d2ab1dcbab114ee | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/681fef8380eb818c0b845fca5d2ab1dcbab114ee | USB: usbfs: fix potential infoleak in devio
The stack object “ci” has a total size of 8 bytes. Its last 3 bytes
are padding bytes which are not initialized and leaked to userland
via “copy_to_user”.
Signed-off-by: Kangjie Lu <kjlu@gatech.edu>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 0 | static int proc_connectinfo(struct usb_dev_state *ps, void __user *arg)
{
struct usbdevfs_connectinfo ci;
memset(&ci, 0, sizeof(ci));
ci.devnum = ps->dev->devnum;
ci.slow = ps->dev->speed == USB_SPEED_LOW;
if (copy_to_user(arg, &ci, sizeof(ci)))
return -EFAULT;
return 0;
}
| 7,412,314,399,009,915,000,000,000,000,000,000,000 | devio.c | 298,543,626,569,910,560,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2016-4482 | The proc_connectinfo function in drivers/usb/core/devio.c in the Linux kernel through 4.6 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel stack memory via a crafted USBDEVFS_CONNECTINFO ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2016-4482 |
2,024 | atheme | 87580d767868360d2fed503980129504da84b63e | https://github.com/atheme/atheme | https://github.com/atheme/atheme/commit/87580d767868360d2fed503980129504da84b63e | Do not copy more bytes than were allocated | 1 | void xmlrpc_char_encode(char *outbuffer, const char *s1)
{
long unsigned int i;
unsigned char c;
char buf2[15];
mowgli_string_t *s = mowgli_string_create();
*buf2 = '\0';
*outbuffer = '\0';
if ((!(s1) || (*(s1) == '\0')))
{
return;
}
for (i = 0; s1[i] != '\0'; i++)
{
c = s1[i];
if (c > 127)
{
sn... | 43,536,472,075,997,620,000,000,000,000,000,000,000 | xmlrpclib.c | 209,647,623,324,171,000,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-4478 | Buffer overflow in the xmlrpc_char_encode function in modules/transport/xmlrpc/xmlrpclib.c in Atheme before 7.2.7 allows remote attackers to cause a denial of service via vectors related to XMLRPC response encoding. | https://nvd.nist.gov/vuln/detail/CVE-2016-4478 |
159,530 | atheme | 87580d767868360d2fed503980129504da84b63e | https://github.com/atheme/atheme | https://github.com/atheme/atheme/commit/87580d767868360d2fed503980129504da84b63e | Do not copy more bytes than were allocated | 0 | void xmlrpc_char_encode(char *outbuffer, const char *s1)
{
long unsigned int i;
unsigned char c;
char buf2[15];
mowgli_string_t *s = mowgli_string_create();
*buf2 = '\0';
*outbuffer = '\0';
if ((!(s1) || (*(s1) == '\0')))
{
return;
}
for (i = 0; s1[i] != '\0'; i++)
{
c = s1[i];
if (c > 127)
{
sn... | 49,972,677,404,573,070,000,000,000,000,000,000,000 | xmlrpclib.c | 253,384,204,368,629,760,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-4478 | Buffer overflow in the xmlrpc_char_encode function in modules/transport/xmlrpc/xmlrpclib.c in Atheme before 7.2.7 allows remote attackers to cause a denial of service via vectors related to XMLRPC response encoding. | https://nvd.nist.gov/vuln/detail/CVE-2016-4478 |
2,066 | iperf | 91f2fa59e8ed80dfbf400add0164ee0e508e412a | https://github.com/esnet/iperf | https://github.com/esnet/iperf/commit/91f2fa59e8ed80dfbf400add0164ee0e508e412a | Fix a buffer overflow / heap corruption issue that could occur if a
malformed JSON string was passed on the control channel. This issue,
present in the cJSON library, was already fixed upstream, so was
addressed here in iperf3 by importing a newer version of cJSON (plus
local ESnet modifications).
Discovered and repo... | 1 | static const char *parse_string( cJSON *item, const char *str )
{
const char *ptr = str + 1;
char *ptr2;
char *out;
int len = 0;
unsigned uc, uc2;
if ( *str != '\"' ) {
/* Not a string! */
ep = str;
return 0;
}
/* Skip escaped quotes. */
while ( *ptr != '\"' && *ptr && ++len )
if ( *ptr++ == '\\' )... | 202,681,723,794,535,540,000,000,000,000,000,000,000 | cjson.c | 211,459,362,401,629,130,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-4303 | The parse_string function in cjson.c in the cJSON library mishandles UTF8/16 strings, which allows remote attackers to cause a denial of service (crash) or execute arbitrary code via a non-hex character in a JSON string, which triggers a heap-based buffer overflow. | https://nvd.nist.gov/vuln/detail/CVE-2016-4303 |
159,570 | iperf | 91f2fa59e8ed80dfbf400add0164ee0e508e412a | https://github.com/esnet/iperf | https://github.com/esnet/iperf/commit/91f2fa59e8ed80dfbf400add0164ee0e508e412a | Fix a buffer overflow / heap corruption issue that could occur if a
malformed JSON string was passed on the control channel. This issue,
present in the cJSON library, was already fixed upstream, so was
addressed here in iperf3 by importing a newer version of cJSON (plus
local ESnet modifications).
Discovered and repo... | 0 | static const char *parse_string( cJSON *item, const char *str )
static const char *parse_string(cJSON *item,const char *str,const char **ep)
{
const char *ptr=str+1,*end_ptr=str+1;char *ptr2;char *out;int len=0;unsigned uc,uc2;
if (*str!='\"') {*ep=str;return 0;} /* not a string! */
while (*end_ptr!='\"' && *end... | 72,138,985,393,442,700,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-4303 | The parse_string function in cjson.c in the cJSON library mishandles UTF8/16 strings, which allows remote attackers to cause a denial of service (crash) or execute arbitrary code via a non-hex character in a JSON string, which triggers a heap-based buffer overflow. | https://nvd.nist.gov/vuln/detail/CVE-2016-4303 |
2,078 | libarchive | a550daeecf6bc689ade371349892ea17b5b97c77 | https://github.com/libarchive/libarchive | https://github.com/libarchive/libarchive/commit/a550daeecf6bc689ade371349892ea17b5b97c77 | Fix libarchive/archive_read_support_format_mtree.c:1388:11: error: array subscript is above array bounds | 1 | parse_device(dev_t *pdev, struct archive *a, char *val)
{
#define MAX_PACK_ARGS 3
unsigned long numbers[MAX_PACK_ARGS];
char *p, *dev;
int argc;
pack_t *pack;
dev_t result;
const char *error = NULL;
memset(pdev, 0, sizeof(*pdev));
if ((dev = strchr(val, ',')) != NULL) {
/*
* Device's major/minor are given... | 140,177,069,250,601,300,000,000,000,000,000,000,000 | archive_read_support_format_mtree.c | 289,329,355,082,132,950,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-4301 | Stack-based buffer overflow in the parse_device function in archive_read_support_format_mtree.c in libarchive before 3.2.1 allows remote attackers to execute arbitrary code via a crafted mtree file. | https://nvd.nist.gov/vuln/detail/CVE-2016-4301 |
159,581 | libarchive | a550daeecf6bc689ade371349892ea17b5b97c77 | https://github.com/libarchive/libarchive | https://github.com/libarchive/libarchive/commit/a550daeecf6bc689ade371349892ea17b5b97c77 | Fix libarchive/archive_read_support_format_mtree.c:1388:11: error: array subscript is above array bounds | 0 | parse_device(dev_t *pdev, struct archive *a, char *val)
{
#define MAX_PACK_ARGS 3
unsigned long numbers[MAX_PACK_ARGS];
char *p, *dev;
int argc;
pack_t *pack;
dev_t result;
const char *error = NULL;
memset(pdev, 0, sizeof(*pdev));
if ((dev = strchr(val, ',')) != NULL) {
/*
* Device's major/minor are given... | 137,248,843,602,913,370,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-4301 | Stack-based buffer overflow in the parse_device function in archive_read_support_format_mtree.c in libarchive before 3.2.1 allows remote attackers to execute arbitrary code via a crafted mtree file. | https://nvd.nist.gov/vuln/detail/CVE-2016-4301 |
2,080 | linux | b348d7dddb6c4fbfc810b7a0626e8ec9e29f7cbb | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b348d7dddb6c4fbfc810b7a0626e8ec9e29f7cbb | USB: usbip: fix potential out-of-bounds write
Fix potential out-of-bounds write to urb->transfer_buffer
usbip handles network communication directly in the kernel. When receiving a
packet from its peer, usbip code parses headers according to protocol. As
part of this parsing urb->actual_length is filled. Since the inp... | 1 | int usbip_recv_xbuff(struct usbip_device *ud, struct urb *urb)
{
int ret;
int size;
if (ud->side == USBIP_STUB) {
/* the direction of urb must be OUT. */
if (usb_pipein(urb->pipe))
return 0;
size = urb->transfer_buffer_length;
} else {
/* the direction of urb must be IN. */
if (usb_pipeout(urb->pipe)... | 169,401,871,138,519,960,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-3955 | The usbip_recv_xbuff function in drivers/usb/usbip/usbip_common.c in the Linux kernel before 4.5.3 allows remote attackers to cause a denial of service (out-of-bounds write) or possibly have unspecified other impact via a crafted length value in a USB/IP packet. | https://nvd.nist.gov/vuln/detail/CVE-2016-3955 |
159,582 | linux | b348d7dddb6c4fbfc810b7a0626e8ec9e29f7cbb | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b348d7dddb6c4fbfc810b7a0626e8ec9e29f7cbb | USB: usbip: fix potential out-of-bounds write
Fix potential out-of-bounds write to urb->transfer_buffer
usbip handles network communication directly in the kernel. When receiving a
packet from its peer, usbip code parses headers according to protocol. As
part of this parsing urb->actual_length is filled. Since the inp... | 0 | int usbip_recv_xbuff(struct usbip_device *ud, struct urb *urb)
{
int ret;
int size;
if (ud->side == USBIP_STUB) {
/* the direction of urb must be OUT. */
if (usb_pipein(urb->pipe))
return 0;
size = urb->transfer_buffer_length;
} else {
/* the direction of urb must be IN. */
if (usb_pipeout(urb->pipe)... | 282,520,257,578,694,800,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-3955 | The usbip_recv_xbuff function in drivers/usb/usbip/usbip_common.c in the Linux kernel before 4.5.3 allows remote attackers to cause a denial of service (out-of-bounds write) or possibly have unspecified other impact via a crafted length value in a USB/IP packet. | https://nvd.nist.gov/vuln/detail/CVE-2016-3955 |
2,081 | linux | 4d06dd537f95683aba3651098ae288b7cbff8274 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4d06dd537f95683aba3651098ae288b7cbff8274 | cdc_ncm: do not call usbnet_link_change from cdc_ncm_bind
usbnet_link_change will call schedule_work and should be
avoided if bind is failing. Otherwise we will end up with
scheduled work referring to a netdev which has gone away.
Instead of making the call conditional, we can just defer
it to usbnet_probe, using the... | 1 | static int cdc_ncm_bind(struct usbnet *dev, struct usb_interface *intf)
{
int ret;
/* MBIM backwards compatible function? */
if (cdc_ncm_select_altsetting(intf) != CDC_NCM_COMM_ALTSETTING_NCM)
return -ENODEV;
/* The NCM data altsetting is fixed, so we hard-coded it.
* Additionally, generic NCM devices ar... | 286,704,641,831,086,000,000,000,000,000,000,000,000 | cdc_ncm.c | 107,934,168,350,224,250,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2016-3951 | Double free vulnerability in drivers/net/usb/cdc_ncm.c in the Linux kernel before 4.5 allows physically proximate attackers to cause a denial of service (system crash) or possibly have unspecified other impact by inserting a USB device with an invalid USB descriptor. | https://nvd.nist.gov/vuln/detail/CVE-2016-3951 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.