Linux
libbpf: Reject non-exclusive metadata maps in the signed loader
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- >= fb2b0e290147ba01a53dfd92cf91058c9d2ee254, < b6862b6a25c6a925fb0b0e549ee4a52a8d2966fb
- >= fb2b0e290147ba01a53dfd92cf91058c9d2ee254, < 0dad5adeb34b6f78a883e8faa6a1c947a240e7c9
- >= fb2b0e290147ba01a53dfd92cf91058c9d2ee254, < 0fb6c9ed6493b4af01be8bb0a384574eba7df636
Fixed in b6862b6a25c6a925fb0b0e549ee4a52a8d2966fb, 0dad5adeb34b6f78a883e8faa6a1c947a240e7c9, 0fb6c9ed6493b4af01be8bb0a384574eba7df636
- 6.18
Fixed in 0, 6.18.40, 7.1.5, 7.2
Mitigation
Upgrade Linux to b6862b6a25c6a925fb0b0e549ee4a52a8d2966fb or 0dad5adeb34b6f78a883e8faa6a1c947a240e7c9 or 0fb6c9ed6493b4af01be8bb0a384574eba7df636 or later.
Upgrade Linux to 0 or 6.18.40 or 7.1.5 or 7.2 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.