CVE-2022-48714

See a problem?
Please try reporting it to the source first.
Source
https://nvd.nist.gov/vuln/detail/CVE-2022-48714
Import Source
https://storage.googleapis.com/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-18T03:22:33.558116Z
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

Affected packages

Debian:11 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
5.10.103-1

Affected versions

5.*

5.10.46-4
5.10.46-5
5.10.70-1~bpo10+1
5.10.70-1
5.10.84-1
5.10.92-1~bpo10+1
5.10.92-1
5.10.92-2
5.10.103-1~bpo10+1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

Debian:12 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
5.16.10-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

Debian:13 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
5.16.10-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}