Home / Security updates / CrackArmor Vulnerabilities
CrackArmor Vulnerabilities
Security updates detail rendered from /security-updates/upd_466db7dd19796372.
Overview
| ID | upd_466db7dd19796372 |
| Collection | Security Updates |
| Provider | SafeBase |
| Company | Scaleway |
| URL | - |
| Counts | - |
| Updated | - |
Raw record
| Field | Value |
|---|---|
| id | upd_466db7dd19796372 |
| providerId | safebase |
| organizationId | org_9c40dfe3f8d30eb8 |
| trustCenterId | tc_97ceaa0bb95c8ff7 |
| title | CrackArmor Vulnerabilities |
| message | # Security Advisory: CrackArmor (AppArmor Vulnerabilities) ## 1. Definition CrackArmor is the collective name for a suite of nine vulnerabilities discovered in the Linux kernel’s AppArmor security module, disclosed in March 2026. These flaws represent a significant breakdown in the kernel's access control mechanisms, allowing an unprivileged local attacker to bypass security boundaries, trigger a Denial of Service (DoS), or achieve a full Local Privilege Escalation (LPE) to root. ## 2. How It Works The core of the CrackArmor suite is a classic "confused deputy" vulnerability located within AppArmor’s interface for managing security profiles. AppArmor uses several pseudo-files (such as .load, .replace, and .remove) found within the securityfs filesystem (typically at `/sys/kernel/security/apparmor/`). The vulnerability stems from two critical oversights: * **Permissions Mismatch**: These control files were mistakenly set to be world-writable. While the kernel eventually checks for |
| url | - |
| publishedAt | 2026-03-18 |
| source | {
"field": "statuspage/public/compliance-update",
"category": "vulnerabilities"
} |
| company | {
"id": "org_9c40dfe3f8d30eb8",
"name": "Scaleway",
"domains": [
"security.scaleway.com",
"scaleway.com"
]
} |
| trust_center | {
"id": "tc_97ceaa0bb95c8ff7",
"name": "Scaleway",
"url": "https://security.scaleway.com",
"host": "security.scaleway.com"
} |
| provider | {
"id": "safebase",
"name": "SafeBase"
} |
| links | {
"self": "/v1/security-updates/upd_466db7dd19796372",
"company": "/v1/companies/org_9c40dfe3f8d30eb8",
"trust_center": "/v1/trust-centers/tc_97ceaa0bb95c8ff7",
"provider": "/v1/providers/safebase"
} |
Get this page with API
Rendered from the bluedoor Trust Centers API. Reproduce it:
GET https://api.bluedoor.sh/trust-centers/v1/security-updates/upd_466db7dd19796372JSON