CVE-2021-46939

Aliases:UBUNTU-CVE-2021-46939DEBIAN-CVE-2021-46939
Advisory lineage Upstream: 0 Downstream: 11
Modified
Published: 27 Feb 2024, 18:40
Last modified:11 May 2026, 13:44

Vulnerability Summary

Overall Risk (default)
low
22/100
CVSS Score
5.5 MEDIUM
v3.1 (cve.org)
EPSS Score
0.25% LOW
0% probability +0.24%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

27 Feb 2024, 18:40
Published
Vulnerability first disclosed
11 May 2026, 13:44
Last Modified
Vulnerability information updated

Description

In the Linux kernel, the following vulnerability has been resolved: tracing: Restructure trace_clock_global() to never block It was reported that a fix to the ring buffer recursion detection would cause a hung machine when performing suspend / resume testing. The following backtrace was extracted from debugging that case: Call Trace: trace_clock_global+0x91/0xa0 __rb_reserve_next+0x237/0x460 ring_buffer_lock_reserve+0x12a/0x3f0 trace_buffer_lock_reserve+0x10/0x50 __trace_graph_return+0x1f/0x80 trace_graph_return+0xb7/0xf0 ? trace_clock_global+0x91/0xa0 ftrace_return_to_handler+0x8b/0xf0 ? pv_hash+0xa0/0xa0 return_to_handler+0x15/0x30 ? ftrace_graph_caller+0xa0/0xa0 ? trace_clock_global+0x91/0xa0 ? __rb_reserve_next+0x237/0x460 ? ring_buffer_lock_reserve+0x12a/0x3f0 ? trace_event_buffer_lock_reserve+0x3c/0x120 ? trace_event_buffer_reserve+0x6b/0xc0 ? trace_event_raw_event_device_pm_callback_start+0x125/0x2d0 ? dpm_run_callback+0x3b/0xc0 ? pm_ops_is_empty+0x50/0x50 ? platform_get_irq_byname_optional+0x90/0x90 ? trace_device_pm_callback_start+0x82/0xd0 ? dpm_run_callback+0x49/0xc0 With the following RIP: RIP: 0010:native_queued_spin_lock_slowpath+0x69/0x200 Since the fix to the recursion detection would allow a single recursion to happen while tracing, this lead to the trace_clock_global() taking a spin lock and then trying to take it again: ring_buffer_lock_reserve() { trace_clock_global() { arch_spin_lock() { queued_spin_lock_slowpath() { /* lock taken */ (something else gets traced by function graph tracer) ring_buffer_lock_reserve() { trace_clock_global() { arch_spin_lock() { queued_spin_lock_slowpath() { /* DEAD LOCK! */ Tracing should *never* block, as it can lead to strange lockups like the above. Restructure the trace_clock_global() code to instead of simply taking a lock to update the recorded "prev_time" simply use it, as two events happening on two different CPUs that calls this at the same time, really doesn't matter which one goes first. Use a trylock to grab the lock for updating the prev_time, and if it fails, simply try again the next time. If it failed to be taken, that means something else is already updating it. Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=212761

CVSS Metrics

  • v3.1•MEDIUM•Score: 5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS Trends

Current EPSS score: 0.25%• Percentile: 16%

Techniques & Countermeasures

  • CWE-662•Improper Synchronization

    The product utilizes multiple threads, processes, components, or systems to allow temporary access to a shared resource that can only be exclusive to one process at a time, but it does not properly synchronize these actions, which might cause simultaneous accesses of this resource by multiple threads or processes.

  • CWE-400•Uncontrolled Resource Consumption

    The product does not properly control the allocation and maintenance of a limited resource.

Affected Systems

  • debian•linux

    < 5.10.38-1 | < 5.10.38-1 | < 5.10.38-1 | < 5.10.38-1

  • ubuntu•linux

    all | < 4.4.0-254.288 | < 4.15.0-151.157 | < 5.4.0-77.86

  • ubuntu•linux-allwinner-5.19

    all

  • ubuntu•linux-aws

    < 4.4.0-1131.137 | < 4.4.0-1169.184 | < 4.15.0-1109.116 | < 5.4.0-1051.53

  • ubuntu•linux-aws-5.0

    all

  • ubuntu•linux-aws-5.11

    all

  • ubuntu•linux-aws-5.13

    all

  • ubuntu•linux-aws-5.19

    all

  • ubuntu•linux-aws-5.3

    all

  • ubuntu•linux-aws-5.4

    < 5.4.0-1051.53~18.04.1

  • ubuntu•linux-aws-5.8

    all

  • ubuntu•linux-aws-6.2

    all

  • ubuntu•linux-aws-fips

    < 4.15.0-2051.53 | all | < 5.4.0-1069.73+fips2

  • ubuntu•linux-aws-hwe

    < 4.15.0-1109.116~16.04.1

  • ubuntu•linux-azure

    < 4.15.0-1121.134~14.04.1 | < 4.15.0-1121.134~16.04.1 | all | < 5.4.0-1051.53

  • ubuntu•linux-azure-4.15

    < 4.15.0-1121.134

  • ubuntu•linux-azure-5.11

    all

  • ubuntu•linux-azure-5.13

    all

  • ubuntu•linux-azure-5.19

    all

  • ubuntu•linux-azure-5.3

    all

  • ubuntu•linux-azure-5.4

    < 5.4.0-1051.53~18.04.1

  • ubuntu•linux-azure-5.8

    all

  • ubuntu•linux-azure-6.2

    all

  • ubuntu•linux-azure-edge

    all

  • ubuntu•linux-azure-fde

    all

  • ubuntu•linux-azure-fde-5.19

    all

  • ubuntu•linux-azure-fde-6.2

    all

  • ubuntu•linux-azure-fips

    < 4.15.0-2033.37 | all | < 5.4.0-1073.76+fips1

  • ubuntu•linux-bluefield

    all | < 5.4.0-1013.16

  • ubuntu•linux-fips

    < 4.4.0-1101.108 | all | < 4.15.0-1066.75 | < 5.4.0-1028.32

  • ubuntu•linux-gcp

    < 4.15.0-1106.120~16.04.1 | all | < 5.4.0-1046.49

  • ubuntu•linux-gcp-4.15

    < 4.15.0-1106.120

  • ubuntu•linux-gcp-5.11

    all

  • ubuntu•linux-gcp-5.13

    all

  • ubuntu•linux-gcp-5.19

    all

  • ubuntu•linux-gcp-5.3

    all

  • ubuntu•linux-gcp-5.4

    < 5.4.0-1046.49~18.04.1

  • ubuntu•linux-gcp-5.8

    all

  • ubuntu•linux-gcp-6.2

    all

  • ubuntu•linux-gcp-fips

    < 4.15.0-2016.18 | all | < 5.4.0-1067.71~20.04.1

  • ubuntu•linux-gke

    all

  • ubuntu•linux-gke-4.15

    all

  • ubuntu•linux-gke-5.15

    all

  • ubuntu•linux-gke-5.4

    all

  • ubuntu•linux-gkeop

    < 5.4.0-1018.19

  • ubuntu•linux-gkeop-5.4

    all

  • ubuntu•linux-hwe

    < 4.15.0-151.157~16.04.1 | all

  • ubuntu•linux-hwe-5.11

    all

  • ubuntu•linux-hwe-5.13

    all

  • ubuntu•linux-hwe-5.19

    all

Showing first 50 affected entries in server-rendered view.

References (14)