| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2024-56741: apparmor: test: Fix memory leak for aa_unpack_strdup() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| apparmor: test: Fix memory leak for aa_unpack_strdup() |
| |
| The string allocated by kmemdup() in aa_unpack_strdup() is not |
| freed and cause following memory leaks, free them to fix it. |
| |
| unreferenced object 0xffffff80c6af8a50 (size 8): |
| comm "kunit_try_catch", pid 225, jiffies 4294894407 |
| hex dump (first 8 bytes): |
| 74 65 73 74 69 6e 67 00 testing. |
| backtrace (crc 5eab668b): |
| [<0000000001e3714d>] kmemleak_alloc+0x34/0x40 |
| [<000000006e6c7776>] __kmalloc_node_track_caller_noprof+0x300/0x3e0 |
| [<000000006870467c>] kmemdup_noprof+0x34/0x60 |
| [<000000001176bb03>] aa_unpack_strdup+0xd0/0x18c |
| [<000000008ecde918>] policy_unpack_test_unpack_strdup_with_null_name+0xf8/0x3ec |
| [<0000000032ef8f77>] kunit_try_run_case+0x13c/0x3ac |
| [<00000000f3edea23>] kunit_generic_run_threadfn_adapter+0x80/0xec |
| [<00000000adf936cf>] kthread+0x2e8/0x374 |
| [<0000000041bb1628>] ret_from_fork+0x10/0x20 |
| unreferenced object 0xffffff80c2a29090 (size 8): |
| comm "kunit_try_catch", pid 227, jiffies 4294894409 |
| hex dump (first 8 bytes): |
| 74 65 73 74 69 6e 67 00 testing. |
| backtrace (crc 5eab668b): |
| [<0000000001e3714d>] kmemleak_alloc+0x34/0x40 |
| [<000000006e6c7776>] __kmalloc_node_track_caller_noprof+0x300/0x3e0 |
| [<000000006870467c>] kmemdup_noprof+0x34/0x60 |
| [<000000001176bb03>] aa_unpack_strdup+0xd0/0x18c |
| [<0000000046a45c1a>] policy_unpack_test_unpack_strdup_with_name+0xd0/0x3c4 |
| [<0000000032ef8f77>] kunit_try_run_case+0x13c/0x3ac |
| [<00000000f3edea23>] kunit_generic_run_threadfn_adapter+0x80/0xec |
| [<00000000adf936cf>] kthread+0x2e8/0x374 |
| [<0000000041bb1628>] ret_from_fork+0x10/0x20 |
| |
| The Linux kernel CVE team has assigned CVE-2024-56741 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.6 with commit 4d944bcd4e731ab7bfe8d01a7041ea0ebdc090f1 and fixed in 5.10.231 with commit f856246ff6da25c4f8fdd73a9c875e878b085e9f |
| Issue introduced in 5.6 with commit 4d944bcd4e731ab7bfe8d01a7041ea0ebdc090f1 and fixed in 5.15.174 with commit 5354599855a9b5568e05ce686119ee3ff8b19bd5 |
| Issue introduced in 5.6 with commit 4d944bcd4e731ab7bfe8d01a7041ea0ebdc090f1 and fixed in 6.1.120 with commit 89265f88701e54dde255ddf862093baeca57548c |
| Issue introduced in 5.6 with commit 4d944bcd4e731ab7bfe8d01a7041ea0ebdc090f1 and fixed in 6.6.64 with commit 2a9b68f2dc6812bd1b8880b5c00e60203d6f61f6 |
| Issue introduced in 5.6 with commit 4d944bcd4e731ab7bfe8d01a7041ea0ebdc090f1 and fixed in 6.11.11 with commit 59a149e7c38e7b76616c8b333fc6aa5b6fb2293c |
| Issue introduced in 5.6 with commit 4d944bcd4e731ab7bfe8d01a7041ea0ebdc090f1 and fixed in 6.12.2 with commit d62ee5739a66644b0e7f11e657d562458cdcdea3 |
| Issue introduced in 5.6 with commit 4d944bcd4e731ab7bfe8d01a7041ea0ebdc090f1 and fixed in 6.13 with commit 7290f59231910ccba427d441a6e8b8c6f6112448 |
| |
| Please see https://www.kernel.org for a full list of currently supported |
| kernel versions by the kernel community. |
| |
| Unaffected versions might change over time as fixes are backported to |
| older supported kernel versions. The official CVE entry at |
| https://cve.org/CVERecord/?id=CVE-2024-56741 |
| will be updated if fixes are backported, please check that for the most |
| up to date information about this issue. |
| |
| |
| Affected files |
| ============== |
| |
| The file(s) affected by this issue are: |
| security/apparmor/policy_unpack_test.c |
| |
| |
| Mitigation |
| ========== |
| |
| The Linux kernel CVE team recommends that you update to the latest |
| stable kernel version for this, and many other bugfixes. Individual |
| changes are never tested alone, but rather are part of a larger kernel |
| release. Cherry-picking individual commits is not recommended or |
| supported by the Linux kernel community at all. If however, updating to |
| the latest release is impossible, the individual changes to resolve this |
| issue can be found at these commits: |
| https://git.kernel.org/stable/c/f856246ff6da25c4f8fdd73a9c875e878b085e9f |
| https://git.kernel.org/stable/c/5354599855a9b5568e05ce686119ee3ff8b19bd5 |
| https://git.kernel.org/stable/c/89265f88701e54dde255ddf862093baeca57548c |
| https://git.kernel.org/stable/c/2a9b68f2dc6812bd1b8880b5c00e60203d6f61f6 |
| https://git.kernel.org/stable/c/59a149e7c38e7b76616c8b333fc6aa5b6fb2293c |
| https://git.kernel.org/stable/c/d62ee5739a66644b0e7f11e657d562458cdcdea3 |
| https://git.kernel.org/stable/c/7290f59231910ccba427d441a6e8b8c6f6112448 |