Bug 2267936 (CVE-2021-47089) - CVE-2021-47089 kernel: kfence: fix memory leak when cat kfence objects
Summary: CVE-2021-47089 kernel: kfence: fix memory leak when cat kfence objects
Keywords:
Status: NEW
Alias: CVE-2021-47089
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 2268181
TreeView+ depends on / blocked
 
Reported: 2024-03-05 16:07 UTC by Zack Miele
Modified: 2024-06-28 12:11 UTC (History)
51 users (show)

Fixed In Version: kernel 5.15.12, kernel 5.16
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Zack Miele 2024-03-05 16:07:43 UTC
In the Linux kernel, the following vulnerability has been resolved:

kfence: fix memory leak when cat kfence objects

The Linux kernel CVE team has assigned CVE-2021-47089 to this issue.

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024030413-CVE-2021-47089-bc5a@gregkh/T

Comment 2 Audra Mitchell 2024-03-12 20:12:45 UTC
Hey Zack-
Looks to me we already have the fix for this issue in RHEL 9:

$ kerneloscope  downstream 0129ab1f268b
0a838c65d871 (in rhel-9.1, rhel-9.2, rhel-9.3, rhel-9.4) kfence: fix memory leak when cat kfence objects

I'm going to go ahead and close the jiras for this issue. Let me know if you have any questions.

Comment 3 Alex 2024-06-09 17:06:22 UTC
The result of automatic check (that is developed by Alexander Larkin) for this CVE-2021-47089 is: CHECK	Maybe valid. Check manually. with impact LOW (that is an approximation based on flags INIT LEAK  ; 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.


Note You need to log in before you can comment on or make changes to this bug.