libbpf: Handle size overflow for ringbuf mmap
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0140e079a42064680394fff1199a7b5483688dec, Kernel 535a25ab4f9a45f74ba38ab71de95e97474922ed, Kernel 8a549ab6724520aa3c07f47e0eba820293551490 and 1 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.8, >=bf99c936f9478a05d51e9f101f90de70bee9a89c <0140e079a42064680394fff1199a7b5483688dec, >=bf99c936f9478a05d51e9f101f90de70bee9a89c <535a25ab4f9a45f74ba38ab71de95e97474922ed, >=bf99c936f9478a05d51e9f101f90de70bee9a89c <8a549ab6724520aa3c07f47e0eba820293551490, >=bf99c936f9478a05d51e9f101f90de70bee9a89c <927cbb478adf917e0a142b94baa37f06279cc466 | 0140e079a42064680394fff1199a7b5483688dec, 535a25ab4f9a45f74ba38ab71de95e97474922ed, 8a549ab6724520aa3c07f47e0eba820293551490, 927cbb478adf917e0a142b94baa37f06279cc466 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket