CVE-2021-47603 json
audit: improve robustness of the audit queue handling
published 2024-06-19 2 y ago modified 2026-06-17 4 mo ago also EUVD-2021-34605
- cvss
- 4.4
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 4.11, 4.14.259, 4.19.222, 5.4.168, 5.10.88, 5.15.11, 5.16
- linux Debian 14, Debian 13, Debian 12 5.15.15-1
debian advisories DEBIAN-CVE-2021-47603
- linux Ubuntu 18.04 LTS 4.15.0-169.177
- linux Ubuntu 20.04 LTS 5.4.0-105.119
- linux-aws Ubuntu 18.04 LTS 4.15.0-1121.129
- linux-aws Ubuntu 20.04 LTS 5.4.0-1069.73
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1068.72
- linux-ibm Ubuntu 20.04 LTS 5.4.0-1018.20
- linux-kvm Ubuntu 18.04 LTS 4.15.0-1107.109
- linux-kvm Ubuntu 20.04 LTS 5.4.0-1059.62
ubuntu advisories UBUNTU-CVE-2021-47603
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- dtb-aarch64 openSUSE Leap 15.5 5.14.21-150500.55.73.1
- kernel-64kb SLE Module for Basesystem 15 SP5, openSUSE Leap 15.5 5.14.21-150500.55.73.1
- kernel-syms SLE Module for Development Tools 15 SP5, openSUSE Leap 15.5 5.14.21-150500.55.73.1
- kernel-obs-qa openSUSE Leap 15.5 5.14.21-150500.55.73.1
- kernel-source SLE Module for Development Tools 15 SP5, SLE Module for Basesystem 15 SP5, openSUSE Leap 15.5 5.14.21-150500.55.73.1
- kernel-default SLE Workstation Extension 15 SP5, SLE Module for Legacy 15 SP5, SLE Module for Basesystem 15 SP5 +5 more 5.14.21-150500.55.73.1
- kernel-kvmsmall openSUSE Leap 15.5 5.14.21-150500.55.73.1
- kernel-zfcpdump SLE Module for Basesystem 15 SP5, openSUSE Leap 15.5 5.14.21-150500.55.73.1
suse advisories SUSE-SU-2024:2939-1SUSE-SU-2024:2929-1SUSE-SU-2024:2902-1SUSE-SU-2024:2561-1SUSE-SU-2024:2394-1SUSE-SU-2024:2381-1
- git.kernel.org/stable/c/75fdb751f84727d614deea0571a1490c3225d83a commit
- git.kernel.org/stable/c/8389f50ceb854cb437fefb9330d5024ed3c7c1f5 commit
- git.kernel.org/stable/c/0d3277eabd542fb662be23696e5ec9f390d688e1 commit
- git.kernel.org/stable/c/4cc6badff97f74d0fce65f9784b5df3b64e4250b commit
- git.kernel.org/stable/c/a5f4d17daf2e6cd7c1d9676b476147f6b4ac53f2 commit
- git.kernel.org/stable/c/f4b3ee3c85551d2d343a3ba159304066523f730f commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2021-47603 updated cvss 4.4
kernel: audit: improve robustness of the audit queue handling
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 moreaffected: no fix available
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 4.4 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-667 Improper Locking
- Technology feeds
References
-
git.kernel.org
/stable/c/75fdb751f84727d614deea0571a1490c3225d83a
patch
-
git.kernel.org
/stable/c/8389f50ceb854cb437fefb9330d5024ed3c7c1f5
patch
-
git.kernel.org
/stable/c/0d3277eabd542fb662be23696e5ec9f390d688e1
patch
-
git.kernel.org
/stable/c/4cc6badff97f74d0fce65f9784b5df3b64e4250b
patch
-
git.kernel.org
/stable/c/a5f4d17daf2e6cd7c1d9676b476147f6b4ac53f2
patch
-
git.kernel.org
/stable/c/f4b3ee3c85551d2d343a3ba159304066523f730f
patch
Sources
- CVE List CVE-2021-47603
- NVD CVE-2021-47603
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.