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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
16,006 | openssl | 6e629b5be45face20b4ca71c4fcbfed78b864a2e | https://github.com/openssl/openssl | https://git.openssl.org/?p=openssl.git;a=commitdiff;h=6e629b5be45face20b4ca71c4fcbfed78b864a2e | Add some sanity checks when checking CRL scores
Note: this was accidentally omitted from OpenSSL 1.0.2 branch.
Without this fix any attempt to use CRLs will crash.
CVE-2016-7052
Thanks to Bruce Stephens and Thomas Jakobi for reporting this issue.
Reviewed-by: Stephen Henson <steve@openssl.org>
Reviewed-by: Rich Sal... | 0 | static int check_issued(X509_STORE_CTX *ctx, X509 *x, X509 *issuer)
{
int ret;
ret = X509_check_issued(issuer, x);
if (ret == X509_V_OK)
return 1;
/* If we haven't asked for issuer errors don't set ctx */
if (!(ctx->param->flags & X509_V_FLAG_CB_ISSUER_CHECK))
return 0;
ctx->err... | 186,806,565,681,330,300,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2016-7052 | crypto/x509/x509_vfy.c in OpenSSL 1.0.2i allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) by triggering a CRL operation. | https://nvd.nist.gov/vuln/detail/CVE-2016-7052 |
16,007 | openssl | 6e629b5be45face20b4ca71c4fcbfed78b864a2e | https://github.com/openssl/openssl | https://git.openssl.org/?p=openssl.git;a=commitdiff;h=6e629b5be45face20b4ca71c4fcbfed78b864a2e | Add some sanity checks when checking CRL scores
Note: this was accidentally omitted from OpenSSL 1.0.2 branch.
Without this fix any attempt to use CRLs will crash.
CVE-2016-7052
Thanks to Bruce Stephens and Thomas Jakobi for reporting this issue.
Reviewed-by: Stephen Henson <steve@openssl.org>
Reviewed-by: Rich Sal... | 0 | static int check_policy(X509_STORE_CTX *ctx)
{
int ret;
if (ctx->parent)
return 1;
ret = X509_policy_check(&ctx->tree, &ctx->explicit_policy, ctx->chain,
ctx->param->policies, ctx->param->flags);
if (ret == 0) {
X509err(X509_F_CHECK_POLICY, ERR_R_MALLOC_FAILUR... | 25,771,525,378,933,337,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2016-7052 | crypto/x509/x509_vfy.c in OpenSSL 1.0.2i allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) by triggering a CRL operation. | https://nvd.nist.gov/vuln/detail/CVE-2016-7052 |
16,008 | openssl | 6e629b5be45face20b4ca71c4fcbfed78b864a2e | https://github.com/openssl/openssl | https://git.openssl.org/?p=openssl.git;a=commitdiff;h=6e629b5be45face20b4ca71c4fcbfed78b864a2e | Add some sanity checks when checking CRL scores
Note: this was accidentally omitted from OpenSSL 1.0.2 branch.
Without this fix any attempt to use CRLs will crash.
CVE-2016-7052
Thanks to Bruce Stephens and Thomas Jakobi for reporting this issue.
Reviewed-by: Stephen Henson <steve@openssl.org>
Reviewed-by: Rich Sal... | 0 | static int check_trust(X509_STORE_CTX *ctx)
{
int i, ok;
X509 *x = NULL;
int (*cb) (int xok, X509_STORE_CTX *xctx);
cb = ctx->verify_cb;
/* Check all trusted certificates in chain */
for (i = ctx->last_untrusted; i < sk_X509_num(ctx->chain); i++) {
x = sk_X509_value(ctx->chain, i);
... | 256,072,379,840,855,440,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2016-7052 | crypto/x509/x509_vfy.c in OpenSSL 1.0.2i allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) by triggering a CRL operation. | https://nvd.nist.gov/vuln/detail/CVE-2016-7052 |
16,009 | openssl | 6e629b5be45face20b4ca71c4fcbfed78b864a2e | https://github.com/openssl/openssl | https://git.openssl.org/?p=openssl.git;a=commitdiff;h=6e629b5be45face20b4ca71c4fcbfed78b864a2e | Add some sanity checks when checking CRL scores
Note: this was accidentally omitted from OpenSSL 1.0.2 branch.
Without this fix any attempt to use CRLs will crash.
CVE-2016-7052
Thanks to Bruce Stephens and Thomas Jakobi for reporting this issue.
Reviewed-by: Stephen Henson <steve@openssl.org>
Reviewed-by: Rich Sal... | 0 | static int internal_verify(X509_STORE_CTX *ctx)
{
int ok = 0, n;
X509 *xs, *xi;
EVP_PKEY *pkey = NULL;
int (*cb) (int xok, X509_STORE_CTX *xctx);
cb = ctx->verify_cb;
n = sk_X509_num(ctx->chain);
ctx->error_depth = n - 1;
n--;
xi = sk_X509_value(ctx->chain, n);
if (ctx->check_... | 146,943,588,074,155,180,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2016-7052 | crypto/x509/x509_vfy.c in OpenSSL 1.0.2i allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) by triggering a CRL operation. | https://nvd.nist.gov/vuln/detail/CVE-2016-7052 |
16,010 | openssl | 6e629b5be45face20b4ca71c4fcbfed78b864a2e | https://github.com/openssl/openssl | https://git.openssl.org/?p=openssl.git;a=commitdiff;h=6e629b5be45face20b4ca71c4fcbfed78b864a2e | Add some sanity checks when checking CRL scores
Note: this was accidentally omitted from OpenSSL 1.0.2 branch.
Without this fix any attempt to use CRLs will crash.
CVE-2016-7052
Thanks to Bruce Stephens and Thomas Jakobi for reporting this issue.
Reviewed-by: Stephen Henson <steve@openssl.org>
Reviewed-by: Rich Sal... | 0 | static X509 *lookup_cert_match(X509_STORE_CTX *ctx, X509 *x)
{
STACK_OF(X509) *certs;
X509 *xtmp = NULL;
int i;
/* Lookup all certs with matching subject name */
certs = ctx->lookup_certs(ctx, X509_get_subject_name(x));
if (certs == NULL)
return NULL;
/* Look for exact match */
f... | 315,841,031,545,923,900,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2016-7052 | crypto/x509/x509_vfy.c in OpenSSL 1.0.2i allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) by triggering a CRL operation. | https://nvd.nist.gov/vuln/detail/CVE-2016-7052 |
16,011 | spice | 9113dc6a303604a2d9812ac70c17d076ef11886c | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/libcacard/commit/?id=9113dc6a303604a2d9812ac70c17d076ef11886c | None | 0 | vcard7816_file_system_process_apdu(VCard *card, VCardAPDU *apdu,
VCardResponse **response)
{
/* TODO: if we want to support a virtual file system card, we do it here.
* It would probably be a pkcs #15 card type */
*response = vcard_make_response(
VCARD... | 181,235,954,283,776,100,000,000,000,000,000,000,000 | None | null | [
"CWE-772"
] | CVE-2017-6414 | Memory leak in the vcard_apdu_new function in card_7816.c in libcacard before 2.5.3 allows local guest OS users to cause a denial of service (host memory consumption) via vectors related to allocating a new APDU object. | https://nvd.nist.gov/vuln/detail/CVE-2017-6414 |
16,012 | spice | 9113dc6a303604a2d9812ac70c17d076ef11886c | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/libcacard/commit/?id=9113dc6a303604a2d9812ac70c17d076ef11886c | None | 0 | vcard_apdu_set_class(VCardAPDU *apdu) {
apdu->a_channel = 0;
apdu->a_secure_messaging = 0;
apdu->a_type = apdu->a_cla & 0xf0;
apdu->a_gen_type = VCARD_7816_ISO;
/* parse the class tables 8 & 9 of the 7816-4 Part 4 spec */
switch (apdu->a_type) {
/* we only support the basic types */
... | 303,515,655,899,765,800,000,000,000,000,000,000,000 | None | null | [
"CWE-772"
] | CVE-2017-6414 | Memory leak in the vcard_apdu_new function in card_7816.c in libcacard before 2.5.3 allows local guest OS users to cause a denial of service (host memory consumption) via vectors related to allocating a new APDU object. | https://nvd.nist.gov/vuln/detail/CVE-2017-6414 |
16,013 | spice | 9113dc6a303604a2d9812ac70c17d076ef11886c | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/libcacard/commit/?id=9113dc6a303604a2d9812ac70c17d076ef11886c | None | 0 | vcard_apdu_set_length(VCardAPDU *apdu)
{
int L, Le;
/* process according to table 5 of the 7816-4 Part 4 spec.
* variable names match the variables in the spec */
L = apdu->a_len-4; /* fixed APDU header */
apdu->a_Lc = 0;
apdu->a_Le = 0;
apdu->a_body = NULL;
switch (L) {
case 0:
... | 192,010,135,003,170,440,000,000,000,000,000,000,000 | None | null | [
"CWE-772"
] | CVE-2017-6414 | Memory leak in the vcard_apdu_new function in card_7816.c in libcacard before 2.5.3 allows local guest OS users to cause a denial of service (host memory consumption) via vectors related to allocating a new APDU object. | https://nvd.nist.gov/vuln/detail/CVE-2017-6414 |
16,014 | spice | 9113dc6a303604a2d9812ac70c17d076ef11886c | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/libcacard/commit/?id=9113dc6a303604a2d9812ac70c17d076ef11886c | None | 0 | vcard_make_response(vcard_7816_status_t status)
{
VCardResponse *response;
switch (status) {
/* known 7816 response codes */
case VCARD7816_STATUS_SUCCESS:
return VCARD_RESPONSE_GET_STATIC(
VCARD7816_STATUS_SUCCESS);
case VCARD7816_STATUS_WARNING:
return VCARD_RE... | 97,470,289,627,486,950,000,000,000,000,000,000,000 | None | null | [
"CWE-772"
] | CVE-2017-6414 | Memory leak in the vcard_apdu_new function in card_7816.c in libcacard before 2.5.3 allows local guest OS users to cause a denial of service (host memory consumption) via vectors related to allocating a new APDU object. | https://nvd.nist.gov/vuln/detail/CVE-2017-6414 |
16,015 | spice | 9113dc6a303604a2d9812ac70c17d076ef11886c | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/libcacard/commit/?id=9113dc6a303604a2d9812ac70c17d076ef11886c | None | 0 | vcard_process_apdu(VCard *card, VCardAPDU *apdu, VCardResponse **response)
{
VCardStatus status;
VCardBufferResponse *buffer_response;
/* first handle any PTS commands, which aren't really APDU's */
if (apdu->a_type == VCARD_7816_PTS) {
/* the PTS responses aren't really responses either */
... | 157,812,423,111,175,310,000,000,000,000,000,000,000 | None | null | [
"CWE-772"
] | CVE-2017-6414 | Memory leak in the vcard_apdu_new function in card_7816.c in libcacard before 2.5.3 allows local guest OS users to cause a denial of service (host memory consumption) via vectors related to allocating a new APDU object. | https://nvd.nist.gov/vuln/detail/CVE-2017-6414 |
16,016 | spice | 9113dc6a303604a2d9812ac70c17d076ef11886c | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/libcacard/commit/?id=9113dc6a303604a2d9812ac70c17d076ef11886c | None | 0 | vcard_response_delete(VCardResponse *response)
{
if (response == NULL) {
return;
}
switch (response->b_type) {
case VCARD_MALLOC:
/* everything was malloc'ed */
g_free(response->b_data);
g_free(response);
break;
case VCARD_MALLOC_DATA:
/* only the data... | 178,513,110,078,084,660,000,000,000,000,000,000,000 | None | null | [
"CWE-772"
] | CVE-2017-6414 | Memory leak in the vcard_apdu_new function in card_7816.c in libcacard before 2.5.3 allows local guest OS users to cause a denial of service (host memory consumption) via vectors related to allocating a new APDU object. | https://nvd.nist.gov/vuln/detail/CVE-2017-6414 |
16,017 | spice | 9113dc6a303604a2d9812ac70c17d076ef11886c | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/libcacard/commit/?id=9113dc6a303604a2d9812ac70c17d076ef11886c | None | 0 | vcard_response_new(VCard *card, unsigned char *buf,
int len, int Le, vcard_7816_status_t status)
{
VCardResponse *new_response;
if (len > Le) {
return vcard_init_buffer_response(card, buf, len);
}
new_response = vcard_response_new_data(buf, len);
if (new_response == NULL)... | 147,723,823,737,923,440,000,000,000,000,000,000,000 | None | null | [
"CWE-772"
] | CVE-2017-6414 | Memory leak in the vcard_apdu_new function in card_7816.c in libcacard before 2.5.3 allows local guest OS users to cause a denial of service (host memory consumption) via vectors related to allocating a new APDU object. | https://nvd.nist.gov/vuln/detail/CVE-2017-6414 |
16,018 | spice | 9113dc6a303604a2d9812ac70c17d076ef11886c | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/libcacard/commit/?id=9113dc6a303604a2d9812ac70c17d076ef11886c | None | 0 | vcard_response_new_bytes(VCard *card, unsigned char *buf, int len, int Le,
unsigned char sw1, unsigned char sw2)
{
VCardResponse *new_response;
if (len > Le) {
return vcard_init_buffer_response(card, buf, len);
}
new_response = vcard_response_new_data(buf, len);
if ... | 120,088,951,222,124,050,000,000,000,000,000,000,000 | None | null | [
"CWE-772"
] | CVE-2017-6414 | Memory leak in the vcard_apdu_new function in card_7816.c in libcacard before 2.5.3 allows local guest OS users to cause a denial of service (host memory consumption) via vectors related to allocating a new APDU object. | https://nvd.nist.gov/vuln/detail/CVE-2017-6414 |
16,019 | spice | 9113dc6a303604a2d9812ac70c17d076ef11886c | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/libcacard/commit/?id=9113dc6a303604a2d9812ac70c17d076ef11886c | None | 0 | vcard_response_new_data(unsigned char *buf, int len)
{
VCardResponse *new_response;
new_response = g_new(VCardResponse, 1);
new_response->b_data = g_malloc(len + 2);
memcpy(new_response->b_data, buf, len);
new_response->b_total_len = len+2;
new_response->b_len = len;
new_response->b_type = ... | 218,247,377,203,831,800,000,000,000,000,000,000,000 | None | null | [
"CWE-772"
] | CVE-2017-6414 | Memory leak in the vcard_apdu_new function in card_7816.c in libcacard before 2.5.3 allows local guest OS users to cause a denial of service (host memory consumption) via vectors related to allocating a new APDU object. | https://nvd.nist.gov/vuln/detail/CVE-2017-6414 |
16,020 | spice | 9113dc6a303604a2d9812ac70c17d076ef11886c | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/libcacard/commit/?id=9113dc6a303604a2d9812ac70c17d076ef11886c | None | 0 | vcard_response_new_status(vcard_7816_status_t status)
{
VCardResponse *new_response;
new_response = g_new(VCardResponse, 1);
new_response->b_data = &new_response->b_sw1;
new_response->b_len = 0;
new_response->b_total_len = 2;
new_response->b_type = VCARD_MALLOC_STRUCT;
vcard_response_set_st... | 317,523,247,614,975,850,000,000,000,000,000,000,000 | None | null | [
"CWE-772"
] | CVE-2017-6414 | Memory leak in the vcard_apdu_new function in card_7816.c in libcacard before 2.5.3 allows local guest OS users to cause a denial of service (host memory consumption) via vectors related to allocating a new APDU object. | https://nvd.nist.gov/vuln/detail/CVE-2017-6414 |
16,021 | spice | 9113dc6a303604a2d9812ac70c17d076ef11886c | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/libcacard/commit/?id=9113dc6a303604a2d9812ac70c17d076ef11886c | None | 0 | vcard_response_set_status(VCardResponse *response, vcard_7816_status_t status)
{
unsigned char sw1, sw2;
response->b_status = status; /* make sure the status and swX representations
* are consistent */
sw1 = (status >> 8) & 0xff;
sw2 = status & 0xff;
response->b_sw1... | 46,631,243,626,237,530,000,000,000,000,000,000,000 | None | null | [
"CWE-772"
] | CVE-2017-6414 | Memory leak in the vcard_apdu_new function in card_7816.c in libcacard before 2.5.3 allows local guest OS users to cause a denial of service (host memory consumption) via vectors related to allocating a new APDU object. | https://nvd.nist.gov/vuln/detail/CVE-2017-6414 |
16,022 | spice | 9113dc6a303604a2d9812ac70c17d076ef11886c | https://gitlab.freedesktop.org/spice/spice | https://cgit.freedesktop.org/spice/libcacard/commit/?id=9113dc6a303604a2d9812ac70c17d076ef11886c | None | 0 | vcard_response_set_status_bytes(VCardResponse *response,
unsigned char sw1, unsigned char sw2)
{
response->b_status = sw1 << 8 | sw2;
response->b_sw1 = sw1;
response->b_sw2 = sw2;
response->b_data[response->b_len] = sw1;
response->b_data[response->b_len+1] = sw2;
}
| 103,850,824,496,545,870,000,000,000,000,000,000,000 | None | null | [
"CWE-772"
] | CVE-2017-6414 | Memory leak in the vcard_apdu_new function in card_7816.c in libcacard before 2.5.3 allows local guest OS users to cause a denial of service (host memory consumption) via vectors related to allocating a new APDU object. | https://nvd.nist.gov/vuln/detail/CVE-2017-6414 |
16,054 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void __report_context_error(const char *fname, struct vrend_context *ctx, enum virgl_ctx_errors error, uint32_t value)
{
ctx->in_error = true;
ctx->last_error = error;
fprintf(stderr,"%s: context error reported %d \"%s\" %s %d\n", fname, ctx->ctx_id, ctx->debug_name, vrend_ctx_error_strings[error], valu... | 170,005,904,502,559,930,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,055 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void __report_core_warn(const char *fname, struct vrend_context *ctx, enum virgl_ctx_errors error, uint32_t value)
{
fprintf(stderr,"%s: core profile violation reported %d \"%s\" %s %d\n", fname, ctx->ctx_id, ctx->debug_name, vrend_core_profile_warn_strings[error], value);
}
| 104,340,981,448,692,600,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,056 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static struct vrend_linked_shader_program *add_shader_program(struct vrend_context *ctx,
struct vrend_shader *vs,
struct vrend_shader *fs,
... | 307,352,406,488,329,170,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,057 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static bool check_iov_bounds(struct vrend_resource *res,
const struct vrend_transfer_info *info,
struct iovec *iov, int num_iovs)
{
GLuint send_size;
GLuint iovsize = vrend_get_iovec_size(iov, num_iovs);
GLuint valid_stride, valid_layer_stride;
/* v... | 112,758,094,203,459,850,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,058 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static int check_resource_valid(struct vrend_renderer_resource_create_args *args)
{
/* do not accept handle 0 */
if (args->handle == 0)
return -1;
/* limit the target */
if (args->target >= PIPE_MAX_TEXTURE_TYPES)
return -1;
if (args->format >= VIRGL_FORMAT_MAX)
return -1;
/* only... | 209,784,760,582,677,400,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,059 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static bool check_transfer_bounds(struct vrend_resource *res,
const struct vrend_transfer_info *info)
{
int lwidth, lheight;
/* check mipmap level is in bounds */
if (info->level > res->base.last_level)
return false;
if (info->box->x < 0 || info->box->y < 0)
re... | 152,075,882,497,904,220,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,060 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static inline int conv_a8_blend(int blend_factor)
{
if (blend_factor == PIPE_BLENDFACTOR_DST_ALPHA)
return PIPE_BLENDFACTOR_DST_COLOR;
if (blend_factor == PIPE_BLENDFACTOR_INV_DST_ALPHA)
return PIPE_BLENDFACTOR_INV_DST_COLOR;
return blend_factor;
}
| 130,687,653,801,176,440,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,061 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static inline int conv_dst_blend(int blend_factor)
{
if (blend_factor == PIPE_BLENDFACTOR_DST_ALPHA)
return PIPE_BLENDFACTOR_ONE;
if (blend_factor == PIPE_BLENDFACTOR_INV_DST_ALPHA)
return PIPE_BLENDFACTOR_ZERO;
return blend_factor;
}
| 173,623,041,330,731,880,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,062 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static inline GLenum convert_mag_filter(unsigned int filter)
{
if (filter == PIPE_TEX_FILTER_NEAREST)
return GL_NEAREST;
return GL_LINEAR;
}
| 252,398,720,010,328,840,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,063 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static inline GLenum convert_min_filter(unsigned int filter, unsigned int mip_filter)
{
if (mip_filter == PIPE_TEX_MIPFILTER_NONE)
return convert_mag_filter(filter);
else if (mip_filter == PIPE_TEX_MIPFILTER_LINEAR) {
if (filter == PIPE_TEX_FILTER_NEAREST)
return GL_NEAREST_MIPMAP_LINEAR;
... | 76,973,355,529,347,720,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,064 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void dump_stream_out(struct pipe_stream_output_info *so)
{
int i;
if (!so)
return;
printf("streamout: %d\n", so->num_outputs);
printf("strides: ");
for (i = 0; i < 4; i++)
printf("%d ", so->stride[i]);
printf("\n");
printf("outputs:\n");
for (i = 0; i < so->num_outputs; i++) {... | 310,251,864,827,939,600,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,065 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void flush_eventfd(int fd)
{
ssize_t len;
uint64_t value;
do {
len = read(fd, &value, sizeof(value));
} while ((len == -1 && errno == EINTR) || len == sizeof(value));
}
| 174,270,582,135,019,800,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,066 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static GLenum get_gs_xfb_mode(GLenum mode)
{
switch (mode) {
case GL_POINTS:
return GL_POINTS;
case GL_LINE_STRIP:
return GL_LINES;
case GL_TRIANGLE_STRIP:
return GL_TRIANGLES;
default:
fprintf(stderr, "illegal gs transform feedback mode %d\n", mode);
return GL_POINTS;
}
... | 36,957,047,652,073,230,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,067 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static GLenum get_xfb_mode(GLenum mode)
{
switch (mode) {
case GL_POINTS:
return GL_POINTS;
case GL_TRIANGLES:
case GL_TRIANGLE_STRIP:
case GL_TRIANGLE_FAN:
case GL_QUADS:
case GL_QUAD_STRIP:
case GL_POLYGON:
return GL_TRIANGLES;
case GL_LINES:
case GL_LINE_LOOP:
case GL_LIN... | 217,559,293,483,926,800,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,068 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static inline bool is_dst_blend(int blend_factor)
{
return (blend_factor == PIPE_BLENDFACTOR_DST_ALPHA ||
blend_factor == PIPE_BLENDFACTOR_INV_DST_ALPHA);
}
| 232,268,819,952,370,530,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,069 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static struct vrend_linked_shader_program *lookup_shader_program(struct vrend_context *ctx,
GLuint vs_id, GLuint fs_id, GLuint gs_id, bool dual_src)
{
struct vrend_linked_shader_program *ent;
LIST_FOR_EACH_ENTRY(ent, &ctx->sub->programs, head) {
... | 281,362,028,665,963,730,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,070 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static inline const char *pipe_shader_to_prefix(int shader_type)
{
switch (shader_type) {
case PIPE_SHADER_VERTEX: return "vs";
case PIPE_SHADER_FRAGMENT: return "fs";
case PIPE_SHADER_GEOMETRY: return "gs";
default:
return NULL;
};
}
| 118,755,989,467,248,990,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,071 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void read_transfer_data(struct pipe_resource *res,
struct iovec *iov,
unsigned int num_iovs,
char *data,
uint32_t src_stride,
struct pipe_box *box,
... | 108,448,723,034,681,860,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,072 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void set_stream_out_varyings(int prog_id, struct vrend_shader_info *sinfo)
{
struct pipe_stream_output_info *so = &sinfo->so_info;
char *varyings[PIPE_MAX_SHADER_OUTPUTS*2];
int i, j;
int n_outputs = 0;
int last_buffer = 0;
char *start_skip;
int buf_offset = 0;
int skip;
if (!so->num_o... | 185,238,350,485,433,760,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,073 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static inline bool should_invert_viewport(struct vrend_context *ctx)
{
/* if we have a negative viewport then gallium wanted to invert it,
however since we are rendering to GL FBOs we need to invert it
again unless we are rendering upside down already
- confused?
so if gallium asks for a nega... | 84,654,341,753,966,810,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,074 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static GLenum tgsitargettogltarget(const enum pipe_texture_target target, int nr_samples)
{
switch(target) {
case PIPE_TEXTURE_1D:
return GL_TEXTURE_1D;
case PIPE_TEXTURE_2D:
return (nr_samples > 1) ? GL_TEXTURE_2D_MULTISAMPLE : GL_TEXTURE_2D;
case PIPE_TEXTURE_3D:
return GL_TEXTURE_3D;
... | 144,752,744,808,430,400,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,075 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static int thread_sync(void *arg)
{
virgl_gl_context gl_context = vrend_state.sync_context;
struct vrend_fence *fence, *stor;
pipe_mutex_lock(vrend_state.fence_mutex);
vrend_clicbs->make_current(0, gl_context);
while (!vrend_state.stop_sync_thread) {
if (LIST_IS_EMPTY(&vrend_state.fence_wait_list... | 87,377,067,043,471,380,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,076 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static inline GLenum to_gl_swizzle(int swizzle)
{
switch (swizzle) {
case PIPE_SWIZZLE_RED: return GL_RED;
case PIPE_SWIZZLE_GREEN: return GL_GREEN;
case PIPE_SWIZZLE_BLUE: return GL_BLUE;
case PIPE_SWIZZLE_ALPHA: return GL_ALPHA;
case PIPE_SWIZZLE_ZERO: return GL_ZERO;
case PIPE_SWIZZLE_ONE: retur... | 179,038,414,825,699,500,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,077 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static GLenum translate_blend_factor(uint32_t pipe_factor)
{
switch (pipe_factor) {
case PIPE_BLENDFACTOR_ONE: return GL_ONE;
case PIPE_BLENDFACTOR_SRC_COLOR: return GL_SRC_COLOR;
case PIPE_BLENDFACTOR_SRC_ALPHA: return GL_SRC_ALPHA;
case PIPE_BLENDFACTOR_DST_COLOR: return GL_DST_COLOR;
case PIPE_BLE... | 175,526,242,214,924,040,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,078 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static GLenum translate_blend_func(uint32_t pipe_blend)
{
switch(pipe_blend){
case PIPE_BLEND_ADD: return GL_FUNC_ADD;
case PIPE_BLEND_SUBTRACT: return GL_FUNC_SUBTRACT;
case PIPE_BLEND_REVERSE_SUBTRACT: return GL_FUNC_REVERSE_SUBTRACT;
case PIPE_BLEND_MIN: return GL_MIN;
case PIPE_BLEND_MAX: return G... | 82,997,277,925,268,740,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,079 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static inline GLenum translate_fill(uint32_t mode)
{
switch (mode) {
case PIPE_POLYGON_MODE_POINT:
return GL_POINT;
case PIPE_POLYGON_MODE_LINE:
return GL_LINE;
case PIPE_POLYGON_MODE_FILL:
return GL_FILL;
default:
assert(0);
return 0;
}
}
| 297,428,127,868,635,350,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,080 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | translate_logicop(GLuint pipe_logicop)
{
switch (pipe_logicop) {
#define CASE(x) case PIPE_LOGICOP_##x: return GL_##x
CASE(CLEAR);
CASE(NOR);
CASE(AND_INVERTED);
CASE(COPY_INVERTED);
CASE(AND_REVERSE);
CASE(INVERT);
CASE(XOR);
CASE(NAND);
CASE(AND);
CASE(EQ... | 76,136,724,542,734,660,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,081 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | translate_stencil_op(GLuint op)
{
switch (op) {
#define CASE(x) case PIPE_STENCIL_OP_##x: return GL_##x
CASE(KEEP);
CASE(ZERO);
CASE(REPLACE);
CASE(INCR);
CASE(DECR);
CASE(INCR_WRAP);
CASE(DECR_WRAP);
CASE(INVERT);
default:
assert("invalid stencilop token()" =... | 278,381,066,569,295,540,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,082 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_alpha_test_enable(struct vrend_context *ctx, bool alpha_test_enable)
{
if (vrend_state.use_core_profile) {
/* handled in shaders */
return;
}
if (ctx->sub->alpha_test_enabled != alpha_test_enable) {
ctx->sub->alpha_test_enabled = alpha_test_enable;
if (alpha_test_enabl... | 336,553,856,887,680,200,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,083 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_apply_sampler_state(struct vrend_context *ctx,
struct vrend_resource *res,
uint32_t shader_type,
int id,
int sampler_id,
... | 250,352,161,397,727,500,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,084 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | void vrend_begin_query(struct vrend_context *ctx, uint32_t handle)
{
struct vrend_query *q;
q = vrend_object_lookup(ctx->sub->object_hash, handle, VIRGL_OBJECT_QUERY);
if (!q)
return;
if (q->gltype == GL_TIMESTAMP)
return;
glBeginQuery(q->gltype, q->id);
}
| 73,038,794,453,185,975,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,085 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | void vrend_bind_shader(struct vrend_context *ctx,
uint32_t handle, uint32_t type)
{
struct vrend_shader_selector *sel;
if (type > PIPE_SHADER_GEOMETRY)
return;
if (handle == 0) {
ctx->sub->shader_dirty = true;
vrend_shader_state_reference(&ctx->sub->shaders[type], NUL... | 112,529,041,593,331,520,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,086 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | void vrend_bind_vertex_elements_state(struct vrend_context *ctx,
uint32_t handle)
{
struct vrend_vertex_element_array *v;
if (!handle) {
ctx->sub->ve = NULL;
return;
}
v = vrend_object_lookup(ctx->sub->object_hash, handle, VIRGL_OBJECT_VERTEX_ELEMENTS);
... | 181,355,856,283,894,550,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,087 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_blend_enable(struct vrend_context *ctx, bool blend_enable)
{
if (ctx->sub->blend_enabled != blend_enable) {
ctx->sub->blend_enabled = blend_enable;
if (blend_enable)
glEnable(GL_BLEND);
else
glDisable(GL_BLEND);
}
}
| 283,976,453,068,038,520,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,088 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static bool vrend_check_query(struct vrend_query *query)
{
uint64_t result;
struct virgl_host_query_state *state;
bool ret;
ret = vrend_get_one_query_result(query->id, false, &result);
if (ret == false)
return false;
state = (struct virgl_host_query_state *)query->res->ptr;
state->result = ... | 281,978,334,860,966,580,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,089 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | void vrend_clear(struct vrend_context *ctx,
unsigned buffers,
const union pipe_color_union *color,
double depth, unsigned stencil)
{
GLbitfield bits = 0;
if (ctx->in_error)
return;
if (ctx->ctx_switch_pending)
vrend_finish_context_switch(ctx);
... | 220,337,080,135,161,100,000,000,000,000,000,000,000 | vrend_renderer.c | 8,973,076,452,455,057,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,090 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static bool vrend_compile_shader(struct vrend_context *ctx,
struct vrend_shader *shader)
{
GLint param;
glShaderSource(shader->id, 1, (const char **)&shader->glsl_prog, NULL);
glCompileShader(shader->id);
glGetShaderiv(shader->id, GL_COMPILE_STATUS, ¶m);
if (param == ... | 212,105,255,307,244,140,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,091 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | struct vrend_context *vrend_create_context(int id, uint32_t nlen, const char *debug_name)
{
struct vrend_context *grctx = CALLOC_STRUCT(vrend_context);
if (!grctx)
return NULL;
if (nlen && debug_name) {
strncpy(grctx->debug_name, debug_name, 64);
}
grctx->ctx_id = id;
list_inithead(&gr... | 5,350,972,017,933,847,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,092 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | int vrend_create_query(struct vrend_context *ctx, uint32_t handle,
uint32_t query_type, uint32_t query_index,
uint32_t res_handle, uint32_t offset)
{
struct vrend_query *q;
struct vrend_resource *res;
uint32_t ret_handle;
res = vrend_renderer_ctx_res_lookup(ctx,... | 256,186,307,756,993,200,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,093 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | int vrend_create_sampler_state(struct vrend_context *ctx,
uint32_t handle,
struct pipe_sampler_state *templ)
{
struct vrend_sampler_state *state = CALLOC_STRUCT(vrend_sampler_state);
int ret_handle;
if (!state)
return ENOMEM;
state->base ... | 129,271,903,581,080,060,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,094 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | int vrend_create_sampler_view(struct vrend_context *ctx,
uint32_t handle,
uint32_t res_handle, uint32_t format,
uint32_t val0, uint32_t val1, uint32_t swizzle_packed)
{
struct vrend_sampler_view *view;
struct vrend_resource ... | 220,329,453,427,504,670,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,095 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | int vrend_create_shader(struct vrend_context *ctx,
uint32_t handle,
const struct pipe_stream_output_info *so_info,
const char *shd_text, uint32_t offlen, uint32_t num_tokens,
uint32_t type, uint32_t pkt_length)
{
struct v... | 274,018,240,397,829,320,000,000,000,000,000,000,000 | vrend_renderer.c | 51,950,024,320,464,650,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,096 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void *vrend_create_shader_state(struct vrend_context *ctx,
const struct pipe_stream_output_info *so_info,
unsigned pipe_shader_type)
{
struct vrend_shader_selector *sel = CALLOC_STRUCT(vrend_shader_selector);
if (!sel)
ret... | 327,227,930,284,623,930,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,097 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | int vrend_create_so_target(struct vrend_context *ctx,
uint32_t handle,
uint32_t res_handle,
uint32_t buffer_offset,
uint32_t buffer_size)
{
struct vrend_so_target *target;
struct vrend_resource *res;
int... | 139,821,885,050,691,210,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,098 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | int vrend_create_surface(struct vrend_context *ctx,
uint32_t handle,
uint32_t res_handle, uint32_t format,
uint32_t val0, uint32_t val1)
{
struct vrend_surface *surf;
struct vrend_resource *res;
uint32_t ret_handle;
if (format >= PI... | 190,628,755,744,279,740,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,099 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_depth_test_enable(struct vrend_context *ctx, bool depth_test_enable)
{
if (ctx->sub->depth_test_enabled != depth_test_enable) {
ctx->sub->depth_test_enabled = depth_test_enable;
if (depth_test_enable)
glEnable(GL_DEPTH_TEST);
else
glDisable(GL_DEPTH_TEST);
}
}... | 291,309,963,885,001,000,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,100 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | bool vrend_destroy_context(struct vrend_context *ctx)
{
bool switch_0 = (ctx == vrend_state.current_ctx);
struct vrend_context *cur = vrend_state.current_ctx;
struct vrend_sub_context *sub, *tmp;
if (switch_0) {
vrend_state.current_ctx = NULL;
vrend_state.current_hw_ctx = NULL;
}
if (vren... | 89,515,117,461,969,050,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,101 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_destroy_program(struct vrend_linked_shader_program *ent)
{
int i;
glDeleteProgram(ent->id);
list_del(&ent->head);
for (i = PIPE_SHADER_VERTEX; i <= PIPE_SHADER_GEOMETRY; i++) {
if (ent->ss[i])
list_del(&ent->sl[i]);
free(ent->shadow_samp_mask_locs[i]);
free(ent-... | 49,414,017,085,300,350,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,102 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_destroy_resource_object(void *obj_ptr)
{
struct vrend_resource *res = obj_ptr;
if (pipe_reference(&res->base.reference, NULL))
vrend_renderer_resource_destroy(res, false);
}
| 303,361,760,341,445,700,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,103 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_destroy_sampler_state_object(void *obj_ptr)
{
struct vrend_sampler_state *state = obj_ptr;
glDeleteSamplers(1, &state->id);
FREE(state);
}
| 17,361,077,142,857,380,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,104 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_destroy_sampler_view(struct vrend_sampler_view *samp)
{
vrend_resource_reference(&samp->texture, NULL);
free(samp);
}
| 104,707,178,785,417,050,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,105 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_destroy_sampler_view_object(void *obj_ptr)
{
struct vrend_sampler_view *samp = obj_ptr;
vrend_sampler_view_reference(&samp, NULL);
}
| 236,613,501,365,456,000,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,106 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_destroy_shader_object(void *obj_ptr)
{
struct vrend_shader_selector *state = obj_ptr;
vrend_shader_state_reference(&state, NULL);
}
| 4,871,218,449,748,163,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,107 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_destroy_shader_selector(struct vrend_shader_selector *sel)
{
struct vrend_shader *p = sel->current, *c;
int i;
while (p) {
c = p->next_variant;
vrend_shader_destroy(p);
p = c;
}
if (sel->sinfo.so_names)
for (i = 0; i < sel->sinfo.so_info.num_outputs; i++)
... | 337,621,285,622,901,420,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,108 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_destroy_so_target(struct vrend_so_target *target)
{
vrend_resource_reference(&target->buffer, NULL);
free(target);
}
| 184,462,021,650,676,040,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,109 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_destroy_so_target_object(void *obj_ptr)
{
struct vrend_so_target *target = obj_ptr;
struct vrend_sub_context *sub_ctx = target->sub_ctx;
struct vrend_streamout_object *obj, *tmp;
bool found;
int i;
LIST_FOR_EACH_ENTRY_SAFE(obj, tmp, &sub_ctx->streamout_list, head) {
found = fa... | 324,965,711,444,103,400,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,110 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_destroy_streamout_object(struct vrend_streamout_object *obj)
{
int i;
list_del(&obj->head);
for (i = 0; i < obj->num_targets; i++)
vrend_so_target_reference(&obj->so_targets[i], NULL);
if (vrend_state.have_tf2)
glDeleteTransformFeedbacks(1, &obj->id);
FREE(obj);
}
| 279,143,844,459,629,460,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,111 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_destroy_sub_context(struct vrend_sub_context *sub)
{
int i, j;
struct vrend_streamout_object *obj, *tmp;
if (sub->fb_id)
glDeleteFramebuffers(1, &sub->fb_id);
if (sub->blit_fb_ids[0])
glDeleteFramebuffers(2, sub->blit_fb_ids);
glBindBuffer(GL_ELEMENT_ARRAY_BUFFER, 0);
... | 180,072,830,104,973,220,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,112 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_destroy_surface(struct vrend_surface *surf)
{
vrend_resource_reference(&surf->texture, NULL);
free(surf);
}
| 26,831,660,218,375,704,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,113 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_destroy_surface_object(void *obj_ptr)
{
struct vrend_surface *surface = obj_ptr;
vrend_surface_reference(&surface, NULL);
}
| 95,840,137,775,066,800,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,114 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_destroy_vertex_elements_object(void *obj_ptr)
{
struct vrend_vertex_element_array *v = obj_ptr;
if (vrend_state.have_vertex_attrib_binding) {
glDeleteVertexArrays(1, &v->id);
}
FREE(v);
}
| 212,453,351,587,885,700,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,115 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_draw_bind_samplers(struct vrend_context *ctx)
{
int sampler_id;
int i;
int shader_type;
sampler_id = 0;
for (shader_type = PIPE_SHADER_VERTEX; shader_type <= ctx->sub->last_shader_idx; shader_type++) {
int index = 0;
for (i = 0; i < ctx->sub->views[shader_type].num_views; i... | 92,007,669,395,798,010,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,116 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_draw_bind_ubo(struct vrend_context *ctx)
{
int i;
int ubo_id;
int shader_type;
ubo_id = 0;
for (shader_type = PIPE_SHADER_VERTEX; shader_type <= ctx->sub->last_shader_idx; shader_type++) {
uint32_t mask;
int shader_ubo_idx = 0;
struct pipe_constant_buffer *cb;
s... | 21,437,771,658,301,584,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,117 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_draw_bind_vertex_binding(struct vrend_context *ctx,
struct vrend_vertex_element_array *va)
{
int i;
glBindVertexArray(va->id);
if (ctx->sub->vbo_dirty) {
for (i = 0; i < ctx->sub->num_vbos; i++) {
struct vrend_resource *res = (struct... | 145,814,704,792,540,100,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,118 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_draw_bind_vertex_legacy(struct vrend_context *ctx,
struct vrend_vertex_element_array *va)
{
uint32_t num_enable;
uint32_t enable_bitmask;
uint32_t disable_bitmask;
int i;
num_enable = va->count;
enable_bitmask = 0;
disable_bitmask = ~((1u... | 61,107,237,558,039,740,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,119 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | void vrend_end_query(struct vrend_context *ctx, uint32_t handle)
{
struct vrend_query *q;
q = vrend_object_lookup(ctx->sub->object_hash, handle, VIRGL_OBJECT_QUERY);
if (!q)
return;
if (vrend_is_timer_query(q->gltype)) {
if (q->gltype == GL_TIMESTAMP)
glQueryCounter(q->id, q->gltype);
... | 257,302,793,287,849,900,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,120 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | void vrend_fb_bind_texture(struct vrend_resource *res,
int idx,
uint32_t level, uint32_t layer)
{
const struct util_format_description *desc = util_format_description(res->base.format);
GLenum attachment = GL_COLOR_ATTACHMENT0_EXT + idx;
if (vrend_format_i... | 77,869,941,414,469,725,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,121 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static inline void vrend_fill_shader_key(struct vrend_context *ctx,
struct vrend_shader_key *key)
{
if (vrend_state.use_core_profile == true) {
int i;
bool add_alpha_test = true;
key->cbufs_are_a8_bitmask = 0;
for (i = 0; i < ctx->sub->nr_cbufs; i++) {... | 309,439,527,897,308,430,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,122 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_finish_context_switch(struct vrend_context *ctx)
{
if (ctx->ctx_switch_pending == false)
return;
ctx->ctx_switch_pending = false;
if (vrend_state.current_hw_ctx == ctx)
return;
vrend_state.current_hw_ctx = ctx;
vrend_clicbs->make_current(0, ctx->sub->gl_context);
}
| 105,060,223,286,906,530,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,123 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static int vrend_finish_shader(struct vrend_context *ctx,
struct vrend_shader_selector *sel,
const struct tgsi_token *tokens)
{
int r;
sel->tokens = tgsi_dup_tokens(tokens);
r = vrend_shader_select(ctx, sel, NULL);
if (r) {
return EINVAL;... | 276,367,864,847,982,100,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,124 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static inline bool vrend_format_can_render(enum virgl_formats format)
{
return tex_conv_table[format].bindings & VREND_BIND_RENDER;
}
| 112,116,303,193,492,120,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,125 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static inline bool vrend_format_is_ds(enum virgl_formats format)
{
return tex_conv_table[format].bindings & VREND_BIND_DEPTHSTENCIL;
}
| 42,333,663,336,557,522,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,126 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | bool vrend_format_is_emulated_alpha(enum virgl_formats format)
{
if (!vrend_state.use_core_profile)
return false;
return (format == VIRGL_FORMAT_A8_UNORM ||
format == VIRGL_FORMAT_A16_UNORM);
}
| 132,855,891,129,646,870,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,127 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_free_programs(struct vrend_sub_context *sub)
{
struct vrend_linked_shader_program *ent, *tmp;
if (LIST_IS_EMPTY(&sub->programs))
return;
LIST_FOR_EACH_ENTRY_SAFE(ent, tmp, &sub->programs, head) {
vrend_destroy_program(ent);
}
}
| 141,961,873,097,373,200,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,128 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_free_sync_thread(void)
{
if (!vrend_state.sync_thread)
return;
pipe_mutex_lock(vrend_state.fence_mutex);
vrend_state.stop_sync_thread = true;
pipe_mutex_unlock(vrend_state.fence_mutex);
pipe_condvar_signal(vrend_state.fence_cond);
pipe_thread_wait(vrend_state.sync_thread);
... | 228,129,144,321,469,640,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,129 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static bool vrend_get_one_query_result(GLuint query_id, bool use_64, uint64_t *result)
{
GLint ready;
GLuint passed;
GLuint64 pass64;
glGetQueryObjectiv(query_id, GL_QUERY_RESULT_AVAILABLE_ARB, &ready);
if (!ready)
return false;
if (use_64) {
glGetQueryObjectui64v(query_id, GL_QUERY_RES... | 277,899,950,011,551,600,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,130 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | void vrend_get_query_result(struct vrend_context *ctx, uint32_t handle,
uint32_t wait)
{
struct vrend_query *q;
bool ret;
q = vrend_object_lookup(ctx->sub->object_hash, handle, VIRGL_OBJECT_QUERY);
if (!q)
return;
ret = vrend_check_query(q);
if (ret == false)
... | 53,395,240,752,662,430,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,131 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_hw_emit_blend(struct vrend_context *ctx, struct pipe_blend_state *state)
{
if (state->logicop_enable != ctx->sub->hw_blend_state.logicop_enable) {
ctx->sub->hw_blend_state.logicop_enable = state->logicop_enable;
if (state->logicop_enable) {
glEnable(GL_COLOR_LOGIC_OP);
... | 193,155,989,954,019,730,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,132 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_hw_emit_dsa(struct vrend_context *ctx)
{
struct pipe_depth_stencil_alpha_state *state = &ctx->sub->dsa_state;
if (state->depth.enabled) {
vrend_depth_test_enable(ctx, true);
glDepthFunc(GL_NEVER + state->depth.func);
if (state->depth.writemask)
glDepthMask(GL_TRUE);
... | 247,766,917,689,175,650,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,133 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_hw_emit_framebuffer_state(struct vrend_context *ctx)
{
static const GLenum buffers[8] = {
GL_COLOR_ATTACHMENT0_EXT,
GL_COLOR_ATTACHMENT1_EXT,
GL_COLOR_ATTACHMENT2_EXT,
GL_COLOR_ATTACHMENT3_EXT,
GL_COLOR_ATTACHMENT4_EXT,
GL_COLOR_ATTACHMENT5_EXT,
GL_COLOR_AT... | 32,818,432,411,005,606,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,134 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_hw_emit_rs(struct vrend_context *ctx)
{
struct pipe_rasterizer_state *state = &ctx->sub->rs_state;
int i;
if (state->depth_clip) {
glDisable(GL_DEPTH_CLAMP);
} else {
glEnable(GL_DEPTH_CLAMP);
}
if (state->point_size_per_vertex) {
glEnable(GL_PROGRAM_POINT_SIZE);
... | 174,472,641,473,115,320,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,135 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_hw_emit_streamout_targets(struct vrend_context *ctx, struct vrend_streamout_object *so_obj)
{
int i;
for (i = 0; i < so_obj->num_targets; i++) {
if (so_obj->so_targets[i]->buffer_offset || so_obj->so_targets[i]->buffer_size < so_obj->so_targets[i]->buffer->base.width0)
glBindBuff... | 323,010,065,999,334,420,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
16,136 | virglrenderer | 737c3350850ca4dbc5633b3bdb4118176ce59920 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=737c3350850ca4dbc5633b3bdb4118176ce59920 | renderer: fix memory leak in vertex elements state create
Reported-by: Li Qiang
Free the vertex array in error path.
This was introduced by this commit:
renderer: fix heap overflow in vertex elements state create.
I rewrote the code to not require the allocation in the first
place if we have an error, seems nicer.
S... | 0 | static void vrend_hw_set_zsurf_texture(struct vrend_context *ctx)
{
struct vrend_resource *tex;
int first_layer, last_layer;
if (!ctx->sub->zsurf) {
glFramebufferTexture2DEXT(GL_FRAMEBUFFER_EXT, GL_DEPTH_STENCIL_ATTACHMENT,
GL_TEXTURE_2D, 0, 0);
return;
}
tex ... | 183,868,554,446,991,850,000,000,000,000,000,000,000 | vrend_renderer.c | 16,381,365,421,525,090,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2017-6386 | Memory leak in the vrend_create_vertex_elements_state function in vrend_renderer.c in virglrenderer allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGL_OBJECT_VERTEX_ELEMENTS commands. | https://nvd.nist.gov/vuln/detail/CVE-2017-6386 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.