Bug 2282615 (CVE-2023-52707)

Summary: CVE-2023-52707 kernel: sched/psi: Fix use-after-free in ep_remove_wait_queue()
Product: [Other] Security Response Reporter: Mauro Matteo Cascella <mcascell>
Component: vulnerabilityAssignee: Product Security <prodsec-ir-bot>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: acaringi, allarkin, aquini, bhu, chwhite, cye, cyin, dbohanno, debarbos, dfreiber, drow, dvlasenk, esandeen, ezulian, hkrzesin, jarod, jburrell, jdenham, jfaracco, jlelli, joe.lawrence, jshortt, jstancek, jwyatt, kcarcia, ldoskova, lgoncalv, lzampier, mleitner, mmilgram, mstowell, nmurray, pauld, ptalbert, rparrazo, rrobaina, rvrbovsk, rysulliv, scweaver, sidakwo, sukulkar, tglozar, tyberry, vkumar, wcosta, williams, wmealing, ycote, ykopkova, zhijwang
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: kernel 5.4.232, kernel 5.10.169, kernel 5.15.95, kernel 6.1.13, kernel 6.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2282865    

Description Mauro Matteo Cascella 2024-05-22 16:33:20 UTC
In the Linux kernel, the following vulnerability has been resolved:

sched/psi: Fix use-after-free in ep_remove_wait_queue()

The Linux kernel CVE team has assigned CVE-2023-52707 to this issue.

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024052158-CVE-2023-52707-e048@gregkh/T

Comment 5 Alex 2024-06-09 17:19:13 UTC
The result of automatic check (that is developed by Alexander Larkin) for this CVE-2023-52707 is: CHECK	Maybe valid. Check manually. with impact LOW (that is an approximation based on flags KASAN UAF DMAorINTERRUPT HARDWARE  ; these flags parsed automatically based on patch data). Such automatic check happens only for Low/Moderates (and only when not from reporter, but parsing already existing CVE). Highs always checked manually (I check it myself and then we check it again in Remediation team). In rare cases some of the Moderates could be increased to High later.

Comment 11 Alex 2024-06-10 11:16:22 UTC
In reply to comment #5:
> The result of automatic check (that is developed by Alexander Larkin) for
> this CVE-2023-52707 is: CHECK	Maybe valid. Check manually. with impact LOW
> (that is an approximation based on flags KASAN UAF DMAorINTERRUPT HARDWARE 
> ; these flags parsed automatically based on patch data). Such automatic
> check happens only for Low/Moderates (and only when not from reporter, but
> parsing already existing CVE). Highs always checked manually (I check it
> myself and then we check it again in Remediation team). In rare cases some
> of the Moderates could be increased to High later.

Changed from Low to Moderate manually (based on that potentially UAF and attack complexity high).

Comment 22 errata-xmlrpc 2024-07-24 13:12:18 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.2 Extended Update Support

Via RHSA-2024:4823 https://access.redhat.com/errata/RHSA-2024:4823

Comment 23 errata-xmlrpc 2024-07-24 13:24:24 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.2 Extended Update Support

Via RHSA-2024:4831 https://access.redhat.com/errata/RHSA-2024:4831

Comment 24 errata-xmlrpc 2024-08-08 04:43:58 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2024:5102 https://access.redhat.com/errata/RHSA-2024:5102

Comment 25 errata-xmlrpc 2024-08-08 04:55:32 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2024:5101 https://access.redhat.com/errata/RHSA-2024:5101