Back to bug 2215837

Who When What Removed Added
TEJ RATHI 2023-06-19 07:06:06 UTC CC acaringi, allarkin, bhu, chwhite, dbohanno, ddepaula, debarbos, dfreiber, dvlasenk, ezulian, hkrzesin, jarod, jburrell, jdenham, jfaracco, jferlan, jforbes, jlelli, joe.lawrence, jshortt, jstancek, jwyatt, kcarcia, kernel-mgr, ldoskova, lgoncalv, lleshchi, lzampier, nmurray, ptalbert, qzhao, rogbas, rrobaina, rvrbovsk, rysulliv, scweaver, swood, tyberry, vkumar, walters, wcosta, williams, wmealing, ycote, ymankad
TEJ RATHI 2023-06-19 07:38:45 UTC Blocks 2215849
TEJ RATHI 2023-06-19 11:05:45 UTC Depends On 2215906, 2215907
TEJ RATHI 2023-06-19 11:19:37 UTC Depends On 2215914
Mauro Matteo Cascella 2023-06-20 09:00:06 UTC Summary TRIAGE-CVE-2023-35825 kernel: use-after-free was found in r592_remove in drivers/memstick/host/r592.c CVE-2023-35825 kernel: r592: race condition leading to use-after-free in r592_remove()
Alias TRIAGE-CVE-2023-35825 CVE-2023-35825
Mauro Matteo Cascella 2023-06-20 09:27:44 UTC Fixed In Version kernel 6.4-rc1
Mauro Matteo Cascella 2023-06-20 10:14:05 UTC Depends On 2216153, 2216152
Mauro Matteo Cascella 2023-06-20 10:56:32 UTC Doc Text A race condition vulnerability was found in the Linux kernel's r592 device driver when removing the module before cleanup in the r592_remove function. This flaw can eventually result in a use-after-free issue, possibly leading to a system crash or other undefined behaviors.
Paige Jung 2023-06-20 14:08:11 UTC Doc Text A race condition vulnerability was found in the Linux kernel's r592 device driver when removing the module before cleanup in the r592_remove function. This flaw can eventually result in a use-after-free issue, possibly leading to a system crash or other undefined behaviors. A race condition was found in the Linux kernel's r592 device driver, when removing the module before cleanup in the r592_remove function. This can result in a use-after-free issue, possibly leading to a system crash or other undefined behaviors.
Red Hat Bugzilla 2023-07-07 08:35:03 UTC Assignee security-response-team nobody

Back to bug 2215837