Back to bug 2122089
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Wade Mealing | 2022-08-29 05:00:01 UTC | Summary | linux: Fix possible buffer overflow in sysfs reading. | CVE-2022-20166 linux: Fix possible buffer overflow in sysfs reading. |
| Alias | CVE-2022-20166 | |||
| Wade Mealing | 2022-08-29 06:17:32 UTC | CC | adscvr, airlied, alciregi, bskeggs, hdegoede, hpa, jarodwilson, jglisse, jonathan, josef, jwboyer, kernel-maint, lgoncalv, linville, masami256, mchehab, steved | |
| Wade Mealing | 2022-08-29 06:20:56 UTC | CC | chwhite, debarbos, jlelli, jwyatt, lleshchi, qzhao, swood, tyberry, williams | |
| Wade Mealing | 2022-08-29 06:29:16 UTC | CC | jburrell, vkumar | |
| Wade Mealing | 2022-08-30 02:28:20 UTC | Fixed In Version | kernel-5.10-rc1 | |
| Wade Mealing | 2022-08-30 02:50:09 UTC | Doc Text | A flaw was found in the Linux kernels sysfs layer allowing a local users with the ability to read files under the /sysfs mount point to corrupt memory or possibly crash the system | |
| Wade Mealing | 2022-08-30 06:16:10 UTC | Depends On | 2122471, 2122470, 2122472, 2122468 | |
| Wade Mealing | 2022-08-30 07:34:25 UTC | Summary | CVE-2022-20166 linux: Fix possible buffer overflow in sysfs reading. | CVE-2022-20166 kernel: Fix possible buffer overflow in sysfs reading. |
| RaTasha Tillery-Smith | 2022-08-30 13:59:35 UTC | Doc Text | A flaw was found in the Linux kernels sysfs layer allowing a local users with the ability to read files under the /sysfs mount point to corrupt memory or possibly crash the system | A flaw was found in the Linux kernel’s sysfs layer. This flaw allows a local user who can read files under the /sysfs mount point to corrupt memory or possibly crash the system. |
| Ian Kent | 2022-08-31 00:44:56 UTC | CC | ikent | |
| Eric Sandeen | 2022-09-01 20:29:59 UTC | CC | esandeen | |
| Red Hat Bugzilla | 2022-12-31 23:36:31 UTC | CC | fhrbata | |
| Red Hat Bugzilla | 2023-04-01 08:42:22 UTC | CC | dhoward | |
| Red Hat Bugzilla | 2023-07-07 08:31:20 UTC | Assignee | security-response-team | nobody |
Back to bug 2122089