SECUFOCUSNOW
Home›CVE index›CVE-2022-49030
Review reviewHigh

CVE-2022-49030

Linux Linux, linux kernel

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.

CVSS
7.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2024.10.22
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.8

Vulnerability overview

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 product and versions

Product
Linux Linux, linux kernel
Affected versions
>= bf99c936f9478a05d51e9f101f90de70bee9a89c < 8a549ab6724520aa3c07f47e0eba820293551490, >= bf99c936f9478a05d51e9f101f90de70bee9a89c < 0140e079a42064680394fff1199a7b5483688dec, >= bf99c936f9478a05d51e9f101f90de70bee9a89c < 535a25ab4f9a45f74ba38ab71de95e97474922ed, >= bf99c936f9478a05d51e9f101f90de70bee9a89c < 927cbb478adf917e0a142b94baa37f06279cc466, >= 5.8, >= 5.8 < 5.10.158, >= 5.11 < 5.15.82, >= 5.16 < 6.0.12, 6.1
Fixed versions
5.10.158, 5.15.82, 6.0.12

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-190