mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: audit@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] audit/audit-pr-20260730
Date: Thu, 30 Jul 2026 17:20:07 -0400	[thread overview]
Message-ID: <c551862a4b55c930fd56840d2b30d495@paul-moore.com> (raw)

Linus,

Two audit fixes for the next Linux v7.2-rc release:

- Fix potential integer overflows in audit_log_n_string()

  Similar to the earlier fix to audit_log_n_hex() that you merged earlier
  in July.  Expect a cleaner, and generally better fix for these
  functions in an upcoming merge window, but this addresses the problem
  in a small patch that should be easy for people to backport.

- Fix potential use-after-free in audit_del_rule()

Paul

--
The following changes since commit f5098b6bae761e346ebcd9da7f95622c04733cff:

  Linux 7.2-rc5 (2026-07-26 14:45:48 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/audit.git
    tags/audit-pr-20260730

for you to fetch changes up to 246df90b5f1a8a6e6abbd2f058b029558720adec:

  audit: fix potential use-after-free in audit_del_rule()
    (2026-07-29 16:19:06 -0400)

----------------------------------------------------------------
audit/stable-7.2 PR 20260730
----------------------------------------------------------------

Luxiao Xu (1):
      audit: fix potential use-after-free in audit_del_rule()

Zhan Xusheng (1):
      audit: fix potential integer overflow in audit_log_n_string()

 kernel/audit.c       |   11 +++++++++--
 kernel/auditfilter.c |    6 ++++--
 2 files changed, 13 insertions(+), 4 deletions(-)

--
paul-moore.com

             reply	other threads:[~2026-07-30 21:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30 21:20 Paul Moore [this message]
2026-07-30 22:15 ` pr-tracker-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c551862a4b55c930fd56840d2b30d495@paul-moore.com \
    --to=paul@paul-moore.com \
    --cc=audit@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®