APPLIED[J]/Cmnt: [SRU] [Jammy] [PATCH 0/1] UBUNTU: audit: fix memory leak of audit_log_lsm()
Jianlin Lv
iecedge at gmail.com
Fri Feb 24 14:24:11 UTC 2023
On Fri, Feb 24, 2023 at 5:44 PM Stefan Bader <stefan.bader at canonical.com> wrote:
>
> On 17.02.23 18:05, Jianlin Lv wrote:
> > BugLink: https://bugs.launchpad.net/bugs/1987430
> >
> > [Impact]
> >
> > Under upgrading server to Ubuntu 22.04 with kernel 5.15.0-XX, memory
> > started to ramp up slowly that growth ~1 GB a day.
> >
> > [Fix]
> >
> > The memory leak is an allocated struct audit_buffer object in
> > audit_log_lsm() that to record LSM attributes.
> > Free audit buffer before audit_log_lsm() return.
> >
> > [Test Plan]
> >
> > 1.Disable apparmor module by append apparmor=0 to grub
> >
> > 2.Start auditd service with following audit rule:
> > -a exit,always -F arch=b64 -S execve
> > -a exit,always -F arch=b32 -S execve
> >
> > 3.Using Kmemleak to check if memory leak has occurred
> > $ cat /sys/kernel/debug/kmemleak
> > or Keep watching for changes in slabinfo
> > $ watch "sudo cat /proc/slabinfo | grep kmalloc-2k"
> >
> > Jianlin Lv (1):
> > UBUNTU: audit: fix memory leak of audit_log_lsm()
> >
> > kernel/auditsc.c | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
> >
>
> Applied to jammy:linux/master-next adding "SAUCE:" and a "Fixes:".
> Thanks. I saw that the bug report also has a Kinetic task but not seeing
> any submission for that. Is that expected?
Have no background about why this memleak issue affects Kinetic.
Check auditsc.c of Kinetic and didn't find the same memleak issue as jammy.
Jianlin
>
> -Stefan
>
> --
> kernel-team mailing list
> kernel-team at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/kernel-team
More information about the kernel-team
mailing list