How severe is CVE-2026-1653?

CVE-2026-1653 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2026-1653 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-1653?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-1653 have an EU (EUVD) identifier?

Yes. CVE-2026-1653 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-11355.

When was CVE-2026-1653 published?

CVE-2026-1653 was published on 2026-03-11 and last updated on 2026-06-17.

CVE-2026-1653

CVE-2026-1653 is a medium-severity vulnerability with a CVSS 3.x base score of 5.5. 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-369.

Key facts

Severity: Medium (CVSS 3.x base score 5.5)
CVSS v4: 6.8
EPSS exploit prediction: 0% (1st percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-11355
Weakness: CWE-369
Published: 2026-03-11
Last modified: 2026-06-17

Description

A potential divide by zero vulnerability was reported in the Lenovo Virtual Bus driver used in Smart Connect that could allow a local authenticated user to cause a Windows blue screen error.

Frequently asked questions

What is CVE-2026-1653?: A potential divide by zero vulnerability was reported in the Lenovo Virtual Bus driver used in Smart Connect that could allow a local authenticated user to cause a Windows blue screen error.
How severe is CVE-2026-1653?: CVE-2026-1653 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2026-1653 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-1653?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-1653 have an EU (EUVD) identifier?: Yes. CVE-2026-1653 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-11355.
When was CVE-2026-1653 published?: CVE-2026-1653 was published on 2026-03-11 and last updated on 2026-06-17.

References

https://support.lenovo.com/us/en/product_security/LEN-209683

Other CWE-369 (Divide By Zero) vulnerabilities

CVE-2021-32494 — Critical (CVSS 10.0): Radare2 has a division by zero vulnerability in Mach-O parser's rebase_buffer function. This allow attackers to create…
CVE-2017-11720 — Critical (CVSS 9.8): There is a division-by-zero vulnerability in LAME 3.99.5, caused by a malformed input file.
CVE-2020-20892 — High (CVSS 8.8): An issue was discovered in function filter_frame in libavfilter/vf_lenscorrection.c in Ffmpeg 4.2.1, allows attackers…
CVE-2025-4637 — High (CVSS 8.7): Divide By Zero vulnerability in davisking dlib allows remote attackers to cause a denial of service via a crafted…
CVE-2026-37232 — High (CVSS 8.6): An issue was discovered in OpenAirInterface5G 2.4.0 (nr-softmodem) in the E2SM-KPM RAN Function's PRB utilization…
CVE-2024-26945 — High (CVSS 8.4): In the Linux kernel, the following vulnerability has been resolved: crypto: iaa - Fix nr_cpus < nr_iaa case If…

Browse all CWE-369 (Divide By Zero) vulnerabilities →