CVE-2026-74274: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-xw27-v9cq-fc4v
Share
Published
Advisory Summary

CVE-2026-74274 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-74274 at a Glance

CVE Identifier CVE-2026-74274
GHSA Identifier GHSA-xw27-v9cq-fc4v
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-74274

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-74274, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

In the Linux kernel, the following vulnerability has been resolved: cxl/region: Fill first free targets[] slot during auto-discovery Any invalid endpoint decoder pointer in the target array of an active region is not allowed by cxl driver. This means cxl driver always assumes the first p->nr_targets entries of the target array in an auto-assembly region are valid. However, there are scenarios that could leave NULL endpoint decoder pointer holes in the target array. 1. When cxl_cancel_auto_attach() removes an endpoint decoder from a target array, the target slot is set to NULL. If the removed endpoint decoder is not the last element in the target array, the target array will contain a NULL hole. 2. When a auto-assembly region removes an assigned endpoint decoder, if the removed endpoint decoder is not the last element in the target array, always remains a NULL hole in the target array. When a NULL pointer hole exists in a region's target array, it introduces two potential problems: 1. Access an endpoint decoder via a NULL pointer. it always trigger calltrace like that. Oops: general protection fault, probably for non-canonical address 0xdffffc0000000008: 0000 [#1] SMP KASAN PTI RIP: 0010:cxl_calc_interleave_pos+0x26/0x810 [cxl_core] Call Trace: <TASK> cxl_region_attach+0xc50/0x2140 [cxl_core] cxl_add_to_region+0x321/0x2330 [cxl_core] discover_region+0x92/0x150 [cxl_port] device_for_each_child+0xf3/0x170 cxl_port_probe+0x150/0x200 [cxl_port] cxl_bus_probe+0x4f/0xa0 [cxl_core] really_probe+0x1c8/0x960 __driver_probe_device+0x323/0x450 driver_probe_device+0x45/0x120 __device_attach_driver+0x15d/0x280 bus_for_each_drv+0x10f/0x190 2. Not having enough valid endpoint decoders attached to an auto-assembly region. if an auto-assembly region is created with lock flag or assigned endpoint decoder with lock flag, which means assigned endpoint decoder will not be reset during detaching, they could re-attach to the auto-assembly region again. But cxl region driver relies on p->nr_targets to verify whether the required number of endpoint decoders has been attached, and NULL endpoint decoder pointers are still counted in that case. To fix above issues, adjust cxl_region_attach_auto() logic to find the first free target slot for endpoint decoder attachment, this ensures NULL holes in the target array are filled, rather than adding new endpoint decoders at the tail of the target array.

References

NVD — CVE-2026-74274 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-74274
git.kernel.org/stable/c/6fde3fcdfe... WEB
https://git.kernel.org/stable/c/6fde3fcdfec438ba0df26e25a8ac7c3707211799
git.kernel.org/stable/c/aa8a76711c... WEB
https://git.kernel.org/stable/c/aa8a76711c15041ec1e42c3a74c15c2df0bd31f6

Frequently Asked Questions

What is CVE-2026-74274?
CVE-2026-74274 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-74274?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-74274?
CVE-2026-74274 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-74274?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-xw27-v9cq-fc4v",
  "modified" : "2026-08-15T06:32:27Z",
  "published" : "2026-08-15T06:32:27Z",
  "aliases" : [ "CVE-2026-74274" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ncxl/region: Fill first free targets[] slot during auto-discovery\n\nAny invalid endpoint decoder pointer in the target array of an active\nregion is not allowed by cxl driver. This means cxl driver always\nassumes the first p->nr_targets entries of the target array in an\nauto-assembly region are valid. However, there are scenarios that could\nleave NULL endpoint decoder pointer holes in the target array.\n\n1. When cxl_cancel_auto_attach() removes an endpoint decoder from a\n   target array, the target slot is set to NULL. If the removed endpoint\n   decoder is not the last element in the target array, the target array\n   will contain a NULL hole.\n\n2. When a auto-assembly region removes an assigned endpoint decoder, if\n   the removed endpoint decoder is not the last element in the target\n   array, always remains a NULL hole in the target array.\n\nWhen a NULL pointer hole exists in a region's target array, it\nintroduces two potential problems:\n1. Access an endpoint decoder via a NULL pointer. it always trigger\n   calltrace like that.\n    Oops: general protection fault, probably for non-canonical address 0xdffffc0000000008: 0000 [#1] SMP KASAN PTI\n    RIP: 0010:cxl_calc_interleave_pos+0x26/0x810 [cxl_core]\n    Call Trace:\n      <TASK>\n      cxl_region_attach+0xc50/0x2140 [cxl_core]\n      cxl_add_to_region+0x321/0x2330 [cxl_core]\n      discover_region+0x92/0x150 [cxl_port]\n      device_for_each_child+0xf3/0x170\n      cxl_port_probe+0x150/0x200 [cxl_port]\n      cxl_bus_probe+0x4f/0xa0 [cxl_core]\n      really_probe+0x1c8/0x960\n      __driver_probe_device+0x323/0x450\n      driver_probe_device+0x45/0x120\n      __device_attach_driver+0x15d/0x280\n      bus_for_each_drv+0x10f/0x190\n\n2. Not having enough valid endpoint decoders attached to an\n   auto-assembly region. if an auto-assembly region is created with lock\n   flag or assigned endpoint decoder with lock flag, which means\n   assigned endpoint decoder will not be reset during detaching, they\n   could re-attach to the auto-assembly region again. But cxl region\n   driver relies on p->nr_targets to verify whether the required number\n   of endpoint decoders has been attached, and NULL endpoint decoder\n   pointers are still counted in that case.\n\nTo fix above issues, adjust cxl_region_attach_auto() logic to find the\nfirst free target slot for endpoint decoder attachment, this ensures\nNULL holes in the target array are filled, rather than adding new\nendpoint decoders at the tail of the target array.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-74274"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6fde3fcdfec438ba0df26e25a8ac7c3707211799"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/aa8a76711c15041ec1e42c3a74c15c2df0bd31f6"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:22:26Z"
  }
}