Back to bug 2214348
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Alex | 2023-06-12 17:44:54 UTC | CC | dfreiber, jburrell, rogbas, vkumar | |
| Alex | 2023-06-12 17:45:49 UTC | Depends On | 2214349 | |
| Alex | 2023-06-12 18:16:31 UTC | Depends On | 2214356, 2214358, 2214359, 2214357 | |
| Alex | 2023-06-12 18:20:49 UTC | Alias | CVE-2023-3212 | |
| Summary | kernel: NULL pointer dereference in gfs2_evict_inode() in fs/gfs2/super.c | CVE-2023-3212 kernel: NULL pointer dereference in gfs2_evict_inode() in fs/gfs2/super.c | ||
| Mauro Matteo Cascella | 2023-06-22 08:34:42 UTC | Severity | medium | low |
| Summary | CVE-2023-3212 kernel: NULL pointer dereference in gfs2_evict_inode() in fs/gfs2/super.c | CVE-2023-3212 kernel: gfs2: NULL pointer dereference in gfs2_evict_inode() | ||
| Priority | medium | low | ||
| Mauro Matteo Cascella | 2023-06-22 08:40:56 UTC | Fixed In Version | kernel 6.4-rc2 | |
| Mauro Matteo Cascella | 2023-06-22 09:14:32 UTC | Doc Text | A NULL pointer dereference issue was found in the gfs2 file system in the Linux kernel. It occurs on corrupt gfs2 file systems when the evict code tries to reference the journal descriptor structure after it has been freed and set to NULL. A privileged local user could use this flaw to cause a kernel panic. | |
| RaTasha Tillery-Smith | 2023-06-22 13:28:28 UTC | Doc Text | A NULL pointer dereference issue was found in the gfs2 file system in the Linux kernel. It occurs on corrupt gfs2 file systems when the evict code tries to reference the journal descriptor structure after it has been freed and set to NULL. A privileged local user could use this flaw to cause a kernel panic. | A NULL pointer dereference flaw was found in the gfs2 file system in the Linux kernel. This issue occurs on corrupt gfs2 file systems when the evict code tries to reference the journal descriptor structure after it has been freed and set to NULL. This flaw allows a privileged local user to cause a kernel panic. |
| Red Hat Bugzilla | 2023-07-07 08:34:23 UTC | Assignee | security-response-team | nobody |
Back to bug 2214348