cvelist/2017/1000xxx/CVE-2017-1000111.json

{
    "CVE_data_meta": {
        "ASSIGNER": "cve@mitre.org",
        "DATE_ASSIGNED": "2017-08-22T17:29:33.324350",
        "ID": "CVE-2017-1000111",
        "REQUESTER": "willemdebruijn.kernel@gmail.com",
        "STATE": "PUBLIC"
    },
    "affects": {
        "vendor": {
            "vendor_data": [
                {
                    "product": {
                        "product_data": [
                            {
                                "product_name": "n/a",
                                "version": {
                                    "version_data": [
                                        {
                                            "version_value": "n/a"
                                        }
                                    ]
                                }
                            }
                        ]
                    },
                    "vendor_name": "n/a"
                }
            ]
        }
    },
    "data_format": "MITRE",
    "data_type": "CVE",
    "data_version": "4.0",
    "description": {
        "description_data": [
            {
                "lang": "eng",
                "value": "Linux kernel: heap out-of-bounds in AF_PACKET sockets. This new issue is analogous to previously disclosed CVE-2016-8655. In both cases, a socket option that changes socket state may race with safety checks in packet_set_ring. Previously with PACKET_VERSION. This time with PACKET_RESERVE. The solution is similar: lock the socket for the update. This issue may be exploitable, we did not investigate further. As this issue affects PF_PACKET sockets, it requires CAP_NET_RAW in the process namespace. But note that with user namespaces enabled, any process can create a namespace in which it has CAP_NET_RAW."
            }
        ]
    },
    "problemtype": {
        "problemtype_data": [
            {
                "description": [
                    {
                        "lang": "eng",
                        "value": "n/a"
                    }
                ]
            }
        ]
    },
    "references": {
        "reference_data": [
            {
                "name": "RHSA-2017:3200",
                "refsource": "REDHAT",
                "url": "https://access.redhat.com/errata/RHSA-2017:3200"
            },
            {
                "name": "100267",
                "refsource": "BID",
                "url": "http://www.securityfocus.com/bid/100267"
            },
            {
                "name": "RHSA-2017:2918",
                "refsource": "REDHAT",
                "url": "https://access.redhat.com/errata/RHSA-2017:2918"
            },
            {
                "name": "RHSA-2017:2931",
                "refsource": "REDHAT",
                "url": "https://access.redhat.com/errata/RHSA-2017:2931"
            },
            {
                "name": "DSA-3981",
                "refsource": "DEBIAN",
                "url": "http://www.debian.org/security/2017/dsa-3981"
            },
            {
                "name": "https://access.redhat.com/security/cve/cve-2017-1000111",
                "refsource": "CONFIRM",
                "url": "https://access.redhat.com/security/cve/cve-2017-1000111"
            },
            {
                "name": "1039132",
                "refsource": "SECTRACK",
                "url": "http://www.securitytracker.com/id/1039132"
            },
            {
                "name": "RHSA-2017:2930",
                "refsource": "REDHAT",
                "url": "https://access.redhat.com/errata/RHSA-2017:2930"
            }
        ]
    }
}