LiveActive security incident?Get immediate response
CVE Record

CVE-2026-43307: iio: accel: adxl380: Avoid reading more entries than present in FIFO

In the Linux kernel, the following vulnerability has been resolved: iio: accel: adxl380: Avoid reading more entries than present in FIFO The interrupt handler reads FIFO entries in batches of N samples, where N is the number of scan elements that have been enabled. However, the sensor fills the FIFO one sample at a time, even when more than one channel is enabled. Therefore,the number of entries reported by the FIFO status registers may not be a multiple of N; if this number is not a multiple, the number of entries read from the FIFO may exceed the number of entries actually present. To fix the above issue, round down the number of FIFO entries read from the status registers so that it is always a multiple of N.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-43307 is a Linux kernel driver flaw in the ADXL380 accelerometer handling code. A local user may be able to trigger incorrect FIFO reads, with CVSS impact rated high for confidentiality, integrity, and availability. There is no cited evidence of active exploitation, and exposure is likely limited to systems using this driver path.

Executive priority

Treat as a high-priority kernel maintenance item for Linux fleets that use this sensor driver. It is not currently supported by cited evidence of active exploitation, so urgency should be strongest for exposed embedded, IoT, or hardware-integrated systems using ADXL380.

Technical view

The iio accel adxl380 interrupt handler reads FIFO entries in batches based on enabled scan elements. The sensor reports entries one sample at a time, so the count may not align with the batch size. The fix rounds the read count down to a valid multiple, avoiding reads beyond entries actually present.

Likely exposure

Linux systems with affected kernel versions and the ADXL380 IIO accelerometer driver present or in use are the most relevant exposure. Exact distribution package impact is not fully defined in the provided sources, so teams should map kernel builds to vendor advisories or backported stable commits.

Exploitation context

The CVSS vector is local, low-complexity, low-privilege, and requires no user interaction. The source bundle does not identify public exploitation, and KEV status is false. Practical exploitability depends on local access and whether the affected driver and hardware path are reachable.

Researcher notes

The public record describes the root cause and fix direction but does not provide a CWE or detailed distro matrix. Avoid assuming broad server exposure without driver and hardware evidence. Review the referenced kernel commits and vendor backports for exact affected branches.

Mitigation direction

  • Apply a vendor kernel update containing the referenced stable fixes.
  • If using custom kernels, incorporate the relevant upstream stable commit.
  • Check Linux distribution advisories for backport status and package names.
  • Prioritize devices that use ADXL380 accelerometer functionality.

Validation and detection

  • Inventory Linux kernel versions across relevant systems.
  • Determine whether the ADXL380 IIO driver is built, loaded, or required.
  • Confirm the running kernel includes the stable fix or vendor backport.
  • Document systems where distribution guidance is still pending.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-43307 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2026-43307Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxdf36de13677a0ebd3ab31dd2c603f9eafdf8de7d, df36de13677a0ebd3ab31dd2c603f9eafdf8de7d, df36de13677a0ebd3ab31dd2c603f9eafdf8de7d, df36de13677a0ebd3ab31dd2c603f9eafdf8de7dunaffected
LinuxLinux6.12, 0, 6.12.75, 6.18.16, 6.19.6, 7.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.