MEDIUM 5.5

CVE-2026-52972 Linux Kernel af_alg AEAD Integer Overflow DoS Vulnerability

A vulnerability in the Linux kernel's cryptographic socket implementation allows a local attacker to trigger an arithmetic overflow when processing AEAD (Authenticated Encryption with Associated Data) operations. By crafting requests with excessively large associated data lengths, an attacker can cause a denial-of-service condition affecting system stability. The vulnerability requires local access and standard user privileges to exploit.

Source data · NVD / CISA · public domain

CVSS
3.1 · 5.5 MEDIUM · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weaknesses (CWE)
CWE-190
Affected products
1 configuration(s)
Published / Modified
2026-06-24 / 2026-07-24

NVD description (verbatim)

In the Linux kernel, the following vulnerability has been resolved: crypto: af_alg - Cap AEAD AD length to 0x80000000 In order to prevent arithmetic overflows when checking the TX buffer size, cap the associated data length to 0x80000000.

12 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-52972 is an integer overflow vulnerability in the Linux kernel's af_alg (Application Family socket for cryptographic algorithms) subsystem. The vulnerability exists in the AEAD associated data (AD) length validation logic. Without a cap on the AD length parameter, arithmetic operations performed during TX buffer size validation can overflow, leading to memory allocation failures or denial of service. The fix implements a cap of 0x80000000 (2GB) on the AEAD AD length to prevent overflow conditions during buffer calculations.

Business impact

This vulnerability can disrupt cryptographic services and applications relying on kernel-level AEAD operations through denial of service. Organizations using Linux systems for security-sensitive workloads—including VPN gateways, encrypted storage systems, or TLS acceleration—may experience service interruptions if this flaw is exploited. The impact is primarily availability-focused rather than confidentiality or integrity, but application crashes can cascade to dependent services.

Affected systems

The vulnerability affects Linux kernel implementations that include the af_alg subsystem with AEAD cipher support. Any distribution or embedded system running a vulnerable kernel version is at risk. Organizations should consult their distribution's security advisories to determine which specific kernel versions are affected and the corresponding patch schedules.

Exploitability

Exploitation requires local system access and standard (non-root) user privileges, making this vulnerability less attractive to remote attackers but viable for local privilege escalation or lateral movement scenarios. No known public exploits have been documented in the kernel vulnerabilities database, and this is not tracked as an in-the-wild exploitation target. The barrier to exploitation is moderate—an attacker must craft specific AEAD requests, but no specialized tools or complex conditions are required.

Remediation

Apply kernel security updates that include the fix capping AEAD AD length to 0x80000000. Most mainstream distributions have already released or are preparing patches. Verify the specific patched kernel version from your distribution's security advisory, as version numbers vary. For systems unable to patch immediately, consider restricting local user access and reviewing application-level access controls for cryptographic services.

Patch guidance

Monitor your Linux distribution's security bulletins for kernel updates addressing this vulnerability. Patch versions vary by distribution (Red Hat, Debian, Ubuntu, SUSE, etc.); refer to your vendor's advisory for exact version numbers and deployment timelines. Coordinate kernel patching with change management protocols, as it typically requires a system reboot. Test patches in non-production environments before production deployment.

Detection guidance

Look for failed AEAD cipher operations, kernel crashes, or out-of-memory errors in systems processing large cryptographic operations. Monitor kernel logs for af_alg-related errors or buffer allocation failures. Network-based detection is limited due to the local nature of the vulnerability; focus on endpoint monitoring for suspicious cryptographic API calls with abnormally large parameters from non-privileged processes.

Why prioritize this

While the CVSS score of 5.5 (MEDIUM) reflects the local-access requirement and availability-only impact, this vulnerability should be prioritized for patching to maintain the integrity of cryptographic services. Organizations with strict availability requirements, especially those running cryptographic appliances or middleware, should treat this as moderately urgent. The lack of in-the-wild exploitation provides a reasonable window for controlled, planned patching.

Risk score, explained

The CVSS 3.1 vector (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) reflects a local attack vector (AV:L) with low attack complexity (AC:L), requiring low privileges (PR:L) and no user interaction (UI:N). The high availability impact (A:H) combined with no impact to confidentiality or integrity yields a MEDIUM severity rating of 5.5. The underlying integer overflow flaw (CWE-190) is correctly scoped to the affected system only (S:U) with no cross-boundary spillover.

Frequently asked questions

Can this vulnerability be exploited remotely?

No. The vulnerability requires local system access and standard user privileges. Remote attack scenarios are not feasible without prior compromise of the target system.

What cryptographic operations are affected?

The vulnerability specifically affects AEAD (Authenticated Encryption with Associated Data) cipher operations using the af_alg kernel socket interface. Applications using kernel-level AEAD implementations are at risk if they process requests with abnormally large associated data parameters.

Is there a workaround if I cannot patch immediately?

No robust workaround exists at the application level. Mitigation focuses on restricting local user access, disabling unnecessary cryptographic services, and prioritizing kernel patching. Application-level input validation cannot fully compensate for kernel-level vulnerabilities.

Do I need to reboot after applying the patch?

Yes, kernel security patches require a system reboot to take effect. Plan patching during maintenance windows and coordinate with change management procedures.

This analysis is based on published vulnerability data as of the modification date. Patch availability, affected versions, and remediation timelines vary by Linux distribution and deployment context. Organizations should verify specific vulnerable kernel versions and patch schedules against their vendor's official security advisories. This vulnerability is not currently tracked as actively exploited in the wild, but local access vulnerabilities can pose elevated risk in multi-tenant or shared hosting environments. No proof-of-concept code or exploitation techniques are provided in this analysis. Source: NVD (public-domain), retrieved 2026-07-30. Analysis generated by SEC.co (claude-haiku-4-5).