RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2049040 - CVE-2022-24122 kernel: Backport fixes for ucount rlimits
Summary: CVE-2022-24122 kernel: Backport fixes for ucount rlimits
Keywords:
Status: CLOSED ERRATA
Alias: None
Deadline: 2022-02-14
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: kernel
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 9.0
Assignee: Alexey Gladkov
QA Contact: Chao Ye
URL:
Whiteboard:
: 2048624 (view as bug list)
Depends On:
Blocks: CVE-2022-24122 2048626
TreeView+ depends on / blocked
 
Reported: 2022-02-01 11:40 UTC by Alexey Gladkov
Modified: 2022-05-17 16:01 UTC (History)
8 users (show)

Fixed In Version: kernel-5.14.0-70.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-17 15:45:26 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gitlab redhat/centos-stream/src/kernel centos-stream-9 merge_requests 463 0 None None None 2022-02-01 13:58:14 UTC
Red Hat Issue Tracker RHELPLAN-110512 0 None None None 2022-02-01 11:47:46 UTC
Red Hat Product Errata RHBA-2022:3907 0 None None None 2022-05-17 15:46:03 UTC

Description Alexey Gladkov 2022-02-01 11:40:21 UTC
We need to backport the fixes for ucounts including UAF in shm code.

f9d87929d451d3e649699d0f1d74f71f77ad38f5 ucount:  Make get_ucount a safe get_user replacement
59ec71575ab440cd5ca0aa53b2a2985b3639fad4 ucounts: Fix rlimit max values check
32342701b4ba57a6fd77e8aca2f65f68c0fa1da6 ucounts: Use atomic_long_sub_return for clarity
da70d3109e74adf6ae9f8d1f6c7c0c9735d314ba ucounts: Add get_ucounts_or_wrap for clarity
5fc9e37cd5ae762b856912cdedb226a884b3c3e0 ucounts: Remove unnecessary test for NULL ucount in get_ucounts

Comment 2 Chris von Recklinghausen 2022-02-11 11:06:57 UTC
*** Bug 2048624 has been marked as a duplicate of this bug. ***

Comment 17 Chao Ye 2022-02-23 07:55:12 UTC
Namespace test pass with kernel-5.14.0-51.mr463_220201_1415.el9:
https://beaker.engineering.redhat.com/jobs/6332294

Comment 22 Chao Ye 2022-03-02 04:49:07 UTC
Namespace test pass with kernel-5.14.0-70.el9:
https://beaker.engineering.redhat.com/jobs/6356781

Comment 24 errata-xmlrpc 2022-05-17 15:45:26 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: kernel), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:3907


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