Bug 2270084 (CVE-2023-52619)

Summary:	CVE-2023-52619 kernel: pstore/ram: Fix crash when setting number of cpus to an odd number
Product:	[Other] Security Response	Reporter:	Zack Miele <zmiele>
Component:	vulnerability	Assignee:	Product Security <prodsec-ir-bot>
Status:	NEW ---	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	acaringi, allarkin, aquini, bhu, chwhite, cye, cyin, dbohanno, debarbos, dfreiber, drow, dvlasenk, esandeen, ezulian, hkrzesin, jarod, jburrell, jdenham, jfaracco, jforbes, jlelli, joe.lawrence, jshortt, jstancek, jwyatt, kcarcia, ldoskova, lgoncalv, lszubowi, lzampier, mleitner, mmilgram, mstowell, nmurray, 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 4.19.307, kernel 5.4.269, kernel 5.10.210, kernel 5.15.149, kernel 6.1.77, kernel 6.6.16, kernel 6.7.4, kernel 6.8	Doc Type:	If docs needed, set a value
Doc Text:	A vulnerability was found in the pstore/ram component of the Linux kernel, which caused crashes when the number of CPU cores was set to an odd number. This issue occurs because the odd-numbered zones became misaligned. This flaw allows a local, authenticated attacker to cause a denial of service.	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:	2270085
Bug Blocks:	2270105

Description Zack Miele 2024-03-18 13:11:01 UTC

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

pstore/ram: Fix crash when setting number of cpus to an odd number

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

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/20240318102117.2839904-9-lee@kernel.org/T

Comment 1 Zack Miele 2024-03-18 13:11:34 UTC

Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 2270085]

Comment 5 Justin M. Forbes 2024-03-26 16:07:00 UTC

This was fixed for Fedora with the 6.7.4 stable kernel updates.

Comment 8 Alex 2024-06-09 15:12:25 UTC

The result of automatic check (that is developed by Alexander Larkin) for this CVE-2023-52619 is: CHECK	Maybe valid. Check manually. with impact MODERATE (that is approximation based on flags DANGER DISK INIT SIMPLEFIX  ; these flags parsed automatically based on patche 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 19 errata-xmlrpc 2024-08-08 04:40:42 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 20 errata-xmlrpc 2024-08-08 04:51:29 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

Comment 22 errata-xmlrpc 2024-09-03 15:42:39 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.8 Extended Update Support

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