Linux kernel use-after-free in flower filter deletion
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net/sched: cls_flower: avoid stale mask references after delete
Flower releases a mask reference when a filter is removed from the classifier. The filter object can remain alive while dump, walk, or hardware reoffload paths hold a reference to it. Those paths can then dereference f->mask after the mask has already been released.
Keep the mask reference until the filter reference count reaches zero. Release the mask synchronously from the final __fl_put() while the caller still holds the tcf_proto reference, and leave the existing RCU work to free the mask. This keeps the mask available to every reader that still holds the filter.
The filter is still removed from the classifier indexes immediately. Therefore, a deleted filter can temporarily retain an otherwise empty mask; fl_delete() uses the handle IDR, rather than the mask list, to determine whether the classifier has become empty.
Failed mask assignment can leave fnew->mask as an error or borrowed pointer without an owned mask reference. Clear it before the common failure path so the final put cannot release an unowned reference.
This fix does not add fields, snapshots, or per-filter memory.
From the CVE record · Linux
The Linux kernel flower classifier can release a filter’s mask while dump, walk, or hardware reoffload paths still hold a reference to the filter. This can lead to a stale mask dereference if a filter is removed during those operations. The input does not specify whether an attacker needs local or network access, authentication, or user interaction.
Engineers running the Linux kernel should check their versions; affected versions are not specified.