libbpf: Handle size overflow for ringbuf mmap
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:
libbpf: Handle size overflow for ringbuf mmap
The maximum size of ringbuf is 2GB on x86-64 host, so 2 * max_entries will overflow u32 when mapping producer page and data pages. Only casting max_entries to size_t is not enough, because for 32-bits application on 64-bits kernel the size of read-only mmap region also could overflow size_t.
So fixing it by casting the size of read-only mmap region into a __u64 and checking whether or not there will be overflow during mmap.
From the CVE record · Linux
Linux libbpf has a size overflow when mapping ring buffer producer and data pages. The overflow can also affect the read-only mapping region for a 32-bit application on a 64-bit kernel. The input does not specify what an attacker could achieve or whether network access, authentication, or user interaction is required.
Engineers running Linux with libbpf ring buffer use should check their systems; affected versions are not specified.