LiveActive security incident?Get immediate response
CVE Record

CVE-2023-26242: afu_mmio_region_get_by_offset in drivers/fpga/dfl-afu-region.c in the Linux kernel through 6.1.12 has an in...

afu_mmio_region_get_by_offset in drivers/fpga/dfl-afu-region.c in the Linux kernel through 6.1.12 has an integer overflow.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a high-severity Linux kernel flaw in FPGA DFL AFU memory-region handling. A local user could trigger an integer overflow that may compromise confidentiality, integrity, and availability. Business urgency is highest for Linux systems or appliances that expose the affected FPGA subsystem or ship vendor kernels carrying this code.

Executive priority

Treat as a targeted high-priority kernel update item, not an internet-wide emergency. Prioritize regulated, multi-user, appliance, or shared compute environments where local privilege boundaries matter and FPGA functionality may be present.

Technical view

CVE-2023-26242 is a CWE-190 integer overflow in afu_mmio_region_get_by_offset in drivers/fpga/dfl-afu-region.c, reported for Linux kernel versions through 6.1.12. The CVSS vector is local, low complexity, low privileges, no user interaction, with high CIA impact.

Likely exposure

Exposure appears limited to systems running affected Linux kernels where the FPGA DFL AFU code path is present and reachable by a local low-privileged user. The bundle does not provide complete affected product, distribution, or appliance version lists.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. The CVSS vector indicates local exploitation with low privileges and no user interaction, but no public exploit status is established by the provided sources.

Researcher notes

Key uncertainty is exposure scope: the CVE record names the kernel file and version boundary, while the affected product list in the bundle is not populated. Validate reachability against actual kernel configuration, hardware, and vendor backports before assigning asset risk.

Mitigation direction

  • Apply vendor kernel updates that include the upstream fix when available.
  • Check NetApp and SUSE guidance for affected product-specific remediation.
  • Prioritize systems with FPGA DFL or AFU functionality enabled.
  • If unused, assess vendor-supported ways to disable FPGA DFL AFU exposure.
  • Track kernel package status for versions newer than 6.1.12.

Validation and detection

  • Inventory Linux kernel versions and flag systems at or below 6.1.12.
  • Identify hosts or appliances using FPGA DFL AFU-related kernel functionality.
  • Confirm vendor advisory status for NetApp, SUSE, and other deployed distributions.
  • Verify remediation through vendor package metadata or kernel changelogs.
  • Document any systems requiring compensating controls pending updates.
Prepared
Confidence
medium
Sources
5

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.

cwe · low confidence lookup

CWE-190: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-26242 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
0Timeline events
0ADP providers
4Source 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.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2023-26242Attack 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-190 · source CWE mapping

Integer Overflow or Wraparound

Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.