A malicious X server could cause a heap overflow by injecting a large DEVICE_ENABLE reply when processed by libXi before 1.8.4.
Product
azure linux libXi vulnerabilities
9 published CVES affecting azure linux libXi, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 9
- Critical
- 0
- High
- 3
- Medium
- 6
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest azure linux libXi CVEs
Newest publication first
-
HighCVSS 7.5 EPSS 0.26%
-
HighCVSS 7.5 EPSS 0.26%
A buffer overflow when handling DEVICE_RESOLUTION in libXi before 1.8.4 could overflow a heap, triggered by a malicious X server.
-
MediumCVSS 5.6 EPSS 0.13%
An out-of-bounds read in libXi's XI2 enter/leave/focus cookie conversion in libXi before 1.8.4 could be used by malicious X server to crash an attached X client.
-
MediumCVSS 6.5 EPSS 0.21%
An out-of-bounds read in libXi's XListInputDevices() class parsing in libXi before 1.8.4 could be used by malicious X servers to crash an attached X client.
-
MediumCVSS 6.5 EPSS 0.21%
An out-of-bounds read in libXi's XListInputDevices() in libXi before 1.8.4 could be used by malicious X servers to crash an attached X client.
-
MediumCVSS 6.5 EPSS 0.26%
An out-of-bounds read in libXi's XI2 XIQueryDevice reply parsing in libXi before 1.8.4 can be used by a malicious X server to crash an attached X client.
-
HighCVSS 7.4 EPSS 0.26%
An out-of-bounds read in libXi's XI2 class parser in libXi before 1.8.4 could be used by malicious X servers to crash an attached X client.
-
CVE-2026-93542 Out-of-bounds read in libXi's XI2 class parsing via size_classes() and copy_classes()
PublishedMediumCVSS 6.5 EPSS 0.26%An out-of-bounds read in libXi's XI2 class parsing via size_classes() and copy_classes() in libXi before 1.8.4 could be used by malicous servers to crash the X client.
-
MediumCVSS 6.5 EPSS 0.26%
An out-of-bounds read in libXi's XQueryDeviceState() in libXi before 1.8.4 could be used by a
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.