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,137 | 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_hw_switch_context(struct vrend_context *ctx, bool now)
{
if (ctx == vrend_state.current_ctx && ctx->ctx_switch_pending == false)
return true;
if (ctx->ctx_id != 0 && ctx->in_error) {
return false;
}
ctx->ctx_switch_pending = true;
if (now == true) {
vrend_finish_context_swi... | 205,489,706,916,328,480,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,138 | 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_init_pstipple_texture(struct vrend_context *ctx)
{
glGenTextures(1, &ctx->pstipple_tex_id);
glBindTexture(GL_TEXTURE_2D, ctx->pstipple_tex_id);
glTexImage2D(GL_TEXTURE_2D, 0, GL_R8, 32, 32, 0, GL_RED, GL_UNSIGNED_BYTE, NULL);
glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_S, GL_REPEAT);
... | 288,521,866,031,918,960,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,139 | 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 | vrend_insert_format_swizzle(int override_format, struct vrend_format_table *entry, uint32_t bindings, uint8_t swizzle[4])
{
int i;
tex_conv_table[override_format] = *entry;
tex_conv_table[override_format].bindings = bindings;
tex_conv_table[override_format].flags = VREND_BIND_NEED_SWIZZLE;
for (i = 0; i ... | 82,046,014,748,330,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,140 | 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_is_ds_format(enum virgl_formats format)
{
return vrend_format_is_ds(format);
}
| 201,504,630,057,936,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,141 | 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_is_timer_query(GLenum gltype)
{
return gltype == GL_TIMESTAMP ||
gltype == GL_TIME_ELAPSED;
}
| 276,745,133,795,702,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,142 | 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_object_bind_blend(struct vrend_context *ctx,
uint32_t handle)
{
struct pipe_blend_state *state;
if (handle == 0) {
memset(&ctx->sub->blend_state, 0, sizeof(ctx->sub->blend_state));
vrend_blend_enable(ctx, false);
return;
}
state = vrend_object_looku... | 295,022,567,549,124,260,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,143 | 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_object_bind_dsa(struct vrend_context *ctx,
uint32_t handle)
{
struct pipe_depth_stencil_alpha_state *state;
if (handle == 0) {
memset(&ctx->sub->dsa_state, 0, sizeof(ctx->sub->dsa_state));
ctx->sub->dsa = NULL;
ctx->sub->stencil_state_dirty = true;
ct... | 280,012,840,369,346,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,144 | 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_object_bind_rasterizer(struct vrend_context *ctx,
uint32_t handle)
{
struct pipe_rasterizer_state *state;
if (handle == 0) {
memset(&ctx->sub->rs_state, 0, sizeof(ctx->sub->rs_state));
return;
}
state = vrend_object_lookup(ctx->sub->object_hash, han... | 281,314,392,634,331,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,145 | 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_patch_blend_state(struct vrend_context *ctx)
{
struct pipe_blend_state new_state = ctx->sub->blend_state;
struct pipe_blend_state *state = &ctx->sub->blend_state;
bool dest_alpha_only = false, dest_has_no_alpha = false;
struct pipe_blend_color blend_color = ctx->sub->blend_color;
int i;... | 287,220,626,125,414,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,146 | 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_pause_render_condition(struct vrend_context *ctx, bool pause)
{
if (pause) {
if (ctx->sub->cond_render_q_id)
glEndConditionalRenderNV();
} else {
if (ctx->sub->cond_render_q_id)
glBeginConditionalRender(ctx->sub->cond_render_q_id,
c... | 242,401,807,338,802,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,147 | 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_renderer_attach_res_ctx(int ctx_id, int resource_id)
{
struct vrend_context *ctx = vrend_lookup_renderer_ctx(ctx_id);
struct vrend_resource *res;
if (!ctx)
return;
res = vrend_resource_lookup(resource_id, 0);
if (!res)
return;
vrend_object_insert_nofree(ctx->res_hash, res, si... | 208,108,094,285,404,340,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,148 | 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_renderer_blit(struct vrend_context *ctx,
uint32_t dst_handle, uint32_t src_handle,
const struct pipe_blit_info *info)
{
struct vrend_resource *src_res, *dst_res;
src_res = vrend_renderer_ctx_res_lookup(ctx, src_handle);
dst_res = vrend_renderer_ctx_r... | 294,130,958,035,156,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,149 | 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_renderer_blit_int(struct vrend_context *ctx,
struct vrend_resource *src_res,
struct vrend_resource *dst_res,
const struct pipe_blit_info *info)
{
GLbitfield glmask = 0;
int src_y1, src_y2,... | 5,965,281,066,790,903,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,150 | 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_renderer_check_queries(void)
{
struct vrend_query *query, *stor;
if (!vrend_state.inited)
return;
LIST_FOR_EACH_ENTRY_SAFE(query, stor, &vrend_state.waiting_query_list, waiting_queries) {
vrend_hw_switch_context(vrend_lookup_renderer_ctx(query->ctx_id), true);
if (vrend_check_que... | 255,650,626,238,456,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,151 | 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_renderer_create_fence(int client_fence_id, uint32_t ctx_id)
{
struct vrend_fence *fence;
fence = malloc(sizeof(struct vrend_fence));
if (!fence)
return ENOMEM;
fence->ctx_id = ctx_id;
fence->fence_id = client_fence_id;
fence->syncobj = glFenceSync(GL_SYNC_GPU_COMMANDS_COMPLETE, 0);
... | 196,742,439,392,277,620,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,152 | 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_renderer_create_sub_ctx(struct vrend_context *ctx, int sub_ctx_id)
{
struct vrend_sub_context *sub;
struct virgl_gl_ctx_param ctx_params;
LIST_FOR_EACH_ENTRY(sub, &ctx->sub_ctxs, head) {
if (sub->sub_ctx_id == sub_ctx_id) {
return;
}
}
sub = CALLOC_STRUCT(vrend_sub_conte... | 65,007,740,014,028,960,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,153 | 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_resource *vrend_renderer_ctx_res_lookup(struct vrend_context *ctx, int res_handle)
{
struct vrend_resource *res = vrend_object_lookup(ctx->res_hash, res_handle, 1);
return res;
}
| 191,295,117,649,076,570,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,154 | 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_renderer_destroy_sub_ctx(struct vrend_context *ctx, int sub_ctx_id)
{
struct vrend_sub_context *sub, *tofree = NULL;
/* never destroy sub context id 0 */
if (sub_ctx_id == 0)
return;
LIST_FOR_EACH_ENTRY(sub, &ctx->sub_ctxs, head) {
if (sub->sub_ctx_id == sub_ctx_id) {
tofre... | 188,995,803,616,276,300,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,155 | 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_renderer_detach_res_ctx(int ctx_id, int res_handle)
{
struct vrend_context *ctx = vrend_lookup_renderer_ctx(ctx_id);
if (!ctx)
return;
vrend_renderer_detach_res_ctx_p(ctx, res_handle);
}
| 255,219,606,414,535,750,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,156 | 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_renderer_detach_res_ctx_p(struct vrend_context *ctx, int res_handle)
{
struct vrend_resource *res;
res = vrend_object_lookup(ctx->res_hash, res_handle, 1);
if (!res)
return;
vrend_object_remove(ctx->res_hash, res_handle, 1);
}
| 282,368,577,410,394,680,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,157 | 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_renderer_fill_caps(uint32_t set, uint32_t version,
union virgl_caps *caps)
{
int i;
GLint max;
int gl_ver = epoxy_gl_version();
if (!caps)
return;
memset(caps, 0, sizeof(*caps));
if (set != 1 && set != 0) {
caps->max_version = 0;
return;
... | 99,531,650,661,402,470,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,158 | 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 | vrend_renderer_fini(void)
{
if (!vrend_state.inited)
return;
vrend_free_sync_thread();
if (vrend_state.eventfd != -1) {
close(vrend_state.eventfd);
vrend_state.eventfd = -1;
}
vrend_decode_reset(false);
vrend_object_fini_resource_table();
vrend_decode_reset(true);
vrend_stat... | 173,592,311,132,449,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,159 | 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_renderer_force_ctx_0(void)
{
struct vrend_context *ctx0 = vrend_lookup_renderer_ctx(0);
vrend_state.current_ctx = NULL;
vrend_state.current_hw_ctx = NULL;
vrend_hw_switch_context(ctx0, true);
vrend_clicbs->make_current(0, ctx0->sub->gl_context);
}
| 257,707,483,883,739,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,160 | 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_renderer_get_cap_set(uint32_t cap_set, uint32_t *max_ver,
uint32_t *max_size)
{
if (cap_set != VREND_CAP_SET) {
*max_ver = 0;
*max_size = 0;
return;
}
*max_ver = 1;
*max_size = sizeof(union virgl_caps);
}
| 176,468,650,601,210,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,161 | 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_renderer_get_cursor_contents(uint32_t res_handle, uint32_t *width, uint32_t *height)
{
GLenum format, type;
struct vrend_resource *res;
int blsize;
char *data, *data2;
int size;
int h;
res = vrend_resource_lookup(res_handle, 0);
if (!res)
return NULL;
if (res->base.width0 ... | 97,179,869,061,741,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,162 | 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_renderer_get_poll_fd(void)
{
if (!vrend_state.inited)
return -1;
return vrend_state.eventfd;
}
| 338,443,353,637,629,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,163 | 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_renderer_get_rect(int res_handle, struct iovec *iov, unsigned int num_iovs,
uint32_t offset, int x, int y, int width, int height)
{
struct vrend_resource *res = vrend_resource_lookup(res_handle, 0);
struct vrend_transfer_info transfer_info;
struct pipe_box box;
int el... | 81,179,403,697,819,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,164 | 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 | GLint64 vrend_renderer_get_timestamp(void)
{
GLint64 v;
glGetInteger64v(GL_TIMESTAMP, &v);
return v;
}
| 272,768,473,370,522,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,165 | 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_renderer_init(struct vrend_if_cbs *cbs, uint32_t flags)
{
int gl_ver;
virgl_gl_context gl_context;
struct virgl_gl_ctx_param ctx_params;
if (!vrend_state.inited) {
vrend_state.inited = true;
vrend_object_init_resource_table();
vrend_clicbs = cbs;
}
ctx_params.shared = fal... | 122,182,282,329,448,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,166 | 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 | vrend_renderer_object_destroy(struct vrend_context *ctx, uint32_t handle)
{
vrend_object_remove(ctx->sub->object_hash, handle, 0);
}
| 305,590,750,147,032,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,167 | 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 | uint32_t vrend_renderer_object_insert(struct vrend_context *ctx, void *data,
uint32_t size, uint32_t handle, enum virgl_object_type type)
{
return vrend_object_insert(ctx->sub->object_hash, data, size, handle, type);
}
| 88,173,248,568,328,340,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,168 | 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_renderer_reset(void)
{
if (vrend_state.sync_thread) {
vrend_free_sync_thread();
vrend_state.stop_sync_thread = false;
}
vrend_reset_fences();
vrend_decode_reset(false);
vrend_object_fini_resource_table();
vrend_decode_reset(true);
vrend_object_init_resource_table();
vrend_... | 7,434,954,354,082,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,169 | 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_renderer_resource_attach_iov(int res_handle, struct iovec *iov,
int num_iovs)
{
struct vrend_resource *res;
res = vrend_resource_lookup(res_handle, 0);
if (!res)
return EINVAL;
if (res->iov)
return 0;
/* work out size and max resource size *... | 184,598,739,807,978,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,170 | 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_renderer_resource_copy_region(struct vrend_context *ctx,
uint32_t dst_handle, uint32_t dst_level,
uint32_t dstx, uint32_t dsty, uint32_t dstz,
uint32_t src_handle, uint32_t src_level,
... | 143,081,637,137,860,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,171 | 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_renderer_resource_create(struct vrend_renderer_resource_create_args *args, struct iovec *iov, uint32_t num_iovs)
{
struct vrend_resource *gr;
int level;
int ret;
ret = check_resource_valid(args);
if (ret)
return EINVAL;
gr = (struct vrend_resource *)CALLOC_STRUCT(vrend_texture);
i... | 310,440,683,672,518,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,172 | 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_renderer_resource_destroy(struct vrend_resource *res, bool remove)
{
if (res->readback_fb_id)
glDeleteFramebuffers(1, &res->readback_fb_id);
if (res->ptr)
free(res->ptr);
if (res->id) {
if (res->target == GL_ELEMENT_ARRAY_BUFFER_ARB ||
res->target == GL_ARRAY_BUFFER_ARB ... | 95,283,584,350,327,090,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,173 | 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_renderer_resource_detach_iov(int res_handle,
struct iovec **iov_p,
int *num_iovs_p)
{
struct vrend_resource *res;
res = vrend_resource_lookup(res_handle, 0);
if (!res) {
return;
}
if (iov_p)
*iov_p = re... | 204,515,471,668,978,330,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,174 | 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_renderer_resource_unref(uint32_t res_handle)
{
struct vrend_resource *res;
struct vrend_context *ctx;
res = vrend_resource_lookup(res_handle, 0);
if (!res)
return;
/* find in all contexts and detach also */
/* remove from any contexts */
LIST_FOR_EACH_ENTRY(ctx, &vrend_state.act... | 327,643,283,834,888,330,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,175 | 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_renderer_set_sub_ctx(struct vrend_context *ctx, int sub_ctx_id)
{
struct vrend_sub_context *sub;
/* find the sub ctx */
if (ctx->sub && ctx->sub->sub_ctx_id == sub_ctx_id)
return;
LIST_FOR_EACH_ENTRY(sub, &ctx->sub_ctxs, head) {
if (sub->sub_ctx_id == sub_ctx_id) {
ctx->sub... | 256,549,908,463,984,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,176 | 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_renderer_transfer_send_iov(struct vrend_context *ctx,
struct vrend_resource *res,
struct iovec *iov, int num_iovs,
const struct vrend_transfer_info *info)
{
if (res->ta... | 213,920,107,212,556,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,177 | 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_renderer_transfer_write_iov(struct vrend_context *ctx,
struct vrend_resource *res,
struct iovec *iov, int num_iovs,
const struct vrend_transfer_info *info)
{
void *d... | 108,529,665,280,130,630,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,178 | 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_renderer_use_threaded_sync(void)
{
struct virgl_gl_ctx_param ctx_params;
if (getenv("VIRGL_DISABLE_MT"))
return;
ctx_params.shared = true;
ctx_params.major_ver = vrend_state.gl_major_ver;
ctx_params.minor_ver = vrend_state.gl_minor_ver;
vrend_state.stop_sync_thread = false;
... | 46,232,961,006,885,470,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,179 | 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_renderer_use_threaded_sync(void)
{
}
| 80,639,234,999,454,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,180 | 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_report_buffer_error(struct vrend_context *ctx, int cmd)
{
report_context_error(ctx, VIRGL_ERROR_CTX_ILLEGAL_CMD_BUFFER, cmd);
}
| 319,377,214,922,662,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,181 | 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_reset_fences(void)
{
struct vrend_fence *fence, *stor;
if (vrend_state.sync_thread)
pipe_mutex_lock(vrend_state.fence_mutex);
LIST_FOR_EACH_ENTRY_SAFE(fence, stor, &vrend_state.fence_list, fences) {
free_fence_locked(fence);
}
if (vrend_state.sync_thread)
pipe_mutex... | 131,458,194,250,853,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,182 | 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_resource_buffer_copy(struct vrend_context *ctx,
struct vrend_resource *src_res,
struct vrend_resource *dst_res,
uint32_t dstx, uint32_t srcx,
uint... | 106,188,525,658,441,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,183 | 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_resource_copy_fallback(struct vrend_context *ctx,
struct vrend_resource *src_res,
struct vrend_resource *dst_res,
uint32_t dst_level,
uint... | 125,178,718,706,626,630,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,184 | 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 | vrend_sampler_view_reference(struct vrend_sampler_view **ptr, struct vrend_sampler_view *view)
{
struct vrend_sampler_view *old_view = *ptr;
if (pipe_reference(&(*ptr)->reference, &view->reference))
vrend_destroy_sampler_view(old_view);
*ptr = view;
}
| 218,818,890,876,491,560,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,185 | 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_scale_depth(void *ptr, int size, float scale_val)
{
GLuint *ival = ptr;
const GLfloat myscale = 1.0f / 0xffffff;
int i;
for (i = 0; i < size / 4; i++) {
GLuint value = ival[i];
GLfloat d = ((float)(value >> 8) * myscale) * scale_val;
d = CLAMP(d, 0.0F, 1.0F);
ival[i... | 200,584,424,546,728,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,186 | 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_set_blend_color(struct vrend_context *ctx,
struct pipe_blend_color *color)
{
ctx->sub->blend_color = *color;
glBlendColor(color->color[0], color->color[1], color->color[2],
color->color[3]);
}
| 184,919,234,598,292,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,187 | 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_set_clip_state(struct vrend_context *ctx, struct pipe_clip_state *ucp)
{
if (vrend_state.use_core_profile) {
ctx->sub->ucp_state = *ucp;
} else {
int i, j;
GLdouble val[4];
for (i = 0; i < 8; i++) {
for (j = 0; j < 4; j++)
val[j] = ucp->ucp[i][j];
... | 138,914,496,878,891,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,188 | 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_set_constants(struct vrend_context *ctx,
uint32_t shader,
uint32_t index,
uint32_t num_constant,
float *data)
{
struct vrend_constants *consts;
int i;
consts = &ctx->sub->consts[shader];
ctx->sub-... | 142,251,723,118,231,180,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,189 | 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_set_framebuffer_state(struct vrend_context *ctx,
uint32_t nr_cbufs, uint32_t surf_handle[PIPE_MAX_COLOR_BUFS],
uint32_t zsurf_handle)
{
struct vrend_surface *surf, *zsurf;
int i;
int old_num;
GLenum status;
GLint new_height = -1... | 116,178,415,820,268,430,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,190 | 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_set_index_buffer(struct vrend_context *ctx,
uint32_t res_handle,
uint32_t index_size,
uint32_t offset)
{
struct vrend_resource *res;
ctx->sub->ib.index_size = index_size;
ctx->sub->ib.offset = offset;
if (res_han... | 196,246,954,026,724,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,191 | 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_set_num_sampler_views(struct vrend_context *ctx,
uint32_t shader_type,
uint32_t start_slot,
int num_sampler_views)
{
if (start_slot + num_sampler_views < ctx->sub->views[shader_type].num_views) {
int i... | 122,360,346,639,651,190,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,192 | 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_set_num_vbo(struct vrend_context *ctx,
int num_vbo)
{
int old_num = ctx->sub->num_vbos;
int i;
ctx->sub->num_vbos = num_vbo;
ctx->sub->old_num_vbos = old_num;
if (old_num != num_vbo)
ctx->sub->vbo_dirty = true;
for (i = num_vbo; i < old_num; i++) {
vren... | 193,175,970,998,319,970,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,193 | 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_set_polygon_stipple(struct vrend_context *ctx,
struct pipe_poly_stipple *ps)
{
if (vrend_state.use_core_profile) {
static const unsigned bit31 = 1 << 31;
GLubyte *stip = calloc(1, 1024);
int i, j;
if (!ctx->pstip_inited)
vrend_init_pstipple_... | 15,926,015,979,332,342,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,194 | 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_set_sample_mask(struct vrend_context *ctx, unsigned sample_mask)
{
glSampleMaski(0, sample_mask);
}
| 183,897,519,816,553,630,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,195 | 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_set_scissor_state(struct vrend_context *ctx,
uint32_t start_slot,
uint32_t num_scissor,
struct pipe_scissor_state *ss)
{
int i, idx;
if (start_slot > PIPE_MAX_VIEWPORTS ||
num_scissor > (PIPE_MAX_VIEWPORTS - ... | 72,182,741,543,292,240,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,196 | 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_set_single_sampler_view(struct vrend_context *ctx,
uint32_t shader_type,
int index,
uint32_t handle)
{
struct vrend_sampler_view *view = NULL;
struct vrend_texture *tex;
if (handle) {
view... | 69,774,322,620,589,820,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,197 | 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_set_single_vbo(struct vrend_context *ctx,
int index,
uint32_t stride,
uint32_t buffer_offset,
uint32_t res_handle)
{
struct vrend_resource *res;
if (ctx->sub->vbo[index].stride != stride ||
c... | 62,508,674,063,491,710,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,198 | 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_set_stencil_ref(struct vrend_context *ctx,
struct pipe_stencil_ref *ref)
{
if (ctx->sub->stencil_refs[0] != ref->ref_value[0] ||
ctx->sub->stencil_refs[1] != ref->ref_value[1]) {
ctx->sub->stencil_refs[0] = ref->ref_value[0];
ctx->sub->stencil_refs[1] = ref->r... | 172,426,444,017,596,240,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,199 | 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_set_streamout_targets(struct vrend_context *ctx,
uint32_t append_bitmask,
uint32_t num_targets,
uint32_t *handles)
{
struct vrend_so_target *target;
int i;
if (num_targets) {
bool found = false;... | 97,202,188,249,457,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,200 | 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_set_uniform_buffer(struct vrend_context *ctx,
uint32_t shader,
uint32_t index,
uint32_t offset,
uint32_t length,
uint32_t res_handle)
{
struct vrend_resourc... | 310,506,596,659,820,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,201 | virglrenderer | a2f12a1b0f95b13b6f8dc3d05d7b74b4386394e4 | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=a2f12a1b0f95b13b6f8dc3d05d7b74b4386394e4 | renderer: fix memory leak in add shader program
Free 'sprog' in error path to avoid memory leak.
Signed-off-by: Li Qiang <liq3ea@gmail.com>
Signed-off-by: Dave Airlie <airlied@redhat.com> | 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... | 90,675,852,073,179,820,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-6317 | Memory leak in the add_shader_program function in vrend_renderer.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (host memory consumption) via vectors involving the sprog variable. | https://nvd.nist.gov/vuln/detail/CVE-2017-6317 |
16,202 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static inline uint32_t get_buf_entry(struct vrend_decode_ctx *ctx, uint32_t offset)
{
return ctx->ds->buf[ctx->ds->buf_offset + offset];
}
| 32,419,485,451,690,320,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,203 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static inline void *get_buf_ptr(struct vrend_decode_ctx *ctx,
uint32_t offset)
{
return &ctx->ds->buf[ctx->ds->buf_offset + offset];
}
| 263,756,263,122,968,160,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,204 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static float uif(unsigned int ui)
{
union { float f; unsigned int ui; } myuif;
myuif.ui = ui;
return myuif.f;
}
| 213,972,007,199,642,230,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,205 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_begin_query(struct vrend_decode_ctx *ctx, int length)
{
if (length != 1)
return EINVAL;
uint32_t handle = get_buf_entry(ctx, VIRGL_QUERY_BEGIN_HANDLE);
vrend_begin_query(ctx->grctx, handle);
return 0;
}
| 261,162,820,332,327,000,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,206 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_bind_object(struct vrend_decode_ctx *ctx, uint16_t length)
{
if (length != 1)
return EINVAL;
uint32_t header = get_buf_entry(ctx, VIRGL_OBJ_BIND_HEADER);
uint32_t handle = get_buf_entry(ctx, VIRGL_OBJ_BIND_HANDLE);
uint8_t obj_type = (header >> 8) & 0xff;
switch (obj_type)... | 45,934,015,913,914,520,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,207 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_bind_sampler_states(struct vrend_decode_ctx *ctx, int length)
{
if (length < 2)
return EINVAL;
uint32_t shader_type = get_buf_entry(ctx, VIRGL_BIND_SAMPLER_STATES_SHADER_TYPE);
uint32_t start_slot = get_buf_entry(ctx, VIRGL_BIND_SAMPLER_STATES_START_SLOT);
uint32_t num_states ... | 334,068,791,851,453,600,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,208 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_bind_shader(struct vrend_decode_ctx *ctx, int length)
{
uint32_t handle, type;
if (length != VIRGL_BIND_SHADER_SIZE)
return EINVAL;
handle = get_buf_entry(ctx, VIRGL_BIND_SHADER_HANDLE);
type = get_buf_entry(ctx, VIRGL_BIND_SHADER_TYPE);
vrend_bind_shader(ctx->grctx, handl... | 262,296,693,155,790,500,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,209 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_blit(struct vrend_decode_ctx *ctx, int length)
{
struct pipe_blit_info info;
uint32_t dst_handle, src_handle, temp;
if (length != VIRGL_CMD_BLIT_SIZE)
return EINVAL;
temp = get_buf_entry(ctx, VIRGL_CMD_BLIT_S0);
info.mask = temp & 0xff;
info.filter = (temp >> 8) & 0x3;
... | 206,135,415,445,995,400,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,210 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | int vrend_decode_block(uint32_t ctx_id, uint32_t *block, int ndw)
{
struct vrend_decode_ctx *gdctx;
bool bret;
int ret;
if (ctx_id >= VREND_MAX_CTX)
return EINVAL;
if (dec_ctx[ctx_id] == NULL)
return EINVAL;
gdctx = dec_ctx[ctx_id];
bret = vrend_hw_switch_context(gdctx->grctx, true);... | 153,820,514,952,150,780,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,211 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_clear(struct vrend_decode_ctx *ctx, int length)
{
union pipe_color_union color;
double depth;
unsigned stencil, buffers;
int i;
if (length != VIRGL_OBJ_CLEAR_SIZE)
return EINVAL;
buffers = get_buf_entry(ctx, VIRGL_OBJ_CLEAR_BUFFERS);
for (i = 0; i < 4; i++)
colo... | 102,715,618,151,186,770,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,212 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_create_blend(struct vrend_decode_ctx *ctx, uint32_t handle, uint16_t length)
{
struct pipe_blend_state *blend_state;
uint32_t tmp;
int i;
if (length != VIRGL_OBJ_BLEND_SIZE) {
return EINVAL;
}
blend_state = CALLOC_STRUCT(pipe_blend_state);
if (!blend_state)
ret... | 151,964,231,845,521,430,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,213 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_create_dsa(struct vrend_decode_ctx *ctx, uint32_t handle, uint16_t length)
{
int i;
struct pipe_depth_stencil_alpha_state *dsa_state;
uint32_t tmp;
if (length != VIRGL_OBJ_DSA_SIZE)
return EINVAL;
dsa_state = CALLOC_STRUCT(pipe_depth_stencil_alpha_state);
if (!dsa_state... | 105,027,334,576,595,800,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,214 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_create_object(struct vrend_decode_ctx *ctx, int length)
{
if (length < 1)
return EINVAL;
uint32_t header = get_buf_entry(ctx, VIRGL_OBJ_CREATE_HEADER);
uint32_t handle = get_buf_entry(ctx, VIRGL_OBJ_CREATE_HANDLE);
uint8_t obj_type = (header >> 8) & 0xff;
int ret = 0;
i... | 316,414,197,598,373,480,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,215 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_create_query(struct vrend_decode_ctx *ctx, uint32_t handle, uint16_t length)
{
uint32_t query_type;
uint32_t query_index;
uint32_t res_handle;
uint32_t offset;
uint32_t tmp;
if (length != VIRGL_OBJ_QUERY_SIZE)
return EINVAL;
tmp = get_buf_entry(ctx, VIRGL_OBJ_QUERY_T... | 248,373,186,044,193,300,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,216 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_create_rasterizer(struct vrend_decode_ctx *ctx, uint32_t handle, uint16_t length)
{
struct pipe_rasterizer_state *rs_state;
uint32_t tmp;
if (length != VIRGL_OBJ_RS_SIZE)
return EINVAL;
rs_state = CALLOC_STRUCT(pipe_rasterizer_state);
if (!rs_state)
return ENOMEM;
... | 263,694,757,642,323,700,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,217 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_create_sampler_state(struct vrend_decode_ctx *ctx, uint32_t handle, uint16_t length)
{
struct pipe_sampler_state state;
int i;
uint32_t tmp;
if (length != VIRGL_OBJ_SAMPLER_STATE_SIZE)
return EINVAL;
tmp = get_buf_entry(ctx, VIRGL_OBJ_SAMPLER_STATE_S0);
state.wrap_s = tm... | 145,847,363,990,917,790,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,218 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_create_sampler_view(struct vrend_decode_ctx *ctx, uint32_t handle, uint16_t length)
{
uint32_t res_handle, format, val0, val1, swizzle_packed;
if (length != VIRGL_OBJ_SAMPLER_VIEW_SIZE)
return EINVAL;
res_handle = get_buf_entry(ctx, VIRGL_OBJ_SAMPLER_VIEW_RES_HANDLE);
format ... | 295,903,250,356,839,050,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,219 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_create_shader(struct vrend_decode_ctx *ctx,
uint32_t handle,
uint16_t length)
{
struct pipe_stream_output_info so_info;
int i, ret;
uint32_t shader_offset;
unsigned num_tokens, num_so_outputs, offlen;
uint... | 111,439,815,067,170,730,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,220 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_create_stream_output_target(struct vrend_decode_ctx *ctx, uint32_t handle, uint16_t length)
{
uint32_t res_handle, buffer_size, buffer_offset;
if (length != VIRGL_OBJ_STREAMOUT_SIZE)
return EINVAL;
res_handle = get_buf_entry(ctx, VIRGL_OBJ_STREAMOUT_RES_HANDLE);
buffer_offset... | 293,651,333,347,139,550,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,221 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_create_sub_ctx(struct vrend_decode_ctx *ctx, int length)
{
if (length != 1)
return EINVAL;
uint32_t ctx_sub_id = get_buf_entry(ctx, 1);
vrend_renderer_create_sub_ctx(ctx->grctx, ctx_sub_id);
return 0;
}
| 90,918,197,582,153,680,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,222 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_create_surface(struct vrend_decode_ctx *ctx, uint32_t handle, uint16_t length)
{
uint32_t res_handle, format, val0, val1;
int ret;
if (length != VIRGL_OBJ_SURFACE_SIZE)
return EINVAL;
res_handle = get_buf_entry(ctx, VIRGL_OBJ_SURFACE_RES_HANDLE);
format = get_buf_entry(ctx... | 263,294,198,854,748,700,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,223 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_create_ve(struct vrend_decode_ctx *ctx, uint32_t handle, uint16_t length)
{
struct pipe_vertex_element *ve = NULL;
int num_elements;
int i;
int ret;
if (length < 1)
return EINVAL;
if ((length - 1) % 4)
return EINVAL;
num_elements = (length - 1) / 4;
if (nu... | 299,027,673,952,819,000,000,000,000,000,000,000,000 | vrend_decode.c | 320,493,338,135,670,100,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,224 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_destroy_object(struct vrend_decode_ctx *ctx, int length)
{
if (length != 1)
return EINVAL;
uint32_t handle = get_buf_entry(ctx, VIRGL_OBJ_DESTROY_HANDLE);
vrend_renderer_object_destroy(ctx->grctx, handle);
return 0;
}
| 69,580,039,304,519,550,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,225 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_draw_vbo(struct vrend_decode_ctx *ctx, int length)
{
struct pipe_draw_info info;
uint32_t cso;
if (length != VIRGL_DRAW_VBO_SIZE)
return EINVAL;
memset(&info, 0, sizeof(struct pipe_draw_info));
info.start = get_buf_entry(ctx, VIRGL_DRAW_VBO_START);
info.count = get_buf_e... | 192,985,478,648,532,640,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,226 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_end_query(struct vrend_decode_ctx *ctx, int length)
{
if (length != 1)
return EINVAL;
uint32_t handle = get_buf_entry(ctx, VIRGL_QUERY_END_HANDLE);
vrend_end_query(ctx->grctx, handle);
return 0;
}
| 313,679,727,749,472,360,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,227 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_get_query_result(struct vrend_decode_ctx *ctx, int length)
{
if (length != 2)
return EINVAL;
uint32_t handle = get_buf_entry(ctx, VIRGL_QUERY_RESULT_HANDLE);
uint32_t wait = get_buf_entry(ctx, VIRGL_QUERY_RESULT_WAIT);
vrend_get_query_result(ctx->grctx, handle, wait);
retu... | 75,205,192,536,116,610,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,228 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | void vrend_decode_reset(bool ctx_0_only)
{
int i;
vrend_hw_switch_context(dec_ctx[0]->grctx, true);
if (ctx_0_only == false) {
for (i = 1; i < VREND_MAX_CTX; i++) {
if (!dec_ctx[i])
continue;
if (!dec_ctx[i]->grctx)
continue;
vrend_destroy_context(de... | 255,618,711,974,961,980,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,229 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_resource_copy_region(struct vrend_decode_ctx *ctx, int length)
{
struct pipe_box box;
uint32_t dst_handle, src_handle;
uint32_t dst_level, dstx, dsty, dstz;
uint32_t src_level;
if (length != VIRGL_CMD_RESOURCE_COPY_REGION_SIZE)
return EINVAL;
dst_handle = get_buf_entry(... | 333,450,520,017,244,800,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,230 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_resource_inline_write(struct vrend_decode_ctx *ctx, uint16_t length)
{
struct vrend_transfer_info info;
struct pipe_box box;
uint32_t res_handle;
uint32_t level, usage, stride, layer_stride, data_len;
struct iovec dataiovec;
void *data;
if (length < 12)
return EINVAL;... | 32,681,065,364,479,833,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,231 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_set_blend_color(struct vrend_decode_ctx *ctx, int length)
{
struct pipe_blend_color color;
int i;
if (length != VIRGL_SET_BLEND_COLOR_SIZE)
return EINVAL;
for (i = 0; i < 4; i++)
color.color[i] = uif(get_buf_entry(ctx, VIRGL_SET_BLEND_COLOR(i)));
vrend_set_blend_col... | 121,876,721,096,764,460,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,232 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_set_clip_state(struct vrend_decode_ctx *ctx, int length)
{
struct pipe_clip_state clip;
int i, j;
if (length != VIRGL_SET_CLIP_STATE_SIZE)
return EINVAL;
for (i = 0; i < 8; i++)
for (j = 0; j < 4; j++)
clip.ucp[i][j] = uif(get_buf_entry(ctx, VIRGL_SET_CLIP_STAT... | 91,914,391,052,597,670,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,233 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_set_constant_buffer(struct vrend_decode_ctx *ctx, uint16_t length)
{
uint32_t shader;
uint32_t index;
int nc = (length - 2);
if (length < 2)
return EINVAL;
shader = get_buf_entry(ctx, VIRGL_SET_CONSTANT_BUFFER_SHADER_TYPE);
index = get_buf_entry(ctx, VIRGL_SET_CONSTANT_... | 124,201,968,531,136,920,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,234 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_set_framebuffer_state(struct vrend_decode_ctx *ctx, int length)
{
if (length < 2)
return EINVAL;
uint32_t nr_cbufs = get_buf_entry(ctx, VIRGL_SET_FRAMEBUFFER_STATE_NR_CBUFS);
uint32_t zsurf_handle = get_buf_entry(ctx, VIRGL_SET_FRAMEBUFFER_STATE_NR_ZSURF_HANDLE);
uint32_t surf... | 86,408,269,789,452,760,000,000,000,000,000,000,000 | vrend_decode.c | 320,493,338,135,670,100,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,235 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_set_index_buffer(struct vrend_decode_ctx *ctx, int length)
{
if (length != 1 && length != 3)
return EINVAL;
vrend_set_index_buffer(ctx->grctx,
get_buf_entry(ctx, VIRGL_SET_INDEX_BUFFER_HANDLE),
(length == 3) ? get_buf_entry(ctx, VIR... | 232,224,722,574,989,560,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
16,236 | virglrenderer | 0a5dff15912207b83018485f83e067474e818bab | https://gitlab.freedesktop.org/virgl/virglrenderer | https://cgit.freedesktop.org/virglrenderer/commit/?id=0a5dff15912207b83018485f83e067474e818bab | vrend: never destroy context 0 in vrend_renderer_context_destroy
There will be a crash if the guest destroy context 0. As the context 0 is
allocate in renderer init, not destroy in vrend_renderer_context_destroy.
The context will be freed in renderer fini by calling vrend_decode_reset.
Signed-off-by: Li Qiang <liq3ea... | 0 | static int vrend_decode_set_render_condition(struct vrend_decode_ctx *ctx, int length)
{
if (length != VIRGL_RENDER_CONDITION_SIZE)
return EINVAL;
uint32_t handle = get_buf_entry(ctx, VIRGL_RENDER_CONDITION_HANDLE);
bool condition = get_buf_entry(ctx, VIRGL_RENDER_CONDITION_CONDITION) & 1;
uint mode ... | 107,996,433,528,763,450,000,000,000,000,000,000,000 | vrend_decode.c | 142,230,531,657,531,470,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-6210 | The vrend_decode_reset function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (NULL pointer dereference and QEMU process crash) by destroying context 0 (zero). | https://nvd.nist.gov/vuln/detail/CVE-2017-6210 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.