Bug 2267733 (CVE-2023-52559)
Summary: | CVE-2023-52559 kernel: iommu/vt-d: memory allocation in iommu_suspend() leading to intermittent suspend/hibernation | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | ybuenos |
Component: | vulnerability | Assignee: | Product Security <prodsec-ir-bot> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
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, 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 5.15.136, kernel 6.1.57, kernel 6.5.7, kernel 6.6 | Doc Type: | If docs needed, set a value |
Doc Text: |
A flaw was found in the Linux kernel's Input–output memory management unit functionality. This issue can cause warnings during suspend/hibernation and could allow a local user to crash the system.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2024-04-09 16:35:12 UTC | 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: | 2267764 |
Description
ybuenos
2024-03-04 17:08:14 UTC
The result of automatic check (that is developed by Alexander Larkin) for this CVE-2023-52559 is: CHECK Maybe valid. Check manually. with impact LOW (that is an approximation based on flags WARNONLY NOMEMCHK ; 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. |