CVE-2022-36337

CVE-2022-36337 is a high-severity vulnerability in Insyde Kernel with a CVSS 3.x base score of 8.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-787.

Key facts

Description

An issue was discovered in Insyde InsydeH2O with kernel 5.0 through 5.5. A stack buffer overflow vulnerability in the MebxConfiguration driver leads to arbitrary code execution. Control of a UEFI variable under the OS can cause this overflow when read by BIOS code.

Frequently asked questions

What is CVE-2022-36337?
An issue was discovered in Insyde InsydeH2O with kernel 5.0 through 5.5. A stack buffer overflow vulnerability in the MebxConfiguration driver leads to arbitrary code execution. Control of a UEFI variable under the OS can cause this overflow when read by BIOS code.
How severe is CVE-2022-36337?
CVE-2022-36337 has a CVSS 3.x base score of 8.2, rated high severity. It is exploitable over local access with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2022-36337 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (12th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2022-36337?
CVE-2022-36337 affects Insyde Kernel. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2022-36337?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2022-36337 published?
CVE-2022-36337 was published on 2022-11-23 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Insyde Kernel

All CVEs affecting Insyde Kernel →

Other CWE-787 (Out-of-bounds Write) vulnerabilities

Browse all CWE-787 (Out-of-bounds Write) vulnerabilities →