CVE-2026-47334
MediumCVSS 5.5Exploitation Probability (EPSS)
Low risk2th percentile - higher than 2% of all known CVEs
Summary
Ubuntu Linux 6.8, 6.17, and 7.0 contain AppArmor SAUCE patches which incorrectly sleep while holding a spinlock in notification handling code. The bug can be triggered by an unprivileged local user and can result in kernel panic or deadlock.
Risk Assessment
The organization may experience significant disruptions in system operation, including kernel crashes, which can lead to service unavailability.
Recommendation
It is recommended to update the system to the latest version to mitigate this vulnerability and to monitor the system for unauthorized actions by local users.
Other vulnerabilities in Ubuntu Linux 6.8, 6.17, 7.0
See all- CVE-2026-47333High
Ubuntu Linux 6.8, 6.17, and 7.0 contain AppArmor SAUCE patches that may incorrectly compute the size of an internal buffer, leading to a heap memory out-of-bounds read in notification handling code.
- CVE-2026-47332Medium
Ubuntu Linux 6.8, 6.17, and 7.0 contain AppArmor SAUCE patches that incorrectly validate the size of an internal structure, leading to an out-of-bounds read in notification handling code.
- CVE-2026-47328Medium
Ubuntu Linux 6.8, 6.17, and 7.0 contain AppArmor SAUCE patches that incorrectly attempt to free a pointer that was not previously kmalloc()d, leading to memory leaks. The bug can be triggered by an unprivileged local user.
- CVE-2026-47327Low
Ubuntu Linux 6.8, 6.17, and 7.0 contain SAUCE patches that may lead to a NULL pointer dereference in the handling of AppArmor notifications. The bug can be triggered by an unprivileged local user, potentially resulting in a kernel oops.
- CVE-2026-47326Medium
Ubuntu Linux 6.8, 6.17, and 7.0 contain SAUCE patches with a memory leak in the handling of big responses to AppArmor notifications. The bug can be triggered by an unprivileged local user.
Original NVD description (English source)
Ubuntu Linux 6.8, 6.17 and 7.0 contain AppArmor SAUCE patches which incorrectly sleep while holding a spinlock in notification handling code. The bug can be triggered by an unprivileged local user and can result in kernel panic or deadlock.