Back to bug 2049700
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Guilherme de Almeida Suckevicz | 2022-02-02 14:58:37 UTC | Blocks | 2040774 | |
| Summary | kernel: memcg does not limit the number of POSIX file locks allowing memory exhaustion | CVE-2022-0480 kernel: memcg does not limit the number of POSIX file locks allowing memory exhaustion | ||
| Alias | CVE-2022-0480 | |||
| Guilherme de Almeida Suckevicz | 2022-02-02 14:58:52 UTC | Blocks | 2049704 | |
| Guilherme de Almeida Suckevicz | 2022-02-02 15:00:56 UTC | Depends On | 2049708 | |
| Evgenii Shatokhin | 2022-02-03 05:33:07 UTC | CC | eshatokhin | |
| Rohit Keshri | 2022-02-07 18:28:02 UTC | Depends On | 2051677, 2051678 | |
| Rohit Keshri | 2022-02-07 18:44:54 UTC | Doc Text | A flaw was found in filelock_init in fs/locks.c in the Linux kernel. In this flaw, A host memory exhaustion is possible because memcg does not limit the number of POSIX file locks. | |
| Rohit Keshri | 2022-02-07 18:45:50 UTC | Comment | 0 | updated |
| Rohit Keshri | 2022-02-07 18:46:16 UTC | CC | rkeshri | |
| RaTasha Tillery-Smith | 2022-02-08 15:16:41 UTC | Doc Text | A flaw was found in filelock_init in fs/locks.c in the Linux kernel. In this flaw, A host memory exhaustion is possible because memcg does not limit the number of POSIX file locks. | A flaw was found in the filelock_init in fs/locks.c function in the Linux kernel. This issue can lead to host memory exhaustion due to memcg not limiting the number of Portable Operating System Interface (POSIX) file locks. |
| Rohit Keshri | 2022-03-22 07:03:07 UTC | Depends On | 2066601, 2066600 | |
| Red Hat Bugzilla | 2022-06-04 08:04:46 UTC | CC | fpacheco | |
| Red Hat Bugzilla | 2022-07-16 03:20:44 UTC | CC | brdeoliv | |
| Red Hat Bugzilla | 2022-12-31 23:36:20 UTC | CC | fhrbata | |
| Red Hat Bugzilla | 2023-04-01 08:42:07 UTC | CC | dhoward | |
| Rohit Keshri | 2023-05-25 13:21:36 UTC | Depends On | 2209994, 2209998, 2209997, 2209996, 2209995, 2209993 | |
| Red Hat Bugzilla | 2023-07-07 08:35:15 UTC | Assignee | security-response-team | nobody |
Back to bug 2049700