CVE-2026-80619 json
apparmor: fix potential UAF in aa_replace_profiles
published 2mo ago modified 2mo ago also EUVD-2026-67495
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
apparmor: fix potential UAF in aa_replace_profiles
The function aa_replace_profiles was accessing udata->size after calling aa_put_loaddata(udata), causing a potential UAF.
Fixed this by saving the size to a local variable before dropping the reference.
Patch / fix
- Linux Linux 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5, 7.2
- linux Debian 12 6.1.180-1
- linux Debian 13 6.12.100-1
- linux Debian 14 7.1.5-1
debian advisories DEBIAN-CVE-2026-80619
- linux Ubuntu 22.04 LTS 5.15.0-198.208
- linux Ubuntu 24.04 LTS 6.8.0-147.147
- linux Ubuntu 26.04 LTS 7.0.0-38.38
- linux-aws Ubuntu 22.04 LTS 5.15.0-1117.124
- linux-aws Ubuntu 24.04 LTS 6.8.0-1067.70
- linux-aws Ubuntu 26.04 LTS 7.0.0-1014.14
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1118.128
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1071.79
ubuntu advisories UBUNTU-CVE-2026-80619
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
- git.kernel.org/stable/c/9d8e47cbce7536f19c96e37d0685a042010187ee commit
- git.kernel.org/stable/c/9d37dc6376e336dc4b4f39a7ad0d069aa70e9495 commit
- git.kernel.org/stable/c/c0f3a3fda617beeec58708720304dd026a1a4dd7 commit
- git.kernel.org/stable/c/5cba148eae6e8550c2889f5c0f94d72bed864321 commit
- git.kernel.org/stable/c/c44de0880b7ccc15c70a6352b5e107677d32b061 commit
- git.kernel.org/stable/c/57b1bd4486d56254bb8af1a8f3d4445bbe505290 commit
- git.kernel.org/stable/c/dd5f1202f45a2dbe2c7dd10093f5c6bb2d8ac5bb commit
- git.kernel.org/stable/c/7b42f95813dc9ceb6bda35afcf914630909a19f9 commit
Is CVE-2026-80619 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-80619 updated cvss 5.5
kernel: apparmor: fix potential UAF in aa_replace_profiles
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more 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 kernelnot 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.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/9d8e47cbce7536f19c96e37d0685a042010187ee
- git.kernel.org /stable/c/9d37dc6376e336dc4b4f39a7ad0d069aa70e9495
- git.kernel.org /stable/c/c0f3a3fda617beeec58708720304dd026a1a4dd7
- git.kernel.org /stable/c/5cba148eae6e8550c2889f5c0f94d72bed864321
- git.kernel.org /stable/c/c44de0880b7ccc15c70a6352b5e107677d32b061
- git.kernel.org /stable/c/57b1bd4486d56254bb8af1a8f3d4445bbe505290
- git.kernel.org /stable/c/dd5f1202f45a2dbe2c7dd10093f5c6bb2d8ac5bb
- git.kernel.org /stable/c/7b42f95813dc9ceb6bda35afcf914630909a19f9
Sources
- CVE List CVE-2026-80619
- NVD CVE-2026-80619
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.