CVE-2026-43307

Kernel memory corruption via unrounded FIFO count

Published May 8, 2026 · Updated May 8, 2026

Out-of-bounds write in the Linux kernel ADXL380 driver allows local users to corrupt kernel memory through incorrect FIFO batching. The interrupt handler fills st->fifo_buf in enabled-channel batches without rounding down the reported FIFO entry count, so a final partial batch writes beyond the fixed buffer. Reachability requires local access to IIO buffer and scan controls, multiple enabled scan elements, and an attached ADXL380 device; corruption can disclose data, alter kernel state, or crash the system.

CVSS severity7.8
High
EPSS probability0.13%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Out-of-bounds write in the Linux kernel ADXL380 driver allows local users to corrupt kernel memory through incorrect FIFO batching. The interrupt handler fills st->fifo_buf in enabled-channel batches without rounding down the reported FIFO entry count, so a final partial batch writes beyond the fixed buffer. Reachability requires local access to IIO buffer and scan controls, multiple enabled scan elements, and an attached ADXL380 device; corruption can disclose data, alter kernel state, or crash the system.

The record

CVE
CVE-2026-43307
Published
May 8, 2026
Updated
May 8, 2026
Vendor
The Linux Kernel Organization
Product
Linux Kernel
Classifications
T1068
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. May 8, 2026CVE publishedPublication date reported by the CVE source.
  2. May 8, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=6.12
  2. Affected versionversion=df36de13677a0ebd3ab31dd2c603f9eafdf8de7d <a40f316085985f916ba1599fc303fdbc6a078e86
  3. Affected versionversion=df36de13677a0ebd3ab31dd2c603f9eafdf8de7d <a8e88edfd69df7b63c882aa53e61e7c078806ad7
  4. Affected versionversion=df36de13677a0ebd3ab31dd2c603f9eafdf8de7d <c1b14015224cfcccd5356333763f2f4f401bd810
  5. Affected versionversion=df36de13677a0ebd3ab31dd2c603f9eafdf8de7d <f42ddb2945ae4ce2b6f1c2e7aae9f14455a734d3

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linux Kernelversion=6.12; version=df36de13677a0ebd3ab31dd2c603f9eafdf8de7d <a40f316085985f916ba1599fc303fdbc6a078e86; version=df36de13677a0ebd3ab31dd2c603f9eafdf8de7d <a8e88edfd69df7b63c882aa53e61e7c078806ad7; version=df36de13677a0ebd3ab31dd2c603f9eafdf8de7d <c1b14015224cfcccd5356333763f2f4f401bd810; version=df36de13677a0ebd3ab31dd2c603f9eafdf8de7d <f42ddb2945ae4ce2b6f1c2e7aae9f14455a734d3

Published CVSS scores

7.8kernel.orgCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1068Exploitation for Privilege Escalation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo