7

CVE-2023-52847

media: bttv: fix use after free error due to btv->timeout timer

In the Linux kernel, the following vulnerability has been resolved:

media: bttv: fix use after free error due to btv->timeout timer

There may be some a race condition between timer function
bttv_irq_timeout and bttv_remove. The timer is setup in
probe and there is no timer_delete operation in remove
function. When it hit kfree btv, the function might still be
invoked, which will cause use after free bug.

This bug is found by static analysis, it may be false positive.

Fix it by adding del_timer_sync invoking to the remove function.

cpu0                cpu1
                  bttv_probe
                    ->timer_setup
                      ->bttv_set_dma
                        ->mod_timer;
bttv_remove
  ->kfree(btv);
                  ->bttv_irq_timeout
                    ->USE btv
Daten sind bereitgestellt durch National Vulnerability Database (NVD)
Linux ≫ Linux Kernel Version >= 4.15 < 4.19.299
Linux ≫ Linux Kernel Version >= 4.20 < 5.4.261
Linux ≫ Linux Kernel Version >= 5.5 < 5.10.201
Linux ≫ Linux Kernel Version >= 5.11 < 5.15.139
Linux ≫ Linux Kernel Version >= 5.16 < 6.1.63
Linux ≫ Linux Kernel Version >= 6.2 < 6.5.12
Linux ≫ Linux Kernel Version >= 6.6 < 6.6.2
VulnDex Vulnerability Enrichment
Diese Information steht angemeldeten Benutzern zur Verfügung. Login Login
Zu dieser CVE wurde keine Warnung gefunden.
EPSS Metriken
Typ Quelle Score Percentile
EPSS FIRST.org 0.18% 0.08
CVSS Metriken
Quelle Base Score Exploit Score Impact Score Vector String
nvd@nist.gov 7 1 5.9
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

CWE-416 Use After Free

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

https://git.kernel.org/stable/c/1871014d6ef4812ad11ef7d838d73ce09d632267
Patch
Mailing List
https://git.kernel.org/stable/c/20568d06f6069cb835e05eed432edf962645d226
Patch
Mailing List
https://git.kernel.org/stable/c/2f3d9198cdae1cb079ec8652f4defacd481eab2b
Patch
Mailing List
https://git.kernel.org/stable/c/51c94256a83fe4e17406c66ff3e1ad7d242d8574
Patch
Mailing List
https://git.kernel.org/stable/c/847599fffa528b2cdec4e21b6bf7586dad982132
Patch
Mailing List
https://git.kernel.org/stable/c/b35fdade92c5058a5e727e233fe263b828de2c9a
Patch
Mailing List
https://git.kernel.org/stable/c/bbc3b8dd2cb7817e703f112d988e4f4728f0f2a9
Patch
Mailing List
https://git.kernel.org/stable/c/bd5b50b329e850d467e7bcc07b2b6bde3752fbda
Patch
Mailing List