Bug 2083455 (CVE-2022-1651) - CVE-2022-1651 kernel: A memory leak problem in acrn_dev_ioctl()
Summary: CVE-2022-1651 kernel: A memory leak problem in acrn_dev_ioctl()
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2022-1651
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2083718 2083719
Blocks: 2083452 2083636
TreeView+ depends on / blocked
 
Reported: 2022-05-10 07:06 UTC by Rohit Keshri
Modified: 2023-07-28 17:01 UTC (History)
47 users (show)

Fixed In Version: kernel 5.18 rc1
Doc Type: If docs needed, set a value
Doc Text:
A memory leak flaw was found in the Linux kernel in acrn_dev_ioctl in the drivers/virt/acrn/hsm.c function in how the ACRN Device Model emulates virtual NICs in VM. This flaw allows a local privileged attacker to leak unauthorized kernel information, causing a denial of service.
Clone Of:
Environment:
Last Closed: 2023-05-10 18:33:21 UTC
Embargoed:

Attachments (Terms of Use)

Description Rohit Keshri 2022-05-10 07:06:23 UTC 
A memory leak problem was found in acrn_dev_ioctl in drivers/virt/acrn/hsm.c in ACRN Device Model emulates virtual NICs in VM. This flaw may allow a local privileged attacker to leak kernel unauthorized information, and may also cause a denial of service problem.

#Fix
Now the patch for this issue is available upstream.
1.https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ecd1735f14d6ac868ae5d8b7a2bf193fa11f388b
2.https://lore.kernel.org/all/20220308092047.1008409-1-butterflyhuangxx@gmail.com/
Comment 11 Product Security DevOps Team 2023-05-10 18:33:16 UTC 
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2022-1651
Comment 12 Jan Pazdziora 2023-07-28 17:01:41 UTC 
Hello, the CVE page https://access.redhat.com/security/cve/CVE-2022-1651 Statement paragraph says

The affected code was not introduced into any kernel versions shipped with Red Hat Enterprise Linux making this vulnerable and not applicable to these platforms.

Should that be "making this vulnerability not applicable" or something similar?

Also, given we list all RHEL versions Not affected, why do we include that Mitigation section on that CVE page?
Note You need to log in before you can comment on or make changes to this bug.