diff options
| author | Zhan Xusheng <zhanxusheng1024@gmail.com> | 2026-07-18 13:09:22 +0800 |
|---|---|---|
| committer | Paul Moore <paul@paul-moore.com> | 2026-07-29 16:19:06 -0400 |
| commit | f865c143629d4094866a811dba5f329250bad486 (patch) | |
| tree | 21e45247baabc84a9ab7f99c3981e5691d82e90f /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | f5098b6bae761e346ebcd9da7f95622c04733cff (diff) | |
audit: fix potential integer overflow in audit_log_n_string()
audit_log_n_string() computes new_len as "slen + 3" (enclosing quotes
plus the NUL terminator) and stores it into an int, while slen is a
size_t. For a sufficiently large slen the addition can overflow and/or
the result be truncated when assigned to the int new_len, so the
"new_len > avail" check can be bypassed and the subsequent
memcpy(ptr, string, slen) can write past the skb tail.
This is the same class of bug that was fixed for the hex sibling in
commit 65dfde57d1e2 ("audit: fix potential integer overflow in
audit_log_n_hex()"); both helpers are reached through
audit_log_n_untrustedstring() with the same length source.
Make new_len a size_t and use check_add_overflow() to catch the
overflow, mirroring the audit_log_n_hex() fix. No functional change for
the in-tree callers, which all pass bounded lengths.
Cc: stable@vger.kernel.org
Fixes: 168b7173959f ("AUDIT: Clean up logging of untrusted strings")
Signed-off-by: Zhan Xusheng <zhanxusheng@xiaomi.com>
Signed-off-by: Paul Moore <paul@paul-moore.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions
