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

crypto: ccp - Fix snp_filter_reserved_mem_regions() off-by-one

Sashiko notes:

> regarding the bounds check in snp_filter_reserved_mem_regions()
> called via walk_iomem_res_desc(): does the check
> if ((range_list->num_elements * 16 + 8) > PAGE_SIZE)
> allow an off-by-one heap buffer overflow?
>
> If range_list->num_elements is 255, 255 * 16 + 8 = 4088, which is <= 4096.
> Writing range->base (8 bytes) fills 4088-4095, but writing range->page_count
> (4 bytes) would write to 4096-4099, overflowing the kzalloc-allocated
> PAGE_SIZE buffer.

Fix this by accounting for the entry about to be written to, in addition to
the entries that are already allocated.
Published: 2026-08-15
Score: 7.8 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A bounds‑checking error in the Linux kernel’s snp_filter_reserved_mem_regions() function allows an off‑by‑one heap buffer overflow when a specially crafted range list with 255 elements is processed. The overflow occurs because the check does not account for the incoming entry, allowing data beyond the allocated PAGE_SIZE buffer to be written. An attacker with the ability to supply such data to the crypto CCP module could corrupt kernel memory or gain arbitrary code execution, effectively elevating privileges to kernel level. The flaw is a classic heap‑based buffer overflow and is therefore an exploitable vulnerability that can compromise system confidentiality, integrity, and availability.

Affected Systems

The vulnerability impacts all Linux kernels that include the crypto CCP component. No specific version numbers are listed in the data, so it may affect multiple releases until a patch is applied. This includes standard distributions that ship the upstream kernel.

Risk and Exploitability

The CVSS score is 7.8, indicating high severity. The EPSS score of 0.00186 indicates a very low but non‑zero probability of exploitation in the general population, though the flaw remains valuable for targeted attacks. The vulnerability is not listed in the CISA KEV catalog, which does not reduce the risk of a targeted exploitation. Given that the flaw resides in a low‑level component, an attacker would likely need to inject crafted data into the CCP module, which may be limited to privileged or privileged‑escalated users, but the potential impact remains severe.

Generated by OpenCVE AI on August 17, 2026 at 12:04 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a version that includes the fix for snp_filter_reserved_mem_regions(). The official fix has already been committed to stable branches; install the latest kernel update available from your distribution.
  • If an update is not immediately available, disable or restrict the CCP crypto module. This can be done by setting CONFIG_CRYPTO_CCP=y in the kernel config and ensuring the module is not loaded unless required, or by using boot‑time kernel module disabling options such as modprobe.d overrides.
  • Apply kernel hardening measures such as enabling KASLR, enforcing SELinux or AppArmor confinement, and restricting write access to /dev/mem or related interfaces. These mitigations reduce the window of exploitation even if the overflow is present.

Generated by OpenCVE AI on August 17, 2026 at 12:04 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 21 Aug 2026 00:15:00 +0000


Mon, 17 Aug 2026 06:00:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}


Sat, 15 Aug 2026 14:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-119
CWE-787

Sat, 15 Aug 2026 06:15:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Fix snp_filter_reserved_mem_regions() off-by-one Sashiko notes: > regarding the bounds check in snp_filter_reserved_mem_regions() > called via walk_iomem_res_desc(): does the check > if ((range_list->num_elements * 16 + 8) > PAGE_SIZE) > allow an off-by-one heap buffer overflow? > > If range_list->num_elements is 255, 255 * 16 + 8 = 4088, which is <= 4096. > Writing range->base (8 bytes) fills 4088-4095, but writing range->page_count > (4 bytes) would write to 4096-4099, overflowing the kzalloc-allocated > PAGE_SIZE buffer. Fix this by accounting for the entry about to be written to, in addition to the entries that are already allocated.
Title crypto: ccp - Fix snp_filter_reserved_mem_regions() off-by-one
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-17T05:46:46.485Z

Reserved: 2026-08-15T05:44:03.892Z

Link: CVE-2026-74404

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-15T06:22:42.433

Modified: 2026-08-17T06:19:35.607

Link: CVE-2026-74404

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-08-15T00:00:00Z

Links: CVE-2026-74404 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-17T12:15:17Z

Weaknesses
  • CWE-119

    Improper Restriction of Operations within the Bounds of a Memory Buffer

  • CWE-787

    Out-of-bounds Write