CVE-2022-49030
published 2024-10-21CVE-2022-49030: 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…
PriorityP339high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.28%
19.9th percentile
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
14 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.0.12-1 (bookworm) | linux 6.0.12-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= bf99c936f9478a05d51e9f101f90de70bee9a89c < 8a549ab6724520aa3c07f47e0eba820293551490 | 8a549ab6724520aa3c07f47e0eba820293551490 |
| linux | linux | >= bf99c936f9478a05d51e9f101f90de70bee9a89c < 0140e079a42064680394fff1199a7b5483688dec | 0140e079a42064680394fff1199a7b5483688dec |
| linux | linux | >= bf99c936f9478a05d51e9f101f90de70bee9a89c < 535a25ab4f9a45f74ba38ab71de95e97474922ed | 535a25ab4f9a45f74ba38ab71de95e97474922ed |
| linux | linux | >= bf99c936f9478a05d51e9f101f90de70bee9a89c < 927cbb478adf917e0a142b94baa37f06279cc466 | 927cbb478adf917e0a142b94baa37f06279cc466 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.158-1 | 5.10.158-1 |
| linux | linux_kernel | >= 0 < 6.0.12-1 | 6.0.12-1 |
| linux | linux_kernel | >= 0 < 6.0.12-1 | 6.0.12-1 |
| linux | linux_kernel | >= 0 < 6.0.12-1 | 6.0.12-1 |
| linux | linux_kernel | >= 5.11 < 5.15.82 | 5.15.82 |
| linux | linux_kernel | >= 5.16 < 6.0.12 | 6.0.12 |
| linux | linux_kernel | >= 5.8 < 5.10.158 | 5.10.158 |
CVSS provenance
nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv7.8HIGH
vendor_debian7.8HIGH
vendor_redhat7.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: libbpf: Handle size overflow for ringbuf mmap
vendor_redhat·2024-10-21·CVSS 7.8
CVE-2022-49030 [HIGH] CWE-190 kernel: libbpf: Handle size overflow for ringbuf mmap
kernel: libbpf: Handle size overflow for ringbuf mmap
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.
Statement: BPF is a privileged operation on RHEL Kernel.
Package: kernel (Red Hat Enterprise Linux 6) - Not affected
Package: kernel (Red Hat Enterprise Linux 7) - Not affected
Package: kernel-rt (Re
Debian
CVE-2022-49030: linux - In the Linux kernel, the following vulnerability has been resolved: libbpf: Han...
vendor_debian·2022·CVSS 7.8
CVE-2022-49030 [HIGH] CVE-2022-49030: linux - In the Linux kernel, the following vulnerability has been resolved: libbpf: Han...
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.
Scope: local
bookworm: resolved (fixed in 6.0.12-1)
bullseye: resolved (fixed in 5.10.158-1)
forky: resolved (fixed in 6.0.12-1)
sid: resolved (fixed in 6.0.12-1)
trixie: resolved (fixed in 6.0.12-1)
GHSA
GHSA-75vm-7626-f557: In the Linux kernel, the following vulnerability has been resolved:
libbpf: Handle size overflow for ringbuf mmap
The maximum size of ringbuf is 2GB
ghsa_unreviewed·2024-10-21
CVE-2022-49030 [HIGH] CWE-190 GHSA-75vm-7626-f557: In the Linux kernel, the following vulnerability has been resolved:
libbpf: Handle size overflow for ringbuf mmap
The maximum size of ringbuf is 2GB
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.
OSV
CVE-2022-49030: In the Linux kernel, the following vulnerability has been resolved: libbpf: Handle size overflow for ringbuf mmap The maximum size of ringbuf is 2GB o
osv·2024-10-21·CVSS 7.8
CVE-2022-49030 [HIGH] CVE-2022-49030: In the Linux kernel, the following vulnerability has been resolved: libbpf: Handle size overflow for ringbuf mmap The maximum size of ringbuf is 2GB o
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.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2024-10-21
Published