Menu

Star on GitHub · 3.4k

CVE-2026-98413

In the Linux kernel, the following vulnerability has been resolved: selinux: always fill AVC decision in avc_has_perm_noaudit() avc_has_perm_noaudit() is documented to return a copy of the access…

Published Oct 14, 2026EPSS 0.22%

Overview

CVE-2026-98413 is a known-severity vulnerability. It was published on October 14, 2026.

Technical description

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

selinux: always fill AVC decision in avc_has_perm_noaudit()

avc_has_perm_noaudit() is documented to return a copy of the access

decision in @avd, but its early return for an empty requested permission

set leaves the buffer untouched. All callers pass an uninitialized

stack variable and afterwards feed it to avc_audit(), and the inode hook

even stores it in the per-task decision cache.

Fill in a deny-all, audit-all decision, similar to avd_init(), so every

caller receives a defined value at no cost on the hot path.

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-98413?

CVE-2026-98413 is a known-severity vulnerability. It was published on October 14, 2026.

How severe is CVE-2026-98413?

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-98413?

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-98413?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-98413 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.

LiveWatch live →