Description
In the Linux kernel, the following vulnerability has been resolved: libbpf: Reject non-exclusive metadata maps in the signed loader The loader verifies map->sha against the metadata hash in its instructions. map->sha is calculated when BPF_OBJ_GET_INFO_BY_FD is called on the frozen map. While the map is frozen, the /signed loader/ must also ensure the map is exclusive, as, without exclusivity (which a hostile host could just omit when loading the loader), another BPF program with map access can mutate the contents afterwards, so the check passes on stale data. With the extra check as part of the signed loader, it now refuses to move on with map->sha validation if the host set it up wrongly.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
fb2b0e290147ba01a53dfd92cf91058c9d2ee254 to < b6862b6a25c6a925fb0b0e549ee4a52a8d2966fbaffectedfb2b0e290147ba01a53dfd92cf91058c9d2ee254 to < 0dad5adeb34b6f78a883e8faa6a1c947a240e7c9affectedfb2b0e290147ba01a53dfd92cf91058c9d2ee254 to < 0fb6c9ed6493b4af01be8bb0a384574eba7df636affected
Linux Linux
Default version status: affected
6.18affected0 to < 6.18unaffected6.18.40 to ≤ 6.18.*unaffected7.1.5 to ≤ 7.1.*unaffected7.2 to ≤ *unaffected