CVE-2026-98413 json
selinux: always fill AVC decision in avc_has_perm_noaudit()
published 28d ago modified 23d ago also EUVD-2026-101062
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 7.3
- linux Debian 12 6.1.190-1
- linux Debian 13 6.12.113-1
- linux Debian 14 7.2.8-1
- linux-6.12 Debian 12 6.12.113-1~deb12u1
debian advisories DEBIAN-CVE-2026-98413
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 24.04 LTS 6.8.0-149.149
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 24.04 LTS 6.8.0-1069.74
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1073.81
ubuntu advisories UBUNTU-CVE-2026-98413
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel Azure Linux 3.0 6.6.159.1-1
azure linux advisories AZL-108185
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/c781e737aa0de95289b1774d5fd29388895737a9 commit
- git.kernel.org/stable/c/e308c5acfe283a66627fc407065626df4ab753ec commit
- git.kernel.org/stable/c/f9da796fa238f8e4414ee8481e6c979759a3d563 commit
- git.kernel.org/stable/c/e77461af13eab5c9a953cc52ec8432cc941d61e2 commit
- git.kernel.org/stable/c/5a6f9a872b4ff68877caf998bee352153b7154bc commit
- git.kernel.org/stable/c/24e00850bcff46b984f4c44b92e5499450fcfb5a commit
- git.kernel.org/stable/c/835133337c2ce200db56f62d018c79087dee2603 commit
- git.kernel.org/stable/c/8861db305103107199b1426f25fde1fb6d465583 commit
Is CVE-2026-98413 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-98413 updated cvss 5.5
kernel: selinux: always fill AVC decision in avc_has_perm_noaudit()
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: workaround, no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: workaround, no fix available “Fix deferred”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/c781e737aa0de95289b1774d5fd29388895737a9
- git.kernel.org /stable/c/e308c5acfe283a66627fc407065626df4ab753ec
- git.kernel.org /stable/c/f9da796fa238f8e4414ee8481e6c979759a3d563
- git.kernel.org /stable/c/e77461af13eab5c9a953cc52ec8432cc941d61e2
- git.kernel.org /stable/c/5a6f9a872b4ff68877caf998bee352153b7154bc
- git.kernel.org /stable/c/24e00850bcff46b984f4c44b92e5499450fcfb5a
- git.kernel.org /stable/c/835133337c2ce200db56f62d018c79087dee2603
- git.kernel.org /stable/c/8861db305103107199b1426f25fde1fb6d465583
Sources
- CVE List CVE-2026-98413
- NVD CVE-2026-98413
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.