Menu

Star on GitHub · 3.4k

CVE-2026-98680

In the Linux kernel, the following vulnerability has been resolved: iio: accel: kionix-kx022a: Prevent memory leak and fix state The driver allocates memory for samples at buffer enable path.

Published Oct 18, 2026EPSS 0.17%

Overview

CVE-2026-98680 is a known-severity vulnerability. It was published on October 18, 2026.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

iio: accel: kionix-kx022a: Prevent memory leak and fix state

The driver allocates memory for samples at buffer enable path. If regmap

operation fails in the kx022a_fifo_enable() at the buffer enable path, the

allocated memory is never freed. Furthermore, the state information and

previous hardware configuration(s) aren't undone, potentially leaving

WMI interrupts and buffers enabled, or driver state flags wrong.

Free the memory and revert the hardware configuration and state flags on

error path.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-98680?

CVE-2026-98680 is a known-severity vulnerability. It was published on October 18, 2026.

How severe is CVE-2026-98680?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-98680?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-98680?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-98680 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Watch the demo →