CVE-2024-45111
Vie, 13/09/2024 – 09:15
CVE-2024-45111
CVE-2024-45111
Vie, 13/09/2024 – 09:15
CVE-2024-45111
CVE-2024-6656
Vie, 13/09/2024 – 09:15
CVE-2024-6656
CVE-2024-41874
Vie, 13/09/2024 – 10:15
CVE-2024-41874
CVE-2024-43756
Vie, 13/09/2024 – 10:15
CVE-2024-43756
CVE-2024-45108
Vie, 13/09/2024 – 10:15
CVE-2024-45108
CVE-2024-43760
Vie, 13/09/2024 – 10:15
CVE-2024-43760
CVE-2024-45113
Vie, 13/09/2024 – 10:15
CVE-2024-45113
CVE-2024-45109
Vie, 13/09/2024 – 10:15
CVE-2024-45109
CVE-2024-46711
Vie, 13/09/2024 – 07:15
CVE-2024-46711
mptcp: pm: fix ID 0 endp usage after multiple re-creations
'local_addr_used' and 'add_addr_accepted' are decremented for addresses
not related to the initial subflow (ID0), because the source and
destination addresses of the initial subflows are known from the
beginning: they don't count as "additional local address being used" or
"ADD_ADDR being accepted".
It is then required not to increment them when the entrypoint used by
the initial subflow is removed and re-added during a connection. Without
this modification, this entrypoint cannot be removed and re-added more
than once.
CVE-2024-46710
Vie, 13/09/2024 – 07:15
CVE-2024-46710
drm/vmwgfx: Prevent unmapping active read buffers
The kms paths keep a persistent map active to read and compare the cursor
buffer. These maps can race with each other in simple scenario where:
a) buffer "a" mapped for update
b) buffer "a" mapped for compare
c) do the compare
d) unmap "a" for compare
e) update the cursor
f) unmap "a" for update
At step "e" the buffer has been unmapped and the read contents is bogus.
Prevent unmapping of active read buffers by simply keeping a count of
how many paths have currently active maps and unmap only when the count
reaches 0.