Menu

Star on GitHub · 3.2k

CVE-2026-74399

In the Linux kernel, the following vulnerability has been resolved: evm: terminate and bound the evm_xattrs read buffer evm_read_xattrs() allocates size + 1 bytes, fills them from the list of ena…

Published Aug 15, 2026EPSS 0.21%

Overview

CVE-2026-74399 is a known-severity vulnerability. It was published on August 15, 2026.

Technical description

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

evm: terminate and bound the evm_xattrs read buffer

evm_read_xattrs() allocates size + 1 bytes, fills them from the list of

enabled xattrs, and then passes strlen(temp) to

simple_read_from_buffer(). When no configured xattrs are enabled, the

fill loop stores nothing and temp[0] remains uninitialized, so strlen()

reads beyond initialized memory.

Explicitly terminate the buffer after allocation, use snprintf() for

each formatted line, and pass the accumulated length, without risk of

truncation, to simple_read_from_buffer().

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-74399?

CVE-2026-74399 is a known-severity vulnerability. It was published on August 15, 2026.

How severe is CVE-2026-74399?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-74399?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-74399?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-74399 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.