What is CVE-2026-89620?

CVE-2026-89620 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10, affecting Linux kernel versions from 6.14 onward and patched in 6.18.50, 7.2.4 and 7.3-rc1. CVE-2026-89620 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-89620?

CVE-2026-89620 has a CVSS score of 7.8 out of 10, rated High severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Is there a patch available for CVE-2026-89620?

Yes, CVE-2026-89620 has been patched. Fixed versions include 6.18.50, 7.2.4 and 7.3-rc1. If you are running Linux kernel 6.14 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-89620 actively exploited?

CVE-2026-89620 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-89620

High

In the Linux kernel, the following vulnerability has been resolved: HID: intel-thc-hid: intel-quickspi: validate report size before copy write_cmd_to_txdma() builds an output report in qsdev->report_buf, a heap buffer allocated in quickspi_alloc_report_buf() to the device-descriptor derived max_report_len (a few hundred bytes for a touch controller). It copies the caller-supplied report into that buffer: memcpy(write_buf->content, report_buf, report_buf_len); The HID core caps a report at HID_MAX_BUFFER_SIZE (16384) by default, and quickspi_hid_ll_driver does not set max_buffer_size, so the length reaches the driver unbounded. A hidraw SET_REPORT/SET_FEATURE ioctl carrying a report larger than max_report_len therefore overflows report_buf with attacker-controlled length and content. Record the report_buf allocation size and reject reports that do not fit before copying, matching the equivalent guard in the intel-quicki2c sibling (quicki2c_init_write_buf()) and the hid-goodix-spi fix. write_cmd_to_txdma() writes the output report header ahead of the content in the same buffer, so size the allocation to cover the header as well. That keeps the added bound from rejecting a maximum-sized report.

Package Linux Kernel

Published 2026-09-11

Last modified 2026-09-13

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

7.8

out of 10

High

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Vector string

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

Affected versions

Linux kernel versions 6.14 and later are affected. Fixed in 6.18.50, 7.2.4, 7.3-rc1 and their respective stable series.

Affected from

≥ 6.14

Fixed in

✓ 6.18.50 6.18.x ✓ 7.2.4 7.2.x ✓ 7.3-rc1

References

3 total

Details

CVE ID CVE-2026-89620

Severity High

CVSS score 7.8 / 10

CVSS version 3.1

Published 2026-09-11

Modified 2026-09-13

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-89620?

CVE-2026-89620 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10 . It affects Linux kernel versions from 6.14 onward and has been patched in 6.18.50, 7.2.4 and 7.3-rc1. CVE-2026-89620 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-89620?

CVE-2026-89620 has a CVSS score of 7.8 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
Is there a patch available for CVE-2026-89620?

Yes. CVE-2026-89620 has been patched. Fixed versions include 6.18.50, 7.2.4 and 7.3-rc1. If you are running Linux kernel 6.14 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-89620 actively exploited?

No. CVE-2026-89620 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.