CVE-2022-48714
- Source
- https://nvd.nist.gov/vuln/detail/CVE-2022-48714
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2022-48714.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2022-48714
- Related
- Published
- 2024-06-20T11:15:55Z
- Modified
- 2024-09-11T04:57:00.034882Z
- Summary
- [none]
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
bpf: Use VMMAP instead of VMALLOC for ringbuf
After commit 2fd3fb0be1d1 ("kasan, vmalloc: unpoison VMALLOC pages after mapping"), non-VMALLOC mappings will be marked as accessible in _getvmareanode() when KASAN is enabled. But now the flag for ringbuf area is VMALLOC, so KASAN will complain out-of-bound access after vmap() returns. Because the ringbuf area is created by mapping allocated pages, so use VMMAP instead.
After the change, info in /proc/vmallocinfo also changes from [start]-[end] 24576 ringbufmapalloc+0x171/0x290 vmalloc user to [start]-[end] 24576 ringbufmapalloc+0x171/0x290 vmap user
- References
-
- https://git.kernel.org/stable/c/5e457aeab52a5947619e1f18047f4d2f3212b3eb
- https://git.kernel.org/stable/c/6304a613a97d6dcd49b93fbad31e9f39d1e138d6
- https://git.kernel.org/stable/c/b293dcc473d22a62dc6d78de2b15e4f49515db56
- https://git.kernel.org/stable/c/d578933f6226d5419af9306746efa1c693cbaf9c
- https://security-tracker.debian.org/tracker/CVE-2022-48714
Affected packages
Debian:11 / linux
Package
- Name
- linux
- Purl
- pkg:deb/debian/linux?arch=source
Affected ranges
- Type
- ECOSYSTEM
- Events
-
Introduced0Unknown introduced version / All previous versions are affectedFixed5.10.103-1
Debian:12 / linux
Package
- Name
- linux
- Purl
- pkg:deb/debian/linux?arch=source
Debian:13 / linux
Package
- Name
- linux
- Purl
- pkg:deb/debian/linux?arch=source