octeontx2-pf: Fix potential use after free in otx2_tc_add_flow()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
octeontx2-pf: Fix potential use after free in otx2_tc_add_flow()
This code calls kfree_rcu(new_node, rcu) and then dereferences "new_node" and then dereferences it on the next line. Two lines later, we take a mutex so I don't think this is an RCU safe region. Re-order it to do the dereferences before queuing up the free.
From the CVE record · Linux
The Linux kernel's octeontx2-pf driver may dereference a flow node after scheduling it to be freed in otx2_tc_add_flow(). This could cause a use-after-free when that code path runs; the input does not specify attacker access requirements, user interaction, or a resulting exploit impact.
Engineers running Linux kernels with the octeontx2-pf driver should check their kernel version; affected versions were not provided.