Back to bug 2040358

Who When What Removed Added
Marian Rehak 2022-01-13 14:45:48 UTC CC security-response-team
Marian Rehak 2022-01-13 14:47:34 UTC Blocks 2040359
Murphy Zhou 2022-01-14 06:44:51 UTC CC xzhou
Rohit Keshri 2022-01-14 07:52:05 UTC Depends On 2040578, 2040579, 2040584, 2040586, 2040585, 2040588, 2040580, 2040582, 2040577, 2040583, 2040587, 2040581
Rohit Keshri 2022-01-14 07:53:35 UTC CC asavkov, ctoe, joe.lawrence, jpoimboe, jthierry, rhandlin, ycote
Rohit Keshri 2022-01-14 07:55:41 UTC Depends On 2040592, 2040591, 2040593, 2040590
Rohit Keshri 2022-01-14 08:20:57 UTC Doc Text An out of bounds (OOB) write problem was found in legacy_parse_param in fs/fs_context.c in the Linux kernel filesystem due to a heap overflow. This issue is caused by an integer underflow due to a miscalculation of a valid max length, resulting in a privilege escalation problem.
Rohit Keshri 2022-01-14 08:34:47 UTC CC esandeen, rkeshri
Rohit Keshri 2022-01-14 08:35:24 UTC Comment 0 updated
Florencio Cano 2022-01-14 08:36:56 UTC CC bdettelb
Petr Matousek 2022-01-14 10:13:10 UTC CC cmaiolin, pmatouse
Stoyan Nikolov 2022-01-14 11:43:11 UTC CC michal.skrivanek, mperina, nobody, sbonazzo
Stoyan Nikolov 2022-01-14 11:44:02 UTC Depends On 2040658
Clifford Perry 2022-01-14 12:46:10 UTC CC cperry
RaTasha Tillery-Smith 2022-01-14 14:07:06 UTC Doc Text An out of bounds (OOB) write problem was found in legacy_parse_param in fs/fs_context.c in the Linux kernel filesystem due to a heap overflow. This issue is caused by an integer underflow due to a miscalculation of a valid max length, resulting in a privilege escalation problem. An out-of-bounds (OOB) write flaw was found in the legacy_parse_param in fs/fs_context.c function in the Linux kernel’s filesystem due to a heap overflow. This issue is caused by an integer underflow due to a miscalculation of a valid max length, resulting in a privilege escalation problem.
Don Howard 2022-01-14 15:56:45 UTC CC bfoster
Karen Noel 2022-01-14 20:36:08 UTC CC knoel, swhiteho
Mike Stowell 2022-01-15 22:35:29 UTC CC mstowell
Petr Matousek 2022-01-18 09:09:02 UTC Doc Text An out-of-bounds (OOB) write flaw was found in the legacy_parse_param in fs/fs_context.c function in the Linux kernel’s filesystem due to a heap overflow. This issue is caused by an integer underflow due to a miscalculation of a valid max length, resulting in a privilege escalation problem. A heap-based buffer overflow flaw was found in the way the legacy_parse_param function in the Filesystem Context functionality of the Linux kernel verified the supplied parameters length. An unprivileged (in case of unprivileged user namespaces enabled, otherwise needs namespaced CAP_SYS_ADMIN privilege) local user able to open a filesystem that does not support the Filesystem Context API (and thus fallbacks to legacy handling) could use this flaw to escalate their privileges on the system.
Summary EMBARGOED CVE-2022-0185 kernel: integer underflow allows out-of-bound write EMBARGOED CVE-2022-0185 kernel: fs_context: heap overflow in legacy parameter handling
Petr Matousek 2022-01-18 09:11:02 UTC Comment 0 updated
Rohit Keshri 2022-01-18 09:56:08 UTC Comment 0 updated
Steve Whitehouse 2022-01-18 10:05:38 UTC CC dhowells
Rodrigo A B Freire 2022-01-18 12:27:33 UTC Flags needinfo?(pmatouse)
CC rfreire
Petr Matousek 2022-01-18 12:34:23 UTC CC proguski
Flags needinfo?(pmatouse) needinfo?(proguski)
Przemyslaw Roguski 2022-01-18 14:20:07 UTC Flags needinfo?(proguski)
Petr Matousek 2022-01-18 16:08:11 UTC Comment 19 updated
Rohit Keshri 2022-01-18 18:41:56 UTC Group security, qe_staff
Summary EMBARGOED CVE-2022-0185 kernel: fs_context: heap overflow in legacy parameter handling CVE-2022-0185 kernel: fs_context: heap overflow in legacy parameter handling
CC adscvr, airlied, alciregi, bskeggs, hdegoede, jarodwilson, jeremy, jglisse, jonathan, josef, jwboyer, kernel-maint, kernel-mgr, kpatch-maint, linville, masami256, mchehab, steved
Deadline 2022-01-18
Rohit Keshri 2022-01-18 18:42:39 UTC Depends On 2042052
Rohit Keshri 2022-01-18 18:45:20 UTC Comment 0 updated
errata-xmlrpc 2022-01-19 09:59:51 UTC Link ID Red Hat Product Errata RHSA-2022:0176
errata-xmlrpc 2022-01-19 14:18:58 UTC Link ID Red Hat Product Errata RHSA-2022:0187
errata-xmlrpc 2022-01-19 14:42:44 UTC Link ID Red Hat Product Errata RHSA-2022:0186
errata-xmlrpc 2022-01-19 15:07:07 UTC Link ID Red Hat Product Errata RHSA-2022:0188
Rodrigo A B Freire 2022-01-20 01:45:31 UTC CC rfreire
errata-xmlrpc 2022-01-24 09:43:49 UTC Link ID Red Hat Product Errata RHSA-2022:0232
errata-xmlrpc 2022-01-24 09:48:51 UTC Link ID Red Hat Product Errata RHSA-2022:0231
errata-xmlrpc 2022-01-24 14:08:55 UTC Link ID Red Hat Product Errata RHBA-2022:0238
Adam Kaplan 2022-01-25 13:57:05 UTC CC adam.kaplan
Flags needinfo?(proguski)
Adam Kaplan 2022-01-25 13:59:14 UTC Flags needinfo?(nalin)
CC nalin
Przemyslaw Roguski 2022-01-25 14:49:08 UTC Flags needinfo?(proguski)
Nalin Dahyabhai 2022-01-25 15:48:39 UTC Flags needinfo?(nalin)
Andy Bartlett 2022-01-27 13:11:19 UTC CC andbartl
Andy Bartlett 2022-02-04 13:38:04 UTC Flags needinfo?(proguski)
Przemyslaw Roguski 2022-02-04 13:50:31 UTC Flags needinfo?(proguski)
errata-xmlrpc 2022-02-15 10:59:09 UTC Link ID Red Hat Product Errata RHSA-2022:0540
Ronit Dey 2022-02-22 04:53:36 UTC CC rdey
Product Security DevOps Team 2022-05-11 15:15:27 UTC Status NEW CLOSED
Resolution --- ERRATA
Last Closed 2022-05-11 15:15:27 UTC

Back to bug 2040358