In the Linux kernel, the following vulnerability has been resolved:

bpf: Allow delete from sockmap/sockhash only if update is allowed

We have seen an influx of syzkaller reports where a BPF program attached to
a tracepoint triggers a locking rule violation by performing a map_delete
on a sockmap/sockhash.

We don't intend to support this artificial use scenario. Extend the
existing verifier allowed-program-type check for updating sockmap/sockhash
to also cover deleting from a map.

From now on only BPF programs which were previously allowed to update
sockmap/sockhash can delete from these map types.

kernel.org https://git.kernel.org/stable/c/000a65bf1dc04fb2b65e2abf116f0bc0fc2ee7b1 [No types assigned]

kernel.org https://git.kernel.org/stable/c/11e8ecc5b86037fec43d07b1c162e233e131b1d9 [No types assigned]

kernel.org https://git.kernel.org/stable/c/29467edc23818dc5a33042ffb4920b49b090e63d [No types assigned]

kernel.org https://git.kernel.org/stable/c/6693b172f008846811f48a099f33effc26068e1e [No types assigned]

kernel.org https://git.kernel.org/stable/c/98e948fb60d41447fd8d2d0c3b8637fc6b6dc26d [No types assigned]

kernel.org https://git.kernel.org/stable/c/b81e1c5a3c70398cf76631ede63a03616ed1ba3c [No types assigned]