Vulnerability · Published May 27, 2026 · Assigned by Linux
CVE-2026-45966apparmor: fix NULL pointer dereference in __unix_needs_revalidation
Medium 5.5
In plain English
A medium-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.
Official description
In the Linux kernel, the following vulnerability has been resolved: apparmor: fix NULL pointer dereference in __unix_needs_revalidation When receiving file descriptors via SCM_RIGHTS, both the socket pointer and the socket's sk pointer can be NULL during socket setup or teardown, causing NULL pointer dereferences in __unix_needs_revalidation(). This is a regression in AppArmor 5.0.0 (kernel 6.17+) where the new __unix_needs_revalidation() function was added without proper NULL checks. The crash manifests as: BUG: kernel NULL pointer dereference, address: 0x0000000000000018 RIP: aa_file_perm+0xb7/0x3b0 (or +0xbe/0x3b0, +0xc0/0x3e0) Call Trace: apparmor_file_receive+0x42/0x80 security_file_receive+0x2e/0x50 receive_fd+0x1d/0xf0 scm_detach_fds+0xad/0x1c0 The function dereferences sock->sk->sk_family without checking if either sock or sock->sk is NULL first. Add NULL checks for both sock and sock->sk before accessing sk_family.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:14 | linux | 6.18.14-1 | DEBIAN-CVE-2026-45966 |
| Ubuntu:25.10 | linux | 6.17.0-29.29 | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:25.10 | linux-aws | 6.17.0-1015.15 | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | 6.17.0-1017.17~24.04.1 | UBUNTU-CVE-2026-45966 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | 6.17.0-1017.17~24.04.1 | USN-8374-1 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:25.10 | linux-azure | 6.17.0-1015.15 | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | 6.17.0-1015.15~24.04.1 | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:25.10 | linux-azure-fde | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:25.10 | linux-gcp | 6.17.0-1018.19 | UBUNTU-CVE-2026-45966 |
| Ubuntu:25.10 | linux-gcp | 6.17.0-1018.19 | USN-8374-1 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | 6.17.0-1018.19~24.04.1 | USN-8374-1 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | 6.17.0-1018.19~24.04.1 | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | 6.17.0-29.29~24.04.1 | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | 6.17.0-1026.26 | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | 6.17.0-1023.23 | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:25.10 | linux-oracle | 6.17.0-1014.14 | UBUNTU-CVE-2026-45966 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | 6.17.0-1014.14~24.04.1 | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:25.10 | linux-raspi | 6.17.0-1017.17 | UBUNTU-CVE-2026-45966 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:25.10 | linux-realtime | 6.17.0-1013.15 | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:25.10 | linux-riscv | 6.17.0-29.29.1 | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | 6.17.0-29.29.1~24.04.1 | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2026-45966 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2026-45966 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 88fec3526e84123997ecebd6bb6778eb4ce779b7 – before fea017a7f6abe179decf575a2d8464c74edb396488fec3526e84123997ecebd6bb6778eb4ce779b7 – before e85bc9101afc4202aa2269967ce9d3ffbecd099488fec3526e84123997ecebd6bb6778eb4ce779b7 – before e2938ad00b21340c0362562dfedd7cfec0554d67 |
| Linux | Linux | 6.17 |