Vulnerability · Published Jul 19, 2026 · Assigned by Linux

CVE-2026-63827apparmor: fix use-after-free in rawdata dedup loop

High 7.8

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 2% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.8High
Exploit odds (30 days)0.1%top 97.9% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: apparmor: fix use-after-free in rawdata dedup loop aa_replace_profiles() walks ns->rawdata_list to dedup the incoming policy blob against entries already attached to existing profiles. Per the kernel-doc on struct aa_loaddata, list membership does not hold a reference: profiles hold pcount, and when the last pcount drops, do_ploaddata_rmfs() is queued on a workqueue that takes ns->lock and removes the entry. Between dropping the last pcount and the workqueue running, an entry remains on the list with pcount == 0. aa_get_profile_loaddata() is an unconditional kref_get() on pcount, so when the dedup loop hits such an entry, refcount hardening reports refcount_t: addition on 0; use-after-free. inside aa_replace_profiles(), and the poisoned counter then trips "saturated" and "underflow" warnings on the subsequent uses of the same loaddata. Before commit a0b7091c4de4 ("apparmor: fix race on rawdata dereference") the dedup path used a get_unless_zero-style helper on a single counter, so the existing "if (tmp)" guard was meaningful. The split-refcount refactor introduced aa_get_profile_loaddata(), which has plain kref_get() semantics, and the guard quietly became a no-op. Introduce aa_get_profile_loaddata_not0(), matching the existing _not0 convention used by aa_get_profile_not0(), and use it for the rawdata_list dedup lookup so dying entries are skipped. Reproduced on x86_64 with v7.1-rc5 in QEMU+KVM running Ubuntu 24.04 + stress-ng 0.17.06: stress-ng --apparmor 1 --klog-check --timeout 60s Without this patch the three refcount_t warnings fire within a few seconds. With it the same 60 s run is clean. Coverage is a smoke-test only; a longer soak with CONFIG_KASAN, CONFIG_KCSAN and CONFIG_PROVE_LOCKING would be welcome from anyone with the cycles.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.177-1DEBIAN-CVE-2026-63827
Debian:13linux6.12.95-1DEBIAN-CVE-2026-63827
Debian:14linux7.1.3-1DEBIAN-CVE-2026-63827
Ubuntu:22.04:LTSlinux5.15.0-198.208UBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux6.8.0-147.147UBUNTU-CVE-2026-63827
Ubuntu:26.04:LTSlinux7.0.0-31.31UBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-aws5.15.0-1117.124UBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-aws6.8.0-1067.70UBUNTU-CVE-2026-63827
Ubuntu:26.04:LTSlinux-aws7.0.0-1012.12UBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-aws-7.07.0.0-1012.12~24.04.1UBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-azure5.15.0-1123.132UBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-azure6.8.0-1071.79UBUNTU-CVE-2026-63827
Ubuntu:26.04:LTSlinux-azure7.0.0-1014.14UBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-azure-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1122.131UBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-azure-fde6.8.0-1069.76UBUNTU-CVE-2026-63827
Ubuntu:26.04:LTSlinux-azure-fde7.0.0-1013.13UBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-azure-fde-7.07.0.0-1013.13~24.04.1UBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-gcp5.15.0-1118.128UBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-gcp6.8.0-1071.79UBUNTU-CVE-2026-63827
Ubuntu:26.04:LTSlinux-gcp7.0.0-1011.11UBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-gcp-7.07.0.0-1011.11~24.04.1UBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-gke5.15.0-1113.119UBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-gke6.8.0-1066.74UBUNTU-CVE-2026-63827
Ubuntu:26.04:LTSlinux-gke7.0.0-1006.7UBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1100.108UBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1052.56UBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-31.31~24.04.1UBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-ibm5.15.0-1111.115UBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-ibm6.8.0-1067.68UBUNTU-CVE-2026-63827
Ubuntu:26.04:LTSlinux-ibm7.0.0-1013.13UBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1112.118UBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-kvm5.15.0-1109.114UBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-195.205UBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-147.147.1UBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1112.113UBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-63827
Ubuntu:26.04:LTSlinux-nvidia7.0.0-1018.18UBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-nvidia-7.07.0.0-1018.18~24.04.1UBUNTU-CVE-2026-63827
Ubuntu:26.04:LTSlinux-nvidia-bos7.0.0-2018.18UBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1070.72UBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1036.39UBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1059.59UBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-63827
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1013.13UBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-oracle5.15.0-1114.120UBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-oracle6.8.0-1064.67UBUNTU-CVE-2026-63827
Ubuntu:26.04:LTSlinux-oracle7.0.0-1011.11UBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-oracle-7.07.0.0-1011.11~24.04.1UBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-63827
Ubuntu:26.04:LTSlinux-raspi7.0.0-1019.19UBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-63827
Ubuntu:26.04:LTSlinux-realtime7.0.0-31.31.1UBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-63827
Ubuntu:26.04:LTSlinux-riscv7.0.0-31.31.1UBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-31.31.1~24.04.1UBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-vmware6.8.0-1008.8UBUNTU-CVE-2026-63827
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-63827
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1080.84UBUNTU-CVE-2026-63827

Affected products (as reported)

VendorProductVersions
Linux Linux 3b8e77c7abab40e6de9ad9de730d77984a498840 – before 643221da57dbb1a8fd800610331cf1ec27969f71d9d8560b9b7932f8cffc4c068c14289220900f79 – before b17f0c59cc1525765625cf07d0391b7f9c1ed7e56b6ba87579c7e7c669e0bec91823e7fb693bc5df – before a7a2890028f16e5b0af0bb005d80fcb32559cca36ef1f2926c41ab96952d9696d55a052f1b3a9418 – before 15fd83a1e42ede15070968806bb6c8b1a5170688f9761add6d100962a23996cb68f3d6abdd4d1815 – before ce261a20b41db522e320a41bbf1292bf85af66dfaf782cc8871e3683ddd5a3cd2f7df526599863a9 – before c3ca2631073b2cef06824fd2bfc452ff7a1023dea0b7091c4de45a7325c8780e6934a894f92ac86b – before 5e34fa9f6f7cd688ae153fff13139a5cf2d42339a0b7091c4de45a7325c8780e6934a894f92ac86b – before 6f060496d03e4dc560a40f73770bd08335cb7a27
Linux Linux 7.0

References