CVE-2021-47603

audit: improve robustness of the audit queue handling

MEDIUM
4.4
CVSS Score
Published: June 19, 2024 at 02:54 PM UTC
Updated: June 17, 2026 at 04:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.4
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: audit: improve robustness of the audit queue handling If the audit daemon were ever to get stuck in a stopped state the kernel's kauditd_thread() could get blocked attempting to send audit records to the userspace audit daemon. With the kernel thread blocked it is possible that the audit queue could grow unbounded as certain audit record generating events must be exempt from the queue limits else the system enter a deadlock state. This patch resolves this problem by lowering the kernel thread's socket sending timeout from MAX_SCHEDULE_TIMEOUT to HZ/10 and tweaks the kauditd_send_queue() function to better manage the various audit queues when connection problems occur between the kernel and the audit daemon. With this patch, the backlog may temporarily grow beyond the defined limits when the audit daemon is stopped and the system is under heavy audit pressure, but kauditd_thread() will continue to make progress and drain the queues as it would for other connection problems. For example, with the audit daemon put into a stopped state and the system configured to audit every syscall it was still possible to shutdown the system without a kernel panic, deadlock, etc.; granted, the system was slow to shutdown but that is to be expected given the extreme pressure of recording every syscall. The timeout value of HZ/10 was chosen primarily through experimentation and this developer's "gut feeling". There is likely no one perfect value, but as this scenario is limited in scope (root privileges would be needed to send SIGSTOP to the audit daemon), it is likely not worth exposing this as a tunable at present. This can always be done at a later date if it proves necessary.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 4.10.74.10.7 ≤ v < 4.114.11 ≤ v < 4.14.2594.11 ≤ v < 4.19.2224.11 ≤ v < 5.10.884.11 ≤ v < 5.15.114.11 ≤ v < 5.164.11 ≤ v < 5.4.1684.15 ≤ v < 4.19.2224.20 ≤ v < 5.4.1685.11 ≤ v < 5.15.115.5 ≤ v < 5.10.884.10.75.16 rc15.16 rc25.16 rc35.16 rc45.16 rc55b52330bbfe63b3305765354d6046c9f7f89c011a0c48115cd2343231585f2f5e609b2ac9aa4e0af
Vendor states this is fixed in 0d3277eabd542fb662be23696e5ec9f390d688e1 (fixed)
Vendor states this is fixed in 4cc6badff97f74d0fce65f9784b5df3b64e4250b (fixed)
Vendor states this is fixed in 75fdb751f84727d614deea0571a1490c3225d83a (fixed)
Vendor states this is fixed in 8389f50ceb854cb437fefb9330d5024ed3c7c1f5 (fixed)
Vendor states this is fixed in a5f4d17daf2e6cd7c1d9676b476147f6b4ac53f2 (fixed)
Vendor states this is fixed in f4b3ee3c85551d2d343a3ba159304066523f730f (fixed)
Vendor states this is fixed in 4.11 (unaffected)
Vendor states this is fixed in 4.14.259 (unaffected)
Vendor states this is fixed in 4.19.222 (unaffected)
Vendor states this is fixed in 5.10.88 (unaffected)
Vendor states this is fixed in 5.15.11 (unaffected)
Vendor states this is fixed in 5.16 (unaffected)
Vendor states this is fixed in 5.4.168 (unaffected)

References (6)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/0d3277eabd542fb662be23696e5ec9f390d688e1
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/4cc6badff97f74d0fce65f9784b5df3b64e4250b
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/75fdb751f84727d614deea0571a1490c3225d83a
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/8389f50ceb854cb437fefb9330d5024ed3c7c1f5
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/a5f4d17daf2e6cd7c1d9676b476147f6b4ac53f2
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/f4b3ee3c85551d2d343a3ba159304066523f730f

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
HIGH
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-667

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card