CVE-2022-50754Published Dec 24, 2025 · Dec 24Updated Nov 12
apparmor: fix a memleak in multi_transaction_new()
Linux
Unrated
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1dea3b41e84c5923173fe654dcb758a5cb4a46e5 · < 88989932c2269ea66074f52a6213598838f8b9e7| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
apparmor: fix a memleak in multi_transaction_new()
In multi_transaction_new(), the variable t is not freed or passed out on the failure of copy_from_user(t->data, buf, size), which could lead to a memleak.
Fix this bug by adding a put_multi_transaction(t) in the error path.
From the CVE record · Linux
AppArmor's multi_transaction_new() can leak memory if copy_from_user() fails, because it does not release the transaction. The input does not establish how an attacker could trigger the failure or whether authentication or user interaction is required.
Engineers running the Linux kernel should check their AppArmor installations; affected versions are not specified.