CVE-2024-53128: Medium Vulnerability in Linux Kernel

In the Linux kernel, the following vulnerability has been resolved: sched/task_stack: fix object_is_on_stack() for KASAN tagged pointers. When CONFIG_KASAN_SW_TAGS and CONFIG_KASAN_STACK are enabled, the object_is_on_stack() function may produce incorrect results due to the presence of tags in the obj pointer, while the stack pointer does not have tags. This discrepancy can lead to incorrect stack object detection and subsequently trigger warnings if CONFIG_DEBUG_OBJECTS is also enabled. Example of the warning: ODEBUG: object 3eff800082ea7bb0 is NOT on stack ffff800082ea0000, but annotated. ------------[ cut here ]------------ WARNING: CPU: 0 PID: 1 at lib/debugobjects.c:557 __debug_object_init+0x330/0x364 Modules linked in: CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.0-rc5 #4 Hardware name: linux,dummy-virt (DT) pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __debug_object_init+0x330/0x364 lr : __debug_object_init+0x330/0x364 sp : ffff800082ea7b40 x29: ffff800082ea7b40 x28: 98ff0000c0164518 x27: 98ff0000c0164534 x26: ffff800082d93ec8 x25: 0000000000000001 x24: 1cff0000c00172a0 x23: 0000000000000000 x22: ffff800082d93ed0 x21: ffff800081a24418 x20: 3eff800082ea7bb0 x19: efff800000000000 x18: 0000000000000000 x17: 00000000000000ff x16: 0000000000000047 x15: 206b63617473206e x14: 0000000000000018 x13: ffff800082ea7780 x12: 0ffff800082ea78e x11: 0ffff800082ea790 x10: 0ffff800082ea79d x9 : 34d77febe173e800 x8 : 34d77febe173e800 x7 : 0000000000000001 x6 : 0000000000000001 x5 : feff800082ea74b8 x4 : ffff800082870a90 x3 : ffff80008018d3c4 x2 : 0000000000000001 x1 : ffff800082858810 x0 : 0000000000000050 Call trace: __debug_object_init+0x330/0x364 debug_object_init_on_stack+0x30/0x3c schedule_hrtimeout_range_clock+0xac/0x26c schedule_hrtimeout+0x1c/0x30 wait_task_inactive+0x1d4/0x25c kthread_bind_mask+0x28/0x98 init_rescuer+0x1e8/0x280 workqueue_init+0x1a0/0x3cc kernel_init_freeable+0x118/0x200 kernel_init+0x28/0x1f0 ret_from_fork+0x10/0x20 ---[ end trace 0000000000000000 ]--- ODEBUG: object 3eff800082ea7bb0 is NOT on stack ffff800082ea0000, but annotated. ------------[ cut here ]------------

Vulnerability Details

This vulnerability allows incorrect stack object detection when specific kernel configurations are enabled. The CVSS score is 5.5, indicating a medium severity level due to potential high availability impact with no confidentiality or integrity impacts. The affected product is the Linux kernel.

Technical Analysis

The root cause of the vulnerability stems from the object_is_on_stack() function, which fails to accurately determine if an object is on the stack due to the presence of KASAN tagged pointers. The attack vector is local, requiring low complexity and privileges, with no user interaction needed. The availability impact is categorized as high, while confidentiality and integrity impacts are none.

Risk & Impact Analysis

Risk to organizations includes potential system instability due to incorrect stack object detection, which may lead to crashes or unintended behavior. Given the medium CVSS score and the fact that it is not actively exploited, organizations should address this in their priority patch cycle.

Exploitation Status

Affected Versions

All versions prior to vendor patch 6.11.10 are affected.

Mitigation & Remediation

Organizations should prioritize patching immediately. Ensure that the kernel is updated to the latest version that includes the fix for this vulnerability. For further security practices, consider implementing penetration testing to identify similar weaknesses.

Detection Guidance

Monitor for log indicators related to stack object detection warnings. Behavioral anomalies during kernel operations should be noted, especially if CONFIG_DEBUG_OBJECTS is enabled.

AppSecure Threat Intelligence Insight

The long-term significance of this vulnerability highlights the importance of thorough testing in kernel configurations. Security teams should review their kernel settings regularly to prevent similar vulnerabilities. For additional insights, consider reviewing our penetration testing methodology and how to address vulnerabilities effectively. Additionally, organizations are encouraged to explore our resources on vulnerability management and security testing best practices to strengthen their defenses.