Back to bug 2124061
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Alex | 2022-09-04 11:17:44 UTC | CC | security-response-team | |
| Alex | 2022-09-04 11:23:16 UTC | Doc Text | A flaw possible leak of data in the Linux kernel's BPF subsystem was found in the way user call BPF_FUNC_ringbuf_discard after BPF_FUNC_ringbuf_reserve. A local user could use this flaw to get unprivileged access to some data or potentially escalate their privileges on the system. |
|
| Alex | 2022-12-07 13:49:34 UTC | Doc Text | A flaw possible leak of data in the Linux kernel's BPF subsystem was found in the way user call BPF_FUNC_ringbuf_discard after BPF_FUNC_ringbuf_reserve. A local user could use this flaw to get unprivileged access to some data or potentially escalate their privileges on the system. | A flaw possible leak of data in the Linux kernel's BPF subsystem was found in the way user triggers release_reg_references() of BPF in the way that release fails. A local user could use this flaw to get unprivileged access to some data or potentially escalate their privileges on the system. |
| Alex | 2022-12-07 13:50:15 UTC | Summary | EMBARGOED kernel: eBPF verifier bug: Mishandling in release_reg_references() cause a PTR leak vulnerability | kernel: eBPF verifier bug: Mishandling in release_reg_references() cause a PTR leak vulnerability |
| Group | security, qe_staff | |||
| CC | adscvr, airlied, alciregi, bskeggs, ddepaula, dfreiber, ezulian, hdegoede, hpa, jarodwilson, jferlan, jglisse, josef, jwboyer, kernel-maint, kernel-mgr, linville, masami256, mchehab, rogbas, steved | |||
| Alex | 2022-12-07 13:50:35 UTC | Depends On | 2151552 | |
| Alex | 2022-12-07 13:57:20 UTC | Comment | 0 | updated |
| Alex | 2022-12-07 14:01:14 UTC | Depends On | 2151563, 2151560, 2151562, 2151561 | |
| Red Hat Bugzilla | 2022-12-31 23:35:43 UTC | CC | fhrbata | |
| Red Hat Bugzilla | 2023-04-01 08:41:11 UTC | CC | dhoward | |
| Red Hat Bugzilla | 2023-07-07 08:32:43 UTC | CC | security-response-team | |
| Assignee | security-response-team | nobody |
Back to bug 2124061